I am pleased to announce the immediate availability of Magma 1.0 release "44" for both Squeak, 3.9, 3.10 and Pharo. Although I am looking into alternatives for future releases, for now I am still distributing Magma in my traditional ways:
- On SqueakMap - three one-click installable packages.
- In the "1.0r44" Monticello Configuration in the "Magma" project of squeaksource, there are three one-click installable configurations (client, server, tester).
- The "r44Final" Monticello Configuration in the "MagmaTester" project of squeaksource is the one-click installable MagmaTester package.
As has always been the case, ONLY ONE of the three packages needs to be installed, the full and proper configuration is loaded with one-click.
Compared to r43, this is mostly a maintenance release without any major new functionality, but with improved robustness in the HA and luxury querying as well as several other fixes. Here are the specific improvements over 43:
- Made several HA fixes and improvements, many identified by Bart Gaquie by testing with more than a two-server Magma Node. Many thanks Bart. - Updated MaQueryExecutor>>#fractionComplete to answer an unreduced Fraction instead of a reduced one. This convey's more information; since the denominator represents the total number of elements in the final result. Thanks again to Bart Gauqie. - Upgraded MagmaCollectionReader>>#release to allow give a well-behaved application much freer access to the "luxury" query features of MagmaCollections. It is essential for applications employing luxury query features of Magma for ad-hoc querying, to #release the Reader returned from the query so that resources on the server can be freed. - Now properly truncating the applied.images file, so it doesn't grow and grow.. - Now, when a repository is opened locally, if it's location has never been set (new repository) or was a different *local* location, then update it to the new aMagmaLocalLocation. If it was formerly a network-hosted server, do not update since we could be here simply just for re-opening that repository. So, to go from a remote repository to a local one, you have to manually update the node's primaryLocation. - Server no longer allows any clients to log in with the system name, since it is sometimes checked for special-purpose server housekeeping. - Updated MagmaSession's standard printing method, again! - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending: and #sortBy:makeDistinct:descending:. - Made MaRepositoryDisconnectRequest asynchronous, it now returns considerably faster! - Fix for a recent MagmaCollection optimization. - Removed hard-reference to OSProcess. - Patch for #removeListener to avoid DependentsArray problem. - Fixed a ReadStrategy regression.
Hi Chris, Once again, thanks for your work. One question though, is this version running fine on the latest Pharo 1.0 ? I haven't been able to start a server successfuly, I get a primitive has failed. It doesn't run on Pharo 1.1 or Squeak trunk but you didn't mention those :)
I loaded it in a fresh Pharo 1.0 image using:
ScriptLoader new installer. Installer ss project: 'Magma'; install: '1.0r44 (server)'.
Cheers
r
On Wed, Feb 17, 2010 at 8:46 PM, Chris Muller asqueaker@gmail.com wrote:
I am pleased to announce the immediate availability of Magma 1.0 release "44" for both Squeak, 3.9, 3.10 and Pharo. Although I am looking into alternatives for future releases, for now I am still distributing Magma in my traditional ways:
On SqueakMap - three one-click installable packages.
In the "1.0r44" Monticello Configuration in the "Magma" project of
squeaksource, there are three one-click installable configurations (client, server, tester).
- The "r44Final" Monticello Configuration in the "MagmaTester"
project of squeaksource is the one-click installable MagmaTester package.
As has always been the case, ONLY ONE of the three packages needs to be installed, the full and proper configuration is loaded with one-click.
Compared to r43, this is mostly a maintenance release without any major new functionality, but with improved robustness in the HA and luxury querying as well as several other fixes. Here are the specific improvements over 43:
- Made several HA fixes and improvements, many identified by BartGaquie by testing with more than a two-server Magma Node. Many thanks Bart. - Updated MaQueryExecutor>>#fractionComplete to answer an unreduced Fraction instead of a reduced one. This convey's more information; since the denominator represents the total number of elements in the final result. Thanks again to Bart Gauqie. - Upgraded MagmaCollectionReader>>#release to allow give a well-behaved application much freer access to the "luxury" query features of MagmaCollections. It is essential for applications employing luxury query features of Magma for ad-hoc querying, to #release the Reader returned from the query so that resources on the server can be freed. - Now properly truncating the applied.images file, so it doesn't grow and grow.. - Now, when a repository is opened locally, if it's location has never been set (new repository) or was a different *local* location, then update it to the new aMagmaLocalLocation. If it was formerly a network-hosted server, do not update since we could be here simply just for re-opening that repository. So, to go from a remote repository to a local one, you have to manually update the node's primaryLocation. - Server no longer allows any clients to log in with the system name, since it is sometimes checked for special-purpose server housekeeping. - Updated MagmaSession's standard printing method, again! - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending: and #sortBy:makeDistinct:descending:. - Made MaRepositoryDisconnectRequest asynchronous, it now returns considerably faster! - Fix for a recent MagmaCollection optimization. - Removed hard-reference to OSProcess. - Patch for #removeListener to avoid DependentsArray problem. - Fixed a ReadStrategy regression. _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Hi Ramiro, something happened between Pharo1.0-10502-rc1dev09.12.2. and 10508 related to Networking. Please see:
http://lists.gforge.inria.fr/pipermail/pharo-project/2010-February/021912.ht...
I am not sure what happened. Perhaps someone on the Pharo team would elaborate?
- Chris
On Tue, Feb 23, 2010 at 6:54 PM, Ramiro Diaz Trepat ramiro@diaztrepat.name wrote:
Hi Chris, Once again, thanks for your work. One question though, is this version running fine on the latest Pharo 1.0 ? I haven't been able to start a server successfuly, I get a primitive has failed. It doesn't run on Pharo 1.1 or Squeak trunk but you didn't mention those :) I loaded it in a fresh Pharo 1.0 image using: ScriptLoader new installer. Installer ss project: 'Magma'; install: '1.0r44 (server)'.
Cheers
r
On Wed, Feb 17, 2010 at 8:46 PM, Chris Muller asqueaker@gmail.com wrote:
I am pleased to announce the immediate availability of Magma 1.0 release "44" for both Squeak, 3.9, 3.10 and Pharo. Although I am looking into alternatives for future releases, for now I am still distributing Magma in my traditional ways:
- On SqueakMap - three one-click installable packages.
- In the "1.0r44" Monticello Configuration in the "Magma" project of squeaksource, there are three one-click installable configurations (client, server, tester).
- The "r44Final" Monticello Configuration in the "MagmaTester" project of squeaksource is the one-click installable MagmaTester package.
As has always been the case, ONLY ONE of the three packages needs to be installed, the full and proper configuration is loaded with one-click.
Compared to r43, this is mostly a maintenance release without any major new functionality, but with improved robustness in the HA and luxury querying as well as several other fixes. Here are the specific improvements over 43:
- Made several HA fixes and improvements, many identified by Bart Gaquie by testing with more than a two-server Magma Node. Many thanks Bart. - Updated MaQueryExecutor>>#fractionComplete to answer an unreduced Fraction instead of a reduced one. This convey's more information; since the denominator represents the total number of elements in the final result. Thanks again to Bart Gauqie. - Upgraded MagmaCollectionReader>>#release to allow give a well-behaved application much freer access to the "luxury" query features of MagmaCollections. It is essential for applications employing luxury query features of Magma for ad-hoc querying, to #release the Reader returned from the query so that resources on the server can be freed. - Now properly truncating the applied.images file, so it doesn't grow and grow.. - Now, when a repository is opened locally, if it's location has never been set (new repository) or was a different *local* location, then update it to the new aMagmaLocalLocation. If it was formerly a network-hosted server, do not update since we could be here simply just for re-opening that repository. So, to go from a remote repository to a local one, you have to manually update the node's primaryLocation. - Server no longer allows any clients to log in with the system name, since it is sometimes checked for special-purpose server housekeeping. - Updated MagmaSession's standard printing method, again! - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending: and #sortBy:makeDistinct:descending:. - Made MaRepositoryDisconnectRequest asynchronous, it now returns considerably faster! - Fix for a recent MagmaCollection optimization. - Removed hard-reference to OSProcess. - Patch for #removeListener to avoid DependentsArray problem. - Fixed a ReadStrategy regression. _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Hi Chris, thanks for your reply, I am aware of all the problems caused by the new NetNameResolver in Pharo. Nevertheless, I have been unable to cleanly install Magma from SqueakMap or Monticello on Squeak 3.10.2-7179 which I believe is the latest stable release, nor on the latest trunk build. I get errors during the installation. It would be great if you could take a look at the installation process, or even provide ready images like Seaside's. Thanks
r
On Wed, Feb 24, 2010 at 4:38 AM, Chris Muller asqueaker@gmail.com wrote:
Hi Ramiro, something happened between Pharo1.0-10502-rc1dev09.12.2. and 10508 related to Networking. Please see:
http://lists.gforge.inria.fr/pipermail/pharo-project/2010-February/021912.ht...
I am not sure what happened. Perhaps someone on the Pharo team would elaborate?
- Chris
On Tue, Feb 23, 2010 at 6:54 PM, Ramiro Diaz Trepat ramiro@diaztrepat.name wrote:
Hi Chris, Once again, thanks for your work. One question though, is this version running fine on the latest Pharo 1.0
?
I haven't been able to start a server successfuly, I get a primitive has failed. It doesn't run on Pharo 1.1 or Squeak trunk but you didn't mention those
:)
I loaded it in a fresh Pharo 1.0 image using: ScriptLoader new installer. Installer ss project: 'Magma'; install: '1.0r44 (server)'.
Cheers
r
On Wed, Feb 17, 2010 at 8:46 PM, Chris Muller asqueaker@gmail.com
wrote:
I am pleased to announce the immediate availability of Magma 1.0 release "44" for both Squeak, 3.9, 3.10 and Pharo. Although I am looking into alternatives for future releases, for now I am still distributing Magma in my traditional ways:
On SqueakMap - three one-click installable packages.
In the "1.0r44" Monticello Configuration in the "Magma" project of
squeaksource, there are three one-click installable configurations (client, server, tester).
- The "r44Final" Monticello Configuration in the "MagmaTester"
project of squeaksource is the one-click installable MagmaTester package.
As has always been the case, ONLY ONE of the three packages needs to be installed, the full and proper configuration is loaded with one-click.
Compared to r43, this is mostly a maintenance release without any major new functionality, but with improved robustness in the HA and luxury querying as well as several other fixes. Here are the specific improvements over 43:
- Made several HA fixes and improvements, many identified by BartGaquie by testing with more than a two-server Magma Node. Many thanks Bart. - Updated MaQueryExecutor>>#fractionComplete to answer an
unreduced
Fraction instead of a reduced one. This convey's more information; since the denominator represents the total number of elements in the final result. Thanks again to Bart Gauqie. - Upgraded MagmaCollectionReader>>#release to allow give a well-behaved application much freer access to the "luxury" query features of MagmaCollections. It is essential for applications employing luxury query features of Magma for ad-hoc querying, to #release the Reader returned from the query so that resources on the server can be freed. - Now properly truncating the applied.images file, so it doesn't grow and grow.. - Now, when a repository is opened locally, if it's location has never been set (new repository) or was a different *local* location, then update it to the new aMagmaLocalLocation. If it was formerly a network-hosted server, do not update since we could be here simply just for re-opening that repository. So, to go from a remote repository to a local one, you have to manually update the node's primaryLocation. - Server no longer allows any clients to log in with the system name, since it is sometimes checked for special-purpose server housekeeping. - Updated MagmaSession's standard printing method, again! - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending:
and
#sortBy:makeDistinct:descending:. - Made MaRepositoryDisconnectRequest asynchronous, it now returns considerably faster! - Fix for a recent MagmaCollection optimization. - Removed hard-reference to OSProcess. - Patch for #removeListener to avoid DependentsArray problem. - Fixed a ReadStrategy regression. _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Hi Ramiro, I just tested installing into Pharo 10508 via MC Configurations. There is a Warning that you must proceed past regarding EventSensor. This is a harmless warning related to Pharo's renaming of that class to "InputEventSensor" that was discussed on this list last month.
But yes, something did go wrong with the SqueakMap SAR files that had the wrong version of one of the packages specified. This has been fixed and I have tested loading all three tiers (client, server, tester) into a base Squeak 3.10-7179 image. You may now install from SqueakMap.
Thanks for letting me know! Chris
On Sun, Feb 28, 2010 at 7:27 AM, Ramiro Diaz Trepat ramiro@diaztrepat.name wrote:
Hi Chris, thanks for your reply, I am aware of all the problems caused by the new NetNameResolver in Pharo. Nevertheless, I have been unable to cleanly install Magma from SqueakMap or Monticello on Squeak 3.10.2-7179 which I believe is the latest stable release, nor on the latest trunk build. I get errors during the installation. It would be great if you could take a look at the installation process, or even provide ready images like Seaside's. Thanks
r
On Wed, Feb 24, 2010 at 4:38 AM, Chris Muller asqueaker@gmail.com wrote:
Hi Ramiro, something happened between Pharo1.0-10502-rc1dev09.12.2. and 10508 related to Networking. Please see:
http://lists.gforge.inria.fr/pipermail/pharo-project/2010-February/021912.ht...
I am not sure what happened. Perhaps someone on the Pharo team would elaborate?
- Chris
On Tue, Feb 23, 2010 at 6:54 PM, Ramiro Diaz Trepat ramiro@diaztrepat.name wrote:
Hi Chris, Once again, thanks for your work. One question though, is this version running fine on the latest Pharo 1.0 ? I haven't been able to start a server successfuly, I get a primitive has failed. It doesn't run on Pharo 1.1 or Squeak trunk but you didn't mention those :) I loaded it in a fresh Pharo 1.0 image using: ScriptLoader new installer. Installer ss project: 'Magma'; install: '1.0r44 (server)'.
Cheers
r
On Wed, Feb 17, 2010 at 8:46 PM, Chris Muller asqueaker@gmail.com wrote:
I am pleased to announce the immediate availability of Magma 1.0 release "44" for both Squeak, 3.9, 3.10 and Pharo. Although I am looking into alternatives for future releases, for now I am still distributing Magma in my traditional ways:
- On SqueakMap - three one-click installable packages.
- In the "1.0r44" Monticello Configuration in the "Magma" project of squeaksource, there are three one-click installable configurations (client, server, tester).
- The "r44Final" Monticello Configuration in the "MagmaTester" project of squeaksource is the one-click installable MagmaTester package.
As has always been the case, ONLY ONE of the three packages needs to be installed, the full and proper configuration is loaded with one-click.
Compared to r43, this is mostly a maintenance release without any major new functionality, but with improved robustness in the HA and luxury querying as well as several other fixes. Here are the specific improvements over 43:
- Made several HA fixes and improvements, many identified by Bart Gaquie by testing with more than a two-server Magma Node. Many thanks Bart. - Updated MaQueryExecutor>>#fractionComplete to answer an unreduced Fraction instead of a reduced one. This convey's more information; since the denominator represents the total number of elements in the final result. Thanks again to Bart Gauqie. - Upgraded MagmaCollectionReader>>#release to allow give a well-behaved application much freer access to the "luxury" query features of MagmaCollections. It is essential for applications employing luxury query features of Magma for ad-hoc querying, to #release the Reader returned from the query so that resources on the server can be freed. - Now properly truncating the applied.images file, so it doesn't grow and grow.. - Now, when a repository is opened locally, if it's location has never been set (new repository) or was a different *local* location, then update it to the new aMagmaLocalLocation. If it was formerly a network-hosted server, do not update since we could be here simply just for re-opening that repository. So, to go from a remote repository to a local one, you have to manually update the node's primaryLocation. - Server no longer allows any clients to log in with the system name, since it is sometimes checked for special-purpose server housekeeping. - Updated MagmaSession's standard printing method, again! - Added MagmaCollectionReader>>#sortBy:makeDistinct:descending: and #sortBy:makeDistinct:descending:. - Made MaRepositoryDisconnectRequest asynchronous, it now returns considerably faster! - Fix for a recent MagmaCollection optimization. - Removed hard-reference to OSProcess. - Patch for #removeListener to avoid DependentsArray problem. - Fixed a ReadStrategy regression. _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Hi Chris, thanks for your reply, I am aware of all the problems caused by the new NetNameResolver in Pharo.
BTW, I am not so aware of these problems. Basic networking seems to be so badly broken I am not even able to connect a socket, so I've got to think any networking application, including even Seaside, would be broken. I'm surprised that such a breakage would be allowed to persist in Pharo for so long. Do you know what is going on and what the plan is?
Adrian did a change and asked for feedback. Not sure what happened.
On Tue, Mar 2, 2010 at 4:56 PM, Chris Muller asqueaker@gmail.com wrote:
Hi Chris, thanks for your reply, I am aware of all the problems caused by the new NetNameResolver in Pharo.
BTW, I am not so aware of these problems. Basic networking seems to be so badly broken I am not even able to connect a socket, so I've got to think any networking application, including even Seaside, would be broken. I'm surprised that such a breakage would be allowed to persist in Pharo for so long. Do you know what is going on and what the plan is? _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
Please check the issue in our tracker to follow the progress: http://code.google.com/p/pharo/issues/detail?id=1884
For some platforms/configurations (IPv4 vs. v6) it is working (also depending on manually setting useOldNetwork). So there are many variables involved, which makes fixing difficult. But we will get there eventually. Any help welcome of course :)
On Wed, Mar 3, 2010 at 10:37 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
Adrian did a change and asked for feedback. Not sure what happened.
On Tue, Mar 2, 2010 at 4:56 PM, Chris Muller asqueaker@gmail.com wrote:
Hi Chris, thanks for your reply, I am aware of all the problems caused
by
the new NetNameResolver in Pharo.
BTW, I am not so aware of these problems. Basic networking seems to be so badly broken I am not even able to connect a socket, so I've got to think any networking application, including even Seaside, would be broken. I'm surprised that such a breakage would be allowed to persist in Pharo for so long. Do you know what is going on and what the plan is? _______________________________________________ Magma mailing list Magma@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/magma
magma@lists.squeakfoundation.org
-
Chris Muller -
Mariano Martinez Peck -
Ramiro Diaz Trepat