How long does it take to fine tuning a Alpaca 7B model?

Check before submitting issues

[X] Make sure to pull the latest code, as some issues and bugs have been fixed.
[X] I have read the Wiki and FAQ section AND searched for similar issues and did not find a similar problem or solution
[X] Third-party plugin issues - e.g., llama.cpp, LangChain, text-generation-webui, we recommend checking the corresponding project for solutions

Type of Issue
Model training and fine-tuning
Base Model
Chinese-Alpaca-2 (7B/13B)
Operating System
Linux
Describe your issue in detail
Command: bash run_sft.sh

run_sft.sh: Default parameters with modules_to_save removed.
I'm buying the service for renting a 4090 for 1 day. The progress seems slow (idk, maybe 30mins for 0.01 epochs?). I don't know if I'm correct. How long will it take? I'm worrying I have to expend the renting time to more days.
Dependencies (must be provided for code-related issues)
peft                          0.3.0.dev0
sentencepiece                 0.1.99
torch                         2.0.1+cu118
torchaudio                    2.0.2+cu118
torchvision                   0.15.2+cu118
transformers                  4.32.1

Execution logs or screenshots

Thanks, where do I set the eval strategy?

nvm, I saw that, thanks!


Mediapipe Android Build Issue

Plugin Version or Commit ID
v0.10.1
Unity Version
2020.3.29f1
Your Host OS
Windows 11
Target Platform
Android
[Windows Only] Visual Studio C++ and Windows SDK Version
No response
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
No response
Command Sequences
python build.py build --android arm64 -v
Log
INFO (build.py): Building protobuf sources...
DEBUG (build.py): Running bazel build -c opt //mediapipe_api:mediapipe_proto_srcs
2022/12/16 15:31:28 Downloading https://releases.bazel.build/5.2.0/release/bazel-5.2.0-linux-x86_64...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
WARNING: Download from http://mirror.tensorflow.org/github.com/bazelbuild/rules_closure/archive/cf1e44edb908e9616030cc83d085989b8e6cd6df.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/2f6de37d68a4c69e2ff9eec3cebbf1369e496940.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_benchmark' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11_bazel' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'xctestrunner' because it already exists.
DEBUG: /home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/org_tensorflow/third_party/repo.bzl:124:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: Rule 'rules_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "3d26569c952113b6dfa61553d451a78e5aa6d36b7b9206490d7fc8d0dfa28171"
DEBUG: Repository rules_cc instantiated at:
/home/mediapipe/WORKSPACE:90:13: in
Repository rule http_archive defined at:
/home/mediapipe/.cache/bazel/_bazel_mediapipe/6c11c387a04fa8f17c87a5c6db6ee555/external/bazel_tools/tools/build_defs/repo/http.bzl:353:31: in
INFO: Analyzed target //mediapipe_api:mediapipe_proto_srcs (102 packages loaded, 1252 targets configured).
INFO: Found 1 target...
ERROR: /home/mediapipe/mediapipe_api/calculators/image/BUILD:78:17: Executing genrule //mediapipe_api/calculators/image:recolor_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:108:17: Executing genrule //mediapipe_api/util/tracking:push_pull_filtering_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/gpu/BUILD:122:17: Executing genrule //mediapipe_api/gpu:gpu_origin_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/gpu/BUILD:156:17: Executing genrule //mediapipe_api/gpu:copy_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/video/BUILD:65:17: Executing genrule //mediapipe_api/calculators/video:box_tracker_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:124:17: Executing genrule //mediapipe_api/calculators/util:packet_latency_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/core/BUILD:104:17: Executing genrule //mediapipe_api/calculators/core:gate_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/tflite/BUILD:90:17: Executing genrule //mediapipe_api/calculators/tflite:tflite_tensors_to_landmarks_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/core/BUILD:68:17: Executing genrule //mediapipe_api/calculators/core:packet_thinner_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:229:17: Executing genrule //mediapipe_api/calculators/util:landmark_projection_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/video/BUILD:75:17: Executing genrule //mediapipe_api/calculators/video:tracked_detection_manager_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/motion/BUILD:20:17: Executing genrule //mediapipe_api/framework/formats/motion:optical_flow_field_data_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/BUILD:138:17: Executing genrule //mediapipe_api/framework/formats:image_file_properties_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:302:17: Executing genrule //mediapipe_api/calculators/util:local_file_contents_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/gpu/BUILD:130:17: Executing genrule //mediapipe_api/gpu:scale_mode_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/gpu/BUILD:147:17: Executing genrule //mediapipe_api/gpu:gl_surface_sink_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/BUILD:39:17: Executing genrule //mediapipe_api/util:audio_decoder_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:124:17: Executing genrule //mediapipe_api/util/tracking:frame_selection_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:140:17: Executing genrule //mediapipe_api/util/tracking:tracking_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:60:17: Executing genrule //mediapipe_api/util/tracking:motion_saliency_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:247:17: Executing genrule //mediapipe_api/calculators/util:rect_transformation_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/image/BUILD:125:17: Executing genrule //mediapipe_api/calculators/image:opencv_encoded_image_to_image_frame_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:311:17: Executing genrule //mediapipe_api/calculators/util:logic_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/face_geometry/protos/BUILD:53:17: Executing genrule //mediapipe_api/modules/face_geometry/protos:geometry_pipeline_metadata_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/BUILD:117:17: Executing genrule //mediapipe_api/framework:calculator_options_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:129:17: Executing genrule //mediapipe_api/modules/objectron/calculators:filter_detection_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:36:17: Executing genrule //mediapipe_api/util/tracking:tone_models_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:210:17: Executing genrule //mediapipe_api/calculators/util:thresholding_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:200:17: Executing genrule //mediapipe_api/calculators/util:labels_to_render_data_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/core/BUILD:59:17: Executing genrule //mediapipe_api/calculators/core:packet_resampler_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/core/BUILD:77:17: Executing genrule //mediapipe_api/calculators/core:split_vector_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/tensor/BUILD:57:17: Executing genrule //mediapipe_api/calculators/tensor:tensors_to_landmarks_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/BUILD:162:17: Executing genrule //mediapipe_api/framework/formats:location_data_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/BUILD:64:17: Executing genrule //mediapipe_api/util:render_data_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/BUILD:165:17: Executing genrule //mediapipe_api/framework:stream_handler_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/BUILD:179:17: Executing genrule //mediapipe_api/framework/formats:rect_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:266:17: Executing genrule //mediapipe_api/calculators/util:landmarks_smoothing_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:293:17: Executing genrule //mediapipe_api/calculators/util:top_k_scores_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:111:17: Executing genrule //mediapipe_api/modules/objectron/calculators:lift_2d_frame_annotation_to_3d_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/video/BUILD:45:17: Executing genrule //mediapipe_api/calculators/video:motion_analysis_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:107:17: Executing genrule //mediapipe_api/calculators/util:packet_frequency_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/BUILD:146:17: Executing genrule //mediapipe_api/framework/formats:image_format_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:161:17: Executing genrule //mediapipe_api/calculators/util:rect_to_render_scale_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/BUILD:56:17: Executing genrule //mediapipe_api/util:label_map_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/annotation/BUILD:29:17: Executing genrule //mediapipe_api/framework/formats/annotation:locus_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:238:17: Executing genrule //mediapipe_api/calculators/util:landmarks_to_floats_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:90:17: Executing genrule //mediapipe_api/calculators/util:latency_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/core/BUILD:95:17: Executing genrule //mediapipe_api/calculators/core:sequence_shift_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/face_geometry/protos/BUILD:44:17: Executing genrule //mediapipe_api/modules/face_geometry/protos:face_geometry_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:52:17: Executing genrule //mediapipe_api/modules/objectron/calculators:a_r_capture_metadata_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:92:17: Executing genrule //mediapipe_api/util/tracking:motion_models_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/BUILD:48:17: Executing genrule //mediapipe_api/util:color_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:62:17: Executing genrule //mediapipe_api/calculators/util:detection_label_id_to_text_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:72:17: Executing genrule //mediapipe_api/calculators/util:filter_detections_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:142:17: Executing genrule //mediapipe_api/calculators/util:association_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:85:17: Executing genrule //mediapipe_api/modules/objectron/calculators:belief_decoder_config_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:256:17: Executing genrule //mediapipe_api/calculators/util:landmarks_to_detection_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/graphs/object_detection_3d/calculators/BUILD:35:17: Executing genrule //mediapipe_api/graphs/object_detection_3d/calculators:model_matrix_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/core/BUILD:86:17: Executing genrule //mediapipe_api/calculators/core:quantize_float_vector_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/BUILD:129:17: Executing genrule //mediapipe_api/framework/formats:detection_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/framework/formats/object_detection/BUILD:20:17: Executing genrule //mediapipe_api/framework/formats/object_detection:anchor_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:76:17: Executing genrule //mediapipe_api/modules/objectron/calculators:frame_annotation_tracker_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/audio/BUILD:51:17: Executing genrule //mediapipe_api/calculators/audio:stabilized_log_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:52:17: Executing genrule //mediapipe_api/util/tracking:region_flow_computation_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:44:17: Executing genrule //mediapipe_api/modules/objectron/calculators:object_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:148:17: Executing genrule //mediapipe_api/util/tracking:box_tracker_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:44:17: Executing genrule //mediapipe_api/util/tracking:tone_estimation_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:84:17: Executing genrule //mediapipe_api/util/tracking:region_flow_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/tensor/BUILD:48:17: Executing genrule //mediapipe_api/calculators/tensor:tensors_to_detections_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:164:17: Executing genrule //mediapipe_api/util/tracking:box_detector_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:220:17: Executing genrule //mediapipe_api/calculators/util:detections_to_rects_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:98:17: Executing genrule //mediapipe_api/calculators/util:non_max_suppression_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:93:17: Executing genrule //mediapipe_api/modules/objectron/calculators:tflite_tensors_to_objects_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/face_geometry/protos/BUILD:61:17: Executing genrule //mediapipe_api/modules/face_geometry/protos:mesh_3d_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/util/tracking/BUILD:76:17: Executing genrule //mediapipe_api/util/tracking:motion_analysis_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/calculators/util/BUILD:170:17: Executing genrule //mediapipe_api/calculators/util:detections_to_render_data_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
ERROR: /home/mediapipe/mediapipe_api/modules/objectron/calculators/BUILD:120:17: Executing genrule //mediapipe_api/modules/objectron/calculators:frame_annotation_to_rect_calculator_cs failed: (Exit 127): bash failed: error executing command /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
/bin/bash: $'\r': command not found
Target //mediapipe_api:mediapipe_proto_srcs failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 736.021s, Critical Path: 60.83s
INFO: 346 processes: 161 internal, 185 processwrapper-sandbox.

