Re: [Pharo-dev] Downloading the latest 40 Image - Error
Reproduced with Windows and CentOS 7. Image ZIP downloads but it seems corrupt? $ md5sum image.zip 7ff5e1cbdd434a1194b4777056005143 *image.zip $ file image.zip image.zip: Zip archive data, at least v2.0 to extract 13,6 MB (14.347.593 bytes) $ zip -F image.zip --out img.zip Fix archive (-F) - assume mostly intact archive zip warning: bad archive - missing end signature zip warning: (If downloaded, was binary mode used? If not, the zip warning: archive may be scrambled and not recoverable) zip warning: Can't use -F to fix (try -FF) zip error: Zip file structure invalid (image.zip) $ zip -FF image.zip --out img.zip Fix archive (-FF) - salvage what can zip warning: Missing end (EOCDR) signature - either this archive is not readable or the end is damaged Is this a single-disk archive? (y/n): y Assuming single-disk archive Scanning for entries... copying: Pharo-40593.image (9988133 bytes) copying: Pharo-40594.changes (4362852 bytes) $ unzip img.zip Archive: img.zip inflating: Pharo-40593.image error: invalid compressed data to inflate bad CRC 176d616a (should be cb225fb1) inflating: Pharo-40594.changes error: invalid compressed data to inflate bad CRC aebb9aa5 (should be 4bc50ce1) Cheers, Hernán 2015-04-04 17:32 GMT-03:00 Sven Van Caekenberghe s...@stfx.eu: I think this has to do with CDN caching or cache invalidation. On 04 Apr 2015, at 21:09, Max Leske maxle...@gmail.com wrote: Confirmed. On 04 Apr 2015, at 20:46, Hernán Morales Durand hernan.mora...@gmail.com wrote: FYI $ wget -O- get.pharo.org/40+vm | bash --2015-04-04 18:41:59-- http://get.pharo.org/40+vm Resolving get.pharo.org... 128.93.162.72 Connecting to get.pharo.org|128.93.162.72|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 2885 (2.8K) [text/html] Saving to: `STDOUT' 100%[==] 2,885 --.-K/s in 0.001s 2015-04-04 18:42:00 (2.54 MB/s) - written to stdout [2885/2885] Downloading the latest 40 Image: http://files.pharo.org/image/40/latest.zip [image.MJSoCf/image.zip] End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of image.MJSoCf/image.zip or image.MJSoCf/image.zip.zip, and cannot find image.MJSoCf/image.zip.ZIP, period.
Re: [Pharo-dev] Ways to do 32-bit arithmetics?
On Fri, 3 Apr 2015, Stefan Marr wrote: Hi Eliot: On 03 Apr 2015, at 16:47, Eliot Miranda eliot.mira...@gmail.com wrote: if seed is Andes with 16r when it is initialized then the Java code can be used to generate the next value and the sign conversion only applied once to yield the next value. That would eliminate lots of conversions and make the code readable, right? Sorry, I don’t understand you. In the Java code the `0x` is redundant/superfluous. It’s there because I ported the code from JavaScript. The important part is that Java has signed 32bit integers. So, it works as expected out of the box. The SOM version shows the explicit operations you need if you don’t have any knowledge about the underlying integer representation. In most SOM implementations, integers happen to be represented as 64bit values, that overflow into some form of big/large integer representations. The sign-related operations are necessary to get the correct shift and overflow semantics. I guess I could implement it easily on a 64-bit Spur image, but I haven’t looked into that yet. Marcus’ comment looks also useful, but it is going to be very slow… It's still the fastest option within a 32-bit image (way faster than LargeInteger operations). Of course you could just use Nativeboost if it's for Pharo. Levente Best regards Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/
[Pharo-dev] WhatsUp from: 2015-04-06 until: 2015-04-19
Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-04-19 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)
[Pharo-dev] Add MetaRepoForPharo40 to default repository group
Why not? - Cheers, Sean -- View this message in context: http://forum.world.st/Add-MetaRepoForPharo40-to-default-repository-group-tp4817749.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] New Pull Request for UpdatedPharoByExample
You might have to click on the Watch button on the repo. On Sunday, April 5, 2015, kilon alios kilon.al...@gmail.com wrote: Strangely enough it does not notify me, probably need to change something in my github settings. On Sun, Apr 5, 2015 at 6:39 PM, Dmitri Zagidulin dmi...@zagidulin.net javascript:_e(%7B%7D,'cvml','dmi...@zagidulin.net'); wrote: Thanks, Gaurav! It is now merged. I don't think one needs to send an email to the mailing list, though, for PRs. Github usually notifies anybody who's watching the repository, when new PRs are made. On Sun, Apr 5, 2015 at 9:28 AM, Gaurav Singh grvanm.co...@gmail.com javascript:_e(%7B%7D,'cvml','grvanm.co...@gmail.com'); wrote: I have made a few corrections in the chapter Syntax in a Nutshell. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 Kindly review the pull request.
Re: [Pharo-dev] Magritte = Auto-GT Presentation
NorbertHartl wrote Cool! Can you add a spec based editor for the object? ;) It's on my todo list, but not near the top :/ btw The presenter, packaged in Magritte-GT, now loads by default in Pharo 4.0 with the Magritte3 stable version (3.3), available from the 4.0 meta repo. - Cheers, Sean -- View this message in context: http://forum.world.st/Magritte-Auto-GT-Presentation-tp4817448p4817752.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Metacello: Resolving Conflicting Attributes
Nicolas Cellier wrote If you think your corrections are solid enough and backward compatible, maybe you could push them in these repos too. IIRC the changes were pretty straightforward - just remove FileUrl extensions. I followed the apparent Xtreams convention of creating a pharo40 branch of the effected packages. Config copied to sqs/Xtreams and sqs/MetacelloRepository - Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-Resolving-Conflicting-Attributes-tp4817683p4817754.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] New Pull Request for UpdatedPharoByExample
no, as I suspected I have forgot to change from my old email to my new one. Should work now. On Mon, Apr 6, 2015 at 2:17 AM, Dmitri Zagidulin dmi...@zagidulin.net wrote: You might have to click on the Watch button on the repo. On Sunday, April 5, 2015, kilon alios kilon.al...@gmail.com wrote: Strangely enough it does not notify me, probably need to change something in my github settings. On Sun, Apr 5, 2015 at 6:39 PM, Dmitri Zagidulin dmi...@zagidulin.net wrote: Thanks, Gaurav! It is now merged. I don't think one needs to send an email to the mailing list, though, for PRs. Github usually notifies anybody who's watching the repository, when new PRs are made. On Sun, Apr 5, 2015 at 9:28 AM, Gaurav Singh grvanm.co...@gmail.com wrote: I have made a few corrections in the chapter Syntax in a Nutshell. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 Kindly review the pull request.
Re: [Pharo-dev] Magritte = Auto-GT Presentation
The editor should be provided if you load the Glamour-Presentations-Magritte. Cheers, Doru On Mon, Apr 6, 2015 at 3:18 AM, Sean P. DeNigris s...@clipperadams.com wrote: NorbertHartl wrote Cool! Can you add a spec based editor for the object? ;) It's on my todo list, but not near the top :/ btw The presenter, packaged in Magritte-GT, now loads by default in Pharo 4.0 with the Magritte3 stable version (3.3), available from the 4.0 meta repo. - Cheers, Sean -- View this message in context: http://forum.world.st/Magritte-Auto-GT-Presentation-tp4817448p4817752.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. -- www.tudorgirba.com Every thing has its own flow
Re: [Pharo-dev] Xtreams Now in MetaRepoForPharo40
Sean P. DeNigris wrote It was a bit ugly... I asked a question on the MetaC list about cleaning it up. Okay, Dale explained how to do it properly (http://forum.world.st/Xtreams-Pharo-4-0-Other-FileSystem-Images-tp4816537p4816756.html). New version published. - Cheers, Sean -- View this message in context: http://forum.world.st/Xtreams-Now-in-MetaRepoForPharo40-tp4816538p4817681.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] Xtreams Now in MetaRepoForPharo40
Thanks Sean. On Sun, Apr 5, 2015 at 10:07 PM, Sean P. DeNigris s...@clipperadams.com wrote: Sean P. DeNigris wrote It was a bit ugly... I asked a question on the MetaC list about cleaning it up. Okay, Dale explained how to do it properly ( http://forum.world.st/Xtreams-Pharo-4-0-Other-FileSystem-Images-tp4816537p4816756.html ). New version published. - Cheers, Sean -- View this message in context: http://forum.world.st/Xtreams-Now-in-MetaRepoForPharo40-tp4816538p4817681.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
[Pharo-dev] Metacello: Resolving Conflicting Attributes
Dale taught me something helpful (and maybe a little obscure) while fixing ConfigurationOfXtreams... Problem: Say you have a platform attribute #pharo4.x, and a #customProjectAttribute #FileSystem. The problem is that the FileSystem-related packages required for #pharo4.x are different than those for the default cases. spec for: #'pharo4.x' do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem.pharo40-SeanDeNigris.4' ]. ... spec for: #FileSystem do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem-nice.1'. ] Solution: Nest a spec for: #FileSystem do: inside the spec for: #pharo4.x do: declaring the #pharo4.x-specifics spec for: #'pharo4.x' do: [ spec for: #'FileSystem' do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem.pharo40-SeanDeNigris.4' ]. Why it works: Per Dale, The spec:for:do: blocks are evaluated in attribute order (ConfigurationOfX project attributes) with top-level blocks evaluated before nested blocks ... second level blocks are evaluated in top-level block order after the first level block evaluation ... so having #FileSystem nested inside of #pharo4.x and given that #FileSystem follows #pharo4.x in attribute order means that the nested #FileSystem block inside of #pharo4.x is evaluated after to top-level #FileSystem block allowing you to do #pharo4.x specific overrides - Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-Resolving-Conflicting-Attributes-tp4817683.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Re: [Pharo-dev] 14606 Really Important bug - Can't see some variables values while debugging closure
Thanks both of you for the energy you put into Pharo. The tam really appreciates. This is because there are guys like you that Pharo is worth being done. Thanks for the tests. Esteban has apparently found the bug on the VM. Stef On Sun, Apr 5, 2015 at 1:23 PM, Ben Coman b...@openinworld.com mailto:b...@openinworld.com wrote: I got annoyed since a few times I thought I'd solved everything just the issue looking at the manual examples of one issue, only to find I'd caused the other case to fail. Also keeping track of all cases as I threw away images with partial solutions was awkward. So I turned the examples from all these Cases into tests and uploaded AdditionalTests-14606-13260-15174-BenComan.1 - so solutions can consistently test all cases. These can be integrated once we have a solution for all of them. Can you think of anymore to add? And of course, please advise if you think the tests are correct. cheers -ben They look good. Just for reference, in the slice for fixing issue 13260, I added two testcases MethodMapTest#testCopiedVarFromDeadContext and MethodMapTest#testExampleTempNamedTempVectorInlinedLoop
Re: [Pharo-dev] 14606 Really Important bug - Can't see some variables values while debugging closure
Yes, incredible work, well done. Thank you. On 05 Apr 2015, at 14:59, stepharo steph...@free.fr wrote: Thanks both of you for the energy you put into Pharo. The tam really appreciates. This is because there are guys like you that Pharo is worth being done. Thanks for the tests. Esteban has apparently found the bug on the VM. Stef On Sun, Apr 5, 2015 at 1:23 PM, Ben Coman b...@openinworld.com wrote: I got annoyed since a few times I thought I'd solved everything just the issue looking at the manual examples of one issue, only to find I'd caused the other case to fail. Also keeping track of all cases as I threw away images with partial solutions was awkward. So I turned the examples from all these Cases into tests and uploaded AdditionalTests-14606-13260-15174-BenComan.1 - so solutions can consistently test all cases. These can be integrated once we have a solution for all of them. Can you think of anymore to add? And of course, please advise if you think the tests are correct. cheers -ben They look good. Just for reference, in the slice for fixing issue 13260, I added two testcases MethodMapTest#testCopiedVarFromDeadContext and MethodMapTest#testExampleTempNamedTempVectorInlinedLoop
[Pharo-dev] New Pull Request for UpdatedPharoByExample
I have made a few corrections in the chapter Syntax in a Nutshell. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 Kindly review the pull request.
Re: [Pharo-dev] 14606 Really Important bug - Can't see some variables values while debugging closure
2015-04-05 7:25 GMT+02:00 Ben Coman b...@openinworld.com: On Sun, Apr 5, 2015 at 1:23 PM, Ben Coman b...@openinworld.com wrote: I got annoyed since a few times I thought I'd solved everything just the issue looking at the manual examples of one issue, only to find I'd caused the other case to fail. Also keeping track of all cases as I threw away images with partial solutions was awkward. So I turned the examples from all these Cases into tests and uploaded AdditionalTests-14606-13260-15174-BenComan.1 - so solutions can consistently test all cases. These can be integrated once we have a solution for all of them. Can you think of anymore to add? And of course, please advise if you think the tests are correct. cheers -ben They look good. Just for reference, in the slice for fixing issue 13260, I added two testcases MethodMapTest#testCopiedVarFromDeadContext and MethodMapTest#testExampleTempNamedTempVectorInlinedLoop
Re: [Pharo-dev] 14606 Really Important bug - Can't see some variables values while debugging closure
On Sun, Apr 5, 2015 at 8:59 PM, stepharo steph...@free.fr wrote: Thanks both of you for the energy you put into Pharo. The tam really appreciates. This is because there are guys like you that Pharo is worth being done. Thanks for the tests. Esteban has apparently found the bug on the VM. Stef Energy breeds energy. For me it was an opportunity to learn more deep stuff(tm) by digging with a goal. It remains a bit beyond me, but I'm happy if I've been able to beat the high grass enough to flush the tiger into the open where the marksman can take a shot at it. Nice to flush out a VM bug (can't be too many of those left ;). Let us know when we can do testing on it.I guess I'll read more about it on [vm-dev]. cheers -ben
Re: [Pharo-dev] New Pull Request for UpdatedPharoByExample
Thanks, Gaurav! It is now merged. I don't think one needs to send an email to the mailing list, though, for PRs. Github usually notifies anybody who's watching the repository, when new PRs are made. On Sun, Apr 5, 2015 at 9:28 AM, Gaurav Singh grvanm.co...@gmail.com wrote: I have made a few corrections in the chapter Syntax in a Nutshell. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 Kindly review the pull request.
Re: [Pharo-dev] New Pull Request for UpdatedPharoByExample
Thanks :) On Sun, Apr 5, 2015 at 9:09 PM, Dmitri Zagidulin dmi...@zagidulin.net wrote: Thanks, Gaurav! It is now merged. I don't think one needs to send an email to the mailing list, though, for PRs. Github usually notifies anybody who's watching the repository, when new PRs are made. On Sun, Apr 5, 2015 at 9:28 AM, Gaurav Singh grvanm.co...@gmail.com wrote: I have made a few corrections in the chapter Syntax in a Nutshell. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 Kindly review the pull request.
Re: [Pharo-dev] Spotter
Am 05.04.2015 um 19:09 schrieb Ben Coman b...@openinworld.com: On Sun, Apr 5, 2015 at 11:37 PM, stepharo steph...@free.fr mailto:steph...@free.fr wrote: aliaksei what would be nice is that each time we click on a button or press a command key you emit a growl notification with the description. Stef For just a moment there, I thought you wanted Spotter to start making bear noises? *grin* Me, too. But the moment didn't finish yet Norbert
Re: [Pharo-dev] Spotter
The problem of people like a tool too much you get a ton of feature requests :D I don't envy those poor developers.
Re: [Pharo-dev] New Pull Request for UpdatedPharoByExample
Strangely enough it does not notify me, probably need to change something in my github settings. On Sun, Apr 5, 2015 at 6:39 PM, Dmitri Zagidulin dmi...@zagidulin.net wrote: Thanks, Gaurav! It is now merged. I don't think one needs to send an email to the mailing list, though, for PRs. Github usually notifies anybody who's watching the repository, when new PRs are made. On Sun, Apr 5, 2015 at 9:28 AM, Gaurav Singh grvanm.co...@gmail.com wrote: I have made a few corrections in the chapter Syntax in a Nutshell. Link to the pull request: https://github.com/SquareBracketAssociates/UpdatedPharoByExample/pull/30 Kindly review the pull request.
Re: [Pharo-dev] Ways to do 32-bit arithmetics?
Hi: On 03 Apr 2015, at 17:44, Eliot Miranda eliot.mira...@gmail.com wrote: seed := ((seed + 16r7ed55d16) + (seed 12)) 16r. seed := ((seed ^ 16rc761c23c) ^ (seed as32BitSignedValue 19)) 16r. seed := ((seed + 16r165667b1) + (seed5)) 16r. seed := ((seed + 16rd3a2646c) ^ (seed9)) 16r. seed := ((seed + 16rfd7046c5) + (seed3)) 16r. seed := ((seed ^ 16rb55a4f09) ^ (seed as32BitSignedValue 16)) 16r. ^ seed as32BitSignedValue Ok, my implementation looks now like this: random Robert Jenkins' 32 bit integer hash function. seed := ((seed + 16r7ed55d16) + (seed 12)). seed := ((seed bitXor: 16rc761c23c) bitXor: ((seed bitAnd: 16r) 19)). seed := ((seed + 16r165667B1) + (seed 5)). seed := ((seed + 16rd3a2646c) bitXor: (seed 9)). seed := ((seed + 16rfd7046c5) + (seed 3)). seed := self as32BitSigned: ((seed bitXor: 16rb55a4f09) bitXor: ((seed bitAnd: 16r) 16)). ^ seed as32BitSigned: val | r | r := val bitAnd: 16r. (r bitAnd: 16r8000) = 0 ifTrue: [ ^ r ]. ^ (16r1 - r) * -1 The #as32BitSigned: looks a little naive, but didn’t have any better idea. And Andres, the random number generator is a given, I can’t just change it. Best regards Stefan -- Stefan Marr INRIA Lille - Nord Europe http://stefan-marr.de/research/
Re: [Pharo-dev] Spotter
On Sun, Apr 5, 2015 at 11:37 PM, stepharo steph...@free.fr wrote: aliaksei what would be nice is that each time we click on a button or press a command key you emit a growl notification with the description. Stef For just a moment there, I thought you wanted Spotter to start making bear noises? *grin*
Re: [Pharo-dev] 14606 Really Important bug - Can't see some variables values while debugging closure
2015-04-05 17:38 GMT+02:00 Ben Coman b...@openinworld.com: On Sun, Apr 5, 2015 at 8:59 PM, stepharo steph...@free.fr wrote: Thanks both of you for the energy you put into Pharo. The tam really appreciates. This is because there are guys like you that Pharo is worth being done. Thanks for the tests. Esteban has apparently found the bug on the VM. Stef Energy breeds energy. For me it was an opportunity to learn more deep stuff(tm) by digging with a goal. It remains a bit beyond me, but I'm happy if I've been able to beat the high grass enough to flush the tiger into the open where the marksman can take a shot at it. Nice to flush out a VM bug (can't be too many of those left ;). Let us know when we can do testing on it.I guess I'll read more about it on [vm-dev]. cheers -ben If it's a VM bug, the VM folks would be really really interested by a bug report, especially if ever it may affect Eliot's branch. Even if it's a Pharo only bug, it is still very interesting to know, because there's allways something to learn from a bug. So I'm all ears... cheers Nicolas
Re: [Pharo-dev] Metacello: Resolving Conflicting Attributes
Hi Sean, I wish I had more time to dive into this. Before I do, where did you publish the corrections? Only in meta repo for Pharo4? I also maintain a copy at Xtreams http://www.squeaksource.com/Xtreams and another at http://www.squeaksource.com/MetacelloRepository. Sometimes, I also backport to meta repo for Pharo3... If you think your corrections are solid enough and backward compatible, maybe you could push them in these repos too. In all cases, thanks for your contribution. cheers Nicolas 2015-04-05 16:20 GMT+02:00 Sean P. DeNigris s...@clipperadams.com: Dale taught me something helpful (and maybe a little obscure) while fixing ConfigurationOfXtreams... Problem: Say you have a platform attribute #pharo4.x, and a #customProjectAttribute #FileSystem. The problem is that the FileSystem-related packages required for #pharo4.x are different than those for the default cases. spec for: #'pharo4.x' do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem.pharo40-SeanDeNigris.4' ]. ... spec for: #FileSystem do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem-nice.1'. ] Solution: Nest a spec for: #FileSystem do: inside the spec for: #pharo4.x do: declaring the #pharo4.x-specifics spec for: #'pharo4.x' do: [ spec for: #'FileSystem' do: [ spec package: 'Xtreams-TerminalsFileSystem' with: 'Xtreams-TerminalsFileSystem.pharo40-SeanDeNigris.4' ]. Why it works: Per Dale, The spec:for:do: blocks are evaluated in attribute order (ConfigurationOfX project attributes) with top-level blocks evaluated before nested blocks ... second level blocks are evaluated in top-level block order after the first level block evaluation ... so having #FileSystem nested inside of #pharo4.x and given that #FileSystem follows #pharo4.x in attribute order means that the nested #FileSystem block inside of #pharo4.x is evaluated after to top-level #FileSystem block allowing you to do #pharo4.x specific overrides - Cheers, Sean -- View this message in context: http://forum.world.st/Metacello-Resolving-Conflicting-Attributes-tp4817683.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
