-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compatibility errors #1
Comments
Based on gauge source code I can say that recently gauge introduced |
@nvborisenko yes, you are right. Gauge is moving to gRPC. However, this is yet to be released. This feature is under development, and we expect to support the older mechanism and give users enough notice before deprecating it. The information for gauge's gRPC schema/events are discussed here: https://spectrum.chat/gauge/engineering/proto-messages-used-by-gauge-and-its-plugins-to-exchange-information-during-the-authoring-and-execution~4cb1ac64-751a-4903-a317-2f5e454fd0f1 . Please feel free to post your recommendations. As for this issue - I can try to replicate the issue, but I do not have a report portal instance. If you can point me to any step to replicate this issue, that'll be helpful. |
Thumbs up for gRPC. Does it mean that at this moment released gauge and plugins use mixed technologies? |
Right now we haven't released any plugin with gRPC support. However, we might do it (i.e. release a plugin with gRPC support, before Gauge core's gRPC support). This would mean that the plugin's gRPC feature is toggled off. |
Ok, what about initial issue where grpc is not used? I just developed plugin, with the code above, and this code raises exception. Code is very simple, just listening to incoming proto messages. |
@nvborisenko Gauge and its plugins with GRPC support has been released. |
Ok, thanks for letting me know. My initial issue was about incompatibility between parties. Just watch out and discover what version of proto messages is used by plugins/runners. Java/Dotnet/AnyReporterPlugin references to different proto messages.. I believe.. |
Fixed in v1.0.7 and Gauge.CSharp.Core 0.3.7 nuget package. |
Reopening it, trying new grpc capabilities and it seems I am missing something, Please help. Here is how I start server: var server = new Server();
var s = Reporter.BindService(new MyHandler(server));
server.Services.Add(s);
var g_port = server.Ports.Add(new ServerPort("127.0.0.1", 0, ServerCredentials.Insecure));
TraceLogger.Info($"Listening on port: {g_port}");
server.Start();
TraceLogger.Info("Server has started.");
server.ShutdownTask.Wait(); And public class MyHandler : Gauge.Messages.Reporter.ReporterBase
{
private static ITraceLogger TraceLogger = TraceLogManager.GetLogger<MyHandler>();
private Server _server;
public MyHandler(Server server)
{
_server = server;
}
public override Task<Empty> NotifyExecutionStarting(ExecutionStartingRequest request, ServerCallContext context)
{
TraceLogger.Info("NotifyExecutionStarting received");
return Task.FromResult(new Empty());
}
public override Task<Empty> NotifyExecutionEnding(ExecutionEndingRequest request, ServerCallContext context)
{
return Task.FromResult(new Empty());
}
public override Task<Empty> Kill(KillProcessRequest request, ServerCallContext context)
{
try
{
TraceLogger.Info("KillProcessrequest received");
return Task.FromResult(new Empty());
}
finally
{
_server.ShutdownAsync();
}
}
} The issue is the methods in At the same time gauge runner prints error: |
@nvborisenko One thing which I can think of is |
Right, the capability was added. Didn't work. Any other thoughts? |
Ha, plugin has to share server port via stdout..
Amazing communication. |
Closing it, thanks for support. |
I am trying to use this library to listen to incoming events from gauge. I am creating reporting plugin.
How I do it:
And I got exception:
I blame compatibility between gauge core and gauge runner and gauge any else. I guess that proto messages are not actualized in some gauge layer. Please confirm it or point me how to create reporting plugin in right way in the world of .Net.
Environment:
Sometimes I get
Wire protocol error
.The text was updated successfully, but these errors were encountered: