yes... there is a problem in latest vm's and UUID generation (I don't know if
it is present at any vm or just mines, but well...). For the moment, faster
solution is by deactivating uuid primitive, at:
UUID>>#primMakeUUID
<primitive: 'primitiveMakeUUID' module: 'UUIDPlugin'>
UUIDGenerator default generateBytes: self forVersion: 4.
just comment the primitive call.
cheers,
Esteban
El 19/07/2011, a las 3:45p.m., Philippe Marschall escribió:
> Hi
>
> I have run into an issue where there wouldn't any unique UUIDs be
> produced any more.
>
> ((1 to: 100) collect: [ :i |
> UUID new asString ]) asSet size
>
> answers 2 or 3 in my image.
>
> My system:
> linux 64bit
> cog r2462
> Pharo 1.3 latest updates
> (no changes to the UUID class)
>
> I found the issue because there are several versions of Seaside-Core in
> the WIP repository [1] with the same UUID. For example
> Seaside-Core-pmm.728 and Seaside-Core-pmm.729 or Seaside-Core-pmm.727
> and Seaside-Core-pmm.726.
>
> Since this means I can't write any Seaside code anymore I'm obviously
> not happy.
>
> [1] http://www.squeaksource.com/SeasideWip
>
> Cheers
> Philippe
>
>