<div dir="ltr">oops, please ignore...<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 21, 2020 at 12:06 PM Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com">eliot.miranda@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="auto">Hi Fabio,<br><div dir="ltr"><br></div><div dir="ltr"><br><blockquote type="cite">On Jul 28, 2020, at 12:10 PM, Fabio Niephaus <<a href="mailto:lists@fniephaus.com" target="_blank">lists@fniephaus.com</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div>On Tue, 28 Jul 2020 at 8:31 pm, karl ramberg <<a href="mailto:karlramberg@gmail.com" target="_blank">karlramberg@gmail.com</a>> wrote:<br></div><div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr"><div>Who can update so that new bundles from <a href="http://files.squeak.org/trunk/" target="_blank">http://files.squeak.org/trunk/</a> uses new VM ?</div></div></blockquote><div dir="auto"><br></div><div dir="auto">I can do that, but I wonder whether there should be a new VM release? I haven't fully followed the discussion: are the changes backwards compatible?</div><div dir="auto"><br></div><div dir="auto">Fabio</div><div dir="auto"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div dir="ltr"><div></div><div><br></div><div>Best,</div><div>Karl<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 27, 2020 at 10:47 AM Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" target="_blank">marcel.taeumel@hpi.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)"><div id="gmail-m_-2413959672132951793m_4712224047141870903m_-3422360800944155014gmail-m_-8228207970398476809__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0)">
Works: <div style="font-family:Arial"><div><image.png></div><div style="font-family:Arial"></div>
</div><div style="font-family:Arial"><br></div><div style="font-family:Arial">Best,</div><div style="font-family:Arial">Marcel</div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px;min-width:500px;font-family:Arial">
<p style="margin-top:10px;font-family:Arial;color:rgb(170,170,170)">Am 23.07.2020 13:41:17 schrieb Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" style="font-family:Arial" target="_blank">marcel.taeumel@hpi.de</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div id="gmail-m_-2413959672132951793m_4712224047141870903m_-3422360800944155014gmail-m_-8228207970398476809__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0)">
Hmm... AppVeyor is just for the Windows builds. We might want to do a beta release for such crucial fixes and then point to the GitHub releases page?<div style="font-family:Arial"><br></div><div style="font-family:Arial">Best,</div><div style="font-family:Arial">Marcel</div><div style="font-family:Arial"></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px;min-width:500px;font-family:Arial">
<p style="margin-top:10px;font-family:Arial;color:rgb(170,170,170)">Am 22.07.2020 19:50:31 schrieb Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" style="font-family:Arial" target="_blank">eliot.miranda@gmail.com</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><br></div><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><br><blockquote type="cite" style="min-width:500px;font-family:Arial,Helvetica,sans-serif">On Jul 22, 2020, at 7:44 AM, Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" style="font-family:Arial,Helvetica,sans-serif" target="_blank">marcel.taeumel@hpi.de</a>> wrote:<br><br></blockquote></div><blockquote type="cite" style="min-width:500px;font-family:Arial,Helvetica,sans-serif"><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><div id="gmail-m_-2413959672132951793m_4712224047141870903m_-3422360800944155014gmail-m_-8228207970398476809__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0)">
Hi Eliot,<div style="font-family:Arial"><br></div><div style="font-family:Arial">looks good. In "About Squeak", we point to "Visit <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm" style="font-family:Arial" target="_blank">https://github.com/OpenSmalltalk/opensmalltalk-vm</a>".</div></div></div></blockquote><div style="font-family:Arial,Helvetica,sans-serif"><br></div>Should we augment that with a direct pointer to the Appveyor CI server?<div style="font-family:Arial,Helvetica,sans-serif"><br><blockquote type="cite" style="min-width:500px;font-family:Arial,Helvetica,sans-serif"><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><div id="gmail-m_-2413959672132951793m_4712224047141870903m_-3422360800944155014gmail-m_-8228207970398476809__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0)"><div style="font-family:Arial"><br></div><div style="font-family:Arial">Best,</div><div style="font-family:Arial">Marcel</div><div style="font-family:Arial"></div><blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px;min-width:500px;font-family:Arial">
<p style="margin-top:10px;font-family:Arial;color:rgb(170,170,170)">Am 22.07.2020 16:41:08 schrieb Eliot Miranda <<a href="mailto:eliot.miranda@gmail.com" style="font-family:Arial" target="_blank">eliot.miranda@gmail.com</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif"><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><br></div><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><blockquote type="cite" style="min-width:500px;font-family:Arial,Helvetica,sans-serif">On Jul 22, 2020, at 12:49 AM, Marcel Taeumel <<a href="mailto:marcel.taeumel@hpi.de" style="font-family:Arial,Helvetica,sans-serif" target="_blank">marcel.taeumel@hpi.de</a>> wrote:<br><br></blockquote></div><blockquote type="cite" style="min-width:500px;font-family:Arial,Helvetica,sans-serif"><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><div id="gmail-m_-2413959672132951793m_4712224047141870903m_-3422360800944155014gmail-m_-8228207970398476809__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0)">
Hi Levente.<div style="font-family:Arial"><br></div><div style="font-family:Arial">> <span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">I'm thinking about checking the VM version in the preamble of the package</span></div><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">> and raising a Warning when it clearly lacks the required updates.</span><br style="font-family:Arial,Helvetica,sans-serif;font-size:13px"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">> Users can still continute with a Warning or terminate the update process,</span><br style="font-family:Arial,Helvetica,sans-serif;font-size:13px"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">> while cli tools will act as if an error had occured.</span><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px"><br></span></div><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">+1</span></div><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px"><br></span></div><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">A one-liner would be nice. The warning should also (roughly) point to the location of the new VM for download.</span></div><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px"><br></span></div><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">MCMcmUpdater checkVM: </span><span style="font-family:Arial,Helvetica,sans-serif"><span style="font-size:13px;font-family:Arial,Helvetica,sans-serif">202003021730. "and newer"</span></span></div></div></div></blockquote><div style="font-family:Arial,Helvetica,sans-serif"><br></div>I wrote it like this:<div style="font-family:Arial,Helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"><br></span></div><div style="font-family:Arial,Helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif;background-color:rgb(255,255,255)"> "Use of the Spur FloatArray>>at:[put:] prims requires at least VMMaker.oscog.2778"</span></div><div style="font-family:Arial,Helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif;background-color:rgb(255,255,255)"><br></span></div><div style="font-family:Arial,Helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif">Smalltalk vmVMMakerVersion < 2778 ifTrue:</span><div style="font-family:Arial,Helvetica,sans-serif"><span style="font-family:Arial,Helvetica,sans-serif"> [Warning signal: 'This virtual machine is too old to support correct versions of the FloatArray>>at:[put:] primitives 238 and 239. FloatArray subclasses will not behave correctly and FloatArray[64]Test tests will fail. Please upgrade your VM. You may continue and upgrade later or abort and upgrade now.']!</span></div><div style="font-family:Arial,Helvetica,sans-serif"><span style="font-size:20px;font-family:Arial,Helvetica,sans-serif"><br></span><blockquote type="cite" style="min-width:500px;font-family:Arial,Helvetica,sans-serif"><div dir="ltr" style="font-family:Arial,Helvetica,sans-serif"><div id="gmail-m_-2413959672132951793m_4712224047141870903m_-3422360800944155014gmail-m_-8228207970398476809__MailbirdStyleContent" style="font-size:10pt;font-family:Arial;color:rgb(0,0,0)"><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">Best,</span></div><div style="font-family:Arial"><span style="font-family:Arial,Helvetica,sans-serif;font-size:13px">Marcel</span></div><div style="font-family:Arial"></div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-top:20px;margin-left:0px;padding-left:10px;min-width:500px;font-family:Arial">
<p style="margin-top:10px;font-family:Arial;color:rgb(170,170,170)">Am 21.07.2020 20:21:39 schrieb Levente Uzonyi <<a href="mailto:leves@caesar.elte.hu" style="font-family:Arial" target="_blank">leves@caesar.elte.hu</a>>:</p><div style="font-family:Arial,Helvetica,sans-serif">Hi Eliot,
<br>
<br>On Mon, 20 Jul 2020, Eliot Miranda wrote:
<br>
<br>> Hi All,
<br>> I've just found and fixed a VM bug in an as-yet-unpublished pair of primitives that replace FloatArrayPlugin>>primitiveAt[Put] and Float64ArrayPlugin>>primitiveAt[Put]. The new replacement, which allows two methods
<br>> (at:[put:]) in FloatArray to relace four methods (Float32Array>>at:[put:] & Float64Array>>at:[put:]) are some 5 to 10 times faster than the plugin methods. The issue is when to publish the corrections to trunk.
<br>> Since the existing VM is broken I don't want to simply push to trunk and have people inconvenienced by a sudden emergence of failures in the FoatArrayTests. However, I do want to push the corrections soon, because they're a
<br>> substantial improvement. So the question is how long should I wait?
<br>>
<br>> Is it OK if I push the fixes to FloatArray and subclasses in a week? Do people using trunk keep an eye on the CI builds and upgrade, or would they appreciate a heads up? If so, as soon as the AppVeyor builds succeed
<br>> for CogVM source as per VMMaker.oscog-eem.2778, I'll let you know and ask that you upgrade your VM.
<br>
<br>I think most people don't update their VMs often. I still tend to fire
<br>up the one shipped with the 5.3 release. So, IMO the question is not how
<br>long to wait but what to do when things are about to break.
<br>I presume that without updating the VM, the image would not work properly.
<br>So, I think the best would be if the user were warned during the update
<br>if the VM would be incompatible with the changes.
<br>I'm thinking about checking the VM version in the preamble of the package
<br>and raising a Warning when it clearly lacks the required updates.
<br>Users can still continute with a Warning or terminate the update process,
<br>while cli tools will act as if an error had occured.
<br>
<br>
<br>Levente
<br>
<br>> _,,,^..^,,,_
<br>> best, Eliot </div></blockquote></div></div></blockquote></div></div></div></div></blockquote></div></div></blockquote></div></div></blockquote></div></div></blockquote></div></blockquote></div></blockquote></div></div></div></blockquote><div><br></div><div>_,,,^..^,,,_ (phone)</div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><span style="font-size:small;border-collapse:separate"><div>_,,,^..^,,,_<br></div><div>best, Eliot</div></span></div></div></div>