GPU builds fail

With the newest release (v0.8.11) i can't build any solutions for gpu anymore.
The problem does not occur with release v<IP_ADDRESS>.
System information (Please provide as much relevant information as possible)

OS Platform and Distribution (e.g. Linux Ubuntu 16.04, Android 11, iOS 14.4):
Ubuntu 18.04.6 LTS
Compiler version (e.g. gcc/g++ 8 /Apple clang version 12.0.0):
gcc/g++ 8.4.0
Installed using virtualenv? pip? Conda? (if python):
no
MediaPipe version:
0.8.11
Bazel version:
5.2.0
OpenCV version (if running on desktop):
3.2.0 (output of dpkg -l | grep libopencv)

Build command / log
bazel build --copt -DMESA_EGL_NO_X11_HEADERS --copt -DEGL_NO_X11 mediapipe/examples/desktop/face_mesh:face_mesh_gpu

Starting local Bazel server and connecting to it...
DEBUG: Rule 'rules_foreign_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "c2cdcf55ffaf49366725639e45dedd449b8c3fe22b54e31625eb80ce3a240f1e"
DEBUG: Repository rules_foreign_cc instantiated at:
  /home/mldev1/Documents/Misc/mediapipe-official/WORKSPACE:49:13: in <toplevel>
Repository rule http_archive defined at:
  /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/bazel_tools/tools/build_defs/repo/http.bzl:353:31: in <toplevel>
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'flatbuffers' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_googlesource_code_re2' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'zlib' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "691a29db9c336349e48e04c5c2f4873f2890af5cbfa6e51f4de87fefe6169294"
DEBUG: Repository rules_cc instantiated at:
  /home/mldev1/Documents/Misc/mediapipe-official/WORKSPACE:42:13: in <toplevel>
Repository rule http_archive defined at:
  /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/bazel_tools/tools/build_defs/repo/http.bzl:353:31: in <toplevel>
WARNING: /home/mldev1/Documents/Misc/mediapipe-official/mediapipe/framework/tool/BUILD:185:24: in cc_library rule //mediapipe/framework/tool:field_data_cc_proto: target '//mediapipe/framework/tool:field_data_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
WARNING: /home/mldev1/Documents/Misc/mediapipe-official/mediapipe/framework/BUILD:54:24: in cc_library rule //mediapipe/framework:calculator_cc_proto: target '//mediapipe/framework:calculator_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
INFO: Analyzed target //mediapipe/examples/desktop/face_mesh:face_mesh_gpu (150 packages loaded, 6167 targets configured).
INFO: Found 1 target...
INFO: From Compiling mediapipe/framework/tool/message_type_util.cc [for host]:
mediapipe/framework/tool/message_type_util.cc: In static member function 'static int mediapipe::DescriptorReader::MatchingPrefixLength(const string&, const string&)':
mediapipe/framework/tool/message_type_util.cc:66:14: warning: comparison of integer expressions of different signedness: 'int' and 'const long unsigned int' [-Wsign-compare]
     while (i < std::min(s.size(), t.size()) && s[i] == t[i]) {
            ~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: From Compiling tensorflow/lite/delegates/gpu/api.cc:
In file included from external/opencl_headers/CL/cl.h:20,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/api.h:43,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/api.cc:16:
external/opencl_headers/CL/cl_version.h:22:104: note: #pragma message: cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)
 #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)")
                                                                                ^
INFO: From Compiling tensorflow/lite/delegates/gpu/gl/api2.cc:
In file included from external/opencl_headers/CL/cl.h:20,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/api.h:43,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/api2.h:23,
                 from external/org_tensorflow/tensorflow/lite/delegates/gpu/gl/api2.cc:16:
external/opencl_headers/CL/cl_version.h:22:104: note: #pragma message: cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)
 #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)")
                                                                                ^
ERROR: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/tensorflow/lite/kernels/BUILD:718:11: Compiling tensorflow/lite/kernels/batch_matmul.cc failed: (Exit 1): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer '-std=c++0x' -MD -MF ... (remaining 93 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/pmmintrin.h:31,
                 from /usr/lib/gcc/x86_64-linux-gnu/8/include/tmmintrin.h:31,
                 from /usr/lib/gcc/x86_64-linux-gnu/8/include/smmintrin.h:32,
                 from external/gemmlowp/fixedpoint/./fixedpoint_sse.h:21,
                 from external/gemmlowp/fixedpoint/fixedpoint.h:907,
                 from external/org_tensorflow/tensorflow/lite/kernels/internal/common.h:27,
                 from external/org_tensorflow/tensorflow/lite/kernels/internal/reference/batch_matmul.h:21,
                 from external/org_tensorflow/tensorflow/lite/kernels/batch_matmul.cc:16:
external/arm_neon_2_x86_sse/NEON_2_SSE.h: In static member function 'static void tflite::cpu_backend_gemm::detail::CustomGemvImpl<LhsScalar, RhsScalar, int, DstScalar, quantization_flavor>::Run(const tflite::cpu_backend_gemm::MatrixParams<LhsScalar>&, const LhsScalar*, const tflite::cpu_backend_gemm::MatrixParams<RhsScalar>&, const RhsScalar*, const tflite::cpu_backend_gemm::MatrixParams<DstScalar>&, DstScalar*, const tflite::cpu_backend_gemm::GemmParams<int, DstScalar, quantization_flavor>&, int, int) [with LhsScalar = signed char; RhsScalar = signed char; DstScalar = signed char; tflite::cpu_backend_gemm::QuantizationFlavor quantization_flavor = (tflite::cpu_backend_gemm::QuantizationFlavor)1]':
external/arm_neon_2_x86_sse/NEON_2_SSE.h:2290:30: error: selector must be an integer constant in the range 0..7
     #define _MM_INSERT_EPI16 _mm_insert_epi16
                              ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:9363:40: note: in expansion of macro '_MM_INSERT_EPI16'
 #define vld1q_lane_s16(ptr, vec, lane) _MM_INSERT_EPI16(vec, *(ptr), lane)
                                        ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:12084:12: note: in expansion of macro 'vld1q_lane_s16'
     return vld1q_lane_s16(&val, vec,  lane);
            ^~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:2290:30: error: selector must be an integer constant in the range 0..7
     #define _MM_INSERT_EPI16 _mm_insert_epi16
                              ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:9363:40: note: in expansion of macro '_MM_INSERT_EPI16'
 #define vld1q_lane_s16(ptr, vec, lane) _MM_INSERT_EPI16(vec, *(ptr), lane)
                                        ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:12084:12: note: in expansion of macro 'vld1q_lane_s16'
     return vld1q_lane_s16(&val, vec,  lane);
            ^~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:2290:30: error: selector must be an integer constant in the range 0..7
     #define _MM_INSERT_EPI16 _mm_insert_epi16
                              ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:9363:40: note: in expansion of macro '_MM_INSERT_EPI16'
 #define vld1q_lane_s16(ptr, vec, lane) _MM_INSERT_EPI16(vec, *(ptr), lane)
                                        ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:12084:12: note: in expansion of macro 'vld1q_lane_s16'
     return vld1q_lane_s16(&val, vec,  lane);
            ^~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:2290:30: error: selector must be an integer constant in the range 0..7
     #define _MM_INSERT_EPI16 _mm_insert_epi16
                              ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:9363:40: note: in expansion of macro '_MM_INSERT_EPI16'
 #define vld1q_lane_s16(ptr, vec, lane) _MM_INSERT_EPI16(vec, *(ptr), lane)
                                        ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:12084:12: note: in expansion of macro 'vld1q_lane_s16'
     return vld1q_lane_s16(&val, vec,  lane);
            ^~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:2290:30: error: selector must be an integer constant in the range 0..7
     #define _MM_INSERT_EPI16 _mm_insert_epi16
                              ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:9363:40: note: in expansion of macro '_MM_INSERT_EPI16'
 #define vld1q_lane_s16(ptr, vec, lane) _MM_INSERT_EPI16(vec, *(ptr), lane)
                                        ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:12084:12: note: in expansion of macro 'vld1q_lane_s16'
     return vld1q_lane_s16(&val, vec,  lane);
            ^~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:2290:30: error: selector must be an integer constant in the range 0..7
     #define _MM_INSERT_EPI16 _mm_insert_epi16
                              ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:9363:40: note: in expansion of macro '_MM_INSERT_EPI16'
 #define vld1q_lane_s16(ptr, vec, lane) _MM_INSERT_EPI16(vec, *(ptr), lane)
                                        ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:12084:12: note: in expansion of macro 'vld1q_lane_s16'
     return vld1q_lane_s16(&val, vec,  lane);
            ^~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:2290:30: error: selector must be an integer constant in the range 0..7
     #define _MM_INSERT_EPI16 _mm_insert_epi16
                              ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:9363:40: note: in expansion of macro '_MM_INSERT_EPI16'
 #define vld1q_lane_s16(ptr, vec, lane) _MM_INSERT_EPI16(vec, *(ptr), lane)
                                        ^~~~~~~~~~~~~~~~
external/arm_neon_2_x86_sse/NEON_2_SSE.h:12084:12: note: in expansion of macro 'vld1q_lane_s16'
     return vld1q_lane_s16(&val, vec,  lane);
            ^~~~~~~~~~~~~~
Target //mediapipe/examples/desktop/face_mesh:face_mesh_gpu failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 439.866s, Critical Path: 223.17s
INFO: 1534 processes: 385 internal, 1149 linux-sandbox.
FAILED: Build did NOT complete successfully

Hi @vertify-mldev1, Due to the latest release 8.11, *tflite model and other large binaries are moved to Google Cloud Storage as mentioned in the release note. Please update your Python binaries if they are fetching models from GitHub (see download_utils.py) and let us know if this resolves the issue.
Thank you!

Hi @vertify-mldev1, Could you confirm that as per above comment you are able to build the facemeshgpuin the latest release 0.8.11 or still issue exists. Thank you!

Model download works without problems:
>>> download_utils.download_oss_model('mediapipe/modules/face_landmark/face_landmark.tflite')
Downloading model to /home/mldev1/Documents/mediapipe/mediapipe/modules/face_landmark/face_landmark.tflite

My problem is unrelated to that. During the build this python script won't be run anyway right?

Hi @vertify-mldev1, Models file are important while building the MediaPipe but due to latest release it might have impacted. Could you try once to build it with updated download_utils.py and please let us know if you are encountering the same error.
Thank you!

Yes, I aleady had the latest version of download_utils.py when i opened the issue

Hi @vertify-mldev1, Could you please provide compete steps to reproduce the issue and System information as mentioned in the template.
Thank you!

Sure, I now updated the problem description above

Hi @vertify-mldev1,
Could you please confirm that you are able to install Hello world example of MediaPipe as mentioned here to build Face Mesh in the ubuntu. Thank you!

Yes, the hello world example works:
bazel run --copt -DMESA_EGL_NO_X11_HEADERS --copt -DEGL_NO_X11     mediapipe/examples/desktop/hello_world:hello_world
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'flatbuffers' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_googlesource_code_re2' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'zlib' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /home/mldev1/.cache/bazel/_bazel_mldev1/824bf6172127d18cb1057a50b98d1e6a/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11' because it already exists.
WARNING: /home/mldev1/Documents/Misc/mediapipe-official/mediapipe/framework/BUILD:54:24: in cc_library rule //mediapipe/framework:calculator_cc_proto: target '//mediapipe/framework:calculator_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
WARNING: /home/mldev1/Documents/Misc/mediapipe-official/mediapipe/framework/tool/BUILD:185:24: in cc_library rule //mediapipe/framework/tool:field_data_cc_proto: target '//mediapipe/framework/tool:field_data_cc_proto' depends on deprecated target '@com_google_protobuf//:cc_wkt_protos': Only for backward compatibility. Do not use.
INFO: Analyzed target //mediapipe/examples/desktop/hello_world:hello_world (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //mediapipe/examples/desktop/hello_world:hello_world up-to-date:
  bazel-bin/mediapipe/examples/desktop/hello_world/hello_world
INFO: Elapsed time: 0.203s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
INFO: Build completed successfully, 1 total action
I20220921 13:45:00.808912 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809016 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809036 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809052 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809069 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809090 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809166 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809224 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809288 21287 hello_world.cc:57] Hello World!
I20220921 13:45:00.809346 21287 hello_world.cc:57] Hello World!

Could resolve the issue. I updated gcc/g++ to 9.4.0 and encountered some other build issues.
After cleaning the bazel cache (by running bazel clean --expunge) everything works.
Retried it with a clean bazel cache and gcc/g++ 8.4.0 and i got the same error as in the issue description.

Hi @vertify-mldev1,
Good to hear that the issue has been fixed as per above command mentioned. Could we move this issue to close status as it has been fixed. Thank you!

failed to build a debug type of examples with the same error, but successfully build opt type -c opt.
bazel build -c dbg --copt -DMEDIAPIPE_OMIT_EGL_WINDOW_BIT  --copt -DMESA_EGL_NO_X11_HEADERS --copt -DEGL_NO_X11 mediapipe/examples/desktop/selfie_segmentation:selfie_segmentation_gpu

mediapipe: v0.8.11
bazel 5.3.2
mediapipe redhat 8.4
gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)


Feature Request: Pause Transfers

Can you add the ability to pause the current transfer? Adding a pause option next to cancel in the notification would work the best imho.
Often I find the need to pause long transfers especially when it's eating up all my bandwidth.
Currently the only option is to cancel the transfer (hope there isn't another transfer queued) and restart it when I'm ready to resume the transfer.
Maybe suspending the process would work? If the transfer itself has its own pid. Anyway, I hope this is fairly easy to implement. Thanks in advance!

This functionality is dependent on upstream rclone, which does not expose an interface for pausing/resuming transfers. There is already some discussion in https://github.com/ncw/rclone/issues/87, but nothing substantial so far.
Suspending the process might work for some remotes, but maybe not at all on Android. I'll try to test it later in Termux.


Works on Windows, fails on Linux

I opened issue 4557 on the main Cypress repo but thought I'd link it here in case anyone has seen this.
I'm using cypress-cucumber-preprocessor on a new Angular 8 project. Cypress runs fine on Windows. The logs show that it's using browersify to run its plugins/index.js file. On Linux, it's using webpack and the plugins/index.js file doesn't get run. I don't know why it's picking webpack on Linux...

I asked a question on https://github.com/cypress-io/cypress/issues/4557 about this issue, please tag me there or here when you answer. The preprocessor repo runs on linux on circleCI (with webpack, typescript, and this repo itself), and on countless installations by people using it, so we know it works on Linux. :)
We need more info.


gulp-rev-napkin cleans up unhashed files after rev'ing

gulp-rev-napkin removes original files after they have been run through gulp-rev as mentioned in issue #147

Just tested. Looks great! Thanks!


add version-number-tag

Version number tag #95

There is something not right here. Looks like this PR includes the previous calendar related PR? Can you please re-open with a new clean PR?


RTMP SUPPORT THIS PLAYER

Is that player supporting RTMP streaming

No, it does not.  I don't believe there is any way to support RTMP streaming from JavaScript, given that we are largely restricted to HTTP transport and the containers and codecs supported by MediaSource.

@asifagaria, does this answer your question?  Anything else we can do for you on this issue?

Closing due to inactivity. Please feel free to reopen if there's something else we can do!


bump dcos-diagnostics

High Level Description
Bump dcos-diagnostics sha.
Change naming convention for diagnostics bundle to
bundle-$year-$month-$day-$unixtimestamp.zip
This PR is to solve a problem for windows environment, where colons in a filename is causing problems.
Related Issues
COPS-1875
Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
Unittest has been updated for this improvement. Current set of integration tests fully cover this.
[X] Read the DC/OS contributing guidelines
[X] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[X] Change log from the last version integrated (this should be a link to commits for easy verification and review): diff
[X] Test Results: dcos-diagnostics
[X] Code Coverage (if available): dcos-diagnostics

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

Looks good :D

The failed test is a CI failure, its being muted right now. good for ship it

@mesosphere-mergebot label ship it


FIX

Two comments:

Please add documentation to explain how an existing ROSA cluster can be used
Please follow steps here: https://ibm.github.io/cloud-pak-deployer/80-development/deployer-development-setup/#set-up-gpg-for-the-development-user to sign off your commits.

Two comments:

Please add documentation to explain how an existing ROSA cluster can be used
Please follow steps here: https://ibm.github.io/cloud-pak-deployer/80-development/deployer-development-setup/#set-up-gpg-for-the-development-user to sign off your commits.

Done.

I see the PR is still in draft. Do want to merge it?

Please add documentation here: https://github.com/IBM/cloud-pak-deployer/blob/main/docs/src/10-use-deployer/3-run/aws-rosa.md

Done


minor: enrich log

Codecov Report

Merging #5 (808d733) into master (6d7fe78) will increase coverage by 0.03%.
The diff coverage is 100.00%.

:exclamation: Current head 808d733 differs from pull request most recent head a0cd571. Consider uploading reports for the commit a0cd571 to get more accurate results

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
+ Coverage   95.71%   95.74%   +0.03%
==========================================
  Files           4        4
  Lines         140      141       +1
==========================================
+ Hits          134      135       +1
  Misses          6        6

Impacted Files
Coverage Δ

bk_monitor_report/reporter.py
90.00% <100.00%> (+0.16%)
:arrow_up:

Continue to review full report at Codecov.

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


kdump: collect dmesg along with a kdump

Colect plain-text dmesg log along with a kernel dump in order to simplify kernel debugging: sometimes it can be enough to take a look into a dmesg once in order to understand a root cause rather than to download kernel debug symbols, use the crash tool and dive deeper into the analysis.
And yes, I renamed the 'kcrash-' to 'kdump-' in order to have both files aligned, thus the log looks perfect now:
   >>>>>>>>>>>> Crashed kernel dmesg END <<<<<<<<<<
   kdump collected: /persist/kcrashes/kdump-2022-11-30-13-58-40.dump
   dmesg collected: /persist/kcrashes/dmesg-2022-11-30-13-58-40.log

Promise not to change filenames anymore!

Difference to the previous version:

add a commit which covers Erik's comment regarding ISO date format: date -iS


rm follows symlinks thus recursively deleting linked content

if x refers to root (as in /) then rm(x) deletes entire harddrive (according to my tests)
Reproduce steps
bash
```
mkdir -p /mnt/user/homes/alex/test
cd /mnt/user/homes/alex/test
ln -s /mnt/user/homes/alex/test subtest
echo test > test.file
echo test2 > subtest/test2.file
mkdir aDir
echo test3 > aDir/test3.file
Now run in ammonite
cd!(Path("/mnt/user/homes/alex/test")) rm! 'subtest
Problem:
Delete entire test-dir, except aDir (but also deleted its file). For some reason had that setup on my media -> /media folder, and then I played around using ammonite to delete the link, and OMG it took longer than 1 sec. So I broke the command, killed the shell, checked ps to make sure ammonite wasn't running, and then did some checks against the filesystem coverage with md5 that I have to check nothing got deleted. Phew!
rm definitely should not traverse symlinks dirs to wipe user content within dirs

see https://github.com/lihaoyi/Ammonite/pull/886

I just noticed the original rm-code only traverses and deletes linked directories when the file given to rm is a symlinked dir, not when subdirs contain symlinked dirs. The problem being the first line of the Walker.
def these = ls.iter(p)
This is also the reason why my suggested solution calls delete and not recursiveDelete on the root-target.
I don't know if this is actually a problem in the walker, or if it is desired behaviour in other areas. Of cause ls('symlinkedDir) should list the content of the symlinked dir, but maybe ls.rec('symlinkedDir) should not, since it does not recursively list content of other symlinked dirs.


chore: jx-demo-2 to 0.0.10

chore: Promote jx-demo-2 to version 0.0.10

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Note about citing clue.io

We concluded that it is ok to have Level 3-5 data on GitHub, although we will cite clue.io as the primary source and references for this data, similar to this README by @gwaygenomics
The following data will eventually be made available on clue.io/morphology
Level 1-5 + connectivity file of

REP (1571 compounds, A549, 48h, 6 doses)
LKCP (~360 compounds, MCF7/A549/U2OS, 6h/24h/48h, 3 doses)
DBG (a subset of LKCP)

Can I clarify what the different data levels are? Is this accurate?

Data
Level

Images
Level 1

SQLite File (single cell profiles )
Level 2

Aggregated Profiles with Well Information (metadata)
Level 3

Normalized Aggregated Profiles with Metadata
Level 4

Normalized and Feature Selected Aggregated Profiles with Metadata
Level 5

Can I clarify what the different data levels are? Is this accurate?

I have updated your table @gwaygenomics


Give flexibility to the users by allowing them to specify remote configuration

Grab some of the paths from the environment variables. It give flexibility to the users. For example constants.py can be modified as follows
REMOTE_CONF_DIR = os.environ['PRESTO_REMOTE_CONF_DIR'] if 'PRESTO_REMOTE_CONF_DIR' in os.environ else '/etc/presto'

For variables that get set in Presto config files, I think the right way to do this would be to get the values directly from the config files.  e.g. look at remote_config_util.py to see how we do this for the getting the Presto log directories and the catalog directory.  Even for these, it looks like in some places in the code the constants get used instead of calling these functions, so those usages just need to be replaced with the appropriate function call.

This is  a duplicate of https://github.com/prestodb/presto-admin/issues/229

Thank you for the comment.
I will update the code to fetch values from config files. I will push the changes whenever I get time


MqttApplicationMessageReceivedEventArgs: Prevent NullReferenceException.

Only set PacketIdentifier property of MqttApplicationMessageReceivedEventArgs if publishPacket is not null.
This prevents a NullReferenceException in cases publishPacket is null.
This should not happen in production code, but accepting a publishPacket argument which is null is useful in unit testing, where publishPacket is not important in many cases. In these unit test cases, it is convenient to initialize the publishPacket argument with null.
Based on: #1466

I will not approve this pull request because in my opinion this is not the right decision. In my opinion I forgot the null check for the parameter. So that ideally an exception will be thrown because the publish packet is mandatory. Unit Tests from other projects are not relevant for design decisions etc. made in this project. I assume it should be easy to just create an instance of the publish packet because it requires no parameters at all so that this choice should also perfectly work in your mentioned Unit Tests.


Added ability to explicitly set the edit mode and force changes. - REBASED

@mindscratch I recreated your PR with the addition of the new CI configs so I can properly ensure tests are passing.  I will close your other PR.


fix: strict report for stylex.create argument as object expression

What changed / motivation ?
I have fixed to report when a value other than an ObjectExpression is specified as an argument for stylex.create.
Additional Context

Pre-flight checklist

[x] I have read the contributing guidelines
Contribution Guidelines
[x] Performed a self-review of my code

I'll merge for now since the tests are still passing. The bigger refactor can wait.

@nmn

I don't think this change can be made without a bigger refactor, but I'll let the tests run in case this is accounted for.

What do you mean?
The only fix is that the following code is executed when a value other than ObjectExpression is specified as the argument to stylex.create.
https://github.com/facebook/stylex/blob/ca1dc8bfda5cccdb722fefdaaa0a48b2caa32b75/packages/eslint-plugin/src/stylex-valid-styles.js#L2745-L2755
Prior to this fix, the following code would not report a problem, but now it does.
stylex.create("test")
stylex.create(1)
const foo = {}
stylex.create(foo)

@kotarella1110 That's my misunderstanding. Thanks!


Still having build errors on 3.1.4 on XCode 12

Hi, thanks for getting 3.1.4 up to address the build errors on XCode 12.
Comparing the 3.1.3 (https://github.com/optimizely/objective-c-sdk/issues/448), the number of build errors goes down but there are some errors still remaining.

Thanks again for the hard work!

Workaround: use Legacy Build System. it works for me.

Great! We'll continue investigation for better solutions.

@AshleyDeng @mattiacantalu With 3.1.4 we were addressing a separate bucketing behavior issue in the obj-c SDK, we are still looking into whether a fix for these XCode parallel code build issues will be feasible for the Objective-C SDK.
Our recommendation in general is to move to our Swift SDK at your next upgrade opportunity, which will be our primary SDK for new iOS feature development moving forward. https://docs.developers.optimizely.com/full-stack/docs/migrate-to-swift-sdk
For the time being as @mattiacantalu cited the Legacy Build System should another workaround option until a migration is possible

@Danny-Driscoll Thanks for the response. And @mattiacantalu Thanks for the workaround!
We've investigated the proposed options but we think we will wait for the real fix. Reasons are:

We cannot use the Legacy Build System due to some business reasons.
We cannot migrate to your Swift SDK just yet as there are lots of regression testings needed for the migration, which we are not comfortable in doing so yet.

@AshleyDeng We just released a patch (3.1.5) with a fix for this Xcode-12 build issue. Please give it a try and let us know if it works for you. Tx!


(BKR-426) long-term fix to end '/' issue in fetch_http_file

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/1242/
Test FAILed.


[WIP] docs(guide): document internationalization (i18n)

Hello !
Here is the dev guide for internationalization (i18n).
This is my first guide, which means that there are probably a lot of things to improve ! And since I'm french, there might be typos and weird sentences, don't hesitate to tell me what should be changed :-)
edit: @Foxandxss told me that I should add an application with a story, I'll be working on that

Would be nice to add a short text about placeholders:

this is bold

this is an {{ exp }}

@ocombe First, thanks for this doc.
It could be interesting that you speak about the i18n-placeholder directive (and some others that I could not know).
For information, I've implemented i18n in this app with the help of your doc (ng2-rc.7, angular-cli webpack.9-4): https://github.com/actimeo/simmage-ui
It is not very clear how to choose the language at bootstrap time. I've made a first try with some quick hack to get the language from local storage.

@feloy there will be a complete example added that should help you to know about to select the language at setup
Also what is the "i18n-placeholder" ? it's nowhere in the source of angular

I've found the code here:
https://github.com/angular/angular/blob/master/modules/%40angular/compiler/src/i18n/extractor_merger.ts#L314
In fact it is possible to mark any translatable attribute, e.g. i18n-placeholder to mark to translate the placeholder one.

Interesting, thanks, I'm not sure if it is intended though, this might be something that could change later and you shouldn't rely on it
What do you think @vicb ?

Continuing in #2340

wahou what happens, too many francais here ;)

Yep i18n-<attrName> is working and here to stay.


Include the Pods/ directory

This makes it easier to get started as you won't have to download CocoaPods and download the dependencies :)

Thank you very much for the contribution ! 😃


Alt Drag Window

Description of the new feature / enhancement
Enabling the ability to drag a window within an open application using keyboard keys and the mouse, aside from the header, would be beneficial. Currently, it can be difficult and sometimes frustrating to reposition apps when they are temporarily placed at the edge of the screen. For instance, in the Edge browser, the window header is crowded with buttons, making it challenging to move. Also, it would be great to have this updated version of Alt Drag. Some existing software was even flagged by my pc as unsafe. I'm begging. :)
Scenario when this would be used?
An easy way to move any open windows.
Supporting information
No response

Oh, the same suggestion has been submitted. About 5 Years ago. :(

/dup #269


[Autocomplete] - Passing props to ListboxComponent

Not sure if this is a bug or not.
I am trying to fetch more options when ListboxComponent scroll is at the bottom. Having issues with the custom ListboxComponent.
When I pass props I get a fowardRef warning and the list items won't render correctly even tho fowardRef was used.
      ListboxComponent={listboxProps => (
        <ListboxComponent
          {...listboxProps}
          setIsScrollBottom={setIsScrollBottom}
        />
      )}

const ListboxComponent = forwardRef(function ListboxComponent({ setIsScrollBottom, ...rest }, ref) {
  return (
    <ul
      ref={ref}
      {...rest}
      onScroll={({ target }) =>
        setIsScrollBottom(target.scrollHeight - target.scrollTop === target.clientHeight)
      }
    />
  );
});

Demo
https://codesandbox.io/s/jolly-matsumoto-ugs5d

We have a related issue in #18450, I would love to learn more about your load more use case.

The ref warning in your codesandbox is expected, it creates a new component at each render without forwarding the ref. You could use the context to be able to listen to your scroll bottom event.

In my case, I am not using the internal filterOptions function.
We are using AWS cloud search. I query the API on throttled keystroke.
A user can search their company’s address book.
When a user searches for “BBQ” AWS may return the first 10 of 45 results.
If the user doesn’t see their match they can either refine the search “BBQ Austin” and return new results or scroll to the bottom of the ListboxComponent and load the next 10 results appending them to the options.

What prevents you from getting, say, 100 results, instead of 10?
In which case, the pagination is likely no longer useful. I don't think that somebody will scan more than 100 items, the user will likely refine his query after this order of magnitude.
Do you display some sort of indicator at the bottom of the option list to let the user know more options are available/loading?
What do you think of a new ListboxProps prop?
If we had a non-MIT API adapter in the enterprise version of Material-UI for AWS cloud search, would that something you would be potentially interested in?

What prevents you from getting, say, 100 results, instead of 10?

Nothing, but the infinite scroll does look cool

In which case, the pagination is likely no longer useful. I don't think that somebody will scan more than 100 items, the user will likely refine his query after this order of magnitude.

I agree.

Do you display some sort of indicator at the bottom of the option list to let the user know more options are available/loading?

Not at the moment but I am playing around this idea. API results come back in fast enough that not sure it matters for my case but it could for others.

What do you think of a new ListboxProps prop?

I think that would be great. I think it would be the best solution.

If we had a non-MIT API adapter in the enterprise version of Material-UI for AWS cloud search, would that something you would be potentially interested in?

Probably not, not familiar. Didn't know there was an enterprise version

I think that would be great. I think it would be the best solution.

We have added this xProps prop a couple of times in the past to solve this very problem. I think that it would make a good addition.

Hi oliviertassinari,
I had same problem, I have 3000 options, So I dont like load all options. When user scroll to bottom, I will load more options.
I think we should have new ListboxProps like onScrollToBottom.
Thank you.

What do you think about this diff?
I still have to adjust the scroll position after options are changed. In this codesandbox the list jumps to the first option when more items are added.
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
index 5b4ef231c..cec1a01f5 100644
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -88,11 +88,13 @@ export default function useAutocomplete(props) {
     id: idProp,
     includeInputInList = false,
     inputValue: inputValueProp,
+    ListboxProps = {},
     multiple = false,
     onChange,
     onClose,
     onOpen,
     onInputChange,
+    onScrollToBottom,
     open: openProp,
     options = [],
     value: valueProp,
@@ -688,6 +690,12 @@ export default function useAutocomplete(props) {
     setHighlightedIndex(highlightedIndexRef.current);
   });

+  const handleListboxScroll = ({ target }) => {
+    if (target.scrollHeight - target.scrollTop === target.clientHeight && onScrollToBottom) {
+      onScrollToBottom();
+    }
+  }
+
   const handlePopupIndicator = event => {
     inputRef.current.focus();

@@ -800,6 +808,8 @@ export default function useAutocomplete(props) {
         // Prevent blur
         event.preventDefault();
       },
+      onScroll: handleListboxScroll,
+      ...ListboxProps
     }),
     getOptionProps: ({ index, option }) => {
       const selected = (multiple ? value : [value]).some(

In this codesandbox the list jumps to the first option when more items are added.

@m4theushw This codesandbox is not valid, it remounts the Listbox component at each update, I don't think that we can make any decision based on it.

What do you think about this diff?

I don't think that a strict equality check is enough. There is a 8 pixels bottom padding. I would include it to work with keyboard navigation.
Regarding the onScrollToBottom prop, I'm in favor of discouraging the "load more option as we scroll" pattern, so to not support this prop.

@oliviertassinari I agree with you, this is a particular case. Also, adding more items would increase the number of DOM elements and decrease performance. An ideal implementation should not create new elements but reuse the ones not visible.
I think that in favor of infinite scroll the developer should add a way to let the user know that more results are available but they can only be visualised in another page. Like what GitHub does.

Would you like me to make a PR for ListboxProps?
Need to update useAutocomplete, docs and add a test?

This would be great :)

Should I add support for PaperProps and PopperProps while were at it? Just to keep things consistent.

Please don't, the fewer we have, the better.

Oh boy https://github.com/mui-org/material-ui/issues/18885 🙃

this lib is driving me crazy!

@ChrisWiles have you find a way to prevent the "jump to start" scrolling glitch?

@ChrisWiles have you find a way to prevent the "jump to start" scrolling glitch?

Never heard of that, this is how I set it up
const [isScrollBottom, setIsScrollBottom] = useState(false);
const nearBottom = (target = {}) => {
  const diff = Math.round(target.scrollHeight - target.scrollTop);
  return diff - 25 <= target.clientHeight;
};
  // Autocomplete
      ListboxProps={{
        onScroll: ({ target }) => setIsScrollBottom(nearBottom(target)),
      }}

@ChrisWiles have you find a way to prevent the "jump to start" scrolling glitch?
Hi, maybe:

ListboxProps={{    onScroll: (event: React.SyntheticEvent) => {       event.stopPropagation();       const listboxNode = event.currentTarget;       const savedScrollTop = listboxNode.scrollTop;       const diff = Math.round(          listboxNode.scrollHeight - savedScrollTop,       );       if (diff - 25 <= listboxNode.clientHeight) {          **const returnScrollTop = () => {             setTimeout(() => {                listboxNode.scrollTop = savedScrollTop;             }, 0);          };**          getData(returnScrollTop);       }    }, }}

After X long hours spent on trying do 'hacks' with scroll/fix warning type listBoxComponent props i couldn't find any working way do handle that... the way which i've chosen is use hook useAutocomplete and provide custom list box build based on material-ui components like <Typography component='li' />   (i wanted have the same style/look like material-ui autocomplete)
there is good example (easy to convert to TypeScript) https://codesandbox.io/s/material-demo-0fbyb?file=/demo.js
in my case i only imported getRootProps( for parent div), getInputProps( for inputProps TextField) and everything works

@oliviertassinari
@WasiakSzymon
@WasiakSzymon
hi,
it is strange but i pass a simple ref to the ListBoxProps as a second argument to the Autocomplete and this bug fix but it raise an error in type script project.
can anyone help me to fix this issue???
this is the error :
Type '{ onScroll: (e: UIEvent<HTMLUListElement, UIEvent>) => void; ref: MutableRefObject; }' is not assignable to type 'HTMLAttributes'.
Object literal may only specify known properties, and 'ref' does not exist in type 'HTMLAttributes'.ts(2322)
Autocomplete.d.ts(163, 3): The expected type comes from property 'ListboxProps' which is declared here on type 'IntrinsicAttributes & AutocompleteProps<any, false, false, false, "div">'

This thread helped me figure out what I wanted to do all these years later. :)


Create Variables For Specific/Selected Themes

Is your feature request related to a problem? Please describe.
Ability to create variables of specific themes only.
Used-case:
Users do not want to create all the themes they have set up in all the files they are working in.
Extra information:
Slack Threads

@LukeFinch suggesting to close as this is covered in the PR 1974 https://github.com/tokens-studio/figma-plugin/pull/2522


Add AgentAttribute

Doing this in a PR because I'm not sure if you'd want it
Added Agent attributes to identify agent classes for easier parsing programmatically

This is fine, the goal is to simplify using game classes, after all.


How to modify the eMBFuncReadHoldingRegister function (IDFGH-11595)

Because of business need, I need to modify the eMBFuncReadHoldingRegister this function is implemented, in this function you need to call I write other components of the library, but how to compile all not modified by, and be submitted to the following error:
[1/3] espressif/esp-modbus (1.0.12)
[2/3] espressif/mdns (1.2.2)
[3/3] idf (5.0.0)
CMake Error at E:/ESP-IDF/Espressif/frameworks/esp-idf-v5.0/tools/cmake/build.cmake:519 (message):
ERROR: Some components (espressif/esp-modbus) in the "managed_components"
directory were modified on the disk since the last run of the CMake.
Content of this directory is managed automatically.
If you want to keep the changes, you can move the directory with the
component to the "components"directory of your project.
I.E.  for "espressif__esp-modbus" run:
mv
C:\Users\Administrator\Desktop\modbusTCP\WifiLogger\managed_components\espressif__esp-modbus
C:\Users\Administrator\Desktop\modbusTCP\WifiLogger\components\espressif__esp-modbus
Or, if you want to discard the changes remove the ".component_hash" file
from the component's directory.
I.E.  for "espressif__esp-modbus" run:
rm
C:\Users\Administrator\Desktop\modbusTCP\WifiLogger\managed_components\espressif__esp-modbus.component_hash
Call Stack (most recent call first):
E:/ESP-IDF/Espressif/frameworks/esp-idf-v5.0/tools/cmake/project.cmake:440 (idf_build_process)
CMakeLists.txt:11 (project)
-- Configuring incomplete, errors occurred!
See also "C:/Users/Administrator/Desktop/modbusTCP/WifiLogger/build/CMakeFiles/CMakeOutput.log".

@iamugly ,
if you need to override some functionality of the esp-modbus component, there are several ways to do this.

The simple way to change some functionality of the library is to move the C:\Users\Administrator\Desktop\modbusTCP\WifiLogger\managed_components\espressif__esp-modbus folder into C:\Users\Administrator\Desktop\modbusTCP\WifiLogger\components\espressif__esp-modbus. This is exactly what is stated in your message. In this case you can update the files components\espressif__esp-modbus folder to override the component downloaded by package manager.
Other way is to create new component\patched_esp_modbus and modify its CMakeFiles.txt to be able to override one file from patched component and other files from official component. See patched component example here.
Add your other component dependencies into requirements list of patched esp-modbus component if you need it.
If you need to override just some of symbols from the library to your implementation you can use the --wrap= linker approach for this.

#add this to your main component CMakeLists.txt file ....
set(WRAP_FUNCTIONS
    eMBFuncWriteHoldingRegister # This function will be overridden with your implementation below
    # add other functions from the esp-modbus to override in your code
)

foreach(wrap ${WRAP_FUNCTIONS})
    target_link_libraries(${COMPONENT_LIB} PUBLIC "-Wl,--undefined=${wrap}")
    target_link_libraries(${COMPONENT_LIB} PUBLIC "-Wl,--wrap=${wrap}")
    #target_link_libraries(${COMPONENT_LIB} INTERFACE "-u __wrap_${wrap}")
endforeach()

your_implementation_file.c:
eMBException __wrap_eMBFuncWriteHoldingRegister( UCHAR * pucFrame, USHORT * usLen )
{
    // Do what you need here, because this body will be executed instead of original function
}

your_implementation_file.h:
eMBException __wrap_eMBFuncWriteHoldingRegister( UCHAR * pucFrame, USHORT * usLen );
extern eMBException __real_eMBFuncWriteHoldingRegister( UCHAR * pucFrame, USHORT * usLen );

Note: do not forget to add the above files into sources and include list of your project CMakeLists.txt. See the documentation

Other ways also possible, but the simplest ones are above.

Thank you very much for your answer!

@iamugly ,
Thank you for update. I will close the issue as solved then. Feel free to reopen if you need more help.


How to prepare a BAM file

"It requires as input the BAM file of the sample to be genotyped.”
In this step: "SVDSS smooth --bam sample.bam --workdir $PWD --reference GRCh38.fa --threads 16",
My understanding is that HiFi reads (CCS data) were used to map to the reference genome and get this bam file.
If I have genomes and HiFi data (CCS data) for multiple species and need to make inter- and intra-species comparisons, do all HiFi data map to the same genome, or do they map to themselves?
Thanks a lot !

Hi,
To do smoothing, you need to map your input CCS reads to the reference genome and then run SVDSS smooth on the resulting BAM file.
What sort of comparison are you trying to perform? SVDSS is not directly meant for comparative analysis. You can however genotype each of your samples individually and then compare the variants.
If you have several samples of the same species, one option is to map all of your samples to the same reference genome and genotype them with SVSDSS against that reference and then compare the genotypes using other tools for analysis.
You may find our earlier method PingPong  useful for comparative analysis. SVDSS is based on PingPong.

In this step: "SVDSS smooth --bam sample.bam --workdir $PWD --reference GRCh38.fa --threads 16"
smoothed_reads.txt and ignored_reads.txt in workdir is empty
[I] Processed batch 1. Reads so far 20000. Reads per second: 20000. Time: 1
[I] Processed bases: 1, num mismatch: 0, mismatch rate: 0, ignored reads: 0
[I] Processed batch 2. Reads so far 30000. Reads per second: 3750. Time: 8
[I] Processed bases: 1, num mismatch: 0, mismatch rate: 0, ignored reads: 0

mmm that [I] Processed bases: 1, is quite strange.. That number should be the total number of bases processed if I'm not wrong (and it's initialized at 1).. It seems like all read have been filtered(smoothed_reads.txt should be non-empty).
Some reasons why this could happen:

there is no primary alignment (but I don't think this is the case)
the .bam is corrupted (as above)
every read is aligned to a chromosome not present in the input reference
https://github.com/Parsoa/SVDSS/blob/dc0333e6368a2c98944597e3b33bcf0be92c315a/smoother.cpp#L265-L268
alignments are too dirty (and then are skipped)

How did you map the reads? In case, would it be possible for you to share the .bam?
Best,


JIRA status reconciliation management command

based on #3947, so merge that one first.
Basically what I added to the docs, explains this PR:
Status reconciliation
Sometimes JIRA is down, or Defect Dojo is down, or there was bug in a webhook. In this case
JIRA can become out of sync with Defect Dojo. If this is the case for lots of issues, manual reconciliation
might not be feasible. For this scenario there is the management command 'jira_status_reconciliation'.
usage: manage.py jira_status_reconciliation [-h] [--mode MODE] [--product PRODUCT] [--engagement ENGAGEMENT] [--dryrun] [--version] [-v {0,1,2,3}]

Reconcile finding status with JIRA issue status, stdout will contain semicolon seperated CSV results. Risk Accepted findings are skipped.

optional arguments:
  -h, --help            show this help message and exit
  --mode MODE           - reconcile: (default)reconcile any differences in status between Defect Dojo and JIRA, will look at the latest status change
                        timestamp in both systems to determine which one is the correct status
                        - push_status_to_jira: update JIRA status for all JIRA issues
                        connected to a Defect Dojo finding (will not push summary/description, only status)
                        - import_status_from_jira: update Defect Dojo
                        finding status from JIRA
  --product PRODUCT     Only process findings in this product (name)
  --engagement ENGAGEMENT
                        Only process findings in this product (name)
  --dryrun              Only print actions to be performed, but make no modifications.
  -v {0,1,2,3}, --verbosity {0,1,2,3}
                        Verbosity level; 0=minimal output, 1=normal output, 2=verbose output, 3=very verbose output

This can be executed from the uwsgi docker container using:
$ docker-compose exec uwsgi /bin/bash -c 'python manage.py jira_status_reconciliation'

DEBUG output can be obtained via -v 3
$ docker-compose exec uwsgi /bin/bash -c 'python manage.py jira_status_reconciliation -v 3'

At the end of the command a semicolon separated CSV summary will be printed. This can be captured by redirecting stdout to a file:
$ docker-compose exec uwsgi /bin/bash -c 'python manage.py jira_status_reconciliation > jira_reconciliation.csv'

To achieve this, I had to make some changes inside Defect Dojo:

extract webhook code to update finding status, move this to jira helper
extract code to update the status in JIRA into its own method
improve verbose_name and help_text for open_status_key en close_status_key. this doesn't affect the SQL schema, so it's safe to modify the existing migrations.
use updated timestamp from JIRA when handling incoming webhook

Also includes some bugfixes:

#3965

Been dreaming of this one! Everything looks good to me except for the migrations.

Why the decision to edit older ones?
Is this to avoid a new migrations?
Do these changes take affect for existing installs? Does Django even notice a change?
Are these changes even needed for existing installs?

What do you mean by editing older ones? Do you mean why I am modifying existing findings and setting the last_status_update field there?
Or do you mean why I am editing existing migrations? I have noticed that existing migrations can be editing safely as long as they don't affect the SQL schema. So it helps to avoid having lots of small migrations only changing display texts. It really helps me if you have multiple PRs and have to keep all the migrations in sync/rebased/renamed.
What django does is that it builds a model in memory from applying all the migrations from 0001 to the end. And then it compares that to what is in models.py. So these needs to be in sync. And all this has to be in sync with the database. But django is only able to compare things with the database that are actually there, so new columns, renamed columns, changed columns, new indexes etc they need a new migration because they need to be applied to existing instances.
But things like verbose_name and help_text or even choices are not in the sql schema. So there is no migration needed, and also django won't be able to compare anything with the database so there is nothing that can be out of sync.
For those 'display' fields the only thing that matter is that the end result of all the migrations (in memory) is identical to what is in models.py.

This is super useful! Works like a charm too. Very glad to see that pulling changes from JIRA and reflecting them on dojo works without a webhoook. The only thing I noticed was the jira change column was not being updated consistently when viewing a finding. When findings are reconciled and changes in dojo were different than JIRA, the jira change value was not updated. The opposite occurred when changes in JIRA were different than in dojo as the jira change column was updated.
Besides that, this is a solid PR and ready for an approval from me.

This is super useful! Works like a charm too. Very glad to see that pulling changes from JIRA and reflecting them on dojo works without a webhoook. The only thing I noticed was the jira change column was not being updated consistently when viewing a finding. When findings are reconciled and changes in dojo were different than JIRA, the jira change value was not updated. The opposite occurred when changes in JIRA were different than in dojo as the jira change column was updated.
Great find! Fixed now.


ci: Add e2e tests for merge validations

Issue #, if available:
Description of changes:
Add e2e tests and workflow for merge validations. Tests can also be triggered by workflow_dispatch.
Testing done:
Yes on fork.
See https://github.com/vsiravar/finch-core-public/actions/runs/4571222330/jobs/8069314687 for results.

[X] I've reviewed the guidance in CONTRIBUTING.md

License Acceptance
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

In general, should we be testing Finch here, or just finch-core, which is just a set of lima + socket_vmnet + a specific OS image?
If its the latter, I think we can just build/install Lima from source on whatever commit submodule uses, without downloading a specific bundle. fedora.yaml might also need some scripting to add the correct OS image during make.

In general, should we be testing Finch here, or just finch-core, which is just a set of lima + socket_vmnet + a specific OS image?

In this repo, we'll test against the the pinned set of lima + socket_vmnet and specific OS since want to decouple finch-core from finch. It might also add circular dependency if we make finch-core depend on finch since finch-core is a submodule of finch.

If its the latter, I think we can just build/install Lima from source on whatever commit submodule uses, without downloading a specific bundle. fedora.yaml might also need some scripting to add the correct OS image during make.

Yeah, for this I am thinking of moving this workflow from the cli repo which will update the Makefile with the latest set up pinned dependencies in a separate PR. I will make changes in the PR to test against the OS and socket_vmnet version managed by this repo. WDYT?

Yeah, for this I am thinking of moving this workflow from the cli repo which will update the Makefile with the latest set up pinned dependencies in a separate PR rather than building each time from the source every time. I will make changes in the PR to test against the OS and socket_vmnet version managed by this repo. WDYT?

Moving the workflow makes sense in general, but I don't see why we can't just rebuild Lima/socket_vmnet/other-deps from source as part of this test. Saves a network round-trip. The upload job should run after the merge or independently imo.

Yeah, for this I am thinking of moving this workflow from the cli repo which will update the Makefile with the latest set up pinned dependencies in a separate PR rather than building each time from the source every time. I will make changes in the PR to test against the OS and socket_vmnet version managed by this repo. WDYT?

Moving the workflow makes sense in general, but I don't see why we can't just rebuild Lima/socket_vmnet/other-deps from source as part of this test. Saves a network round-trip. The upload job should run after the merge or independently imo.

Yeah we could build a new dependency set for every PR, it would add an additional 30 mins to the CI workflow based on historical data. Building dependencies for every PR might not be different from using the most recent set of dependencies available in the S3 dependency bucket. This is because we update the submodules and build and upload the dependencies (Lima, QEMU, and their dependencies) once a  week. I don't feel strongly about either solution :), I am okay to build dependencies for every run but just want to call the 30min overhead in building dependencies for every PR.

I agree with Vishwas's point that it is unnecessory to build new dependency for every PR, because the trigger point is the reverse way: Finch Core is depend on the lima & qemu build and OS image.
lima & qemu build is a black box that the deep dependency can update without lima update, so it needs its own scheduler to generate the latest build. Once a new build is done, the it needs to make Core ref to this new artifact and then run the CI to validate if regression happens because of dependency update. It is similar behavior with other dependency update such as OS image patch.
The generic update sequence is:

Dependency artifact got updated, i.e., lima & qemu, OS image patch, etc
PR to Core to update artifact ref
e2e test run during the merge validation
PR checked in and Finch repo has Finch-Core submodule updated.

Finch Core is depend on the lima & qemu build and OS image.

finch-core currently has no dependency on the lima and qemu dependency archive. We can move the generation of that archive to a workflow on this repo in this PR, but it currently is not in finch-core. @vsiravar, if you want to move the workflow to this repo like you suggested, I'm ok with that. If the concern is test run time, then I do think its fine to cache the lima-and-qemu artifacts in remote storage (S3), since the same archive may be reused multiple times.

The generation of the archive is already a github action in this repo, what I mean is that the Makefile in this PR need to ref to that new archive and then the CI will validate that archive has no regression.


How to insert a table like docxtemplater

https://docxtemplater.com/demo/#table

See the README https://github.com/guigrpa/docx-templates#for-and-end-for and the example templates https://github.com/guigrpa/docx-templates/blob/c4356261c0d9bc220db9f30f955c8aaaa4dac377/src/tests/fixtures/for-row1.docx
docx-templates has nothing to do with docxtemplater.com

if template is like this

it will result like this

Can you explain what is going wrong? Also, please post a reproducible example.

@jjhbw nothing is wrong, I added answer for the original question, so in case someone else came to this thread see it, (like me that I came and current answer was not clear to me)

Sorry I misread! I didn't notice I was commenting on a closed issue from the github app. Thanks for posting the solution!


Mac Vscode doesn't start anmyore

VSCode Version: 1.9.1 insider from today (not sure which commit hash)
OS Version: Mac OS Sierra

Just upgraded vscode to the latest insider build and now it crashes on startup before even showing a window. I know that this is really vague but I don't know how to capture stack traces or more debug infos for native apps (web dev here). When launching from the terminal, vscode immediately exits silently.
A reinstall of the insiders build didn't help.
Steps to Reproduce:

Open vscode-insiders
crash

Same here - installed latest update and now doesn't start.

Same here - it never restarted when I clicked update and won't start at all after.

Seems to be a duplicate of https://github.com/Microsoft/vscode/issues/20555 Deleting the files listed in the comments solved this issue for me and vscode starts without crashing.


Save checkpoints and use in next scan

The idea of checkpoints is to avoid scanning the same github content multiple times.  It's stubbed out, but not fully implemented since checkpoints are never actually saved.
What's currently in place:

The params to the github user events scanner is defaulted to a fake list of checkpoints for 12 hours ago, which basically means the scanner will stop as soon as it sees events that are older than 12 hours ago.  This limits the amount of content scanned and speeds up the overall processing.  Since this runs with a polling frequency of 15 mins by default, and there are no checkpoints being saved, the same github content will be scanned many times.

In gh_user_event_fetcher.go it skips any content that is older than the checkpoint

In the github user events scanner result, the new checkpoints are emitted, but they are never persisted or used after that.

Fixed in https://github.com/tleyden/keynuker/pull/20


Bump dmutils 13.5.0

This upgrade includes:

https://github.com/alphagov/digitalmarketplace-utils/pull/206
https://github.com/alphagov/digitalmarketplace-utils/pull/207
https://github.com/alphagov/digitalmarketplace-utils/pull/209
https://github.com/alphagov/digitalmarketplace-utils/pull/208

:+1:


Multiple Form Submit Actions

This allows us to submit forms different ways. For example, update and delete. And it allows FF to still manage the submit progress.
<Form>
  onSubmit={(data) => {
    data.submitAction === 'delete' ? doDelete() : doUpdate();
  }}
>
  {({ handleSubmit }) => (
    <form onSubmit={handleSubmit}>
      <SubmitButton />
      <SubmitButton action="delete">Delete</SubmitButton>
    </form>
  )}
</Form>

One caveat I just thought of is that the form still has to be valid. So you couldn't remove a required value and then submit a delete action. Maybe this edge case can be handled later.

One caveat I just thought of is that the form still has to be valid. So you couldn't remove a required value and then submit a delete action. Maybe this edge case can be handled later.

Definitely sounds like an edge case to me.
This is neat!


gpt-4o-mini as the default model for explanation?

Since gpt-4o-mini was released out now and it's way cheaper than gpt-3.5-turbo. It would be nice to set 4o-mini as the default model for explanation, or offer an additional option for choosing the default model.

good idea, PRs always valued! I would check first to make sure it doesn't have requirements like gpt-4 of having spent at least $20 or whatever openai has, if it doesn't i agree it would be great to get it as the new default


Evalute migration to mermaid js

from gaphor, for documentation diagrams.
C4 diagrams are supported experimentally by mermaid.However, it may be preferrable to drop the C4 specific style and go for simpler diagrams instead. Advantages:

Learned skills are trasferrable to other use cases calling for diagrams.
Obsidian has integrated support for mermaid. Documentation could be written and viewed in Obsidian. (+ hot reload, autoformat) (- how to deploy these docs? would be nice to have them on github pages for example.)
Easier setup / onboarding.
No more fiddling around in the gaphor GUI.
Seems to be under active development.

or D2!

d2 rocks!


(Budget metering) Add cost tiers to wasmi instructions

Based on results from https://github.com/stellar/rs-soroban-env/pull/597, we need to account for different costs of wasmi instructions in the host metering.

To break down different wasmi instructions to several tiers, and assign a unit cost to each tier.
Account for the unit cost in the buffered step meter.
Expose the wasmi cost tier parameters as new Budget::CostTypes.

Instruction level calibration has been done in https://github.com/stellar/rs-soroban-env/pull/597.
But to add different cost tiers in wasmi, we need to evaluate wasmi's out-of-box fuel metering first -- https://github.com/stellar/rs-soroban-env/issues/683

After switching to wasmi fuel metering (https://github.com/stellar/rs-soroban-env/issues/683), we will set these configurations to enable different instruction costs.


-1073741795

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary):
TensorFlow version:
Python version:
Installed using virtualenv? pip? conda?:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:

ImportError: Traceback (most recent call last):
File "C:\Users\Junaid\Anaconda3\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\Junaid\Anaconda3\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 28, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\Junaid\Anaconda3\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 24, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\Junaid\Anaconda3\lib\imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\Junaid\Anaconda3\lib\imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: DLL load failed with error code -1073741795
Failed to load the native TensorFlow runtime.

first I run the command line pip install tensorflow==2.2.0
then while importing the tensorflow it throws the above error

@Junaidkhan1809
Please verify your system meets the requirements mentioned above mentioned for you to use tensorflow.

@Junaidkhan1809
Please verify your system meets the requirements mentioned above mentioned for you to use tensorflow.

My machine has windows 7 64bit i3

What specification are required to run tensorflow @Saduf2019

@Junaidkhan1809
Please click on the links given by bot above and verify [ex python 64 bit, AVX support, os 64 bit etc].

My machine is not compatible !
one last query What type of machine is required in terms of specification @Saduf2019

Thank You !


Fix small style issue

Fixes a small style issue introduced in https://github.com/inventree/InvenTree/pull/7752

Thank you, I completely overlooked that


Extra parenthesis are not removed when used with lib.optionals

The following snippet
  [ ]
  ++ (lib.optionals (cyrus_sasl != null) [ "--enable-cyrus-sasl=yes" ])
  ++ (lib.optionals (gnutls != null) ["--enable-gnutls=yes" "--enable-nss=no"])
  ++ (lib.optionals stdenv.isDarwin ["--disable-gtkspell" "--disable-vv"]);

should be converted to
  [ ]
  ++ lib.optionals (cyrus_sasl != null) [ "--enable-cyrus-sasl=yes" ]
  ++ lib.optionals (gnutls != null) ["--enable-gnutls=yes" "--enable-nss=no"]
  ++ lib.optionals stdenv.isDarwin ["--disable-gtkspell" "--disable-vv"];

Thanks for the report! Currently statix does not remove useless parentheses in binary expressions, like x ++ (y), I am waiting for some parsing changes around operator precedence to land before implementing this.


hi, i am using recast and node.js to build a chatbot, i want to know how can a bot autometically sends message like "how can i help you" when the user first opens the bot?

I am using facebook messenger


Video tutorials of each docs guide

@ravenac95 I would love to see some 2 minute Loom videos for Dagster jobs. The following are probably most relevant but I'm sure there are more:

[ ] Syncing OSS Directory
[ ] Triggering a full run
[ ] Triggering a run for a specific source
[ ] Triggering a backfill
[ ] Re-materializing a metric model and everything downstream

Syncing OSS Directory: https://www.loom.com/share/9342f91620e1416e83a9823a605d5bf4
Trigging a full run (and also specific dbt environments including backfill): https://www.loom.com/share/55534d1aa6cd4187a2d52ec98709edf1
Triggering a run for a specific source: https://www.loom.com/share/5a2818d05bed4fc8a4a153b72b07ee8d
Rematerializing a metric model: https://www.loom.com/share/0b673d1c8e9a494ab30d84bbb9d9134a

Thanks @ravenac95 - these are great. I added all of them a Tutorials Space on Loom. You should be able to access it here: https://www.loom.com/spaces/All-Kariba-Labs-24123308/folders/Tutorials-7be451e369fb4fe788137545eb8d2469


Dimmer with events

@NothernMan54 Can you change the hard-codes value sent for brightness to use the min/max range from options from deviceConfig? My devices freak out if that value is set lower than 11.

@GioCirque I was looking at my commit, and it is included.  Are you thinking of something else?
https://github.com/codetheweb/homebridge-tuya/pull/18/files#diff-75f6c91a049938dfc57cb00d7181b04aR29

@NorthernMan54 Look at line #54. I changed it, when I included your changes, to be the reverse of the calculation in the set handler.
https://github.com/codetheweb/homebridge-tuya/pull/20/files#diff-75f6c91a049938dfc57cb00d7181b04a

Closing


Current working dir is user/tmp instead of original

Bug Report
I started using this tool today. I discovered it because of the dependant crate cprint which i've created! So I was kinda happy to see it was useful and i checked out this project and it is actually useful for me.
So I create a file in the current working dir but it creates it in tmp dir.
I mean it is not a big issue, it doesn't work only when i use wargo run not when I start the built executable
Current Behavior

The CWD is the tmp dir instead of the project dir
Expected behavior/code

The CWD should be the project dir
Additional context/screenshots

Unless I miss something in the report the destination dir (defaulting to ~/tmp in your WSL environment) usage is intentional, as you can see:
https://github.com/asaaki/wargo/blob/796cc3674e4413e0aae4e0d51e3451c25ceda750/src/lib.rs#L319
https://github.com/asaaki/wargo/blob/796cc3674e4413e0aae4e0d51e3451c25ceda750/src/lib.rs#L339
The reason is that it's currently easier to not only move and compile in the tmp dir, but also for the run command to just execute from there.
You basically execute all cargo command from the tmp copy location, not your original one.
If you really want to execute from your original location, for now you still need to separate compile and run steps.
I can consider a refactoring to use/define a different CWD for the execution of binaries, but this might be tricky, since we cannot pass a different working directory directly to the cargo run command (there is no option for that), and we must set the current directory for calling cargo run to the tmp copy.
I can try tinkering with --manifest-path <some path>/Cargo.toml option, to see if that fixes it.


The app seems too slow to load please make the loading performance better

I would mean a lot make it as fast at native explorer

@fisforfaheem Can you please fill out the issue template?

Thanks again for your feedback.
We remain committed to improving the performance of Files, but since we didn't hear from you on this topic for 3+ days, we'll assume everything is worked out and close this feedback item. If you had more feedback to provide, please re-open this and help the owners by describing the current status and any steps taken to troubleshoot this.

ok, i have seen some speed improvements
On Sun, Nov 29, 2020 at 10:27 PM Luke Blevins<EMAIL_ADDRESS>wrote:

Closed #2434 https://github.com/files-community/Files/issues/2434.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/2434#event-4049237131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIRXJSACN25WLKM6FJ2ERPLSSJ76JANCNFSM4UCDVFTQ
.

We're excited to share that startup performance will be significantly improved in the upcoming release of version 3. You can download the preview version from our website https://files.community/download.


chore: growth trial flow

fixes MON-122

📝 Changed routes:

…board/settings/billing
/pricing

(view full size)
(view full size)

Commit 8d41434c307f70d9cb5793850c8e19eafcb85f30 (https://thirdweb-ml0gd4e4k.thirdweb-preview.com).


Feature: Automatically switch to PiP

It would be nice, if Zapp would automatically switch to PiP mode, if one minimizes the app or switch to another app, via app switcher.
Also, it would be nice, if PiP is active, that turning off the screen would result in automatic background playback.
So going to the 3-dots menu in the top right corner during playback could be skipped.
YouTube Vanced works/ worked that way and I find that really convenient 🙂

I find this feature very stressfull and would not like to enable it by default.
But i'll try to find out if this is something more users might like.

I have no problem with a switch in the settings, that allows to en- or disable such a feature ;-)

that would be two great options

Note to self:
This would require a new preferences section along the line of "video player". This may contain the existing "Videos always in landscape mode" setting and the new "Resume playback in picture in picture mode" setting.

How other apps do it
Youtube

back press: mini player
app switch: stop playback

New Pipe

back press: mini player
app switch: switch to audio playback

Netflix

back press: stop playback
app switch: stop playback

VLC

back press: stop playback
app switch: can be changed:

stop
audio playback
picture in picture

Switching to picture in picture on back press is very easy by placing this in AbstractPlayerActivity::onCreate:
onBackPressedDispatcher.addCallback(object : OnBackPressedCallback(true) {
	override fun handleOnBackPressed() {
		MultiWindowHelper.enterPictureInPictureMode(this@AbstractPlayerActivity)
	}
})

However, there are some subtle bugs when switching videos while in picture in picture mode. And there is #168

Switching to picture in picture on back press is very easy by placing this in AbstractPlayerActivity::onCreate:
onBackPressedDispatcher.addCallback(object : OnBackPressedCallback(true) {
	override fun handleOnBackPressed() {
		MultiWindowHelper.enterPictureInPictureMode(this@AbstractPlayerActivity)
	}
})

However, there are some subtle bugs when switching videos while in picture in picture mode. And there is #168

The related bugs first to fix are: #341 #340

This issue is now implemented with upcoming version 8.1.0. Pip will start (after enabling it in preferences) after a back press from the video player. Turning the screen off during playback will switch to background playback.


Can I have two forward addresses?

Hello, I'm wondering if you can add two forward addresses. I've found two servers that only support donations and don't save requests or collect any data. I think it works because I haven't had any errors in Unbound so far, but I wanted to ask again.
I imagined it like this:
forward-zone:
name: "."
forward-tls-upstream: yes
forward-first: no
forward-no-cache: no
forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>forward-addr<EMAIL_ADDRESS>

Yes, it is possible to list a number of addresses for forward-addr, also stub-addr, forward-host and stub-host. They are attempted with randomisation, and fallback to the other servers if there is trouble.


remove obsolete py2.7 print_function

I've removed all the obsolete import of print_function lines.

what is dict_search.py?

what is dict_search.py?

My bad.  Accidentally added it.

please squash or fix up the commits to remove the noise of the erroneous commit.

For all the examples, need to check that the code imports in the Documentation.rst for all of them are still valid (the :lines: 19- line may need to be modified for some).

Oh yeah.  I'll fix them.

All the Sphinx doc pages look ok.  It seems that the documentation in Examples/Python is not being built.  Is that intentional?


Show Element Id when set to true breaks the code due to FreeTypeFont has no getsize attribute

Describe the bug
I was trying to use show_element_id as True in draw_box but suddenly got an AttributeError: 'FreeTypeFont' object has no attribute 'getsize'
Checklist

I have searched related issues but cannot get the expected help.
The bug has not been fixed in the latest version, see the Layout Parser Releases

To Reproduce
Steps to reproduce the behavior:

What command or script did you run?

lp.draw_box(pdf_images[4], text_blocks, box_width=3, show_element_id=True)  # Use the default font provided by the library

Environment

Used on windows with jupyter lab on conda
Using layoutparser version 0.3.4
All other libraries has been installed

Error traceback
AttributeError                            Traceback (most recent call last)
Cell In[17], line 1
----> 1 lp.draw_box(pdf_images[4], text_blocks,
2             box_width=3, show_element_id=True)  # Use the default font provided by the library
File ~\miniconda3\Lib\site-packages\layoutparser\visualization.py:194, in image_loader..wrap(canvas, layout, *args, **kwargs)
192 elif isinstance(canvas, np.ndarray):
193     canvas = Image.fromarray(canvas)
--> 194 out = func(canvas, layout, *args, **kwargs)
195 return out
File ~\miniconda3\Lib\site-packages\layoutparser\visualization.py:392, in draw_box(canvas, layout, box_width, box_alpha, box_color, color_map, show_element_id, show_element_type, id_font_size, id_font_path, id_text_color, id_text_background_color, id_text_background_alpha)
389     text = str(ele.type) if not text else text + ": " + str(ele.type)
391 start_x, start_y = ele.coordinates[:2]
--> 392 text_w, text_h = font_obj.getsize(text)
394 text_box_object = Rectangle(
395     start_x, start_y, start_x + text_w, start_y + text_h
396 )
397 # Add a small background for the text
AttributeError: 'FreeTypeFont' object has no attribute 'getsize'
Screenshots

You can fix this issue by running pip install Pillow==9.5.0.
This happens because FreeTypeFont.getsize() has been deprecated in Version 10.0.0 of Pillow.

Had the same issue and this solution worked for me. Thank you!

You can fix this issue by running pip install Pillow==9.5.0.
This happens because FreeTypeFont.getsize() has been deprecated in Version 10.0.0 of Pillow.


Add alt attributes to image elements.

To pass some accessibility testing we needed to add the alt attribute to images, including the map controls.
This change helps users using screen readers to navigate the page. It does not change performance or functionality for other users.

Thanks for the fix.


[ENG-183, ENG-187] feat: Implement read action for salesforce

This PR implements basic read functionality for the Salesforce connector. It also has a fairly major refactor of the error handling, as well as a bigger emphasis on type safety (via generics).
Major features:

Paging awareness (caller controlled)
Ability to query deleted objects (recycle bin, in Salesforce terms)
Ability to specify a "since" date to only fetch new records
Backfill capability (by simply not specifying a "since" date)
Retry logic
OAuth token refresh logic (addresses ENG-187)
Instead of unmarshalling to a concrete type immediately, JSON data is umarshalled to an abstract representation (easier to query) before finally becoming native go objects.

Test program output
GOROOT=/opt/homebrew/Cellar/go/1.21.0/libexec #gosetup
GOPATH=/Users/chris/go #gosetup
/opt/homebrew/Cellar/go/1.21.0/libexec/bin/go build -o /Users/chris/Library/Caches/JetBrains/GoLand2023.2/tmp/GoLand/___go_build_salesforce_go /Users/chris/connectors/test/salesforce.go #gosetup
/Users/chris/Library/Caches/JetBrains/GoLand2023.2/tmp/GoLand/___go_build_salesforce_go
{
  "rows": 14,
  "data": [
    {
      "BillingCity": null,
      "Id": "001Dp000003pfgjIAA",
      "IsDeleted": false,
      "Name": "Test Account",
      "SystemModstamp": "2023-06-30T18:28:25.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp000003pfgjIAA"
      }
    },
    {
      "BillingCity": "Mountain View",
      "Id": "001Dp0000048VHxIAM",
      "IsDeleted": false,
      "Name": "GenePoint",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHxIAM"
      }
    },
    {
      "BillingCity": null,
      "Id": "001Dp0000048VHvIAM",
      "IsDeleted": false,
      "Name": "United Oil \u0026 Gas, UK",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHvIAM"
      }
    },
    {
      "BillingCity": "Singapore",
      "Id": "001Dp0000048VHwIAM",
      "IsDeleted": false,
      "Name": "United Oil \u0026 Gas, Singapore",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHwIAM"
      }
    },
    {
      "BillingCity": "Austin",
      "Id": "001Dp0000048VHnIAM",
      "IsDeleted": false,
      "Name": "Edge Communications",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHnIAM"
      }
    },
    {
      "BillingCity": "Burlington",
      "Id": "001Dp0000048VHoIAM",
      "IsDeleted": false,
      "Name": "Burlington Textiles Corp of America",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHoIAM"
      }
    },
    {
      "BillingCity": "Paris",
      "Id": "001Dp0000048VHpIAM",
      "IsDeleted": false,
      "Name": "Pyramid Construction Inc.",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHpIAM"
      }
    },
    {
      "BillingCity": "Lawrence",
      "Id": "001Dp0000048VHqIAM",
      "IsDeleted": false,
      "Name": "Dickenson plc",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHqIAM"
      }
    },
    {
      "BillingCity": "Chicago",
      "Id": "001Dp0000048VHrIAM",
      "IsDeleted": false,
      "Name": "Grand Hotels \u0026 Resorts Ltd",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHrIAM"
      }
    },
    {
      "BillingCity": "Portland",
      "Id": "001Dp0000048VHtIAM",
      "IsDeleted": false,
      "Name": "Express Logistics and Transport",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHtIAM"
      }
    },
    {
      "BillingCity": "Tucson",
      "Id": "001Dp0000048VHuIAM",
      "IsDeleted": false,
      "Name": "University of Arizona",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHuIAM"
      }
    },
    {
      "BillingCity": "New York",
      "Id": "001Dp0000048VHsIAM",
      "IsDeleted": false,
      "Name": "United Oil \u0026 Gas Corp.",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHsIAM"
      }
    },
    {
      "BillingCity": "San Francisco",
      "Id": "001Dp0000048VHyIAM",
      "IsDeleted": false,
      "Name": "sForce",
      "SystemModstamp": "2023-03-28T21:04:23.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp0000048VHyIAM"
      }
    },
    {
      "BillingCity": null,
      "Id": "001Dp000003nigfIAA",
      "IsDeleted": false,
      "Name": "Sample Account for Entitlements",
      "SystemModstamp": "2023-03-28T21:07:42.000+0000",
      "attributes": {
        "type": "Account",
        "url": "/services/data/v58.0/sobjects/Account/001Dp000003nigfIAA"
      }
    }
  ],
  "done": true
}

Process finished with the exit code 0

This is looking really great! I think this is structured really well for us to be able to build more connectors easily. Can you please update the code snippet README.md with the new interface?

Yeah can do

Also I was originally envisioning that Temporal would handle our retry logic, since it's our orchestration layer. And the jdvr/go-again library you're using here doesn't have an OSS license. Here's more info on Temporal retry policies, seems pretty flexible: https://docs.temporal.io/retry-policies. What do you think?

Oh yeah that's a good point. We shouldn't do retrys at the library level then. I removed the problematic library, thanks for pointing out the license issue.


Build instructions update and improve CI

Just as a note: go doesn’t support Windows on ARM :(

Thank you!
I don't think it's necessary to implement a release etc. now, but it's helpful to be able to check if the build passes.
The implementation in Go is still WIP, so I'll consider releasing it when compatibility is almost achieved.

I didn’t implement a release, and yeah continuous deployment could be a real pain sometimes😖
Thank you for merging!


feat(tutorial): complete step 1

Closes #
{{Completed step1 of carbon-tutorial}}
Changelog
New

{{new thing}}

Changed

{{change thing}}

Removed

{{removed thing}}

@sandrarapp Looks good 🥇! I've recorded your completion of step 1.
And thanks for your help with hands-on facilitation! 🎉
P.S. We discussed in person why commit should include .yarn-offline-mirror.


Question regarding data structures

Hi Markus,
Would it be possible to get the sample .nwb file or some explanation about the data structure expected by DeepInsight (for the channels, timestamps, position, etc)? I have data from a different recording system (Neuralynx) and would be very interested in trying to use it.
Thanks and happy holidays,
Elhanan

Similarly, is it feasible to use numpy epoched arrays ([channels, times])?

For now there are two functions which need to be adjusted for using it with a custom dataset (code taken from Readme):
# Load your electrophysiological or calcium-imaging data
(raw_data,
 raw_timestamps,
 output,
 output_timestamps,
 info) = deepinsight.util.tetrode.read_tetrode_data(fp_raw_file)

Replace the function read_tetrode_data with your function, e.g. read_neuralynx_data. Note that this function should return the raw_data (shape: N x M. N: number of timepoints, M : channels), the raw_timestamps indicating the timestamp for each point (shape: N) plus the desired output and the corresponding timestamps.
# Prepare outputs
deepinsight.util.tetrode.preprocess_output(fp_deepinsight, raw_timestamps, output, output_timestamps,
                                           sampling_rate=info['sampling_rate'])

Given the output from above, this function calculates alignment to the raw_data and writes the given outputs to a HDF5 file. Adjust this based on the behaviour/stimuli you want to decode to.
I will also upload a jupyter notebook soon to provide a clear example of the full workflow given a new dataset.

Hi Markus, thanks for the help. I got it running on Google Colab for some testing, however the model loss/shuffled loss calculation phase either takes a very long time or something is broken. It just continues looping over the different models indefinitely, always returning "Performed 1079 gradient steps".
Is it supposed to take this long, or is something wrong?
Thanks

Hi elhananby,
I am trying to do something similar (run deepinsight from google colab over neuralnyx files), is there a chance you could share how you did it?
I am using neo to load the Neuralynx files and just pip installed deepInsight in google colab. Now trying to run an example...
Thanks!

Hi Markus,
Would it be possible to get the sample .nwb file or some explanation about the data structure expected by DeepInsight (for the channels, timestamps, position, etc)? I have data from a different recording system (Neuralynx) and would be very interested in trying to use it.
Thanks and happy holidays,
Elhanan


Fix attribute parser in Chapter 15

I assume this is here for testing? Or left over? Perhaps we should just delete it...

I referred to it in my chapter text, saying it was a lot like the CSS parser but left it out because it was redundant. I added it because alt text is unreasonably restrictive otherwise, as it can't contain a space character.


Fix a NULL deref in tcp_client_windows.cc

grpc_sockaddr_to_uri(addr) can return nullptr, and we are directly
passing it to grpc_slice_from_copied_string. Clusterfuzz found this
issue in https://clusterfuzz.com/testcase-detail/5188592759603200
Use "NULL" when target URI is nullptr, to avoid null deref.
Fixes #18544

Thank you @jtattermusch !

known failure: #15352 #5481


Cannot install with package.el on Emacs 24.4

package-compute-transaction: Package erc-5.3' is unavailable` it seems to have gone from MELPA/Marmalade/GNU package repositories.

I'm not sure but perhaps this happens because "erc.el" does not contain Version: field in its header.
Anyway I believe it would be better to exclude (erc "5.3") from "Package-Requires:" line, since erc has been a part of Emacs for a long time.
It will fix this issue.

I just created a pull request to fix this issue since I just stumbled upon it as well. Let's hope it gets merged soon.

see milkypostman/melpa#2824

This is actually closed by https://github.com/sshirokov/ZNC.el/pull/19


ReSharper 2016.2 support

Any ETA for support for this version?

It's already there! Go to Extension Manager and search for it.

Ahh, it wasn't showing for me on RS2016.1, After upgrading to 2016.2 and restarting VS, I now see it.
However, according to this page the last release was in 2014: https://resharper-plugins.jetbrains.com/packages/CleanCode/
Ahh, I see, you changed the package name. Why?

The name change is a requirement of the installer since ReSharper 9, I think it was. It needs to be at least a two part name. Annoying, but there you are.


Adds 2 new properties to DisplayObject: scaleMin and scaleMax.

These are Point objects that allow you to set a lower and upper bounds on the scale value the display object can transform to. The updateTransform method now checks these two properties (if set) and enforces them.
A small helper method setScaleMinMax has been added to allow the devs to quickly set these two properties, but if you feel it's not needed then you can remove it and it'll carry on working happily with it out.
I have found these 2 properties utterly invaluable in some responsive bbc games we've been building. For example we had a case where the whole game scaled responsively, but the top-level UI was never allowed to go below a certain size (or it becamse impossible to touch). Setting just the scaleMin allowed this, but it could still scale up happily on larger displays.

Where did we land on this @GoodBoyDigital, do we want this in core or userland?

userland! :+1: cheers all!