text:
Build errors for libtensorflow_inference.so

I am trying to build libtensorflow_inference.so, in order to run a TF model in an Android app.  I found the following command in issue #6166, however the command is failing.  I reported an earlier error message in that issue, but now the error message has changed and it fails completely.
It is worth noting that I am able to compile the Inception demo app with no trouble (from inside Android Studio), so I think the full tool chain is functional.
I added the verbose option to try to troubleshoot the issue (not that it helped):
$  bazel build //tensorflow/contrib/android:libtensorflow_inference.so    --crosstool_top=//external:android/crosstool    --host_crosstool_top=@bazel_tools//tools/cpp:toolchain    --cpu=armeabi-v7a --verbose_failures
I am running on MacOS (10.12.1) with TF0.12 (SHA=46b7b6).
Installed version of CUDA and cuDNN: None
Bazel Verion:
Build label: 0.4.2-homebrew
Build target: bazel-out/local-opt/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
Build time: Thu Dec 8 03:17:26 2016 (1481167046)
Build timestamp: 1481167046
Build timestamp as int: 1481167046

Here is the error message:
WARNING: /Users/kevin/tensorflow/tensorflow/core/BUILD:779: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: /Users/kevin/tensorflow/tensorflow/core/BUILD:779:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:bounds_check.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/kevin/tensorflow/tensorflow/core/BUILD:779: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: /Users/kevin/tensorflow/tensorflow/core/BUILD:779: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.
<snip>
WARNING: /Users/kevin/tensorflow/tensorflow/core/BUILD:779: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: /Users/kevin/tensorflow/tensorflow/core/BUILD:779: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.
INFO: Found 1 target...
ERROR: /Users/kevin/tensorflow/tensorflow/core/BUILD:163:1: C++ compilation of rule '//tensorflow/core:protos_all_cc' failed: sandbox-exec failed: error executing command
  (cd /private/var/tmp/_bazel_kevin/a09094529daf7e22afa1fbacb9484a3a/bazel-sandbox/4c850042-6906-474b-9554-e958a1aadaeb-3/execroot/tensorflow && \
  exec env - \
    PATH=/Users/kevin/anaconda2/bin:/Users/kevin/anaconda/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin \
    TMPDIR=/var/folders/cm/1r6x6rbj7hn_51qvfjzj7nx80000gn/T/ \
  /usr/bin/sandbox-exec -f /private/var/tmp/_bazel_kevin/a09094529daf7e22afa1fbacb9484a3a/bazel-sandbox/4c850042-6906-474b-9554-e958a1aadaeb-3/sandbox.sb /bin/false -MD -MF bazel-out/stub_armeabi-v7a-fastbuild/bin/tensorflow/core/_objs/protos_all_cc/tensorflow/core/framework/device_attributes.pb.pic.d '-frandom-seed=bazel-out/stub_armeabi-v7a-fastbuild/bin/tensorflow/core/_objs/protos_all_cc/tensorflow/core/framework/device_attributes.pb.pic.o' -fPIC -iquote . -iquote bazel-out/stub_armeabi-v7a-fastbuild/genfiles -iquote external/protobuf -iquote bazel-out/stub_armeabi-v7a-fastbuild/genfiles/external/protobuf -iquote external/bazel_tools -iquote bazel-out/stub_armeabi-v7a-fastbuild/genfiles/external/bazel_tools -isystem external/protobuf/src -isystem bazel-out/stub_armeabi-v7a-fastbuild/genfiles/external/protobuf/src -isystem external/bazel_tools/tools/cpp/gcc3 -Wno-unknown-warning-option -Wno-unused-but-set-variable -Wno-sign-compare -c bazel-out/stub_armeabi-v7a-fastbuild/genfiles/tensorflow/core/framework/device_attributes.pb.cc -o bazel-out/stub_armeabi-v7a-fastbuild/bin/tensorflow/core/_objs/protos_all_cc/tensorflow/core/framework/device_attributes.pb.pic.o).
sandbox-exec: /bin/false: No such file or directory
Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build
INFO: Elapsed time: 44.632s, Critical Path: 2.86s

BTW, I chose to generate libtensorflow_inference.so because I only need to compute an inference based on an existing graph, from within an Android app.  The app is to take a 128 element numeric vector and classify a result to one of six classes.

@kevinashaw Yes, this is the library you want, along with the corresponding Java src that //tensorflow/contrib/android:android_tensorflow_inference_java will place in a Jar file for you.
On OSX false may be found in /usr/bin/, not /bin, though I'm not sure if that's the root cause of the problem. Can you try bazel clean and then rebuild with --sandbox_debug enabled? That may provide a more informative error.

Thank you.   I will try that tonight.
Where do you recommend putting the .so file so that Android Studio can find it?
In the meantime I was able to generate libtensorflow_demo.so using:
bazel build //tensorflow/examples/android:tensorflow_native_libs --crosstool_top=//external:android/crosstool --cpu=$CPU --host_crosstool_top=@bazel_tools//tools/cpp:toolchain

