Re: [Pharo-dev] Zinc question

[Santiago Bragagnolo]

thanks a lot for the fast response!  I will do a workaround for the moment
:)


On Thu, 17 Nov 2016 at 16:05 Sven Van Caekenberghe  wrote:

Santiago,

Hmm, that is actually a Zodiac and SSL Plugin problem.

It seems the certificate from that site is based on Elliptic Curve crypto
that might not be supported by the plugin.

I am afraid I cannot help you much further. Hopefully someone else has more
experience here.

Sven

> On 17 Nov 2016, at 15:54, Santiago Bragagnolo <
santiagobragagn...@gmail.com> wrote:
>
> Hi! Im trying to do a GET on this address:
>
>
https://etherchain.org/api/account/0xbf35faa9c265baf50c9cff8c389c363b05753275/source
>
> Is a rest API over https.
>
> For some reason, in linux im having "Connection closed while waiting for
data".
>
> in Mac "SSL exception connection failed code -5"
>
> Does any have any clue about how to make this work :)?
>
> Thanks!
>
> Santiago.
>
>
>
>
>
>
>
>
>

Re: [Pharo-dev] Zinc question

[Sven Van Caekenberghe]

Santiago,

Hmm, that is actually a Zodiac and SSL Plugin problem. 

It seems the certificate from that site is based on Elliptic Curve crypto that 
might not be supported by the plugin. 

I am afraid I cannot help you much further. Hopefully someone else has more 
experience here.

Sven

> On 17 Nov 2016, at 15:54, Santiago Bragagnolo  
> wrote:
> 
> Hi! Im trying to do a GET on this address: 
> 
> https://etherchain.org/api/account/0xbf35faa9c265baf50c9cff8c389c363b05753275/source
> 
> Is a rest API over https. 
> 
> For some reason, in linux im having "Connection closed while waiting for 
> data".
> 
> in Mac "SSL exception connection failed code -5"
> 
> Does any have any clue about how to make this work :)? 
> 
> Thanks! 
> 
> Santiago. 
> 
> 
> 
> 
> 
> 
> 
> 
> 

[Pharo-dev] Zinc question

[Santiago Bragagnolo]

Hi! Im trying to do a GET on this address:

https://etherchain.org/api/account/0xbf35faa9c265baf50c9cff8c389c363b05753275/source

Is a rest API over https.

For some reason, in linux im having "Connection closed while waiting for
data".

in Mac "SSL exception connection failed code -5"

Does any have any clue about how to make this work :)?

Thanks!

Santiago.

[Pharo-dev] [pharo-project/pharo-core] eec705: 60295

[GitHub]

  Branch: refs/heads/6.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: eec7051ba6c585770dbf8da6a793da4ed2cb33d7
  
https://github.com/pharo-project/pharo-core/commit/eec7051ba6c585770dbf8da6a793da4ed2cb33d7
  Author: Jenkins Build Server 
  Date:   2016-11-17 (Thu, 17 Nov 2016)

  Changed paths:
M AST-Core.package/RBMethodNode.class/instance/testing/defines_.st
A AST-Core.package/RBPragmaNode.class/instance/testing/defines_.st
A 
AST-Tests-Core.package/RBParserTest.class/instance/tests/testQueryingPrimitiveErrorVar.st
M Kernel.package/Context.class/instance/controlling/send_to_with_super_.st
M RPackage-Core.package/RPackage.class/instance/class tags/addClassTag_.st
M 
RPackage-Core.package/RPackageTag.class/instance/accessing/removeFromPackage.st
M RPackage-Core.package/RPackageTag.class/instance/accessing/renameTo_.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
scripts/script60294.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
scripts/script60295.st
R ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
updates/update60294.st
A ScriptLoader60.package/ScriptLoader.class/instance/pharo - 
updates/update60295.st
M 
ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
M Spec-Core.package/FTArrayIndexColumn.class/README.md
A 
Spec-Core.package/FTArrayIndexColumn.class/class/accessing/undefinedColumnWidth.st
A Spec-Core.package/FTArrayIndexColumn.class/class/instance creation/id_.st
M Spec-Core.package/FTArrayIndexColumn.class/definition.st
A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/id.st
A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/id_.st
A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/width.st
A 
Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/widthOrUndefined.st
A Spec-Core.package/FTArrayIndexColumn.class/instance/accessing/width_.st
A 
Spec-Core.package/FTArrayIndexColumn.class/instance/layout/acquireWidth_.st
A System-Announcements.package/ClassTagAdded.class/README.md
A System-Announcements.package/ClassTagAdded.class/definition.st
A System-Announcements.package/ClassTagAnnouncement.class/README.md
A System-Announcements.package/ClassTagAnnouncement.class/class/instance 
creation/in_tag_.st
A System-Announcements.package/ClassTagAnnouncement.class/definition.st
A 
System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/package.st
A 
System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/package_.st
A 
System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/packagesAffected.st
A 
System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/tag.st
A 
System-Announcements.package/ClassTagAnnouncement.class/instance/accessing/tag_.st
A System-Announcements.package/ClassTagRemoved.class/README.md
A System-Announcements.package/ClassTagRemoved.class/definition.st
A System-Announcements.package/ClassTagRenamed.class/README.md
A System-Announcements.package/ClassTagRenamed.class/class/instance 
creation/in_tag_to_.st
A System-Announcements.package/ClassTagRenamed.class/definition.st
A 
System-Announcements.package/ClassTagRenamed.class/instance/accessing/newName.st
A 
System-Announcements.package/ClassTagRenamed.class/instance/accessing/newName_.st
A 
System-Announcements.package/SystemAnnouncer.class/instance/triggering/classTagAdded_inPackage_.st
A 
System-Announcements.package/SystemAnnouncer.class/instance/triggering/classTagRemoved_fromPackage_.st
A 
System-Announcements.package/SystemAnnouncer.class/instance/triggering/classTagRenamed_inPackage_to_.st

  Log Message:
  ---
  60295
19335 Syntax highlighting do not work on methods with primitives that uses "ec"
https://pharo.fogbugz.com/f/cases/19335

19340 Can not step over methods with meta links
https://pharo.fogbugz.com/f/cases/19340

19343 Spec is now dependent on FastTable
https://pharo.fogbugz.com/f/cases/19343

19351 ClassTagAnnouncement is needed to describe operations with class tags
https://pharo.fogbugz.com/f/cases/19351

http://files.pharo.org/image/60/60295.zip

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

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

Re: [Pharo-dev] [Moose-dev] Re: Segfault on Moose 6.1 jobs

[Esteban Lorenzano]

> On 17 Nov 2016, at 10:18, Blondeau Vincent  
> wrote:
> 
> Thanks Eliot,
>  
> However, I use this URL to get Pharo vm: http://get.pharo.org/60+vmLatest 
> . The zip file (here: 
> http://files.pharo.org/get-files/60/ ) 
> was created on October 12, 2016.
>  
> Did you mean that I do not get the latest one for Pharo60?

yes and no.
this is the latest VM with the old process, before the merge with 
opensmalltalk-vm. 
I’m finishing the merge process (it was painful), but I still didn’t integrate 
it into the pharo building process. 

For the moment, you can download “real” latest VMs from here: 
https://bintray.com/estebanlm/pharo-vm/build/201611142324#files 


Esteban

>  
> Vincent
>  
> De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch 
> ] De la part de Eliot Miranda
> Envoyé : mercredi 16 novembre 2016 18:41
> À : Pharo Development List
> Cc : Moose-related development
> Objet : [Moose-dev] Re: [Pharo-dev] Segfault on Moose 6.1 jobs
>  
> Hi Vincent,
>  
> On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent 
> > 
> wrote:
> Hello,
>  
> I would like to report some random segfaults happing during the build of the 
> Moose 6.1 image (based on Pharo 6).
> Please find attached the latest failing stack trace.
>  
> Here are the 2 jobs that fails:
> https://ci.inria.fr/moose/job/moose-6.1/345/console 
> 
> https://ci.inria.fr/moose/job/moose-6.1/347/console 
> 
>  
> It seems that they are not failing for the same reason.
>  
> Maybe because the job is not using the latest VM? :
>  
> pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production 
> Spur ITHB VM]
> Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 
> 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
>  
> Yes, this is very old.  I suggest you update to something around VMMaker 1776 
> at the start of November.  Right now there is a little instability from the 
> LLP64 work for Win64, otherwise I would recommend the tip.
>  
> With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 
> uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
> Revision: https://github.com/pharo-project/pharo-vm.git 
>  Commit: 
> 9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: 
> GitHub > Jenkins build #594
> Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 
> 16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
> plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: 
> /builds/workspace/moose-6.1/pharo-vm/]
>  
> Thanks in advance
>  
> Cheers,
> Vincent
>  
> 
> !!!*
> "Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
> exclusif de ses destinataires. Il peut également être protégé par le secret 
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne 
> pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra 
> être recherchée quant au contenu de ce message. Bien que les meilleurs 
> efforts soient faits pour maintenir cette transmission exempte de tout virus, 
> l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
> saurait être recherchée pour tout dommage résultant d'un virus transmis.
> 
> This e-mail and the documents attached are confidential and intended solely 
> for the addressee; it may also be privileged. If you receive this e-mail in 
> error, please notify the sender immediately and destroy it. As its integrity 
> cannot be secured on the Internet, the Worldline liability cannot be 
> triggered for the message content. Although the sender endeavours to maintain 
> a computer virus-free network, the sender does not warrant that this 
> transmission is virus-free and will not be liable for any damages resulting 
> from any virus transmitted.!!!"
> 
> 
>  
> -- 
> _,,,^..^,,,_
> best, Eliot
> 
> !!!*
> "Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
> exclusif de ses destinataires. Il peut également être protégé par le secret 
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne 
> pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra 
> être recherchée quant au contenu de ce message. 

Re: [Pharo-dev] [Moose-dev] Re: Segfault on Moose 6.1 jobs

[Blondeau Vincent]

Thanks Eliot,

However, I use this URL to get Pharo vm: http://get.pharo.org/60+vmLatest. The 
zip file (here: http://files.pharo.org/get-files/60/) was created on October 
12, 2016.

Did you mean that I do not get the latest one for Pharo60?

Vincent

De : Moose-dev [mailto:moose-dev-boun...@list.inf.unibe.ch] De la part de Eliot 
Miranda
Envoyé : mercredi 16 novembre 2016 18:41
À : Pharo Development List
Cc : Moose-related development
Objet : [Moose-dev] Re: [Pharo-dev] Segfault on Moose 6.1 jobs

Hi Vincent,

On Wed, Nov 16, 2016 at 2:56 AM, Blondeau Vincent 
> wrote:
Hello,

I would like to report some random segfaults happing during the build of the 
Moose 6.1 image (based on Pharo 6).
Please find attached the latest failing stack trace.

Here are the 2 jobs that fails:
https://ci.inria.fr/moose/job/moose-6.1/345/console
https://ci.inria.fr/moose/job/moose-6.1/347/console

It seems that they are not failing for the same reason.

Maybe because the job is not using the latest VM? :

pharo VM version: 5.0 #1 Tue Jun 21 12:37:33 CEST 2016 gcc 4.6.3 [Production 
Spur ITHB VM]
Built from: CoInterpreter VMMaker.oscog-HolgerHansPeterFreyther.1880 uuid: 
16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016

Yes, this is very old.  I suggest you update to something around VMMaker 1776 
at the start of November.  Right now there is a little instability from the 
LLP64 work for Win64, otherwise I would recommend the tip.

With: StackToRegisterMappingCogit VMMaker.oscog-HolgerHansPeterFreyther.1880 
uuid: 16138eb3-2390-40f5-a6c8-15f0494936f8 Jun 21 2016
Revision: https://github.com/pharo-project/pharo-vm.git Commit: 
9638b0190a9fc01479bfb752becd96edfd253c8c Date: 2016-06-21 12:29:26 +0200 By: 
GitHub > Jenkins build #594
Build host: Linux pharo-linux 3.2.0-31-generic-pae #50-Ubuntu SMP Fri Sep 7 
16:39:45 UTC 2012 i686 i686 i386 GNU/Linux
plugin path: /builds/workspace/moose-6.1/pharo-vm/ [default: 
/builds/workspace/moose-6.1/pharo-vm/]

Thanks in advance

Cheers,
Vincent


!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"



--
_,,,^..^,,,_
best, Eliot

!!!*
"Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.!!!"