Additional Context
I am building native library for Android using Linux Docker Container. But When I am running the command  "python build.py build --android arm64 -v". I am getting the error as I mentioned in the Logs. How to resolve this issue?

See https://github.com/homuler/MediaPipeUnityPlugin/wiki/Installation-Guide#binbash-line-1-r-command-not-found.


Unfreeze base query from App Analytics

This will require docs changes
Shouldn't be too much work otherwise? - roughly 1 week for dev and testing work to make sure it doesn't break anything
UX/PM concerns about unfreezing base query breaking other things (for example dashboards?)
@mengweieric what do you think about this?

Could you elaborate a little bit about what are the things to do with this? Context/problem to solve/simple feature briefing? May use a feature template.


Add status code accessor to RedirectAttempt

Gives custom redirect handlers some more info to work with. My actual use case is showing the trace of redirects to the user, including both HTTP status and Location header.

Cool, seems like a fine thing to receive.


[5.3] View sections blank in extending templates

Laravel Version: 5.3.30
PHP Version: 7.1.0
Database Driver & Version: MySQL (5.7.16)

Description:
Hard to describe, but sections have stopped working in templates extending more than one level deep in the hierarchy tree.
Steps To Reproduce:
I have the following template hierarchy:

layouts/master.blade.php
layouts/app.blade.php extends layouts/master.blade.php
layouts/channel.blade.php extends layouts/app.blade.php

I have sections defined in layouts/app.blade.php. But in any views that extend layouts/channel.blade.php, these sections stop appearing.
My layouts/app.blade.php file looks like this:
@extends('layouts.master')

@section('navbar.nav.left')
    <!-- Navbar left content -->
@endsection

@section('navbar.nav.right')
    <!-- Navbar right content -->
@endsection

And my layouts/channel.blade.php template looks like this:
@extends('layouts.app')

Screen-shot of a view that extends layouts/app.blade.php (navbar content visible):

Screen-shot of a view that extends layouts/channel.blade.php (navbar content blank):

My layouts/channel.blade.php template isn’t re-defining or overwriting these sections. And the navbar used to work on these pages. So this seems like a Blade processing issue that’s recently been introduced.

The issue doesn't seem to exist in latest 5.4, please upgrade your application and ping me if the issue still exists.
Or you can upload a test app on a public repo that I can clone and see if I can replicate the issue using your setup.


Remove ArcGisImageServerTerrainProvider

Deprecation PR: https://github.com/AnalyticalGraphicsInc/cesium/pull/4981
Details: https://github.com/AnalyticalGraphicsInc/cesium/issues/4955
There are also a couple @see ArcGisImageServerTerrainProvider in the doc that should be removed as well.

There is also a comment in doc you need to remove.
Also - Can you provide more information about this change?

@hanokhaloni see http://gis.stackexchange.com/questions/228806/cesiumjs-1-32-and-arcgis-10-2-arcgisimageserverterrainprovider-is-being-deprec


Create a new pull request by comparing changes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 94.944%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
1993

Relevant Lines:
2053

💛  - Coveralls


Cannot upload image on Android device

Thank you for this library btw. It's been incredibly helpful.
Anyways, I'm having trouble uploading images to S3 when I am simulating on Android. On iOS, I have no troubles at all.
Note: I am using React-Native-Camera
I am currently using:
{
"react-native": "0.43.0",
"react-native-camera": "git+https://github.com/lwansbrough/react-native-camera.git",
"react-native-aws3": "0.0.8",
}

Here's my code:
    this.camera.capture()
      .then((data) => {
        this.setState({ path: data.path })
        const file = {
          uri: data.path,
          name: `${uuid.v1()}.jpg`,
          type: 'image/jpeg',
        };

        const options = {
          keyPrefix: 'photos/',
          bucket: 'accountabilibuddy-1',
          region: 'us-west-1',
          accessKey: AWSAccessKeyId,
          secretKey: AWSSecretKey,
          successActionStatus: 201
        };

        RNS3.put(file, options).then(response => {
          if (response.status !== 201) {
            throw new Error('Failed to upload image to S3', response);
          }
          this.props.pictureTaken(response.body.postResponse.location) // reduxAction here(don't mind)
        }).catch(err => console.error('Camera error not uploaded: ', err))
      })
      .catch(err => console.error(err));
  }

For the inner catch, I am getting the following error:

For the outer catch, I am getting the following error:

Has this library worked for others on Android?

yes I'm struggling with this error as well :(

@smokymcbear @truongnmt are you still having this error?

@chuson1996 @MrHubble  : I'm not getting an error for this anymore. I was able to solve it by providing the correct AWSSecretKey and AWSAccessKeyId within my .env file as reflected within my bucket accountabilibuddy-1.
Here's the example code where I got it to work: https://github.com/smokymcbear/Accountabili-buddy/blob/master/src/containers/Camera.js
Hope this helps 😁

I'm also having this problem, the library was super easy to setup and worked immediately.... on iOS.  Then when I tested on Andriod its throwing errors.
In my specific case, I am using the Expo Image Picker (ImagePicker.launchImageLibraryAsync) then feeding the file that was picked into React Native ImageEditor to resize it.
I suspect the issue is centered around the file location?
When I console.log the file location on Andriod:
file:///data/user/0/host.exp.exponent/cache/ReactNative_cropped_image_777159874.jpg
When I console.log the file location on iOS:
rct-image-store://0

I dont know why but its now working.  Fortunately, I was committing to git as progress was being made and was able to go back in time and diffmerge my code... there wasn't any changes... it just started working.
I'm going to blame this on me forgetting to restart the packager after I started using the library.  Perhaps the reason I worked in iOS was because I fired up my test iPhone after I installed the library?  I don't know.  But if anyone else finds this, restart Expo or your RN packager and maybe you wont have this problem and waste half a day.
Thanks to those who made this library.... even with me being retarded this was still easier than dealing with it from scratch!


Save stack as template

Is your feature request related to a problem? Please describe.
Currently there is no ability to save stack files as templates.
Describe the solution you'd like
I would like to have the ability to save a stack that I've been working on as a template, and be able to update that template any time I make a change. As part of this I should be able to copy its yaml so that I can paste it into another swarm and change environment variables.
Additional context
This feature would require #3176 to be implemented to include any service level modifications, secrets, volumes, networks, etc. that are necessary to recreate this stack on another server.

Hi there @Daemach, can you please open a separate enhancement request for tab in App Templates that contains templates I create..
As separate enhancements should have separate issues.

Implemented via #3707
From a running stack you now have a new button

Excellent.  Thank you.
On Thu, Jul 23, 2020 at 9:49 PM itsconquest<EMAIL_ADDRESS>wrote:

Implemented via #3707 https://github.com/portainer/portainer/issues/3707
From a running stack you now have a new button
[image: image]
https://user-images.githubusercontent.com/12197793/88361591-a5b03600-cdcd-11ea-8ae3-1b81f58e553d.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/portainer/portainer/issues/3185#issuecomment-663345167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC7Y5YOIVUG5PSSEK6DTGCDR5EHHHANCNFSM4IY6SC3A
.

@itsconquest Is it correct that when creating a template from a stack the edited settings are not used. For example if I import a yml with restart policy always, and I change that setting in Portainer to Never, when I create a template from the stack the Web Editor shows the old value (restart policy always).


ConnectFirst Phone System sometimes not Updating/Creating Outbound Statuses.

Describe the bug
Seems that the Connect First phone system sometimes allows outbound calls to "slip by" without creating and or updating a status for the call.
This is leading to people redialing outbounds that have already been taken care of.
See video for more details:
https://crisiscleanup.slack.com/files/US0MGEX7X/F01CR629LQZ/screen_recording_2020-10-10_at_10.38.56_am.mov
To Reproduce
Unsure. Do not know how the CF system handles outbounds.
Additional context
This is coming from this slack conversation (with some redactions.)

Here is what we know:
1.) User who created the existing case is not using phone beta (by beta I mean AWS system)
2.) The Caller called IN twice, both times she was routed to the ring flow.
3.) The Caller WAS received by User who created the existing case, via the Ring system.
4.) It gets fuzzy here, because we dont get this data from ring, but from what I can tell, it looks like User who created the existing case created a case then added the note.
5.) There is NO existing dnis status for the call however, meaning the outbound completion never changed. I'm not sure when Ring system updates the status, but it never happened here.
6.) When YOU took the call, you completed the outbound and she will not called again. This is the only status that is associated with her DNIS.
So there is a problem here, but its with the Ring system. Not sure at which point that updates outbound status, but it never happened.

This was determined by the following queries (see here):
-- DNIS: ***** (**Caller** Dnis) Can see she HAS received 3 total calls.
SELECT * from phone_dnis WHERE dnis = ******;

-- Any statuses associated with Caller's DNIS (Only existing one is Ross's)
SELECT * from phone_dnis_statuses WHERE dnis_id = 148811;

-- Any events that have ****'s DNIS associated (only will show Ross's events b/c connect system)
SELECT * from event_events_log WHERE attr -> 'dnis' like '%*****' OR attr -> 'dnis1' like '%*****' ORDER BY created_at DESC

-- Can see that CALLER was routed to Ring both times and that she called in twice originally.
SELECT * from phone_outbound WHERE dnis1_id = 148811;
SELECT * from phone_inbound WHERE dnis_id = 148811;

-- Can that USER WHO CREATED EXISTING CASE has never created a DNIS status and is NOT using AWS system
SELECT * from user_users WHERE first_name like '***' and last_name like '***'
SELECT * from phone_dnis_statuses WHERE created_by = 22002
SELECT * from beta_features_users WHERE user_id = 22002

Old.


useLoader equivalent

useLoader is an important feature in R3F, it would be very useful here too.
Code:
https://github.com/pmndrs/react-three-fiber/blob/48f378fb3896dc0232c7bca117abb2b67c75f21c/packages/fiber/src/core/hooks.tsx#L88-L127

This needs documentation but each target has its own hooks export -- it's a bit more involved than R3F which can use a single signature.


Would be nice if a PortalEntry could self-contain it's own (always fullscreen) modal.

The current approach of using 2 sibling Widgets is not condusive to standalone components.
Commonly we want the same behavior for all ToolTips and inline popups which is a basic "showBarrier" and "barrierDismissable".
The current approach requires you to add an Extra PortalEntry to every single view that uses tooltips, and re-write the same logic over and over, or create some extra architectural layer to smooth out this pain pt. It also forces you to maintain multiple bools to track multiple popups, rather than just letting each popup encapsulate it's own state.
Would something like this be possible?
StatefulPortalEntry(
            key: tipKey,
            barrierColor: Colors.black.withOpacity(.1);
            barrierDismissable: false,
            childAnchor: Alignment.bottomLeft,
            portalAnchor: Alignment.topLeft,
            child: ...
...
tipKey.currentState.visible = true;

The basic goal is, if I have a component, that has some popup menu (Like UserAvatar), and I have it exist in various views, I don't have to constantly change the surrounding view to have the popover work. I want to be able to plop a UserAvatar in place, and it works, I don't think this is possible currently.

Another pain point is when you have a Widget of a certain size like "TitleBar" that is 40px tall, and has some internal component that spawns a popover. You can not put the barrier Portal in Titlebar, cause it doesn't occupy  the full height of the screen. Maintaining the Titlebars open state inside the parent makes no sense and is messy. You could turn your Titlebar into a fullscreen stack, but that doesn't read well in terms of layout or scale well with a lot of components.

Another pain point is when you have a Widget of a certain size like "TitleBar" that is 40px tall, and has some internal component that spawns a popover. You can not put the barrier Portal in Titlebar, cause it doesn't occupy  the full height of the screen. Maintaining the Titlebars open state inside the parent makes no sense and is messy. You could turn your Titlebar into a fullscreen stack, but that doesn't read well in terms of layout or scale well with a lot of components.

fwiw, I've started work on another approach that uses Notifications, I think it should turn out pretty cool.
At top of tree:
PopOverContext(child: ...)

Down the tree:
PopOverRegion(
  child: SomeButton();
  popChild: MyToolTip();
  anchor: Alignment.topRight,
  popAnchor: Alignment.topLeft,
  barrierDismissable: true,
  barrierColor: Colors.black.withOpacity(.05)
  mode: PopRegionMode.Hover,
)

Internally PopOverRegion just sends a ShowPopOverNotification up the tree, with a LayerLink and some settings.
Anyone can close the PopOvers anytime, by dispatching a ClosePopOverNotification. Which should make it really easy to have popovers can be shown from anywhere, and easily close themselves if they need.
Only describing in case it inspires some ideas. Cheers!

fwiw, I've started work on another approach that uses Notifications, I think it should turn out pretty cool.
At top of tree:
PopOverContext(child: ...)

Down the tree:
PopOverRegion(
  child: SomeButton();
  popChild: MyToolTip();
  anchor: Alignment.topRight,
  popAnchor: Alignment.topLeft,
  barrierDismissable: true,
  barrierColor: Colors.black.withOpacity(.05)
  mode: PopRegionMode.Hover,
)

Internally PopOverRegion just sends a ShowPopOverNotification up the tree, with a LayerLink and some settings.
Anyone can close the PopOvers anytime, by dispatching a ClosePopOverNotification. Which should make it really easy to have popovers can be shown from anywhere, and easily close themselves if they need.
Only describing in case it inspires some ideas. Cheers!

Sounds like this can be implemented without modifying the package code, such that the package can be minimal :) You approach seems quite good

Hi @fzyzcjy and @esDotDev Do we have a barrierDismissable in Flutter Portal?
If not, what is the best way to implement it? If we use anchor.filled we can give a transparent background however we can't position the opaque menu in the desired location

I personally create a second portaltarget with fullscreen transparent-black content

@fzyzcjy thanks for the quick reply. I tried the same solution and it works fine generally.
However, the full screen follower does not resize properly. When the browser window gets bigger, the full screen follower transparent-black background stays the same. (I am using anchor.filled)
Should I open a new issue for this or are you already aware of this problem?


SNP rsID

For things like germline polymorphisms, it would be good to have a field to put the rsID.

Agreed. For now we have been including it in the text of the evidence statement or as the actual variant name in at least one case.

Maybe it could be displayed as a parenthetical after the variant origin? Otherwise we will be adding another display field that will >90% of the time be NA.
Also, should we allow a comma-separated list?

I suppose we could see about linking out to dbSNP. Pulling in MAF information would be awesome but add another level of complication. If we did have another field I'd propose it goes after the Drug field. At least then we'd have 5 fields on each side.

It's not a problem for me to add this field to the forms and views, @acoffman just needs to add it on the server.

I wonder if we should create a special field for RSID or simply implement the variant synonym concept and use that to store this and many other things.  RSID is one of many IDs that we might want to associate with a variant...

Also we would get this info for free by interfacing with MyVariantInfo, along with a lot of other useful info...

I believe following issue is a more generic solution to this problem that will allow us to benefit from the efforts of the MyVariantInfo team and get RSID along with a ton of other great stuff.
https://github.com/genome/civic-server/issues/171
Unless there are objections we can probably close this one.


Version 291

Can we please capitalize the first letter of the commit message (assuming it does not name a type)?


Add ability for Advantage/Disadvantage Rolls

In GitLab by @mdonovan.nmkac on Apr 6, 2021, 15:45
Summary
In "Legacy Life among the ruins" they have an advantage/disadvantage system that uses roll 3d6 and you pick the two highest/lowest dice. So it would be good if there was a way a: to have alternate dice roll types and b: to be able to select that when you roll.
So
Normal roll 2d6+STAT
Disadvantage lowest(3d6)+STAT
Advantage highest(3d6)+STAT
Labels (do-not-change)
/cc @Asacolips

In GitLab by @Asacolips on May 26, 2021, 07:59
I think this one may be covered by #8, but I'll keep this one open for now until I've progressed farther on that issue. Thanks for reporting this!

In GitLab by @Asacolips on Jul 19, 2021, 08:19
Added support for this in release 0.3.0


Uncaught Invalid string interpolation at 1648

[Enter steps to reproduce below:]

...
...

Atom Version: 1.7.3
System: Mac OS X 10.11.5
Thrown From: Atom Core
Stack Trace
Uncaught Invalid string interpolation at 1648
At /Applications/Atom.app/Contents/Resources/app.asar/node_modules/text-buffer/lib/text-buffer.js:833

undefined

Commands
     -0:27.6.0 snippets:previous-tab-stop (atom-text-editor.editor.is-focused)
     -0:27.6.0 editor:outdent-selected-rows (atom-text-editor.editor.is-focused)
     -0:27.5.0 snippets:previous-tab-stop (atom-text-editor.editor.is-focused)
     -0:27.5.0 editor:outdent-selected-rows (atom-text-editor.editor.is-focused)
     -0:26.2.0 emmet:expand-abbreviation-with-tab (atom-text-editor.editor.is-focused)
     -0:26.2.0 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -0:26.2.0 snippets:expand (atom-text-editor.editor.is-focused)
     -0:26.2.0 editor:indent (atom-text-editor.editor.is-focused)
     -0:26 emmet:expand-abbreviation-with-tab (atom-text-editor.editor.is-focused)
     -0:26 snippets:next-tab-stop (atom-text-editor.editor.is-focused)
     -0:26 snippets:expand (atom-text-editor.editor.is-focused)
     -0:26 editor:indent (atom-text-editor.editor.is-focused)
     -0:23.3.0 core:save (atom-text-editor.editor.is-focused)
     -0:08.2.0 emmet:expand-abbreviation-with-tab (atom-text-editor.editor.is-focused)
     -0:01.6.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:00.8.0 emmet:expand-abbreviation-with-tab (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "ignoredNames": [
      ".DS_Store",
      "Icon"
    ]
  },
  "editor": {
    "backUpBeforeSaving": true,
    "fontSize": 9,
    "invisibles": {},
    "showIndentGuide": true
  }
}

Installed Packages
# User
atom-alignment, v0.12.1
atom-beautify, v0.29.7
color-picker, v2.1.1
emmet, v2.4.3
jshint, v1.8.5
less-than-slash, v0.13.0
linter, v1.11.4
linter-csslint, v1.3.2
linter-htmlhint, vundefined
minimap, v4.23.2
seti-icons, v0.4.5
wordpress-api, v1.2.2

# Dev
No dev packages

Based on the command history this seems to be a problem with Emmet - please report this exception over there.  Thanks!


Add Portfolio File

Pull Request Test Coverage Report for Build 234

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 64.939%

Totals

Change from base Build 233:
0.0%

Covered Lines:
1954

Relevant Lines:
3009

💛  - Coveralls


usability of x509 lookup api or switch to store2

I just push an update of X.509 LOOKUP "By LDAP" based on new API - https://gitlab.com/secsh/pkixssh/commit/bdd223e3cedb3c270bd62b04a7fb45a326a2b3ef
Most of code could be ported except 2 points
(1) typedef int (*X509_LOOKUP_get_by_subject_fn)(X509_LOOKUP *ctx,
X509_LOOKUP_TYPE type,
X509_NAME *name,
X509_OBJECT *ret);
This type def uses enumerate instead integer  as in OpenSSL < 1.1. The size of enumerate is not defined exactly and under some condition it may differ from integer type.
This is binary incompatible modification.
(2) X.509 lookup method perform copy of data between objects - see https://github.com/openssl/openssl/blob/86ed2e1cb04158371385047e0e7832c34273022c/crypto/x509/by_dir.c#L375
The same code is in "By LDAP: - https://gitlab.com/secsh/pkixssh/blob/x509lookup/x509_by_ldap.c#L1059 .
There is no way to perform update of return argument X509_OBJECT *ret.
(3) looking - see https://github.com/openssl/openssl/blob/86ed2e1cb04158371385047e0e7832c34273022c/crypto/x509/by_dir.c#L330
I think that lock should be on X.509 store itself , i.e. on "xl->store_ctx" instead on "ctx"
I'm not convinced and new api is so good.
OpenSSL store2 functionality if good point to write only fetch path of get_by_subject "callback". The management of X.509 store, i.e. add/lock/check and etc is OpenSSL responsibility and application should not know anything about internal structural management of X.509 store.

This looks like three different issues put together into one.  Would you mind splitting the cases apart?

Richard Levitte wrote:

This looks like three different issues put together into one.  Would you mind splitting the cases apart?

As the practice is new issue to be opened to correct something in an
user report this will be split.
I wonder how to proceed.
Perhaps only p.3 (lock of x.509 store cache) could be fixed . It look
like regression perhaps with origin in  1.1.0 branch.
Use of enumerate as part of p.1 perhaps is not limited to X.509 lookup.
There is other public API methods with arguments from enumerated type.
Regards,
Roumen Petrov