I placed it in both ~project/libs and ~project/src/app/src/main/jniLibs, but I have been unable to get Android Studio / Gradle to recognize it.  For example, in the following code, org.tensorflow is not resolving:
{
package com.foobar.tfdemo;

import org.tensorflow.contrib.android.TensorFlowInferenceInterface;

public class TensorFlowClassifier implements Classifier {
// do something
}

I'm wondering if there is some special location or process for bringing the .so files in to a project?
Aside: I even used readelf on the .so file (results attached) to see if the proper entry points existed, but don't see anything.  I've tried to fully document the issue in SO: http://stackoverflow.com/questions/41176321/tensorflow-android-studio-and-bazel-setting-up-a-new-project
Thanks for the help!
elf.txt

@kevinshaw You can try using build.gradle to have AS automatically build and install the native libs with gradle (calling out to bazel).
If you're doing it manually the .so will probably need to go in libs/armeabi-v7a. You'll also need to copy over the Jar produced from building //tensorflow/contrib/android:android_tensorflow_inference_java, or alternatively just copy over the Java file itself.

Closing; please update if there are any remaining issues.
It's also worth mentioning that we are planning on providing an AAR solution soon that should make integrating TF into Android apps in Android Studio much simpler if you do not need to modify native C/C++ code.

I have a similar problem on OSX when running
bazel build //tensorflow/contrib/android:libtensorflow_inference.so    --rosstool_top=//external:android/crosstool    --host_crosstool_top=@bazel_tools//tools/cpp:toolchain    --cpu=armeabi-v7a --sandbox_debug --verbose_failures
I get the following error
INFO: Found 1 target...
ERROR: /private/var/tmp/_bazel_jean-baptistebuisson/230f1e1bd98ef893dd2fae3f5b464a27/external/protobuf/BUILD:73:1: C++ compilation of rule '@protobuf//:protobuf_lite' failed: false failed: error executing command
  (cd /private/var/tmp/_bazel_jean-baptistebuisson/230f1e1bd98ef893dd2fae3f5b464a27/execroot/tensorflow && \
  exec env - \
    PATH=/Users/jean-baptistebuisson/anaconda/bin:/Library/Frameworks/Python.framework/Versions/3.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin \
    TF_NEED_CUDA=0 \
    TF_NEED_OPENCL=0 \
    TMPDIR=/var/folders/cz/w7p3l65n35g2dd96x3pdfm1h0000gn/T/ \
  /bin/false -MD -MF bazel-out/stub_armeabi-v7a-py3-opt/bin/external/protobuf/_objs/protobuf_lite/external/protobuf/src/google/protobuf/generated_message_util.pic.d '-frandom-seed=bazel-out/stub_armeabi-v7a-py3-opt/bin/external/protobuf/_objs/protobuf_lite/external/protobuf/src/google/protobuf/generated_message_util.pic.o' -fPIC -iquote external/protobuf -iquote bazel-out/stub_armeabi-v7a-py3-opt/genfiles/external/protobuf -iquote external/bazel_tools -iquote bazel-out/stub_armeabi-v7a-py3-opt/genfiles/external/bazel_tools -isystem external/protobuf/src -isystem bazel-out/stub_armeabi-v7a-py3-opt/genfiles/external/protobuf/src -isystem external/bazel_tools/tools/cpp/gcc3 -DHAVE_PTHREAD -Wall -Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -Wno-unused-function -c external/protobuf/src/google/protobuf/generated_message_util.cc -o bazel-out/stub_armeabi-v7a-py3-opt/bin/external/protobuf/_objs/protobuf_lite/external/protobuf/src/google/protobuf/generated_message_util.pic.o): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
process-wrapper: execvp("/bin/false", ...): No such file or directory
Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build
INFO: Elapsed time: 9.860s, Critical Path: 0.63s

And bazel clean did not help

Hi,
I am having the same issue....The bazel build runs for a very long time and throws up error :(
bazel clean doesnt help...
Can some one please help....

@azainab What is your actual error? It's not included in the screenshots you posted.

It runs for a whole very long time and has a big list of lines...Is there a way I can see the 3 errors? I tried the --verbose_failures but it says 0 targets found....
If yes, I run a command to see the errors and post it...
Few warnings and errors I got....
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:bounds_check.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:ops_util.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917: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: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:devices.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:devices.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:grappler_item.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:grappler_item.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:op_types.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:op_types.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:utils.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler:utils.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/clusters:cluster.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/clusters:cluster.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/inputs:utils.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/inputs:utils.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:auto_parallel.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:auto_parallel.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:constant_folding.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:constant_folding.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:graph_optimizer.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:graph_rewriter.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:graph_rewriter.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:layout_optimizer.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:layout_optimizer.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:memory_optimizer.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:memory_optimizer.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:meta_optimizer.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:meta_optimizer.h' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:model_pruner.cc' directly. You should either move the file to this package or depend on an appropriate rule there.
WARNING: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/core/BUILD:917:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/grappler/optimizers:model_pruner.h' directly. You should either move the file to this package or depend on an appropriate rule there.
INFO: From Compiling external/protobuf/src/google/protobuf/compiler/js/embed.cc [for host]:
external/protobuf/src/google/protobuf/compiler/js/embed.cc:37:12: warning: unused variable 'output_file' [-Wunused-const-variable]
const char output_file[] = "well_known_types_embed.cc";
^

@azainab These are warnings, not the error, which would be just above the section from your screenshot.
Are you using NDK r12b?

I am using r14b...

That the problem then. We recommend r12b as r14b currently has incompatibilities with TF due to the different default flags used by Clang.

Error I got...
ERROR: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/contrib/android/BUILD:29:1: C++ compilation of rule '//tensorflow/contrib/android:android_tensorflow_inference_jni' failed: Process exited with status 1 [sandboxed].
tensorflow/contrib/android/asset_manager_filesystem.cc:97:26: error: use of undeclared identifier 'AAsset_seek64'; did you mean 'AAsset_seek'?
off64_t new_offset = AAsset_seek64(asset.get(), offset, SEEK_SET);
^~~~~~~~~~~~~
AAsset_seek
external/androidndk/ndk/platforms/android-12/arch-arm/usr/include/android/asset_manager.h:96:7: note: 'AAsset_seek' declared here
off_t AAsset_seek(AAsset* asset, off_t offset, int whence);
^
tensorflow/contrib/android/asset_manager_filesystem.cc:98:22: error: use of undeclared identifier 'AAsset_getLength64'; did you mean 'AAsset_getLength'?
off64_t length = AAsset_getLength64(asset.get());
^~~~~~~~~~~~~~~~~~
AAsset_getLength
external/androidndk/ndk/platforms/android-12/arch-arm/usr/include/android/asset_manager.h:113:7: note: 'AAsset_getLength' declared here
off_t AAsset_getLength(AAsset* asset);
^
tensorflow/contrib/android/asset_manager_filesystem.cc:158:12: error: use of undeclared identifier 'AAsset_openFileDescriptor64'; did you mean 'AAsset_openFileDescriptor'?
int fd = AAsset_openFileDescriptor64(asset.get(), &start, &length);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
AAsset_openFileDescriptor
external/androidndk/ndk/platforms/android-12/arch-arm/usr/include/android/asset_manager.h:126:5: note: 'AAsset_openFileDescriptor' declared here
int AAsset_openFileDescriptor(AAsset* asset, off_t* outStart, off_t* outLength);
^
tensorflow/contrib/android/asset_manager_filesystem.cc:158:53: error: cannot initialize a parameter of type 'off_t ' (aka 'long ') with an rvalue of type 'off64_t ' (aka 'long long ')
int fd = AAsset_openFileDescriptor64(asset.get(), &start, &length);
^~~~~~
external/androidndk/ndk/platforms/android-12/arch-arm/usr/include/android/asset_manager.h:126:53: note: passing argument to parameter 'outStart' here
int AAsset_openFileDescriptor(AAsset asset, off_t outStart, off_t outLength);
^
tensorflow/contrib/android/asset_manager_filesystem.cc:173:14: error: use of undeclared identifier 'AAsset_getLength64'; did you mean 'AAsset_getLength'?
length = AAsset_getLength64(asset.get());
^~~~~~~~~~~~~~~~~~
AAsset_getLength
external/androidndk/ndk/platforms/android-12/arch-arm/usr/include/android/asset_manager.h:113:7: note: 'AAsset_getLength' declared here
off_t AAsset_getLength(AAsset asset);
^
tensorflow/contrib/android/asset_manager_filesystem.cc:214:8: error: use of undeclared identifier 'AAsset_getLength64'; did you mean 'AAsset_getLength'?
s = AAsset_getLength64(asset.get());
^~~~~~~~~~~~~~~~~~
AAsset_getLength
external/androidndk/ndk/platforms/android-12/arch-arm/usr/include/android/asset_manager.h:113:7: note: 'AAsset_getLength' declared here
off_t AAsset_getLength(AAsset asset);
^
6 errors generated.
Use --strategy=CppCompile=standalone to disable sandboxing for the failing actions.
Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build
Use --verbose_failures to see the command lines of failed build steps.

Can you give more details? What ndk are you using? What command are you using to build?

I posted the command in my previous posts..
Here it is:
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
ndk version - r14b.. As suggested I changed it to r12b and running it... It takes a really long time to run...

I ran using ndk r12b I got the error below:
ERROR: /Users/zuni/Documents/androidstudy/Juanjors_AndroidMeneame/tensorflow/contrib/android/BUILD:29:1: C++ compilation of rule '//tensorflow/contrib/android:android_tensorflow_inference_jni' failed: Process exited with status 1 [sandboxed].
tensorflow/contrib/android/asset_manager_filesystem.cc: In member function 'virtual tensorflow::Status tensorflow::{anonymous}::RandomAccessFileFromAsset::Read(tensorflow::uint64, size_t, tensorflow::StringPiece*, char*) const':
tensorflow/contrib/android/asset_manager_filesystem.cc:97:69: error: 'AAsset_seek64' was not declared in this scope
off64_t new_offset = AAsset_seek64(asset.get(), offset, SEEK_SET);
^
tensorflow/contrib/android/asset_manager_filesystem.cc:98:52: error: 'AAsset_getLength64' was not declared in this scope
off64_t length = AAsset_getLength64(asset.get());
^
tensorflow/contrib/android/asset_manager_filesystem.cc: In member function 'virtual tensorflow::Status tensorflow::AssetManagerFileSystem::NewReadOnlyMemoryRegionFromFile(const string&, std::unique_ptrtensorflow::ReadOnlyMemoryRegion)':
tensorflow/contrib/android/asset_manager_filesystem.cc:158:68: error: 'AAsset_openFileDescriptor64' was not declared in this scope
int fd = AAsset_openFileDescriptor64(asset.get(), &start, &length);
^
tensorflow/contrib/android/asset_manager_filesystem.cc:173:44: error: 'AAsset_getLength64' was not declared in this scope
length = AAsset_getLength64(asset.get());
^
tensorflow/contrib/android/asset_manager_filesystem.cc: In member function 'virtual tensorflow::Status tensorflow::AssetManagerFileSystem::GetFileSize(const string&, tensorflow::uint64)':
tensorflow/contrib/android/asset_manager_filesystem.cc:214:38: error: 'AAsset_getLength64' was not declared in this scope
*s = AAsset_getLength64(asset.get());
^
Use --strategy=CppCompile=standalone to disable sandboxing for the failing actions.
Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build
Use --verbose_failures to see the command lines of failed build steps.

The Tensorflow TF Detect for android example draws boxes around humans seen by the camera, however I would like to train a model to detect things other than humans.

vagrant@vagrant:~/tensorflow$ ../.bazel/bin/bazel build -c opt --copt="-DSELECTIVE_REGISTRATION" --copt="-DSUPPORT_SELECTIVE_REGISTRATION" //tensorflow/contrib/android:libtensorflow_inference.so --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --crosstool_top=//external:android/crosstool --cpu=armeabi-v7a --verbose_failures
WARNING: /home/vagrant/.cache/bazel/_bazel_vagrant/2608380002b7e82b3d07fef59e49e485/external/protobuf_archive/WORKSPACE:1: Workspace name in /home/vagrant/.cache/bazel/_bazel_vagrant/2608380002b7e82b3d07fef59e49e485/external/protobuf_archive/WORKSPACE (@com_google_protobuf) does not match the name given in the repository's definition (@protobuf_archive); this will cause a build error in future versions
WARNING: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:bounds_check.h' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525:12: in srcs attribute of cc_library rule //tensorflow/core:android_tensorflow_lib_lite: please do not import '//tensorflow/core/kernels:ops_util.cc' directly. You should either move the file to this package or depend on an appropriate rule there
WARNING: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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: /home/vagrant/tensorflow/tensorflow/core/BUILD:1525: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
INFO: Analysed target //tensorflow/contrib/android:libtensorflow_inference.so (29 packages loaded).
INFO: Found 1 target...
ERROR: /home/vagrant/.cache/bazel/_bazel_vagrant/2608380002b7e82b3d07fef59e49e485/external/fft2d/BUILD.bazel:21:1: C++ compilation of rule '@fft2d//:fft2d' failed (Exit 1): false failed: error executing command
  (cd /home/vagrant/.cache/bazel/_bazel_vagrant/2608380002b7e82b3d07fef59e49e485/execroot/org_tensorflow && \
  exec env - \
    PWD=/proc/self/cwd \
  /bin/false -MD -MF bazel-out/armeabi-v7a-opt/bin/external/fft2d/_objs/fft2d/external/fft2d/fft/fftsg.pic.d -fPIC -iquote external/fft2d -iquote bazel-out/armeabi-v7a-opt/genfiles/external/fft2d -iquote external/bazel_tools -iquote bazel-out/armeabi-v7a-opt/genfiles/external/bazel_tools -DSELECTIVE_REGISTRATION -DSUPPORT_SELECTIVE_REGISTRATION -c external/fft2d/fft/fftsg.c -o bazel-out/armeabi-v7a-opt/bin/external/fft2d/_objs/fft2d/external/fft2d/fft/fftsg.pic.o)
Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build
INFO: Elapsed time: 211.430s, Critical Path: 13.76s
INFO: 190 processes, local.
FAILED: Build did NOT complete successfully

I got this error even after cleaning the bazel.
Please anyone could help thanks.

I cleaned hazel and gave the following 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++11  --verbose_failures --sandbox_debug
it gave me the following error:
ERROR: /private/var/tmp/_bazel_root/23994111945cccf7235ecf4d9dc9fbce/external/com_google_absl/absl/numeric/BUILD.bazel:26:1: C++ compilation of rule '@com_google_absl//absl/numeric:int128' failed (Exit 1): clang failed: error executing command    (cd /private/var/tmp/_bazel_root/23994111945cccf7235ecf4d9dc9fbce/execroot/org_tensorflow && \   exec env - \     ANDROID_BUILD_TOOLS_VERSION=28.0.3 \     ANDROID_NDK_API_LEVEL=18 \     ANDROID_NDK_HOME=/Users/ivlab/Downloads/android-ndk-r14b/ \     ANDROID_SDK_API_LEVEL=28 \     ANDROID_SDK_HOME=/Users/ivlab/library/Android/Sdk \     BAZEL_USE_CPP_ONLY_TOOLCHAIN=1 \     PATH=/Library/Frameworks/Python.framework/Versions/3.6/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/ivlab/bin \     PWD=/proc/self/cwd \     PYTHON_BIN_PATH=/Library/Frameworks/Python.framework/Versions/3.6/bin/python3 \     PYTHON_LIB_PATH=/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages \     TF_CONFIGURE_IOS=0 \     TF_DOWNLOAD_CLANG=1 \     TF_NEED_CUDA=0 \     TF_NEED_OPENCL_SYCL=0 \     TF_NEED_ROCM=0 \   external/androidndk/ndk/toolchains/llvm/prebuilt/darwin-x86_64/bin/clang -gcc-toolchain external/androidndk/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64 -fpic -ffunction-sections -funwind-tables -fstack-protector-strong -Wno-invalid-command-line-argument -Wno-unused-command-line-argument -no-canonical-prefixes -fno-integrated-as -target armv7-none-linux-androideabi '-march=armv7-a' '-mfloat-abi=softfp' '-mfpu=vfpv3-d16' -mthumb -Os -g -DNDEBUG -MD -MF bazel-out/armeabi-v7a-opt/bin/external/com_google_absl/absl/numeric/_objs/int128/int128.d '-frandom-seed=bazel-out/armeabi-v7a-opt/bin/external/com_google_absl/absl/numeric/_objs/int128/int128.o' -iquote external/com_google_absl -iquote bazel-out/armeabi-v7a-opt/genfiles/external/com_google_absl -iquote bazel-out/armeabi-v7a-opt/bin/external/com_google_absl '-std=c++11' -Wall -Wextra -Wcast-qual -Wconversion-null -Wmissing-declarations -Woverlength-strings -Wpointer-arith -Wunused-local-typedefs -Wunused-result -Wvarargs -Wvla -Wwrite-strings -Wno-missing-field-initializers -Wno-sign-compare '--sysroot=external/androidndk/ndk/platforms/android-18/arch-arm' -isystem external/androidndk/ndk/sources/cxx-stl/gnu-libstdc++/4.9/include -isystem external/androidndk/ndk/sources/cxx-stl/gnu-libstdc++/4.9/libs/armeabi-v7a/include -isystem external/androidndk/ndk/sources/cxx-stl/gnu-libstdc++/4.9/include/backward -c external/com_google_absl/absl/numeric/int128.cc -o bazel-out/armeabi-v7a-opt/bin/external/com_google_absl/absl/numeric/_objs/int128/int128.o) Execution platform: @bazel_tools//platforms:host_platform external/com_google_absl/absl/numeric/int128.cc:139:59: error: no member named 'trunc' in namespace 'std'; did you mean simply 'trunc'?   uint64_t w0 = static_cast<uint64_t>(static_cast<double>(std::trunc(v)));                                                           ^~~~~~~~~~                                                           trunc external/androidndk/ndk/platforms/android-18/arch-arm/usr/include/math.h:284:8: note: 'trunc' declared here double  trunc(double);         ^ external/com_google_absl/absl/numeric/int128.cc:141:59: error: no member named 'trunc' in namespace 'std'; did you mean simply 'trunc'?   uint64_t w1 = static_cast<uint64_t>(static_cast<double>(std::trunc(v)));                                                           ^~~~~~~~~~                                                           trunc external/androidndk/ndk/platforms/android-18/arch-arm/usr/include/math.h:284:8: note: 'trunc' declared here double  trunc(double);         ^ external/com_google_absl/absl/numeric/int128.cc:143:59: error: no member named 'trunc' in namespace 'std'; did you mean simply 'trunc'?   uint64_t w2 = static_cast<uint64_t>(static_cast<double>(std::trunc(v)));                                                           ^~~~~~~~~~                                                           trunc external/androidndk/ndk/platforms/android-18/arch-arm/usr/include/math.h:284:8: note: 'trunc' declared here double  trunc(double);         ^ 3 errors generated. Target //tensorflow/contrib/android:libtensorflow_inference.so failed to build INFO: Elapsed time: 134.270s, Critical Path: 17.16s INFO: 235 processes: 235 local. FAILED: Build did NOT complete successfully
Please help.

I posted the command in my previous posts..
Here it is:
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
ndk version - r14b.. As suggested I changed it to r12b and running it... It takes a really long time to run...

Google Should concentrate on Supporting Higher Version of NDK rather 14b ,
NDK 19 and NDk20 compiler are more otimized and inference code runs much faster..
There is considerable slowness if you use older NDK( i.e 14b) .. but its very painful to compile with newer ndk as google official dont support them

authors: VacheMumchyan alokprasad andrewharp azainab japer21 jbuisson1 kevinashaw sodiumLights


text:
keep_checkpoint_every_n_hours is ignored

I think that when creating a new saver here, the keep_checkpoint_every_n_hours flag from the RunConfig should be passed to it.

Thanks for reporting! I've submitted the fix.

Thanks for reporting! I've submitted the fix.

source: gharchive/issue

authors: dennybritz terrytangyuan

repo: tensorflow/tensorflow

license_type: permissive

license_source: github-api


text:
Wrong explanation about an argument of tflite interpreter

Issue type
Documentation Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
Current master branch
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I was using tensorflow.lite.Interpreter, and reading the comments to understand the parameters.
According to the comments, the num_threads value can be set to -1 or any non-negative value (or None).
https://github.com/tensorflow/tensorflow/blob/b297295711589c2d71880a046333e6ec095c6d7d/tensorflow/lite/python/interpreter.py#L409-L416
However, the actual code restricts that the num_threads value is set to 1 or higher (or None).
https://github.com/tensorflow/tensorflow/blob/b297295711589c2d71880a046333e6ec095c6d7d/tensorflow/lite/python/interpreter.py#L460-L464
Standalone code to reproduce the issue
N/A

Relevant log output
No response

@illian01,
Thank you for reporting the documentation issue. We have raised the PR for the changes which were suggested. The pr has been assigned for reviewing and once it is merged this issue will move to closed status.
https://github.com/tensorflow/tensorflow/pull/68866
Thank you!


text:
Does Crypto.com have live customer support? Can I live chat with Crypto.com support? {Help-US}}}

