Closed dleibrandt closed 8 years ago
Another thing I guess is problematic is RPCing the Notifier
mutations.
@sbourdeauducq This is a bug in set_dataset--it ought to always return None, or at least, always return the same type, in order to be a valid RPC.
Yes, I'll change it.
I was trying to try out this fix, and I ran into a problem. I'm subscribed to only the main m-labs conda channel. I created a new conda environment following the instructions in the manual today, but it seems that the git commit id of the artiq version that I got is 10 days old:
(artiq-2016-03-29)rabi@688101H116ARTIQ:~/artiq-work$ conda list artiq
# packages in environment at /home/rabi/anaconda3/envs/artiq-2016-03-29:
#
artiq 1.0rc1 py_0+git1c9b8a1 http://conda.anaconda.org/m-labs/channel/main/noarch/artiq-1.0rc1-py_0+git1c9b8a1.tar.bz2
artiq-kc705-nist_clock 1.0rc1 py_0+git1c9b8a1 http://conda.anaconda.org/m-labs/channel/main/noarch/artiq-kc705-nist_clock-1.0rc1-py_0+git1c9b8a1.tar.bz2
asyncserial (/home/rabi/artiq-dev2/asyncserial) 0.1 <pip>
llvmlite-artiq 0.5.1 py35_19 http://conda.anaconda.org/m-labs/channel/main/linux-64/llvmlite-artiq-0.5.1-py35_19.tar.bz2
migen (/home/rabi/artiq-dev2/migen) 0.2 <pip>
misoc (/home/rabi/artiq-dev2/misoc) 0.1 <pip>
Should I be subscribed to the dev channel also?
The fix will be available in the next release (1.0rc2). The dev channel currently has a number of new and serious bugs.
Running this experiment:
Causes this error:
This only occurs when run is a kernel AND broadcast=True.