[BUG]calling pf_client.run inside the callable target function for evaluate got "Error: (AssertionError) daemonic processes are not allowed to have children."

Describe the bug
A clear and concise description of the bug.
How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:
I am trying to hook up the evaluate method with my own prompt which used to run from pf_client.run
example code below:
from promptflow.client import PFClient

pf_client = PFClient()

def user_call():
    my_prompt_flow = pf_client.run(my prompt flow configs)
    return my_prompt_flow_output

def run_evaluation():
    results = evaluate(
                 evaluation_name=evaluation_name,
                 data=data_path,
                 target=user_call,
                 evaluators={
                    "violence": violence_evaluator,
                    "sexual": sex_evaluator,
                    "self_harm": self_harm_evaluator,
                    "hate_unfairnes": hate_unfairness_evaluator,
                    "content_safety": content_safety_evaluator
                 },
                azure_ai_project=project_scope
             )

2024-07-06 00:58:41 +0000 1845174 execution.bulk INFO The process [1845174] has received a terminate signal.
2024-07-06 00:58:42 +0000 1844849 execution ERROR 1/1 flow run failed, indexes: [0], exception of index 0: Execution failure in 'user_call': (UnexpectedError) Unexpected error occurred while executing the batch run. Error: (AssertionError) daemonic processes are not allowed to have children.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Running Information(please complete the following information):

Promptflow Package Version using pf -v: [e.g. 0.0.102309906]
Operating System: [e.g. Ubuntu 20.04, Windows 11]
Python Version using python --version: [e.g. python==3.10.12]
{
"promptflow": "1.13.0",
"promptflow-azure": "1.13.0",
"promptflow-core": "1.13.0",
"promptflow-devkit": "1.13.0",
"promptflow-evals": "0.3.0",
"promptflow-tracing": "1.13.0"
}
Additional context
Add any other context about the problem here.

thanks @D-W- , that works!


💅 Linter fail on code files contains literal RegExp contains Cyrillic symbols

Environment information
Linter fail on code files contains literal RegExp contains Cyrillic symbols.

Example code:
() => currentValue !== '' && !checkError(currentValue.replace(/[^A-ZА-Я0-9]/gi, '')),

Linter Output:
 × processing panicked: byte index 6 is not a char boundary; it is inside 'А' (bytes 5..7) of `[^A-ZА-Я0-9]`

Or (if RegExp contains symbol "-"):
  × processing panicked: byte index 9 is not a char boundary; it is inside '—' (bytes 7..10) of `[0-3]\d—[0-3]\d`

Rule name
noMisleadingCharacterClass
Playground link
https://biomejs.dev/playground/?code=YwBvAG4AcwB0ACAAYQAgAD0AIAAvAFsAXgBBAC0AWgAQBC0ALwQwAC0AOQBdAC8AZwBpADsACgBjAG8AbgBzAHQAIABiACAAPQAgAC8AWwAwAC0AMwBdAFwAZAAUIFsAMAAtADMAXQBcAGQALwBnAGkAOwAKAA%3D%3D
Expected result
Print valid validation information for rule "noMisleadingCharacterClass".
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

I have the same issue with the following code:
value.replaceAll(/[\u200E\u2066-\u2069]/gu, "");

The error is:
Source Location: crates/biome_js_analyze/src/semantic_analyzers/nursery/no_misleading_character_class.rs:317:62
Thread Name: biome::worker_0
Message: byte index 2 is not a char boundary; it is inside '\u{200e}' (bytes 1..4) of `[-]`


Fixed force linking to an existing directory

Previously, trying to symlink to an existing directory with the force flag would error.  It was calling unlink on a directory.  This fixes that by checking if it is a directory before removing.
Let me know if there is anything else you need to merge this!

@wesleytodd does this conform with unix behavior? I can't reproduce the expected result. To me it looks like it's supposed to put the symlink inside the directory dir/

Tbh I dont know if I have used this since I submitted this. I can try to look tomorrow. But no promises 😀

:+1: I figure it's better to follow up on an old PR than to just let it sit even longer.

Yep!  Sadly since I'm not using it anymore I am not very incentivized to help out. That is the price of leaving OS issues for too long :). If you dont think it is a good pr then feel free to close. Wont offend me

I think I'm going to opt to close this, since I think it differs from unix behavior. Thanks for the contribution though @wesleytodd! If you think this is an important feature, please feel free to ping this thread or reopen.


npm install fails on windows

Looks like as part of the install it tries to create a .env file using the touch command.
This doesn't exist on Windows.

The example project that used touch .env has been replaced with npm create @keystatic@latest so this is no longer relevant


Don't connect to cormanlisp.com's servers looking for patches

The whole auto update facility is implemented in Sys\auto-update.lisp, the parameter auto-update-enabled is a switch to control it.  And the patch server URL entry is something like this:
http://www.cormanlisp.com/CormanLisp/patches/3_01f1/CormanLisp_3_01_patch_index.lisp
Then the downloaded index file will be analyzed for further download of other files.
I think maybe the idea of auto-update is still useful, because it's really convenient. By changing the patch server URL to Github, and add a similar "patches" directory into our code base, I say we're the first open source CL implementation which supports auto updates.  What do you think @luismbo @xach?

Or, maybe common-lisp.net is a better place as the patch server.

I would like the idea more if patches were fetched securely and verified as authentic before loading. Until that's done, I think it's better to remove the checking.

I produce the occasional patch at work and find that maintenance strategy to be a royal PITA. These days it should be easier to download the whole binary, maybe use binary diffs if necessary, than having to produce custom patches.

OK, make sense, this is a security hole. Then let me push a fix to disable the auto-updates by default.

Auto update is disabled by default. I hope we preserve the related code and not delete them.


Update spinner.component.tsx

Fix the missing text. Thus, closes #674.
Please read and mark the following check list before creating a pull request:

[x] I read and followed the CONTRIBUTING.md guide.
[x] I read and followed the New Feature Checklist guide.

Short description of what this resolves:
Typo/missing text in the API doc.

Thanks!


Button Failure and Questions

Hello my fellow dev. friend and greetings from San Francisco, California! Great work so far in this great little extension, I came very close to making my own and until I found this little gem you have graciously given to the world. :) I have some to points
1- What is supposed to happen when you click on >> Select >>  "Get New Context Menu"? Nothing happens when I tried it, and I am pretty sure it is supposed to do something.
2- Does your extension affect the quick rendering of a page at all? If so, by how much approximately? Or, does the execution ONLY start when the right click happens?
3- Does the Google Chrome API allow to have dropdown menus within the context menu? I was hoping your group functionality would do just that, but correct me if I am wrong, your group feature is meant only to open up the group of links all at once?
"Digital" hug and appreciation,
Sylvia

Sylvia Hello,
Thank you for your compliments about your question

Due to the economic problems of my application server expire, so you can not get online New Context Menu;
In order to improve the performance of memory-resident CM will occupy some memory;
3.chrome API does not permit the dropdown menus.

Xuender,
I thank you for your response and I am sure you will cleverly solve issue number "1.".  ;)
Was the functionality of "Get New Context Menu" a way for people to get more "search" url templates for more menu items? If so, why not just have your extension check one central json/cvs/xml/txt file from which to get templates.
1- In going back to your "2.", out of all the possible things that can affect memory usage, I don't think having (what seems to me) some static menu items should be that big of a deal.  But, do you think there will be an issue if I run 5 different (so I can have multiple dropdown menus) of your extensions, each with 10-20 possible menu items?
Any stable solution should eliminate any possible point of failure, and as such, CM should not rely on solely on one server application to serve its purpose. Does CM sync with chrome? This should be enough for chrome store users, but for developers who wish to use your application without competing with yours in the store there should be a sync solution for them/us too.
2- Check out this Note taking application https://laverna.cc/index.html#/settings it is "top" ranked at http://alternativeto.net/tag/notebook/ .
3- Notice the way they handle syncing of data, here https://laverna.cc/index.html#/setting, using https://dropbox.com and http://remotestorage.io/.
4- Do you think the only way to make multiple menu with sub-menu items in your CM extension is if I installed them manually and with different custom names?
5- Possible New Feature: Do you think creating Context Menus based on domain, full URL, or part of the url can trigger custom menus? Think about this, in a world full of web-based applications, having the right and customized menu options as easily accessible as a simple right click can be extremely good. This can add a whole realm of possibilities to your application. For example, if I am in github.com and I do a right click, I can send a selected code snippet to my snippets code base app on the appropriate category, or I can annotate the page, or I can add a technical to do for later... What do you think?
6- Having a solution like in number "3-", smart context menus triggered by full/part of the url, a few tweaks in the way you present your application, a little of clever gorilla marketing and I don't why your extension shouldn't be "The King of the Right Right Mouse Button When Surfing the Internet" of all the Chromium based browsers!
As of 2014, the number of internet users worldwide was 2.92 billion, and with Chrome with 51% of the  browsers there is at least 1.5 billion people that can benefit from this Extension...  Food for thought don't you think! :)
Sylvia


Team Relevant Blog Posts

Add all team relevant blog posts from blog.openmined.org to their individual sections on their team category pages.

@4mber I'd love to work on this. There are posts under different team groups (federated learning, differential privacy) and some not under a team on the openmined blog. Should i add the content by unique posts or by "filed under". What do you suggest?

@Boluwatifeh Great question!
There are SO many posts, and I'm sure a lot of them have something to do with a team. So maybe go through each category, add the ones that there are already categories for to their related team, then scan through the ones that aren't categorised to see if they should be connected to any specific team (for instance, I know there are a few to do with the Learning Team, announcing the team and the beta-bootcamp, and there may be other uncategorised ones like that as well).
Does that make sense?
Just going to tag in @em-blue as well, as she leads the writing team and may be able to help in some capacity.
The idea is just that, we have info for each team on the Dev and Community Team pages in this repo, and we just want to add a section for each team including links to related OM blog posts, if they exist, so people can read more about each team and see what the team has worked on, if they've written about it.

Alright, sounds doable. Working on it

@Boluwatifeh Great idea - and if you feel up to it, I could give you temporary editor permissions on our blog so you could go through and tag previous blog posts with whichever tags you think fit them. Our tagging hasn't been very thorough, some blogs don't have any tags

@em-blue that would be great as the tags would also serve as a base guide for future blog posts

Ooh great idea guys!! :raised_hands:

made the changes to reflect relevant blog posts for each team  @4mber kindly look into this PR so i can send the PR for this particular issue thanks.

Perfect, thanks so much @Boluwatifeh ! :)


chore: update terraform azurerm provider to version 4.x and migrate t…

…erraform properties to match new version
Purpose

Migration / update of the used azurerm terraform provider to the newest version

Does this introduce a breaking change?

[ ] Yes
[x ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ x] Other... Please describe: **dependency updates**

How to Test

Get the code
execute terraform with set variables

@microsoft-github-policy-service agree company="Valtech Mobility GmbH"


Refactor DVC to use external storage

When external storage is available, set up this repository to use it. This will mean may mean adding a new remote. The data stored in data and data/dvc_storage may be moved to a dvc data repository and removed from this repository.

When the external storage is set up enable the CI workflow again. As the data is too big to be moved through github without external storage or paying for git-lfs, it will always fail checks as it can't pull the data.


License Definition

Is this code distributed under Apache2 as Tensorflow

The code is distributed under BSD 2-Clause


Error: Linking of rule '@protobuf_archive//:protoc' failed (Exit 1): clang failed: error executing command

System information

OS Platform and Distribution: Windows 10
TensorFlow installed from (source or binary):
TensorFlow version: 1.12
Python version: 3.6.8
Installed using virtualenv? pip? conda?: pip
Bazel version (if compiling from source): 0.23.0
GCC/Compiler version (if compiling from source): 7.4.0

I was trying to do real-time object detection in android using tensorflow. I already trained the model and have the frozen inference graph and other required data. Then I started following this website (https://www.skcript.com/svr/realtime-object-and-face-detection-in-android-using-tensorflow-object-detection-api/) to deploy it to android. Now I am not able to build a .so(c++ compiled) file from my existing tensorflow model. When I run the command,
bazel build -c opt //tensorflow/contrib/android:libtensorflow_inference.so
--crosstool_top=//external:android/crosstool
--host_crosstool_top=@bazel_tools//tools/cpp:toolchain
--cpu=armeabi-v7a
--cxxopt=-std=c++17
I got this error:
(tensorflow1) C:\tensorflow1\models\research\object_detection\tensorflow>bazel build -c opt //tensorflow/contrib/android:libtensorflow_inference.so --crosstool_top=//external:android/crosstool --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --cpu=armeabi-v7a --cxxopt=-std=c++17
INFO: Options provided by the client:
Inherited 'common' options: --isatty=1 --terminal_columns=120
INFO: Options provided by the client:
'build' options: --python_path=C:/ProgramData/Anaconda3/envs/tensorflow1/python.exe
INFO: Reading rc options for 'build' from c:\tensorflow1\models\research\object_detection\tensorflow.bazelrc:
'build' options: --apple_platform_type=macos --define framework_shared_object=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone --strategy=Genrule=standalone -c opt --announce_rc --define=grpc_no_ares=true --define=PREFIX=/usr --define=LIBDIR=$(PREFIX)/lib --define=INCLUDEDIR=$(PREFIX)/include
INFO: Reading rc options for 'build' from c:\tensorflow1\models\research\object_detection\tensorflow.tf_configure.bazelrc:
'build' options: --action_env PYTHON_BIN_PATH=C:/ProgramData/Anaconda3/envs/tensorflow1/python.exe --action_env PYTHON_LIB_PATH=C:/ProgramData/Anaconda3/envs/tensorflow1/lib/site-packages --python_path=C:/ProgramData/Anaconda3/envs/tensorflow1/python.exe --config monolithic --copt=-w --host_copt=-w --copt=-DWIN32_LEAN_AND_MEAN --host_copt=-DWIN32_LEAN_AND_MEAN --copt=-DNOGDI --host_copt=-DNOGDI --verbose_failures --distinct_host_configuration=false --define=override_eigen_strong_inline=true --action_env TF_CONFIGURE_IOS=0
INFO: Found applicable config definition build:monolithic in file c:\tensorflow1\models\research\object_detection\tensorflow.bazelrc: --define framework_shared_object=false
DEBUG: Rule 'io_bazel_rules_docker' modified arguments {"shallow_since": "1556410077 -0400"}
INFO: Build option --cxxopt has changed, discarding analysis cache.
WARNING: The major revision of the Android NDK referenced by android_ndk_repository rule 'androidndk' is 20. The major revisions supported by Bazel are [10, 11, 12, 13, 14, 15, 16, 17, 18]. Bazel will attempt to treat the NDK as if it was r18. This may cause compilation and linkage problems. Please download a supported NDK version.
WARNING: API level 14 specified by android_ndk_repository 'androidndk' is not available. Using latest known API level 28
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_beam_entry.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_beam_scorer.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_beam_search.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_decoder.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/ctc:ctc_loss_util.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/internal:profiler_interface.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/internal:profiler_interface.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/internal:traceme_recorder.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/internal:traceme_recorder.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/lib:BUILD' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/lib:profiler_session.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/lib:profiler_session.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/lib:traceme.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/profiler/lib:traceme.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:attr_builder.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:attr_builder.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:context.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:context.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:copy_to_device_node.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:eager_executor.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:eager_executor.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:eager_operation.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:eager_operation.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:execute.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:execute.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:execute_node.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:kernel_and_device.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:kernel_and_device.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:tensor_handle.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/common_runtime/eager:tensor_handle.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:avgpooling_op.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:batch_util.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:cwise_ops.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:cwise_ops_common.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:cwise_ops_gradients.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_activations.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_attention.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_backward_cuboid_convolutions.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_backward_spatial_convolutions.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_cuboid_convolution.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_pooling.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_softmax.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_spatial_convolutions.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_spatial_convolutions-inl.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:eigen_volume_patch.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:fifo_queue.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:maxpooling_op.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:ops_util.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:padding_fifo_queue.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:pooling_ops_common.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:pooling_ops_common.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:queue_base.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:queue_op.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:typed_queue.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/tensor_bundle:naming.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/tensor_bundle:naming.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/tensor_bundle:tensor_bundle.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/util/tensor_bundle:tensor_bundle.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:c_api.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:c_api.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:c_api_function.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:c_api_internal.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:checkpoint_reader.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:checkpoint_reader.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:env.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:env.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:kernels.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:kernels.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:ops.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:ops.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_attrtype.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_datatype.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_datatype.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_status.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_status.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_status_helper.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_status_helper.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_status_internal.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_tensor.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c:tf_tensor.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/cc:framework/gradients.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/cc:framework/ops.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/cc:framework/scope.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/cc:framework/scope_internal.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/cc:ops/while_loop.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/cc/saved_model:loader.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/distributed_runtime:server_lib.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c/eager:c_api.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c/eager:c_api.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c/eager:c_api_debug.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c/eager:c_api_internal.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/BUILD:1890:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/c/eager:tape.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: C:/tensorflow1/models/research/object_detection/tensorflow/tensorflow/core/kernels/BUILD:6410:12: in srcs attribute of cc_library rule //tensorflow/core/kernels:android_tensorflow_kernels: please do not import '//tensorflow/c/kernels:bitcast_op.cc' directly. You should either move the file to this package or depend on an appropriate rule there
INFO: Analysed target //tensorflow/contrib/android:libtensorflow_inference.so (0 packages loaded, 10655 targets configured).
INFO: Found 1 target...
ERROR: C:/users/devim/_bazel_devim/ktcla6nj/external/protobuf_archive/BUILD:388:1: Linking of rule '@protobuf_archive//:protoc' failed (Exit 1): clang failed: error executing command
cd C:/users/devim/_bazel_devim/ktcla6nj/execroot/org_tensorflow
SET PATH=C:\msys64\usr\bin;C:\msys64\bin;C:\ProgramData\Anaconda3\envs\tensorflow1;C:\ProgramData\Anaconda3\envs\tensorflow1\Library\mingw-w64\bin;C:\ProgramData\Anaconda3\envs\tensorflow1\Library\usr\bin;C:\ProgramData\Anaconda3\envs\tensorflow1\Library\bin;C:\ProgramData\Anaconda3\envs\tensorflow1\Scripts;C:\ProgramData\Anaconda3\envs\tensorflow1\bin;C:\ProgramData\Anaconda3\condabin;C:\Program Files (x86)\Intel\iCLS Client;C:\Program Files\Intel\iCLS Client;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Program Files\MATLAB\R2018a\bin;C:\WINDOWS\System32\OpenSSH;C:\Tensorflow\models\research\object_detection;C:\Tensorflow\object_detection;C:\Program Files\Microsoft SQL Server\130\Tools\Binn;C:\Users\devim.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit;C:\Users\devim\AppData\Local\Microsoft\WindowsApps;C:\Users\devim\AppData\Local\GitHubDesktop\bin;c:\msys64\usr\bin;C:\tensorflow1\models;C:\tensorflow1\models\research;C:\tensorflow1\models\research\slim
SET PWD=/proc/self/cwd
SET PYTHON_BIN_PATH=C:/ProgramData/Anaconda3/envs/tensorflow1/python.exe
SET PYTHON_LIB_PATH=C:/ProgramData/Anaconda3/envs/tensorflow1/lib/site-packages
SET TF_CONFIGURE_IOS=0
external/androidndk/ndk/toolchains/llvm/prebuilt/windows-x86_64/bin/clang -o bazel-out/armeabi-v7a-opt/bin/external/protobuf_archive/protoc bazel-out/armeabi-v7a-opt/bin/external/protobuf_archive/_objs/protoc/main.o bazel-out/armeabi-v7a-opt/bin/external/protobuf_archive/libprotoc_lib.a bazel-out/armeabi-v7a-opt/bin/external/protobuf_archive/libprotobuf.a bazel-out/armeabi-v7a-opt/bin/external/protobuf_archive/libprotobuf_lite.a bazel-out/armeabi-v7a-opt/bin/external/zlib_archive/libzlib.a external/androidndk/ndk/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a/libandroid_support.a external/androidndk/ndk/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a/libc++_static.a external/androidndk/ndk/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a/libc++abi.a external/androidndk/ndk/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a/libunwind.a -target armv7-none-linux-androideabi -Wl,--fix-cortex-a8 -gcc-toolchain external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/windows-x86_64 -no-canonical-prefixes -Lexternal/androidndk/ndk/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a -static-libgcc --sysroot=external/androidndk/ndk/platforms/android-28/arch-arm
Execution platform: @bazel_tools//platforms:host_platform
external/androidndk/ndk/sources/cxx-stl/llvm-libc++/include/math.h:834: error: undefined reference to 'ceilf'
external/androidndk/ndk/sources/cxx-stl/llvm-libc++/include/math.h:834: error: undefined reference to 'ceilf'
external/androidndk/ndk/sources/cxx-stl/llvm-libc++/include/math.h:834: error: undefined reference to 'ceilf'
external/androidndk/ndk/sources/cxx-stl/llvm-libc++/include/math.h:834: error: undefined reference to 'ceilf'
external/protobuf_archive/src/google/protobuf/stubs/common.cc:149: error: undefined reference to '__android_log_write'
external/protobuf_archive/src/google/protobuf/stubs/common.cc:157: error: undefined reference to '__android_log_write'
/usr/local/google/buildbot/src/android/ndk-release-r20/external/libcxx/../../external/libunwind_llvm/src/AddressSpace.hpp:481: error: undefined reference to 'dladdr'
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build
INFO: Elapsed time: 143.166s, Critical Path: 28.59s
INFO: 297 processes: 297 local.
FAILED: Build did NOT complete successfully
Protobuf version is 3.6.1
Please help me. I don't know what is causing this error. Is it because I am doing everything on Windows ??

Did you try to follow Object Detection on android. If not, please have a look and let us know if that helps. Thanks!

@achandraa I tried this code already. This should have a detect.tflite file in the assets folder, which is now missing. Does it mean we don't need a tflite  file now ? But when I tried, i needed a detect.tflite file from my tensorflow trained model. I followed this website to get the .tflite file from frozen_graph.pb using bazel. I was able to solve all the errors. But finally, I got a detect.tflite file with 0 kb.  I will try to run the new code again in android studio.

@achandraa . I tried the code and it generated the detect.tflite file in the assets folder. So this is the same code. Can you help me with getting a detect.tflite file from my tensorflow model ? Also, I tried to change the existing detect.tflite file in this code with a sample detect.tflite file given in the above mentioned website. But when I run the code, the sample tflite file I copied from the website gets converted to the default tflite file automatically. So, changing the tflite file in the assets folder is not the correct thing to do. What exactly should I do to customize this code according to my model ?

Can you file a separate bug for the conversion issue you're facing? Thanks.


Extend Wrapped interface

From my point of view current contract of Wrapper is not complete. If we pretend to unwrap some instance especially Connection or smth like that, we should consider that such an instance can be in some intermediate state.
It's better to demonstrate on BufferedInputStream example. If we use underlying stream of buffered there's no guarantee that its state is consistent because buffered's buffer may be unflushed.
So the same is applicable to any wrapped object. We should either check for ability to unwrap at some point in time or call preparation for unwrapping or at least be prepared to catch some predefined exception telling that wrapped instance is not in consistent state. But current interface doesn't take into account any of these.
So my suggestion is to extend interface either with additional method(s) or append exception signature to the single one.
Related to #28

Ensuring consistency isn't a goal of the wrapper API and there's likely no way to do so. What we try to achieve is providing an API instead of folks building reflection-based access themselves to obtain the delegate which can easily break at any time.
Care to provide a bit more background on where you see a risk of obtaining an object of inconsistent state? Maybe you have already encountered such a case? What would happen in the same case with JDBC (e.g. trying to unwrap a pooled connection that has been given back to the pool)?

@mp911de here you provide interface not solely for connection but for any possible implementor. So it should have maximally broad contract. Even mentioned jdbc wrapper is designed to throw an SQLException but for another reason according to the docs. But at least it can be used technically to react on some internal failures inside unwrap method appearing during preparation for unwrapping (let's say flushing buffer, releasing locks etc).
I'll try to provide you an example some time later

The R2DBC allows generally the use of IllegalState, IllegatArgument, and UnsupportedOperationException. So probably throwing an exception should be an implementation detail.
Refining the spec makes sense if we can come up with a number of cases that need to consider exceptional behavior.

With 0.9, we introduced unwrap(Class<E> targetClass) that serves the purpose of unwrapping to a specific target type. Closing this ticket as we have everything in place for improved type safety.

See #176 for further reference.


Fix compilation errors on Visual Studio 2015 (_MSC_VER 1900)

Latest version of cl.exe complains about ignored typedef, hidden "path" local variable and hash_map being deprecated.
With C++11-compliant compilers (and MSC >= 1900), it is possible to use the standard unordered_map container instead of vendor-specific structures.

Thanks!


:bug: Fix too small JSON payload triggering md with high ratio

Close #58~
To reproduce:
from charset_normalizer import from_bytes

results = from_bytes(b"{}").best()

Expected encoding = 'ASCII'; Got 'UTF-16 (Variant)'.
Why does this happen?
Because the first pass consists of assessing the "mess/chaos" ratio, and one of the detection plugins was unadjusted for a small JSON payload.

Codecov Report

Merging #59 (bde9973) into master (53b2dab) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #59      +/-   ##
==========================================
+ Coverage   84.49%   84.59%   +0.09%
==========================================
  Files          11       11
  Lines        1058     1058
==========================================
+ Hits          894      895       +1
+ Misses        164      163       -1

Impacted Files
Coverage Δ

charset_normalizer/md.py
87.05% <100.00%> (ø)

charset_normalizer/models.py
86.97% <0.00%> (+0.52%)
:arrow_up:

Continue to review full report at Codecov.

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

Great to get i addressed so quickly !

With a change that big, comes to some responsibilities. Will make sure that this change is worth it.


Unable to RDP to VMSS. Article still not updated

Hi,
Still doesn't work.  Please update the instructions to show how to create the NSG or fix the command so it created the NSG

Create NSG in Same Resource Group and Location as VMSS
Create Inbound Rule allowing RDP ANy ANY TCP 3389
Associate it to the Subnet

Being able to connect to a scale set is an important concept.
Originally posted by @mimckitt in https://github.com/MicrosoftDocs/azure-docs/issues/28077#issuecomment-569768413

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

ID: 92e965d9-bda3-ba82-00e0-a4c8b30a23cf
Version Independent ID: d00377a2-9524-d17e-e98c-780a633d70ce
Content: Tutorial: Create & manage an Azure VM scale set – Azure PowerShell - Azure Virtual Machine Scale Sets
Content Source: articles/virtual-machine-scale-sets/tutorial-create-and-manage-powershell.md
Service: virtual-machine-scale-sets
Sub-service: management
GitHub Login: @ju-shim
Microsoft Alias: jushiman

@dpapkin Thanks for the feedback! We will review and update accordingly.

@dpapkin Thanks for the feedback! We will review and update accordingly.

Sure. This documentation issue has been unresolved for years , since people still giving feedback on it. Lets solve it once and for all :)

The information is updated in this article here: https://docs.microsoft.com/en-us/azure/virtual-machines/windows/tutorial-create-vmss#allow-traffic-to-application
Thanks for the feedback! I have assigned the issue to the content author to update this document as well.

I created a work item on my end to tackle this issue and provide accurate information on this process. Work is slated for June/July timeframe. There will be other doc improvements made on the topic of connecting to a scale set(s) sooner than that.
Thank you for the feedback and patience!
#please-close

The document referenced by @Karishma-Tiwari-MSFT only references web pages where there are no port translation rules in the app and only port 80 is being used. However this does not help for setting up rules for port 3389 to access the machines which requires different ports being forwarded to 3389 on the destinations. Each machine will have a different port so even though it's possible to add two ports to the NSG, these are going to vary each time  the scale set is updated.

@Absoblogginlutely Thanks for sharing the feedback. The doc author has shared the update in the comment above:
"I created a work item on my end to tackle this issue and provide accurate information on this process. Work is slated for June/July timeframe. There will be other doc improvements made on the topic of connecting to a scale set(s) sooner than that."

#assign: @mimckitt

I will be taking a look at this in the next few days and get a PR with a fix.

Pushing fix shortly. Will be live by EOD.
#please-close


Error

Hello,
I'm trying to reproduce your algorithm, but I will get this error. What am I doing wrong?

Try changing the cudnn and cudatoolkit versions.
I used
conda install cudatoolkit==9.0 cudnn==7.1.4
and it fixed the error.


Track dependencies in pyproject.toml instead of Pipfile.lock

I don't want to force my opinion onto this project (which I'm not part of), but based on my experience with other Django projects in the Digitalfabrik ecosystem (lunes-cms and integreat-cms), I would not recommend to use pipenv for new setups. Migrating the dependency manager in mid-project is a bit cumbersome, so I suggest to debate this in an early stage (though I'm aware that this is not the most urgent topic right now).
My main arguments are:

Installing/updating dependencies via pipenv takes longer than with plain pip (couple of mins compared to couple of seconds - in the long term, this really cumulates to a lot of wasted dev time... I think this is not worth the benefits pipenv is offering)
Debugging problems with pipenv itself did cost us quite some time when we cumulate this over the past years

Proposed solution

Follow this guide to specify dependencies in pyproject.toml: https://setuptools.pypa.io/en/stable/userguide/pyproject_config.html

Use pip install -e . instead of pipenv install to install the dependencies

@timoludwig thx for looking into the code, every hint is valuable!
We have (so far) good experience in using pyproject.toml with poetry: https://python-poetry.org/docs/pyproject/ in the searchwing context.
Or do you think this is overkill?


realm_domains: Move realm domains table to organization permissions.

The Realm domains table used to be in a modal. This PR moves that table to be in organization permissions of organization settings
Testing Plan:
Ran automated tests.
Manually tested UI to cover everything possible in that area.
GIFs or Screenshots:

@chdinesh1089 thanks for working on this!  I think we need to do a bit more work to make this UI acceptable:

The use of the old-style green banner feedback and general confirmation logic for the modal is inconsistent with the rest of this page.
The "Waiting period" setting ends up out of place in a confusing way.
The heading would be better as an h4 rather than an h3, unless we're hoping to make it a setting heading.

To resolve these:

Let's add a prep commit that moves "Waiting period before new members turn into full members " to the "User identity" section; while that's a bit off from what we want long-term, I think given the restructuring we're doing to everything in "Joining the organization", we'll want it in another place for now.  Be sure to update the Help Center in that commit.
Let's add a next series of commits that work on making the save behavior for changes to the "Allowed domains" form consistent with how the other settings in "Joining the organization" work.

Made the changes and modified tests as needed. This is how it looks now.

(link to CircleCI: https://circleci.com/gh/chdinesh1089/zulip/tree/domains-table)

Thanks for reviewing this @aero31aero. Made the suggested changes.

Rebased and fixed conflicts. Could you do a review @timabbott ?


aligned depth image and RGB image in L515

By using L515 ,I have already got the rgb images and depth images,but how to align them one by one ?
i have got the inner intrinsics {"fx":<PHONE_NUMBER>375, "fy":<PHONE_NUMBER>5, "ppx":<PHONE_NUMBER>3203125, "ppy":<PHONE_NUMBER>388672, "height": 480, "width": 640, "depth_scale": 0.0002500000118743628} like this, but when i use them to align the point cloud is not the same as i got by using the code-(rosbag record -o test1.bag /camera/depth/color/points).
here is the code:
import pyrealsense2 as rs
import numpy as np
import cv2
import matplotlib.pyplot as plt
import open3d as o3d
load image and depth from .png and .npz file
img_f = 'K:/YOLO/yolov7-main/yolov7-main/runs/detect/exp8/3.jpg'
color_image = cv2.imread(img_f)
cv2.imshow('img', color_image)
cv2.waitKey(1)
img_dep = 'K:/YOLO/yolov7-main/yolov7-main/runs/detect/exp9/3.jpg'
depth_image = np.load(img_dep,allow_pickle=True)
depth_image= cv2.imread(img_dep)
o3d_color = o3d.geometry.Image(color_image)
o3d_depth = o3d.geometry.Image(depth_image)
rgbd_image = o3d.geometry.RGBDImage.create_from_color_and_depth(o3d_color, o3d_depth,
depth_scale=1.0/ 0.0002500000118743628,
depth_trunc=4000) ##########深度值高于1000直接省略
转换为open3d中的相机参数
pinhole_camera_intrinsic = o3d.camera.PinholeCameraIntrinsic(640,480,599.6552734375,599.66796875,325.10821533203125,235.8369598388672)
use open3d save to ply file
tmp = o3d.geometry.PointCloud.create_from_rgbd_image(
rgbd_image,
pinhole_camera_intrinsic
)
o3d.visualization.draw_geometries([tmp])
o3d.io.write_point_cloud("3.pcd", tmp)

i have got the inner intrinsics {"fx":<PHONE_NUMBER>375, "fy":<PHONE_NUMBER>5, "ppx":<PHONE_NUMBER>3203125, "ppy":<PHONE_NUMBER>388672, "height": 480, "width": 640, "depth_scale": 0.0002500000118743628} like this, but when i use them to align the point cloud is not the same as i got by using the  code-(rosbag record -o  test1.bag  /camera/depth/color/points).

Hi @OneShz  There is a pyrealsense2 / Open3D pointcloud script that uses depth-color alignment at https://github.com/isl-org/Open3D/issues/473#issuecomment-508139946 that you could compare to your own script.

Hi @OneShz There is a pyrealsense2 / Open3D pointcloud script that uses depth-color alignment at isl-org/Open3D#473 (comment) that you could compare to your own script.

Thank you for your reply I will try.

Hi @OneShz There is a pyrealsense2 / Open3D pointcloud script that uses depth-color alignment at isl-org/Open3D#473 (comment) that you could compare to your own script.

I see the comment but it not use,because I need a postpone 3d points,in the example it generates a instant 3d points so it must be connect by the machine,while i have gotten the rgb images and depth images.The following are the 3d I generated and the instant got.

There are very few references available about creating pointclouds using RealSense and Open3D, so this will be a difficult issue to diagnose unfortunately.
Where did you obtain your intrinsic values for your L515 from, please?  Each camera has unique intrinsic values because of the manufacturing process at the factory, so it is important to retrieve the values from the exact camera that is being used rather than use values from another camera.
The intrinsic values below for depth and color at 640x480 are from one of my own L515.

Hi @OneShz  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.

Hi, @MartyG-RealSense
I notice L515 rgb can support 1280x720, but the max depth is 1024x768. like rs.align(rs.stream.depth)？
How should I align rgb and depth during the data recording?

Hi @kingchou007  The RealSense SDK's align processing block component automatically adjusts for different depth and RGB resolutions when rs.align is used.


Update minimist to fix security vulnerability (#3161)

Pull request opened by the merge tool on behalf of #3161

Merged in a9270dbe44268a061ed38bdd801443ffa84bc545


how to fix typos in data?

I think you can't. There's a dedicated data team which maintains all the data in Google Sheet.
Probably, we'll have to put requests somewhere/here for them to fix things.

We should have automated validation system which validates simple typos and restricts user from doing simple mistakes.
I can do that if possible.

What typos? Could you describe further?

@sudevschiz Some of the points had been mentioned already in #31 #26 and #29

@sudevschiz Some of the points had been mentioned already in #31 #26 and #29

@alphasingh, we've fixed the names in sheet as well as the site to match correctly. Could you please check whether these issues still exist? If yes could you close them from this repo and raise at https://github.com/covid19india/covid19india-react ?


x/tools/cmd/goimports: Return exit code greater than zero if there's an offense

What version of Go are you using (go version)?

$ go version
go version go1.14.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="~/.cache/go-build"
GOENV="~/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="~/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/lib/go/go-latest"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/lib/go/go-latest/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="~/go/path/to/project/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build335622656=/tmp/go-build -gno-record-gcc-switches"

What did you do?

This is more of a feature request (or question) rather than bug reporting. I'm trying to check formatting of go files with goimports which works as expected, but if there's any offensive file it always exit with code 0. As a result I need to hack around with tee and similar tools to manually fail my make checkfmt target on CI.
I was wondering if this was by design or any specific reasons not to return exit code greater than zero on list (-l). I briefly looked around and it seems there might be a really easy way to add this, something like adding:
exitCode = 1 # or any other reasonable exit code

right after line 156, here:
https://github.com/golang/tools/blob/a4cde3673cf4d442ef00a2df0d7a6f707d9e726b/cmd/goimports/goimports.go#L155-L157

https://github.com/golang/tools/blob/a4cde3673cf4d442ef00a2df0d7a6f707d9e726b/cmd/goimports/goimports.go#L155-L157

Makes sense to me. Would you like to send a CL?

Yes definitely.


How to use.

I've tried using SDL2 and using SDL. I can't figure out

Me too.. I tried installing all packages of SDL from nuget (image, ttf, etc) but there's no SDL namespace thing. @kosmotema any demo or doc to explain usage?

Hello. It looks like you're trying to use this package in a C# project, but sdl2.nuget is only for C++ projects.
So you need another package like Ryujinx.SDL2-CS or ppy.SDL2-CS (or any other SDL2 bindings for C# package)

Please clarify this in the documentation.


how to enable debugging mode ?

@snipercy Set log4j.properties file, log4j.rootLogger=INFO, SLOG, CONSOLE, SERROR replace to log4j.rootLogger=DEBUG, SLOG, CONSOLE, SERROR

@snipercy  Finally, thank you very much for your feedback.


Modified README

I have changed the formatting of README
I don't have discord link of the community so didn't update it.
Closes #30

Okay, will work on them.

Hi, @kumar-kalyan
Can you share link to discord community as the one in README is invalid

Raise a new issue named fix discord link and asldd this link :
https://discord.gg/RJQ57S8NeF
On Sun, 9 Oct, 2022, 11:41 pm Uday Mehtani, @.***>
wrote:

Hi, @kumar-kalyan https://github.com/kumar-kalyan
Can you share link to discord community as the one in README is invalid
[image: image]
https://user-images.githubusercontent.com/59679281/194772706-9cb267d1-53db-4124-91c7-845a9665e312.png
—
Reply to this email directly, view it on GitHub
https://github.com/hackbeats/complete-web3-bootcamp/pull/31#issuecomment-1272598494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP7W3ZWQVPUR4FRRIGPBRKTWCMDEFANCNFSM6AAAAAARAQ5XVU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Done, will make a PR once I'm assigned issue #47

Sure, will take care of it.

We can close this PR after accepting #48 PR


Allow installation of either tensorflow or tensorflow-gpu

The tensorflow requirement in install_requires prevents installation of tensorflow-gpu. This problem is because TensorFlow has two registered Python package names, one for CPU and for GPU. I moved tensorflow to be in extras_require, so that the user can pick either. (Of course this doesn't solve all problems though.) Am open to other options.
Let me know what you think.

Thanks @dustinvtran  this looks like the best solution.
I'll replicate this PR internally to GPflow so that the CI can run.

Codecov Report

Merging #362 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #362   +/-   ##
=======================================
  Coverage   99.73%   99.73%
=======================================
  Files          28       28
  Lines        2253     2253
=======================================
  Hits         2247     2247
  Misses          6        6

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 312f109...103e881. Read the comment docs.

merged vian internal PR


Generated pdf can't be validated by verapdf when using AddUTF8FontFromBytes

verapdf is a pdf/a validation tool. When using default font Arial, verapdf can validate the pdf with some warnings.

But when using font NotoSansSC, which is added by AddUTF8FontFromBytes, the pdf can't be validated. verapdf reports an error:
Sep 20, 2019 3:50:21 PM org.verapdf.processor.ProcessorImpl validate
WARNING: Exception caught when validating item
org.verapdf.core.ValidationException: Caught unexpected runtime exception during validation
	at org.verapdf.pdfa.validation.validators.BaseValidator.validate(BaseValidator.java:95)
	at org.verapdf.processor.ProcessorImpl.validate(ProcessorImpl.java:219)
	at org.verapdf.processor.ProcessorImpl.process(ProcessorImpl.java:120)
	at org.verapdf.processor.BatchFileProcessor.processItem(BatchFileProcessor.java:98)
	at org.verapdf.processor.BatchFileProcessor.processList(BatchFileProcessor.java:74)
	at org.verapdf.processor.AbstractBatchProcessor.process(AbstractBatchProcessor.java:102)
	at org.verapdf.gui.ValidateWorker.doInBackground(ValidateWorker.java:118)
	at org.verapdf.gui.ValidateWorker.doInBackground(ValidateWorker.java:53)
	at javax.swing.SwingWorker$1.call(SwingWorker.java:295)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at javax.swing.SwingWorker.run(SwingWorker.java:334)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.RuntimeException: Error while parsing object : 5 0
	at org.verapdf.cos.COSDocument.getObject(COSDocument.java:226)
	at org.verapdf.cos.COSIndirect.getDirect(COSIndirect.java:368)
	at org.verapdf.gf.model.visitor.cos.pb.GFCosVisitor.visitFromIndirect(GFCosVisitor.java:137)
	at org.verapdf.gf.model.impl.cos.GFCosObject.getFromValue(GFCosObject.java:70)
	at org.verapdf.gf.model.impl.cos.GFCosDict.getValues(GFCosDict.java:115)
	at org.verapdf.gf.model.impl.cos.GFCosDict.getLinkedObjects(GFCosDict.java:86)
	at org.verapdf.pdfa.validation.validators.BaseValidator.addAllLinkedObjects(BaseValidator.java:199)
	at org.verapdf.pdfa.validation.validators.BaseValidator.checkNext(BaseValidator.java:166)
	at org.verapdf.pdfa.validation.validators.BaseValidator.validate(BaseValidator.java:117)
	at org.verapdf.pdfa.validation.validators.BaseValidator.validate(BaseValidator.java:93)
	... 13 more
Caused by: java.io.IOException: PDFParser::GetDictionary()invalid pdf dictionary
	at org.verapdf.parser.COSParser.getDictionary(COSParser.java:250)
	at org.verapdf.parser.COSParser.nextObject(COSParser.java:179)
	at org.verapdf.parser.PDFParser.getObject(PDFParser.java:282)
	at org.verapdf.io.Reader.getObject(Reader.java:122)
	at org.verapdf.io.Reader.getObject(Reader.java:95)
	at org.verapdf.cos.COSDocument.getObject(COSDocument.java:217)
	... 22 more

Does invalid pdf dictionary mean that the pdf format is broken?

Thanks for the report, @sify21. I am glad to know about the verapdf tool for validating PDF/A compliance. This is an enhancement that was brought up in #144.
The problem related to AddUTF8FontFromBytes appears to be two-fold. Clearly something is going wrong with the UTF-8 implementation in gopdf. Additionally, the problem causes verapdf to crash so this should be brought to the attention of the authors at verapdf.org.

Does invalid pdf dictionary mean that the pdf format is broken?

My guess is that the UTF-8 feature in gofpdf generates some faulty output that isn't severe enough to cause problems with PDF readers but does not conform to the standard. Any help tracking this down will be greatly appreciated.

The error is this: "/BaseFont /utf8noto sans sc" and "/BaseFont /utf8noto sans scB". The spaces are wrong.

After removing white spaces from the familyStr variable of AddUTF8FontFromBytes, the generated pdf can be parsed.

Ok, I verified that if the familyStr contains white space, the generated pdf can't be viewed properly on Mac. So maybe there should be a note in the function comment or add some code in function body to remove whitespaces. @jung-kurt

Citing from 5.3 part of this article:

The names in PDF documents are represented by a sequence of ASCII characters in the range 0x21 – 0x7E. The exception are the characters: %, (, ), <, >, [, ], {, }, / and #, which must be preceded by a slash. An alternative representation of the characters is with their hexadecimal equivalent, preceded by the character ‘#’. There is a limitation of the length of the name element, which may be only 127 bytes long.

When writing a name a slash must be used to introduce a name; the slash is not part of the name, but is a prefix indicating that what follows is a sequence of characters representing the name. If we want to use whitespace or any other special character as part of the name it must be encoded with 2-digit hexadecimal notation.

@sify21, @THausherr: could you test my fix for this? In branch issue_304, I escape spaces in the font family string by replacing them with "#20".
Create a directory named "issue_304" and place the following files in it:
main.go
package main

import (
  "fmt"

  "github.com/jung-kurt/gofpdf/v2"
)

func main() {

  pdf := gofpdf.New("L", "mm", "A4", "")
  pdf.AddUTF8Font("a b", "", "../NotoSansSC-Regular.ttf")
  pdf.SetFont("a b", "", 16)
  pdf.AddPage()
  pdf.Write(20, "Hello, 世界")
  err := pdf.OutputFileAndClose("issue_304.pdf")
  if err != nil {
    fmt.Print("%s\n", err)
  }
}

go.mod
module issue_304

go 1.13

require github.com/jung-kurt/gofpdf/v2 v2.13.1-0.20190924173108-f7e9373a76e7

go.sum
github.com/jung-kurt/gofpdf/v2 v2.13.1-0.20190924173108-f7e9373a76e7 h1:77NlLaLGz5bzEhvHefYSafiJoKT0yxEbK1qJLuPbrsw=
github.com/jung-kurt/gofpdf/v2 v2.13.1-0.20190924173108-f7e9373a76e7/go.mod h1:RF/RGAP0AS4rd9fVZ6gb7Lbw6178P/AdAxMRW8Kn/Vk=

Then issue go build -v and ./issue_304.

@jung-kurt  The result is ok to me.

@jung-kurt I can't test your fix because I don't use GO, sorry. If you attach it here, I can have a look at the result PDF with PDFDebugger to see if PDFBox has any complaints. (I did so with the first file, and I was told the exact "bad" offsets in log messages)

@THausherr  This is the pdf file I generated locally.
issue_304.pdf

works fine 👍

Thanks, @sify21 and @THausherr -- I will merge changes.

Merged into master (cae7d4739e815a170819d84c5361b05306b2f019) and v2 (f7e9373a76e736ecc3aff31810376ec0486af131). Thanks for your help.


Hub firmware no longer supports Z-Wave association interactions

I have long been a fan of the Z-Wave Tweaker device handler for making one-time configuration changes to a device (that its normal device handler does not consider/support) and then reverting to the normal device handler.
For example, I have 3 Aeotec Nano Dimmer devices that I want associated with each other so that they can talk between themselves without getting SmartThings involved. I got this all to work before using Z-Wave Tweaker as described. This recently broke as one ND dropped off the network and needed to be added back. Of course, when it came back it had a new Device Network Id and the associations broke. When I tried to fix them, Z-Wave Tweaker can no longer do it. It seems that its  HubActions no longer work with the latest Hub firmware.

I have the same issue with my NuTone NWT00Z devices. I used to be able to create association group 1 (zwtAssocGroupId) with tweaker but I started trying a few days ago with a new deployment and now cannot. I can set them using the phone app or the IDE but the device sync fails with:
sync(): Unknown association group. Requesting more info.
I am able to set the group members (zwtAssocGroupMembers) and sync works but as soon as I try to set zwtAssocGroupId, the sync fails.

I believe that it is firmware related.
It worked for me in August and then failed in September.
AFAIK, nothing changed on my end except, perhaps, SmartThings.
I reached out to SmartThings.
The last I heard from them was on September 30:

Our development team are now working on this one. As soon as we get updated, you'll get to know.

In the meantime, I was able to workaround the problem by joining an Aeotec Z-Stick to the SmartThings as a Z-Wave Controller Device. I used the Z-Wave PC Controller from https://www.silabs.com/products/development-tools/software/z-wave to do this and then to program the associations.
This tells me that there is nothing wrong with my devices -- their association groups are configurable. I just can't do it from Z-Wave tweaker anymore.

Good to know. I had a similar idea so I built out a 2nd Z-Wave network using a Vera Edge controller. I was able to set the group id and build the association groups with no issues. The downside was that this solution is super slow for some reason. Turning on/off at the switch takes 6 seconds to actually affect the device which is much, much slower than just using SmartLighting SmartApp. Oddly, control from the PC UI is instant. I suspect the issue is just the nature of having 2 Z-wave networks - collisions and confusion on the devices. The good news is that I learned a lot about moving devices from network to network. The Edge is an interesting device and I still have lots of exploration of its features to do. Since I have several Samsung devices in my network, I don't plan to switch but never say never.
Please post here when you hear about the firmware fix.

I'm experiencing the same issue on hub firmware v000.027.00009. I tried to report this to SmartThings support via email. The zwave.associationV2.associationGet command is not being sent correctly as the target device never responds to it. It apparently worked prior to this firmware version because it was the most recommended approach for setting device associations (SmartThings Hub w/ Z-Wave Tweaker). In fact it was the only reason I bought a SmartThings Hub as I purchased my first Z-Wave switches a few weeks ago specifically for a creating a virtual 3-way.
I ordered a Zooz Z-Wave Plus S2 USB Stick ZST10 ($35). Going to try the Z-Wave PC Controller software linked by @rtyle.

I got ended up going the same route as rtyle  but figuring out how to get the SW was a pita so I wanted to share it. I found a DL link in this (not related) post:
https://community.openhab.org/t/solved-new-uzb-dongle-z-wave-pc-controller-immediately-exits-or-crashes-with-no-error-message/77320/11
There is a significant learning curve to using the SW but I was able to great group 1 and the necessary associations to fix my issue. I would rather see them fix the hub firmware, however as I think that using Tweaker is more straightforward and better documented.

Some good news on the root cause of this issue:
https://community.smartthings.com/t/leviton-vrcs4/4748/267

I just confirmed that FW release<PHONE_NUMBER>1 fixed this issue. I can now create association groups again.


Review get started

Hi Pedro,
I made a small review, trying to provide clear instructions separated in steps.
Thanks

Thanks so much


heroku locally and remotely

[x] Heroku locally and remotely, issue updated #77

I have added a condition based on Environmental Variables, which is like:

First it checks for DB_HEROKU_POSTGRES variable which is Heroku PostgreSQL db locally, If it is not found,

It checks for db.sqlite3 ,If it is not exists,

It checks for DB_HEROKU variable which is Heroku db AWS remotely.

It is working exactly same as the video of a person you shared with me.

Thank you, Best Regards
Umar Ahmed :+1:

Thanks, @UmarGit!
I pulled your changes and I can't figure out where I insert the Postgres URI. For example, line 97-98 reads:
if DB_HEROKU_POSTGRES != 'None':
    DATABASES = {'default': dj_database_url.config(env="DB_HEROKU_POSTGRES", default=DB_HEROKU_POSTGRES, conn_max_age=600)}

For the config method parameters, for default I entered: 'postgres://jckmeibmxypuvn:11033b956dd9cc6011e8efb7d23d56bb277bef7e9634a31ae0f0b304f34e9667@ec2-3-231-241-17.compute-1.amazonaws.com:5432/d9eds0cfpna1li'  - - with quotes and it appears that sqlite continues to be in play when I am expecting Django to serve the data from the remote postgres silo locally when I am at http://<IP_ADDRESS>:8000/tarot_key/4 in my web browser.


psol make error: unknown array size in delete

Environment:

Alpine -> 3.5
libressl and libressl-dev
PSOL -> <IP_ADDRESS>
libPNG -> 1.6.28

Getting below error make:
third_party/re2/src/re2/dfa.cc: In constructor 're2::DFA::State::State()':
third_party/re2/src/re2/dfa.cc:118:10: error: unknown array size in delete
   struct State {
          ^~~~~
third_party/re2/src/re2/dfa.cc: In member function 're2::DFA::State* re2::DFA::CachedState(int*, int, uint32_t)':
third_party/re2/src/re2/dfa.cc:726:9: note: synthesized method 're2::DFA::State::State()' first required here
   State state;
         ^~~~~
make: *** [third_party/re2/re2.target.mk:317: out/Release/obj.target/re2/third_party/re2/src/re2/dfa.o] Error 1

Here is my make instruction:
make BUILDTYPE=Release CXXFLAGS=" -I/usr/include/apr-1 -I/tmp/libpng-$LIBPNG_VERSION -fPIC -D_GLIBCXX_USE_CXX11_ABI=0" CFLAGS=" -I/usr/include/apr-1 -I/tmp/libpng-$LIBPNG_VERSION -fPIC -D_GLIBCXX_USE_CXX11_ABI=0"
make psol BUILDTYPE=Release CXXFLAGS=" -I/usr/include/apr-1 -I/tmp/libpng-$LIBPNG_VERSION -fPIC -D_GLIBCXX_USE_CXX11_ABI=0" CFLAGS=" -I/usr/include/apr-1 -I/tmp/libpng-$LIBPNG_VERSION -fPIC -D_GLIBCXX_USE_CXX11_ABI=0"'
Anyone knows why I am getting this?

Looks like we need to pick this change up:
https://github.com/google/re2/commit/b94b7cd42e9f02673cd748c1ac1d16db4052514c
On Thu, Mar 2, 2017 at 11:23 AM, Bright Dadson<EMAIL_ADDRESS>wrote:

Environment:

Alpine -> 3.5
PSOL -> <IP_ADDRESS>
libPNG -> 1.6.28

Getting below error make:
third_party/re2/src/re2/dfa.cc: In constructor 're2::DFA::State::State()':
third_party/re2/src/re2/dfa.cc:118:10: error: unknown array size in delete
struct State {
^~~~~
third_party/re2/src/re2/dfa.cc: In member function 're2::DFA::State* re2::DFA::CachedState(int*, int, uint32_t)':
third_party/re2/src/re2/dfa.cc:726:9: note: synthesized method 're2::DFA::State::State()' first required here
State state;
^~~~~
make: *** [third_party/re2/re2.target.mk:317: out/Release/obj.target/re2/third_party/re2/src/re2/dfa.o] Error 1
Here is my make instruction:
make BUILDTYPE=Release CXXFLAGS=" -I/usr/include/apr-1
-I/tmp/libpng-$LIBPNG_VERSION -fPIC -D_GLIBCXX_USE_CXX11_ABI=0" CFLAGS="
-I/usr/include/apr-1 -I/tmp/libpng-$LIBPNG_VERSION -fPIC
-D_GLIBCXX_USE_CXX11_ABI=0"
make psol BUILDTYPE=Release CXXFLAGS=" -I/usr/include/apr-1
-I/tmp/libpng-$LIBPNG_VERSION -fPIC -D_GLIBCXX_USE_CXX11_ABI=0" CFLAGS="
-I/usr/include/apr-1 -I/tmp/libpng-$LIBPNG_VERSION -fPIC
-D_GLIBCXX_USE_CXX11_ABI=0"'
Anyone knows why I am getting this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pagespeed/mod_pagespeed/issues/1504, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ADl1ROJ_JYuV9N-asjn4FYp_pIHEpzKRks5rhu0YgaJpZM4MRNMG
.

I have just patched it in the meantime.
--- a/re2/dfa.cc
+++ b/re2/dfa.cc
@@ -123,7 +123,15 @@ class DFA {
     uint32_t flag_;     // Empty string bitfield flags in effect on the way
                         // into this state, along with kFlagMatch if this
                         // is a matching state.
+
+// Work around the bug affecting flexible array members in GCC 6.1 and 6.2.
+// (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70932)
+#if !defined(__clang__) && defined(__GNUC__) && __GNUC__ == 6 && __GNUC_MINOR__ >= 1
+    std::atomic<State*> next_[0];   // Outgoing arrows from State,
+#else
     std::atomic<State*> next_[];    // Outgoing arrows from State,
+#endif
+
                         // one per input byte class
   };

I am ending up with -> #1460

Maybe #include <limits.h> in whatever file that is?

@morlovich I have tried your suggestion. I am still getting:
In file included from third_party/grpc/src/src/core/lib/tsi/transport_security_interface.h:38:0,
                 from third_party/grpc/src/src/core/lib/security/transport/security_connector.h:40,
                 from third_party/grpc/src/src/core/lib/security/credentials/credentials.h:45,
                 from third_party/grpc/src/src/core/lib/surface/init_secure.c:40:
/usr/include/fortify/stdlib.h: In function 'realpath':
/usr/include/fortify/stdlib.h:42:2: error: #error PATH_MAX unset. A fortified realpath will not work.
 #error PATH_MAX unset. A fortified realpath will not work.
  ^~~~~
make: *** [third_party/grpc/grpc_core.target.mk:488: out/Release/obj.target/grpc_core/third_party/grpc/src/src/core/lib/surface/init_secure.o] Error 1

I have the same issue with <IP_ADDRESS>

Same issue on <IP_ADDRESS> (libpng 1.2.56, alpine 3.6)

I think @morlovich addressed this in https://github.com/pagespeed/mod_pagespeed/commit/8488f6db18e7a90b1c3141835610f88c62c4bdc7#diff-44841ae91d860d39f535f67ca0d2e501, but there is no release available yet that contains that change.
(Bleeding edge builds will include it, though)


Unsoundness: Objects in the arena are allowed to borrow from the arena

Example code demonstrating the problem:
use erased_type_arena::Arena;

struct Helper<'a>(&'a Arena);
impl Drop for Helper<'_> {
    fn drop(&mut self) {
        self.0.alloc(5);
    }
}
fn main() {
    let arena = Box::new(Arena::new());
    arena.alloc(Helper(&arena));
    drop(arena);
}

When Helper is dropped, it holds an &Arena, which conflicts with the supposedly unique &mut Arena held by the fn drop of the caller. More concretely, you're able to allocate in the arena even during drop which is obviously broken.
Miri rightfuly complains about this - the error is rather obtuse but what it's trying to say is that your &Arena is invalid:
error: Undefined Behavior: trying to reborrow for SharedReadWrite at alloc978, but parent tag <2004> does not have an appropriate item in the borrow stack
  --> src/main.rs:6:9
   |
6  |         self.0.alloc(5);
   |         ^^^^^^^^^^^^^^^ trying to reborrow for SharedReadWrite at alloc978, but parent tag <2004> does not have an appropriate item in the borrow stack
   |
   = help: this indicates a potential bug in the program: it performed an invalid operation, but the rules it violated are still experimental
   = help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information

   = note: inside `<Helper as std::ops::Drop>::drop` at src/main.rs:6:9
   = note: inside `std::ptr::drop_in_place::<Helper> - shim(Some(Helper))` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:188:1
   = note: inside closure at ~/.local/share/cargo/registry/src/github.com-1ecc6299db9ec823/erased-type-arena-0.3.1/src/lib.rs:443:13
   = note: inside `<std::boxed::Box<dyn std::ops::FnMut()> as std::ops::FnMut<()>>::call_mut` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/boxed.rs:1861:9
   = note: inside `<erased_type_arena::ArenaBox as std::ops::Drop>::drop` at ~/.local/share/cargo/registry/src/github.com-1ecc6299db9ec823/erased-type-arena-0.3.1/src/lib.rs:463:9
   = note: inside `std::ptr::drop_in_place::<erased_type_arena::ArenaBox> - shim(Some(erased_type_arena::ArenaBox))` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:188:1
   = note: inside `std::ptr::drop_in_place::<erased_type_arena::utils::linked_list::ConcurrentLinkedListNode<erased_type_arena::ArenaBox>> - shim(Some(erased_type_arena::utils::linked_list::ConcurrentLinkedListNode<erased_type_arena::ArenaBox>))` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:188:1
   = note: inside `std::ptr::drop_in_place::<std::boxed::Box<erased_type_arena::utils::linked_list::ConcurrentLinkedListNode<erased_type_arena::ArenaBox>>> - shim(Some(std::boxed::Box<erased_type_arena::utils::linked_list::ConcurrentLinkedListNode<erased_type_arena::ArenaBox>>))` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:188:1
   = note: inside `std::mem::drop::<std::boxed::Box<erased_type_arena::utils::linked_list::ConcurrentLinkedListNode<erased_type_arena::ArenaBox>>>` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/mem/mod.rs:909:24
   = note: inside `<erased_type_arena::utils::linked_list::ConcurrentLinkedList<erased_type_arena::ArenaBox> as std::ops::Drop>::drop` at ~/.local/share/cargo/registry/src/github.com-1ecc6299db9ec823/erased-type-arena-0.3.1/src/utils/linked_list.rs:57:17
   = note: inside `std::ptr::drop_in_place::<erased_type_arena::utils::linked_list::ConcurrentLinkedList<erased_type_arena::ArenaBox>> - shim(Some(erased_type_arena::utils::linked_list::ConcurrentLinkedList<erased_type_arena::ArenaBox>))` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:188:1
   = note: inside `std::ptr::drop_in_place::<erased_type_arena::Arena> - shim(Some(erased_type_arena::Arena))` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:188:1
   = note: inside `std::ptr::drop_in_place::<std::boxed::Box<erased_type_arena::Arena>> - shim(Some(std::boxed::Box<erased_type_arena::Arena>))` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/mod.rs:188:1
   = note: inside `std::mem::drop::<std::boxed::Box<erased_type_arena::Arena>>` at ~/.local/share/rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/mem/mod.rs:909:24

One potential solution is to add a lifetime parameter to Arena and ArenaBox, with ArenaBox containing a PhantomData<&'a ()>. Then the signature of alloc can be changed to:
pub fn alloc<'s, T: 'a>(&self, value: T) -> AllocMut<'s, T>

I believe this resolves the soundness issue.

Note that adding a lifetime parameter to Arena should be done anyway, because of a separate soundness use-after-free issue (that I haven't bothered to open another issue for since the fix is the same as this one's):
use erased_type_arena::Arena;

fn main() {
    let arena = Arena::new();
    let boxed = Box::new(5);
    arena.alloc(Helper(&boxed));
}

struct Helper<'a>(&'a i32);
impl Drop for Helper<'_> {
    fn drop(&mut self) {
        println!("{}", self.0);
    }
}

Hmm, I tried to fix this soundness issue but it seems like it severely reduces the use-cases of the crate - namely, multiple data structures in the Arena can no longer reference each other since they're all required to live longer than the arena itself. This makes me think that the fundamental concept of this crate is unsound, and the crate can't exist at all - unless there's some workaround I don't know of.


added properties object to calendarDay, so it can be used in custom template

@petertakacs Is there any way you could remove clndr.min.js from this pull request? I only ask because it'll conflict and I'll have to recompile, which isn't a huge deal I'd just prefer not to.

Nevermind, I was able to do it locally :P


add my duck and contribution

Description
Here is my Hacktoberfest 2023 contribution to "The Duck Gallery".

Hello @mandeep-s1ngh , thanks for your contribution ! I think you use a code formatter which change all the file. Can you check this to have only one line in changes please ?

Hi @jeanphibaconnais, yes, it was my prettier formatting on save. I prefer double quotes over single quotes.
I have made the necessary changes, hope this is OK now.

Yes it's good ! Thanks !

ok, great, thank you so much for mentioning it actually. I ended up learning a git command that could be very useful if I run into this sort of situation again. Also, thank you so much for letting me contribute to this project.