NoSuchMethodError when using LocalPubSubHelper to test Google Cloud PubSub - google-app-engine

I am trying to use LocalPubSubHelper to unit test my PubSub code but I get this error:
java.lang.NoSuchMethodError: io.grpc.protobuf.ProtoUtils.marshaller(Lcom/google/protobuf/Message;)Lio/grpc/MethodDescriptor$Marshaller;
when I do:
PubSub localPubsub = helper.getOptions().getService();
In my build.gradle, these are the dependencies I have:
force 'com.google.apis:google-api-services-pubsub:v1-rev8-1.21.0'
force 'com.google.api-client:google-api-client:1.21.0'
force 'com.google.http-client:google-http-client:1.21.0'
force 'com.google.http-client:google-http-client-appengine:1.21.0'
force 'com.google.auth:google-auth-library-credentials:0.6.0'
force 'io.grpc:grpc-netty:1.0.1'
force 'io.grpc:grpc-auth:1.0.1'
force 'io.grpc:grpc-core:1.0.1'
force 'com.google.api.grpc:grpc-google-common-protos:0.1.4'
force 'io.netty:netty-handler:4.1.3.Final'
force 'com.google.auto.value:auto-value:1.1'
force 'com.google.api-client:google-api-client-appengine:1.21.0'
force 'io.grpc:grpc-all:0.13.1'
force 'io.grpc:grpc-stub:0.13.1'
force 'io.grpc:grpc-protobuf:0.13.1'
I am not sure what dependency versions are interfering which are causing this error. Can anyone please help?
Thanks,
Abhishek

Related

Permanently resolve Unable to watch for file changes in this large workspace

To resolve this issue I got there to the link provided by vscode
https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Ok, this, corrects the error, But when I restart the Linux and again open my React project,
I get the Same error.
max_user_watches file again gets the value of 8192 as no. of max files.
My react server is not starting due to this issue.
Then I again follow the same step of the link provided, this sometimes gets frustrating.
Any permanent Help I could get from you.
A workaround:
Just disable this built-in extension: TypeScript and JavaScript Language Features

Karma Istanbul fix to work with new version of Chrome

In my AngularJs application I'm using Jasmine and Karma for my unit tests.
Recently, after a chrome update (now on 72.0.3626.81) my unit tests starting failing locally (with no change to code). I believe the error is a result of my coverage tool Instanbul.
Sometimes the error appears like this:
An error was thrown in afterAll Uncaught ReferenceError: __cov_iuQO6FdumXRPLjSMopb0JQ is not defined thrown
Other times it will appear within a specific unit test (not sure why).
I searched my application and the only file this __cov_ variable could come from is the return of a function within the Instanbul package, generateTrackerVar() within instrumenter.js.
As no code changes were made I assume that the issue is with the new version of Chrome, perhaps the security settings.
My question what permissions would karama-coverage/istanbul require? OR if anyone suspects the issue isn't security based, then what could be causing this error?
Thanks
EDIT:
I have tried to disable web security in my gulpfile like so:
browsers: [ 'Chrome_without_security' ],
customLaunchers: {
Chrome_without_security: {
base: 'Chrome',
flags: ['--disable-web-security']
}
},
But this didn't solve the issue. Is there a way to set the chrome version in this config?
I managed to solve this by figuring out the hashcode after __cov_ was related to a test file that was throwing an error. I don't know why the error didn't just appear as it normally would, that will be another problem to solve.
For now I managed to figure out the file by logging in instrumenter.js within the instanbul package. Then by removing my coverage tool I figured out the source of the issue. Simply removing the coverage tool would give me a different error but not tell me which file so I needed to do both.

PageableManagerInterface error in SonataAdminBundle

I'm trying to configure SonataAdminBundle and SonataUserBundle to use mongodb and am getting the following error:
ClassNotFoundException: Attempted to load interface "PageableManagerInterface" from namespace "Sonata\CoreBundle\Model" in /Users/me/Sites/mynamespace-webtools/vendor/sonata-project/user-bundle/Model/UserManagerInterface.php line 25. Do you need to "use" it from another namespace?
Can anyone shed any light on what might be causing this? I was also getting the symptoms described here and have tried the answers suggested there.
Can anyone confirm if the mongodb functionality is just broken? Am also wondering if this error relates to this commit?
This appears to be a dependency error within the Sonata system itself, and not strictly related to the MongoDB module.
The PageableManagerInterface class is provided by the Sonata Core Bundle. Make sure that you have it in your composer.json file:
"require": {
"sonata-project/core-bundle": "dev-master",
}
After that, make sure your install is up to date and clean your cache, as usual:
php composer.phar self-update ; php composer.phar update

Deploy Vosao in Capedwarf Beta 3

I get a lot of errors when trying to deploy Vosao in Capedwarf Beta 3:
Here's the complete log:
http://pastebin.com/2z35pEvE
java.lang.LinkageError: Failed to link org/apache/velocity/tools/view/jsp/VelocityViewTag (Module "org.apache.velocity.tools:main" from local module loader
Looks like CD can't locate the Apache Velocity dependency?
Anyway, I still tried accessing the context root:
http://127.0.0.1:9990/vosaocms-0.9.14
and
http://127.0.0.1:9990/vosaocms-0.9.14/vosaocms
I guess there was really a problem in the deployment.
How can I fix this error?
Do you use Velocity in your app?
I would say yes, as it looks like it overlaps with CapeDwarf's Velocity usage - we use it to rended admin console.
Try removing the Velocity libs.
But I will also fix this in CapeDwarf, so the two libs won't overlap.
Leaving you with your own version of Velocity then.

TypeError in qx.ui.mobile.core.EventHandler after update to qooxdoo 1.5

After updating to qooxdoo 1.5 I am seeing this error:
Uncaught TypeError: Expecting a function in instanceof check, but got #<HTMLDocument>
:8080/qooxdoo-1.5-sdk/framework/source/class/qx/ui/mobile/core/EventHandler.js?nocache=0.38786523090675473:245
Strange thing is, that I am not using the qx.ui.mobile.* classes at all. This is with a source-all build and "qx.debug" set.
As for including the qx.ui.mobile.* classes, this comes from using the source-all job, which includes, well, all known classes, also the qx.ui.mobile.* ones. Try using the normal source job, which only includes the classes necessary for your app.
As for the error, please open a bug report at http://bugzilla.qooxdoo.org. Please specify the OS and browser you are using when you get the error. If possible, supply a minimal Application.js (or a Playground link) that reproduces the error. Cheers.

Resources