Re: [VOTE] Release Apache Avro 1.8.2 RC1

[Sean Timm]

Suraj, Ryan,

Can you please review AVRO-1957 for inclusion in the RC? It is a fairly
simple bug fix.

Thanks,
Sean

On Tue, Mar 28, 2017 at 4:44 PM, Suraj Acharya  wrote:

> Hi,
> If the decision was to continue with the problem, and no one has any
> objection I will try to build a RC sometime this week.
>
> Hope that is cool with everyone.
>
> Suraj
>
> On Thu, Nov 10, 2016 at 10:48 AM, Ryan Blue 
> wrote:
>
> > Thanks, Niels. I think it's fine to continue with this problem in the RC
> so
> > I'm still happy voting +1. Lets plan on getting a fix for this into the
> > next RC, since this vote failed for other reasons.
> >
> > rb
> >
> > On Thu, Nov 10, 2016 at 8:18 AM, Niels Basjes  wrote:
> >
> > > Ryan,
> > >
> > > When you fix this build problem I vote +1 again.
> > > Thanks.
> > >
> > > Niels
> > >
> > > On Thu, Nov 10, 2016 at 5:04 PM, Ryan Blue 
> > > wrote:
> > >
> > > > The C# issue was fixed by AVRO-1626 [1], which had to be reverted for
> > the
> > > > 1.8.2 RC because it caused build failures in docker. I reopened the
> > issue
> > > > so we can fix it for next release. Either way, the tests pass in the
> > > common
> > > > environment and I would rather not fail an RC for something like
> this.
> > > >
> > > > [1]: https://issues.apache.org/jira/browse/AVRO-1626
> > > >
> > > > On Thu, Nov 10, 2016 at 7:17 AM, Niels Basjes 
> wrote:
> > > >
> > > > > Guys,
> > > > >
> > > > > Please have a look at this idea: https://github.com/apache/
> > > avro/pull/153
> > > > > If you agree/disagree please go ahead and change/fix/commit it.
> > > > > I'll be at the Apache Con BigData in sevilla next week so I wil
> > > probably
> > > > be
> > > > > rather busy.
> > > > >
> > > > > Oh and yes, this also means I'm changing my stance on Avro 1.8.2
> RC1
> > > to :
> > > > > -1
> > > > > This RC1 is not good enough due to this issue.
> > > > >
> > > > > Niels Basjes
> > > > >
> > > > > On Thu, Nov 10, 2016 at 1:59 PM, Niels Basjes 
> > wrote:
> > > > >
> > > > > > @Simon I find it strange you say that the docker is 'leaking'
> > > something
> > > > > so
> > > > > > I did some testing.
> > > > > > I ran the tests on my system using docker and everything worked.
> > > > > > Then I remove all docker containers and images related to the
> avro
> > > > build
> > > > > > environment and ran it again.
> > > > > > The second time indeed it failed
> > > > > >
> > > > > > My best guess right now is that
> > > > > > 1) during the creation of the docker image we do and update of
> the
> > > base
> > > > > > system and install all the tools.
> > > > > > 2) Upstream something relevant to us changed.
> > > > > >
> > > > > > People (like me) who have and existing image on their system the
> > > > 'update'
> > > > > > of the OS is not done because the local image was built with the
> > > > > > instructions that are in the dockerfile.
> > > > > > So "New" docker images are different because the base OS has the
> > > > updates
> > > > > > installed from a later point in time.
> > > > > >
> > > > > > I created https://issues.apache.org/jira/browse/AVRO-1956
> > > > > > Working on a fix.
> > > > > >
> > > > > > Niels
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Tue, Nov 8, 2016 at 10:52 PM, Simon Woodford <
> > > > simonwoodf...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > >> -1 from me. C# tests fail to run. The source of the problem is
> as
> > > > > follows:
> > > > > >>
> > > > > >> Prior to this tag, the lang/csharp/build.sh file contained the
> > test
> > > > > line:
> > > > > >> nunit-console --framework=4.0 Avro.nunit
> > > > > >>
> > > > > >> From discussion with @jcustenborder, it seems like the C# tests
> > > won't
> > > > > run
> > > > > >> on a Mac if we keep the --framework=4.0 in this line; removing
> it
> > > (as
> > > > > has
> > > > > >> been done for 1.8.2) makes the tests run. But removing it makes
> > the
> > > > > tests
> > > > > >> fail on my system (CentOS 7). This suggests that something is
> > > missing
> > > > > from
> > > > > >> the docker setup and is being picked up from the host computer,
> > but
> > > I
> > > > > >> haven't had a chance to investigate.
> > > > > >>
> > > > > >> Given that it's a choice between it passing for me or passing on
> > all
> > > > > Macs
> > > > > >> everywhere, go ahead and release. I'll chase this up for the
> 1.8.3
> > > > > >> release.
> > > > > >> All tests other than the C# pass when running build.sh test from
> > > > docker.
> > > > > >>
> > > > > >> Simon
> > > > > >>
> > > > > >>
> > > > > >> On Sun, Nov 6, 2016 at 9:59 PM, Ryan Blue 
> > wrote:
> > > > > >>
> > > > > >> > Hi everyone,
> > > > > >> >
> > > > > >> > I propose the following RC to be released as official Apache
> > Avro
> > > > > 1.8.2
> > > > > >> > release.
> > > > > >> >
> > > > > >> > The commit id is 

Re: [VOTE] Release Apache Avro 1.8.2 RC1

[Suraj Acharya]

Hi,
If the decision was to continue with the problem, and no one has any
objection I will try to build a RC sometime this week.

Hope that is cool with everyone.

Suraj

On Thu, Nov 10, 2016 at 10:48 AM, Ryan Blue 
wrote:

> Thanks, Niels. I think it's fine to continue with this problem in the RC so
> I'm still happy voting +1. Lets plan on getting a fix for this into the
> next RC, since this vote failed for other reasons.
>
> rb
>
> On Thu, Nov 10, 2016 at 8:18 AM, Niels Basjes  wrote:
>
> > Ryan,
> >
> > When you fix this build problem I vote +1 again.
> > Thanks.
> >
> > Niels
> >
> > On Thu, Nov 10, 2016 at 5:04 PM, Ryan Blue 
> > wrote:
> >
> > > The C# issue was fixed by AVRO-1626 [1], which had to be reverted for
> the
> > > 1.8.2 RC because it caused build failures in docker. I reopened the
> issue
> > > so we can fix it for next release. Either way, the tests pass in the
> > common
> > > environment and I would rather not fail an RC for something like this.
> > >
> > > [1]: https://issues.apache.org/jira/browse/AVRO-1626
> > >
> > > On Thu, Nov 10, 2016 at 7:17 AM, Niels Basjes  wrote:
> > >
> > > > Guys,
> > > >
> > > > Please have a look at this idea: https://github.com/apache/
> > avro/pull/153
> > > > If you agree/disagree please go ahead and change/fix/commit it.
> > > > I'll be at the Apache Con BigData in sevilla next week so I wil
> > probably
> > > be
> > > > rather busy.
> > > >
> > > > Oh and yes, this also means I'm changing my stance on Avro 1.8.2 RC1
> > to :
> > > > -1
> > > > This RC1 is not good enough due to this issue.
> > > >
> > > > Niels Basjes
> > > >
> > > > On Thu, Nov 10, 2016 at 1:59 PM, Niels Basjes 
> wrote:
> > > >
> > > > > @Simon I find it strange you say that the docker is 'leaking'
> > something
> > > > so
> > > > > I did some testing.
> > > > > I ran the tests on my system using docker and everything worked.
> > > > > Then I remove all docker containers and images related to the avro
> > > build
> > > > > environment and ran it again.
> > > > > The second time indeed it failed
> > > > >
> > > > > My best guess right now is that
> > > > > 1) during the creation of the docker image we do and update of the
> > base
> > > > > system and install all the tools.
> > > > > 2) Upstream something relevant to us changed.
> > > > >
> > > > > People (like me) who have and existing image on their system the
> > > 'update'
> > > > > of the OS is not done because the local image was built with the
> > > > > instructions that are in the dockerfile.
> > > > > So "New" docker images are different because the base OS has the
> > > updates
> > > > > installed from a later point in time.
> > > > >
> > > > > I created https://issues.apache.org/jira/browse/AVRO-1956
> > > > > Working on a fix.
> > > > >
> > > > > Niels
> > > > >
> > > > >
> > > > >
> > > > > On Tue, Nov 8, 2016 at 10:52 PM, Simon Woodford <
> > > simonwoodf...@gmail.com
> > > > >
> > > > > wrote:
> > > > >
> > > > >> -1 from me. C# tests fail to run. The source of the problem is as
> > > > follows:
> > > > >>
> > > > >> Prior to this tag, the lang/csharp/build.sh file contained the
> test
> > > > line:
> > > > >> nunit-console --framework=4.0 Avro.nunit
> > > > >>
> > > > >> From discussion with @jcustenborder, it seems like the C# tests
> > won't
> > > > run
> > > > >> on a Mac if we keep the --framework=4.0 in this line; removing it
> > (as
> > > > has
> > > > >> been done for 1.8.2) makes the tests run. But removing it makes
> the
> > > > tests
> > > > >> fail on my system (CentOS 7). This suggests that something is
> > missing
> > > > from
> > > > >> the docker setup and is being picked up from the host computer,
> but
> > I
> > > > >> haven't had a chance to investigate.
> > > > >>
> > > > >> Given that it's a choice between it passing for me or passing on
> all
> > > > Macs
> > > > >> everywhere, go ahead and release. I'll chase this up for the 1.8.3
> > > > >> release.
> > > > >> All tests other than the C# pass when running build.sh test from
> > > docker.
> > > > >>
> > > > >> Simon
> > > > >>
> > > > >>
> > > > >> On Sun, Nov 6, 2016 at 9:59 PM, Ryan Blue 
> wrote:
> > > > >>
> > > > >> > Hi everyone,
> > > > >> >
> > > > >> > I propose the following RC to be released as official Apache
> Avro
> > > > 1.8.2
> > > > >> > release.
> > > > >> >
> > > > >> > The commit id is 7ec35ea24ff0270586a26afbc6f6f530d272d1f7
> > > > >> > * This corresponds to the tag: release-1.8.2-rc1
> > > > >> > * https://github.com/apache/avro/tree/7ec35ea2
> > > > >> > *
> > > > >> > https://git-wip-us.apache.org/repos/asf/projects/repo?p=
> > > > >> > avro.git=commit=7ec35ea2
> > > > >> >
> > > > >> > The release tarball, signature, and checksums are here:
> > > > >> > * https://dist.apache.org/repos/dist/dev/avro/avro-1.8.2-rc1/
> > > > >> >
> > > > >> > You can find the KEYS file here:
> > > > >> > * 

Regarding release date of AVRO version 1.8.2

[rahul-zb.agarwal]

Hi Team,

We are looking out for a Decimal support in avro, which seems to be available 
in 1.8.2 as per
https://issues.apache.org/jira/browse/AVRO-1847

Could you please confirm this and release date for the same

Thanks in Advance.

Thanks & Regards
Rahul Agrawal

Visit our website at http://www.ubs.com 

This message contains confidential information and is intended only 
for the individual named. If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail. Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system. 

E-mails are not encrypted and cannot be guaranteed to be secure or 
error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses. The sender 
therefore does not accept liability for any errors or omissions in the 
contents of this message which arise as a result of e-mail transmission. 
If verification is required please request a hard-copy version. This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities 
or related financial instruments. 

UBS Limited is a company limited by shares incorporated in the United 
Kingdom registered in England and Wales with number 2035362.  
Registered Office: 5 Broadgate, London EC2M 2QS
UBS Limited is authorised by the Prudential Regulation Authority 
and regulated by the Financial Conduct Authority and the Prudential 
Regulation Authority.

UBS AG is a public company incorporated with limited liability in
Switzerland domiciled in the Canton of Basel-City and the Canton of
Zurich respectively registered at the Commercial Registry offices in
those Cantons with new Identification No: CHE-101.329.561 as from 18
December 2013 (and prior to 18 December 2013 with Identification
No: CH-270.3.004.646-4) and having respective head offices at
Aeschenvorstadt 1, 4051 Basel and Bahnhofstrasse 45, 8001 Zurich,
Switzerland and is authorised and regulated by the Financial Market
Supervisory Authority in Switzerland.  Registered in the United
Kingdom as a foreign company with No: FC021146 and having a UK
Establishment registered at Companies House, Cardiff, with
No: BR 004507.  The principal office of UK Establishment: 
5 Broadgate, London EC2M 2QS. In the United Kingdom, UBS AG is 
authorised by the Prudential Regulation Authority and subject to 
regulation by the Financial Conduct Authority and limited regulation 
by the Prudential Regulation Authority.  Details about the extent 
of our regulation by the Prudential Regulation Authority are 
available from us on request.

UBS reserves the right to retain all messages. Messages are protected 
and accessed only in legally justified cases. 

[jira] [Commented] (AVRO-1710) sync() returns wrong value if DataFileWriter.appendTo() is used to initialize the DataFileWriter

[Cliff Sun (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945587#comment-15945587
 ] 

Cliff Sun commented on AVRO-1710:
-

I've seen this 'issue' in the 1.8.1 too. Since there hasn't been any activity 
on it in a while I'm not sure if the developers see this as a bug. If not, I do 
think the documentation should be updated to mention that it returns a relative 
position (rather than absolute). 
The good thing is that the position returned by sync() simply just returns the 
relative byte position in the file. If you have access to the file itself and 
you've used appendTo (to append to an existing Avro file) you can just do a 
combination of file.length() + position (the value returned by sync) to get the 
absolute position. 
We use this for indexing so we can do fast lookups on the data file later on.

> sync() returns wrong value if DataFileWriter.appendTo() is used to initialize 
> the DataFileWriter
> 
>
> Key: AVRO-1710
> URL: https://issues.apache.org/jira/browse/AVRO-1710
> Project: Avro
>  Issue Type: Bug
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Christopher Ng
>  Labels: starter
>
> If you append to an existing file using DataFileWriter.appendTo(), sync() 
> returns the wrong values as it doesn't take into account the position in the 
> existing file.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (AVRO-1684) Add date, time, and timestamp to specific object model classes

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AVRO-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey resolved AVRO-1684.
---
  Resolution: Fixed
Hadoop Flags: Incompatible change
Release Note: This change causes the IDL parser to treat "date", "time", 
and "timestamp" as reserved words for field names. See AVRO-1924 for more 
details.

> Add date, time, and timestamp to specific object model classes
> --
>
> Key: AVRO-1684
> URL: https://issues.apache.org/jira/browse/AVRO-1684
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Ryan Blue
>Assignee: Ryan Blue
> Fix For: 1.8.1
>
> Attachments: AVRO-1684.1.patch
>
>
> AVRO-1672 adds conversions for date, time, and timestamp. These should be 
> available to specific classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AVRO-1684) Add date, time, and timestamp to specific object model classes

[Sean Busbey (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945504#comment-15945504
 ] 

Sean Busbey commented on AVRO-1684:
---

I haven't dug in enough yet to figure that part out.

> Add date, time, and timestamp to specific object model classes
> --
>
> Key: AVRO-1684
> URL: https://issues.apache.org/jira/browse/AVRO-1684
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Ryan Blue
>Assignee: Ryan Blue
> Fix For: 1.8.1
>
> Attachments: AVRO-1684.1.patch
>
>
> AVRO-1672 adds conversions for date, time, and timestamp. These should be 
> available to specific classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Reopened] (AVRO-1684) Add date, time, and timestamp to specific object model classes

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AVRO-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey reopened AVRO-1684:
---

> Add date, time, and timestamp to specific object model classes
> --
>
> Key: AVRO-1684
> URL: https://issues.apache.org/jira/browse/AVRO-1684
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Ryan Blue
>Assignee: Ryan Blue
> Fix For: 1.8.1
>
> Attachments: AVRO-1684.1.patch
>
>
> AVRO-1672 adds conversions for date, time, and timestamp. These should be 
> available to specific classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AVRO-1684) Add date, time, and timestamp to specific object model classes

[Ryan Blue (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945493#comment-15945493
 ] 

Ryan Blue commented on AVRO-1684:
-

We should definitely mark 1.8.1 as incompatible. Is it possible to fix the 
parser for future releases?

> Add date, time, and timestamp to specific object model classes
> --
>
> Key: AVRO-1684
> URL: https://issues.apache.org/jira/browse/AVRO-1684
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Ryan Blue
>Assignee: Ryan Blue
> Fix For: 1.8.1
>
> Attachments: AVRO-1684.1.patch
>
>
> AVRO-1672 adds conversions for date, time, and timestamp. These should be 
> available to specific classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (AVRO-1684) Add date, time, and timestamp to specific object model classes

[Sean Busbey (JIRA)]

[ 
https://issues.apache.org/jira/browse/AVRO-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945468#comment-15945468
 ] 

Sean Busbey commented on AVRO-1684:
---

In light of AVRO-1924, should we flag this as incompatible?

> Add date, time, and timestamp to specific object model classes
> --
>
> Key: AVRO-1684
> URL: https://issues.apache.org/jira/browse/AVRO-1684
> Project: Avro
>  Issue Type: New Feature
>  Components: java
>Affects Versions: 1.7.7
>Reporter: Ryan Blue
>Assignee: Ryan Blue
> Fix For: 1.8.1
>
> Attachments: AVRO-1684.1.patch
>
>
> AVRO-1672 adds conversions for date, time, and timestamp. These should be 
> available to specific classes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Test Failure in Ruby - AVRO-1.7

[Sean Busbey]

Okay, I filed AVRO-2013 and I upgraded AVRO-1516 to critical.

On Tue, Mar 28, 2017 at 9:42 AM, Sean Busbey  wrote:
> Okay, I tried over the weekend to get a Ruby 1.8 install on my OS X
> 10.11 laptop and failed. So I'm definitely not going to try to get
> Ruby 1.8 support working in 1.7 again for this release cycle.
>
> With Ruby 1.9.3 I get 4 errors, three of which look like your
> JSON::GeneratorError. I don't have one that looks like your last
> issue, which is AVRO-1516.
>
> I'll file a jira for the 1.9.3 problems. What do folks think is a
> reasonable amount of time for us to hold the 1.7.8 RCs while trying to
> get these issues closed out?
>
> On Thu, Mar 23, 2017 at 3:05 PM, Sean Busbey  wrote:
>> Ruby 1.8 not working on branch-1.7 might be something I want to fix,
>> since I think that's the version we rely on in HBase (and we rely on
>> Ruby 1.8).
>>
>> On Thu, Mar 23, 2017 at 3:04 PM, Sean Busbey  wrote:
>>> Short version: we don't sufficiently document what version(s) of Ruby
>>> we expect to work.
>>>
>>> We have AVRO-1559 for dropping Ruby 1.8 support, but it's open. There
>>> are several tickets referenced from there that mention not working
>>> with Ruby 1.8. (AVRO-1694, AVRO-1783). AVRO-1775 mentions having Ruby
>>> 2.2 working for branch-1.8, but AVRO-1516 shows 2.0+ broken on 1.7+.
>>>
>>> So I think we want to work for Ruby 1.9 - 2.2, but 2.0+ is broken. Can
>>> you test in Ruby 1.9?
>>>
>>>
>>>
>>> On Thu, Mar 23, 2017 at 11:32 AM, Sean Busbey  wrote:
 Hurm. I didn't think our Avro stuff in the 1.7 branch worked with Ruby 2.1.
 lemme see if we doc this anywhere.

 On Thu, Mar 23, 2017 at 11:20 AM, suraj acharya  
 wrote:
> This is what I am using.
> ruby 2.1.5p273 (2014-11-13) [x86_64-linux-gnu]
>
> Hope that helps.
>
> S
>
> -Suraj Acharya
>
> On Thu, Mar 23, 2017 at 8:51 AM, Sean Busbey  wrote:
>
>> What's your Ruby environment?
>>
>> On Wed, Mar 22, 2017 at 5:34 PM, suraj acharya 
>> wrote:
>> > Hi,
>> >
>> > I was trying to make a release for 1.7 and I am seeing 3 tests fail in
>> ruby.
>> > I was wondering if someone in the community can help resolve these 
>> > issues
>> > so we can go ahead and work on getting a release.
>> >
>> > I have attached a sample of the error.
>> >
>> >   1) Error:
>> > TestFingerprints#test_md5_fingerprint:
>> > JSON::GeneratorError: only generation of JSON objects or arrays allowed
>> >
>> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
>> json/common.rb:224:in
>> > `generate'
>> >
>> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
>> json/common.rb:224:in
>> > `generate'
>> >
>> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
>> json/common.rb:394:in
>> > `dump'
>> > 
>> > /home/sacharya/avro/lang/ruby/lib/avro/schema_normalization.rb:28:in
>> > `to_parsing_form'
>> > 
>> > /home/sacharya/avro/lang/ruby/lib/avro/schema_normalization.rb:20:in
>> > `to_parsing_form'
>> > /home/sacharya/avro/lang/ruby/lib/avro/schema.rb:143:in
>> > `md5_fingerprint'
>> > /home/sacharya/avro/lang/ruby/test/test_fingerprints.rb:26:in
>> > `test_md5_fingerprint'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1265:in `run'
>> > /usr/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `map'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:661:in `each'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run'
>> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:27:in `run'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:780:in `run'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in
>> autorun'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:33:in `run_once'
>> > /usr/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun'
>> >
>> > [ 8/52] TestFingerprints#test_sha256_fingerprint = 0.00 s
>> >   2) Error:
>> > TestFingerprints#test_sha256_fingerprint:
>> > JSON::GeneratorError: only generation of JSON objects or arrays 

[jira] [Created] (AVRO-2013) Unit test failure in Ruby 1.9

[Sean Busbey (JIRA)]

Sean Busbey created AVRO-2013:
-

 Summary: Unit test failure in Ruby 1.9
 Key: AVRO-2013
 URL: https://issues.apache.org/jira/browse/AVRO-2013
 Project: Avro
  Issue Type: Bug
  Components: ruby
Affects Versions: 1.7.8
Reporter: Sean Busbey
Priority: Critical
 Fix For: 1.7.8


{code}
  1) Error:
test_md5_fingerprint(TestFingerprints):
JSON::GeneratorError: only generation of JSON objects or arrays allowed

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:224:in
 `generate'

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:224:in
 `generate'

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:394:in
 `dump'

/Users/busbey/projects/avro/lang/ruby/lib/avro/schema_normalization.rb:28:in 
`to_parsing_form'

/Users/busbey/projects/avro/lang/ruby/lib/avro/schema_normalization.rb:20:in 
`to_parsing_form'
/Users/busbey/projects/avro/lang/ruby/lib/avro/schema.rb:143:in 
`md5_fingerprint'
/Users/busbey/projects/avro/lang/ruby/test/test_fingerprints.rb:26:in 
`test_md5_fingerprint'

  2) Error:
test_sha256_fingerprint(TestFingerprints):
JSON::GeneratorError: only generation of JSON objects or arrays allowed

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:224:in
 `generate'

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:224:in
 `generate'

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:394:in
 `dump'

/Users/busbey/projects/avro/lang/ruby/lib/avro/schema_normalization.rb:28:in 
`to_parsing_form'

/Users/busbey/projects/avro/lang/ruby/lib/avro/schema_normalization.rb:20:in 
`to_parsing_form'
/Users/busbey/projects/avro/lang/ruby/lib/avro/schema.rb:149:in 
`sha256_fingerprint'
/Users/busbey/projects/avro/lang/ruby/test/test_fingerprints.rb:35:in 
`test_sha256_fingerprint'

  3) Error:
test_primitives(TestSchemaNormalization):
JSON::GeneratorError: only generation of JSON objects or arrays allowed

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:224:in
 `generate'

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:224:in
 `generate'

/Users/busbey/projects/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/json/common.rb:394:in
 `dump'

/Users/busbey/projects/avro/lang/ruby/lib/avro/schema_normalization.rb:28:in 
`to_parsing_form'

/Users/busbey/projects/avro/lang/ruby/lib/avro/schema_normalization.rb:20:in 
`to_parsing_form'

/Users/busbey/projects/avro/lang/ruby/test/test_schema_normalization.rb:28:in 
`block in test_primitives'

/Users/busbey/projects/avro/lang/ruby/test/test_schema_normalization.rb:23:in 
`each'

/Users/busbey/projects/avro/lang/ruby/test/test_schema_normalization.rb:23:in 
`test_primitives'

  4) Error:
test_shared_dataset(TestSchemaNormalization):
NameError: uninitialized constant CaseFinder::StringScanner
/Users/busbey/projects/avro/lang/ruby/test/case_finder.rb:11:in `initialize'
/Users/busbey/projects/avro/lang/ruby/test/case_finder.rb:7:in `new'
/Users/busbey/projects/avro/lang/ruby/test/case_finder.rb:7:in `cases'

/Users/busbey/projects/avro/lang/ruby/test/test_schema_normalization.rb:166:in 
`test_shared_dataset'

52 tests, 799 assertions, 0 failures, 4 errors, 0 skips

{code}

I'm using 1.9.3 installed via RVM.

{code}
Busbey-MBA:ruby busbey$ rvm version
rvm 1.29.1 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin 
[https://rvm.io/]
Busbey-MBA:ruby busbey$ rvm list

rvm rubies

=> ruby-1.9.3-p551 [ x86_64 ]
 * ruby-2.2.1 [ x86_64 ]

# => - current
# =* - current && default
#  * - default
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Test Failure in Ruby - AVRO-1.7

[Sean Busbey]

Okay, I tried over the weekend to get a Ruby 1.8 install on my OS X
10.11 laptop and failed. So I'm definitely not going to try to get
Ruby 1.8 support working in 1.7 again for this release cycle.

With Ruby 1.9.3 I get 4 errors, three of which look like your
JSON::GeneratorError. I don't have one that looks like your last
issue, which is AVRO-1516.

I'll file a jira for the 1.9.3 problems. What do folks think is a
reasonable amount of time for us to hold the 1.7.8 RCs while trying to
get these issues closed out?

On Thu, Mar 23, 2017 at 3:05 PM, Sean Busbey  wrote:
> Ruby 1.8 not working on branch-1.7 might be something I want to fix,
> since I think that's the version we rely on in HBase (and we rely on
> Ruby 1.8).
>
> On Thu, Mar 23, 2017 at 3:04 PM, Sean Busbey  wrote:
>> Short version: we don't sufficiently document what version(s) of Ruby
>> we expect to work.
>>
>> We have AVRO-1559 for dropping Ruby 1.8 support, but it's open. There
>> are several tickets referenced from there that mention not working
>> with Ruby 1.8. (AVRO-1694, AVRO-1783). AVRO-1775 mentions having Ruby
>> 2.2 working for branch-1.8, but AVRO-1516 shows 2.0+ broken on 1.7+.
>>
>> So I think we want to work for Ruby 1.9 - 2.2, but 2.0+ is broken. Can
>> you test in Ruby 1.9?
>>
>>
>>
>> On Thu, Mar 23, 2017 at 11:32 AM, Sean Busbey  wrote:
>>> Hurm. I didn't think our Avro stuff in the 1.7 branch worked with Ruby 2.1.
>>> lemme see if we doc this anywhere.
>>>
>>> On Thu, Mar 23, 2017 at 11:20 AM, suraj acharya  wrote:
 This is what I am using.
 ruby 2.1.5p273 (2014-11-13) [x86_64-linux-gnu]

 Hope that helps.

 S

 -Suraj Acharya

 On Thu, Mar 23, 2017 at 8:51 AM, Sean Busbey  wrote:

