- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About your contributions: Improve Pharo right now, right there.

by Tim Mackinnon

Bump? The text on http://pharo.org/contribute-propose-fix is still wrong - can someone include the text I fixed up below? Also - do we want to make pharo.org the primary place for docs (and hence change the first paragraph to: #How to propose a bug fix or enhancement First check if your change has already been entered into Fogbugz, and consider watching the [overview video](https://www.youtube.com/watch?v=iFomI-7h4qQ) of the steps documented below. If we want to move away from the Fogbugz wiki, I will also simplify some of the text and point it back to pharo.org. Tim On 8 Aug 2014, at 08:40, Tim Mackinnon <tim(a)testit.works> wrote: > Ok - Iâve fixed my faux-pas and propose the following text (a slight rework of what is published now). Taking a hint from Martin there is a notehub link here (http://notehub.org/2014/8/8/how-to-propose-a-bug-fix-or-enhancement) - although Iâve noticed notehub handles sub-bullets a bit strangely. We might also want to do another slight change if we agree that Fogbugz should be secondary content (if so - adjust the first paragraph to something like: Check if your change has already been entered into Fogbugz, and consider watching the overview video of the steps documented below.) > > ââ > #How to propose a bug fix or enhancement > First check you meet the submission requirements and are familiar with the more detailed [contribution steps](https://pharo.fogbugz.com/default.asp?W68) (watch the [tutorial video](https://pharo.fogbugz.com/default.asp?pg=pgDownload&pgType=pgWikiAtt…, it's great!) > > ##Prerequisites > In order to propose a bug fix or enhancement for Pharo you need: > > - An account for the [Fogbugz Pharo Issue Tracker]( https://pharo.fogbugz.com) > - An account on [SmalltalkHub](http://smalltalkhub.com) with rights to the [Pharo Inbox]( http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox) > _Note, in the recent version of SmalltalkHub this is a public repository. If you encounter problems you can ask for commit rights on the [Pharo Developers mailinglist(http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.o… > > ##Procedure > To commit a change, you will follow these steps: > > - Take the latest [stable or development system](http://pharo.org/download), ideally using the latest virtual machine for your OS > - Ensure you have created [details of the issue in the Fogbugz issue tracker] (https://pharo.fogbugz.com) > - Create a code fix (ideally with a [unit test](http://pharo.gforge.inria.fr/PBE1/PBE1ch8.html) exercising the working code) > - Create a Monticello Slice (group of packages) for your changes: > - Open the Monticello Browser > - Open the Slice Maker by clicking the "Slice" button > - In Slice Maker enter the Fogbugz issue number and "grab" the issue summary > - Select all dirty packages affected by your fix > - Verify your changes (click the Changes button) > - Select the Pharo40 repository > - Select your Slice > - Press changes in the Monticello Browser and verify that your changes are correct > - Publish the Slice to the inbox: > - Select the whole Slice (not it's individual packages). > - Select the SmalltalkHub Pharo Inbox repository. > - Commit the Slice. > - Verify that your fix loads: > - Take a fresh image and load the Slice you just published > - Update the bug entry to mention that you submitted a Slice in the inbox > - Now sit back and feel good! You've helped influence a brighter future... > > You can also contribute to Pharo by proposing enhancements on the mailing list and/or by submitting a Fogbugz issue. Note that all code submitted to the [Pharo repositories](http://smalltalkhub.com/#!/~Pharo) is licensed under the [MIT license]http://opensource.org/licenses/MIT) Do not forget to sign the [license agreement](http://files.pharo.org/media/PharoSoftwareDistributionAgreement.…. > > > On 8 Aug 2014, at 07:16, Tim Mackinnon <tim(a)testit.works> wrote: > >> Stef - I've confused you with my suggestion. Where I wrote "use link" after the text in [] - I meant put that hyperlink for the [text]. >> >> Sorry, I was writing my reply in a text editor and was doing a sort of pseudo markdown syntax. >> >> Looking at where this is going - maybe we should instead make the Pharo.org site the main source of info and not Fogbugz? We have a duplication problem - and when things change we end up with conflicting instructions as we forget to update the other copies. Essentially we need to refactor the docs. >> >> Is Pharo.org easily editable by others (is this the Pillar bit?). If it was then I would say let's edit the Fogbugz pages - simplify them and point them back to the more detailed Pharo.org pages. >> >> For now, I will find a laptop and send some cleaned up text. >> >> Tim >> >> Sent from my iPhone >> >> On 7 Aug 2014, at 10:45 pm, "stepharo [via Smalltalk]" <[hidden email]> wrote: >> >>> in fact I just did a merge with the version of Tim and it is looking great. >>> On 7/8/14 22:32, stepharo wrote: >>> >>> > Thanks martin I will have a look tomorrow. >>> > >>> > Stef >>> > >>> > On 7/8/14 22:11, MartinW wrote: >>> >> Could you extend http://pharo.org/contribute-propose-fix a bit? And >>> >> add a >>> >> screenshot of Slice Maker (I attach one). The following text would have >>> >> helped me (I paste the markdown. I also posted it on NoteHub for a >>> >> better >>> >> reading experience >>> >> http://www.notehub.org/2014/8/7/how-to-propose-a-bug-fix) >>> >> >>> >> #How to propose a bug fix: >>> >> ##Prerequesites: >>> >> In order to propose a bug fix or enhancement for Pharo you need: >>> >> >>> >> - an account at the [Pharo Issue Tracker on >>> >> Fogbugz](https://pharo.fogbugz.com), >>> >> - a [SmalltalkHub](http://smalltalkhub.com) account and >>> >> - the commit right for the [Pharo Inbox on >>> >> SmalltalkHub](http://smalltalkhub.com/#!/~Pharo/Pharo40Inbox) (Ask on >>> >> the >>> >> [Pharo Developers >>> >> mailinglist](http://lists.pharo.org/mailman/listinfo/pharo-dev_lists.pharo.… >>> >> >>> >> for the commit right). >>> >> >>> >> ##Procedure: >>> >> - Take the latest stable or latest development system, ideally using the >>> >> latest virtual machine. >>> >> - Do a fix for a given bug, or a new bug you entered to the issue >>> >> tracker. >>> >> - Create a slice (group of packages): >>> >> - Open the Monticello Browser. >>> >> - Open the Slice Maker by clicking the **+Slice** button. >>> >> - In Slice Maker enter the Fogbugz issue number and **grab** the >>> >> issue >>> >> summary. >>> >> - Select all dirty packages affected by your bug fix. >>> >> - Publish the slice to the inbox: >>> >> - Select the whole slice (not it's individual packages). >>> >> - Select the SmalltalkHub Pharo Inbox repository. >>> >> - Commit your slice. >>> >> - Verify that your fix loads: take a fresh image and load the slice you >>> >> published. >>> >> - Update the bug entry to mention that you submitted a slice in the >>> >> inbox. >>> >> >>> >> You can also contribute to Pharo by proposing enhancements following the >>> >> same process. Note that all code submitted to the Pharo repositories is >>> >> licensed under the MIT license. Do not forget to sign the license >>> >> agreement. >>> >> >>> >> <http://forum.world.st/file/n4772388/SliceMaker.png> >>> >> >>> >> >>> >> >>> >> -- >>> >> View this message in context: >>> >> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… >>> >> Sent from the Pharo Smalltalk Developers mailing list archive at >>> >> Nabble.com. >>> >> >>> >> >>> > >>> > >>> > >>> >>> >>> >>> If you reply to this email, your message will be added to the discussion below: >>> http://forum.world.st/About-your-contributions-Improve-Pharo-right-now-righ… >>> To unsubscribe from About your contributions: Improve Pharo right now, right there., click here. >>> NAML >> >> View this message in context: Re: About your contributions: Improve Pharo right now, right there. >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 11, 2014

Re: [Pharo-dev] Right to left language

by Henrik Johansen

On 11 Aug 2014, at 5:14 , Hilaire <hilaire(a)drgeo.eu> wrote: > Yes strange, probably my test image. Or you could just be on a different platform, the Clipboard VM source for Linux/Windows isâ¦ something else entirely. On OSX, it asks for the text in UTF8 specifically; ExternalClipboard >> clipboardText ... bytes := self primReadClipboardData: clipboard format: 'public.utf8-plain-text'. (whatâs the valid formats other than that you ask? Darned if I know, probably need to read the VM sources) On Unix/Windows, it works differently, you donât use a primitive where you specifically set the encoding you want for clipboard text entering the image. My memory is a bit hazy, but IIRC, the Windows primitive code will also return utf8 consistently, so the code in Clipboard >> clipboardText will work correctly. While on *nix, the bytes returned will be converted either to the current localeâs default encoding (which is why I asked for it), or the one specified by the vmâs -locale parameter when it was launched, I canât quite remember the details. So if youâre on Linux it *might* help if you start the VM with an -encoding UTF8 parameter set, or use a system locale which returns #utf8. > It looks correctly rendered in reverse order. > Btw, do we have tool to help to pickup the right font given the pharo locale? > > Thanks > > Hilaire Itâs not rendered in reverse order, when one does the same as Sven did with example text #2 (Â«Ready to continue?Â»), the String will render in Pharo with the question mark at the end. Cheers, Henry

Aug. 11, 2014

Re: [Pharo-dev] Right to left language

by Hilaire

Yes strange, probably my test image. It looks correctly rendered in reverse order. Btw, do we have tool to help to pickup the right font given the pharo locale? Thanks Hilaire Le 11/08/2014 22:50, Sven Van Caekenberghe a Ã©crit : > I took the characters that you pasted in the issue you just made, and on > Mac OS X, with a proper a Unicode font set, Arial Unicode MS, I get this: > > > Is that correct ? > > There will be a left-to-right issue, but it is not a UTF-8 / Unicode > problem I think. > > On 11 Aug 2014, at 16:39, Hilaire <hilaire(a)drgeo.eu > <mailto:hilaire@drgeo.eu>> wrote: > >> Le 11/08/2014 18:23, Henrik Johansen a Ã©crit : >>> Although Pharo doesnât support RTL renderin, thatâs not a rendering >>> error though, but a mismatch between the encoding of the text in >>> clipboard, and that expected by the image. >>> (R2L text isnât*stored* RTL, so that should have no impact). >>> >>> Could it be youâre using a non-Unicode locale? >>> Any chance you could find what OS/locale settings/source text this >>> happens for? >> >> >> No I just copy and paste from the iStoa web translation tool some >> hebrew messages[1] in Pharo. >> Then I try to copy paste by the intermediate of a text editor with >> UTF-8 encoding same error (I noted that when pasting in the text >> editor, the message was right aligned). >> When I try to copy and paste a single character same error. >> So we may have an issue in the UTF-8 converter. >> >> >> >> Hilaire >> >> [1] >> https://translations.launchpad.net/istoa/trunk/+pots/istoa/he/+translate?st… >> >> >> -- >> Dr. Geo - http://drgeo.eu >> iStoa - http://istao.drgeo.eu >> >> > -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Aug. 11, 2014

