use x$lastSeedValue, not .Random.seed (which may not exist) #502
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'm seeing an error where cbind() wounds up run without .Random.seed set, which this solves. Per `?.Random.seed`, no seed is set initially in the session until the first time `set.seed()` is run: > Initially, there is no seed; a new one is created from the current time and the process ID when one is required. I don't know enough about the package to know if this fix is for sure correct, but I noticed a similar fix applied in the same file: amices@1189fe1
|
Thanks. We intend to tackle this one with #515. |
|
Adressed by c084cdd |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'm seeing an error where cbind() wounds up run without .Random.seed set, which this solves.
Per
?.Random.seed, no seed is set initially in the session until the first timeset.seed()is run:I don't know enough about the package to know if this fix is for sure correct, but I noticed a similar fix applied in the same file:
1189fe1