Sorry if this is a noob question but is there some way for me to be able to start utilizing these changes before they are fully tested? I am running across this error and hoping this fix will resolve them.

@ryanchesler The changes should be landing very soon if you could wait a bit. If not, you can find the full diff here: https://github.com/pytorch/pytorch/commits/gh/syed-ahmed/13/orig. It's the first 5 commits.

@ezyang all tests have passed in the stack. GitHub is just not updating the statuses

Awesome. Glad this is making it through. Hopefully it solves the issue blocking me.

Hey @syed-ahmed this stack is conflicting with cauchy which I just landed. Can you rebase past that?

Rebased :)

@ezyang merged this pull request in 0e3c4a0.

Hi,
Sorry for this question.
I am facing some issues with rng states (see here).
It was suggested that this merge has fixed the issue.
By checking the date of this merge and the date of the latest version of Pytorch 1.1.0 (April 30), it seems that Pytorch 1.1.0 does not have this feature yet.

Do you have an idea when this feature will be available in a stable version?

I want to publish my code, and make it clear which version of Pytorch I used so it will be easy to install/reproduce.

Thanks!

It will probably be included in 1.2 (assuming it doesn't get reverted before branch cut). You can also try using a nightly to get binaries with the fix earlier.

Thanks!
The issue seems to be fixed in the nightly build (https://download.pytorch.org/whl/nightly/cu100/torch_nightly-1.2.0.dev20190616-cp37-cp37m-linux_x86_64.whl).

I hope 1.2.0 will be released soon!

hi,
@ezyang @syed-ahmed
sorry to bother you.
was this commit integrated in v1.2.0 which was released today?
https://github.com/pytorch/pytorch/releases/tag/v1.2.0

I searched in the notes (key: rng, 21301), and did not find it.
thanks

Yes it's in 1.2.0; 0e3c4a0 is reachable from v1.2.0 branch. It does look like this is missing from the changelog notes.

thanks!