Crypto.com's customer support team 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) works continuously, all day and night, to assist customers. They are available 24 hours a day, 7 days a week to answer𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) any questions or concerns you may have, ensuring prompt assistance at any time.
In the world of cryptocurrencies, security and customer support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)are key factors that users consider before choosing a platform to trade or invest. One popular platform in the market is Crypto.com, known for its user-friendly interface and secure transactions. But the burning question remains - does Crypto.com have 24/7 support? Let's dive into this frequently asked question and explore what Crypto.com 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬 𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)has to offer in terms of customer assistance.
Yes, Crypto.com offers 24/7 support through 1-(206)-683-0106 phone and live chat. For assistance in the USA, you can call𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) . For the UK, use the same number,𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) . You can also access live chat support by clicking the "Contact Us" button in the help center on their website.
FAQs about Crypto.com support
Is Crypto.com support available 24/7?
Crypto.com offers customer support services to its users around the clock, 24 hours a day, 7 days a week. 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)This ensures that users can reach out for help whenever they encounter any issues or have inquiries regarding their accounts or transactions. So, rest assured that Crypto.com 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)has your back at any time of the day.
How can I contact Crypto.com customer support?
There are several ways to get in touch with Crypto.com's support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)team. You can reach them via email, live chat on their website, or by submitting a support ticket through their platform. Additionally, Crypto.com provides𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) a comprehensive FAQ section where you can find answers to common questions and troubleshooting guides.
What kind of issues can Crypto.com support help with?
Crypto.com's customer support team𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) is well-equipped to assist you with a wide range of issues, including account verification, transaction inquiries, security concerns, and technical troubleshooting. Whether you're a beginner or an experienced trader, Crypto.com's support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)staff is there to provide the guidance and assistance you need.
Are there any limitations to Crypto.com's customer support?
While Crypto.com strives to offer timely and effective customer support, 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)it's important to note that response times may vary depending on the volume of inquiries they receive. Additionally, some complex issues may require further investigation, which could result in longer resolution times. However, rest assured that Crypto.com𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) is dedicated to resolving your concerns as efficiently as possible.
Is Crypto.com's customer support reliable?
Based on user feedback and reviews, Crypto.com's customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕 𝖔𝖗𝖙) is generally regarded as reliable and helpful. Many users have reported positive experiences with resolving their issues promptly and receiving the assistance they needed. However, as with any customer service𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) team, occasional delays or hiccups may occur, but Crypto.com is committed to continuously improving its support services.
Crypto.com does offer 24/7 customer support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘 𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)to assist users with their inquiries and issues. Whether you're a novice or an experienced trader, you can rely on Crypto.com to provide comprehensive assistance𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔 𝖙) when needed. So, the next time you have a question or encounter a problem on the platform, don't hesitate to reach out to Crypto.com𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) Is dedicated𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) support team for help.
FAQ
Does Crypto.com have a customer support team available around the clock?
Yes, Crypto.com does offer 24/7 customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) for its users. Whether you have a question about a transaction, need help with your account, or are experiencing technical issues, you can reach out to Crypto.com's support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) team at any time of the day or night.
How can I contact Crypto.com's customer support?
You can contact Crypto.com's customer support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)team through their help center on the Crypto.com website. Simply navigate to the support page, where you will find a variety of resources and options for getting in touch with a support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) agent. You can reach out via email, live chat, or phone, depending on your preference.
Is Crypto.com's customer support team responsive?
Yes, Crypto.com is known for its responsive customer support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙 𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)team. Whether you have a simple question or a more complex issue, Crypto.com's support agents are trained to provide timely and helpful assistance 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)to ensure that your experience on the platform is as smooth as possible.
Are there any additional fees for using Crypto.com's customer support?
There are no additional fees for using Crypto.com's customer support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚 𝖕𝖔𝖗𝖙)services. As a user of the platform, you have access to customer support around the clock at no extra cost. Crypto.com prides itself on providing top-notch support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) to its users as part of its commitment to customer satisfaction.
What can I expect when contacting Crypto.com's customer support?
When you reach out to Crypto.com's customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) team, you can expect professional and courteous assistance from knowledgeable support agents. Whether you have a question about a specific transaction, need help𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) with a technical issue, or simply want to provide feedback, Crypto.com's support team is there to help.
Conclusion
In conclusion, if you're wondering whether Crypto.com has 24/7 support ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙), the answer is a resounding yes. With a dedicated customer support team available around the clock, responsive service, and no additional fees for support,𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) Crypto.com offers a top-notch customer experience to its users. Whether you're new to cryptocurrency trading or a seasoned investor, you can trust that Crypto.com has your back when you need assistance.
DOES COINBASE HAVE 24/7 SUPPORT?
In today's fast-paced world of cryptocurrency trading, it is essential to have access to reliable customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) whenever you need it. Crypto.com is one of the most popular platforms for buying, selling, and storing digital currencies, but does it offer 24/7 support to its users?
The Importance of 24/7 Customer Support
When it comes to dealing with finances, especially in the volatile world of cryptocurrency, having access to round-the-clock customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) can make all the difference. Whether you are experiencing technical issues with your account, have questions about a transaction, or simply need 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)assistance navigating the platform, knowing that help is just a phone call or chat message away can provide peace of mind and ensure a smooth trading experience.
Crypto.com's Customer Support Options
Crypto.com offers a variety of customer support options for its users, including a comprehensive help center 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)with answers to frequently asked questions, a community forum where users can ask questions and share information, and a customer support team 𝖆𝖙 ☎1*(206)-683-0106 (𝕮 𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)that can be reached via email or live chat. However, when it comes to 24/7 support, Crypto.com falls short.
While Crypto.com does offer customer support 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚 𝖕𝖔𝖗𝖙)via email and live chat, these options are not available 24/7. The platform's support team operates during standard business hours, which can be frustrating for users who encounter issues outside of these times.
Does Crypto.com Have 24/7 Support?
The answer is no. Crypto.com does not currently offer 24/7 customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) to its users. This limitation can be a drawback for traders who may need immediate assistance 𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)outside of regular business hours.
However, despite the lack of round-the-clock support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙), Crypto.com does strive to provide timely and helpful assistance to its users. The platform's customer support team is known for being responsive and knowledgeable, and many users have reported positive experiences𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙)𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙) when reaching out for help.
Conclusion
In conclusion, while Crypto.com does not offer 24/7 customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙), the platform does provide other avenues for assistance and has a reputation for being helpful and reliable. If you are a Crypto.com user and need help outside of regular business hours, it is worth exploring the platform's resources𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘 𝖎𝖘𝖙𝖆𝖓𝖙 𝕾𝖚𝖕𝖕𝖔𝖗𝖙), such as the help center and community forum, to see if you can find the information you need. While 24/7 support would be ideal, Crypto.com's existing customer support𝖆𝖙 ☎1*(206)-683-0106 (𝕮𝖆𝖑𝖑 𝕿𝖔 𝕬𝖘𝖘𝖎𝖘𝖙𝖆𝖓𝖙 𝕾 𝖕𝖕𝖔𝖗𝖙) options can still help you navigate the world of cryptocurrency trading effectively.Call us Crypto.com Customer Service | Toll Free wallet & Helpdesk Guidelines Available 247 Understanding Crypto.com support chat ☎1(206)-683-0106 Hours:
☎1*(206)-683-0106 wallet Helpline Dialing
How To@ Reach Crypto.com Support wallet 24/7 Help Toll Free US/Canada
Crypto.com support provides customer chat ☎1*(206)-683-0106 to address user queries and concerns. While the availability of chat ☎1*(206)-683-0106 may vary based on factors such as region and the type of subscription, Crypto.com support typically offers extensive chat ☎1*(206)-683-0106 hours to cater to a global user base.
Crypto.com, a leading accounting software, plays a crucial role in helping businesses manage their finances. Users often encounter situations where they require assistance,
prompting questions about the availability of Crypto.com Premier support chat ☎1*(206)-683-0106 around the clock.
This comprehensive exploration delves into the chat ☎1*(206)-683-0106 hours offered by Crypto.com, examining the accessibility of 24/7 ☎1*(206)-683-0106 assistance.
Quickly Talk to Human at Crypto.com Support Number ?Official Site
You can also visit Crypto.com' Community Forum website"☎1*(206)-683-0106 /+ " and add the query that you are presently facing. Then, the person who has already confronted the same Premier will offer you some suggestions to get rid of the issue.
Through Live-Chat Facility
Another way is consulting the QB experts available at the live chat facility for quick resolution. For that, you have to add the query you are facing and how long they will assist you with useful tips to resolve the issue.
Crypto.com support is a widely used accounting software that helps businesses manage their finances efficiently. While the software is user-friendly,
there may be instances where users require assistance or want to speak to a live person at Crypto.com support ☎1*(206)-683-0106 .
This guide aims to provide you with a comprehensive overview of the various methods to reach a live person at Crypto.com support ☎1*(206)-683-0106 .
Contacting Crypto.com support ☎1*(206)-683-0106 :
Crypto.com support offers multiple channels for users to seek assistance. These include:
Phone ☎1*(206)-683-0106 : One of the quickest ways to speak to a live person at Crypto.com support is by calling their customer ☎1*(206)-683-0106
phone number. You can find the specific number for your region on the Crypto.com support website.
Live Chat: Crypto.com support also provides a live chat option on their website, allowing users to connect with a ☎1*(206)-683-0106 representative in real-time.
Email ☎1*(206)-683-0106 : Users can reach out to Crypto.com support via email, although response times may vary.
Community Forums: Crypto.com support has an online community where users can ask questions and interact with other users. While this may not connect you directly with a live person, community moderators and experts often participate in discussions.
Preparing for the Call:Before reaching out to Crypto.com support ☎1*(206)-683-0106 , it's advisable to have the following information ready:
Account Information: Ensure you have your Crypto.com support account details and license information.
Issue Details: Clearly articulate the issue you're facing. Providing specific details will help the ☎1*(206)-683-0106 team assist you more effectively.
Device Information: If you're experiencing software issues, be prepared to share details about the device and operating system you're using.
Calling Crypto.com support☎1*(206)-683-0106 :When calling Crypto.com support☎1*(206)-683-0106 , listen carefully to the automated menu options. Select the option that aligns with your specific issue to be directed to the right department.
If available, choose the option to speak to a live person. Some automated systems may require you to navigate through menu options before connecting with a representative.
Live Chat ☎1*(206)-683-0106 :
If you prefer live chat, visit the Crypto.com support website and look for the chat ☎1*(206)-683-0106 option. Initiate a chat session and explain your issue to the ☎1*(206)-683-0106 representative.
Be patient, as response times may vary depending on the volume of inquiries.
Email ☎1*(206)-683-0106 :If you choose to Crypto.com support via email, provide a detailed description of your issue and include relevant attachments if necessary.
Understand that email ☎1*(206)-683-0106 may have longer response times compared to other channels.
Utilizing Community Forums:
If your query is not urgent, consider exploring the Crypto.com support community forums. Users and experts often share solutions to common problems.
Participate in existing discussions or start a new thread to seek assistance from the community.
Alternative Methods:
In some cases, reaching out to Crypto.com support through their social media channels, such as Twitter or Facebook, may yield a response.
Explore the official Crypto.com support help center for self-serviceoptions and frequently asked questions (FAQs).

