Hi Philippe, There is no need to be so dramatic :) it was not a *known* issue. Better: *I* knew it, because I found same problem last week. I thought it was a problem with my virtual machines, which is still not production released, just collecting issues -like this-, that's why I didn't ran to solve it. When you described the problem, I thought it was same bug... and that's why I started think it was a general UUID plugin bug... we are collecting this problems, and solving them as soon as we can... please, be a little patient, your feedback is very important to us. cheers, Esteban El 20/07/2011, a las 3:36a.m., Philippe Marschall escribió:
On 07/19/2011 09:41 PM, Esteban Lorenzano wrote:
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.
Guys, srsly? Is this some kind of practical joke? You have been shipping with a known bug that has a trivial fix and eats peoples code? You are wondering why nobody takes you seriously and you don't have more users? You teach software engineering?
This is exactly the kind of shit that makes me want to never again use Pharo in production. This is the reason why I don't recommend Pharo to other people.
Cheers Philippe