Bug description
On Pharo 12, since a couple of days, the random generator is broken.
Random new next always produces the same value.
This breaks Seaside, who is using the random generator to produce session keys and now all session and continuation keys are aaaaaaaaaaaaa.
Edit: this is a VM issue
It works well with VM Pharo 10.2.1-aeba90c8 built on May 16 2024 15:53:24
But it fails starting with VM Pharo 10.2.1-49e95fa7 built on Jun 4 2024 15:16:03
To Reproduce
Execute the following snippet in Pharo 11 and Pharo 12.
In Pharo 12, the entire collection will have only the value 1 (WRONG).
In Pharo 11, you will get a collection with 1,2 and3 (CORRECT).
| random collection |
random := Random new.
collection := (1 to: 200) collect: [ :e | random nextInteger: 3 ].
collection asSet
Expected behavior
See above.
Version information:
- OS: [Mac] (but also Linux on the Seaside CI)
- Pharo Version 12
- Build information: Pharo-12.0.0+SNAPSHOT.build.1514.sha.3eb8aad6ce720672fe608e9f64aec10e20d577bb
Bug description
On Pharo 12, since a couple of days, the random generator is broken.
Random new nextalways produces the same value.This breaks Seaside, who is using the random generator to produce session keys and now all session and continuation keys are
aaaaaaaaaaaaa.Edit: this is a VM issue
It works well with VM Pharo 10.2.1-aeba90c8 built on May 16 2024 15:53:24
But it fails starting with VM Pharo 10.2.1-49e95fa7 built on Jun 4 2024 15:16:03
To Reproduce
Execute the following snippet in Pharo 11 and Pharo 12.
In Pharo 12, the entire collection will have only the value
1(WRONG).In Pharo 11, you will get a collection with
1,2and3(CORRECT).Expected behavior
See above.
Version information: