How do you shut off all the text generated by google vision when performing ocr?
example:
12:37:51.834 [grpc-nio-worker-ELG-3-3] DEBUG io.grpc.netty.shaded.io.grpc.netty.NettyClientHandler - [id: 0x48359d52,
I do not see a setting and it fills the console up with garbage
Related
We are running an application using Forge Design Automation for Revit and have an issue I can't fully explain. Our tests have been working just fine but we got a couple lately that seem to freeze inside Revit as far as I can tell. Here is the OnStartup method of my external application:
public ExternalDBApplicationResult OnStartup(ControlledApplication application)
{
SharedData.Initialize(new LoggerConsole());
// Startup is only for registering the DA ready event
SharedData.Log.AddLine("Design automation startup in App");
DesignAutomationBridge.DesignAutomationReadyEvent += DesignAutomationBridge_DesignAutomationReadyEvent;
SharedData.Log.AddLine("Design automation event registered");
return ExternalDBApplicationResult.Succeeded;
}
Here is the outline of the event handler referenced:
void DesignAutomationBridge_DesignAutomationReadyEvent(object sender, DesignAutomationReadyEventArgs e)
{
// Start the actual processing here
SharedData.Log.AddLine($"Into automation ready event, working directory is: {Environment.CurrentDirectory}");
...Other Code...
}
The log for one of the jobs I'm talking about (clipped to relevant portion) looks as follows:
[12/10/2020 01:34:42] Design automation startup in App
[12/10/2020 01:34:42] Design automation event registered
[12/10/2020 01:34:42] Initialize and get RCE: (VersionBuild) 21.1.10.26 (VersionNumber) 2021 (SubVersionNumber) 2021.2
[12/10/2020 04:34:33] Error: Revit Core Engine Core Console is shut down due to process time limit.
[12/10/2020 04:34:33] End script phase.
As you can see, it makes it to the log line about event registered so the only thing left to do after that is return success. It does seem to get that success because the next log line is from inside Revit (the one that starts with 'Initialize and get'). Then after that it seems to wait 3 hours and then error because of time out. It never logs the very first line of the event handler so as far as I can tell that's not getting called.
Anyone else experienced this? How would you even go about debugging it?
Previously Google Maps works fine on my Android device. I did not change any code and certificates. Now I am getting the following error Log:
EDT] 0:20:38,90 - Exception: java.lang.RuntimeException - Waited too long for browser bridge
java.lang.RuntimeException: Waited too long for browser bridge
at com.codename1.g.d$a.a(MapContainer.java:262)
at com.codename1.g.d$a.b(MapContainer.java:223)
at com.codename1.g.d.a(MapContainer.java:709)
at com.zetta.survey.a.c.a(GoogleMapsTestApp.java:78)
at com.zetta.survey.d$2.a(MainMenu.java:144)
at com.codename1.s.r.a(Form.java:1621)
at com.codename1.s.ae$a$a.run(SideMenuBar.java:1745)
at com.codename1.s.n.l(Display.java:1101)
at com.codename1.s.n.j(Display.java:1045)
at com.codename1.s.n.i(Display.java:946)
at com.codename1.s.ad.run(RunnableWrapper.java:120)
at com.codename1.impl.b$1.run(CodenameOneThread.java:60)
at java.lang.Thread.run(Thread.java:818)
Any Suggestions?
For some reason the native maps are failing to initialize so it is falling back to the web-based maps - which shouldn't happen on device. Things to check:
Make sure your app has the android.playService.maps=true build hint.
Refresh cn1libs, and clean and build, then try again.
Try reading the device log in DDMS. There is surely an error reported when it fails to create that native map.
Lines from my 'Exception Description' from Google Analytics 'Crashes and Exceptions' report include:
IllegalArgumentException (#ak:g:-1) {Thread-8609}
IllegalStateException (#w:a:-1) {main}
I'm trying to decode them with the Proguard GUI as the Proguard mapping file is 33693 lines long, including hundreds of '-> ak' and '->w' lines. I've tried editing the exception lines down and adding a 'proguard.' preface without any luck:
There is now another way to decode obfuscated exception reports.
If you connect your app to the new Firebase developer platform and add Firebase Analytics to your code, you will get access to the Firebase Developer Console. If you click the 'Crash Reporting' tab, it will give you a detailed list of your crashes, including app version number. Click on any of the crash listings and you will get a full trace, including an 'Upload a ProGuard mapping file to deobfuscate future stack traces for version xxx' message. Click the 'UPLOAD' button and browse to your 'mapping.txt' file. Upload the file and, voilà, the trace is decoded.
If you've never browsed to your 'mapping.txt' file, it's well buried at 'app/build/outputs/mapping/release'.
Configuring and coding for Firebase and Firebase Analytics I'll leave to the Docs, and to Stack Overflow if you have issues.
In developing in Fi-Cloud's CEP I've been having an issue that has been happening repeatedly. As I'm trying to develop a definition to perform a task, CEP's server and Authoring Tool stop responding, although ssh is still responsive.
This issue happens as I develop. I'm using the AuthoringTool to alter the definition bit by bit and then I re-upload it to the server through the authoring tool's export feature.
To reinitiate the proton with the new definition each time I alter it, I use Google's Postman with this single operation:
-PUT (url:http://{ip}:8080/ProtonOnWebServerAdmin/resources/instances/ProtonOnWebServer)
header: 'Content-Type' : 'application/json'; body : {"action": "ChangeDefinitions","definitions-url" : "/ProtonOnWebServerAdmin/resources/definitions/Definition_Name"}
At the same time, I'm logged in with three ssh intances, one to monitor the files being created on /opt/tomcat10/sample/ and other things, and the other two to 'tail -f ' log files the definition writes to, as events are processed: one log for events recieved and another log for events detected by the EPAgent.
I'm iterating through these procedures over and over as I'm developing and eventualy CEP server and the Authoring Tool stop responding.
By "tailing" tomcat's log file (# tail -f /opt/tomcat10/logs/catalina.out) I can see that, when under these circumstances, if I attemp a:
-GET (url: http://{ip}:8080/ProtonOnWebServerAdmin/resources/instances/ProtonOnWebServer)
I get no response back and tomcat logs the following response:
11452100 [http-bio-8080-exec-167] ERROR org.apache.wink.server.internal.RequestProcessor - An unhandled exception occurred which will be propagated to the container.
java.lang.OutOfMemoryError: PermGen space
Exception in thread "http-bio-8080-exec-167" java.lang.OutOfMemoryError: PermGen space
Ssh is still responsive and I can look at tomcat's log this way.
To get over this and continue, I exit ssh connections and restart CEP's instance in the Fi-Cloud.
Is the procedure I'm using to re-upload and re-run the definition inapropriate? Should I take a different approach to developing?
When you update a definition that the CEP is already working with, and you want the CEP engine to work with the updated definition, you need to:
Export the definition using the authoring tool export (as you did)
Stop the engine run, using REST PUT
PUT //host:8080/ProtonOnWebServerAdmin/resources/instances/ProtonOnWebServer
{"action":"ChangeState","state":"stop"}
Start the engine, using REST PUT
PUT //host:8080/ProtonOnWebServerAdmin/resources/instances/ProtonOnWebServer
{"action":"ChangeState","state":"start"}
You don't need to activate the "ChangeDefinitions" action, since it is the same definition name that the engine is already working with.
Activating "ChangeDefinitions" action, only influences the next run of the CEP, and has no influence on the current run.
This answer your question about how you should update a CEP definition.
Hope it will solve your issue.
I have a Windows Phone 8.1 app with Google login, which uses the
GoogleWebAuthorizationBroker.AuthorizeAsync
method. 90 % of the time, the authentication works, however, occasionally, the app just crashes on this line (I am logging right before it, so I am sure). I have the call wrapped inside try - catch, but that doesn't seem to work - exception is never caught.
I am also sure I am calling the method on a UI thread, I am using the DispatcherHelper from MVVMLight for that.
The fact that I am not able to reproduce the crash complicates this a lot, I have not experienced it with debugger attached, only in Release mode, on target device, run locally.
Do you guys have any ideas / clues / pointers? I know I'm not providing a lot of information, but I don't have any..
EDIT> So the error now happened with debugger attached - and the app just froze, last message in Ouput window was
"WinRT information: Cannot get credential from Vault"
But that's normal behavior..