Hi all --
Yesterday, we had a new version of the package "MethodMessage", namely "MethodMassage-eem.56.mcz". The mail titled "[Vm-dev] VM Maker: MethodMassage-eem.56.mcz" was the one that usually gets sent after uploading such a version to source.squeak.org. You can see that in the body, which includes "Time: 11 April 2024, 2:49:11.823981 pm".
Unfortunately, we also have several situations where such info messages for older package versions get sent around in a batch. For example, restarting the SqueakSource server behind source.squeak.org, when a couple of versions have not yet been synchronized and then get processed again. Also, there might be an issue with the client-side image and Monticello where can be copied over again and again in a repository, which also triggers those mails. Not sure what happened here.
Sorry for the inconveniences.
Kind regards, Marcel (on behalf of the box-admins team)
Hi Marcel,
On Apr 12, 2024, at 12:37 AM, Taeumel, Marcel via Vm-dev vm-dev@lists.squeakfoundation.org wrote:
Hi all --
Yesterday, we had a new version of the package "MethodMessage", namely "MethodMassage-eem.56.mcz". The mail titled "[Vm-dev] VM Maker: MethodMassage-eem.56.mcz" was the one that usually gets sent after uploading such a version to source.squeak.org. You can see that in the body, which includes "Time: 11 April 2024, 2:49:11.823981 pm".
Unfortunately, we also have several situations where such info messages for older package versions get sent around in a batch. For example, restarting the SqueakSource server behind source.squeak.org, when a couple of versions have not yet been synchronized and then get processed again. Also, there might be an issue with the client-side image and Monticello where can be copied over again and again in a repository, which also triggers those mails. Not sure what happened here.
What I was doing was trying to show someone MethodMassage (a bytecodes method assembler/disassembler framework) for use in code morphing/shape change on package load. The ss3.gemstone.com (might be wrong, but it starts with ss3.gem…) seems to be down (has it disappeared?). So I copied all versions I have to source.squeak.org/VMMaker
Using a lower level to morph code on shape change is a good idea. VisualWorks goes this. It’s potentially much faster than compilation from source. I should have a go at implementing it for Squeak & Cuis sometime.
Sorry for the inconveniences.
Kind regards, Marcel (on behalf of the box-admins team)
Thanks Eliot,
On 2024-04-12 21:37, Eliot Miranda wrote:
Hi Marcel,
On Apr 12, 2024, at 12:37 AM, Taeumel, Marcel via Vm-dev vm-dev@lists.squeakfoundation.org wrote:
Hi all --
Yesterday, we had a new version of the package "MethodMessage", namely "MethodMassage-eem.56.mcz". The mail titled "[Vm-dev] VM Maker: MethodMassage-eem.56.mcz" was the one that usually gets sent after uploading such a version to source.squeak.org. You can see that in the body, which includes "Time: 11 April 2024, 2:49:11.823981 pm".
Unfortunately, we also have several situations where such info messages for older package versions get sent around in a batch. For example, restarting the SqueakSource server behind source.squeak.org, when a couple of versions have not yet been synchronized and then get processed again. Also, there might be an issue with the client-side image and Monticello where can be copied over again and again in a repository, which also triggers those mails. Not sure what happened here.
What I was doing was trying to show someone MethodMassage (a bytecodes method assembler/disassembler framework) for use in code morphing/shape change on package load. The ss3.gemstone.com (might be wrong, but it starts with ss3.gem...) seems to be down (has it disappeared?). So I copied all versions I have to source.squeak.org/VMMaker
Using a lower level to morph code on shape change is a good idea. VisualWorks goes this. It's potentially much faster than compilation from source. I should have a go at implementing it for Squeak & Cuis sometime.
OK good, so this was a legitimate set of update notifications based on new updates to the repository copied in from another repo. It generated some noise on the list, but that's why we send these update notifications to the list, so all good.
Thanks for the explanation, there has recently been some flaky behavior both on the squeaksource servers and maybe on the mailing lists so we are all trying to keep an eye on it. This particular set of update messages might be just YARH (yet another red herring).
Dave
vm-dev@lists.squeakfoundation.org
-
Eliot Miranda -
lewis＠mail.msen.com -
Taeumel, Marcel