Re: [Sugar-devel] Frequent buildbot check failures in sugar-web

[Code Raguet]

Roger has told me recently (today) that this also happen in his local env...
Some datastore related test randomly fails. Is not always the same test,
but it is one of datastore's and them always fail due to timeouts.

Perhaps it's just matter of performance and we can workaround it with
higher timeouts...

Nice work logging gwebsockets, Daniel.



On Wed, Dec 11, 2013 at 10:18 PM, Daniel Narvaez wrote:

> As an update, we are now back to the intermittent datastore tests failure
> which we have been getting for a while.
>
>
> http://buildbot.sugarlabs.org/builders/full-master/builds/17/steps/shell_3/logs/modules
>
> [1A [2KChrome 25.0 (Linux): Executed 16 of 34
>  [1A [2KChrome 25.0 (Linux) datastore should be able to set object metadata 
> FAILED
>   timeout: timed out after 5000 msec waiting for metadata should be set
> Chrome 25.0 (Linux): Executed 17 of 34 (1 FAILED)
>
> And in the shell logs we can see the corresponding 5 seconds delay in the
> websockets communication
>
> 1386782408.775987 DEBUG gwebsockets: Text message 
> {"method":"datastore.set_metadata","id":3,"params":["56ab3f11-4654-457d-97ee-b8b1ec092e3b",{"title":"hello"}],"jsonrpc":"2.0"}
> 1386782409.802124 DEBUG gwebsockets: Got data, length 114
>
> That's not enough to say if python is never sending the message or if 
> javascript is never receiving/handling it. So I make gwebsockets log sent 
> messages to... when we get the next failure we can check if that helps 
> figuring out what is going on.
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [ASLO] Release Administrar vistas principales-1

[Sugar Labs Activities]

Activity Homepage:
http://activities.sugarlabs.org/addon/4722

Sugar Platform:
0.100 - 0.100

Download Now:
http://activities.sugarlabs.org/downloads/file/28838/manage_homeviews-1.xo

Release notes:
First version 0 bugs known


Sugar Labs Activities
http://activities.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Frequent buildbot check failures in sugar-web

[Daniel Narvaez]

As an update, we are now back to the intermittent datastore tests failure
which we have been getting for a while.

http://buildbot.sugarlabs.org/builders/full-master/builds/17/steps/shell_3/logs/modules

[1AChrome 25.0 (Linux): Executed 16 of 34
Chrome 25.0 (Linux) datastore should be able to set object
metadata FAILED
timeout: timed out after 5000 msec waiting for metadata should be set
Chrome 25.0 (Linux): Executed 17 of 34 (1 FAILED)

And in the shell logs we can see the corresponding 5 seconds delay in the
websockets communication

1386782408.775987 DEBUG gwebsockets: Text message
{"method":"datastore.set_metadata","id":3,"params":["56ab3f11-4654-457d-97ee-b8b1ec092e3b",{"title":"hello"}],"jsonrpc":"2.0"}
1386782409.802124 DEBUG gwebsockets: Got data, length 114

That's not enough to say if python is never sending the message or if
javascript is never receiving/handling it. So I make gwebsockets log
sent messages to... when we get the next failure we can check if that
helps figuring out what is going on.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] XO Help 17

[Iain Brown Douglas]

I have put a little bit of work updating XO Help last month, as requested in [1]

I have also written for Help a page entitled "How to edit Help and
contribute", which will be available within XO Help 17. Pre release the
content is available by this git clone [2]

The page contains 6 small tutorials.

To accompany XO Help 17 is a landing page [3]

[1] http://wiki.laptop.org/go/Help_Activity_refresh/0.98

[2] git clone gitori...@git.sugarlabs.org:help/mainline.git

[3] http://wiki.sugarlabs.org/go/Activities/Help/Contribute

Critical feedback welcome, with thanks,

Iain


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] web-activity: env.getEnvironment dependency with Python code

[Rogelio Mita]

And this pull request: https://github.com/sugarlabs/sugar-web/pull/97

change some semantics on
https://github.com/sugarlabs/sugar-web/blob/master/test/envSpec.js#L129test
and till now we have only this particular case behavior in our API


2013/12/11 Rogelio Mita 

> Hi Daniel, when you have a moment can you check this pull request that
> repairs this functional 
> testwhich
>  no was running
> https://github.com/sugarlabs/sugar-web/pull/96
>
> Thanks!
>
>
> 2013/12/2 Rogelio Mita 
>
>> ok, thanks!
>>
>>
>> 2013/12/2 Daniel Narvaez 
>>
>>> Github is a bit broken at the moment, but I'll try to finish up
>>> reviewing later tonight. Thanks.
>>>
>>>
>>> On Monday, 2 December 2013, Code Raguet wrote:
>>>

 On Thu, Nov 28, 2013 at 3:26 PM, Daniel Narvaez wrote:

> Those are hard questions :) I was also thinking about compatibility
> with old sugar-toolkit-gtk3 versions when we change stuff like
> getEnvironment.
>
 For future changes on this, we add some unitttest, so refactoring
 should be safer
 https://github.com/sugarlabs/sugar-web/pull/94

 Please, can anyone review this pull-request??


> What about having two configurations, one for Sugar running only
> inside sugar-build (what we have now), the other running into a normal web
> browser running outside sugar-build. Seems like this would ensure
> functionality of the contracts we currently care about? The sugar-web
> inside sugar-build would break if sugar-toolkit-gtk3 doesn't fulfil the 
> the
> contract.
>
 This is a good idea, but I'm not sure if it's priority right now...
 perhaps in the short term this would bring-up again and we may revisit this
 issue.


> There is a difference between testing that getEnvironment works or
> that the bits getEnvironment depend on (window.sugar) works as expected.
> Perhaps where we think that difference might matter we could also have
> tests which tests only the contract with toolkit, without other code 
> layers
> in the middle. But getEnvironment is so thin that it probably doesn't
> matter at the moment..
>

 +1

>
> We would need to figure out how to automate tests in a normal web
> browser, but shouldn't be much of a problem.
>
 Roger, pointed me out that datastoreSpec mainly fails on standalone
 mode... perhaps we should review those tests to find out if they can be
 fixed. But it's not enough for having two configs, yet, IMHO.

 PS: we would like to rework a bit env.js, but we need the new unit
 tests merged in order to continue. If someone can review them soon will be
 appreciated.

>>>
>>>
>>> --
>>> Daniel Narvaez
>>>
>>>
>>
>>
>> --
>> Roger
>>
>> Activity Central 
>>
>
>
>
> --
> Roger
>
> Activity Central 
>



-- 
Roger

Activity Central 
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] build an activity

[James Cameron]

On Wed, Dec 11, 2013 at 12:00:25PM -0500, Adam Holt wrote:
> On Wed, Dec 11, 2013 at 11:53 AM, Chris Leonard 
> wrote:
> 
> On Wed, Dec 11, 2013 at 12:36 AM, James Cameron  wrote:
> > Marked {{dated}}.
> >
> > Perhaps Sugar Labs could give us a replacement on their Wiki?
> >
> > I don't think this content needs to be hosted on wiki.laptop.org if it
> > can be hosted at wiki.sugarlabs.org.
> >
> 
> I would imagine many of these pages could benefit from review and / or
> migration.
> 
> http://wiki.laptop.org/go/Category:Developers
> 
> 
> Daniel Drake worked hard on http://wiki.laptop.org/go/Developers_manual ~20
> months ago, but time passes fast :-)

Not relevant; the original poster was talking about activity
development, and [[Developers_manual]] is more broadly focused on
developing for the OLPC XO laptop.  Activity development is only a
small subset of this.  So I would keep the developers' manual.

-- 
James Cameron
http://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] web-activity: env.getEnvironment dependency with Python code

[Rogelio Mita]

Hi Daniel, when you have a moment can you check this pull request that
repairs this functional
testwhich
no was running
https://github.com/sugarlabs/sugar-web/pull/96

Thanks!


2013/12/2 Rogelio Mita 

> ok, thanks!
>
>
> 2013/12/2 Daniel Narvaez 
>
>> Github is a bit broken at the moment, but I'll try to finish up reviewing
>> later tonight. Thanks.
>>
>>
>> On Monday, 2 December 2013, Code Raguet wrote:
>>
>>>
>>> On Thu, Nov 28, 2013 at 3:26 PM, Daniel Narvaez wrote:
>>>
 Those are hard questions :) I was also thinking about compatibility
 with old sugar-toolkit-gtk3 versions when we change stuff like
 getEnvironment.

>>> For future changes on this, we add some unitttest, so refactoring should
>>> be safer
>>> https://github.com/sugarlabs/sugar-web/pull/94
>>>
>>> Please, can anyone review this pull-request??
>>>
>>>
 What about having two configurations, one for Sugar running only inside
 sugar-build (what we have now), the other running into a normal web
 browser running outside sugar-build. Seems like this would ensure
 functionality of the contracts we currently care about? The sugar-web
 inside sugar-build would break if sugar-toolkit-gtk3 doesn't fulfil the the
 contract.

>>> This is a good idea, but I'm not sure if it's priority right now...
>>> perhaps in the short term this would bring-up again and we may revisit this
>>> issue.
>>>
>>>
 There is a difference between testing that getEnvironment works or that
 the bits getEnvironment depend on (window.sugar) works as expected. Perhaps
 where we think that difference might matter we could also have tests which
 tests only the contract with toolkit, without other code layers in the
 middle. But getEnvironment is so thin that it probably doesn't matter at
 the moment..

>>>
>>> +1
>>>

 We would need to figure out how to automate tests in a normal web
 browser, but shouldn't be much of a problem.

>>> Roger, pointed me out that datastoreSpec mainly fails on standalone
>>> mode... perhaps we should review those tests to find out if they can be
>>> fixed. But it's not enough for having two configs, yet, IMHO.
>>>
>>> PS: we would like to rework a bit env.js, but we need the new unit tests
>>> merged in order to continue. If someone can review them soon will be
>>> appreciated.
>>>
>>
>>
>> --
>> Daniel Narvaez
>>
>>
>
>
> --
> Roger
>
> Activity Central 
>



-- 
Roger

Activity Central 
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] build an activity

[Adam Holt]

On Wed, Dec 11, 2013 at 11:53 AM, Chris Leonard wrote:

> On Wed, Dec 11, 2013 at 12:36 AM, James Cameron  wrote:
> > Marked {{dated}}.
> >
> > Perhaps Sugar Labs could give us a replacement on their Wiki?
> >
> > I don't think this content needs to be hosted on wiki.laptop.org if it
> > can be hosted at wiki.sugarlabs.org.
> >
>
> I would imagine many of these pages could benefit from review and / or
> migration.
>
> http://wiki.laptop.org/go/Category:Developers
>

Daniel Drake worked hard on http://wiki.laptop.org/go/Developers_manual ~20
months ago, but time passes fast :-)

--
Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org !

>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] build an activity

[Chris Leonard]

On Wed, Dec 11, 2013 at 12:36 AM, James Cameron  wrote:
> Marked {{dated}}.
>
> Perhaps Sugar Labs could give us a replacement on their Wiki?
>
> I don't think this content needs to be hosted on wiki.laptop.org if it
> can be hosted at wiki.sugarlabs.org.
>

I would imagine many of these pages could benefit from review and / or
migration.

http://wiki.laptop.org/go/Category:Developers
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [DESIGN] Network view refresh button

[Gonzalo Odiard]

+1

The networking / collaboration stack is big and complex, and interact with
power management and timing issues,
in ways difficult to solve for all the cases.

Dextrose used (and we include in AU image) a patch to disable
suspend/resume
while a activity is being shared [1] and the associated ticket [2] show how
complex is the issue.

I think be we should include this patch, and disable suspend/resume when
the user is in the neighborhood view too.

Gonzalo

[1]
https://github.com/godiard/au1b_rpms/blob/master/sugar-toolkit-gtk3/0001-Inhibit-suspend-while-a-activity-is-shared-OLPC-1036.patch
[2] http://dev.laptop.org/ticket/10363



On Tue, Dec 10, 2013 at 11:12 PM, Sebastian Silva  wrote:

> El 10/12/13 16:15, Walter Bender escribió:
>
>  On Tue, Dec 10, 2013 at 4:02 PM, Daniel Narvaez
>>  wrote:
>>
>>> >For what it's worth I agree with Gary comment on the bug. We should fix
>>> the
>>> >bugs.
>>>
>> Hard to argue with fixing bugs but the reality is that the we have no
>> one maintaining the collaboration stack at the moment, incomplete
>> characterizations of the bugs, and this patch is a pretty simple and
>> clean way to paper over a headache for our users.
>>
>> -walter
>>
> +1
> Unless there would be a proper fix, this is a lot better than going to My
> Settings and changing jabber server twice, which is what i've done
> sometimes for a refresh.
>
> Regards,
> Sebastian
>
> --
> @icarito
> I+D SomosAzucar.Org
> freenode: #somosazucar
> Sugar Labs Perú
> Enviado desde mi computadora genérica con Software Libre
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Frequent buildbot check failures in sugar-web

[Code Raguet]

On Tue, Dec 10, 2013 at 6:50 PM, Daniel Narvaez  wrote:

> After I cleaned disk, it always succeeded so far.
>
Nice! Green again  :D


> Let's see when/how it fails again, I guess. But let me know if you want
> access to the slaves.
>
+ 1


Thank, Daniel!
And, of course, next time I can take a look if you are busy.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel