Re: [E-devel] [EGIT] [core/efl] master 16/16: eolian: Add inarray and inlist to source generation

2017-12-04 Thread Jean-Philippe André 
Hi C# guys ;)

Thanks so much for finally merging those patches!

As for this one in particular, I don't think we want to use inarray or
inlist in the EO API.
Those types are quite weird in C, I'm not convinced we should try and
expose them outside of EFL (in EO API). We are currently not using them, I
think.

I will myself merge a large series of patches for C++ generation, including
parts and function pointer support.
I understand perfectly that the code may not be that great, but I want to
merge to master so that we have a common base for work. Please feel free to
modify or let me know what's wrong :)

Best regards,



On Tue, Dec 5, 2017 at 7:37 AM, Felipe Magno de Almeida <
fel...@expertisesolutions.com.br> wrote:

> felipealmeida pushed a commit to branch master.
>
> http://git.enlightenment.org/core/efl.git/commit/?id=
> 66eb8ddfebf65f944a44f8b8871a8628757fe74e
>
> commit 66eb8ddfebf65f944a44f8b8871a8628757fe74e
> Author: Felipe Magno de Almeida 
> Date:   Mon Dec 4 20:32:06 2017 -0200
>
> eolian: Add inarray and inlist to source generation
> ---
>  src/bin/eolian/sources.c   | 28 ++--
>  src/tests/efl_mono/test_testing.eo |  4 ++--
>  2 files changed, 28 insertions(+), 4 deletions(-)
>
> diff --git a/src/bin/eolian/sources.c b/src/bin/eolian/sources.c
> index 2ba900c9bd..a8a349fa86 100644
> --- a/src/bin/eolian/sources.c
> +++ b/src/bin/eolian/sources.c
> @@ -189,14 +189,20 @@ _generate_iterative_free(Eina_Strbuf **buf, const
> Eolian_Type *type, const Eolia
> iterator_header = eina_strbuf_new();
> iter_param = eina_strbuf_new();
>
> +   Eolian_Type_Builtin_Type t = eolian_type_builtin_type_get(type);
> +
> eina_strbuf_append_printf(iter_param, "%s_iter",
> eolian_parameter_name_get(parameter));
>
> //generate the field definition
> eina_strbuf_append_printf(*buf, "   %s", 
> eolian_type_c_type_get(inner_type,
> EOLIAN_C_TYPE_DEFAULT));
> +   if(t == EOLIAN_TYPE_BUILTIN_INARRAY
> +  || t == EOLIAN_TYPE_BUILTIN_INLIST)
> + {
> +   eina_strbuf_append(*buf, "*");
> + }
> eina_strbuf_append_buffer(*buf, iter_param);
> eina_strbuf_append(*buf, ";\n");
>
> -   Eolian_Type_Builtin_Type t = eolian_type_builtin_type_get(type);
>
> if (t == EOLIAN_TYPE_BUILTIN_LIST)
>   {
> @@ -207,6 +213,24 @@ _generate_iterative_free(Eina_Strbuf **buf, const
> Eolian_Type *type, const Eolia
>  eina_strbuf_append(*buf, ")\n");
>  _generate_loop_content(buf, inner_type, iter_param);
>   }
> +   else if (t == EOLIAN_TYPE_BUILTIN_INARRAY)
> + {
> +eina_strbuf_append_printf(*buf, "   EINA_INARRAY_FOREACH(");
> +eina_strbuf_append_buffer(*buf, param);
> +eina_strbuf_append_char(*buf, ',');
> +eina_strbuf_append_buffer(*buf, iter_param);
> +eina_strbuf_append(*buf, ")\n");
> +_generate_loop_content(buf, inner_type, iter_param);
> + }
> +   else if (t == EOLIAN_TYPE_BUILTIN_INLIST)
> + {
> +eina_strbuf_append_printf(*buf, "   EINA_INLIST_FREE(");
> +eina_strbuf_append_buffer(*buf, param);
> +eina_strbuf_append_char(*buf, ',');
> +eina_strbuf_append_buffer(*buf, iter_param);
> +eina_strbuf_append(*buf, ")\n");
> +_generate_loop_content(buf, inner_type, iter_param);
> + }
> else if (t == EOLIAN_TYPE_BUILTIN_ITERATOR)
>   {
>  eina_strbuf_append_printf(*buf, "   EINA_ITERATOR_FOREACH(");
> @@ -237,7 +261,7 @@ _generate_iterative_free(Eina_Strbuf **buf, const
> Eolian_Type *type, const Eolia
>   }
> else
>   {
> -printf("Error, container unknown?!\n");
> +printf("Error, container unknown?! %d\n", (int)t);
>   }
>
> eina_strbuf_free(iterator_header);
> diff --git a/src/tests/efl_mono/test_testing.eo b/src/tests/efl_mono/test_
> testing.eo
> index db6f13bcf2..bf13a57283 100644
> --- a/src/tests/efl_mono/test_testing.eo
> +++ b/src/tests/efl_mono/test_testing.eo
> @@ -370,7 +370,7 @@ class Test.Testing (Efl.Object) {
>/* Integer */
>eina_inarray_int_in {
>   params {
> -@in arr: inarray;
> +@in arr: inarray;
>   }
>   return: bool;
>}
> @@ -387,7 +387,7 @@ class Test.Testing (Efl.Object) {
>
>eina_inarray_int_out {
>   params {
> -@out arr: inarray;
> +@out arr: inarray;
>   }
>   return: bool;
>}
>
> --
>
> --
> Jean-Philippe André
>
>
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [support.osuosl.org #29680] enlightenment5.osuosl.oob fan failure

2017-12-04 Thread William L. Thomson Jr. 
On Tue, 5 Dec 2017 00:18:13 +
Bertrand Jacquin  wrote:
>
> Cedric, can we order a set of new fan to replace the existing ? I
> won't be surprised they have been damaged with time.

I recommend sending a couple extra fans. Having 1 or 2 on hand. I
would also do the same with hard drives and power supplies. Assuming
the server has multiple of each. I think OSUOSL can store them for you.
I had my own racks at DCs I was in so wasn't an issue for me. It is
invaluable at times, and not a major cost.

Talk to Lance Albertson at OSUOSL. I met him years ago at LWE when
were both Gentoo devs. He still is a Gentoo Developer. He is a good
honest guy and knows his stuff. Very trustworthy. I would think he
could accommodate some spares.

Not that me vouching for him counts for anything since its from me
Or any recommendations... Still can't hurt beyond the cost.

-- 
William L. Thomson Jr.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [support.osuosl.org #29680] enlightenment5.osuosl.oob fan failure

2017-12-04 Thread Bertrand Jacquin 
On Mon, Dec 04, 2017 at 04:09:09PM -0800, Jonathan Frederick via RT wrote:
> On Mon Dec 04 14:57:41 2017, bertr...@jacquin.bzh wrote:
> > According to lm_sensors, all is fine:
> >
> > nct7904-i2c-0-2e
> > Adapter: SMBus I801 adapter at 1180
> > in1: +1.04 V
> > in2: +0.43 V
> > in3: +1.50 V
> > in4: +0.51 V
> > in5: +1.27 V
> > in6: +1.26 V
> > in7: +1.83 V
> > in8: +1.46 V
> > in9: +0.94 V
> > in10: +0.82 V
> > in11: +1.50 V
> > in12: +2.01 V
> > in13: +1.50 V
> > in14: +2.01 V
> > in15: +3.37 V
> > in16: +3.22 V
> > in20: +3.32 V
> > fan1: 8035 RPM
> > fan2: 7714 RPM
> > fan3: 8333 RPM
> > fan4: 0 RPM
> > fan5: 7848 RPM
> > fan6: 8132 RPM
> > fan7: 0 RPM
> > fan8: 0 RPM
> > temp1: +36.9 C
> > temp2: +43.5 C
> > temp3: +51.8 C
> >
> > coretemp-isa-
> > Adapter: ISA adapter
> > Physical id 0: +35.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 0: +32.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 1: +32.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 2: +35.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 3: +30.0 C (high = +84.0 C, crit = +94.0 C)
> >
> > coretemp-isa-0001
> > Adapter: ISA adapter
> > Physical id 1: +38.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 0: +36.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 1: +34.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 2: +38.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 3: +38.0 C (high = +84.0 C, crit = +94.0 C)
> >
> > I'm not really sure if I should trust lm_sensors or the buzz.
> >
> 
> As of right now the light and buzzer are still going off, maybe the 
> temperature
> is fine but one of the fans have failed, triggering the buzz.
> 
> It's constantly on for 10 seconds at a time, then off for a while longer

Looking at the server health from the BMC interface, no alarm is present
for far or temp, but it looks like FAN4 is reported as not present,
which is strange. Another alarm is present for Chassis Intrusion,
unfortunately, there is no option to disable this.

Cedric, can we order a set of new fan to replace the existing ? I won't
be surprised they have been damaged with time.

-- 
Bertrand


signature.asc
Description: Digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [support.osuosl.org #29680] enlightenment5.osuosl.oob fan failure

2017-12-04 Thread Bertrand Jacquin via RT 
On Mon, Dec 04, 2017 at 04:09:09PM -0800, Jonathan Frederick via RT wrote:
> On Mon Dec 04 14:57:41 2017, bertr...@jacquin.bzh wrote:
> > According to lm_sensors, all is fine:
> >
> > nct7904-i2c-0-2e
> > Adapter: SMBus I801 adapter at 1180
> > in1: +1.04 V
> > in2: +0.43 V
> > in3: +1.50 V
> > in4: +0.51 V
> > in5: +1.27 V
> > in6: +1.26 V
> > in7: +1.83 V
> > in8: +1.46 V
> > in9: +0.94 V
> > in10: +0.82 V
> > in11: +1.50 V
> > in12: +2.01 V
> > in13: +1.50 V
> > in14: +2.01 V
> > in15: +3.37 V
> > in16: +3.22 V
> > in20: +3.32 V
> > fan1: 8035 RPM
> > fan2: 7714 RPM
> > fan3: 8333 RPM
> > fan4: 0 RPM
> > fan5: 7848 RPM
> > fan6: 8132 RPM
> > fan7: 0 RPM
> > fan8: 0 RPM
> > temp1: +36.9 C
> > temp2: +43.5 C
> > temp3: +51.8 C
> >
> > coretemp-isa-
> > Adapter: ISA adapter
> > Physical id 0: +35.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 0: +32.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 1: +32.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 2: +35.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 3: +30.0 C (high = +84.0 C, crit = +94.0 C)
> >
> > coretemp-isa-0001
> > Adapter: ISA adapter
> > Physical id 1: +38.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 0: +36.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 1: +34.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 2: +38.0 C (high = +84.0 C, crit = +94.0 C)
> > Core 3: +38.0 C (high = +84.0 C, crit = +94.0 C)
> >
> > I'm not really sure if I should trust lm_sensors or the buzz.
> >
> 
> As of right now the light and buzzer are still going off, maybe the 
> temperature
> is fine but one of the fans have failed, triggering the buzz.
> 
> It's constantly on for 10 seconds at a time, then off for a while longer

Looking at the server health from the BMC interface, no alarm is present
for far or temp, but it looks like FAN4 is reported as not present,
which is strange. Another alarm is present for Chassis Intrusion,
unfortunately, there is no option to disable this.

Cedric, can we order a set of new fan to replace the existing ? I won't
be surprised they have been damaged with time.

-- 
Bertrand



signature.asc
Description: PGP signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

[E-devel] [support.osuosl.org #29680] enlightenment5.osuosl.oob fan failure

2017-12-04 Thread Jonathan Frederick via RT 
On Mon Dec 04 14:57:41 2017, bertr...@jacquin.bzh wrote:
> According to lm_sensors, all is fine:
>
> nct7904-i2c-0-2e
> Adapter: SMBus I801 adapter at 1180
> in1: +1.04 V
> in2: +0.43 V
> in3: +1.50 V
> in4: +0.51 V
> in5: +1.27 V
> in6: +1.26 V
> in7: +1.83 V
> in8: +1.46 V
> in9: +0.94 V
> in10: +0.82 V
> in11: +1.50 V
> in12: +2.01 V
> in13: +1.50 V
> in14: +2.01 V
> in15: +3.37 V
> in16: +3.22 V
> in20: +3.32 V
> fan1: 8035 RPM
> fan2: 7714 RPM
> fan3: 8333 RPM
> fan4: 0 RPM
> fan5: 7848 RPM
> fan6: 8132 RPM
> fan7: 0 RPM
> fan8: 0 RPM
> temp1: +36.9 C
> temp2: +43.5 C
> temp3: +51.8 C
>
> coretemp-isa-
> Adapter: ISA adapter
> Physical id 0: +35.0 C (high = +84.0 C, crit = +94.0 C)
> Core 0: +32.0 C (high = +84.0 C, crit = +94.0 C)
> Core 1: +32.0 C (high = +84.0 C, crit = +94.0 C)
> Core 2: +35.0 C (high = +84.0 C, crit = +94.0 C)
> Core 3: +30.0 C (high = +84.0 C, crit = +94.0 C)
>
> coretemp-isa-0001
> Adapter: ISA adapter
> Physical id 1: +38.0 C (high = +84.0 C, crit = +94.0 C)
> Core 0: +36.0 C (high = +84.0 C, crit = +94.0 C)
> Core 1: +34.0 C (high = +84.0 C, crit = +94.0 C)
> Core 2: +38.0 C (high = +84.0 C, crit = +94.0 C)
> Core 3: +38.0 C (high = +84.0 C, crit = +94.0 C)
>
> I'm not really sure if I should trust lm_sensors or the buzz.
>

As of right now the light and buzzer are still going off, maybe the temperature
is fine but one of the fans have failed, triggering the buzz.

It's constantly on for 10 seconds at a time, then off for a while longer

--
Jonathan Frederick
Student Systems Engineer
Oregon State University | Open Source Lab


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [support.osuosl.org #29680] enlightenment5.osuosl.oob fan failure

2017-12-04 Thread Bertrand Jacquin 

Hi,

On 04/12/2017 20:47, Jonathan Frederick via RT wrote:

On Wed Aug 30 12:02:07 2017, doublej472 wrote:

Upon further inspection it appears that the issue has disappeared; The
blinking
light and buzzer noise is no longer present. In that case the box
could be
simply overheating when under heavy load, or be experiencing some
intermittent
fan problems. I'll keep an eye on it for now, in case it decides it
doesn't
want to work again.

On Sun Aug 27 17:19:27 2017, ramereth wrote:
> Thanks for checking. We'll take a closer look sometime tomorrow.


This issue appears to have come back!

When I was in the datacenter it was buzzing and showing the overheating 
symbol
again. It could be that the cooling is inadequate when put under load, 
is it

possible to check the temperature on lm-sensors?


According to lm_sensors, all is fine:

nct7904-i2c-0-2e
Adapter: SMBus I801 adapter at 1180
in1:  +1.04 V
in2:  +0.43 V
in3:  +1.50 V
in4:  +0.51 V
in5:  +1.27 V
in6:  +1.26 V
in7:  +1.83 V
in8:  +1.46 V
in9:  +0.94 V
in10: +0.82 V
in11: +1.50 V
in12: +2.01 V
in13: +1.50 V
in14: +2.01 V
in15: +3.37 V
in16: +3.22 V
in20: +3.32 V
fan1:8035 RPM
fan2:7714 RPM
fan3:8333 RPM
fan4:   0 RPM
fan5:7848 RPM
fan6:8132 RPM
fan7:   0 RPM
fan8:   0 RPM
temp1:+36.9 C
temp2:+43.5 C
temp3:+51.8 C

coretemp-isa-
Adapter: ISA adapter
Physical id 0:  +35.0 C  (high = +84.0 C, crit = +94.0 C)
Core 0: +32.0 C  (high = +84.0 C, crit = +94.0 C)
Core 1: +32.0 C  (high = +84.0 C, crit = +94.0 C)
Core 2: +35.0 C  (high = +84.0 C, crit = +94.0 C)
Core 3: +30.0 C  (high = +84.0 C, crit = +94.0 C)

coretemp-isa-0001
Adapter: ISA adapter
Physical id 1:  +38.0 C  (high = +84.0 C, crit = +94.0 C)
Core 0: +36.0 C  (high = +84.0 C, crit = +94.0 C)
Core 1: +34.0 C  (high = +84.0 C, crit = +94.0 C)
Core 2: +38.0 C  (high = +84.0 C, crit = +94.0 C)
Core 3: +38.0 C  (high = +84.0 C, crit = +94.0 C)

I'm not really sure if I should trust lm_sensors or the buzz.

--
Bertrand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [support.osuosl.org #29680] enlightenment5.osuosl.oob fan failure

2017-12-04 Thread Bertrand Jacquin via RT 
Hi,

On 04/12/2017 20:47, Jonathan Frederick via RT wrote:
> On Wed Aug 30 12:02:07 2017, doublej472 wrote:
>> Upon further inspection it appears that the issue has disappeared; The
>> blinking
>> light and buzzer noise is no longer present. In that case the box
>> could be
>> simply overheating when under heavy load, or be experiencing some
>> intermittent
>> fan problems. I'll keep an eye on it for now, in case it decides it
>> doesn't
>> want to work again.
>> 
>> On Sun Aug 27 17:19:27 2017, ramereth wrote:
>> > Thanks for checking. We'll take a closer look sometime tomorrow.
> 
> This issue appears to have come back!
> 
> When I was in the datacenter it was buzzing and showing the overheating 
> symbol
> again. It could be that the cooling is inadequate when put under load, 
> is it
> possible to check the temperature on lm-sensors?

According to lm_sensors, all is fine:

nct7904-i2c-0-2e
Adapter: SMBus I801 adapter at 1180
in1:  +1.04 V
in2:  +0.43 V
in3:  +1.50 V
in4:  +0.51 V
in5:  +1.27 V
in6:  +1.26 V
in7:  +1.83 V
in8:  +1.46 V
in9:  +0.94 V
in10: +0.82 V
in11: +1.50 V
in12: +2.01 V
in13: +1.50 V
in14: +2.01 V
in15: +3.37 V
in16: +3.22 V
in20: +3.32 V
fan1:8035 RPM
fan2:7714 RPM
fan3:8333 RPM
fan4:   0 RPM
fan5:7848 RPM
fan6:8132 RPM
fan7:   0 RPM
fan8:   0 RPM
temp1:+36.9 C
temp2:+43.5 C
temp3:+51.8 C

coretemp-isa-
Adapter: ISA adapter
Physical id 0:  +35.0 C  (high = +84.0 C, crit = +94.0 C)
Core 0: +32.0 C  (high = +84.0 C, crit = +94.0 C)
Core 1: +32.0 C  (high = +84.0 C, crit = +94.0 C)
Core 2: +35.0 C  (high = +84.0 C, crit = +94.0 C)
Core 3: +30.0 C  (high = +84.0 C, crit = +94.0 C)

coretemp-isa-0001
Adapter: ISA adapter
Physical id 1:  +38.0 C  (high = +84.0 C, crit = +94.0 C)
Core 0: +36.0 C  (high = +84.0 C, crit = +94.0 C)
Core 1: +34.0 C  (high = +84.0 C, crit = +94.0 C)
Core 2: +38.0 C  (high = +84.0 C, crit = +94.0 C)
Core 3: +38.0 C  (high = +84.0 C, crit = +94.0 C)

I'm not really sure if I should trust lm_sensors or the buzz.

-- 
Bertrand



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Enlightenment Developer Days 2018 location proposals

2017-12-04 Thread Andrew Williams 
Hi,

It's perhaps worth noting that ELCE will be in Edinburgh this year -
http://events.linuxfoundation.org/events/embedded-linux-conference-europe .
The venue is really close to where I had proposed for the E Dev Day, I know
it's later in the year but perhaps we could schedule to co-inside?

Just a thought,
Andy



On Mon, 4 Dec 2017 at 12:35 Stefan Schmidt  wrote:

> Hello.
>
>
> On 11/22/2017 05:50 PM, Stefan Schmidt wrote:
> > Hello.
> >
> >
> > The end of the year is near and we should start thinking about the next
> edition of the Enlightenment developer days.
> >
> >
> > So far we have been doing good with starting to source a suitable
> location first and find the best dates after that. I would go the same
> > route this year.
> >
> > Loking back at last years location voting we can see that Malta was on
> the top position together with Toulouse. With a close follow up of
> > Paris and Edinburgh.
> >
> > https://phab.enlightenment.org/V27
> >
> >
> > The questions comes up if our location proposals are still up to date.
> Are the persons willing to do the local organization still available?
> > (move, different employer). If your name is listed on the location
> proposals list please clarify if this is still valid or not. Simply
> > remove it if not.
> >
> > https://phab.enlightenment.org/w/events/location_proposals/
> >
> >
> > One location that is not listed on the wiki which I brought up at last
> years event was Bangkok. As far as I know we have nobody in our
> > community from there but if we would like to aim for a non EU event
> again this might be a sweet spot. In terms of flight prices from Europe
> > and being in good reach for all Asia. Just an idea, we would need to
> find local help if people are interested in it.
> >
> >
> > Please update the location proposals and start your discussion here.
> >
>
> Feedback has so far been very limited. Andy confirmed that Edinburgh would
> be possible with a good lead time for the venue.
>
> Any more comments? I would like to hear comments on potential locations as
> well as actual location offers.
>
> History has shown that we should start to plan for this early on to make
> sure things can get sorted out in time.
>
> regards
> Stefan Schmidt
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
-- 
http://andywilliams.me
http://ajwillia.ms
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

[E-devel] [support.osuosl.org #29680] enlightenment5.osuosl.oob fan failure

2017-12-04 Thread Jonathan Frederick via RT 
On Wed Aug 30 12:02:07 2017, doublej472 wrote:
> Upon further inspection it appears that the issue has disappeared; The
> blinking
> light and buzzer noise is no longer present. In that case the box
> could be
> simply overheating when under heavy load, or be experiencing some
> intermittent
> fan problems. I'll keep an eye on it for now, in case it decides it
> doesn't
> want to work again.
>
> On Sun Aug 27 17:19:27 2017, ramereth wrote:
> > Thanks for checking. We'll take a closer look sometime tomorrow.
> >
>
> --
> Jonathan Frederick
> Student Systems Engineer
> Oregon State University | Open Source Lab

This issue appears to have come back!

When I was in the datacenter it was buzzing and showing the overheating symbol
again. It could be that the cooling is inadequate when put under load, is it
possible to check the temperature on lm-sensors?

--
Jonathan Frederick
Student Systems Engineer
Oregon State University | Open Source Lab


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

[E-devel] Weekly news from the automated build and QA front

2017-12-04 Thread Stefan Schmidt 
Hello.

Summary:
o A bunch of new patches for review


This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parentheses reflect the values from
last week to give you a trend.

CI:
o Overall build statistic: 8.80% (7.16%) failed.
https://build.enlightenment.org/

Unit tests:
o N/A (N/A) unit tests for efl

Coverage:
o EFL total coverage is at N/A% (N/A%) lines, N/A% (N/A%) functions and N/A 
(N/A) branches
https://build.enlightenment.org/view/Test%20Coverage/

Coverity:
o EFL: Outstanding defects 54 (51) with a density of 0.05 (0.04)
o Enlightenment: Outstanding defects 0 (1) with a density of 0 (0)
o Terminology: Outstanding defects 0 (0) with a density of 0 (0)
o Rage: Outstanding defects 1 (1) with a density of 0.02 (0.02)

Phab:
o EFL bug count: 540 (536)
o E bug count: 356 (353)
https://phab.enlightenment.org/maniphest/report/burn/
o Pending patch reviews: 211 (189)

regards
Stefan Schmidt

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] Enlightenment Developer Days 2018 location proposals

2017-12-04 Thread Stefan Schmidt 
Hello.


On 11/22/2017 05:50 PM, Stefan Schmidt wrote:
> Hello.
>
>
> The end of the year is near and we should start thinking about the next 
> edition of the Enlightenment developer days.
>
>
> So far we have been doing good with starting to source a suitable location 
> first and find the best dates after that. I would go the same
> route this year.
>
> Loking back at last years location voting we can see that Malta was on the 
> top position together with Toulouse. With a close follow up of
> Paris and Edinburgh.
>
> https://phab.enlightenment.org/V27
>
>
> The questions comes up if our location proposals are still up to date. Are 
> the persons willing to do the local organization still available?
> (move, different employer). If your name is listed on the location proposals 
> list please clarify if this is still valid or not. Simply
> remove it if not.
>
> https://phab.enlightenment.org/w/events/location_proposals/
>
>
> One location that is not listed on the wiki which I brought up at last years 
> event was Bangkok. As far as I know we have nobody in our
> community from there but if we would like to aim for a non EU event again 
> this might be a sweet spot. In terms of flight prices from Europe
> and being in good reach for all Asia. Just an idea, we would need to find 
> local help if people are interested in it.
>
>
> Please update the location proposals and start your discussion here.
>

Feedback has so far been very limited. Andy confirmed that Edinburgh would be 
possible with a good lead time for the venue.

Any more comments? I would like to hear comments on potential locations as well 
as actual location offers.

History has shown that we should start to plan for this early on to make sure 
things can get sorted out in time.

regards
Stefan Schmidt

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [EGIT] [core/efl] master 01/01: efl_ui_spin: Add new spin and spin_button widgets

2017-12-04 Thread Stefan Schmidt 
Hello.


On 12/04/2017 12:42 PM, 조재현 wrote:
> I had the same problem but the problem was solved when I removed all eo.* 
> files created by compilation as texi2se told me as follows.
>
>
> find . -name "*₩.eo₩.*" -exec rm {} ₩;
>
>
>
>
> 네이버 메일 앱에서 보냈습니다.
>
> -Original Message-
> 보낸사람: "Jean-Philippe André" j...@videolan.org
> 받는사람: "Enlightenment developer list" 
> enlightenment-devel@lists.sourceforge.net
> 참조: wc0917@samsung.com
> 날짜: 2017.12.04 오후 08:03:48
> 제목: Re: [E-devel] [EGIT] [core/efl] master 01/01: efl_ui_spin: Add new spin 
> and spin_button widgets
>
>
>
> Does this still happen? I can't reproduce this problem. Unless someone
> fixed it?
>

You are both right. I had indeed the old eo files around. Sorry for the noise!


regards

Stefan Schmidt


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [EGIT] [core/efl] master 02/02: ecore_con: use eina_future based timeout for tests.

2017-12-04 Thread Gustavo Sverzut Barbieri 
not sure you need a type, I guess you can pass null, so it will accept
all types except error.


-- 
Gustavo Sverzut Barbieri
--
Mobile: +55 (16) 99354-9890

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [EGIT] [core/efl] master 03/05: efl: Introduce interface Efl.Dup

2017-12-04 Thread Gustavo Sverzut Barbieri 
while at that, what about explicitly have 2 methods: shallow copy and deep copy?

the interface/mixin can have both, and implementers just do one... but
it's a common problem to identify "is this copy a shallow or deep? If
I modify that in X, will it reflect in Y?"



On Mon, Dec 4, 2017 at 7:27 AM, Jean-Philippe André  wrote:
> On Sun, Dec 3, 2017 at 3:45 AM, Andrew Williams 
> wrote:
>
>> Is there anyway we could use a more descriptive name? It just seems
>> unnecessarily short.
>>
>
> Absolutely. It didn't "think", and only changed the name from the method
> "dup".
> Cedric mentioned that to me and I think we'll rename to duplicate or
> cloneable.
>
>
>> Maybe that’s just me.
>> Andy
>> On Fri, 1 Dec 2017 at 18:50, Davide Andreoli 
>> wrote:
>>
>> > 2017-12-01 3:12 GMT+01:00 Jean-Philippe André :
>> >
>> > > On Fri, Dec 1, 2017 at 3:49 AM, Davide Andreoli <
>> d...@gurumeditation.it>
>> > > wrote:
>> > >
>> > > > 2017-11-30 3:36 GMT+01:00 Jean-Philippe ANDRÉ :
>> > > >
>> > > > > jpeg pushed a commit to branch master.
>> > > > >
>> > > > > http://git.enlightenment.org/core/efl.git/commit/?id=
>> > > > > bd5b76508b0b3bdc5d92f5f7db9741c100d47d3c
>> > > > >
>> > > > > commit bd5b76508b0b3bdc5d92f5f7db9741c100d47d3c
>> > > > > Author: Jean-Philippe Andre 
>> > > > > Date:   Wed Nov 29 20:03:16 2017 +0900
>> > > > >
>> > > > > efl: Introduce interface Efl.Dup
>> > > > >
>> > > > > A few classes allow their objects to be duplicated, so they
>> > should
>> > > > all
>> > > > > use the same interface.
>> > > > >
>> > > > > Also, rename VG's dup to copy_from as it's not conforming to
>> the
>> > > > > definition of dup.
>> > > > >
>> > > >
>> > > > Is'nt the last rename (vg_dup) an abi break ?
>> > > >
>> > > > python-efl apps now crash like this:
>> > > > Traceback (most recent call last):
>> > > >   File "/usr/bin/epymc", line 5, in 
>> > > > from epymc.main import start_epymc
>> > > >   File "/usr/lib/python3.6/site-packages/epymc/main.py", line 32, in
>> > > > 
>> > > > from efl import edje
>> > > > ImportError: /usr/local/lib/libedje.so.1: undefined symbol:
>> > > > evas_vg_node_dup
>> > > >
>> > > > A python-efl rebuild fixed the issue, this is why I think it's an abi
>> > > > break.
>> > > >
>> > > > note that the bindings do not use/expose evas_vg in any way
>> > > >
>> > >
>> > > I was under the impression that Evas VG was still "beta".
>> > > In fact I can see EFL_BETA_API_SUPPORT.
>> > >
>> > > Could you double-check on your side what's happening?
>> > > Where is this symbol used?
>> > >
>> >
>> > Probably the symbol is used inside edje. PythonEFL is built with
>> > EFL_BETA_API_SUPPORT on, and I think this is the source of
>> > the issue
>> >
>> >
>> > >
>> > > TIA,
>> > >
>> > >
>> > > >
>> > > >
>> > > >
>> > > > > ---
>> > > > >  src/Makefile_Efl.am   |  1 +
>> > > > >  src/bin/elementary/test_events.c  | 10 +-
>> > > > >  src/lib/edje/edje_calc.c  |  2 +-
>> > > > >  src/lib/efl/Efl.h |  1 +
>> > > > >  src/lib/efl/interfaces/efl_dup.eo | 17
>> +
>> > > > >  src/lib/efl/interfaces/efl_gfx_path.c |  4 ++--
>> > > > >  src/lib/efl/interfaces/efl_gfx_path.eo|  3 ++-
>> > > > >  src/lib/efl/interfaces/efl_gfx_shape.c| 12 +++-
>> > > > >  src/lib/efl/interfaces/efl_gfx_shape.eo   | 12 +++-
>> > > > >  src/lib/efl/interfaces/efl_interfaces_main.c  |  1 +
>> > > > >  src/lib/evas/canvas/efl_canvas_vg.c   |  2 +-
>> > > > >  src/lib/evas/canvas/efl_input_event.eo| 13 +
>> > > > >  src/lib/evas/canvas/efl_input_focus.c |  2 +-
>> > > > >  src/lib/evas/canvas/efl_input_focus.eo| 10 +-
>> > > > >  src/lib/evas/canvas/efl_input_hold.c  |  2 +-
>> > > > >  src/lib/evas/canvas/efl_input_hold.eo | 10 +-
>> > > > >  src/lib/evas/canvas/efl_input_key.c   |  2 +-
>> > > > >  src/lib/evas/canvas/efl_input_key.eo  | 10 +-
>> > > > >  src/lib/evas/canvas/efl_input_pointer.c   |  2 +-
>> > > > >  src/lib/evas/canvas/efl_input_pointer.eo  | 10 +-
>> > > > >  src/lib/evas/canvas/efl_vg.eo |  7 ++-
>> > > > >  src/lib/evas/canvas/efl_vg_container.eo   |  2 +-
>> > > > >  src/lib/evas/canvas/efl_vg_gradient.eo|  2 +-
>> > > > >  src/lib/evas/canvas/efl_vg_gradient_linear.eo |  2 +-
>> > > > >  src/lib/evas/canvas/efl_vg_gradient_radial.eo |  2 +-
>> > > > >  src/lib/evas/canvas/efl_vg_shape.eo   |  2 +-
>> > > > >  src/lib/evas/canvas/evas_device.c |  2 +-
>> > > > >  src/lib/evas/canvas/evas_events.c | 22
>> > > > +++---
>> > > > >  src/lib/evas/canvas/evas_vg_container.c   |  6 +++---
>> > > > >

Re: [E-devel] [EGIT] [core/efl] master 01/01: efl_ui_spin: Add new spin and spin_button widgets

2017-12-04 Thread 조재현 
I had the same problem but the problem was solved when I removed all eo.* files 
created by compilation as texi2se told me as follows.


find . -name "*₩.eo₩.*" -exec rm {} ₩;




네이버 메일 앱에서 보냈습니다.

-Original Message-
보낸사람: "Jean-Philippe André" j...@videolan.org
받는사람: "Enlightenment developer list" 
enlightenment-devel@lists.sourceforge.net
참조: wc0917@samsung.com
날짜: 2017.12.04 오후 08:03:48
제목: Re: [E-devel] [EGIT] [core/efl] master 01/01: efl_ui_spin: Add new spin and 
spin_button widgets



Does this still happen? I can't reproduce this problem. Unless someone
fixed it?

On Fri, Dec 1, 2017 at 7:41 PM, Stefan Schmidt ste...@osg.samsung.com
wrote:

 Hello.


 On 11/27/2017 11:55 AM, Woochan Lee wrote:
  jaehyun pushed a commit to branch master.
 
  http://git.enlightenment.org/core/efl.git/commit/?id=
 eefcb49419af9d0057ba4c03e6c9009a1265e31e
 
  commit eefcb49419af9d0057ba4c03e6c9009a1265e31e
  Author: Woochan Lee wc0917@samsung.com
  Date:   Mon Nov 20 19:12:49 2017 +0900
 
  efl_ui_spin: Add new spin and spin_button widgets
 
  Summary:
  https://phab.enlightenment.org/T5900
 
  Creating base class(efl_ui_spin) to support various shape of 
spinner.
 
  Added button interaction widget efl_ui_spin_button inherited from
 efl_ui_spin.
 
  Test Plan: Add tests in elementary_test.
 
  Reviewers: Jaehyun_Cho, woohyun, jpeg, singh.amitesh
 
  Subscribers: jenkins, id213sin, cedric, jpeg
 
  Differential Revision: https://phab.enlightenment.org/D5424
 

 Since this new widget I get compile error when building the examples.
 My guess is that you either did not try to compile the examples or
 disabled the C++ bindings. Please have a look to get this fixed.

  CXX  bg_cxx_example_01.o
   CXX  bg_cxx_example_02.o
   CXX  button_cxx_example_00.o
   CXX  box_cxx_example_02.o
 In file included from ../../../src/lib/elementary/Elementary.eo.hh:69:0,
  from ../../../src/lib/elementary/Elementary.hh:24,
  from box_cxx_example_02.cc:3:
 ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
 ‘static const Efl_Class* eo_cxx::efl::ui::Spin::_eo_class()’:
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:576:14: error:
 ‘EFL_UI_SPIN_CLASS’ was not declared in this scope
return EFL_UI_SPIN_CLASS;
   ^
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:576:14: note: suggested
 alternative: ‘EFL_UI_WIN_CLASS’
return EFL_UI_SPIN_CLASS;
   ^
   EFL_UI_WIN_CLASS
 In file included from ../../../src/lib/elementary/Elementary.eo.hh:69:0,
  from ../../../src/lib/elementary/Elementary.hh:24,
  from box_cxx_example_02.cc:3:
 ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
 ‘static const Efl_Class* efl::ui::Spin::_eo_class()’:
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:660:14: error:
 ‘EFL_UI_SPIN_CLASS’ was not declared in this scope
return EFL_UI_SPIN_CLASS;
   ^
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:660:14: note: suggested
 alternative: ‘EFL_UI_WIN_CLASS’
return EFL_UI_SPIN_CLASS;
   ^
   EFL_UI_WIN_CLASS
 ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
 ‘static const Efl_Event_Description*
 efl::ui::Spin::changed_event::description()’:
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:666:16: error:
 ‘EFL_UI_SPIN_EVENT_CHANGED’ was not declared in this scope
{ return EFL_UI_SPIN_EVENT_CHANGED; }
 ^
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:666:16: note: suggested
 alternative: ‘EFL_UI_RADIO_EVENT_CHANGED’
{ return EFL_UI_SPIN_EVENT_CHANGED; }
 ^
 EFL_UI_RADIO_EVENT_CHANGED
 ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
 ‘static const Efl_Event_Description*
 efl::ui::Spin::min_reached_event::description()’:
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:672:16: error:
 ‘EFL_UI_SPIN_EVENT_MIN_REACHED’ was not declared in this scope
{ return EFL_UI_SPIN_EVENT_MIN_REACHED; }
 ^
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:672:16: note: suggested
 alternative: ‘ELM_SPINNER_EVENT_MIN_REACHED’
{ return EFL_UI_SPIN_EVENT_MIN_REACHED; }
 ^
 ELM_SPINNER_EVENT_MIN_REACHED
 ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
 ‘static const Efl_Event_Description*
 efl::ui::Spin::max_reached_event::description()’:
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:678:16: error:
 ‘EFL_UI_SPIN_EVENT_MAX_REACHED’ was not declared in this scope
{ return EFL_UI_SPIN_EVENT_MAX_REACHED; }
 ^
 ../../../src/lib/elementary/efl_ui_spin.eo.hh:678:16: note:

Re: [E-devel] [EGIT] [core/efl] master 01/01: efl_ui_spin: Add new spin and spin_button widgets

2017-12-04 Thread Jean-Philippe André 
I guess you still have a file "efl_ui_spin.eo.h" in efl/interfaces. Please
remove it and compile again. It should be located in elementary, not efl.

On Mon, Dec 4, 2017 at 8:03 PM, Jean-Philippe André 
wrote:

> Does this still happen? I can't reproduce this problem. Unless someone
> fixed it?
>
> On Fri, Dec 1, 2017 at 7:41 PM, Stefan Schmidt 
> wrote:
>
>> Hello.
>>
>>
>> On 11/27/2017 11:55 AM, Woochan Lee wrote:
>> > jaehyun pushed a commit to branch master.
>> >
>> > http://git.enlightenment.org/core/efl.git/commit/?id=eefcb49
>> 419af9d0057ba4c03e6c9009a1265e31e
>> >
>> > commit eefcb49419af9d0057ba4c03e6c9009a1265e31e
>> > Author: Woochan Lee 
>> > Date:   Mon Nov 20 19:12:49 2017 +0900
>> >
>> > efl_ui_spin: Add new spin and spin_button widgets
>> >
>> > Summary:
>> > https://phab.enlightenment.org/T5900
>> >
>> > Creating base class(efl_ui_spin) to support various shape of
>> spinner.
>> >
>> > Added button interaction widget efl_ui_spin_button inherited from
>> efl_ui_spin.
>> >
>> > Test Plan: Add tests in elementary_test.
>> >
>> > Reviewers: Jaehyun_Cho, woohyun, jpeg, singh.amitesh
>> >
>> > Subscribers: jenkins, id213sin, cedric, jpeg
>> >
>> > Differential Revision: https://phab.enlightenment.org/D5424
>> >
>>
>> Since this new widget I get compile error when building the examples.
>> My guess is that you either did not try to compile the examples or
>> disabled the C++ bindings. Please have a look to get this fixed.
>>
>>  CXX  bg_cxx_example_01.o
>>   CXX  bg_cxx_example_02.o
>>   CXX  button_cxx_example_00.o
>>   CXX  box_cxx_example_02.o
>> In file included from ../../../src/lib/elementary/Elementary.eo.hh:69:0,
>>  from ../../../src/lib/elementary/Elementary.hh:24,
>>  from box_cxx_example_02.cc:3:
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
>> ‘static const Efl_Class* eo_cxx::efl::ui::Spin::_eo_class()’:
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:576:14: error:
>> ‘EFL_UI_SPIN_CLASS’ was not declared in this scope
>>return EFL_UI_SPIN_CLASS;
>>   ^
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:576:14: note: suggested
>> alternative: ‘EFL_UI_WIN_CLASS’
>>return EFL_UI_SPIN_CLASS;
>>   ^
>>   EFL_UI_WIN_CLASS
>> In file included from ../../../src/lib/elementary/Elementary.eo.hh:69:0,
>>  from ../../../src/lib/elementary/Elementary.hh:24,
>>  from box_cxx_example_02.cc:3:
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
>> ‘static const Efl_Class* efl::ui::Spin::_eo_class()’:
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:660:14: error:
>> ‘EFL_UI_SPIN_CLASS’ was not declared in this scope
>>return EFL_UI_SPIN_CLASS;
>>   ^
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:660:14: note: suggested
>> alternative: ‘EFL_UI_WIN_CLASS’
>>return EFL_UI_SPIN_CLASS;
>>   ^
>>   EFL_UI_WIN_CLASS
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
>> ‘static const Efl_Event_Description*
>> efl::ui::Spin::changed_event::description()’:
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:666:16: error:
>> ‘EFL_UI_SPIN_EVENT_CHANGED’ was not declared in this scope
>>{ return EFL_UI_SPIN_EVENT_CHANGED; }
>> ^
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:666:16: note: suggested
>> alternative: ‘EFL_UI_RADIO_EVENT_CHANGED’
>>{ return EFL_UI_SPIN_EVENT_CHANGED; }
>> ^
>> EFL_UI_RADIO_EVENT_CHANGED
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
>> ‘static const Efl_Event_Description*
>> efl::ui::Spin::min_reached_event::description()’:
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:672:16: error:
>> ‘EFL_UI_SPIN_EVENT_MIN_REACHED’ was not declared in this scope
>>{ return EFL_UI_SPIN_EVENT_MIN_REACHED; }
>> ^
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:672:16: note: suggested
>> alternative: ‘ELM_SPINNER_EVENT_MIN_REACHED’
>>{ return EFL_UI_SPIN_EVENT_MIN_REACHED; }
>> ^
>> ELM_SPINNER_EVENT_MIN_REACHED
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
>> ‘static const Efl_Event_Description*
>> efl::ui::Spin::max_reached_event::description()’:
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:678:16: error:
>> ‘EFL_UI_SPIN_EVENT_MAX_REACHED’ was not declared in this scope
>>{ return EFL_UI_SPIN_EVENT_MAX_REACHED; }
>> ^
>> ../../../src/lib/elementary/efl_ui_spin.eo.hh:678:16: note: suggested
>> alternative:

Re: [E-devel] [EGIT] [core/efl] master 01/01: efl_ui_spin: Add new spin and spin_button widgets

2017-12-04 Thread Jean-Philippe André 
Does this still happen? I can't reproduce this problem. Unless someone
fixed it?

On Fri, Dec 1, 2017 at 7:41 PM, Stefan Schmidt 
wrote:

> Hello.
>
>
> On 11/27/2017 11:55 AM, Woochan Lee wrote:
> > jaehyun pushed a commit to branch master.
> >
> > http://git.enlightenment.org/core/efl.git/commit/?id=
> eefcb49419af9d0057ba4c03e6c9009a1265e31e
> >
> > commit eefcb49419af9d0057ba4c03e6c9009a1265e31e
> > Author: Woochan Lee 
> > Date:   Mon Nov 20 19:12:49 2017 +0900
> >
> > efl_ui_spin: Add new spin and spin_button widgets
> >
> > Summary:
> > https://phab.enlightenment.org/T5900
> >
> > Creating base class(efl_ui_spin) to support various shape of spinner.
> >
> > Added button interaction widget efl_ui_spin_button inherited from
> efl_ui_spin.
> >
> > Test Plan: Add tests in elementary_test.
> >
> > Reviewers: Jaehyun_Cho, woohyun, jpeg, singh.amitesh
> >
> > Subscribers: jenkins, id213sin, cedric, jpeg
> >
> > Differential Revision: https://phab.enlightenment.org/D5424
> >
>
> Since this new widget I get compile error when building the examples.
> My guess is that you either did not try to compile the examples or
> disabled the C++ bindings. Please have a look to get this fixed.
>
>  CXX  bg_cxx_example_01.o
>   CXX  bg_cxx_example_02.o
>   CXX  button_cxx_example_00.o
>   CXX  box_cxx_example_02.o
> In file included from ../../../src/lib/elementary/Elementary.eo.hh:69:0,
>  from ../../../src/lib/elementary/Elementary.hh:24,
>  from box_cxx_example_02.cc:3:
> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
> ‘static const Efl_Class* eo_cxx::efl::ui::Spin::_eo_class()’:
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:576:14: error:
> ‘EFL_UI_SPIN_CLASS’ was not declared in this scope
>return EFL_UI_SPIN_CLASS;
>   ^
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:576:14: note: suggested
> alternative: ‘EFL_UI_WIN_CLASS’
>return EFL_UI_SPIN_CLASS;
>   ^
>   EFL_UI_WIN_CLASS
> In file included from ../../../src/lib/elementary/Elementary.eo.hh:69:0,
>  from ../../../src/lib/elementary/Elementary.hh:24,
>  from box_cxx_example_02.cc:3:
> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
> ‘static const Efl_Class* efl::ui::Spin::_eo_class()’:
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:660:14: error:
> ‘EFL_UI_SPIN_CLASS’ was not declared in this scope
>return EFL_UI_SPIN_CLASS;
>   ^
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:660:14: note: suggested
> alternative: ‘EFL_UI_WIN_CLASS’
>return EFL_UI_SPIN_CLASS;
>   ^
>   EFL_UI_WIN_CLASS
> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
> ‘static const Efl_Event_Description*
> efl::ui::Spin::changed_event::description()’:
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:666:16: error:
> ‘EFL_UI_SPIN_EVENT_CHANGED’ was not declared in this scope
>{ return EFL_UI_SPIN_EVENT_CHANGED; }
> ^
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:666:16: note: suggested
> alternative: ‘EFL_UI_RADIO_EVENT_CHANGED’
>{ return EFL_UI_SPIN_EVENT_CHANGED; }
> ^
> EFL_UI_RADIO_EVENT_CHANGED
> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
> ‘static const Efl_Event_Description*
> efl::ui::Spin::min_reached_event::description()’:
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:672:16: error:
> ‘EFL_UI_SPIN_EVENT_MIN_REACHED’ was not declared in this scope
>{ return EFL_UI_SPIN_EVENT_MIN_REACHED; }
> ^
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:672:16: note: suggested
> alternative: ‘ELM_SPINNER_EVENT_MIN_REACHED’
>{ return EFL_UI_SPIN_EVENT_MIN_REACHED; }
> ^
> ELM_SPINNER_EVENT_MIN_REACHED
> ../../../src/lib/elementary/efl_ui_spin.eo.hh: In static member function
> ‘static const Efl_Event_Description*
> efl::ui::Spin::max_reached_event::description()’:
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:678:16: error:
> ‘EFL_UI_SPIN_EVENT_MAX_REACHED’ was not declared in this scope
>{ return EFL_UI_SPIN_EVENT_MAX_REACHED; }
> ^
> ../../../src/lib/elementary/efl_ui_spin.eo.hh:678:16: note: suggested
> alternative: ‘ELM_SPINNER_EVENT_MAX_REACHED’
>{ return EFL_UI_SPIN_EVENT_MAX_REACHED; }
> ^
> ELM_SPINNER_EVENT_MAX_REACHED
> make[2]: *** [Makefile:5442: box_cxx_example_02.o] Error 1
> make[2]: *** Waiting for unfinished jobs
> In file included from ../../../src/lib/elementary/Elementary.eo.hh:69:0,
>

Re: [E-devel] [EGIT] [core/enlightenment] master 01/01: music-control - install properly with meson build with icon

2017-12-04 Thread Stefan Schmidt 
Hello.


On 12/03/2017 02:07 PM, Carsten Haitzler wrote:
> On Sat, 2 Dec 2017 00:10:11 +0100 marcel-hollerb...@t-online.de said:
>
>> Hello,
>>
>> so it turned out that this is a ninja bug.
>>
>> Ninja has some sort of recompactination if the number of entries in the
>> .ninja_log and .ninja_deps files are getting too big, then it will cut
>> off a few, write that into a temp file, and rename that temp file later
>> to .ninja_log or .ninja_deps, if you ran exactly this time ninja as root
>> it will place .ninja_log and .ninja_deps as root owned files in the
>> directory instead of maintaining the old gid / uid of the file.
> I'm amazed it took us to discover this and you to fix it... ninja isn't 
> exactly
> THAT new... :) is it that no one does regular "build as user, install as root"
> when using ninja? like this is the regular workflow with make like since...
> dinosaurs roamed the earth.

There was a report on cmake with ninja on this already:
https://github.com/ninja-build/ninja/issues/1302

But it took Marcel to actually take a stab at it to get it fixed. :)
That being said the bug fix is bot yet merged in ninja, hopefully soon.

regards
Stefan Schmidt

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Re: [E-devel] [EGIT] [core/efl] master 03/05: efl: Introduce interface Efl.Dup

2017-12-04 Thread Jean-Philippe André 
On Sun, Dec 3, 2017 at 3:45 AM, Andrew Williams 
wrote:

> Is there anyway we could use a more descriptive name? It just seems
> unnecessarily short.
>

Absolutely. It didn't "think", and only changed the name from the method
"dup".
Cedric mentioned that to me and I think we'll rename to duplicate or
cloneable.


> Maybe that’s just me.
> Andy
> On Fri, 1 Dec 2017 at 18:50, Davide Andreoli 
> wrote:
>
> > 2017-12-01 3:12 GMT+01:00 Jean-Philippe André :
> >
> > > On Fri, Dec 1, 2017 at 3:49 AM, Davide Andreoli <
> d...@gurumeditation.it>
> > > wrote:
> > >
> > > > 2017-11-30 3:36 GMT+01:00 Jean-Philippe ANDRÉ :
> > > >
> > > > > jpeg pushed a commit to branch master.
> > > > >
> > > > > http://git.enlightenment.org/core/efl.git/commit/?id=
> > > > > bd5b76508b0b3bdc5d92f5f7db9741c100d47d3c
> > > > >
> > > > > commit bd5b76508b0b3bdc5d92f5f7db9741c100d47d3c
> > > > > Author: Jean-Philippe Andre 
> > > > > Date:   Wed Nov 29 20:03:16 2017 +0900
> > > > >
> > > > > efl: Introduce interface Efl.Dup
> > > > >
> > > > > A few classes allow their objects to be duplicated, so they
> > should
> > > > all
> > > > > use the same interface.
> > > > >
> > > > > Also, rename VG's dup to copy_from as it's not conforming to
> the
> > > > > definition of dup.
> > > > >
> > > >
> > > > Is'nt the last rename (vg_dup) an abi break ?
> > > >
> > > > python-efl apps now crash like this:
> > > > Traceback (most recent call last):
> > > >   File "/usr/bin/epymc", line 5, in 
> > > > from epymc.main import start_epymc
> > > >   File "/usr/lib/python3.6/site-packages/epymc/main.py", line 32, in
> > > > 
> > > > from efl import edje
> > > > ImportError: /usr/local/lib/libedje.so.1: undefined symbol:
> > > > evas_vg_node_dup
> > > >
> > > > A python-efl rebuild fixed the issue, this is why I think it's an abi
> > > > break.
> > > >
> > > > note that the bindings do not use/expose evas_vg in any way
> > > >
> > >
> > > I was under the impression that Evas VG was still "beta".
> > > In fact I can see EFL_BETA_API_SUPPORT.
> > >
> > > Could you double-check on your side what's happening?
> > > Where is this symbol used?
> > >
> >
> > Probably the symbol is used inside edje. PythonEFL is built with
> > EFL_BETA_API_SUPPORT on, and I think this is the source of
> > the issue
> >
> >
> > >
> > > TIA,
> > >
> > >
> > > >
> > > >
> > > >
> > > > > ---
> > > > >  src/Makefile_Efl.am   |  1 +
> > > > >  src/bin/elementary/test_events.c  | 10 +-
> > > > >  src/lib/edje/edje_calc.c  |  2 +-
> > > > >  src/lib/efl/Efl.h |  1 +
> > > > >  src/lib/efl/interfaces/efl_dup.eo | 17
> +
> > > > >  src/lib/efl/interfaces/efl_gfx_path.c |  4 ++--
> > > > >  src/lib/efl/interfaces/efl_gfx_path.eo|  3 ++-
> > > > >  src/lib/efl/interfaces/efl_gfx_shape.c| 12 +++-
> > > > >  src/lib/efl/interfaces/efl_gfx_shape.eo   | 12 +++-
> > > > >  src/lib/efl/interfaces/efl_interfaces_main.c  |  1 +
> > > > >  src/lib/evas/canvas/efl_canvas_vg.c   |  2 +-
> > > > >  src/lib/evas/canvas/efl_input_event.eo| 13 +
> > > > >  src/lib/evas/canvas/efl_input_focus.c |  2 +-
> > > > >  src/lib/evas/canvas/efl_input_focus.eo| 10 +-
> > > > >  src/lib/evas/canvas/efl_input_hold.c  |  2 +-
> > > > >  src/lib/evas/canvas/efl_input_hold.eo | 10 +-
> > > > >  src/lib/evas/canvas/efl_input_key.c   |  2 +-
> > > > >  src/lib/evas/canvas/efl_input_key.eo  | 10 +-
> > > > >  src/lib/evas/canvas/efl_input_pointer.c   |  2 +-
> > > > >  src/lib/evas/canvas/efl_input_pointer.eo  | 10 +-
> > > > >  src/lib/evas/canvas/efl_vg.eo |  7 ++-
> > > > >  src/lib/evas/canvas/efl_vg_container.eo   |  2 +-
> > > > >  src/lib/evas/canvas/efl_vg_gradient.eo|  2 +-
> > > > >  src/lib/evas/canvas/efl_vg_gradient_linear.eo |  2 +-
> > > > >  src/lib/evas/canvas/efl_vg_gradient_radial.eo |  2 +-
> > > > >  src/lib/evas/canvas/efl_vg_shape.eo   |  2 +-
> > > > >  src/lib/evas/canvas/evas_device.c |  2 +-
> > > > >  src/lib/evas/canvas/evas_events.c | 22
> > > > +++---
> > > > >  src/lib/evas/canvas/evas_vg_container.c   |  6 +++---
> > > > >  src/lib/evas/canvas/evas_vg_gradient.c|  4 ++--
> > > > >  src/lib/evas/canvas/evas_vg_gradient_linear.c |  4 ++--
> > > > >  src/lib/evas/canvas/evas_vg_gradient_radial.c |  4 ++--
> > > > >  src/lib/evas/canvas/evas_vg_node.c|  4 ++--
> > > > >  src/lib/evas/canvas/evas_vg_shape.c   | 16
> 
> > > > >  src/lib/evas/vg/evas_vg_cache.c   |  2 +-
> > > > >  35 files changed, 121 insertions(+), 86 deletions(-)
> > > > >
> > > > >