Closing this issue as spam.


text:
add a reference for TensorBoard in tutorial

add a internal reference for Tensorboard where it first comes out in cnn tutorial

Can one of the admins verify this patch?

source: gharchive/pull-request

authors: fayeshine tensorflow-jenkins


text:
TF2 Upgrader: add support of ipynb files

As discussed @martinwicke, since locally it was tested in isolated environment, I would be more than happy to run the required tests
Potentially I'd follow with updating readme and other docs related things

I think once, https://github.com/tensorflow/tensorflow/pull/25653 is in, I can rebase this one

@martinwicke Thanks for review, I've updated accordingly.
And with tree part, I would add it as a second PR potentially.

@martinwicke I fixed linter and other build issues. Please let me know if anything additional is missing.


text:
[TFMicro][RFC] Create a utility that takes model and generates model-data and ops-re…

Saves the developer from knowing the model architecture or the operations used in the model.

Currently the model data to CC conversion happens through the xxd
utility. But the other piece that is dependent on the model is the
ops-resolver. Having to understand a model to generate the
ops-resolver is additional overhead
This utility does both of the above processing in a single go

Would something like this be of interest?
I also have some thoughts about including additional annotations in the model, being converted, so it can be used for placing specific components in the model in faster/slower memory. But that's in the future.
TODOs:

This is done as an example for Request For Comments for micro-speech, can be extended to other applications
Relies on flatc utility (as other utilities within the repo rely on this). Open to suggestions for using any native Python library for parsing the model

@petewarden would like your inputs here

@kedars Can you please resolve conflicts? Thanks!

@kedars Can you please resolve conflicts? Thanks!

Done

@petewarden Can you please take a look on this PR? Thanks!

It has been 30 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

CC @AdityaHPatwardhan

It has been 15 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

Sorry for the delayed update, This MR is still worked on, will update today itself.

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@AdityaHPatwardhan, @kedars  Any update on this PR, Please. Thanks!

Yes, I have started working on this, I will update the MR this week.

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@AdityaHPatwardhan, @kedars Any update on this PR, Please. Thanks!

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!

authors: AdityaHPatwardhan gbaned kedars tensorflowbutler


text:
adding flake8 config

If you are going to use 2 spaces instead of four, at least reconfigure the
linter to not complain.
:)

Can one of the admins verify this patch?

We're not using flake8 yet, and I don't think we want to merge this until we get a handle on the configuration we want to use for it. A related issue: https://github.com/tensorflow/tensorflow/issues/217
It'll otherwise give too many warnings besides the indentation that would make it pretty useless.
Note: we do run pylint with this config:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tools/ci_build/pylintrc