[pharo-project/pharo-core] 7f2a5e: 40163

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 7f2a5ebaeda48a32c60b3a03c912c8c1882ebbb0 https://github.com/pharo-project/pharo-core/commit/7f2a5ebaeda48a32c60b3a03… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-11 (Mon, 11 Aug 2014) Changed paths: M Keymapping-Core.package/extension/SystemWindow/class/buildShortcutsOn_.st R Keymapping-KeyCombinations.package/KMAltModifier.class/instance/printing/symbol.st R Keymapping-KeyCombinations.package/KMCtrlModifier.class/instance/printing/symbol.st R Keymapping-KeyCombinations.package/KMMetaModifier.class/instance/printing/symbol.st A Keymapping-KeyCombinations.package/KMModifier.class/instance/printing/symbol.st A Keymapping-KeyCombinations.package/KMNoModifier.class/README.md A Keymapping-KeyCombinations.package/KMNoModifier.class/definition.st A Keymapping-KeyCombinations.package/KMNoModifier.class/instance/initialization/initialize.st R Keymapping-KeyCombinations.package/KMShiftModifier.class/instance/printing/symbol.st M Keymapping-KeyCombinations.package/KMSingleKeyCombination.class/instance/accessing/modifier.st A Keymapping-KeyCombinations.package/KMSingleKeyCombination.class/instance/printing/prettyPrintOn_.st M Manifest-CriticBrowser.package/SingleCodeCriticResultList.class/instance/initialization/initializeShortcuts.st M Morphic-Base.package/TextMorph.class/class/shortcuts/buildTextEditorKeymapsOn_.st A Nautilus.package/extension/AbstractGroup/instance/categoryName.st M NautilusRefactoring.package/ChangesBrowser.class/class/shortcuts/buildShortcutsOn_.st M NautilusRefactoring.package/ChangesBrowser.class/instance/initialization/initializeWidgets.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script163.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40163.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Inspector.package/AbstractEyeElement.class/instance/menu/browseSubMenu_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/shortcuts/registerChangeSetShortcuts_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/shortcuts/registerClassShortcuts_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/shortcuts/registerMethodShortcuts_.st M Spec-Tools.package/MessageBrowser.class/instance/initialization/registerListShortcutsFor_.st M Text-Edition.package/SmalltalkEditor.class/class/shortcuts/buildSmalltalkEditorKeymappingsOn_.st M Tool-Base.package/AbstractTool.class/instance/class/addClassIn_.st A Tool-Base.package/PharoShortcuts.class/README.md A Tool-Base.package/PharoShortcuts.class/class/accessing/current.st A Tool-Base.package/PharoShortcuts.class/definition.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/acceptShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseImplementorsShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseReferencesShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseSendersShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/browseVersionsShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/cancelShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/closeWindowShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/doItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/formatCodeShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/inspectItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/printItShortcut.st A Tool-Base.package/PharoShortcuts.class/instance/keymaps/removeShortcut.st R Tool-Base.package/ToolShortcuts.class/README.md R Tool-Base.package/ToolShortcuts.class/class/initializing/initialize.st R Tool-Base.package/ToolShortcuts.class/class/testing/isGlobalCategory.st R Tool-Base.package/ToolShortcuts.class/definition.st R Tool-Base.package/ToolShortcuts.class/instance/keymaps/openMonticelloPackageBrowser.st R Tool-Base.package/ToolShortcuts.class/instance/keymaps/openSettings.st R Tool-Base.package/ToolShortcuts.class/instance/keymaps/openSystemBrowser.st R Tool-Base.package/ToolShortcuts.class/instance/keymaps/openTranscript.st R Tool-Base.package/ToolShortcuts.class/instance/keymaps/openUnitTestRunner.st R Tool-Base.package/ToolShortcuts.class/instance/keymaps/openWorkspace.st R Tool-Base.package/ToolShortcuts.class/instance/keymaps/saveImage.st A Tool-Base.package/ToolShortcutsCategory.class/README.md A Tool-Base.package/ToolShortcutsCategory.class/class/testing/isGlobalCategory.st A Tool-Base.package/ToolShortcutsCategory.class/definition.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openMonticelloPackageBrowser.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openSettings.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openSystemBrowser.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openTranscript.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openUnitTestRunner.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/openWorkspace.st A Tool-Base.package/ToolShortcutsCategory.class/instance/keymaps/saveImage.st R Tool-Spotlight.package/SpotlightShortcuts.class/README.md R Tool-Spotlight.package/SpotlightShortcuts.class/class/testing/isGlobalCategory.st R Tool-Spotlight.package/SpotlightShortcuts.class/definition.st R Tool-Spotlight.package/SpotlightShortcuts.class/instance/keymaps/keymapToggle.st A Tool-Spotlight.package/SpotlightShortcutsCategory.class/README.md A Tool-Spotlight.package/SpotlightShortcutsCategory.class/class/testing/isGlobalCategory.st A Tool-Spotlight.package/SpotlightShortcutsCategory.class/definition.st A Tool-Spotlight.package/SpotlightShortcutsCategory.class/instance/keymaps/keymapToggle.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/initialization/initializeWidgets.st M Versionner-Spec-Browser.package/VersionnerSpecBrowser.class/instance/initialization/initializeWidgets.st Log Message: ----------- 40163 13821 Concentrate tools shortcuts in a single class https://pharo.fogbugz.com/f/cases/13821 13097 Keymapping: Cmd-n Cmd-c gives error message https://pharo.fogbugz.com/f/cases/13097 13027 KeyCombination pretty printing is broken https://pharo.fogbugz.com/f/cases/13027 http://files.pharo.org/image/40/40163.zip

Aug. 11, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40163 Home: https://github.com/pharo-project/pharo-core

Aug. 11, 2014

Re: [Pharo-dev] Right to left language

by Sven Van Caekenberghe

I took the characters that you pasted in the issue you just made, and on Mac OS X, with a proper a Unicode font set, Arial Unicode MS, I get this: Is that correct ? There will be a left-to-right issue, but it is not a UTF-8 / Unicode problem I think. On 11 Aug 2014, at 16:39, Hilaire <hilaire(a)drgeo.eu> wrote: > Le 11/08/2014 18:23, Henrik Johansen a Ã©crit : >> Although Pharo doesnât support RTL renderin, thatâs not a rendering error though, but a mismatch between the encoding of the text in clipboard, and that expected by the image. >> (R2L text isnât*stored* RTL, so that should have no impact). >> >> Could it be youâre using a non-Unicode locale? >> Any chance you could find what OS/locale settings/source text this happens for? > > > No I just copy and paste from the iStoa web translation tool some hebrew messages[1] in Pharo. > Then I try to copy paste by the intermediate of a text editor with UTF-8 encoding same error (I noted that when pasting in the text editor, the message was right aligned). > When I try to copy and paste a single character same error. > So we may have an issue in the UTF-8 converter. > > > > Hilaire > > [1] https://translations.launchpad.net/istoa/trunk/+pots/istoa/he/+translate?st… > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istao.drgeo.eu > >

Aug. 11, 2014

Re: [Pharo-dev] Right to left language

by Hilaire

Le 11/08/2014 18:23, Henrik Johansen a Ã©crit : > Although Pharo doesnât support RTL renderin, thatâs not a rendering error though, but a mismatch between the encoding of the text in clipboard, and that expected by the image. > (R2L text isnât*stored* RTL, so that should have no impact). > > Could it be youâre using a non-Unicode locale? > Any chance you could find what OS/locale settings/source text this happens for? No I just copy and paste from the iStoa web translation tool some hebrew messages[1] in Pharo. Then I try to copy paste by the intermediate of a text editor with UTF-8 encoding same error (I noted that when pasting in the text editor, the message was right aligned). When I try to copy and paste a single character same error. So we may have an issue in the UTF-8 converter. Hilaire [1] https://translations.launchpad.net/istoa/trunk/+pots/istoa/he/+translate?st… -- Dr. Geo - http://drgeo.eu iStoa - http://istao.drgeo.eu

Aug. 11, 2014

Re: [Pharo-dev] Xtreams build failing on 4.0

by Sven Van Caekenberghe

On 11 Aug 2014, at 15:21, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > I suspect ContextPart>>#reading, that is a class extension from Xtreams in ContextPart to be the reason. > > It should now be an extension of Context and not ContextPart. Yes, that is something we should fix, I saw that while loading the code in a fresh 4.0 However, that still does not explain why the failing tests pass on my Mac. Weird. > 2014-08-11 14:35 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > It seems that the Xtreams build has been failing since june 30th for 4.0 and not 3.0: > > https://ci.inria.fr/pharo-contribution/job/Xtreams/ > > From the changes to 4.0 around that period I can't immediately see something obvious: > > https://github.com/pharo-project/pharo-core/commits/4.0?page=4 > > I just tried loading Xtreams in on my machine and all tests succeed. > > All errors on Jenkins seem to be related to primitives not being found in libCrypto: > > Error Message > > External module not found > > Stacktrace > > XTLibCryptoHash(Object)>>error: > XTLibCryptoHash(Object)>>externalCallFailed > XTLibCryptoHash>>EVP_MD_CTX_init: > XTLibCryptoHash>>initialize > XTHash class>>new > XTHashTest>>testMD5 > XTHashTest(TestCase)>>performTest > > So, is it possible there was a change in the VM ? > > The Xtreams source code itself has not been changed for months. > > Sven > > >

Aug. 11, 2014

Re: [Pharo-dev] Xtreams build failing on 4.0

by ClÃ©ment Bera

I suspect ContextPart>>#reading, that is a class extension from Xtreams in ContextPart to be the reason. It should now be an extension of Context and not ContextPart. 2014-08-11 14:35 GMT+02:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > It seems that the Xtreams build has been failing since june 30th for 4.0 > and not 3.0: > > https://ci.inria.fr/pharo-contribution/job/Xtreams/ > > From the changes to 4.0 around that period I can't immediately see > something obvious: > > https://github.com/pharo-project/pharo-core/commits/4.0?page=4 > > I just tried loading Xtreams in on my machine and all tests succeed. > > All errors on Jenkins seem to be related to primitives not being found in > libCrypto: > > Error Message > > External module not found > > Stacktrace > > XTLibCryptoHash(Object)>>error: > XTLibCryptoHash(Object)>>externalCallFailed > XTLibCryptoHash>>EVP_MD_CTX_init: > XTLibCryptoHash>>initialize > XTHash class>>new > XTHashTest>>testMD5 > XTHashTest(TestCase)>>performTest > > So, is it possible there was a change in the VM ? > > The Xtreams source code itself has not been changed for months. > > Sven > > >

Aug. 11, 2014

Xtreams build failing on 4.0

by Sven Van Caekenberghe

It seems that the Xtreams build has been failing since june 30th for 4.0 and not 3.0: https://ci.inria.fr/pharo-contribution/job/Xtreams/ >From the changes to 4.0 around that period I can't immediately see something obvious: https://github.com/pharo-project/pharo-core/commits/4.0?page=4 I just tried loading Xtreams in on my machine and all tests succeed. All errors on Jenkins seem to be related to primitives not being found in libCrypto: Error Message External module not found Stacktrace XTLibCryptoHash(Object)>>error: XTLibCryptoHash(Object)>>externalCallFailed XTLibCryptoHash>>EVP_MD_CTX_init: XTLibCryptoHash>>initialize XTHash class>>new XTHashTest>>testMD5 XTHashTest(TestCase)>>performTest So, is it possible there was a change in the VM ? The Xtreams source code itself has not been changed for months. Sven

Aug. 11, 2014