I hate "your app is chatty" - messages, so i wrote a custom filter for them:
This works as expected, but i'd like to enhance it:
Currently, the filter shows logs of all of my appstarts.
I'd like it to only show logs of my current appstart (which is the same as the default filter "show only selected application" does)
I suspect this is possible by filtering the PID, but i don't know how.
(Android Studio hints, that there is code-completion enabled in the PID field)
Locat entries that originate from an app without debug information, only have ? as package name. Since all system apps don't contain any debug information (AFAIK), messages from the system and most apps can be filtered by typing the following regex into the Package Name field:
^(?!(\?))
This might not be perfect, since you might have other apps with debug information, which could still pollute your log, but for me it's enough.
Related
I have built an action with Actions-on-Google(2.5.0) and dialogflow-fulfillment(0.6.1) Node.js Library. I cannot test my app on dialogflow test console because I return conv object which is not supported there. Now, I cannot test it in the google action simulator, either. This is the error I get:
Invocation Error
You cannot use standard Google Assistant features in the Simulator. If you want to try them, use Google Assistant on your phone or other compatible devices.
I'd like to use the simulator, so I can debug better.
It is how the error message says: The simulator lacks many features that normal Assistant surfaces (speaker, Assistant app) have and can even sometimes give you completely wrong error messages. There is really no way around testing your app on real devices.
You can however view the same logs that you see in the simulator in Google Stackdriver Logging. To activate this go to the settings of your Dialogflow agent, select the "General" tab and activate the "Log interactions to Google Cloud" option. Then click on the link below the button to get to the logs. The default view will probably show you only the Actions-on-Google logs, i.e. the requests between your users and AoG. To see the requests between Dialogflow and your webhook click on the dropdown arrow in the filter box, select "Convert to advanced filter" and set the filter to resource.type="global".
If you have multiple Actions projects that use the same display name, the simulator chooses one at random. For consistent testing results, use unique names or release channels for each Action.
Reference Link: https://support.google.com/actions-console/answer/9613473?hl=en
Now how to give a display name or change the display name.
Go to develop tab and give display name or change display name as follows
You should definitely be able to test your action in the Actions simulator. Note that the interaction model b/w Dialogflow and Actions simulators are different. In Dialogflow, you can send commands directly to your agent. In the Actions simulator, you first need to invoke your Action.
At the bottom of the screen, you'll see a suggested input like "talk to my test app".
You'll need to send this, or a similar command, first. That will then invoke your action, and you'll be able to send commands to it after. You will see it is invoked by a banner at the top of the simulator.
I am trying to launch an windows application. I have given executable path. Whenever I click on launch, it’s not changing to Identify. It’s coming back to Launch. So what could be the issue?
When the application is successfully launched, but the button does not change from "Launch" to "Detach", it's usually an issue with how you've targeted your window's title.
Usually, appending wildcards to the ends of the window's title will assist in matching correctly. Additionally, ensure that the "Windows process name" field is completed correctly.
This is common for windows applications that are trigger points like RDP, MMC. You would have to have an attach after the launch to gain the connection for identify to become enabled.
Auto Save or Prompt before navigating away from text editors in Kentico CMSDesk not working. I already set the Settings -> Content Management -> Prompt to save changes on exit to checked, but didn't work. Can somebody help me.
-Thanks in advance
What I would suggest is to enable the developer tools in chrome or firebug in firefox and check, if there are any javascript errors in your pages. it's possible that some custom javascript interferes with this check. Check for any errors and try to resolve them. Or, as a test, try creating a completely blank page in the content tree, with only an editable region and disable any master page inheritance so there won't be any custom code used on your page and test, if it works there. If it does, then keep adding your scripts and test to see which component or script is causing the issue. Also make sure your settings are enabled on a site level in the settings application.
Which version and hotfix do you use? I suppose you are using v7 (or less - because of CMSDesk). Please note there were some bug fixes related to prompt in CMSDesk (eg. in 7.0.80).
Content editing - The ‘Prompt to save changes on exit’ setting didn’t work correctly
You can find more information about hotfixes and fixed bugs here.
edit: after additional info (screen from your console) I think you have registered your own jquery and you don`t have registered it in no conflict mode. Can you agree? Could you register your jquery in nonconflict mode and try the prompt behavior again?
Obviously, after the crash Developer tools at port 9222 is of no use, because "Remote debugging has been terminated with reason: websocket_closed". How can I retrieve, for example, recorded timeline; or get call stack; or find anything about the reason the Chromecast decided to reboot itself? What are the best (or, for that matter, any) approach to debug Chromecast crashes?
We need to look at your log file to see what is causing the crash. It is relatively easy to do that but we need some help from your side.
First, open the Chromecast setup app on, say, your Android device and go to the settings for your device. You should see a check box that states something like: "Send Chromecast usage data and crash reports to Google". If it is not checked, make sure you check it and then wait 15 minutes or so and reboot your chromecast.
Try to recreate issue and as soon as it crashes and reboots itself, open the setup app again and select "Submit feedback report" from the overflow menu. You will see a new window on your phone and make sure you enter the following text in the text box there "crash-vmt". We will be using this text to search among the reports that we receive to identify your log.
After doing that, please let us know (add a comment here) so we can grab the log for further investigation.
I would like to display the latest top 3-5 entries of my extension change log (TXT file) when it's auto-updated and ideally in a balloon-type event like the one when you have successfully installed an extension. It should show/popup near the wrench-icon area. Like a replacement for #history that GM scripts have.
There are already a few SO questions about how to get extension version like here.
There are also one here to detect if it's an install or update based on version.
It is not desktop notifications I want.
My question is how to make the balloon and populate it with the lines.
An alternative is open my options.html page in a new tab and show the change log entries there somehow. Requires tabs permission in the manifest.json file.
chrome.tabs.create({url:chrome.extension.getURL('options.html')});
Any ideas how to do this?
Or is this impossible to do?
There's neither a mechanism to create a "balloon" notification (that's reserved for native Chrome code), nor to pop out the popup without user interaction. Your automatic notification methods are fairly limited: creating a new tab with a changelog is certainly possible, but not particularly user-friendly (since it will simply open at some arbitrary time, completely remote from the user's intent).
If possible, I'd suggest waiting to notify the user until she interacts in some way with the extension. Clicking on a page-action, for instance, could have some sort of infobar-like note at the top of the popup's UI inviting the user to read more about the update.