We have a Chrome app with more than 10k users and we started rolling out a new version yesterday using the Controlled Rollout option on Chrome Web Store set to 1%. Surprisingly more than 2000 users got upgraded. I was expecting a number around 100 users.
Does anybody know if this option is not working anymore?
Thanks.
Related
Today I see that many articles were released about Flutter 2.2 and its new functionality. One of them is background caching using service workers. Has anyone an idea of what does it mean and how to use it?
for web apps, we offer background caching using service workers
UPDATE:
Ok I've found some information in this article
Flutter’s newest stable platform, web, has been improved in this release.
To start, we’ve optimized caching behavior with a new service worker-loading mechanism, and fixed double-downloading of main.dart.js. In previous versions of Flutter web, the service worker downloaded updates to your app in the background while giving your user access to the stale version of your app. Once that update was downloaded, the user wouldn’t see those changes until they refreshed the browser page a couple times. As of Flutter 2.2, when the new service worker detects a change, the user will wait until the updates are downloaded to use the app, but then they’ll see the updates without requiring a second manual refresh of the page.
I can't tell you what exactly they changed in caching but for how to use it:
Just upgrade flutter
flutter upgrade
and recompile
flutter build web --release
It should automatically build with the new service worker
I tried to deploy apache storm for a streaming program development. 4 servers for 1 nimbus/ui and 3 supervisors. After all setup, nimbus/ui/supervisors are launched without errors/exceptions reported in logs. But when access to ui via browser, the page is stuck in a spinning prompted "loading summary" like for ever.
All processes are killed and zookeeper node "/storm" and storm data folder are cleared. Still stuck on ui after restart the cluster.
Also switched to lower rev 1.1.3, still same problem, looks like not a bug specific to rev, more like a bug relevant to my setting. But really confusing to figure out. Anyone familiar with storm can help me on this?
I'm having a problem with Microsoft Azure. More specifically, I'm not able to get a mobile app up and running after creation and deployment. When I enter "Quick Start" in mobile apps settings, I get an error saying "Could not install MobileAppsManagement Site Extension" followed by "SettinListPart" and "MICROSOFT_AZURE_MOBILESERVICES". Thus I'm not able to initialize my backend.
I have a DreamSpark subscription (Student) active. I have had no problems with this earlier, and it occurred now that I moved over from free trial to DreamSpark subscription. (Free trial is disabled/inactive)
This seems to be the same or similar problem, however, I find no similar solution.
in azure mobile app quick start don't display result
As long as your site is an F1 Free in the App Service Plan (which is a difference from the trial service), there should be no problems. Steps for troubleshooting:
Go to your site, All Settings, Scale Down and ensure the F1 Free is chosen
You might have a cached permissions issue - do a hard refresh of your browser / clear the cache.
This evening I noticed my staging server ran out of disk space.
When investigating I saw each time I deploy my loopback-js app with strongloop process manager, it installs a brand new app in a new folder.
After deploying 20 times I have 20 versions, which each take up 140 Mb.
I assume those folders make it easy to switch between versions, but I cannot figure out how I should do that with strong-pm and if I can specify how many versions should be saved, etc...
How do these versions, rollback-functionality work in strongloop-process manager and where can i find documentation?
At the moment there is no true "rollback" mechanism in strong-pm. The closest you can get is to deploy a previously deployed git commit, which will re-use the previous deployment that matches that commit's hash.
I'm working with Google App Engine in Eclipse w/ JSP pages in Windows 7.
I already have an app deployed and working, but I am unable to make changes to it for some reason.
If I make changes and debug locally, my localhost page is showing the changes that I implement.
While I am not getting any errors in the deployment, the same changes that work on my local debug are no longer showing up, so I can't update my app.
I thought updating the version number might help, but I had no luck with this.
Any ideas? Thanks.
Are you deploying the same version (as specified in appengine-web.xml) as the default version that is running on your app? If not, you'll have to access your new deployment at http://newversion.appname.appspot.com, or change your default version in app engine to your newly deployed version.
I have had the same problems too, especially when the changes concerned the static pages. Some little things to check:
If you have set an expiration date in your app.yaml, your browser cache could be holding the file.
If it’s specific to the online contents, it could be an intermediary cache (such as a squid server) serving the outdated contents, in which case you’d have to flush the cache to get the new version.
You could start by checking the log on the GAE console to see if the request is received by the server, that would help you debug.
Another trick, if you’re being served an outdated version of http://yourapp.appspot.com/index, try and pass a dummy argument to force the browser to update the version, for instance : http://yourapp.appspot.com/index?p=1