-
Notifications
You must be signed in to change notification settings - Fork 29
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
panic: runtime error: invalid memory address or nil pointer dereference #2
Comments
Hi, thanks for using our project. This looks like it could be a problem with the go version that you are using, or some other dependency. Have you installed your environment following the azure-install.sh script in the repo? |
Hello, I have installed my environment following the azure-install.sh script and have installed python2.7.12, but it still reports the error in the Figure 1, namely "panic: runtime error: invalid memory address or nil pointer dereference". Could it be a problem with the system version or the go-python library version used? I am using Ubuntu 18.04 now, could you please provide the detailed system version you were using at that time? I would be very grateful if it was possible. |
For our experiments we used the following image: And Azure VM type: If you have access to azure, I'd recommend trying to replicate the setup there, since that's the env we were using. |
I also have the same question, which is displayed as: "panic: runtime error: invalid memory address or nil pointer deference". I have installed the experiment-related environment according to the azure-install file. Has author solved it? How was it solved? My ubuntu system version number is 22.04, is that okay? |
Hello! Thank you for your excellent open source project. When I debug the line "./DistSys -i=1 -t=5 -d=creditcard -c=0", I report an error prompt "panic: runtime error: invalid memory address or nil pointer dereference", and I also report an error when compiling python 2.7.12. Could you provide relevant solutions and the detailed environment you use? I really appreciate it.


The text was updated successfully, but these errors were encountered: