Pybullet error: physics server version mismatch (expected 202010061 got 201902120)
I am trying to connect pybullet with VR, and I try to run the example vr code given inside pybullet, vr_kuka_setup_vrSyncPlugin.py, I first ran the "build_visual_studio_vr_pybullet_double.bat" script and the App_PhysicsServer_SharedMemory_VR*.exe, and then I tried vr_kuka_setup_vrSyncPlugin.py, but I get such an error message:
b3Error[examples/SharedMemory/PhysicsClientSharedMemory.cpp,359]:
Error: physics server version mismatch (expected 202010061 got 201902120)
I am pretty sure that there is only one version of pybullet in my computer, the 3.0.9, and the python file and App_PhysicsServer_SharedMemory_VR*.exe comes from the same repo, so I don't know what is the problem related to this error? Is it a version error or something else?
output for code:
code itself
I don't think the pybullet connects to the shared memory successfully, and I think it connects to GUI.
Related
Hey guys I have been trying to automate a task on my browser's machine using chromedp.
I tried examples on the repo however they always fail:
unexpected fault address 0x7f7a36461000 fatal error: fault [signal SIGBUS: bus error code=0x2 addr=0x7f7a36461000 pc=0x53a9d5]
Example's source code am running can be found here.
As I understand chromedp comes with headless pre-compiled version of chrome. I have browsed the API documentation to see if it possible to pass a port on which the dev tools is listening, no success.
However when I tried mafredri/cdp it worked. I came to understand that chromedp is failing to start its embedded chrome. Although, I am not really sure. Why is this happening?
My env:
Google Chrome 85.0.4183.102
Ubuntu 18.04.4 LTS
go version go1.13.5 linux/amd64
Any help would be truly appreciated.
So, long story short I went to run tests on the chromedp locally installed library through go test, it failed. I opened an issue on the Github repo. While it was not indicated that it requires Go 1.14+ but it does.
If you encountered this issue, please proceed to first run the tests on the master branch locally installed library. If it is fails with the following log:
github.com/chromedp/chromedp [github.com/chromedp/chromedp.test]
./chromedp_test.go:862:3: t.Cleanup undefined (type *testing.T has no
field or method Cleanup) ./chromedp_test.go:948:5: t.Cleanup undefined
(type *testing.T has no field or method Cleanup)
./chromedp_test.go:950:5: t.Cleanup undefined (type *testing.T has no
field or method Cleanup) FAIL github.com/chromedp/chromedp [build
failed]
You need to know that t.Cleanup was added on Go 1.14 (credits to Oiyoo).
I hope this helps you if you are having the same problem.
I am using terraform on my Mac system, and terraform apply results with below error
Error: command "bash" failed with no error message
on ssm.tf line 7, in data "external" "ssm-dynamic-general":
7: data "external" "ssm-dynamic-general" {
However there is nothing wrong in ssm.tf file, same runs perfectly fine in my another system.
Can some one please let me know what i am missing here?
You might have done what I accidentally did: not follow the external program protocol:
https://www.terraform.io/docs/providers/external/data_source.html#external-program-protocol
In my particular case, I failed to send the errors that were coming from my program to standard error. Instead, those errors were going to standard out.
That's why Terraform wasn't able to report on those errors.
So if you send any and all errors from your program to standard error using > &2, you should be able to see those errors when you run terraform plan.
Following the official guide of Titan DB here, and trying to run the command:
graph = TitanFactory.open('conf/titan-cassandra-es.properties')
I got this error:
Backend shorthand unknown: conf/titan-cassandra-es.properties
Obviously, the reason is the incorrect path to the
titan-cassandra-es.properties
file. So I changed it to:
graph = TitanFactory.open('../conf/titan-cassandra-es.properties')
and got this error:
Encountered unregistered class ID: 141.
The error happens in the following version:
titan-0.5.4-hadoop2
On titan-1.0.0-hadoop2 instead of this error message I get this one:
Invalid import definition: 'com.thinkaurelius.titan.hadoop.MapReduceIndexManagement'; reason: startup failed: script14747941661821834264593.groovy: 1: unable to resolve class com.thinkaurelius.titan.hadoop.MapReduceIndexManagement # line 1, column 1. import com.thinkaurelius.titan.hadoop.MapReduceIndexManagement ^
1 error
And on titan-1.0.0-hadoop2 I get this one:
The input line is too long.
The syntax of the command is incorrect.
Does anyone know how to handle this issue?
It seems like you have not even managed to get Titan 1 to start up yet.
I do not believe Titan 1 has been deployed to support Windows out of the box. I.e. the downloadable package will not just work with windows.
Saying that I have managed to get Titan DB 1 to work on windows. To do so, all you have to do is install Cassandra 2.x on Windows. This guide may help you out. Start cassandra and enable thrift connections.
With that done you should be able to get Titan doing basic operations on windows. From there you may find dealing with you current errors easier.
Side Note: Windows support for Titan 0.5.x may be more substantial. So you could look into that as well.
I'm not able to run a new phoenix app. This is the error I'm getting; I'm not sure what the reason could be.
I tried changing the port, which didn't change the behaviour. Also, it seems like I'm able to run node correctly.
Compiled web/views/error_view.ex
Compiled web/controllers/page_controller.ex
Compiled web/views/page_view.ex
Compiled web/views/layout_view.ex
Compiled lib/test_phoenix/endpoint.ex
Generated test_phoenix app
[info] Running TestPhoenix.Endpoint with Cowboy on port 4000 (http)
net.js:156
this._handle.open(options.fd);
^
Error: EINVAL, invalid argument
at new Socket (net.js:156:18)
at process.stdin (node.js:664:19)
at bindWatcherEvents (c:\Desarrollo\Phoenix\test_phoenix\node_modules\brunch\l
ib\watch.js:597:12)
at c:\******\Phoenix\test_phoenix\node_modules\brunch\lib\watch.js:667:9
at c:\******\Phoenix\test_phoenix\node_modules\brunch\lib\watch.js:557:16
at c:\******\Phoenix\test_phoenix\node_modules\brunch\lib\watch.js:188:12
at c:\******\Phoenix\test_phoenix\node_modules\brunch\node_modules\async-e
ach\index.js:24:44
at c:\******\Phoenix\test_phoenix\node_modules\brunch\lib\watch.js:175:14
at Object.cb [as oncomplete] (fs.js:168:19)
I was just running into a similar problem and I updated Node to the latest version as Jose Valim suggested. That fixed the problem.
I'm compiling a basic example (as much as using bare X could be simple...) using the X11's RECORD extension on the latest version of Ubuntu, and I'm getting the following error:
RECORD extension for local server is version is 1.13
X Error of failed request: XRecordBadContext
Major opcode of failed request: 135 (RECORD)
Minor opcode of failed request: 5 (XRecordEnableContext)
Context in failed request: 0x17
Serial number of failed request: 10
Current serial number in output stream: 10
Any hints about what's wrong?
I believe that the XRECORD extension is broken in current servers (see https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/315456, although I hit problems with cnee long after the date the fix was supposed to be available). You might want to try installing an older Linux distribution in a virtual machine and giving the sample code a try there.