how to build com.google.mediapipe:tasks-genai for android..need steps please

OS Platform and Distribution
Android
Compiler version
No response
Programming Language and version
Java
Installed using virtualenv? pip? Conda?(if python)
No response
MediaPipe version
No response
Bazel version
No response
XCode and Tulsi versions (if iOS)
No response
Android SDK and NDK versions (if android)
No response
Android AAR (if android)
None
OpenCV version (if running on desktop)
No response
Describe the problem
need steps to build com.google.mediapipe:tasks-genai for android
Complete Logs
need steps to build com.google.mediapipe:tasks-genai for android

when i am running this command bazel build -c opt --config=android_arm64 //mediapipe/tasks/java/com/google/mediapipe/tasks/genai:tasks_genai.aar  in intel windows pc i am getting zlib error .
root@5486d71acc20:/mediapipe# bazel build -c opt --config=android_arm64 //mediapipe/tasks/java/com/google/mediapipe/tasks/genai:tasks_genai.aar
Starting local Bazel server and connecting to it...
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'flatbuffers' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'XNNPACK' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pthreadpool' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'cpuinfo' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_googlesource_code_re2' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'zlib' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'rules_android_ndk' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_glog_glog' because it already exists.
WARNING: The major revision of the Android NDK referenced by android_ndk_repository rule 'androidndk' is 22. The major revisions supported by Bazel are [10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21]. Bazel will attempt to treat the NDK as if it was r21. This may cause compilation and linkage problems. Please download a supported NDK version.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "691a29db9c336349e48e04c5c2f4873f2890af5cbfa6e51f4de87fefe6169294"
DEBUG: Repository rules_cc instantiated at:
/mediapipe/WORKSPACE:52:13: in
Repository rule http_archive defined at:
/root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:372:31: in
INFO: Repository zlib instantiated at:
/mediapipe/WORKSPACE:147:13: in
Repository rule http_archive defined at:
/root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:372:31: in
WARNING: Download from http://zlib.net/fossils/zlib-1.2.13.tar.gz failed: class com.google.devtools.build.lib.bazel.repository.downloader.ContentLengthMismatchException Bytes read 1464677 but wanted 1497445
ERROR: An error occurred during the fetch of repository 'zlib':
Traceback (most recent call last):
File "/root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl", line 132, column 45, in _http_archive_impl
download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [http://zlib.net/fossils/zlib-1.2.13.tar.gz] to /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/zlib/temp15394260953468651184/zlib-1.2.13.tar.gz: Bytes read 1464677 but wanted 1497445
ERROR: /mediapipe/WORKSPACE:147:13: fetching http_archive rule //external:zlib: Traceback (most recent call last):
File "/root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl", line 132, column 45, in _http_archive_impl
download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [http://zlib.net/fossils/zlib-1.2.13.tar.gz] to /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/zlib/temp15394260953468651184/zlib-1.2.13.tar.gz: Bytes read 1464677 but wanted 1497445
INFO: Repository android_opencv instantiated at:
/mediapipe/WORKSPACE:448:13: in
Repository rule http_archive defined at:
/root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:372:31: in
ERROR: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/com_google_protobuf/BUILD:208:11: @com_google_protobuf//:protobuf depends on @zlib//:zlib in repository @zlib which failed to fetch. no such package '@zlib//': java.io.IOException: Error downloading [http://zlib.net/fossils/zlib-1.2.13.tar.gz] to /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/zlib/temp15394260953468651184/zlib-1.2.13.tar.gz: Bytes read 1464677 but wanted 1497445
ERROR: Analysis of target '//mediapipe/tasks/java/com/google/mediapipe/tasks/genai:tasks_genai.aar' failed; build aborted:
INFO: Elapsed time: 38.240s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (217 packages loaded, 12736 targets configured)
Fetching http://zlib.net/fossils/zlib-1.2.13.tar.gz; 1.4 MiB (1,464,640B)
Fetching https://github.com/opencv/opencv/releases/download/4.10.0/opencv-4.10.0-android-sdk.zip; 43.3 MiB (45,381,432B)
@calbot  @kuaashish  please help how i can proceed.

Thank you @calbot i am able to proceed now and now i am getting this error
root@a343c9897bb2:/mediapipe# bazel build -c opt --config=android_arm64 //mediapipe/tasks/java/com/google/mediapipe/tasks/genai:tasks_genai.aar
Starting local Bazel server and connecting to it...
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'flatbuffers' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'XNNPACK' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pthreadpool' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'cpuinfo' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_googlesource_code_re2' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'zlib' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'rules_android_ndk' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'pybind11_protobuf' because it already exists.
DEBUG: /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/org_tensorflow/third_party/repo.bzl:132:14:
Warning: skipping import of repository 'com_github_glog_glog' 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:
/mediapipe/WORKSPACE:41:13: in
Repository rule http_archive defined at:
/root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:372:31: in
WARNING: /mediapipe/mediapipe/framework/tool/BUILD:204: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: /mediapipe/mediapipe/framework/BUILD:69: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.
DEBUG: Rule 'android_opencv' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "464d55abe64b53af3aeb73197cf4620535abd909916d06e6a8b7c32712013966"
DEBUG: Repository android_opencv instantiated at:
/mediapipe/WORKSPACE:437:13: in
Repository rule http_archive defined at:
/root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/external/bazel_tools/tools/build_defs/repo/http.bzl:372:31: in
WARNING: /mediapipe/mediapipe/tasks/java/com/google/mediapipe/tasks/genai/BUILD:37:26: in srcs attribute of android_library rule //mediapipe/tasks/java/com/google/mediapipe/tasks/genai:tasks_genai_android_lib: please do not import '//mediapipe/tasks/java/com/google/mediapipe/tasks/core:LlmTaskRunner.java' directly. You should either move the file to this package or depend on an appropriate rule there. Since this rule was created by the macro 'mediapipe_tasks_genai_aar', the error might have been caused by the macro implementation
INFO: Analyzed target //mediapipe/tasks/java/com/google/mediapipe/tasks/genai:tasks_genai.aar (221 packages loaded, 13958 targets configured).
INFO: Found 1 target...
WARNING: failed to create one or more convenience symlinks for prefix 'bazel-':
cannot create symbolic link bazel-mediapipe -> /root/.cache/bazel/_bazel_root/4884d566396e9b67b62185751879ad14/execroot/mediapipe:  /mediapipe/bazel-mediapipe (File exists)
INFO: From Compiling src/google/protobuf/message_lite.cc [for tool]:
In file included from /usr/include/string.h:535,
from external/com_google_protobuf/src/google/protobuf/stubs/port.h:39,
from external/com_google_protobuf/src/google/protobuf/stubs/common.h:48,
from external/com_google_protobuf/src/google/protobuf/message_lite.h:45,
from external/com_google_protobuf/src/google/protobuf/message_lite.cc:36:
In function 'void* memcpy(void*, const void*, size_t)',
inlined from 'uint8_t* google::protobuf::io::EpsCopyOutputStream::WriteRaw(const void*, int, uint8_t*)' at external/com_google_protobuf/src/google/protobuf/io/coded_stream.h:706:16,
inlined from 'virtual uint8_t* google::protobuf::internal::ImplicitWeakMessage::_InternalSerialize(uint8_t*, google::protobuf::io::EpsCopyOutputStream*) const' at external/com_google_protobuf/src/google/protobuf/implicit_weak_message.h:84:28,
inlined from 'bool google::protobuf::MessageLite::SerializePartialToZeroCopyStream(google::protobuf::io::ZeroCopyOutputStream*) const' at external/com_google_protobuf/src/google/protobuf/message_lite.cc:412:30:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:29:33: warning: 'void* __builtin___memcpy_chk(void*, const void*, long unsigned int, long unsigned int)' specified size between<PHONE_NUMBER>1562067968 and<PHONE_NUMBER>3709551615 exceeds maximum object size<PHONE_NUMBER>854775807 [-Wstringop-overflow=]
29 |   return __builtin___memcpy_chk (__dest, __src, __len,
|          ~~~^~
30 |                                  __glibc_objsize0 (__dest));
|                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~
INFO: From Executing genrule @org_tensorflow//tensorflow/lite/acceleration/configuration:configuration_schema:
When you use --proto, that you should check for conformity yourself, using the existing --conform
INFO: From Generating flatbuffer files for metadata_schema_cc_srcs: //mediapipe/tasks/metadata:metadata_schema_cc_srcs:
warning:
/mediapipe/mediapipe/tasks/metadata/metadata_schema.fbs:486: 21: warning: field names should be lowercase snake_case, got: sentencePiece_model
ERROR: /mediapipe/mediapipe/tasks/cc/metadata/BUILD:14:11: Compiling mediapipe/tasks/cc/metadata/metadata_extractor.cc failed: (Exit 1): clang failed: error executing command (from target //mediapipe/tasks/cc/metadata:metadata_extractor) external/androidndk/toolchains/llvm/prebuilt/linux-x86_64/bin/clang -no-canonical-prefixes '--target=aarch64-linux-android21' -fdiagnostics-color -Wa,--noexecstack '-std=gnu++17' -Wc++2a-extensions ... (remaining 133 arguments skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
In file included from mediapipe/tasks/cc/metadata/metadata_extractor.cc:30:
bazel-out/android-arm64-v8a-opt/bin/mediapipe/tasks/cc/metadata/metadata_parser.h:24:50: error: expected expression
inline constexpr char kMetadataParserVersion[] = "1.5.0
^
bazel-out/android-arm64-v8a-opt/bin/mediapipe/tasks/cc/metadata/metadata_parser.h:25:3: error: expected ';' after top level declarator
";
^
;
2 errors generated.
Target //mediapipe/tasks/java/com/google/mediapipe/tasks/genai:tasks_genai.aar failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 197.254s, Critical Path: 77.73s
INFO: 1965 processes: 418 internal, 1547 linux-sandbox.
FAILED: Build did NOT complete successfully .
Any insights how we can resolve this

@kuaashish  please help

@calbot  @kuaashish  i am using ndk 21will this cause any issue while generting the code ?which version i need to use ?

Hi @BalajiPolisetty2207,
All steps to implement our GenAI are documented here. Please let us know which specific steps you are looking for.
Thank you!!


Many arguments in LogDebug lines

Hi! I'm porting the library to a Nordic nrf52 chip. I've some issues with these lines, where the log command has more arguments than permitted by the SDK log function (the maximum number is 6). Is it possible to divide it in two or more calls ?
https://github.com/FreeRTOS/FreeRTOS-Cellular-Interface/blob/c4ccd2c09f6bcbd79ce31e773a35f552f8c3f16a/source/cellular_3gpp_api.c#L488
https://github.com/FreeRTOS/FreeRTOS-Cellular-Interface/blob/c4ccd2c09f6bcbd79ce31e773a35f552f8c3f16a/source/cellular_3gpp_api.c#L1795

Hello @mrcamilletti, thanks for taking the time to report this. We'll take a look and get back to you.

@mrcamilletti, @AniruddhaKanhere
Thank you the your feedback. I will follow this issue.

@mrcamilletti, @AniruddhaKanhere
This issue is fixed in #67.


Check user access to service on sign in

Context
We would like to check user roles as an authorisation step on the check-records part of the service.
The DfE Signin API exposes an endpoint which replies with user roles for a given user, service and organisation.
Changes

Call the DfE Sign in API get user access to service endpoint as part of the DSI login journey.
Authorise user based on presence of valid role for service, valid role codes are stored in ENV["DFE_SIGN_IN_API_ROLE_CODES"]
Create a DsiUserSession record on each successful login (except when bypass is active). This record contains the role and org info the user authenticated with.

Guidance to review
Local overrides are necessary to make this PR work. Specifically the env vars
DFE_SIGN_IN_API_BASE_URL
DFE_SIGN_IN_API_SECRET
DFE_SIGN_IN_API_AUDIENCE
DFE_SIGN_IN_API_ROLE_CODES

Link to Trello card
https://trello.com/c/mTFXWXo7/166-dfe-signin-role-spike

Checklist

[x] Attach to Trello card
[x] Rebased main
[x] Cleaned commit history
[x] Tested by running locally

 DfE Signin 'role' spike

 Store more things about the user


api: remove createModelFromXml from XMLRoutesDefinitionLoader

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] If you're unsure, you can format the pull request title like [CAMEL-XXX] Fixes bug in camel-file component, where you replace CAMEL-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean install -Psourcecheck in your module with source check enabled to make sure basic checks pass and there are no checkstyle violations. A more thorough check will be performed on your pull request automatically.
Below are the contribution guidelines:
https://github.com/apache/camel/blob/master/CONTRIBUTING.md

@davsclaus I've started working on https://issues.apache.org/jira/browse/CAMEL-15560 and as preliminary work I tried to clean up the XMLRoutesDefinitionLoader APIs, as result I've removed createModelFromXml from XMLRoutesDefinitionLoader as in fact it is only implemented by camel-core-jaxb and it does not look like - at least to me - the method has any relationship with the loader.

Yeah we never had the strong use-case for createModelFromXml in camel-xml-io. And its not really in use, thought had a public api for end users to load xml files into model classes.
But yeah having it on loader is not the nicest place.


Update configure-unit-tests-by-using-a-dot-runsettings-file.md

Add documentation for TreatDiscoveryWarningsAsErrors setting as suggested in this MSTest issue https://github.com/microsoft/testfx/issues/1736

@Mikejo5000
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off Thanks!


Undo Redo doesn't work on paragraph with children.

Hello!
I have this object for the initial editor value, given from the official slate example:
initialValue = [
{
      type: 'paragraph',
      children: [
          { text: 'This is editable ' },
          { text: 'rich', bold: true },
          { text: ' text, ' },
          { text: 'much', bold: true, italic: true },
          { text: ' better than a ' },
          { text: '<textarea>' },
          { text: '!' }
      ]
  }
]

When I mark in the editor for example "text, much" and remove it, then press ctrl+z and after it ctrl+y multiple times, more text gets removed then I initially removed ("text, much").
Thank you for possible solutions!

I fixed it, the mistake was that I got my initialValue for my editor from another component trough an @Input. That causes the undo/redo bugs, I don't know why this happens, but that clearly shouldn't be the case :)

I couldn't understand this issue, could you record a GIF or VIEDO showing the issue happening? @allanatorr


addHTML Is not working on IE 11

i am using addhtml() to add one div content to save as PDF, but it is not working on IE, i am not getting any error from console.
is there any one had same issue?

Unfortunately your issue is not specific enough. If you still have this error, please write and I will reopen the issue.


explore partnership with MangoPay

re: #126
Just had a good first call with Pierre from MangoPay. They basically are the European Balanced. Whitelabled, user experience wouldn't need to change much at all in terms of adding credit card and bank account details, we just switch under the hood based on country. They work with Visa, MC, Amex, and various national card brands. Deposits are via free SEPA wire transfer. Outstanding questions:

Can an American company come under their licence or would we need a European entity?
Gittip would at least need a European bank account. Pierre recommended HSBC and Bank of America (which works with BNP Paribas) for free or cheap wire transfers.
Can we make the flow work from Balanced escrow to Gittip's U.S. bank account to Gittip's European bank account into MangoPay escrow and out from there? (pic below)
He's going to get me detailed pricing and card information. It varies by country and card (amex).
MangoPay is targeting GPB and USD by June.

I suggested that we could have a three-way call with @balanced if needed.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/316261-explore-partnership-with-mangopay?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

Over on #67 we've ended up going with a piecemeal solution, with Braintree for payins, and PayPal/Zipmark (hopefully; #3491) for payouts.


Add New Edibles category

Prerequisites

[X] I am an Open Source Contributor
[X] I checked to make sure that this issue has not already been filed

Description
I want to add bakery products as a new category which will have:

different cards of bakery products
similar UI to other cards
same functionality as other items

Please assign this issue to me under JWOC
Screenshots
No response
Code of Conduct

[X] I follow Contributing Guidelines of this project.

Okay proceed but make sure to add every PNG images compressed to less than 50kb @S-ishita


Fix bower package name case

It's currently Materialize instead of more standard materialize.

+1. Capitalized package name is distracting.

Fixed by #3212


Create an API for the communication between spoolers and qlue

The configuration of the spooler is best known by the developers of the spooler. However, we have to communicate this to the users. So we should set up an API that allows the developer to set some of the properties of the devices that the developer created.

#5 is a first approach that allows the spooler to test if the front-end is having the appropiate configuration. Setting the back-end is most likely quite a bit more complicated. There are few things:

Who should be allowed to change the config. Only the 'spooler' user ? Only authorized 'spooler' maintainers ?
How should we implement the permissions ? Most likely the django permissions system is appropiate for that.

So we should decide if we wait with the acceptance of #5 until these are figured out or if we split it up and already start using the information of the qlue in the spoolers.
@RohitPrasadBhatt ?


Ignore generated scala files.

Description
Add the Macro generated list of files to .gitIgnore
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[X] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[X] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[X] create .gitignore file to ignore files that generated during build.

Comments

@frankfliu Thanks for the contribution!
@nswamy CI passed, could you help merge it? Thanks!
@mxnet-label-bot [pr-awaiting-merge]


Add explosion_radius/fire properties, fixes #1965

This should be expanded to include creepers, which inexplicably have their own methods rather than using the interface https://hub.spigotmc.org/javadocs/spigot/org/bukkit/entity/Creeper.html


boards: sparkfun: Add support for micromod_nrf52840 board and

Initial support of Sparkfun Micromod ecosystem with micromod nrf52840 board, asset tracker shield and micromod header definition.
The idea of this commit is to set up the basis of the Sparkfun Micromod ecosystem, which is a standard based on M.2 connectors and a specification to increase the availability of parts (boards, sensors and carriers). Since this ecosystem suits perfectly the Zephyr philosophy, it would be great to support these boards.
implemented and tested peripherals

UART bus connected to SARA-R5 modem with the samples/net/cellular_modem app
QSPI with w25q128jv flash memory with the samples/drivers/spi_flash app
SPI connected to a microSD with the samples/subsys/fs/fs_sample app
I2C connected to the faul gauge max17048 with the samples/fuel_gauge/max17048 app
USB for serial debugging with the samples/usb/console app

Resources
Micromod ecosystem pin/peripherals definition: https://learn.sparkfun.com/tutorials/getting-started-with-micromod
Micromod nrf52840 board: https://www.sparkfun.com/products/16984
Micromod asset tracker carrier: https://www.sparkfun.com/products/17272

I have updated the board files to suit the new hardware model v2. Thus, the board is "micromod" and the variant is "micromod/nrf52840". Besides, I have added the documentation for both the board and the shield.

Hi! I would like to know the state of the review, is there something else that I need to carry out? Thanks in advance

Hi! Since the new release will be frozen in two weeks... Is there something else that I should modify to get this pull request ready? Thanks in advance

@kartben please, check out that the images of the shield and board are in the corresponding doc/img folder since I have not modified it in this last push, but I see them in the corresponding folders.

Hi! I would like to know the PR status since I would like to close it before v3.7.0 release. I have carried out the @kartben and @nordicjm request. Is there something else that I should modify? thanks!

@jeronimoagullo you'll need to rebase as the CI failure is unrelated to your change and as since then been addressed

I have added minor changes according to check failures. It should pass the test now:

The nrf52840 cannot have two UARTS. Thus uart0 is now "UARTE" and uart1 is "UART" (similar to the nrf52840dk board).
Besides, I have added an overlay into tests/drivers/adc/adc_api test including "nordic,nrf-saadc-common.dtsi"

Now it passes all checks @kartben @nordicjm  @anangl

Hi @anangl it seems to be ready to merge


Inomurko/1265 prevent contracts  change boot

https://github.com/omisego/elixir-omg/issues/1265
Overview
Describe what your Pull Request is about in a few sentences.
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Change 1
Change 2
...

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

Coverage remained the same at ?% when pulling 61c0b46f8c344f13d4b8ff1742822f193d771b64 on inomurko/1265-prevent_contracts__change_boot into 0f14992280e81243a8fbc6f80601e7a8fbbbbb97 on master.

This is kinda a forceful approach to get gas measurements out. BlockQueue does need a bit of a rewrite - so thats why I decided for this approach.

I've also cleaned up some process initialisation so that configuration is now passed IN (top down) rather than read from the process itself!


Roll Engine from 5b2068872afe to 9ba7fdf7246e (4 revisions)

https://github.com/flutter/engine/compare/5b2068872afe...9ba7fdf7246e
2022-01-22<EMAIL_ADDRESS>[macOS] Fixed the platform view creation public method (flutter/engine#30996)
2022-01-22<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from jN5n0Wzss... to 4jCbYGgPk... (flutter/engine#30995)
2022-01-22<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from d1Wlz-aBU... to FPHYMGiv5... (flutter/engine#30994)
2022-01-22<EMAIL_ADDRESS>Roll Dart SDK from f472e051f203 to d680aba1e21f (1 revision) (flutter/engine#30993)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from d1Wlz-aBU1Il to FPHYMGiv55yG
fuchsia/sdk/core/mac-amd64 from jN5n0Wzssv_F to 4jCbYGgPkaa7
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


Change '*' Activation Event to 'OnStartupFinished'

This will help codetour not slow down vscode startup.

#282


[Feature Request] can we get a new release?

Waiting on this change https://github.com/mobile-dev-inc/maestro/pull/1119, but the last release was over a month ago https://github.com/mobile-dev-inc/maestro/releases/tag/cli-1.28.0

We will release next week. Thank you for the feedback and your understanding


Origin registration status API doesn't update

Pelican Version:
Run ./pelican --version to get version number.
Pelican Service:

Origin

Describe the bug
A clear and concise description of what the bug is.
The /origin_ui/exports API contains origin registration status. The data should reflect if the origin registration is complete. However, even after the admin fixed the issue at the registry, the API still returns the existing status and didn't pull the latest status.
To Reproduce
Steps to reproduce the behavior.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. Linux, MacOS]
Browser: [e.g. chrome, safari, if the bug relates to any web user interface]

Additional context
Add any other context about the problem here.

One small comment about these issues -- can you remove any parts of the pre-filled issue that you don't populate? That would make it a bit quicker to find which sections have information.


Time-series widget displays more bins than date data

STR

Create a map from a dataset with a date column. This column has a range of values between 2015-12-18T00:00:00Z and 2016-09-08T00:00:00Z.
Add a time series widget and a formula widget (in order to count rows).
Filter from 15:52 09/22/2016  to  00:00 10/01/2016. The expected result would be just one data point, but instead, you get 571 rows (see screenshot below):

This behaviour is also described happening with Deep Insights.

It looks like very often it is setting way too much bins

This problem will be tackled in #12088.

this has already been pushed as part of https://github.com/CartoDB/cartodb/pull/12464
shall we close the issue then @ramiroaznar ?

Yes! Thanks mates!


Add sustainability notes

Our RepairCafe presents this project during a local "week of sustainability" and promotes support and help for people who want to build this project in the RepairCafe.
For this presentation I wanted to write down some notes on sustainability of this project. I think building a Phoniebox might be more or less sustainable, depending on how the project is built.
I think these notes are a nice addition to the project notes.
What do you think?

Hi @topas-rec
thanks for adding these lines to README. As you saw, and quoted, there is the line "You might be surprised how easy and affordable you can get an RPi second hand. Think about the planet before you buy a new one." Just went back through the files history and saw that I added this with the second commit of the Readme file back in Feb 2017. I am all for your additional information. Thank you.


Chrome crush without lighthouse noticing leads to an infinite loop

<%= moduleName %> version: 0.0.1
node version: v8.11.4
npm (or yarn) version: yarn 1.10.1

What happened:

Problem description:
Chrome is crashing and lighthouse continues to run without rejecting or fulfilling its Promise, and garie-lighthouse never move to the next URL since it didn't finish with the first one, once the cron job is fired again the same thing happens again, it's pretty much a never ending game.
Suggested solution:
Time base short circuit, let's say default to 5min (customized via Env Var) if it's timed out, we simply kill chrome and move on to the next URL.

I'm closing this, if anyone stumbled upon the same issue, you could try this alternative:
https://github.com/mouafa/iceberg-lighthouse


Adding tests to autoinstrumentation (isPodEligible/libsToInject)

This is part of #26632
Adding tests to the autoinstrumentation code and factoring out isPodEligible so we can
have coverage for library injection vs pod eligibility for library injection.
This verbatim lifts out the inlined code and puts it in a separate function.

/merge


Mobject.animate.rotate does not work properly in Manim 0.17.2

Description of bug / unexpected behavior
Mobject.animate.rotate does not work properly in Manim 0.17.2
I think the current transformation is a scaling transformation and not a rotation as it should be.
I tried also Mobject.animate.apply_matrix(np.array([[cos(-PI), sin(-PI), 0], [-sin(-PI), cos(-PI), 0], [0, 0, 1]])), but it does not work.
Expected behavior

It should rotate the Mobject like the Rotate class.
How to reproduce the issue

Code for reproducing the problem
from manim import *
import numpy as np

O = np.array([0., 0., 0.])
X = np.array([1., 0., 0.])
Y = np.array([0., 1., 0.])
Z = np.array([0., 0., 1.])

class Quick(Scene):

    def construct(self):
        center = Dot(O)
        line = Line(O, X)
        self.add(center)
        # With `.rotate`, it does not work
        self.play(line.animate.rotate(-PI, about_point=O, axis=Z))
        # With `Rotate`, it works fine
        # self.play(Rotate(line, angle=-PI, about_point=O, axis=Z))

Additional media files

Images/GIFs
https://user-images.githubusercontent.com/78030392/211155293-80403b4b-b410-4b02-a7d9-fd51ef83d49c.mp4

System specifications
System Details

OS : Linux
Python version : Python 3.10.9
Installed modules : Manim 0.17.2, numpy 1.21.5

FFMPEG
Output of ffmpeg -version: ffmpeg version 4.2.7-0ubuntu0.1

That is the correct behavior, since .animate only interpolates between the starting and ending state. To rotate the object, the Rotate class can be used instead.
See: https://docs.manim.community/en/stable/tutorials/quickstart.html#using-animate-syntax-to-animate-methods

Thanks for your answer ! I will pay more attention next time !


No longer use deprecated function

Could you add a feature check? We should aim for backwards compatibility here, as not every consumer is able to switch to 0.13 immadiately

How would you implement this feature check? Note sure I understand.

Oh, I didn't see it was in the readme. Though this was REact 0.12 to 0.13 compatibility. Lesson learned: Don't comment on PR's while in a meeting :P
Thanks for the PR


better storage obligation safety

The host now locks storage obligations before ever pulling them from the
database, and keeps the locks until the host is no longer going to be
adding them to the database. This resolves some issues relating to
storage obligation corruption, which can cause errors like 'Consensus
Conflict' and can cause the host to report the wrong revision number, or
to have the wrong sector roots, etc.

This causes a NDF in my contractor integration test:
--- FAIL: TestResync (2.52s)
	host_integration_test.go:652: host did not accept revision request: the requested file contract is currently locked

The lock timeout in the test may not be long enough.

same scenario, this time in a different test:
--- FAIL: TestIntegrationDelete (7.61s)
	host_integration_test.go:356: host did not accept revision request: the requested file contract is currently locked

I think I'm going to have to add some custom printlns, been unable to get this to fail locally

ok, I've added some code that should improve the safety and add a lot of output. Hopefully it tells us what is going wrong.

Problem discovered and fixed. Travis should be happy now.
A deadlock witnessed in the wild caused me to add safelocks to the host. The locking in the host is not all that clean, so I think it's a good idea to have them anyway, at least for a short period of time. I'm thinking about adding a safety feature to the TryMutex as well, that will let you set a max duration that a lock can be held. I don't think it would be difficult to implement (easier than for safelocks - the hard part about the safelocks is that the readlocks mean multiple threads can have a lock at once. For the TryMutex, only one lock can be held, so if it's timing out, it is pretty easy to know who is the culprit.
Anyway, this PR should be good to go, safety in the TryMutex is for another PR.

mac still exhibiting NDF on TestResync

Found it for real this time

Recent failure appears to be due to unsafety in the way that the gateway uses ThreadGroups - right now it's possible for the gateway to end up with a single thread that calls Add twice. That's a completely separate PR.


03/27/2018 17:40 : Create Pull Request for branch prTesting_2018032717 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update fs2-core, fs2-io to 2.5.7

Updates

co.fs2:fs2-core
co.fs2:fs2-io

from 2.2.2 to 2.5.7.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "co.fs2" } ]

labels: library-update, semver-minor

Superseded by #200.


[Autocomplete] On mobile selecting option keeps keyboard open

When using the autocomplete input on mobile the keyboard doesn't disappear after selecting an item from the dropdown list. Even when selecting an item and seeing it populate the input then clicking the enter key on the keyboard is still there.

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
Keyboard doesn't disappear on mobile when selecting something from the autocomplete input.

Expected Behavior 🤔
After typing and selecting a match in the list the keyboard should disappear.

Steps to Reproduce 🕹

Steps:

Go to material-ui.com on mobile
Select an autocomplete input and start typing
Click item from list of matches

Context 🔦

I'm making a progressive web app and would like to stay within the material ui component library instead of moving to use react-select or downshift for autocomplete search
Your Environment 🌎

Tech
Version

Material-UI (lab)
v4.0.0-alpha.35

Browser
Chrome 78.0.3904.108

OS
Android 9

@oliviertassinari On desktop as well as mobile, the underlying <TextField /> keeps focused after an option is selected. Is this not the normal behaviour?

@scott-mcnulty I have wondered about this point during the initial implementation of the component. Keeping the focus was done on purpose to be closer to a regular input experience and not to interrupt the experience when working on a multi-select input.

downshift

I believe you would have to implement the logic on your own going with this solution. The solution would be almost identical to what you would need to write to add such support to the Autocomplete.

react-select

If you have a desktop with a touch screen, it will blur the input, even if you have used your mouse or keyboard to select the value ❌.

I think that we can add an opt-in prop for such behavior: blurOnSelect? false | true | 'touch' | 'pointer'.
diff --git a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
index 38f9ee430..6722376bd 100644
--- a/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
+++ b/packages/material-ui-lab/src/useAutocomplete/useAutocomplete.js
@@ -71,6 +71,7 @@ export default function useAutocomplete(props) {
     autoComplete = false,
     autoHighlight = false,
     autoSelect = false,
+    blurOnSelect = 'touch',
     clearOnEscape = false,
     debug = false,
     defaultValue,
@@ -91,8 +92,8 @@ export default function useAutocomplete(props) {
     multiple = false,
     onChange,
     onClose,
-    onOpen,
     onInputChange,
+    onOpen,
     open: openProp,
     options = [],
     value: valueProp,
@@ -666,9 +667,25 @@ export default function useAutocomplete(props) {
     setHighlightedIndex(index, 'mouse');
   };

+  const isTouch = React.useRef(false);
+
+  const handleOptionTouchStart = () => {
+    isTouch.current = true;
+  };
+
   const handleOptionClick = event => {
     const index = Number(event.currentTarget.getAttribute('data-option-index'));
     selectNewValue(event, filteredOptions[index]);
+
+    if (
+      blurOnSelect === true ||
+      (blurOnSelect === 'touch' && isTouch.current) ||
+      (blurOnSelect === 'pointer' && !isTouch.current)
+    ) {
+      inputRef.current.blur();
+    }
+
+    isTouch.current = false;
   };

   const handleTagDelete = index => event => {
@@ -814,6 +831,7 @@ export default function useAutocomplete(props) {
         id: `${id}-option-${index}`,
         onMouseOver: handleOptionMouseOver,
         onClick: handleOptionClick,
+        onTouchStart: handleOptionTouchStart,
         'data-option-index': index,
         'aria-disabled': disabled,
         'aria-selected': selected,

What do you think of this diff? Do you want to work on a pull request?

@scott-mcnulty If you don't mind I could work on this issue.

@m4theushw Ok, this sounds good, but let's way @scott-mcnulty perspective on the matter first :).

I like the idea of the blurOnSelect prop you suggested @oliviertassinari -- seems like a good way to go
@m4theushw If you'd like to work on this be my guest :slightly_smiling_face:
Thank you guys for your help!


Material documentation

Describe the missing content
Materials (e.g. entity.material) don't seem to be documented anywhere. We need to know:

What is the full schema? What do all the fields do, and what possible values are there?
How does inheritance work?
What do all of the vanilla materials look like? As in, visually, with screenshots.

Describe the missing content Materials (e.g. entity.material) don't seem to be documented anywhere. We need to know:

What is the full schema? What do all the fields do, and what possible values are there?
How does inheritance work?
What do all of the vanilla materials look like?

If you are skilled with machine translator or familiar with Chinese, you can refer these Chinese docs:
Full schemas: https://wiki.bedev.cn/page/Manual:材质
Fields / Inharitance usage: above and https://mc.163.com/dev/mcmanual/mc-dev/mcguide/16-美术/7-材质与着色器/材质的分类.html?catalog=1
Vanilla usage: https://mc.163.com/dev/mcmanual/mc-dev/mcguide/16-美术/7-材质与着色器/材质配置说明.html?catalog=1

Hello!
It looks like we've made some progress on this. Since it's been a while, I'm going to close this issue, but if you have any additional feedback, please reach out to us!
Thanks!


grant all privileges?

mysql> grant all privileges on  hklabor to testpriv;
/*preferred output*/
mysql> show tables in hklabor;
+--------------------------------+
| Tables_in_hklabor              |
+--------------------------------+
| some table
| some table
| some table
| some table
| some table
| some table
+--------------------------------+
6 rows in set (0.01 sec)

/*actual output, run from user testpriv*/

MySQL [(none)]> show tables in hklabor;
Empty set (0.002 sec)

/* What actually works */

mysql> grant all privileges on database  hklabor to ‘testpriv’;

However, I do believe based on standard MySQL the first query should have just worked. Very confusing.

Curioser and curiosier, grant all privileges only grants CREATE table privileges, but not select, insert, delete, drop, lol


Can’t override colour of Field Label component

Type: minor
Describe the bug
The colour of a Field Label is set to #737373 no matter what the labelText theme variable is set to.
To Reproduce
Steps to reproduce the behavior:

Set the labelText variable to something obvious like 'red'.
Find a Field Label (like on the Checkout page)
Inspect element
See that there is color: 'red' followed by color: #737373 overriding that.

Expected behavior
If I set labelText: 'red' then I expect the label to be red. Or to have some other variable to set this.
Screenshots

Desktop (please complete the following information):

OS: Mac
Browser: Chrome
Version: 70

@morgoe I think this is an error with the Field theming docs. The field labels use labelText for everything EXCEPT color because color differs based on the validity of the field.
You can override color by adding this to your theme:
FieldLabel: {
  color_default: customDefaultColor,
  color_error: customErrorColor,
  color_focus: customFocusColor,
  color_success: customSuccessColor
}

Note that you'll probably want to have identical or similar colors for each input state, too:
Input: {
    borderColor_default: colors.black20,
    borderColor_error: colors.red,
    borderColor_focus: colors.teal,
    borderColor_success: colors.teal,
    color_default: colors.coolGrey500,
    color_disabled: colors.black25,
    color_error: colors.red,
    color_focus: colors.coolGrey500,
    color_success: colors.black55,
    iconColor_default: colors.black55,
    iconColor_disabled: colors.black25,
    iconColor_error: colors.red,
    iconColor_success: colors.forestGreen
}

I'll leave this issue open so that the info from this comment can be added to the theming docs for those components.


[bug] Doesn't start when use node 14

OS: Ubuntu 20.04
When I use node 14.15.0, the hotel start command is executed without error but it actually doesn't start a server. However, when I switch to node 12.19.0 it work.

Got the same here!
My specs:

OS: Ubuntu 20.04.2 LTS x86_64
Kernel: 5.8.0-45-generic
CPU: AMD Ryzen 5 1600 (12) @ 3.200GHz

Same issue on Node 15.4.0

Node Version: v14.17.0
The hotel start command successfully executed but the browser said it cannot reach localhost:2000.

FYI:  I've been very happily using https://github.com/jeansaad/chalet - a maintained fork that runs on recent Node versions!


fix(rust): improve ockam tcp-outlet delete --help text

Proposed changes

Fixes #6345
Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] There are no Merge commits in this Pull Request. Ockam repo maintains a linear commit history. We merge Pull Requests by rebasing them onto the develop branch. Rebasing to the latest develop branch and force pushing to your Pull Request branch is okay.
[x] I have read and accept the Ockam Community Code of Conduct.
[x] I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

Hey @makeittotop, the PR looks good but we need you to first accept our CLA as described here:

I have read and accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam repository. The easiest way to do this is to edit the CONTRIBUTORS.csv file in the github web UI and create a separate Pull Request, this will mark the commit as verified.

Thanks for the pointer @Adrian. I've created a PR as you suggested -
https://github.com/build-trust/ockam/pull/6427
Kindly take a look when there is time.
Regards.
Abhishek Pareek
On Sun, Oct 8, 2023 at 12:00 PM Adrian Benavides @.***>
wrote:

Hey @makeittotop https://github.com/makeittotop, the PR looks good but
we need you to first accept our CLA as described here:
I have read and accepted the Ockam Contributor License Agreement
https://github.com/build-trust/.github/blob/main/CLA.md by adding my
Git/Github details in a row at the end of the CONTRIBUTORS.csv
https://github.com/build-trust/ockam/blob/develop/.github/CONTRIBUTORS.csv
file in a separate pull request to the build-trust/ockam
https://github.com/build-trust/ockam repository. The easiest way to do
this is to edit the CONTRIBUTORS.csv
https://github.com/build-trust/ockam/edit/develop/.github/CONTRIBUTORS.csv
file in the github web UI and create a separate Pull Request, this will
mark the commit as verified.
—
Reply to this email directly, view it on GitHub
https://github.com/build-trust/ockam/pull/6371#issuecomment-1752131994,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABFYC7LRKQL5WG33JK3S3SLX6LZ3XAVCNFSM6AAAAAA5X3ZA3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGEZTCOJZGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


openBrowser() causes docker-compose set ups to fail because of spawn EACCESS

closes #710

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

Thanks!

Awesome, thanks for merging @gaearon !

@gaearon any chance this could make it in the 0.4.4 release as it's only a bug fix with no bc or other side effects?

I plan to release 0.5.0 today. I likely won't have the time to do two releases today so I hope it won't be too much of an inconvenience to you.

Ah awesome! I thought the 0.5.0 release would be some way further down the road because I saw 0.4.3 and 0.4.4 lined up. That will be aboslutely fast enough :)
Thanks for the uber quick responses!


multiple columns capability for keyed_max aggregate

I have a use case where devices are publishing their position to a stream:
CREATE STREAM raw_gps
( dev_id text,
  ts timestamp(3) with time zone,
  lat double precision,
  lng double precision);

A simple frontend might want to display the latest position of all of the devices, current capability in pipelineDB uses the following syntax where lat and lng is required to be concatenated into a single column for output:
CREATE CONTINUOUS VIEW latest_gps AS
	SELECT dev_id, max(ts), keyed_max (ts,lat || ',' || lng)
	FROM prd_raw_gps
	GROUP BY dev_id;

It would be nice to be able to keep these two (or 'n') items in separate columns in the view, i.e. so that they can be referenced individually in subsequent views.
Something like this would be nice:
SELECT dev_id, max(ts), keyed_max (ts,lat), keyed_max(ts,lng)
OR
SELECT dev_id, max(ts), keyed_max (ts,(lat,lng))

@peterbeasley Another workaround in the meantime is to just use two aggregates:
CREATE CONTINUOUS VIEW latest_gps AS
    SELECT dev_id, max(ts),
        keyed_max (ts,lat) AS lat, keyed_max(ts, lng) as lng
    FROM prd_raw_gps
    GROUP BY dev_id;

keyed_max is a very lightweight aggregate so this is going to incur negligible performance impact.

Ahh that's perfect, I didn't realise it was the naming keyed_max that my database was complaining about... renaming with the AS term has fixed my problem :-)

It seems like just using multiple aggregates is the cleanest solution here.


Get URL

Hi,
How I can get the url from every image?
I would click on the image and download it.
Thanks

or get the image source.

Hey @Mflm , the source for the control is an array with imageUrl properties, so by the current index you can easily get the Url from your bound array.

Thanks


Unable to Configure and Run camera_ros After Reinstallation

Unable to Configure and Run camera_ros After System Reset
Description
I previously used the camera_ros package successfully on my Raspberry Pi 5 without any additional configuration. However, after resetting my computer, I’ve been unable to get it working despite following the same steps and reinstalling all required dependencies.
The node fails to configure the camera and consistently throws errors. I also noticed that both libcamera and camera_ros have been updated recently, and reverting to older versions did not solve the problem. Additionally, I can still capture images using QCam, so libcamera appears to be functioning correctly.

System Details

Hardware: Raspberry Pi 5 + IMX708 camera module (2 units)
Software:

OS: Ubuntu 24.04
ROS 2: Jazzy
Libraries: libcamera, v4l2, camera_ros

Current Issues and Errors

v4l2_camera Error:

Failed stream start: Invalid argument (22)

Camera_ros Error:

Can't configure camera with invalid configuration
terminate called after throwing an instance of 'std::runtime_error'
what():  failed to configure streams
Abort.

Current Issues and Errors

Error Summary: The camera_ros node fails to configure the camera streams due to invalid configuration and unsupported pixel formats.
Details:

The default pixel format (YUV420) is not supported by the camera.
The system attempts to auto-select a pixel format (R8) and resolution (640x480), but adjusts it to an unsupported configuration (1536x864-SBGGR16).
The stream configuration results in the error:Can't configure camera with invalid configuration
failed to configure streams
Removing camera while still in use

Additionally, the container throws the following exception:Component constructor threw an exception: failed to configure streams

ros2 launch camera_ros  camera.launch.py Error

Error Summary: The camera_ros node fails to configure the camera due to invalid stream configuration and unsupported default pixel formats.
Details:

The default pixel format (YUV420) is not supported by the camera.
The system attempts to auto-select a pixel format (R8) and resolution (1920x1080), but adjusts it to an unsupported configuration (2304x1296-SBGGR16).
This leads to the following critical error:Can't configure camera with invalid configuration
failed to configure streams

The process terminates with:terminate called after throwing an instance of 'std::runtime_error'
what():  failed to configure streams

ros2 run camera_ros camera_node   Errors

Error Summary: The camera_ros node fails to configure the camera due to invalid stream configuration and unsupported default pixel formats.
Details:

The default pixel format (YUV420) is not supported by the camera.
The system attempts to auto-select a pixel format (R8) and resolution (1920x1080), but adjusts it to an unsupported configuration (2304x1296-SBGGR16).
This leads to the following critical error:Can't configure camera with invalid configuration
failed to configure streams

The process terminates with:terminate called after throwing an instance of 'std::runtime_error'
what():  failed to configure streams

Steps to Reproduce

Installed all dependencies for camera_ros and libcamera.
Verified the camera works with QCam.
Attempted to run camera_ros using the following commands:

ros2 run camera_ros camera_node --ros-args -p camera:=0 -p format:="YUYV" -p width:=1640 -p height:=1232

or:
ros2 run camera_ros camera_node --ros-args -p camera:=0

Tried modifying the role parameter to raw and viewfinder, but the errors persisted.
Reverted both libcamera and camera_ros to previous versions.

What I Tried

Verified that QCam can still capture images, confirming that libcamera works.
Used supported formats and resolutions (e.g., 1640x1232-YUYV).
Reinstalled all dependencies.
Tried previous versions of both libcamera and camera_ros.

Expected Behavior
The node should configure the camera successfully and stream images, as it did during the initial setup without any manual adjustments.
Questions

Are there any known issues with the latest updates to libcamera or camera_ros?
How can I prevent these configuration errors?
Is there a recommended debugging or setup process to ensure compatibility between libcamera and camera_ros?

Additional Context
The current situation has become very frustrating, as the same hardware and software setup worked flawlessly during my initial installation. Any help or guidance would be greatly appreciated.

v4l2_camera Error:

Failed stream start: Invalid argument (22)

Are you referring to https://gitlab.com/boldhearts/ros2_v4l2_camera.git? This is not using libcamera. Are you trying to use the Raspberry Pi camera with V4L2 instead of libcamera?

Camera_ros Error:

Can't configure camera with invalid configuration
terminate called after throwing an instance of 'std::runtime_error'
what():  failed to configure streams
Abort.

Where is this message coming from? The node does not show an error "Can't configure camera with invalid configuration".
The failed to configure streams exception looks like a duplicate of https://github.com/christianrauch/camera_ros/issues/64. Did you try any of the workarounds there?
Did you have a look at the "Trouble Shooting" section? Especially enabling debug information for libcamera and the ROS node should provide more useful information. Can you also list explicitly which commands you run? It's not yet clear to me which commands cause which error.
Since you also list "2 units", do you have 2 cameras connected to the board? Does this work with a single camera only or with a different camera connected to the board?

Current Issues and Observations
1. V4L2 and Libcamera Usage
I am using the following resources:

Libcamera: Libcamera GitHub
V4L2: V4L2 GitHub

I understand that V4L2 does not utilize Libcamera, but the issue persists even when I use Libcamera exclusively.
2. Error: Can't configure camera with invalid configuration

The error occurs as follows:[0:10:09.009613503] [3434] ERROR Camera camera.cpp:1171 Can't configure camera with invalid configuration
terminate called after throwing an instance of 'std::runtime_error'
  what():  failed to configure streams

I referred to Issue #64 and tried the suggested workarounds, but the issue persists.

3. Pixel Format Errors in Debug Logs

Default pixel format YUV420 is not supported:

[WARN] [camera]: default pixel format (YUV420) not supported

Adjustments auto-select to "1920x1080-R8", but still fail:

[WARN] [camera]: stream configuration adjusted from "1920x1080-R8" to "2304x1296-SBGGR16"

4. QSocketNotifier Error
-This occurs intermittently:
QObject::connect: Cannot queue arguments of type 'QSocketNotifier*'

5. Compilation Errors (Libcamera)

When compiling with Libcamera, switch errors are encountered:

/home/pixbot/ros2_ws/src/camera_ros/src/clamp.cpp: In function ‘libcamera::ControlValue clamp(const libcamera::ControlValue&, const libcamera::ControlValue&, const libcamera::ControlValue&)’:
error: enumeration value ‘ControlTypePoint’ not handled in switch [-Werror=switch]

-Similar issues occur in cv_to_pv.cpp and other files.
Observations

Cameras are detected correctly in debug logs:

>> cameras:
   0: imx708 (/base/axi/pcie@120000/rp1/i2c@88000/imx708@1a)
   1: imx708 (/base/axi/pcie@120000/rp1/i2c@80000/imx708@1a)

Qcam is able to provide an image feed, so the hardware seems functional.

These issues began after re-installing the environment on a reset system.

Steps Tried
-Referred to Trouble Shooting.
-Enabled detailed debugging using LIBCAMERA_LOG_LEVELS=*:DEBUG.
-Verified hardware by testing with Qcam.

1. V4L2 and Libcamera Usage
I am using the following resources:

Libcamera: Libcamera GitHub

The libcamera repo at https://github.com/raspberrypi/libcamera is a fork of the upstream repo that is not supported. Use the official upstream repo or the binary packages from the ROS repo.

2. Error: Can't configure camera with invalid configuration

The error occurs as follows:[0:10:09.009613503] [3434] ERROR Camera camera.cpp:1171 Can't configure camera with invalid configuration
terminate called after throwing an instance of 'std::runtime_error'
  what():  failed to configure streams

You still have to provide the commands that you run and the debug information.

3. Pixel Format Errors in Debug Logs

Default pixel format YUV420 is not supported:

[WARN] [camera]: default pixel format (YUV420) not supported

Adjustments auto-select to "1920x1080-R8", but still fail:

[WARN] [camera]: stream configuration adjusted from "1920x1080-R8" to "2304x1296-SBGGR16"

Did you try to enable debug information?

4. QSocketNotifier Error
-This occurs intermittently:
QObject::connect: Cannot queue arguments of type 'QSocketNotifier*'

This repo is not using Qt. So this error cannot come from the ROS node.

5. Compilation Errors (Libcamera)

When compiling with Libcamera, switch errors are encountered:

/home/pixbot/ros2_ws/src/camera_ros/src/clamp.cpp: In function ‘libcamera::ControlValue clamp(const libcamera::ControlValue&, const libcamera::ControlValue&, const libcamera::ControlValue&)’:
error: enumeration value ‘ControlTypePoint’ not handled in switch [-Werror=switch]

-Similar issues occur in cv_to_pv.cpp and other files.

Use the newest released version from the upstream repo or the binary package from the ROS repo.

Observations

Cameras are detected correctly in debug logs:

>> cameras:
   0: imx708 (/base/axi/pcie@120000/rp1/i2c@88000/imx708@1a)
   1: imx708 (/base/axi/pcie@120000/rp1/i2c@80000/imx708@1a)

Did you try with a single camera as suggested?

Qcam is able to provide an image feed, so the hardware seems functional.
These issues began after re-installing the environment on a reset system.

What could I conclude from this? I don't know what change and could have caused an issue.

Steps Tried
-Referred to Trouble Shooting.

This links to the non-existing website https://github.com/raspberrypi/libcamera/wiki/Troubleshooting. What should I find there?

-Enabled detailed debugging using LIBCAMERA_LOG_LEVELS=*:DEBUG.

Where is this debug log?

-Verified hardware by testing with Qcam.

If you want help, you have to try the suggestions and provide the information that is asked for. Since I do not have the hardware to test and reproduce this myself, I rely on the information from those that have the hardware. But if you cannot provide information to better understand the issue and see if it is different from the other failed to configure streams issue, I have to close those since this just consumes time without any progress.

Hardware and Software Used

Device: Raspberry Pi 5
Camera: Raspberry Pi Camera Module 3
Operating Systems: Ubuntu 24.04 (64-bit) arm
Libcamera Version: v0.3.0
ROS 2 Version: Jazzy

Findings
Camera Not Detected on Ubuntu:
The "Available cameras" section is empty.
The error "Unable to acquire a Unicam instance" was encountered.
Camera Works Seamlessly on Raspbian:
The camera is detected, and image capture is successful.
The ROS 2 node runs without issues.
Driver Compatibility:
It was observed that camera drivers (especially Unicam) are not functioning correctly on Ubuntu.
The Raspberry Pi Camera Module 3 is not properly detected on Ubuntu, whereas it works seamlessly on Raspbian. This indicates a potential incompatibility with camera drivers or the libcamera configuration on Ubuntu.
LIBCANERA_LOG_LEVELS=*:DEBUG cam -l
[1:11:25.540318062] [5901] DEBUG IPAModule ipa_module.cpp:334 ipa_rpi_vc4.so: IPA module /usr/local/lib/aarch64-linux-gnu/libcamera/ipa_rpi_vc4.so is signed
[1:11:25.540429339] [5901] DEBUG IPAManager ipa_manager.cpp:245 Loaded IPA module '/usr/local/lib/aarch64-linux-gnu/libcamera/ipa_rpi_vc4.so'
[1:11:25.540470987] [5901]  INFO Camera camera_manager.cpp:313 libcamera v0.3.0
[1:11:25.540642060] [5904] DEBUG Camera camera_manager.cpp:69 Starting camera manager
[1:11:25.568831078] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rp1-cfe" created from /dev/media0
[1:11:25.570020219] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media0 due to 10 missing dependencies
[1:11:25.573099571] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media0 found
[1:11:25.573152033] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media0: rp1-cfe
[1:11:25.573346588] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rp1-cfe" created from /dev/media1
[1:11:25.573655327] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media1 due to 10 missing dependencies
[1:11:25.575633537] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media1 found
[1:11:25.575648370] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media1: rp1-cfe
[1:11:25.575769092] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rpivid" created from /dev/media3
[1:11:25.575779444] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media3 due to 1 missing dependencies
[1:11:25.576069646] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media3 found
[1:11:25.576092034] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media3: rpivid
[1:11:25.576450699] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "pispbe" created from /dev/media2
[1:11:25.576489069] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media2 due to 9 missing dependencies
[1:11:25.576858363] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "pispbe" created from /dev/media4
[1:11:25.576922789] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media4 due to 9 missing dependencies
[1:11:25.579778716] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media2 found
[1:11:25.579868216] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media2: pispbe
[1:11:25.583751767] [5904] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media4 found
[1:11:25.583789174] [5904] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media4: pispbe
[1:11:25.584485355] [5904] DEBUG Camera camera_manager.cpp:134 Found registered pipeline handler 'rpi/vc4'
[1:11:25.584546762] [5904] DEBUG RPI vc4.cpp:178 Unable to acquire a Unicam instance
[1:11:25.584554836] [5904] DEBUG RPI vc4.cpp:178 Unable to acquire a Unicam instance
Available cameras:

~/ros2_ws$ ros2 run camera_ros camera_node
[1:07:20.248118571] [5694] DEBUG IPAModule ipa_module.cpp:334 ipa_rpi_vc4.so: IPA module /usr/local/lib/aarch64-linux-gnu/libcamera/ipa_rpi_vc4.so is signed
[1:07:20.248228923] [5694] DEBUG IPAManager ipa_manager.cpp:245 Loaded IPA module '/usr/local/lib/aarch64-linux-gnu/libcamera/ipa_rpi_vc4.so'
[1:07:20.279787433] [5694]  INFO Camera camera_manager.cpp:313 libcamera v0.3.0
[1:07:20.280057192] [5709] DEBUG Camera camera_manager.cpp:69 Starting camera manager
[1:07:20.306533728] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rp1-cfe" created from /dev/media0
[1:07:20.306835877] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media0 due to 10 missing dependencies
[1:07:20.308694918] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media0 found
[1:07:20.308708622] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media0: rp1-cfe
[1:07:20.308849844] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rp1-cfe" created from /dev/media1
[1:07:20.309106900] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media1 due to 10 missing dependencies
[1:07:20.310955589] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media1 found
[1:07:20.310965126] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media1: rp1-cfe
[1:07:20.311068849] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rpivid" created from /dev/media3
[1:07:20.311078034] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media3 due to 1 missing dependencies
[1:07:20.311264034] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media3 found
[1:07:20.311272164] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media3: rpivid
[1:07:20.311386016] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "pispbe" created from /dev/media2
[1:07:20.311395905] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media2 due to 9 missing dependencies
[1:07:20.311512165] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "pispbe" created from /dev/media4
[1:07:20.311525128] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media4 due to 9 missing dependencies
[1:07:20.313136353] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media2 found
[1:07:20.313146279] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media2: pispbe
[1:07:20.314749134] [5709] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media4 found
[1:07:20.314760634] [5709] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media4: pispbe
[1:07:20.315274969] [5709] DEBUG Camera camera_manager.cpp:134 Found registered pipeline handler 'rpi/vc4'
[1:07:20.315333432] [5709] DEBUG RPI vc4.cpp:178 Unable to acquire a Unicam instance
[1:07:20.315341821] [5709] DEBUG RPI vc4.cpp:178 Unable to acquire a Unicam instance
terminate called after throwing an instance of 'std::runtime_error'
  what():  no cameras available
[ros2run]: Aborted

~/ros2_ws$ ros2 launch camera_ros  camera.launch.py
[INFO] [launch]: All log files can be found below /home/pixbot/.ros/log/2024-11-30-10-40-33-695463-pixbot-desktop-5740
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [component_container-1]: process started with pid [5758]
[component_container-1] [INFO] [1732952434.412683348] [camera_container]: Load Library: /home/pixbot/ros2_ws/install/camera_ros/lib/libcamera_component.so
[component_container-1] [INFO] [1732952434.526415786] [camera_container]: Found class: rclcpp_components::NodeFactoryTemplate<camera::CameraNode>
[component_container-1] [INFO] [1732952434.526530490] [camera_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<camera::CameraNode>
[component_container-1] [1:07:52.938455688] [5758] DEBUG IPAModule ipa_module.cpp:334 ipa_rpi_vc4.so: IPA module /usr/local/lib/aarch64-linux-gnu/libcamera/ipa_rpi_vc4.so is signed
[component_container-1] [1:07:52.938656466] [5758] DEBUG IPAManager ipa_manager.cpp:245 Loaded IPA module '/usr/local/lib/aarch64-linux-gnu/libcamera/ipa_rpi_vc4.so'
[component_container-1] [1:07:52.957544709] [5758]  INFO Camera camera_manager.cpp:313 libcamera v0.3.0
[component_container-1] [1:07:52.957843154] [5774] DEBUG Camera camera_manager.cpp:69 Starting camera manager
[component_container-1] [1:07:52.982661686] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rp1-cfe" created from /dev/media0
[component_container-1] [1:07:52.984111875] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media0 due to 10 missing dependencies
[component_container-1] [1:07:52.986655380] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media0 found
[component_container-1] [1:07:52.986707713] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media0: rp1-cfe
[component_container-1] [1:07:52.986954899] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rp1-cfe" created from /dev/media1
[component_container-1] [1:07:52.987611456] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media1 due to 10 missing dependencies
[component_container-1] [1:07:52.990527925] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media1 found
[component_container-1] [1:07:52.990592999] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media1: rp1-cfe
[component_container-1] [1:07:52.990921518] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "rpivid" created from /dev/media3
[component_container-1] [1:07:52.990964148] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media3 due to 1 missing dependencies
[component_container-1] [1:07:52.991720261] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media3 found
[component_container-1] [1:07:52.991784298] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media3: rpivid
[component_container-1] [1:07:52.992453633] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "pispbe" created from /dev/media2
[component_container-1] [1:07:52.992522373] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media2 due to 9 missing dependencies
[component_container-1] [1:07:52.993176282] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:230 New media device "pispbe" created from /dev/media4
[component_container-1] [1:07:52.993277245] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:96 Defer media device /dev/media4 due to 9 missing dependencies
[component_container-1] [1:07:52.997043531] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media2 found
[component_container-1] [1:07:52.997086938] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media2: pispbe
[component_container-1] [1:07:52.998927109] [5774] DEBUG DeviceEnumerator device_enumerator_udev.cpp:322 All dependencies for media device /dev/media4 found
[component_container-1] [1:07:52.998950257] [5774] DEBUG DeviceEnumerator device_enumerator.cpp:258 Added device /dev/media4: pispbe
[component_container-1] [1:07:52.999594962] [5774] DEBUG Camera camera_manager.cpp:134 Found registered pipeline handler 'rpi/vc4'
[component_container-1] [1:07:52.999684203] [5774] DEBUG RPI vc4.cpp:178 Unable to acquire a Unicam instance
[component_container-1] [1:07:52.999691110] [5774] DEBUG RPI vc4.cpp:178 Unable to acquire a Unicam instance
[component_container-1] [ERROR] [1732952434.625048527] [camera_container]: Component constructor threw an exception: no cameras available
[ERROR] [launch_ros.actions.load_composable_nodes]: Failed to load node '' of type 'camera::CameraNode' in container '/camera_container': Component constructor threw an exception: no cameras available
[component_container-1] [INFO] [1732952434.632353912] [camera_container]: Load Library: /opt/ros/jazzy/lib/libimage_view_nodes.so
[component_container-1] [INFO] [1732952434.745858572] [camera_container]: Found class: rclcpp_components::NodeFactoryTemplate<image_view::DisparityViewNode>
[component_container-1] [INFO] [1732952434.745932924] [camera_container]: Found class: rclcpp_components::NodeFactoryTemplate<image_view::ExtractImagesNode>
[component_container-1] [INFO] [1732952434.745946517] [camera_container]: Found class: rclcpp_components::NodeFactoryTemplate<image_view::ImageSaverNode>
[component_container-1] [INFO] [1732952434.745959906] [camera_container]: Found class: rclcpp_components::NodeFactoryTemplate<image_view::ImageViewNode>
[component_container-1] [INFO] [1732952434.745972350] [camera_container]: Instantiate class: rclcpp_components::NodeFactoryTemplate<image_view::ImageViewNode>
[component_container-1] [INFO] [1732952434.765416372] [image_view_node]: Using transport "raw"
[INFO] [launch_ros.actions.load_composable_nodes]: Loaded node '/image_view_node' in container '/camera_container'
[component_container-1] QSocketNotifier: Can only be used with threads started with QThread

ls /dev/video*
/dev/video0   /dev/video14  /dev/video22  /dev/video28  /dev/video33  /dev/video5
/dev/video1   /dev/video15  /dev/video23  /dev/video29  /dev/video34  /dev/video6
/dev/video10  /dev/video19  /dev/video24  /dev/video3   /dev/video35  /dev/video7
/dev/video11  /dev/video2   /dev/video25  /dev/video30  /dev/video36  /dev/video8
/dev/video12  /dev/video20  /dev/video26  /dev/video31  /dev/video37  /dev/video9
/dev/video13  /dev/video21  /dev/video27  /dev/video32  /dev/video4

v4l2-ctl --list-devices
pispbe (platform:1000880000.pisp_be):
    /dev/video20
    /dev/video21
    /dev/video22
    /dev/video23
    /dev/video24
    /dev/video25
    /dev/video26
    /dev/video27
    /dev/video28
    /dev/video29
    /dev/video30
    /dev/video31
    /dev/video32
    /dev/video33
    /dev/video34
    /dev/video35
    /dev/video36
    /dev/video37
    /dev/media2
    /dev/media4
rp1-cfe (platform:1f00110000.csi):
    /dev/video8
    /dev/video9
    /dev/video10
    /dev/video11
    /dev/video12
    /dev/video13
    /dev/video14
    /dev/video15
    /dev/media0
rp1-cfe (platform:1f00128000.csi):
    /dev/video0
    /dev/video1
    /dev/video2
    /dev/video3
    /dev/video4
    /dev/video5
    /dev/video6
    /dev/video7
    /dev/media1
rpivid (platform:rpivid):
    /dev/video19
    /dev/media3

Your issue report is inconsistent.
Previously, you reported that the cameras were detected and only failed during the configuration viafailed to configure streams. Now you report that cameras are not detected no cameras available. You also report that the libcamera example cam does not detect the cameras. I don't see how the ROS node can help you with that. If the cameras are not detected because of configuration issues etc., then the ROS node cannot use them.
Please consider the Raspberry Pi documentation on how to set up the cameras.
Also, if ros2 run camera_ros camera_node already fails to detect cameras, why would the launch file ros2 launch camera_ros camera.launch.py help?
Please go back to the original issue of the configuration failure (failed to configure streams) and provide the debug information that was asked for.


Twitter is not a constructor error

Hi all,
I am trying to use this in angular app.I have a component where i have imported using
import {twitter} from 'twitter';
on click on button i am triggering this function but i am getting error

ERROR TypeError: WEBPACK_IMPORTED_MODULE_3_twitter.twitter is not a constructor

This error refers to  "var client = new twitter"
postTweet(){
  //var Twitter = require('twitter'); // i could not use this its giving me error require is unknown.
  var client = new twitter({
  consumer_key: 'QBuYddf0LnKCQLJ2jNPDnn14v',
  consumer_secret:'	RJZZWYuQ3qYryFdfddak3YkEW7dw9v2ecbAmG6nK64iUcfg',
  access_token_key:'<PHONE_NUMBER>84549120-pksmqrMdEYPJbYDvcq015MBWqmD6KdA',
  access_token_secret: 'ShAolKDxsEGgdfdfdfdfdfdstagPbTG7pEok8DcUxpni9iTxB7'
  });
status = 'testing'
  client.post('statuses/update', {status: status},  function(error, tweet, response) {
    if(error) throw error;
    console.log(tweet);  // Tweet body.
    console.log(response);  // Raw response object.
  });

}

What i am missing ?

You should do
import Twitter from 'twitter'

When you do import { something }, you're importing the non-default export by the name "twitter", which is not what you want in this case. You want the class Twitter.


imagine deleting files

https://raw.githubusercontent.com/AcierP/discord-account-generator/033c14ac27eda7b55756140d2c3895dd53d26130/generator.py

If you can read, it’s currently being rewritten

you still shouldn't delete it


Remote database and transaction problem

I have a issue with transaction. In local embedded database everything is fine with following sequence:

Begin Transaction
Add Vertex with any custom property CID (my equivalent of ID) for example CID = 12345
Get Vertex  with CID = 12345
Commit

But in remote database in step 3, Function return null (getVertices().hasNext() == false)

Assigned to @tglman

Hi,
This is solved with the support of remote transactions in 3.0.
Closing


.NET Use case for node.js frontend builds?

Would it be a good idea to point out there are some valid professional reasons you would still want to use Node and frontend build tools etc in Windows vs WSL?
I'm working on a .NET Core Razor Pages based project on Windows and would like to use Node for frontend build tools and packaging.  Things like compiling SCSS, minifying JS and maybe a little Webpack usage for pulling in and bundling in community JS bits and pieces to help with my Razer Pages.
I came to this page expecting some validation of use cases on Windows for projects like mine but left wondering what exactly the best practise is?
Reading through the Microsoft documentation if you use node.js in anyway that's professional you should use WSL.  Trouble is that becomes nearly impossible to manage in a .NET type project like mine in an IDE etc.
I'm also thinking just how would Blazor web developers handle JS pieces they need to pull in and package up etc, WSL again seems tricky at best to use alongside.  I'm guessing everybody is currently using a native Windows install of node.js which again is another very valid 'professional' use case.
I've looked at the node.js repo and as expected Windows is down as a Tier 1 OS with support on par with Linux and MacOS etc.  Totally understand why using it on WSL is better in a lot of ways.  If I was building an isolated React frontend I'd reach for WSL for instance.
I'm just trying to point out there are valid professional use cases and the docs currently cause confusion (to me anyway :))
Here's some of the pages that might need clarification...
https://docs.microsoft.com/en-us/windows/dev-environment/javascript/windows-or-wsl
https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl
https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows
There's some more in the React and Vue getting started areas as well.
Many thanks :)

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

ID: 08e8c321-52c2-f80d-1004-274547ca362e
Version Independent ID: 943bb38d-635e-2772-d61e-5e85f301d259
Content: Should I install on Windows or Windows Subsystem for Linux (WSL)
Content Source: hub/dev-environment/javascript/windows-or-wsl.md
Product: dev-environment
Technology: windows-javascript
GitHub Login: @mattwojo
Microsoft Alias: mattwoj

Well... this is an embarrassingly slow reply, but this issue got buried among all of the other feedback. That said, I'm finally combing through old issues and agree with you that the guidance to use Node on WSL for "professional" use isn't accurate. I've removed the Windows vs WSL guidance as I actually don't think it's helpful any longer. Both Windows and Linux (or WSL) have professional uses for NodeJS and I don't think we actually need to offer guidance on which to use... it will mostly depend on individual circumstances and preferences. Anyhow, here's the commit where I removed all of that guidance: https://github.com/MicrosoftDocs/windows-dev-docs/commit/2197bc6ffeb413324b55e52d2e1ac29c2f555ea2
Closing this issue and thanks for filing it. (and sorry again it took so long to resolve!)

No problem, glad to see the updates 👍

Isn't the section Use Windows Subsystem for Linux for production also outdated?

Node.js has Tier 1 support for running on Windows & Windows Server, same as Linux
The iisnode repository is owned by Azure
Azure supports Nodejs apps on Windows Servers
Needing to host a Node.js app on a Windows Server is less of an edge case now with popular frontend frameworks
like Next.js and Remix


"No checklist found for tag" error shown for pre-existing tag.

Hi,
I've run into a bug that I cannot escape from and is breaking my workflow dramatically. I used to have an "act" tag that I would use for different tasks (i.e. "act/todo", "act/review", etc).
Since last month checklists have stopped working and a "No checklist found for tag #act" is always shown.
Here's the configuration:

And here's what I keep seeing:

Another weird thing I see: the settings menu does not show the correct information for the configured tag.
Edit: Also (as mentioned in a comment below) I cannot click on the tags to show/hide anything

Versions

Checklist plugin: 2.2.7
Obsidian: 0.15.9 (macOS)

Thanks!

I am having similar problems.
As well as the sometimes malformed tag names in the Show Tags? dialogue, I am sometimes finding that I can't click on any of the tag names shown to select the ones I need.
Checklist version 2.2.5
Obsidian v0.15.9 (Windows 11)

I can't replicate this issue on my machines. Would you mind clearing out your tags and re-inputting them fresh?
If you're still seeing the bug can you open up the Developer Console and screenshot if there are any errors?

Using the Tag Wrangler plugin I renamed act to actt and now items are showing :| (weird).
However, new items are not added to the list.

After re-renaming tags back to act things seem to go back to normal:

But as soon as I close the Vault and re-open it... 😢

I am having similar problems.

Maybe it's because of the multi-level tags.

Any update on this @flankstaek ? Did the console screenshots help?

also have this, can no longer see any todo items checklist 2.2.10, Obsidian v1.0.3

Same here v2.2.10 of the plugin and v1.0.3 of obsidian

The plugin had been working great up until today when I was no longer able to add any more todo items and this error arose.
This occurred on two of my machines, at first I still had the todo checklists visible up until I unchecked the todo tag as a filter and they all disappeared. The filter option was then was no longer selectable until the Obsidian program was fully reset. Observing the developer console I am noticing a similar error message as above.

The last few days of using the plugin have been great so I am thrilled with the workflow possibilities using this plugin.
I'm rather inspired to fork the code and begin searching for a solution since it does not seem to be a bug that everyone is experiencing.

I don't know if this plugin is still maintained. Last time I heard from @flankstaek was 5 months ago and didn't get an answer to the updated info I added :(.
This plugin was super useful in my workflow while I used it. If you do fork the code (or become a collaborator) would be super helpful!

Still no answer nor fix :(
Came here to share I'm now using a Dataview query to simulate this plug-in (not optimal but it works).

Install Obsidian Dataview.
Add the same tag to the files where your tasks will be written (I use #my/daily-notes)
Use the tag you would usually list on the obsidian-checklist panel as a header for sets of tasks

Example
### #todo
- [ ] some todo
- [ ] another

Create a new note with the following Dataview query

```dataview
Task
From #my/daily-notes
Where !completed and (text != "" and text != "...")
Sort file.ctime desc
Limit 20
Group by meta(section).subpath

Hope this helps other people having this problem.

Fixed in 2.2.13

Finally, it works again! Thanks!


Can't change input values of slider component when setting min and max as well

Reproduction
https://formkit.link/085a3c140822c833b7e2b5b903118e60
Describe the bug
Hi, I just noticed a problem with the slider component. When you set a min and max value and add the show-input attribute, you can't adjust the number via the input. It is happening in all versions of FormKit.
Reproduction: https://formkit.link/085a3c140822c833b7e2b5b903118e60
Try to change the right number to anything lower than 65 with the input. It will immediately jump to the min value (13) and you just can't adjust it that way.
I was wondering if this is a known issue, if there is a workaround or how I can at least disable the input fields?
Environment
• OS: [e.g. iOS]: MacOS
• Browser [e.g. chrome, safari]: Chrome
• Version [e.g. 22]

Hi @andrew-boyd, I understand this might not be an easy fix! Is there a way I can disable the input fields for now?

Any update on this? @andrew-boyd


Fonts not loading properly in ember-cli 2.4.0

This seems to be a bug with ember-cli 2.4.0. Tracking the issue at https://github.com/ember-cli/ember-cli/issues/5538

This has been fixed in ember-cli 2.4.1


Cloud account takeover if a resource using a service account is compromised

Describe the bug
I have a GCS bucket and a google_storage_bucket_iam_member with a role that allows a service account to manage files within the bucket.
resource "google_storage_bucket_iam_member" "default" {
  bucket = google_storage_bucket.default.name
  role   = "roles/storage.objectAdmin"
  member = "serviceAccount:${google_service_account.default.email}"
}

This produces the following potential problem

Impact:     Cloud account takeover if a resource using a service account is compromised
Resolution: Limit service account access to minimal required set

This seems to me to be a false positive. There are a few other roles that trigger this warning as well. Is the problem triggered because the role has admin in the name?
If this is not a false positive or a bug, what is the recommendation for the level of granularity to assign roles?
I have considered using the 9 assigned permissions for objectAdmin but that seems excessive and a round about way to skirt the problem.
resourcemanager.projects.get
resourcemanager.projects.list
storage.objects.create
storage.objects.delete
storage.objects.get
storage.objects.getIamPolicy
storage.objects.list
storage.objects.setIamPolicy
storage.objects.update

The recommendation is generally to avoid any kind of "admin" level permissions where possible, and assign more granular permissions i.e. a subset of the above permissions as required. This is sometimes going to raise issues where all of those permissions (or use of the storageAdmin role and similar) is required, but we prefer to err on the side of caution in this case.


Golden file comparator can't be extended to define a custom behavior

Description
Current implementation of _TestOptimizationAwareGoldenFileComparator doesn't allow extension mecanism in order to define a custom behavior like allowing tolerance of pixel difference when comparing files. Even a custom comparator is defined, it will be overriden by  _TestOptimizationAwareGoldenFileComparator.
Expected Behavior
A custom comparator are also executed in addition of _TestOptimizationAwareGoldenFileComparator.
Additional Context
Extending the current file comparator meets a real need. We would like to tolerate a little pixel difference on CI. Since upgrading to Flutter 3.7, Golden, even when using the Ahem font, Golden tests are platform sensitive. Then when using very_good test (or flutter) on CI running on MacBook Pro, tests fail because golden masters are built on different architecture or machine type (e.g. M1/M2 with arm chip ).
This is a known issue on flutter. A workaround is allow pixel diff when comparing.:

https://github.com/eBay/flutter_glove_box/issues/160#
https://github.com/flutter/flutter/issues/111739

Facing same problem here

The latest (0.17.0) CLI version should solve this. Feel free to reopen if you experience issues.


Does this code need GPU for inference?

Does this code need GPU for inference/evaluating the model?

No demo runs on CPU: ./demo.py --gpu -1.


feat(onyx-915): use new consignmentSubmission MP fields when rendering submission state section

This PR resolves []
Description
Same as https://github.com/artsy/force/pull/13849 - Force/Eigen hardcode submission status labels and help messages.  We've moved this logic to myCollectionConnection...consignmentSubmission MP field (https://github.com/artsy/metaphysics/pull/5702) and in this PR we are replacing old "hardcoded" data with the new one taken from MP. Nothing should change visually, so I am not attaching screenshots.
PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

#nochangelog
Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against 816d37f5aba46d7a2c2809307f9d3f9b8e6748f9