I'm using Kimono Desktop to crawl a site and posting the data to a Firebase endpoint. Everything is working from beginning to end with the exception of auto-running.
When creating or editing the Kimono API with the Chrome extension the desktop app crawls and reports "the last crawl was successful". The next run is listed as the set time to crawl (I've tried 5 min, 30 min, and 1 hour on multiple machines) but when that time elapses the Next Auto-Run says "Queued" but never actually runs.
Kimono Desktop Crawl Setup
The API in the screen shot above is set to crawl every five minutes but has been queued for at least 2 hours 55 minutes without running. And out of curiosity I let one machine go 2 days without another crawl.
Clicking Start Crawl works fine but defeats the purpose of the auto-run. Ideas?
Unfortunately, as far as I'm aware the Kimono Desktop version does not support autorun.
There have been a few people who have found success by calling the api via ondemand with a script at their own determined intervals, which seems to be the only current way to do this now.
I'm sure more people will find ways to tinker with the desktop version as time goes on, but no luck with autorun so far for me unfortunately.
To find info on how to use the ondemand calls for the desktop version, some info on this answer HERE should be able to get you going.
Related
I'm trying to help a client with their slow-ish website https://www.dp-tools.de. If I use Google page speed for mobile I can see that it takes 7 seconds to be interactive but nothing in the found problems really tells me why it is actually that slow. I also tried chrome lighthouse and couldn't really see all that much.
Is there another way of checking or maybe anyone here sees why it is so slow?
Open up the client's Shopify Admin, and examine the theme. Does it have any strange slow code in it? Examine the Apps installed that directly affect theme. Are any of them crap, old, broken junk?
The best way to debug a slow theme is to just start hacking out any junk the client may have added to their theme. A lot of themes are so bad, for example, they load jQuery 3 times. Likely you have one bad apple in there, a call that is blocking and takes way to long to timeout or respond. Developer tools can point these out to in your console. Mobile versions have to come with a developer console you can inspect too right?
I want to apologise in advance - my question will be not about programming, but rather about some quirk of Google Play Services we have met.
The situation is the following - we did not update the version or change the settings in developers console, but we got a bit over 10 e-mails from players who cannot play anymore - the game gets something different from STATUS_OK in OnRoomCreated callback. Nothing is wrong with the code - these players were able to play just a day before, which makes me think about Google Play Services updated in background. The issue was first reported not more that 2 weeks ago.
I know it is not much info, but we did not get the issue on our devices. With only 10+ e-mails from 1000+ daily online players, we are rather unlikely to see it.
Actions already tried without success:
Restarting device
Reinstalling the game
Disconnecting the game from Google Settings\Connected Apps
Clearing cache, data and removing updates of Google Play Services
Updating to the most recent version of the library
Here we have run out of ideas. If anyone has met the same, or has any good ideas, please, share them.
This issue seems to be account-specific, and the only known solution so far is to make a new Google account. My guess is that the players affected were playing the game when something happened (Google Play Services updated?), and now they are still marked as playing that game. So, they can't start a new one. The corresponding issue is here:
https://code.google.com/p/play-games-platform/issues/detail?id=70
Update: Google team has marked it Fixed.
ive written a script that configures a bunch of items and displays it on screen using javascript. Now we are in the process of trying to take a screenshot of it via a browser. This particular webpage is for use by the general public, and once the screenshot is taken, we post the photo to facebook for the user.
Ive trialled a number of services that take screenshots but they are all pretty slow, mostly averaging around 25 - 25 seconds to take the shot and have it saved on the server. All our users would leave in this time =(
Ive also tried the application from http://www.websitescreenshots.com/ and whilst its brilliant i cant get it to render our page with the js on it.
I have found this to be a common thing amongst screenshot software, and ive even gone through to trying to take advantage of the free webservice from Wordpress MShots.
Whilst it took photos nicely you could never tell how long it was going to take and not good enough for a production website.
So can anyone recommend a utility that will allow screenshots of URL's accessible via a command line that can render JS and also runs on windows server 2008 ? I am having no luck tryning to source an app that does this..
we are developing an extension, hosted in the Google chrome web store.recently - we've got complaints from our users that sometime they get a notification window saying "the extension crashed, click here to reload".
after a short research we found out that this is happening only when we upload a new version to the Chrome Web Store.
we started to look it up online and found no documentation what so ever for this, so we started to check for it ourselves.
we tried to see what exactly can cause this problem and if we can identify a distinctive cause.
our tries included updating only the manifest.json file, a css file, a js file or not changing nothing at all but the version number, and on each change we've uploaded a new version and update it in about 10 different machines.
the results were the same, when on each update we made, it caused the extension to crash on just a few of the machines, while updating perfectly fine on the others. each time different machines acted differently.
then, we thought it might be related to the fact we have a timer working in the background page, and it might be happening just at the time it is working.
so we tried to raise the timer's frequency (from 5 seconds to 100 millisecond), and it still acted the same, crashing on only 3 out of the 10 machines.
we ran out of ideas now, and it really causing a problem in terms of user experience to our extension's users.
did someone had this problem, or came across any extension crashes on version update?
is it a known bug in chrome's extension engine or are we doing something wrong?
I am having the same problem and I think I found the cause. Do you by chance, override the new tab page?
I am able to reproduce the problem 100% of the time and when I remove the new tab override from the manifest, the problem goes away.
I opened an issue: Issue 104401
I am trying to convert one of my earlier written time tracking apps to a web browser based app.
Some options of technology include java, flash, ... My goal here is letting a user track time for our organization while having ideally no extra installation on desktop, or least minimal, like flashplayer or jvm, etc, but the product itself should be in browser.
I have done some research and so far i can't find a way any technology, of the ones i have known, could take a screenshot of whole desktop while running inside web browser even if, say, browser is out of focus.
The best i could do was take a screenshot of the page on which that app will run. Any ideas? Possible? leads?