I just commit "experimental X.509 lookup based on LDAP store" to a new PKIX-SSH branch ( https://gitlab.com/secsh/pkixssh/tree/ldapstore ).
It seems to me use of STORE-API in X.509 lookup is quite simple.
Implementation require one extra functionality - additional constraint to restrict results by X509_NAME according specified lookup type.
Methods "by dir" (1) and "by ldap" (2) are quite similar.
Argument url for OSSL_STORE_open() is "ldap base dn" specified when to lookup method is initialized  In case of "by dir" is should be directory.
Before to loop on store results I decided to use control method to pass "extra constrain". For "ldap" I decided to reuse function with "filter" instead to construct enhanced "ldap url". For "by dir" such functionality it could be used to construct "file name glob pattern" either . or .r.
Let me know how to proceed with further evolution of STORE-API in context X.509 lookups.
Regards,
Roumen Petrov

I have started on a branch that implements by_store, i.e. a X509_STORE_LOOKUP that relies entirely on OSSL_STORE.  Haven't made a PR from it yet, and have been distracted by Other Stuff.  Would that be interesting for you?  You would basically feed it any appropriate URI, and be able to extract the desired type of object.

Hi Levitte,
I guess that you mean branch store2+x509store-store2-integation-radical from yours "store2".
At first look it is more like load all from all specified "location". This is similar to exiting by_file. Another way is by_dir or by_ldap that loads only required items.
To load all I don't need modification to existing code neither X.509 lookup method - at application start I could fetch all cert/crl from external base and to push them to "X.508 store" using "add" functions.
My be I misunderstand proposed modification or I review wrong branch.

I guess that you mean branch store2+x509store-store2-integation-radical from yours "store2".

Nope.  Like I said, I haven't published the branch I'm talking about yet.  What I done is to create a separate X509_LOOKUP_METHOD that takes a URI as location instead of a file or directory name.  It also doesn't do the immediate load of everything like by_dir and by_file do.

#8442 contains what I'm talking about

Richard Levitte wrote:

#8442 contains what I'm talking about

Ok . Soon I will look in more details proposed modification.
I need more time  to enhance "ldap" to use new OpenSSL STORE2 lookup .
Please note that push to "X.509 store" increase up object reference.
new OSSL_STORE_INFO		=> 1
..._get1_CERT/CRL			=> 2
free OSSL_STORE_INFO 		=> 1
X509_STORE_add_cert/crl		=> 2
, i.e. store2 leaks memory.
This is reason in my implementation to use loop like
store_info = OSSL_STORE_load
(*)   ldaplookup_data2store
OSSL_STORE_INFO_free(store_info);
, where data2store performs ..get0_CERT+  X509_STORE_add_cert() and
respective for CRL.
(just pushed fix for CRL in my experimental implementation)
Regards,
Roumen Petrov

Ah, thanks!  Will fix

For protocol "ldap" is rewritten as standalone C-file - engine that provides limited store functionality, but enough for use by x.509 lookup.

After review again by_dir and "lu" I think that x509 lookup api could be used with small correction in call method . Currently X509_STORE_CTX_get_by_subject under condition call X509_LOOKUP_by_subject (wraps x509 lookup  method by_subject) and check result.
So what if instead to check X509_LOOKUP_by_subject to consider invocation of function always as successful(1), to ignore "ret"(2) argument and to fetch(3) again object from X5O9_STORE.
Remark:  by_dir is prepare return from X5O9_STORE entry, so idea is do (3) in caller.
Something like :-1:
...
X509_LOOKUP_by_subject(lu, type, name, &stmp);
tmp = X509_OBJECT_retrieve_by_subject(ctx->objs, type, name);
if (tmp != NULL) break;
...
Benefit :

does not require additional methods;
it is save to back port as does not change reference counters at all (fixes #8707 instead of #8708);
does not require modifications in existing methods.

For what you want, the functions get_by_* are simply not sane, they give the wrong idea. For what you want, the lookup method should simply have a load functions that loads everything it can get into the X509_STORE, because that's essentially what you're asking for.

Richard Levitte wrote:

For what you want, the functions get_by_* are simply not sane, they give the wrong idea.

I did not understand you comment.
Prototype of get_by_subject is historic, public before 1.1 and perhaps
this could explain why is not changed in the past and why by_dir is
implemented like that.
Other get_by_* are never used by X509_STORE  so I cannot see a reason to
implement any of them.

For what you want, the lookup method should simply have a load functions that loads everything it can get into the X509_STORE, because that's essentially what you're asking for.

This is idea to use store2 api . External application to provide
everything need by X509_STORE without to manage data into X509_STORE.
Idea is not only to make X.509 method and related  opaque but to make
X509_STORE functionality encapsulated into library ( blackbox ). This
eliminated needs for x.509 lookup method, management of X509_STORE
entries  and etc, minimized public API.
Minimization of API (without X.509 lookup  ) will allow in future
versions (4.0?) optimization of X509_STORE and minimization of all those
extra updates of reference counters (New/Up/Free).

The idea with the by_store implementation is mostly to get a smooth transition. I have other alternatives too...

Richard Levitte wrote:

The idea with the by_store implementation is mostly to get a smooth transition. I have other alternatives too...

Agreed. If third party is responsible only to provide cert, crl or
key(*) alternative is fine.
(*) +sign/verify and etc. key operations if private part is protected.

PKIX-SSH branch "x509lookup" is replaced with new one. Now it contain following commits:

TESTING: X509_LOOKUP_METHOD accessor methods for compatibility with OpenSSL 1.1.1 API (updated to take into account  changes in PKIX-SSH 12.0 release);
TESTING: X509_LOOKUP_METHOD work-around over missing X509_OBJECT copy functionality: same as before X509_OBJECT accessors, but by_ldap initialize return argument using set1/free methods.

What is visible (build with OpenSSL 1.0.2 stable).
With my internal test application valgrind reports "in use at exit: 18,953 bytes in 71 blocks".
Main part is due to ldap and sasl initialization.
Above  could be minimized with call of sasl_done() at shutdown. After this valgrind report is "in use at exit: 149 bytes in 3 blocks".
First block (32 bytes in 1 blocks are still reachable in loss record 1 of 3) is from _sasl_get_plugin. Leak loop like error in ldap sasl "deinitialization".
Second (37 bytes in 1 blocks are still reachable in loss record 2 of 3) and third (80 bytes in 1 blocks are still reachable in loss record 3 of 3) are from X509_LOOKUP initialization - allocation of X509_LOOKUP_METHOD structure and name of method.
Unfortunately this cannot be fixed at all. Lookup is added to X509_STORE and there is no method to exclude it. Due to this application cannot call X509_LOOKUP_meth_free safely. Some hazard application could use ;).
Next valgrind report is error "Conditional jump or move depends on uninitialised value(s)".
Since decades by_subject method uses :
(1)            ret->type = tmp->type;
(2)            memcpy(&ret->data, &tmp->data, sizeof(ret->data));
to initialize "ret" argument of callback "by_subject", where tmp (a X509_OBJECT) is extracted from X509_STORE.
Let review one of set1 methods - X509_OBJECT_set1_X509. It call x509_object_free_internal where is
code like "switch (a->type)".
Note due to historic initialization in (1) there is no need X509_STORE{_CTX}_get_by_subject to initialize X509_OBJECT argument when is called callback "by_subject".
Remark: Since #8673 get_by_subject  caller in OpenSSL code initializes passed argument.
Problem with this initialization is that third part application cannot decide witch methodology to use  old "memcpy based" or "set1/free" - first one is save for all OpenSSLL releases (including vendor ones), while use of second is save only with next major release (functions from version @OPENSSL_3.0.0).
In addition X509_LOOKUP_by_subject is part of public API and is not clear how is used outside OpenSSL code!
So neither set1/free nor ignoring "ret" argument ( https://github.com/openssl/openssl/issues/6970#issuecomment-482816938 ) is usable.
I start to think that deprecation of X.509 lookup related API is not enough. This includes all X509_LOOKUP_* including those related to opaques structure (X509_LOOKUP_METHOD* and X509_OBJECT* from 1.1.0i+ API).
Look like removal of such API from public headers is preferred solution.
Lets see how improve (temporary) current situation in 1.1* release (documentation #8755 or back-port of store based lookup  #8442).

while use of second is save only with next major release (functions from version @OPENSSL_3.0.0).

That's incorrect, that method should be usable with OpenSSL 1.1.0 and on.

My point on symbol versions was different. Let function foo is from library version "abc" with symbol version xyz. Its internal implementation is changed in incompatible way. New version library is is "abd" but symbol version of foo() remain "xyz".
User build his software with lib-version "abd" and relies on foo() as is in implemented in this version.
What is problem here? As foo() is with symbol version xzy user program could be run with library version "abc". Loader allow this!
=====
Note that during tests I use "debug" builds. According my knowledge such builds zero data segments.
Let review X509_OBJECT_set1_... function. It look like this :
...
switch (o->type) {  /*<--- Note this */
case X509_LU_X509: X509_free(o->data.x509); break;
...
o->type = X509_LU_X509;
o->data.x509 = x;
...
In previous comment (build with 1.0.2) uninitialized value is on line switch (o->type). Due to debug build is expected memory of 'o->type' to contain zeroes. As result o->type is integer value 0, i.e. X509_LU_NONE, i.e. code will not call "free" methods. More over is expected memory of o->data.x509 to contain bytes fill with zero.
In release build situation is different. Memory has random data, i.e. is expected to crash.
=====
Historically (two decades) lookup method relies on initialization of memory (object) in lookup method.
It is from Ralf S. Engelschall SSLeay code:
...
/* we have added it to the cache so now pull
* it out again */
CRYPTO_r_lock(CRYPTO_LOCK_X509_STORE);
tmp=(X509_OBJECT *)lh_retrieve(xl->store_ctx->certs,
(char *)&stmp);
CRYPTO_r_unlock(CRYPTO_LOCK_X509_STORE);
	if (tmp != NULL)
		{
		ok=1;
		ret->type=tmp->type;
		ret->data.x509=tmp->data.x509;
/*		CRYPTO_add(&tmp->data.x509->references,1,
			CRYPTO_LOCK_X509);*/
		goto finish;
		}
	}

....
So I cannot understand neither documentation nor fix for non existent(fake) defect like #8673.

So if I understand correctly, what you're saying is that X509_OBJECT_set1_X509() should not try to free what may already be there, and leave it to the lookup method to do things right (i.e. only assign the X509_OBJECT it has a pointer to once).
Trouble is, that's the semantics of X509_OBJECT_set1_X509() at this point, and has been since 1.1.0.

Richard Levitte wrote:

So if I understand correctly, what you're saying is that X509_OBJECT_set1_X509() should not try to free what may already be there, and leave it to the lookup method to do things right (i.e. only assign the X509_OBJECT it has a pointer to once).
Trouble is, that's the semantics of X509_OBJECT_set1_X509() at this point, and has been since 1.1.0.

I have no idea why is added method like this. It is not since 1.1.0. It
is since 1.1.0i and I'm not sure that I understand OpenSSL rules for
back-port of new functionality.
Perhaps author do mechanical "transformation" of another API to
X509_OBJECT model.
May be set1 function could be used somewhere.
It is not good for "by_subject" lookup method.
Roumen

Someone said that we probably need set0 functions. All things considered, that seems like the right move.

Attempt to use broken API still continue - now in look-up by store (issue #8442) .Crash is permanent.

Does this problem apply to both 1.1.1 and current master branches? It is unclear to me whether this is some API semantic difference between 1.0.2 and 1.1.x branches. If so, I am afraid we will have to live with that unless it is possible to fix it without breaking things that accommodated the 1.1.x way.

Hi Tomáš (@t8m),
X509_LOOKUP functionality is needless for master.
I'm not surre why this issue is marked as bug.

Unfortunately this issue is mixing multiple things and it is now completely unclear to me if there is anything to resolve for this issue on the master branch. If not and the X509_LOOKUP_store is good enough, I'd just close this.

Tomáš Mráz wrote:

Unfortunately this issue is mixing multiple things and it is now completely unclear to me if there is anything to resolve for this issue on the master branch. If not and the X509_LOOKUP_store is good enough, I'd just close this.

It is request to deprecate extra LOOKUP as public functions. OpenSSL could use them internally.

Ah, you mean to deprecate all the public X509_LOOKUP_* functions with the replacement being the OSSL_STORE API? @levitte what do you think about that?

I do not think we are going to do any more deprecations before releasing 3.0.

Marking as inactive, to be closed at the end of 3.4 dev barring further input


Containers "remember" last active child

With Tree Paths finally merged in, containers now have the necessary information to determine which container was last active. This means switching focus will feel much more natural, as switching between different views that are children of container (or between different workspaces) will go the last active one.

"Go to last workspace" is a pretty standard Awesome feature (that I don't use) - is that possible to implement with the current way paths are implemented?

Hmm, right now currently no unfortunately. What the paths do is simply allow us to follow the current "active path". Once a path is no longer active, it is deactivated with no additional metadata about when it was last active. Active edges beneath that may still be active, but it won't be part of the main path. To be able to implement that feature something else will need to be done with paths. I'd like to keep the "active" as a simple binary flag but something else could be worked out so that we have a better history of actions.


Another strategy was already registered.

Hi,
I'm using Spring Cloud Sleuth to track the calls. So, Sleuth registers the default MetricsPublisher.
When HystrixPrometheusMetricsPublisher is tries to register with HystrixPlugins throws "Another strategy was already registered." error.

If this is still an issue, please follow up in the https://github.com/ahus1/prometheus-hystrix repo (which is the maintained fork of this repo).

New maintainer on board, and the repo has been moved. No need to open a new ticket.
I know about this problem and have a working solution in mind.

Thanks @ahus1

I wrote a test case to reproduce the error and adopted the same strategy Sleuth applies: to wrap any existing provider.
Please give it a try and provide feedback. Maybe you also want to look into #4 as it will be part of the next release.
To try it out you can use the 3.2.0-SNAPSHOT release available from Sonartype OSS repo (more on that on the main README.adoc in the repo).

This has now been released as 3.2.0 on maven central.

Thanks @ahus1 for fixing this issue. The code looks fine and working without any issue.
On the another note, is someone updating the Grafana Dashboard based on the new changes
Grafana Hystrix Dashboard

@pradyb - good to hear that it is working for you.
I wasn't aware of this dashboard. For now the old metrics should work as before.
Maybe @sergiu-svinarciuc can help here? As he has uploaded it, he has the permissions to update it.


FR: Set first day of week

My country first day of week is Monday. Can you create a feature that users can set different first day of week

Hi, I have updated the plugin and it is now possible to change between "Monday" and "Sunday" as the first day of the week. https://github.com/karstenpedersen/obsidian-daily-note-navbar/releases/tag/0.1.4


MekExtra Bug with AE2

If stored SiF4 liquid less than 1000mb, trying to place it in the world using "ME Formation Plane" will cause liquid disappear.
(minecraft 1.20.1, with forge 47.3.0, ae2 15.2.13, mek 10.4.9, extra 1.3.2)

I will not disappear when I connect the interface to the panel, you can specify your own.


📑 Feature Request: Adding recent searches

IMPORTANT TO CHECK BEFORE ISSUE

[X] You check that same issue is not present in the repository
[X] You have read contribution guidelines and rules

Please describe your feature request related to a problem?
Users often perform repetitive searches for repositories and issues on GitHub, especially when tracking multiple projects or frequently revisiting the same resources. Currently, there is no way to quickly revisit previous searches in Git-trace.
Describe your solution to problem
Implement a Recent Searches feature that automatically saves and displays the user’s most recent search queries. This would allow users to quickly reuse previous searches without needing to re-enter the search terms manually.
Describe alternatives you have considered
No response
Additional context
No response
Add Relevant Screenshot (if available)
No response

Can you also add the gssoc-ext


GitHub.io vNext plan for docs

Currently we have one pipline that runs on a repo and generates all of the refdocs on github.io in one shot.  We had to disable that automatically running because the docs were drifting "foward" beyond what had been released to the public feeds.
Goals of this Epic

[x] Every time a library is released we update the refdocs for that library
[x] This doc generation step should be a stage in the unified pipelines
[x] [new] store multiple versions of the docs for previously released libraries
[x] [new] Only have the index of all libraries on github.io and store the specific library ref docs in blob storage
[x] [new] Generate docs as part of PR Validation or nightly builds for developers to review (if we move this to blob storage, it becomes trivial)

Closing this epic since we are done with our primary goals.  I've moved all "additional" issues into other epics or created new epics to track them.  This is done.


refactor(registry): extract and rearrange items to their own modules

What does this PR try to resolve?
A refactor moving things to their own new modules.
How should we test and review this PR?
Commit by commit.
The PR just moves things around. I know it's a bit painful to see this kinda of change but to have a better module hierarchy we need to do it now or later.
Additional information
This was done during coping with todos of asymmetric tokens #10519.

This is ready for a new round of review. Please call out if there is something inappropriate.

@bors r+

:pushpin: Commit aaf02211c658bf43fcb40fcc5bb2839fcb4c3039 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit aaf02211c658bf43fcb40fcc5bb2839fcb4c3039 with merge 5febbe5587b74108165f748e79a4f8badbdf5e0e...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 5febbe5587b74108165f748e79a4f8badbdf5e0e to master...


Add REVISED_JULIAN_CALENDAR calendar

Proposed change

Add REVISED_JULIAN_CALENDAR calendar constant (close #1378).
Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[x] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[ ] Dependency update (version deprecation/upgrade)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good: make pre-commit
[x] All tests pass locally: make test, make tox (we strongly encourage adding tests to your code)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

coverage: 100.0%. remained the same when pulling aa4c018da7d730fb0ecf0324c3429a704a607f7f on KJhellico:add-revised-julian-calendar into 12768a61ee6b637646800b20f95ddd5dbbcab401 on dr-prodigy:beta.

It's based on commonly used name, but it doesn't really matter . I've seen someone use MILANKOVIC for similar constant name. :)

It's based on commonly used name, but it doesn't really matter. I've seen someone use MILANKOVIC for similar constant name. :)

Yeah, I saw the origin details, just want to keep it closer to julian_. Let's rename it?


Improve performance of reconnectOrphanedNodes

reconnectOrphanedNodes's ability to produce connected graphs was improved by #335. One change in particular produces a performance regression when reconnecting large (1M+ node graphs) with a sizeable partitioning (e.g., only ~600K nodes are reachable from the entry point, meaning 400k nodes need to be reconnected).
The change is as follows:
Exclude connectionTargets when searching for new connection points. If all of a node's existing neighbors have been considered and a search is performed, it is not unusual to see that the existing neighbors are many of the search results. This is particularly important if approach 2 is used, as connection targets will grow across loop iterations.

This works very well when a small number of nodes need to be reconnected, as the set of connection targets is small. When it's large, like when reconnecting 400k nodes, the performance of the searches is extremely poor.
This PR proposes several changes:

Limit neighbors used as connection targets to nodes connected at the start of the loop iteration. Testing the current reconnection behavior for graphs with large numbers of disconnected nodes showed that the neighbor reconnection has a tendency to connect to nodes already in the partition. This change improves the effectiveness of neighbor reconnection.
Instead of using excludeBits, use resumable searches and post-filter results based on connection targets. This removes the performance hit of connection targets. The threshold of 50 resumes was decided by a basic histogram analysis of the number of resumes needed. Past this point, we see diminishing returns.
Increase reconnect loops. The previous decrease from 5 to 3 is no longer appropriate to see highly effective restoration of connectivity on large, partitioned graphs.
Introduce slf4j-api for basic debug logging. java.util.logging bridged to other logging frameworks via slf4j has some performance concerns. This seemed like the appropriate way to bridge logging to the broader ecosystem.

Looks good overall.
I'm not sure about switching from excludebits to search/resume, especially since we end up with code that uses both.  Here's my attempt to make excludebits less painful.

Try without the backlinking?

Okay, I added back the split search.  It retains most of the simplicity I think.
If it's still slow then again I blame backlink. :)

(I changed the 50 to 2*degree so that it doesn't break down in the corner case with larger degree, since I left out the excludebits for neighbors as well.)

okay, what's your preferred version at this point?

LGTM
nit: can we combine the two connectToClosestNeighbors by passing Bits.ALL as connectedNodes to the four-parameter version?


[Typescript-Angular] Generate client code with rxjs for Angular6+

Feature Request
The client code generated for typescript-angular uses old version of rxjs which is not supported in Angular6+ projects. To make it work you have to manually install rxjs-compat package with npm: npm install rxjs-compat.
Describe the solution you'd like
Generate the client code with the latest versions of rxjs for Angular6+.
Additional context
Find attached the api definition in yml:
openapi.zip
Code generated with Swagger Hub:
typescript-angular-client-generated.zip
Error in ng build:
BUILD ERROR
diary-shit-client-lib/src/lib/api/diary.service.ts(229,1): error TS1005: '}' expected.
../node_modules/rxjs/Observable.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Observable'.
diary-shit-client-lib/src/lib/api/diary.service.ts(19,10): error TS2305: Module '"D:/DANI/vscode/dairy-shit-libs/node_modules/rxjs/Observable"' has no exported member 'Observable'.

Error: diary-shit-client-lib/src/lib/api/diary.service.ts(229,1): error TS1005: '}' expected.
../node_modules/rxjs/Observable.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Observable'.
diary-shit-client-lib/src/lib/api/diary.service.ts(19,10): error TS2305: Module '"D:/DANI/vscode/dairy-shit-libs/node_modules/rxjs/Observable"' has no exported member 'Observable'.

    at Object.<anonymous> (D:\DANI\vscode\dairy-shit-libs\node_modules\ng-packagr\lib\ngc\compile-source-files.js:65:19)
    at Generator.next (<anonymous>)
    at fulfilled (D:\DANI\vscode\dairy-shit-libs\node_modules\ng-packagr\lib\ngc\compile-source-files.js:4:58)
    at <anonymous>

diary-shit-client-lib/src/lib/api/diary.service.ts(229,1): error TS1005: '}' expected.
../node_modules/rxjs/Observable.d.ts(1,15): error TS2307: Cannot find module 'rxjs-compat/Observable'.
diary-shit-client-lib/src/lib/api/diary.service.ts(19,10): error TS2305: Module '"D:/DANI/vscode/dairy-shit-libs/node_modules/rxjs/Observable"' has no exported member 'Observable'.

Apologies, I have created in this repo by error. I close it, please delete.


(Pending) Example of adding network services init functionality to mininet hosts

... of adding network services (DHCP, DNS, ...) on host processes
Project description:
The intent of this project is to add a simplified analog of systemVinit
functionality
to mininet hosts.
Rationale:
Mininet is an advanced IP networks research and modeling tool capable to
model
large networks with complicated topology. Yet networked computers often
run
various network oriented services. The modeling of the behavior of the
mentioned
services could be also of great a interest for research. Still mininet
lack standard
capability to launch even very basic sets of network daemons on network
start.
What is necessary:
To run this example one needs to put mn-services.py into
mininet/examples
directory. Also dhcpd and dhclient programs expected to be present in
system
(tested with isc-dhcp-server and isc-dhcp-client  of 4.1.ESV-R4-0ubuntu5
version)
Proposed dhcpd.mininet.conf ought to be placed in /etc/dhcp/ .
What will happen:
After launch the virtual network will be created with s0 as a central
switch and
s1 -- s3 as a leaf switches with two nodes each h1 -- h6. Aslo hs0 node
will be
attached to s0. DHCP daem will be launched on hs0 and dhclient program
on
h1--h6.
How it works:
File mn-services.py is a quite superficial modification of mn mininet
launcher.
In current example a derivative class wrpMininet:Mininet created. It
wraps start()
and stop() functions. Also it adds some services related functions which
are
necessary to describe services, launch them and shutdown (in future, now
shutdown is practically useless).
What could be done:
Current example structure assumes no modification of mininet core
classes. Yet,
some functions are difficult to implement using wrapper classes. F.e. it
is difficult
through wrapper class to prevent host from getting any IP on startup, or
modify
exec functions in way to that allows to obtain PID, process GID, etc
which could
be of serious assistance for correct services shutdown implementation.

To respond to your comment regarding the node library, it's documented in the Python API documentation for nodelib.py. I think the right approach for customizing nodes is simply to subclass Host or Node and to specify the cls of the node in the topology.

Thanks again for your code and suggestions.


Watcher is not reflecting changes

Im running Shopware 6 in docker. However when i run the watcher in my pod using:
application@ba3e3eeff9da:/app$ ./psh.phar administration:watch
Then the changes are not reflecting when i open the webpage via my host system at http://localhost:8000/admin

Found the solution also that the watcher is running a new service update at 8080 instead of 8000.
Maybe we should add it more clear in the docs?

Hi @pimjansen, we'll consider if this has to be more documented.
but in the console after ./psh.phar administration:watch the output as well tells you where to finde it and provides a link
Since you resolved your issue i'll close this ticket then :)


Skip test until https://github.com/jaegertracing/jaeger/…

…issues/1468 is fixed
Signed-off-by: Kevin Earls<EMAIL_ADDRESS>

@objectiser Please review


readme: remove too generic users

These domain either nxdomain/404 or just generic sites selling some
service.
Remove them from the readme.

Codecov Report

Merging #1164 into master will increase coverage by 0.23%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1164      +/-   ##
==========================================
+ Coverage   55.56%   55.79%   +0.23%
==========================================
  Files          41       41
  Lines       10124     9517     -607
==========================================
- Hits         5625     5310     -315
+ Misses       3476     3196     -280
+ Partials     1023     1011      -12

Impacted Files
Coverage Δ

update.go
58.97% <0.00%> (-12.96%)
:arrow_down:

duplicate.go
28.57% <0.00%> (-8.93%)
:arrow_down:

serve_mux.go
70.27% <0.00%> (-5.29%)
:arrow_down:

listen_go111.go
73.33% <0.00%> (-4.45%)
:arrow_down:

zmsg.go
36.15% <0.00%> (-3.88%)
:arrow_down:

acceptfunc.go
42.85% <0.00%> (-3.81%)
:arrow_down:

msg.go
73.80% <0.00%> (-3.41%)
:arrow_down:

xfr.go
29.45% <0.00%> (-3.17%)
:arrow_down:

dnssec_keygen.go
61.25% <0.00%> (-2.71%)
:arrow_down:

msg_helpers.go
65.43% <0.00%> (-2.59%)
:arrow_down:

... and 31 more

Continue to review full report at Codecov.

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


when my internet is slow, the 'nothing here yet' shows before any blocks begin to load

Closing, I believe this is fixed.


METRON-37: Configure Cobertura Plugin to Aggregate

Merged with current master and linked to JIRA.

As promised, +1 to this.


DotNet is undefined in ContentScript / Razor page

Hello,
I am developing a browser extension with Blazor using your very nice package and template.
I cannot figure out how to call a .Net method from JavaScript. It should work using the "DotNet" object defined as a global variable by Blazor WASM, but the variable remains undefined. So for some reason, Blazor isn't fully working, although I can call JS from a .Net method successfully.
Here is my manifest v3:
{
  "manifest_version": 3,
  "name": "PUBROWSE Extension",
  "description": "Hooks into PU market data and suggests good trades.",
  "version": "0.1",
  "background": {
    "scripts": [ "BackgroundWorker.js" ],
    "type": "module"
  },
  "action": {
    "default_popup": "popup.html"
  },
  "options_ui": {
    "page": "options.html",
    "open_in_tab": true
  },
  "permissions": [ "storage", "scripting", "tabs", "debugger", "activeTab" ],
  "host_permissions": [
    "http://*/*",
    "https://*/*"
  ],
  "content_scripts": [
    {
      "matches": [ "*://*/*" ],
      "js": [ "content/Blazor.BrowserExtension/ContentScript.js", "scripts/MainComponent.js", "scripts/Startup.js" ],
      "css": [ "PUBROWSE.styles.css" ]
    }
  ],
  "content_security_policy": {
    "extension_pages": "script-src 'self' 'wasm-unsafe-eval'; object-src 'self'"
  },
  "web_accessible_resources": [
    {
      "resources": [
        "framework/*",
        "content/*",
        "app.js"
      ],

      "matches": [ "<all_urls>" ]
    }
  ]
}

And the ContentScript Startup.js:
console.log("Startup.js called");
console.log("Is DotNet defined:")
console.log(DotNet)

This results in the error "ReferenceError: DotNet is not defined" in FireFox.
I have also tried it from a Razor component via a button click:
 <div>
     <button onclick="console.log(DotNet)">Test</button>
 </div>

Also not working.
Could you please provide me with some insight?

I believe the Startup.js is ran before DotNet is defined. As for the button click I think the JavaScript is executed in the page's context instead of the content script context.
You can use app.js and call import() in the afterStarted lifecycle.

Thanks for your answer!
I have checked app.js and found out that the DotNet object is available there, so no import() was neccessary.
The question is: why is is not available in other JS files / in my ContentScripts?
What would I have to import exactly to make the Blazor runtime available for JavaScript files?

JavaScript libraries are executed immediately when they are loaded, which is before the DotNet library is executed. Basically the other libraries relying on DotNet should be delayed in their execution by importing them after DotNet is available, instead of declared in the manifest as a content script.

Hmmm, but the button click in the Razor component comes way after initialisation.
Do you maybe have a working code example where the DotNet object is actually used?

The onclick that you have in your Razor code is likely running in the page's context instead of content script context. Instead of using inline onclick, you can either use Blazor's @onclick or attach event handler in JavaScript.
For more information on this, you can read up on the Work in isolated worlds section.
Quoting from the note

Note: Not only does each extension run in its own isolated world, but content scripts and the web page do too. This means that none of these (web page, content scripts, and any running extensions) can access the context and variables of the others.

Thank you, that set me on the right track!
The problem was indeed that razor components are isolated from ContentScripts (and background scripts).
So a way to communicate between these party was neccessary, I use window.postMessage() to send messages from the ContentScript and receive them with window.addEventListener(...)  in the component.

The Blazor components actually execute in the Content Scripts context, it's only the inline JavaScript that you inject into the page gets executed in the page's context.
For communications between the different contexts of an extension, you can refer to the newly added Messaging sample.


[BUG] DivingRPG & GD Causing Lag

Versions
Spigot/Paper/Sponge: Mohist 1.12.2-230
GriefDefender: 1.5.11 (also happened in previous versions)
LuckPerms: 5.3.51

Describe the bug

When having DivineRPG Mod (v1.7.1 and older) and GriefDefender on the server, it will spam errors in the console and whatever error it is running into is causing the server to lag and/or DivineRPG worlds to generate very slowly.
Couple errors in console:
https://paste.helpch.at/tojunufebe.rb
https://paste.helpch.at/wamijiquxe.sql

Steps to reproduce the behavior

Start Mohist (or other Hybrid like Magma) with the mod DivineRPG and GriefDefender.

Expected behavior

I expected the server to not have the current error out and for the server to not lag.

GDDEBUG

Short debug before server started lagging.

Screenshots

The stack trace isn't complete. Please provide a complete stack trace from actual server log.

Performance was greatly improved in latest 2.X versions.


libman.json reports errors for valid destination

Minimal repro steps
Create a libman.json file as:
{
"version": "1.0",
"defaultProvider": "cdnjs",
"libraries": [
{
"library"<EMAIL_ADDRESS>"destination": "wwwroot\lib\jquery"
}
]
}
Expected result
No error reported
Actual result
report warning for destination property

The issue here is the slashes aren't escaped.  JSON strings must escape \ as \\


hasPosition added position deprecated

The paper reviewers complain that position and Position are to similar.
We could deprecate the position property and add the hasPosition property.
For owl based tools the following won't make a difference. RDFS and RDF only tools will notice.
Can we still change this.

This change would make like clearer, so if there are no obvious downsides on the tool side, it seems a good idea.

As said in my email: marking "position" obsolete and introducing an equivalent "hasPosition" property is fine with me. Removing "position" completely is not good though, because it would invalidate the examples in the GFVO paper (https://peerj.com/articles/933/)

:+1:

@indiedotkim this is the suggest fix (see associated commit)
 :position
       rdf:type owl:DatatypeProperty ;
      owl:deprecated true ;
      owl:equivalentProperty :hasPosition ;
      rdfs:comment "This is a deprecated property, use faldo:hasPosition instead." .

:hasPosition
      rdf:type owl:DatatypeProperty ;
      owl:equivalentProperty :position ;
       rdfs:comment "Denoted in 1-based closed coordinates, i.e. the position on the first amino acid or nucleotide of a sequence has the value 1. For nucleotide sequences we count from the 5'end of the sequence, while for Aminoacid sequences we start counting from the N-Terminus."^^xsd:string , "The position value is the offset along the reference where this position is found. Thus the only the position value in combination with the reference determines where a position is."^^xsd:string ;
       rdfs:domain :ExactPosition ;
       rdfs:range

Looks good; plugged it into the Hermit reasoner and it sees no problem either.
Having said that, what happened to the range restriction? I have it in my local repo as:
  rdfs:range
          [ rdf:type rdfs:Datatype ;
            owl:onDatatype xsd:integer ;
            owl:withRestrictions
                    ([ xsd:minInclusive 1
                      ])
          ] .

The range condition is there in the file but the patch where I copied it from does not have it as its "unchanged"

@JervenBolleman Got it -- merge-magic that crops it out in the patch. :+1:

fine with me.

That's OK guys. Thanks

OK, that sounds reasonable to me.

+1

+0

@micheldumontier does that mean don't mind either way? or is that a negative.

I don't feel that you should have to change the uri, as these are case sensitive, and are a widely adopted pattern (which we have already implemented). on the other hand, if people take issue with it then perhaps it's worth changing. Either way, we'll conform to the standard.

Ok no one is strongly opposed, yet no one is strongly in favor either. I think there are 3+1 and 6+0.
I think that making everyone change their tools for a small cosmetic change is not worth it.
Not having achieved a quorum for amongst faldo paper authors I am going to close the issue today without merging at 15:00 geneva time. Any objects are due by then.

Jerven > I think that making everyone change their tools for a small cosmetic change is not worth it.
I agree with you.