mediapipe

mediapipe copied to clipboard

Please make sure that this is a feature request.

System information (Please provide as much relevant information as possible)

• MediaPipe Solution (you are using): framework
• Programming language : C++ / Android Java
• Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state:
We have used mediapipe in the production environment, it is really great, but there will be some crashes in the production environment, because it is a production environment, so there is no symbol table of the native layer, because the crash is in C++, there are no some log, it is difficult to determine the call stack information. and context

Will this change the current api? How? Will change because the log callback interface needs to be added to the JNI layer. But it only changes the JNI layer.

Who will benefit with this feature? All developers using mediapipe on the Android platform

Please specify the use cases for this feature:

    AndroidLog.nativeInjectLoggable(new JNILogging((message, severity, tag) -> {
      if (severity == Loggable.Severity.LS_DEBUG) {
          // do something eg: Use other log libraries in the current application save debug level log
      } else if (severity == Loggable.Severity.LS_INFO) {
          // do something eg:  Use other log libraries in the current application save info level log
      } else if (severity == Loggable.Severity.LS_WARNING) {
         // do something eg:  Use other log libraries in the current application save warning level log
      } else if (severity == Loggable.Severity.LS_ERROR) {
         // do something eg:  Use other log libraries in the current application save error level log
      }
    }));

Any Other info:

Hi @lilinxiong, Thanks for raising this feature request. We will share this request with the internal team and will update if any specific update on the above request. Thank you!

@kuaashish Thanks for your reply, In fact, the day before yesterday, I had simply implemented it myself, but the writing was really ugly. It was just enough to satisfy my own use. Tomorrow I plan to tidy it up and rewrite it beautifully. But I'm still looking forward to your conclusions.

Hello @lilinxiong, We are upgrading the MediaPipe Legacy Solutions to new MediaPipe solutions However, the libraries, documentation, and source code for all the MediapPipe Legacy Solutions will continue to be available in our GitHub repository and through library distribution services, such as Maven and NPM.

You can continue to use those legacy solutions in your applications if you choose. Though, we would request you to check new MediaPipe solutions which can help you more easily build and customize ML solutions for your applications. These new solutions will provide a superset of capabilities available in the legacy solutions. Thank you

This issue has been marked stale because it has no recent activity since 7 days. It will be closed if no further activity occurs. Thank you.

This issue was closed due to lack of activity after being marked stale for past 7 days.