I recently started using the Drive API in my Android project, but it wasn't long before I ran into this issue:
Google Drive InputStreamContent requires length to be set
Basically, I'd like to compress files on the fly, which wasn't possible since the API required a preset length. The issue is supposedly fixed in the 1.13.0 release according to this issue:
https://code.google.com/p/google-api-java-client/issues/detail?id=591
However, the GPE won't update my Drive API to this version. Is this expected behaviour, and if it is, how can I manually update to 1.13.0 so I can start using Drive?
Thanks,
Quint.
Issue resolved, the Drive API can now be updated past 1.13 through the Google Plugin.
Related
I have made a plugin for Confluence v7.13.7. It is working absolutely fine in the Confluence server which is set up locally on my machine. But, when I tried installing the plugin in the client’s instance who is also using the same Confluence version 7.13.7 but using the data center version, the plugin got installed but not giving any result upon hitting the API endpoint.
Is this possible that a plugin can work in a server edition but cannot work in the data center? If this can happen, what are the possible reasons for this?
Please refer to https://developer.atlassian.com/platform/marketplace/developing-apps-for-atlassian-data-center-products/ to learn the difference of apps for DC. Most features will work the same it DC as in Server, but as it uses several nodes, you have to think how to transfer the same objects between them
I upgraded Eclipse and moved to Google Cloud Platform for Eclipse for my existing Standard App Engine project. I also moved to Java 8.
Now, when I deploy my app, the size shown in the console is only 7.1mb vs. 220mb prior to the upgrade. And when I try to go to the app after deployment I get an Error: Not Found message.
Is there something in the setup for my new configuration that would be causing this?
Your question is indeed somewhat broad; you'll need to provide all necessary detail. A correspondingly general information page might help here, though, namely Eclipse "How-to Guides".
Have you adapted and re-written your app for Java 8? If so, in which way? Have you edited your app.yaml configuration file accordingly?
Cloud Tools for Eclipse writes out the app-to-be-deployed to a directory in your workspace called <workspace>/.metadata/.plugins/com.google.cloud.tools.eclipse.appengine.deploy/tmp/<timestamp>/staging-work/exploded-war, where <timestamp> is the time of the last two deploys. Look at the exploded-war directory and see what files are missing. You may then get a better sense of what needs to be remediated.
After upgrade to sdk 2.5.216 and runtime 5.5.216 Test-ServiceFabricApplicationPackage command works only for complete package. In case of partial app upgrade (some Pkg are removed) it results in "Windows PowerShell has stopped working". I have tested on several computers and several apps. to reproduce:
create test app with 2 services and deploy.
change app version and particular service version.
create package and remove Pkg folder from it for the service without modifications.
connect to Service Fabric and test like Test-ServiceFabricApplicationPackage -ApplicationPackagePath "..path" -ImageStoreConnectionString "fabric:ImageStore"
Maybe somebody was able to overcome this issue? or at least has similar behavior so I'm not alone in Universe.
Thanks!
Alex
Take a look at https://github.com/Azure/service-fabric-issues/issues/259
This is a bug in our code. It happens when a compressed package was uploaded and provisioned in the cluster. Testing a new version of the application fails because settings file was not found in the provisioned version.
We fixed the issue and it will become available in one of our next releases.
Meanwhile, you can skip compression or test the version 2 application package without passing in the image store connection string.
Apologies for the inconvenience!
I have a PHP Azure project which I have to manage with Powershell cmdlets. One of these, Publish-AzureServiceProject doesn't seem to be detecting file changes so these are not updated on the cloud (even though no errors are displayed).
I have remote desktop'd into the machines and the code is definitely not updated from weeks ago.
If I deploy to the local emulator, it is fine but this is much more obvious because it displays "removing old package" and "creating local package". The cloud package definitely contains the latest files, so the packaging is working fine.
Can anyone tell me how to force the publish to update the files on the cloud and more importantly, why this is not happening? Also, if I force the update, will it deploy to a new box and get a new IP Address?
Thanks.
It seems to work now.
I have removed and reinstalled azure libraries from my machine and created a new project from scratch and copied the original files over into it. I have not included diagnostics (not sure if that's an issue) and I have modified the Publish-AzureServiceProject script to select the subscription each time before it publishes.
It is possible that the subscription confusion was not helping (I have two Azure subscriptions and it might have used the wrong one at some point and done something weird) and also it was possible there was some conflict with various versions of the Azure SDK since I have been using it for over 6 months but at the moment, all is good.
A related article on my blog here: Problems with PHP Azure
Thanks for the interest
I've download eclipse-jee-galileo-win32.zip and following instruction of this post, http://blog.kukiel.net/2009/09/coldfusion-on-google-app-engine-with.html
After that, I encounter following errors once I've deleted war file and replace openbd's war files into my project.
alt text http://img411.imageshack.us/img411/3479/52229590.png
Please let me know if you have such problem just like me.
Make sure that you are running the latest SDKs (Google Web Toolkit and Google App Engine). I had this same issue until I switched to the latest versions when I first started out as well.
You can see which ones you are using for a particular app by opening up its properties and looking under Google. The latest versions are 1.3.5 (App Engine) and 2.0.4 (Web Toolkit). If you are on older versions look for updates, new features to install the latest.