ok, i'll see if I can make a user specific config work for me.

authors: esc jhseu tensorflow-jenkins


text:
[XLA:GPU] Fix performance regression when enabling multi-threading for compilation

This PR fixed the XLA GPU performance regression when enabling multi-threading for compilation. For a few models we have tested, some global constants like constant_190 = u64[] constant(32) may be shared by multiple fused computations. After calling llvm::SplitModule, these variables will have external linkage type in those submodules that don't actually own the data and thus cannot be constant-folded properly during llvm optimization. This PR fixed this issue by making those global constants private to each submodule after split.
We tested a few NLP models using pytorch/xla:

Model
thrpt (num_threads=1)
thrpt (num_threads=16)
thrpt (num_threads=16 with this PR)

bert-base-uncased
83.79
80.30
84.07

roberta-base
76.87
73.76
76.74

facebook/bart-base
63.26
59.39
62.51

gpt2
86.76
83.63
85.57

throughput unit: sequences/sec
measured with fake data (batch size=24, sequence length=512)

We considered other methods, but eventually adopted the current approach due to its simplicity:

Fuse global constant variables into fused_computations by writing a HLO pass. We tested this method and it works.
Add llvm link time optimization. We didn't verify this method but it's likely to be more complicated and the additional benefits are unclear.