> What's your Ruby environment?
>
> On Wed, Mar 22, 2017 at 5:34 PM, suraj acharya 
> wrote:
> > Hi,
> >
> > I was trying to make a release for 1.7 and I am seeing 3 tests fail in
> ruby.
> > I was wondering if someone in the community can help resolve these 
> > issues
> > so we can go ahead and work on getting a release.
> >
> > I have attached a sample of the error.
> >
> >   1) Error:
> > TestFingerprints#test_md5_fingerprint:
> > JSON::GeneratorError: only generation of JSON objects or arrays allowed
> >
> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
> json/common.rb:224:in
> > `generate'
> >
> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
> json/common.rb:224:in
> > `generate'
> >
> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
> json/common.rb:394:in
> > `dump'
> > /home/sacharya/avro/lang/ruby/lib/avro/schema_normalization.rb:28:in
> > `to_parsing_form'
> > /home/sacharya/avro/lang/ruby/lib/avro/schema_normalization.rb:20:in
> > `to_parsing_form'
> > /home/sacharya/avro/lang/ruby/lib/avro/schema.rb:143:in
> > `md5_fingerprint'
> > /home/sacharya/avro/lang/ruby/test/test_fingerprints.rb:26:in
> > `test_md5_fingerprint'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1265:in `run'
> > /usr/lib/ruby/2.1.0/test/unit/testcase.rb:17:in `run'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:940:in `block in _run_suite'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `map'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:933:in `_run_suite'
> > /usr/lib/ruby/2.1.0/test/unit.rb:663:in `block in _run_suites'
> > /usr/lib/ruby/2.1.0/test/unit.rb:661:in `each'
> > /usr/lib/ruby/2.1.0/test/unit.rb:661:in `_run_suites'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:884:in `_run_anything'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1092:in `run_tests'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1079:in `block in _run'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `each'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1078:in `_run'
> > /usr/lib/ruby/2.1.0/minitest/unit.rb:1066:in `run'
> > /usr/lib/ruby/2.1.0/test/unit.rb:27:in `run'
> > /usr/lib/ruby/2.1.0/test/unit.rb:780:in `run'
> > /usr/lib/ruby/2.1.0/test/unit.rb:372:in `block (2 levels) in
> autorun'
> > /usr/lib/ruby/2.1.0/test/unit.rb:33:in `run_once'
> > /usr/lib/ruby/2.1.0/test/unit.rb:371:in `block in autorun'
> >
> > [ 8/52] TestFingerprints#test_sha256_fingerprint = 0.00 s
> >   2) Error:
> > TestFingerprints#test_sha256_fingerprint:
> > JSON::GeneratorError: only generation of JSON objects or arrays allowed
> >
> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
> json/common.rb:224:in
> > `generate'
> >
> > /home/sacharya/avro/lang/ruby/.gem/gems/json_pure-2.0.3/lib/
> json/common.rb:224:in
> > `generate'
> >
> > 

[jira] [Updated] (AVRO-1516) Unit test failure in Ruby 2.0 and above

[Sean Busbey (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AVRO-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Busbey updated AVRO-1516:
--
Fix Version/s: 1.8.2
   1.9.0
   1.7.8

> Unit test failure in Ruby 2.0 and above
> ---
>
> Key: AVRO-1516
> URL: https://issues.apache.org/jira/browse/AVRO-1516
> Project: Avro
>  Issue Type: Test
>  Components: ruby
>Affects Versions: 1.7.6
>Reporter: Martin Kleppmann
> Fix For: 1.7.8, 1.9.0, 1.8.2
>
>
> The following unit test fails when run with Ruby 2.0 and above:
> {noformat}
> $ bundle exec rake test
> /Users/mkleppma/.rubies/ruby-2.0.0-p195/bin/ruby -I"lib:ext:bin:test" 
> -I"/Users/mkleppma/.gem/ruby/2.0.0/gems/rake-10.3.1/lib" 
> "/Users/mkleppma/.gem/ruby/2.0.0/gems/rake-10.3.1/lib/rake/rake_test_loader.rb"
>  "test/test_datafile.rb" "test/test_help.rb" "test/test_io.rb" 
> "test/test_protocol.rb" "test/test_schema.rb" "test/test_socket_transport.rb"
> Run options:
> # Running tests:
> [30/41] TestIO#test_union = 0.00 s
>   1) Failure:
> test_union(TestIO) 
> [/Users/mkleppma/Applications/avro/lang/ruby/test/test_io.rb:339]:
> <-3372032630846393039> expected but was
> <-3.372032630846393e+18>.
> Finished tests in 0.346139s, 118.4495 tests/s, 2207.2058 assertions/s.
> 41 tests, 764 assertions, 1 failures, 0 errors, 0 skips
> ruby -v: ruby 2.0.0p195 (2013-05-14 revision 40734) [x86_64-darwin12.3.0]
> rake aborted!
> Command failed with status (1): [ruby -I"lib:ext:bin:test" 
> -I"/Users/mkleppma/.gem/ruby/2.0.0/gems/rake-10.3.1/lib" 
> "/Users/mkleppma/.gem/ruby/2.0.0/gems/rake-10.3.1/lib/rake/rake_test_loader.rb"
>  "test/test_datafile.rb" "test/test_help.rb" "test/test_io.rb" 
> "test/test_protocol.rb" "test/test_schema.rb" "test/test_socket_transport.rb" 
> ]
> /Users/mkleppma/.gem/ruby/2.0.0/gems/echoe-4.6.5/lib/echoe.rb:749:in `block 
> in define_tasks'
> Tasks: TOP => test_inner
> (See full trace by running task with --trace)
> {noformat}
> Brief investigation suggests that this isn't a bug in Avro, but just a badly 
> written test. The test is comparing -3372032630846393039 and 
> -3372032630846393000.0, which Ruby 1.9 and below consider to be equal, but 
> Ruby 2.0 and above consider to be non-equal.
> Our tests shouldn't be relying on such edge cases of type coercion.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)