gmane.comp.lang.smalltalk.pharo.devel

[Pharo-dev] About the Mailinglist debacle...

Marcus Denker — 2013-05-15T17:52:40

Hello,

So now that everything is working… sorry for the mess.

We should have left the gforge infrastructure the last time we had a multi-day problem,
not wait till we get it again.

I think this will be my new principle: second real problem -> I leave. No discussions.
We already saw with the jenkins story just how deadly bad infrastructure is.

So what happened was that last Tuesday, the lists (all lists of gforge) stopped delivering.
Why is not clear, seemingly it was not gforge itself but the upstream servers did
not deliver. Whatever.
What is clear is that it was completely unclear how long this would take, and that we
needed a solution after nearly a week of waiting.

So we decided to move the lists. Of course with the old lists down, this was harder than
normal (even involved parsing the html to get the subscribers…) but that is not important.

Now the problem its hat Mailman does not distinguish between people that unsubscribe,
and those turning off delivery. So there where just a lot of people listed with "nomail (U)",

What to do? It was clear that we can't just subscribe lots of people to a list that they *actively*
unsubscribed. So the only option was to skip those by
-> unsubscribing them from the old list
-> then get the list of subscribers
-> put that in the new list.

The only people that will see a bad effect are those using e.g nabble to read the list. But those
would see the new mails, too. The only problem they have is if the want to send. So not *that* of
a big deal.

It seems that we got quite some false positive subscribers anyway in the form of people who filtered
the mails and then with the new list the filter did not work and they suddenly saw mails of a long forgotten
list. We even had the case of people who where "nomail (U)", yet they did get mails delivered. How
that can possibly work, I have no clue *at all*.

What else is missing (and on my TODO since Sunday/Monday, sorry for not yet acting on it):

-> lists.pharo.org has an empty page and needs to point to the list of the lists inttead
-> the archive needs to be moved from the old jenkins.
-> the (incomplete) archive of the new lists is not working since I put it as public.

So… maybe it would have been better to just wait until gforge works again and then move… but
it was just far too long already and not clear when it would be working again.

Marcus

[regression reporter]regression occurred

2013-05-14T16:14:50

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=win/150/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

Re: Stick figure in Pharo smalltalk

Hilaire Fernandes — 2013-05-14T15:34:15

Le 08/05/2013 21:18, Sean P. DeNigris a écrit :


To do what?

sending #betSticky message, is it what you are looking for?

Hilaire

[regression reporter]regression occurred

2013-05-14T16:14:45

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=mac/150/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T16:12:20

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=linux/150/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T10:57:55

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=win/149/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T10:57:45

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=mac/149/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T10:55:29

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=linux/149/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

Re: XPath issue ?

Stéphane Ducasse — 2013-05-14T09:12:54

herve did you try pastell?

Stef

On May 8, 2013, at 11:23 PM, Herve Verjus <herve.verjus-184iAUnY30GJgFC65hhf1w< at >public.gmane.org> wrote:

[regression reporter]regression occurred

2013-05-14T08:52:55

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=win/148/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T08:52:20

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=mac/148/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T08:50:06

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=linux/148/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T07:00:12

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=mac/241/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T06:58:49

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=win/241/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T06:58:28

https://ci.inria.fr/pharo/job/Pharo-2.0-Tests/./Run=run%201,VM=vm,label=linux/241/

1 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect

[regression reporter]regression occurred

2013-05-14T06:54:48

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=win/147/

2 regressions found.
  Zinc.Tests.ZnClientTests.testRedirect
  Zinc.Zodiac.ZnHTTPSTests.testGetPharoVersion

[regression reporter]regression occurred

2013-05-14T06:54:20

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=mac/147/

2 regressions found.
  Tests.Release.ReleaseTest.testObsoleteBehaviors
  Zinc.Tests.ZnClientTests.testRedirect

Re: generalizing NeoCSV

Sven Van Caekenberghe — 2013-05-13T11:25:07

Hi Doru,

On 08 May 2013, at 15:25, Tudor Girba <tudor-49T7vwAQlU/CX7Tz6oRo6w< at >public.gmane.org> wrote:


That is great to hear, thanks !


That is an excellent suggestion, thanks. 

I made the change to both the writer and the reader (sadly #value:#value: does not exist on Symbol).

---
Name: ConfigurationOfNeoCSV-SvenVanCaekenberghe.10
Author: SvenVanCaekenberghe
Time: 13 May 2013, 1:19:12.655 pm
UUID: 98714491-3388-4a52-8720-43c8b27079d1
Ancestors: ConfigurationOfNeoCSV-SvenVanCaekenberghe.9

v8

Added support for blocks as accessors to the writer and the reader as suggested by Tudor Girba (Thx).
Added writer features #addEmptyField and #addConstantField:
---

Regards,

Sven

PS: I am sure you need JSON support as well, please also consider NeoJSON as well ;-) 


--
Sven Van Caekenberghe
Proudly supporting Pharo
http://pharo.org
http://association.pharo.org
http://consortium.pharo.org

Re: Understanding NBOpenGL

Igor Stasenko — 2013-05-13T22:51:03

Oh, and i should also mention, since depending on application you may want
to initialize context differently (different pixel format , different
number of buffers etc).. you will need to
override/rewrite context initialization part by youself.
So, the existing context initialization code is more for demo purposes
but not for serious use.
Another thing, that i don't see how i can provide sufficient "generic"
context creation part,
because there's a lot of flags and options which sometimes need fine
tuning (like
selecting most matching pixel format), which would make code too clever,
and therefore rigid.. and i know by myself that it is best to be left
for developer to decide
what he wants and how.

[regression reporter]regression occurred

2013-05-14T06:52:05

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=linux/147/

2 regressions found.
  Tests.Release.ReleaseTest.testObsoleteBehaviors
  Zinc.Tests.ZnClientTests.testRedirect

Re: Understanding NBOpenGL

Igor Stasenko — 2013-05-13T22:45:51

well, Athens provides convenient API for 2d vector graphics, which not
exists in opengl ..
One day i want to begin implementing opengl backend for Athens.


Neither my image has "NBCallFailureHandler".
Looks like you loaded wrong version of NBOpenGL.
How did you loaded NBOpenGL?
For 2.0/3.0 pharo image use
(ConfigurationOfNBOpenGL project version: '2.0') load

it should work out of the box.
(and you don't need to load NativeBoost, because it is already in image).


That what exactly NBOpenGL is.
Its contents is bindings to OpenGL library (over 3000 functions)
the rest is glue code , which mostly serves as an example how to
create and initialize
opengl context depending on platform you using.

The subcategory "NBOpenGL-Display" contains root classes with that glue code.
While NBOpenGL-Core is 99% is just plain opengl api.

If you don't like this glue, you can just avoid using it.. but throwing away
opengl core and making own.. makes little sense.
I actually encouraged people to write better glue code for
initializing context..
The main problem is that its highly platform specific.. and my
knowledge doesn't covers
deeply all 3 platforms.
I did windows and mac parts.. and linux made by Javier.