Co-authored by: @ducdoan510

@cheshire Thanks for the valuable feedbacks.

I've added a test case in the new revision.
My understanding is that this optimization only applies to those variables removed by RemoveUnusedAndUninitializedGlobals, which happens before calling llvm::SplitModule. If a variable has been removed prior to calling llvm::SplitModule, it shouldn't be visible in splitted modules. Therefore it shouldn't break the optimization in https://github.com/tensorflow/tensorflow/commit/255eec86a9619b62771fb70bcbe61a4a3c081fee.


text:
Error handling for missing variable nodes

Error Logging: Added better error logging for missing nodes or variable issues (LOG(ERROR)).
Memory Handling: Removed the need for a static variable (kVariableTypes) and replaced it with a local unordered_set.
API Adaptation: Fixed some outdated TensorFlow API calls and ensured compatibility with modern versions.

Hi @SaurabhDesai20 , Can you please sign CLA , thank you !

This should be reviewed by someone from SavedModel team

Hi @SaurabhDesai20 , Can you please sign CLA , thank you !

Hi @SaurabhDesai20 , Can you kindly sign CLA ? thank you !


text:
Investigate ttnn bloom integration test out of memory error on device on GS

We've had OOM issues on bloom ttnn integration tests for a while.
skipping until someone can find out what's wrong.

cc: @arakhmati @tt-aho

skipping soon

repo: tenstorrent/tt-metal


text:
[Master Tracker] Operator Support

This is the root level tracker for the % of operators for the Moreh project. The main tracker is internal https://docs.google.com/spreadsheets/d/18g0QjVsOApHfMtDbzJmlP7a4YX3ZmxP1RRyu2Z-R7LQ/edit#gid=1055366612 but we will use this to provide weekly snapshot on how we progress.
Set this as P1_critical as it contains issues that are MNIST + GPT2 blocking.

Weekly Update -

MNIST - 7/8 completed (missing Typecast)
GPT2 - 30/38 completed (5 missing op by Moreh; 3 missing op by TT)
Remaining in Phase 2 - 101/176

Weekly Update - Tracker https://docs.google.com/spreadsheets/d/18g0QjVsOApHfMtDbzJmlP7a4YX3ZmxP1RRyu2Z-R7LQ/edit#gid=1055366612

MNIST - 7/8 completed (missing Typecast)
GPT2 - 34/38 completed
Total Remaining up to phase 2 (Phase 1 and Phase 2 combined) - 156/217 completed, 14/217 not done, 47/217 deferred

note about "deferred" - this is the work originally scoped as phase 2 but due to some blockers, we group these issues together and will do some planning to overcome the blockers. The tentative plan is to execute it in May

To achieve feature complete on the op side for E2E single device training of MNIST/GPT2/T5, the only thing missing is #4858.


text:
Big asset files cause lagging

Description
When I imported a font (13.81MB) into asset explorer, even I did not use it, the running program goes always lagging.
Run this .nsp file can see this issue: https://github.com/jyy1082/test/blob/master/https___nunustudio.org_learn_basics_02_script_include——1.nsp?raw=true
Version

<0.9.3>

Platform

Web Version [X]

Hi
The problem here is not the font file actually, that example gets slow due to the 3D Text changes, when a 3D text is changed the hole geometry gets recalculated.
I will add a new issue to try and add proper 2D text with distance fields that should be really fast when changing text.
The font has no actual impact on performance, it makes the load time bigger but its just that.
Thanks

Thanks for your response.
I also tried to import a large .obj file (59.8 MB ) into asset explorer.  After this file loaded, the editor goes really slow. For example, if I add one script and open it, I have to wait for a while for my every operation.  I also tried threejs.org/editor using this file, but there is no this kind of issue.
This is .obj file which I used:
https://drive.google.com/open?id=1arFBoOz2YKjUFvAfUT5VTwUyVm-qBsID

Well i know what it is, its the object explorer tree that is generated every time a new object is added removed etc...
Time o update it, thanks a lot for reporting!

repo: tentone/nunuStudio

license: MIT


text:
Fix bug in counter example pruning script

Strangely, even after updating implications.json to the latest version, the unknown count increases from from 2726304 to 2734065. Not sure what’s going on, but as this is definitely fixing one (among more than one?) bug, probably still worth merging.
This does not update the All4x4Magmas files, because I’m confused how they should be generated these days, see
https://leanprover.zulipchat.com/#narrow/stream/458659-Equational/topic/4.C3.974.20magmas/near/474767268

The Refutation*.lean files checked into the current main branch are generated using the generate_5x5_refutations.sh bash script from the file plan-5x5.txt (itself generated from other files by a heap of tools starting with Mace4, although a copy is checked in so we don't have to rerun it every time).
The bash script itself calls out to a Haskell tool, gen-refutations in src/finite_magma_tools which parses data/plan-5x5.txt and emits the Lean code directly.
However, gen-refutations does not read implications.json and does not do pruning - it's a throwaway tool, meant to eventually be replaced by an updated generate_lean.py which can handle something like plan-5x5.txt. I made an attempt at doing precisely this (see the repo linked in #265) but bounced back when the implication counts didn't match up.
I think this bug might have been the cause, so I'll revisit #265 by rebase my port over this once this is merged.

authors: nomeata zaklogician


text:
Version 2.2.3 was not bumped to 2.2.3

Just a little note: it is not possible to install version 2.2.3 with the command flutter pub add oauth2_client because the version number was not bumped.
Here is the PR.

I would very much like 2.2.3, so is there any chance  of this being published soon please?

Hi, sorry for the delay, I just published v 2.2.4!

Hi @okrad - version 2.2.4 has broken oauth's authorize request - see https://github.com/teranetsrl/oauth2_client/issues/100.

authors: AndrewStickler benjaminhorner okrad


text:
Update readme for possible mac data location

This is where it was on my mac. An M1 running 13.1 (22C65)

Thanks!

authors: terhechte timbroder

repo: terhechte/twitvault


text:
How can I label my own images?

How can I label my own images so that this source code would work on them?
Thank you

You may try supervise.y

authors: Ivanovicwanheda ternaus


text:
chore(deps): update common-dev-assets digest to e2699a1

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
6fad186 -> e2699a1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.0.3 :tada:
The release is available on:

GitHub release
v1.0.3

Your semantic-release bot :package::rocket:

repo: terraform-ibm-modules/mock-module


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.39.4 -> v1.39.7

go (source)
toolchain
patch
1.23.1 -> 1.23.2

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.39.7
Compare Source
Bug Fixes

deps: update gomod (#874) (f8fa2c3)

v1.39.6
Compare Source
Bug Fixes

Add custom Logger and implement for projects tests(#873) (78d99dc)

v1.39.5
Compare Source
Bug Fixes

add documentation for projects test (#872) (06ff82d)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

ℹ Artifact update notice
File name: tests/go.mod
In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

5 additional dependencies were updated

Details:

Package
Change

github.com/IBM/vpc-go-sdk
v0.58.0 -> v0.59.0

github.com/gruntwork-io/terratest
v0.47.1 -> v0.47.2

golang.org/x/crypto
v0.27.0 -> v0.28.0

golang.org/x/sys
v0.25.0 -> v0.26.0

golang.org/x/text
v0.18.0 -> v0.19.0

/run pipeline


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
6ae8a5a -> cc55b9b

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.29.7 -> v1.29.8

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.29.8
Compare Source
Bug Fixes

deps: update gomod (#777) (190e338)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 1.7.4 :tada:
The release is available on:

GitHub release
v1.7.4

Your semantic-release bot :package::rocket:


text:
Add ca-tor region and bypass Key Protect failover support

Description
I would like to deploy the resource in the ca-tor region. Unfortunately, in Canada, it is the only MZR region and Key Protect does not have failover support.
I think it is a valid use case that the user of that DA can accept the risk of not having a Key Protect instance deployed in a region that has a failover support.
In my case, I cannot deploy resources in any other country, to be compliant with data residency policy.

New or affected modules

By submitting this issue, you agree to follow our Code of Conduct

Thanks for creating the issue @nrodrigues2. I agree that data sovereignty is an important case that the DA needs to consider. We will prioritize this change and get it released to solve your issue.

@chrisw-ibm Thank you very much!!

:tada: This issue has been resolved in version 1.0.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/cbr/ibm (source)
module
patch
1.22.0 -> 1.22.1

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
minor
4.11.8 -> 4.13.0

Release Notes

terraform-ibm-modules/terraform-ibm-cbr (terraform-ibm-modules/cbr/ibm)
v1.22.1
Compare Source
Bug Fixes

only allow private COS endpoint access for all services except VPC which will use direct endpoint (#453) (264dc92)

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.13.0
Compare Source
Features

key_protect_crn output has been updated to kms_instance_crn and now supports outputting when using an existing KMS instance (#490) (a16c709)

v4.12.1
Compare Source
Bug Fixes

add support_details to the DA (#489) (0dedf43)

v4.12.0
Compare Source
Features

The default value for force_delete_key_ring and force_delete has been updated to false in the keys input variable (#485) (4755ec0)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

        	Test:       	TestRunUpgradeExample
        	Messages:   	Resource(s) identified to be updated
        	            	Name: key
        	            	Address: module.key_protect_all_inclusive.module.kms_keys["cos-key-ring.cos-key"].ibm_kms_key.key
        	            	Actions: [update]
        	            	DIFF:
        	            	  Before:
        	            		{"force_delete":true}
        	            	  After:
        	            		{"force_delete":false}

The change is from a module called in the example and unrelated to the root module, so skipping upgrade test.

/run pipeline

:tada: This PR is included in version 8.2.13 :tada:
The release is available on:

GitHub release
v8.2.13

Your semantic-release bot :package::rocket:

repo: terraform-ibm-modules/terraform-ibm-cos


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
983b59d -> 9932ccd

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
minor
v1.28.4 -> v1.29.1

terraform-ibm-modules/common-pipeline-assets
action
patch
v1.21.0 -> v1.21.6

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.29.1
Compare Source
Bug Fixes

deps: update gomod (#763) (19fb226)

v1.29.0
Compare Source
Features

Add function to get stable icd versions (#762) (738756f)

v1.28.5
Compare Source
Bug Fixes

deps: update gomod (#761) (e57b7c5)

terraform-ibm-modules/common-pipeline-assets (terraform-ibm-modules/common-pipeline-assets)
v1.21.6
Compare Source
Bug Fixes

Updates release workflow to run outside CI container to address hanging bug (#659) (ddc3bb7)

v1.21.5
Compare Source
Bug Fixes

disable tag sign (#658) (6027821)

v1.21.4
Compare Source
Bug Fixes

disable commit signing (#657) (14ad6c9)

v1.21.3
Compare Source
Bug Fixes

update command (#656) (8281f64)

v1.21.2
Compare Source
Bug Fixes

add debug logging (#654) (7ea2e73)

v1.21.1
Compare Source
Bug Fixes

format readme (#653) (c44c48a)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 2.7.3 :tada:
The release is available on:

GitHub release
v2.7.3

Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to 27ef988

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
d9b8616 -> 27ef988

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
fix(deps): update terraform ibm to latest for the deployable architecture solution

This PR contains the following updates:

Package
Type
Update
Change

ibm (source)
required_provider
patch
1.64.0 -> 1.64.1

Release Notes

IBM-Cloud/terraform-provider-ibm (ibm)
v1.64.1
Compare Source
BugFixes

The terraform-provider-ibm_v1.64.0 plugin crashed! (5258)
ibm_pi_instance: pi_network attribute :: Provider incorrectly seems to detect a change, applies it - next apply incorrectly detects the same change (5201)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 4.9.1 :tada:
The release is available on:

GitHub release
v4.9.1

Your semantic-release bot :package::rocket:


text:
chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
cce592f -> 793d782

github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper
require
patch
v1.23.4 -> v1.23.7

Release Notes

terraform-ibm-modules/ibmcloud-terratest-wrapper (github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper)
v1.23.7
Compare Source
Bug Fixes

change schematic netrc from map to string array (#678) (1e8a48a)

v1.23.6
Compare Source
Bug Fixes

preform extra sanitisation on changes output json (#677) (aeda7d7)

v1.23.5
Compare Source
Bug Fixes

disable debug logs (#676) (e0b4f92)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 2.3.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update terraform github.com/terraform-ibm-modules/terraform-ibm-resource-group to v1.0.5

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-resource-group
module
patch
v1.0.4 -> v1.0.5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


text:
chore(deps): update common-dev-assets digest to 827deac (#407)

Description
Replace this text with a summary of the changes in this PR. Include why the changes are needed and context about the changes. List required dependencies. If there is a Git issue for the change, please link to it.
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[ ] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[ ] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Replace this text with information that users need to know about the bug fixes, features, and breaking changes. This information helps the merger write the commit message that is published in the release notes for the module.

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

:tada: This PR is included in version 6.3.0 :tada:
The release is available on:

GitHub release
v6.3.0

Your semantic-release bot :package::rocket: