<div dir="ltr"><div dir="ltr">Jupiter,<div><br></div><div>Yeah, it looks like this is an interesting run ... in a standard tODE image, Collection>>groupedBy: is in the GsPharo-Core package that is in <a href="http://seaside.gemtalksystems.com/ss/PharoCompat">http://seaside.gemtalksystems.com/ss/PharoCompat</a> ... </div><div><br></div><div>However, there is a GsDevKit/PharoCompatibility project that you may or may not have loaded ... If you haven't loaded it, then I suggest that you load it and determine if the bug exists there as well and if so, then at least it should be a bit more obvious how to fix the issue. so I assume you haven't loaded it ...</div><div><br></div><div>If you look at the GitHub CI runs[2], you will see that the project needs some TLC as well. I created the github actions CI 5 months ago and it seems that it hasn't been passing for a LONG time (there is a bug from 2017[3] and a bug from 5 months ago[4]) ... Frankly in cases where CI tests have been failing for a significant length of time and no one has noticed but me, I have a hard time justifying any time spent keeping the unit tests running (as I have done with a number of the heavily used projects) ...</div><div><br></div><div>Since you are complaining now, I have made a note to add the repository to those that are tested internally before doing a GemStone Release ... I try to make sure that the heavily used projects are tested BEFORE we make a release, to avoid a mad dash of bug fixing on the day we release a product. Also in some cases the bug is "in the product" and it is useful to be able to fix internal errors before the release.</div><div><br></div><div>With that said, it would be helpful if you took a look at the currently failing tests and got the whole shebang to pass while addressing your specific issue ... and at this point in time, I would restrict the list of tested versions to: GemStone64-3.6.2, GemStone64-3.6.1, GemStone64-3.6.0, GemStone64-3.5.7, and GemStone64-3.4.5 ...</div><div><br></div><div>If you open up an issue, we can discuss things in more detail ... I see that PluggableSet has no methods, so it is likely that issue you are seeing exists for Set and other UnorderedCollections. It looks like GsPharoCollectionTests>>testGroupedByHaving is only testing against Array ...</div><div><br></div><div>Dale</div><div><br></div><div>[1] <a href="https://github.com/GsDevKit/PharoCompatibility">https://github.com/GsDevKit/PharoCompatibility</a></div><div>[2] <a href="https://github.com/GsDevKit/PharoCompatibility/actions/runs/1433022813">https://github.com/GsDevKit/PharoCompatibility/actions/runs/1433022813</a></div><div>[3] <a href="https://github.com/GsDevKit/PharoCompatibility/issues/8">https://github.com/GsDevKit/PharoCompatibility/issues/8</a></div><div>[4] <a href="https://github.com/GsDevKit/PharoCompatibility/issues/12">https://github.com/GsDevKit/PharoCompatibility/issues/12</a></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Nov 11, 2021 at 11:54 AM Jupiter Jones via Glass <<a href="mailto:glass@lists.gemtalksystems.com">glass@lists.gemtalksystems.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">(#( 1 2 3 4 ) groupedBy: [ :i | i even ]) keys<br>
<br>
This throws a DNU since PluggableSet has no accessors for hashBlock (or equalsBlock).<br>
<br>
Not sure how to contribute the simple fix - it’s in the Squeak-Collections-Unordered package.<br>
<br>
Cheers,<br>
<br>
Jupiter<br>
_______________________________________________<br>
Glass mailing list<br>
<a href="mailto:Glass@lists.gemtalksystems.com" target="_blank">Glass@lists.gemtalksystems.com</a><br>
<a href="https://lists.gemtalksystems.com/mailman/listinfo/glass" rel="noreferrer" target="_blank">https://lists.gemtalksystems.com/mailman/listinfo/glass</a><br>
</blockquote></div>