- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

by Ben Coman

First pass approximation... * https://www.microsoft.com/en-us/wdsi/filesubmission * https://answers.microsoft.com/en-us/protect/forum/all/windows-defender-win-… cheers -ben On Sat, Oct 7, 2017 at 12:54 AM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com > wrote: > Le 06/10/2017 Ã 18:32, Stephane Ducasse a Ã©crit : > > both now I do not see what we can do if a third party tools consider > > that we are a virus. > > > > > > Done. > > I don't know how to not be detected but Windows Defender is the default > anti-virus on windows. The majority of windows user use it now. If it is > possible to improve this, it would be cool. Maybe someone has experience > in that area? > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France > >

Oct. 6, 2017

Pulling Web XML data into spreadsheet

by Ben Coman

Unfortunately due to IT lock down I cannot use Pharo at work, but the first 1:30 of video [1] demonstrates a nice use case to aim for DataFrame + FastTable. Similar functionality in Pharo would make a compelling video, to the degree it may even be worthwhile including this out-of-the-box to make a great "first ten minutes" experience for newcomers, or at least a one-click install from the catalog (linked from the help file). What parts do we have for putting together something like this? [1] https://www.youtube.com/watch?v=6H7tBL97orE cheers -ben

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Cyril Ferlicot D.

Le 07/10/2017 Ã 00:34, Cyril Ferlicot D. a Ã©critÂ : > Le 06/10/2017 Ã 21:56, Mariano Martinez Peck a Ã©critÂ : >> >> Weird.... that package is not being loaded...Â sure I can explicitly >> load it ... but I think we must fix the baseline... but the baseline >> looks correct doesnt it ? I don't understand. >> >> Â > > I think I found the way to correct this problem. I will do a PR with the > fix. > https://github.com/pharo-vcs/iceberg/pull/478 >> >> -- >> Mariano >> http://marianopeck.wordpress.com > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Cyril Ferlicot D.

Le 06/10/2017 Ã 21:56, Mariano Martinez Peck a Ã©critÂ : > > Weird.... that package is not being loaded...Â sure I can explicitly > load it ... but I think we must fix the baseline... but the baseline > looks correct doesnt it ? I don't understand. > > Â I think I found the way to correct this problem. I will do a PR with the fix. > > -- > Mariano > http://marianopeck.wordpress.com -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 6, 2017

Re: [Pharo-dev] Reproducible VM Crash using UFFI

by HernÃ¡n Morales Durand

2017-10-06 2:39 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > >> On 6 Oct 2017, at 05:34, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: >> >> Hi Nicolas >> >> 2017-10-05 16:04 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>> >>> >>> 2017-10-05 15:42 GMT+02:00 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: >>>> >>>> I tried, now I get an exception "Use ExternalAddress instead!" >>>> >>>> I guess the message means Use ExternalAddres in the "out" parameter. >>>> But replacing byte with ExternalAddress also crashes the VM (crash.dmp >>>> attached). >>>> >>>> >>>> >>>> 2017-10-05 10:03 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> >>>>>> On 5 Oct 2017, at 14:55, HernÃ¡n Morales Durand >>>>>> <hernan.morales(a)gmail.com> wrote: >>>>>> >>>>>> Forgot to comment that Nacl worked in Pharo 5. >>>>> >>>>> yes but that was with NB and there are some minimum differences. >>>>> I do not have the library and I lack the time to try more, but seems to >>>>> me that here: >>>>> >>>>> apiCryptoHashSha512Output: outByteArray input: inByteArray inputLength: >>>>> inByteArrayLength >>>>> >>>>> ^ self >>>>> ffiCall: #(long crypto_hash_sha512_ref (byte * >>>>> outByteArray, byte * inByteArray, ulonglong * inByteArrayLength)) >>>>> module: 'libsodiumâ. >>>>> >>>>> >>>>> instead "byte * outByteArrayâ, you want "byte **outByteArrayâ >>>>> >>>>> can you try? >>>>> >>>>> Esteban >>>>> >>> >>> >>> Hmm no, internet reference says: >>> >>> extern int crypto_hash_sha512_ref(unsigned char *,const unsigned char >>> *,unsigned long long); >>> >>> The error is rather that you pass the address of length rather than the >>> length... >>> So you pass an erroneous length that may lead to a segfault... >>> >> >> Yes, that extra * was the error indeed. >> Thank you Nicolas. >> >> I do not know the VM internals, however I wonder if it is >> understandable to expect a VM crash for a typo like this? >> Maybe it is too difficult to catch in the VM side? >> >> Just asking, not criticizing anyone's work. > > Of course that is normal. This is C code, any error has the potential to crash your program. In C there are no runtime safe guards. > > There is a reason why we like/use Pharo. > However there are a couple of lightweight libraries which claim to provide exceptions for C: https://github.com/guillermocalvo/exceptions4c or this one https://github.com/psevon/exceptions-and-raii-in-c I wonder if something like that could be used in UFFI >> HernÃ¡n >> >>>>> >>>>> >>>>>> >>>>>> Cheers, >>>>>> >>>>>> HernÃ¡n >>>>>> >>>>>> 2017-10-05 3:23 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>>>> H Hernani, >>>>>>> >>>>>>> Most probably is a problem in the library and not UFFI, but I could >>>>>>> not know without a crash report. >>>>>>> >>>>>>> Esteban >>>>>>> >>>>>>>> On 5 Oct 2017, at 06:00, HernÃ¡n Morales Durand >>>>>>>> <hernan.morales(a)gmail.com> wrote: >>>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I ported Nacl (a libsodium wrapper) from the old FFI apicall: format >>>>>>>> to use the UFFI ffiCall:, but there should be something terribly >>>>>>>> wrong >>>>>>>> because is crashing the VM, in both Windows 8.1 and Linux. >>>>>>>> >>>>>>>> How to reproduce in Pharo 6.1 >>>>>>>> >>>>>>>> Metacello new >>>>>>>> smalltalkhubUser: 'tonyg' project: 'Crypto-Nacl'; >>>>>>>> configuration: 'Nacl'; >>>>>>>> version: #development; >>>>>>>> load. >>>>>>>> >>>>>>>> (Nacl hashString: 'The quick brown fox jumps over the lazy dog') hex >>>>>>>> >>>>>>>> This one does deserve a bug entry? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> >>>>>>>> HernÃ¡n > >

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Cyril Ferlicot D.

Le 06/10/2017 Ã 23:34, Tim Mackinnon a Ã©critÂ : > Gosh - It actually work quite well to be able to easily browse code > online in a more traditional format of seeing an entire class. Hopefully > this leads to us being able to share solutions to common language > agnostic problems. > > One small observation - I quickly grokâd the use of class { â¦. } (with > the curly braces) - but given that smalltalk methods often have lots of > Â [ ] (square braces in them), I was a bit surprised to see that method > declarations in tonal donât use { â¦ } (curly braces) to denote them, but > instead use [ ] - which feels slightly strange given the class > declaration above has. {}. > > Was it easier to parse this way, or is there some subtlety I missed? I > would have been tempted to use Â {} for classes and methods and [] for > the protocols as this more closely matches what other languages do - and > it might actually make it more easily readable for other programmers. > Given we have to learn this new format anyway - Iâd be prepared to give > a nod to what others doâ¦ > > Possibly this observation comes to late - and maybe there is compelling > reason to go the route we have gone - but maybe its worth a quick double > check as its an exciting development. > > Tim > > Hi, I cannot say for class, but the {} for methods metadata (as protocols) is because it is STON. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Tim Mackinnon

Gosh - It actually work quite well to be able to easily browse code online in a more traditional format of seeing an entire class. Hopefully this leads to us being able to share solutions to common language agnostic problems. One small observation - I quickly grokâd the use of class { â¦. } (with the curly braces) - but given that smalltalk methods often have lots of [ ] (square braces in them), I was a bit surprised to see that method declarations in tonal donât use { â¦ } (curly braces) to denote them, but instead use [ ] - which feels slightly strange given the class declaration above has. {}. Was it easier to parse this way, or is there some subtlety I missed? I would have been tempted to use {} for classes and methods and [] for the protocols as this more closely matches what other languages do - and it might actually make it more easily readable for other programmers. Given we have to learn this new format anyway - Iâd be prepared to give a nod to what others doâ¦ Possibly this observation comes to late - and maybe there is compelling reason to go the route we have gone - but maybe its worth a quick double check as its an exciting development. Tim > On 6 Oct 2017, at 18:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi all, > > I released Iceberg version 0.6. It includes a lot of small tweaks and fixes, but the most important inclusion is tonel file format which aims to replace file tree. > > What is Tonel? (https://github.com/pharo-vcs/tonel <https://github.com/pharo-vcs/tonel>) > Tonel is a file-per-class file format for monticello repositories. Itâs purpose is to reduce the amount of files touched each operation, make the IO faster an compact the repositories database. > It has also as an objective to offer an âeasy-to-readâ format, so people wanting to understand a chunk of code will recognise it easily. > For testing, I migrated several of my projects to Tonel and Iâve been using it, you can see some as examples: > > https://github.com/estebanlm/MUDClient <https://github.com/estebanlm/MUDClient> > https://github.com/estebanlm/pharo-tonel <https://github.com/estebanlm/pharo-tonel> (this was just an example and it has some minimal errors already fixed) > > We plan to migrate Pharo development to tonel to address some problems we have: > > - since it has to read/write a lot of files, IO operations are slow > - and even much more slow in Windows > - Windows also has a problem with longpaths. > > Iceberg 0.6 will be integrated to Pharo7 soon :) > To update Pharo 6.1, there are instructions in the readme: https://github.com/pharo-vcs/iceberg/blob/master/README.md <https://github.com/pharo-vcs/iceberg/blob/master/README.md> > now, if you wan to migrate your projects to Tonel (from FileTree), here is a script you can use: https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md <https://github.com/pharo-vcs/tonel/blob/master/MigrateFromFileTree.md> > > btw, tonel is independent of Iceberg and can be used with plain Monticello (but it is a metadaless format, history will reside on git, not on monticello). > > cheers, > Esteban

Oct. 6, 2017

Re: [Pharo-dev] [Pharo-users] ZnClient in Pharo 6.1 not working for Https on Windows

by Tim Mackinnon

Can we not contact the windows defender team and find a way to improve their detection? Presumably the signature they are finding is not good enough? Doesnât one of the Dolphin guys work at MS - or does someone in our network have a contact? Tim > On 6 Oct 2017, at 17:54, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > > Le 06/10/2017 Ã 18:32, Stephane Ducasse a Ã©crit : >> both now I do not see what we can do if a third party tools consider >> that we are a virus. >> >> > > Done. > > I don't know how to not be detected but Windows Defender is the default > anti-virus on windows. The majority of windows user use it now. If it is > possible to improve this, it would be cool. Maybe someone has experience > in that area? > > > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France >

Oct. 6, 2017

Re: [Pharo-dev] State of files.pharo.org

by Christophe Demarey

Thanks a lot for the data. Christophe > Le 6 oct. 2017 Ã 17:13, Gabriel Cotelli <g.cotelli(a)gmail.com> a Ã©crit : > > I've added my testing info in the shared notepad. The download of Pharo6.0-linux.zip took 11m 33s on a 30Mbps connection (I've looked while it was downloading and for the first half it was downloading at 40/50 Kbs), so I think it's representative of the slowness we get. As I previously said it's not always slow, sometimes I works fine. > > Regards, > Gabriel > > On Fri, Oct 6, 2017 at 11:07 AM, Christophe Demarey <christophe.demarey(a)inria.fr <mailto:christophe.demarey@inria.fr>> wrote: > Hello, > > I just finished the meeting with a guy from Inria datacenter. > From Inria, we do not see any problem with files.pharo.org <http://files.pharo.org/>. We do not have tools ready to simulate poor networks nor remote network sensors available :( > Thatâs why if some of you could help to collect some data to guess what is the problem, it would be great: If you can run the commands listed there: https://pad.inria.fr/p/IvdGLh650VN8lkoN <https://pad.inria.fr/p/IvdGLh650VN8lkoN> and also put the results at the bottom of the page, it would be very helpful. > In the same time, I created a project on github to run these command on travis CI: https://travis-ci.org/demarey/test-files-pharo-org <https://travis-ci.org/demarey/test-files-pharo-org>. > With all this data, I hope they can spot the problem quickly. > > Thanks, > Christophe >

Oct. 6, 2017

Re: [Pharo-dev] [ANN] Iceberg 0.6 released

by Mariano Martinez Peck

On Fri, Oct 6, 2017 at 4:46 PM, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: > Le 06/10/2017 Ã 21:38, Cyril Ferlicot D. a Ã©crit : > > Le 06/10/2017 Ã 21:34, Mariano Martinez Peck a Ã©crit : > >> I followed the instructions to update Iceberg from in a 6.1 image. When > >> I tried to clone the repository, I have the attached error (DNU on > >> #dangerTextColor). I workedaround that by doing: > >> > >> IceAbstractModel >> colorError > >> ^ Color red > >> > >> After I manage to make some progress and I finally was able to clone the > >> repository, I get a #free DNU (see attached too). > >> > > > > Hi, > > > > I introduced #dangerTextColor in Pharo 7 and used it on Iceberg. But I > > though I added it to #Iceberg-Pharo6 package. > > > > I'll check and do a hotfix when I'll have the time. > > > > Humâ¦ This is weird because I see those methods in the Iceberg-Pharo6 > package and I see this package in the baseline. > > Can you check if you have this package? > > Weird.... that package is not being loaded... sure I can explicitly load it ... but I think we must fix the baseline... but the baseline looks correct doesnt it ? I don't understand. -- Mariano http://marianopeck.wordpress.com

Oct. 6, 2017