[jira] [Resolved] (AVRO-1926) lang/c++ build.sh doesn't work
[ https://issues.apache.org/jira/browse/AVRO-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Woodford resolved AVRO-1926. -- Resolution: Cannot Reproduce Deleting everything and checking out a fresh version seems to have fixed the issue. > lang/c++ build.sh doesn't work > --- > > Key: AVRO-1926 > URL: https://issues.apache.org/jira/browse/AVRO-1926 > Project: Avro > Issue Type: Bug > Components: c++ >Affects Versions: 1.8.1 > Environment: Centos 7, SELinux, running from Docker container >Reporter: Simon Woodford >Priority: Minor > Fix For: 1.8.3 > > > The lang/c++/build.sh script makes frequent reference to the build directory, > which is empty. Instead, make and all tests should be launched directly from > lang/c++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AVRO-1926) lang/c++ build.sh doesn't work
Simon Woodford created AVRO-1926: Summary: lang/c++ build.sh doesn't work Key: AVRO-1926 URL: https://issues.apache.org/jira/browse/AVRO-1926 Project: Avro Issue Type: Bug Components: c++ Affects Versions: 1.8.1 Environment: Centos 7, SELinux, running from Docker container Reporter: Simon Woodford Priority: Minor Fix For: 1.8.3 The lang/c++/build.sh script makes frequent reference to the build directory, which is empty. Instead, make and all tests should be launched directly from lang/c++. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AVRO-1925) Docker clash with SELinux
Simon Woodford created AVRO-1925: Summary: Docker clash with SELinux Key: AVRO-1925 URL: https://issues.apache.org/jira/browse/AVRO-1925 Project: Avro Issue Type: Bug Components: docker Affects Versions: 1.8.1 Environment: Linux - Centos 7 with SELinux running, avro found in /home/. Reporter: Simon Woodford Priority: Minor Fix For: 1.8.3 When Docker is running in a labelling system like SELinux, it needs to be told to relabel any directories it wants to write to. In build.sh, we tell Docker that it can access /home/USER_NAME, /home/.m2 and /home/.gnupg, but we don't instruct it to relabel them. So if SELinux is running, once in the docker container, you cannot build anything as that involves writing. See e.g. the Volume Labels section in https://docs.docker.com/engine/tutorials/dockervolumes/ for more details. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (AVRO-1626) Missing lang/csharp/src/apache/perf/app.config
[ https://issues.apache.org/jira/browse/AVRO-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15511560#comment-15511560 ] Simon Woodford commented on AVRO-1626: -- Copying the app.config file from src/apache/codegen to src/apache/perf allows this to compile with (apparently) no ill effect. Once I'm convinced that it's the right thing to do, I'll submit a patch > Missing lang/csharp/src/apache/perf/app.config > -- > > Key: AVRO-1626 > URL: https://issues.apache.org/jira/browse/AVRO-1626 > Project: Avro > Issue Type: Bug > Components: csharp >Reporter: Niels Basjes > > This error is output during the build > {code} > Target _CopyAppConfigFile: > /usr/lib/mono/4.5/Microsoft.Common.targets: error : Cannot copy > /home/nbasjes/avro/lang/csharp/src/apache/perf/app.config to > /home/nbasjes/avro/lang/csharp/build/perf/Release/Avro.perf.exe.config, as > the source file doesn't exist. > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (AVRO-1849) C++ printJson fails on record with no fields
Simon Woodford created AVRO-1849: Summary: C++ printJson fails on record with no fields Key: AVRO-1849 URL: https://issues.apache.org/jira/browse/AVRO-1849 Project: Avro Issue Type: Bug Components: c++ Affects Versions: 1.8.0, 1.7.7 Environment: Not relevant Reporter: Simon Woodford Priority: Minor Fix For: 1.8.1 The function NodeRecord::printJson in lang/c++/impl/NodeImpl.cc does not correctly handle a record with no fields. It injects an extra closing curly brace, and the result is invalid JSON. Starting with a schema { "type": "record", "name": "Example", "fields" : [ ] } and parsing it to create a ValidSchema, then calling toJson on the ValidSchema generates { "type": "record", "name": "Example", "fields" : [ } ] } A record with no fields is unusual but we have encountered use cases for it, avro does not invalidate a record with no fields, and I've confirmed that Java, C and C# handle this case correctly. (I have not checked the other supported languages.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)