error image i am getting this error while running my anylogic application therefore not able to run the application
"The source attachment does not contain the source for the file Throwables.class"
Related
I'm using MatlabWithProtoV3 to create protoc.exe with matlab_out in Windows environment.
I was able to create protoc and when I use
protoc.exe user.proto --matlab_out=./
It only creating matlab files for proto messages (files can be found in the bottom attachment) and it is not creating matlab files for services(client and server)
Then, I read about plugins and included the generator and plugin files to gRPC Source to create Matlab plugin and created the grpc_matlab_plugin.exe successfully.
Now, when I execute
protoc.exe user.proto --matlab_out=./ --grpc_out=./ --plugin=protoc-gen-grpc="D:\grpc\cmake\build\Debug\grpc_matlab_plugin.exe
I'm getting
pb_descriptor_LoginRequest.m: Tried to write the same file twice.
pb_read_LoginRequest.m: Tried to write the same file twice.
pb_descriptor_APIResponse.m: Tried to write the same file twice.
pb_read_APIResponse.m: Tried to write the same file twice.
pb_descriptor_Empty.m: Tried to write the same file twice.
pb_read_Empty.m: Tried to write the same file twice.
error message and no files are getting created.
in gRPC repo, for C++ compiler i could find cpp_plugin.h has some codes to create service related files but similar file is not available for Matlab in here or here
Can you please let me know how to create Matlab files for services?
Attached the files created when I execute the above mentioned commands,
sample_files.zip
Github issue
Thanks
protobuf-matlab is just a protobuf plugin - it generates code to read/write protocol buffer.
Unfortunately it does not implement a gRPC plugin which would build the client stub and server.
If you are able to call your matlab code from another language, you could host the gRPC server externally, e.g. create a gRPC server in dotnet and use COM to call your matlab code.
I am trying to run nunit tests in azure test plan by triggering Release build pipelines. I have observed file attachments with greater than 255 characters are not attached to the test report.
Using below code to attach reports TestContext.AddTestAttachment(string path) (comes with nunit package).There is no exception thrown in logs, but just a warning message as below:
Failed to upload result logs to Log store, trying to upload to file service.
File at location is not available on the disk.
Need help on how to attach the file with long paths to the test attachments.
Note: Concerned file is available in the path
The limitation is existed that windows file paths is not longer than 255 characters in Azure test plan.
You could copy or move the files out of the folder into another folder that won't violate the limit. For example, using this Copy Files task to copy file attachments from a source folder to a target folder using match patterns.
I am trying to upload the files using document management API. The file gets uploaded but fails with "We couldn't process the following document. Extraction failed" error message.
I tried uploading image,PDF etc. But the same file gets extracted and published successfully when done manually through UI
Just tested with this sample (source code here) and worked fine.
Everytime I upload a package on my QA server via Package Manager, it keeps loading it for a long time and then throws an error saying "package file parameter missing"
The error logs show absolutely no activity regarding the package.
This happens for both code packages (/apps/...) and content packages (/content/...)
Make sure your server has a tmp (linux) or temp (windows) folder accessible to the AEM process with full permission. This error occurs when the aem process cannot find the temp folder which it uses to temporarily store packages when they are being uploaded.
I've made the transfer of my application from one mac to another, and when I tried to build it, the following error message appears : file does not exist at path 'file://localhost/volumes/tablecellview.xib'
So I don't know how how to deal with that !
right-click on the file in your project view and check to what path it points. If necessary you can adjust it there