Re: [GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[Matt Post]

yeah this is really strange. I'm talking about the regression tests, not the 
unit tests. these are in src/test/resources. run for example 
test/bn-en/hiero/test.sh. 3 seconds on master, 18 on JOSHUA-252 (you might have 
to remove "-threads 2")

matt (from my phone)

> On May 26, 2016, at 9:15 PM, lewismc  wrote:
> 
> Github user lewismc commented on the pull request:
> 
>https://github.com/apache/incubator-joshua/pull/12#issuecomment-222037050
> 
>What kind of 'tests' are we talking about here? The only tests which I 
> know of are invoked by running ```mvn clean test```. These execute very 
> quickly by the looks of it however I assume that they cover little or none of 
> the multithreaded functionality you are referring to. 
>Do you have something we could code, profile and see what is taking so 
> long @mjpost  ? Thanks
> 
>One last thing. No I changed absolutely no code. I did however introduce 
> some classes such as the ArpaFile, etc which were required to get the current 
> tests running. 
> 
> 
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
> with INFRA.
> ---

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[lewismc]

Github user lewismc commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222037050
  
What kind of 'tests' are we talking about here? The only tests which I know 
of are invoked by running ```mvn clean test```. These execute very quickly by 
the looks of it however I assume that they cover little or none of the 
multithreaded functionality you are referring to. 
Do you have something we could code, profile and see what is taking so long 
@mjpost  ? Thanks

One last thing. No I changed absolutely no code. I did however introduce 
some classes such as the ArpaFile, etc which were required to get the current 
tests running. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222032586
  
Okay, I just pushed up the changes after merging in master and making some 
other changes to that the tests will run (with manual calls). The code on 
master runs fine, so it must have been something in the 252 or 262 branches. 
I've done some initial work wrapping LOG.debug() calls in checks for 
LOG.isDebugEnabled(), but that didn't seem to help. All my tests were done with 

log4j.rootLogger=OFF, stdout

I may have some more time to look at this tomorrow.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[thammegowda]

Github user thammegowda commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222027825
  
My guess is that `ConcurrentModificationException` occurs when we try to 
loop (eg: for) on a collection and inside the loop the collection is being 
updated (by adding or removing items).
However, based on the exception, I checked 
https://github.com/apache/incubator-joshua/blob/JOSHUA-252/src/main/java/org/apache/joshua/decoder/chart_parser/DotChart.java#L362
there isnt any such code. I suspect Rule.toString().

That line executes only if DEBUG level is enabled! try disabling DEBUG (by 
setting Log4j level to INFO or higher until we find a fix



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222016587
  
Also, multithreading is broken. I randomly (not always) get the following 
error when decoding with more than 1 thread:

```
Exception in thread "Thread-4" java.lang.RuntimeException: Input 1: FATAL 
UNCAUGHT EXCEPTION: null
at 
org.apache.joshua.decoder.Decoder$DecoderThreadRunner.run(Decoder.java:433)
Caused by: java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:901)
at java.util.ArrayList$Itr.next(ArrayList.java:851)
at 
org.apache.joshua.decoder.chart_parser.DotChart.addDotItem(DotChart.java:362)
at 
org.apache.joshua.decoder.chart_parser.DotChart.expandDotCell(DotChart.java:223)
at org.apache.joshua.decoder.chart_parser.Chart.expand(Chart.java:585)
at 
org.apache.joshua.decoder.DecoderThread.translate(DecoderThread.java:141)
at 
org.apache.joshua.decoder.Decoder$DecoderThreadRunner.run(Decoder.java:424)
```



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303101#comment-15303101
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222016079
  
Okay, I have merged. The handful of test cases I checked passed, but there 
is bad news: the decoder is *significantly* slower, like by an order of 
magnitude. Tests that returned instantly before or took just a second or two 
now take 10–20. This is with log levels turned off. Those of you who have 
worked on this branch, do you have any guesses what the problem might be?



> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222013844
  
Okay, cool. It doesn't seem to look for that file automatically, though; if 
I remove the -Dlog4j.configuration, it doesn't find the file you pointed to. So 
I am just having it hard-point to that path.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303077#comment-15303077
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user thammegowda commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222012667
  
@mjpost as you pointed out, you need to edit log4j settings.

The other way is to edit `src/main/resources/log4j.properties`


If you dont want to rebuild the jar after editing the file, you can create 
an updated log4j.properties and  prefix  its path to the class path (so that it 
gets priority over the one inside jar)


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[thammegowda]

Github user thammegowda commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222012667
  
@mjpost as you pointed out, you need to edit log4j settings.

The other way is to edit `src/main/resources/log4j.properties`


If you dont want to rebuild the jar after editing the file, you can create 
an updated log4j.properties and  prefix  its path to the class path (so that it 
gets priority over the one inside jar)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303068#comment-15303068
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222011444
  
Okay, the answer is that our slfj4 is using log4j12 as the backend. I had 
to add

-Dlog4j.configuration=$JOSHUA/logging.properties

to the invocation, and then put

log4j.rootLogger=OFF

(or info, etc).




> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222011444
  
Okay, the answer is that our slfj4 is using log4j12 as the backend. I had 
to add

-Dlog4j.configuration=$JOSHUA/logging.properties

to the invocation, and then put

log4j.rootLogger=OFF

(or info, etc).




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303061#comment-15303061
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user KellenSunderland commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222011143
  
Does setting it to error instead of info help?
On May 27, 2016 12:04 AM, "Matt Post"  wrote:

> Can someone tell me how to turn off logging in slf4j? I have tried passing
>
> -Dorg.slf4j.Logger.defaultLogLevel=info
>
> but this does not seem to work. Extensive googling around and walking
> through the manual have not turned up anything. I've probably missed
> something.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> 

>



> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[KellenSunderland]

Github user KellenSunderland commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222011143
  
Does setting it to error instead of info help?
On May 27, 2016 12:04 AM, "Matt Post"  wrote:

> Can someone tell me how to turn off logging in slf4j? I have tried passing
>
> -Dorg.slf4j.Logger.defaultLogLevel=info
>
> but this does not seem to work. Extensive googling around and walking
> through the manual have not turned up anything. I've probably missed
> something.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> 

>



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222008424
  
Can someone tell me how to turn off logging in slf4j? I have tried passing

-Dorg.slf4j.Logger.defaultLogLevel=info

but this does not seem to work. Extensive googling around and walking 
through the manual have not turned up anything. I've probably missed something.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15303038#comment-15303038
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222008424
  
Can someone tell me how to turn off logging in slf4j? I have tried passing

-Dorg.slf4j.Logger.defaultLogLevel=info

but this does not seem to work. Extensive googling around and walking 
through the manual have not turned up anything. I've probably missed something.


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222003148
  
Yep, working through those. Making good progress on the build. Once I can 
verify that the test cases pass under the new build (so I can know I've done 
the merge correctly), I'll push it up.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[lewismc]

Github user lewismc commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222002633
  
There will be a number of scripts which we need to update with the paths to 
the generated jar files. This is all part of the new build. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302967#comment-15302967
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222000585
  
Nevermind, found Thamme's [old 
instructions](https://github.com/apache/incubator-joshua/pull/14#issue-155139645).


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-222000585
  
Nevermind, found Thamme's [old 
instructions](https://github.com/apache/incubator-joshua/pull/14#issue-155139645).


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (JOSHUA-273) Joshua API

[Matt Post (JIRA)]

Matt Post created JOSHUA-273:


 Summary: Joshua API
 Key: JOSHUA-273
 URL: https://issues.apache.org/jira/browse/JOSHUA-273
 Project: Joshua
  Issue Type: Improvement
Reporter: Matt Post
 Fix For: 7


We have a lot of work to do to clean up the decoder's internal object pipeline 
in order to create a nice, clean API.

(This is just a stub for this issue; I will return soon with a better 
description and roadmap. Others feel free to edit, as well).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Wiki access

[Tom Barber]

Yeah that was the question thanks Matt. Lewis hooked me up last night, so I
started documenting the docker and juju deployment stuff:
https://cwiki.apache.org/confluence/display/JOSHUA/Deployment

--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)

On 26 May 2016 at 20:34, Matt Post  wrote:

> Hi Tom — This is a dumb question, but where is the Joshua wiki? You're not
> talking about the confluence page, are you? I see you have access there.
>
>
> https://cwiki.apache.org/confluence/display/JOSHUA/Joshua+%28Incubating%29+Home
>
> matt
>
>
>
>
> > On May 25, 2016, at 5:20 PM, Tom Barber  wrote:
> >
> > Hello
> >
> > Can someone give me(bugg_tb) access to the Joshua wiki please.
> >
> > Ta
> >
> > Tom
> > --
> >
> > Director Meteorite.bi - Saiku Analytics Founder
> > Tel: +44(0)5603641316
> >
> > (Thanks to the Saiku community we reached our Kickstart
> > <
> http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/
> >
> > goal, but you can always help by sponsoring the project
> > )
>
>

Re: Wiki access

[Matt Post]

Hi Tom — This is a dumb question, but where is the Joshua wiki? You're not 
talking about the confluence page, are you? I see you have access there.

https://cwiki.apache.org/confluence/display/JOSHUA/Joshua+%28Incubating%29+Home

matt




> On May 25, 2016, at 5:20 PM, Tom Barber  wrote:
> 
> Hello
> 
> Can someone give me(bugg_tb) access to the Joshua wiki please.
> 
> Ta
> 
> Tom
> --
> 
> Director Meteorite.bi - Saiku Analytics Founder
> Tel: +44(0)5603641316
> 
> (Thanks to the Saiku community we reached our Kickstart
> 
> goal, but you can always help by sponsoring the project
> )

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302750#comment-15302750
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-221969513
  
Okay, cool, I got this merged and compiling. First, THANK YOU for all of 
this amazing work! This feels like a real milestone and it was fun to work 
through the merge.

Before I push, I need to run the tests, though, and am not sure how to 
invoke the decoder. Can you provide some assistance here? I don't know maven 
very well, so if there are any maven commands to type first, that would also 
help to know. Basically, if you can get me to the point where I can type

$ echo test | joshua

and it returns

0 ||| test ||| tm_glue_0=1.000 ||| 0.000

then I can run my regression tests and push up.


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-221969513
  
Okay, cool, I got this merged and compiling. First, THANK YOU for all of 
this amazing work! This feels like a real milestone and it was fun to work 
through the merge.

Before I push, I need to run the tests, though, and am not sure how to 
invoke the decoder. Can you provide some assistance here? I don't know maven 
very well, so if there are any maven commands to type first, that would also 
help to know. Basically, if you can get me to the point where I can type

$ echo test | joshua

and it returns

0 ||| test ||| tm_glue_0=1.000 ||| 0.000

then I can run my regression tests and push up.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: too many emails

[Henry Saputra]

+1 for the idea.

I think most ASF projects with github integration have similar approach.

- Henry

On Thu, May 26, 2016 at 11:53 AM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> Hey Matt,
>
> To be clear, I’m asking for input on a name amongst those choices.
>
> Also, we shouldn’t be archiving emails so we forget about them.
> The point is the conversation for the project should happen here
> and if it’s dev relevant conversation then it should be something
> that those that don’t have the advantage of operating at GitHub
> and believing that’s the home for the project still have a chance
> to participate by sending mails and participating in the conversation
> for the project, here.
>
> That said, I think there’s a simple solution:
>
> 1) stand up new list (we can use the mlreq program here, once
> we agree on the name)
> https://infra.apache.org/officers/mlreq/
>
>
> 2) file INFRA JIRA ticket and have ASF GitHub bot send communication
> to list from #1
>
> Make sense? Agree?
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++
>
>
>
>
>
>
>
>
>
> On 5/26/16, 11:23 AM, "Matt Post"  wrote:
>
> >Chris, to be clear, are you asking for input on a name, or suggesting
> creating all three lists?
> >
> >The main issue I'm concerned with is that comments on Github generate
> three emails:
> >
> >- Github sends an email to dev
> >- If the comment is on a pull that matches a JIRA issue, the ASF Github
> bot sends an email to me
> >- It also sends the same email to dev
> >
> >I think we should just (a) tell Github to stop posting to dev and (b)
> tell the ASF Github bot to send everything to commits. We could create a
> new list, but there's some complexity in maintaining lists themselves, and
> it seems that commits would be a good place to bury things and forget about
> them.
> >
> >Would that satisfy the archiving goals? Who can do this? I don't seem to
> have Github permission on incubator-joshua to do (a), and I don't know how
> to do (b).
> >
> >matt
> >
> >
> >
> >
> >> On May 26, 2016, at 11:34 AM, kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
> >>
> >> I'd +1 as well.  Your breakdown looks good to me Chris.
> >>
> >> On Thu, May 26, 2016 at 4:12 PM, Mattmann, Chris A (3980) <
> >> chris.a.mattm...@jpl.nasa.gov> wrote:
> >>
> >>> +1 to a separate list for GitHub stuff. Many communities (Kudu,
> >>> Spark, etc.) end up doing this.
> >>>
> >>> How about:
> >>>
> >>> revi...@joshua.incubator.apache.org
> >>> git...@joshua.incubator.apache.org
> >>> iss...@joshua.incubator.apache.org
> >>>
> >>> Any of those?
> >>>
> >>> ++
> >>> Chris Mattmann, Ph.D.
> >>> Chief Architect
> >>> Instrument Software and Science Data Systems Section (398)
> >>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >>> Office: 168-519, Mailstop: 168-527
> >>> Email: chris.a.mattm...@nasa.gov
> >>> WWW:  http://sunset.usc.edu/~mattmann/
> >>> ++
> >>> Director, Information Retrieval and Data Science Group (IRDS)
> >>> Adjunct Associate Professor, Computer Science Department
> >>> University of Southern California, Los Angeles, CA 90089 USA
> >>> WWW: http://irds.usc.edu/
> >>> ++
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> On 5/26/16, 6:00 AM, "Matt Post"  wrote:
> >>>
>  I agree it's good to have Github stuff archived on Apache-owned
> domains,
> >>> I just think that the list gets overwhelmed with garbage that most
> people
> >>> are just deleting. I mean, I like the idea of skimming through
> commits, but
> >>> today I am waking up to over 100 emails, and I have to pick out the
> >>> auto-generated emails that I don't have time to read from the important
> >>> ones. If most people are just saving things to a separate folder, that
> they
> >>> are never going to read, isn't it better to turn off those auto-emails?
> 
>  Why not use a separate list like git@ or archive@ for such posts?
> Then
> >>> it's there for people to search, but no one has to wade through it.
> 
> 
> 
> 
> > On May 26, 2016, at 12:45 AM, Lewis John Mcgibbney <
> >>> lewis.mcgibb...@gmail.com> wrote:
> 

Re: too many emails

[Mattmann, Chris A (3980)]

Hey Matt,

To be clear, I’m asking for input on a name amongst those choices.

Also, we shouldn’t be archiving emails so we forget about them.
The point is the conversation for the project should happen here
and if it’s dev relevant conversation then it should be something
that those that don’t have the advantage of operating at GitHub
and believing that’s the home for the project still have a chance
to participate by sending mails and participating in the conversation
for the project, here.

That said, I think there’s a simple solution:

1) stand up new list (we can use the mlreq program here, once
we agree on the name)
https://infra.apache.org/officers/mlreq/


2) file INFRA JIRA ticket and have ASF GitHub bot send communication
to list from #1

Make sense? Agree?

Cheers,
Chris

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++









On 5/26/16, 11:23 AM, "Matt Post"  wrote:

>Chris, to be clear, are you asking for input on a name, or suggesting creating 
>all three lists?
>
>The main issue I'm concerned with is that comments on Github generate three 
>emails:
>
>- Github sends an email to dev
>- If the comment is on a pull that matches a JIRA issue, the ASF Github bot 
>sends an email to me
>- It also sends the same email to dev
>
>I think we should just (a) tell Github to stop posting to dev and (b) tell the 
>ASF Github bot to send everything to commits. We could create a new list, but 
>there's some complexity in maintaining lists themselves, and it seems that 
>commits would be a good place to bury things and forget about them.
>
>Would that satisfy the archiving goals? Who can do this? I don't seem to have 
>Github permission on incubator-joshua to do (a), and I don't know how to do 
>(b).
>
>matt
>
>
>
>
>> On May 26, 2016, at 11:34 AM, kellen sunderland 
>>  wrote:
>> 
>> I'd +1 as well.  Your breakdown looks good to me Chris.
>> 
>> On Thu, May 26, 2016 at 4:12 PM, Mattmann, Chris A (3980) <
>> chris.a.mattm...@jpl.nasa.gov> wrote:
>> 
>>> +1 to a separate list for GitHub stuff. Many communities (Kudu,
>>> Spark, etc.) end up doing this.
>>> 
>>> How about:
>>> 
>>> revi...@joshua.incubator.apache.org
>>> git...@joshua.incubator.apache.org
>>> iss...@joshua.incubator.apache.org
>>> 
>>> Any of those?
>>> 
>>> ++
>>> Chris Mattmann, Ph.D.
>>> Chief Architect
>>> Instrument Software and Science Data Systems Section (398)
>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>>> Office: 168-519, Mailstop: 168-527
>>> Email: chris.a.mattm...@nasa.gov
>>> WWW:  http://sunset.usc.edu/~mattmann/
>>> ++
>>> Director, Information Retrieval and Data Science Group (IRDS)
>>> Adjunct Associate Professor, Computer Science Department
>>> University of Southern California, Los Angeles, CA 90089 USA
>>> WWW: http://irds.usc.edu/
>>> ++
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 5/26/16, 6:00 AM, "Matt Post"  wrote:
>>> 
 I agree it's good to have Github stuff archived on Apache-owned domains,
>>> I just think that the list gets overwhelmed with garbage that most people
>>> are just deleting. I mean, I like the idea of skimming through commits, but
>>> today I am waking up to over 100 emails, and I have to pick out the
>>> auto-generated emails that I don't have time to read from the important
>>> ones. If most people are just saving things to a separate folder, that they
>>> are never going to read, isn't it better to turn off those auto-emails?
 
 Why not use a separate list like git@ or archive@ for such posts? Then
>>> it's there for people to search, but no one has to wade through it.
 
 
 
 
> On May 26, 2016, at 12:45 AM, Lewis John Mcgibbney <
>>> lewis.mcgibb...@gmail.com> wrote:
> 
> Hi Matt,
> 
> As Henry said. Either we get them going to a different list or else you
> subscribe to dev-dig...@joshua.incubator.apache.org (subscribe through
> dev-digest-subscr...@joshua.incubator.apache.org)?
> Which do you prefer?
> Quick reasoning as to why Github convo is shadowed on the Apache lists.
>>> If
> Github ever goes away, then we loose all of the conversation. We
>>> 

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302465#comment-15302465
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user lewismc commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-221933542
  
Hi @mjpost thanks for response
```
Do you want me to be the one to merge master into JOSHUA-252? Then we can 
test and merge back into master. I think this might be our 6.1 release?
```
Yes please if you could take care of merging your work on master into 
JOSHUA-252 then that would be grand. I am not overly familiar with the work 
done so I don't want to botch it. Thanks Matt.

```
Is it possible to have Maven do git checkouts (on specific versions?) 
That's one route
```
I was thinking the exact same thing and I am actively investigating here. 
```
Otherwise, we should just rely on the user to set them up. The only real 
problem is for BerkeleyLM and KenLM, since those are runtime. I don't have much 
experience in how to do this. But we could have a maven target that does a git 
checkout of a specific version, kind of like a submodule.
```
Hopefully I can provide insight and input into this. Give me a wee bit of 
time and I can get around to answering in due course. 
```
Thrax and GIZA (and fast_align) we can tell the user to set up.
```
Agreed. I sent a PR for Thrax (which is incomplete due to changes in the 
underlying API) which Mavenies the entire build 
https://github.com/joshua-decoder/thrax/pull/12 we could then pull Thrax as a 
dependency within Joshua.
For GIZA we will get the user to set up.

Thanks


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JOSHUA-272) Simplify the packing and usage of phrase-based grammars

[Matt Post (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302435#comment-15302435
 ] 

Matt Post commented on JOSHUA-272:
--

One open issue on this item: Thrax phrase-based extraction currently does not 
work; it needs to append an [X,1] on the source and target sides.

> Simplify the packing and usage of phrase-based grammars
> ---
>
> Key: JOSHUA-272
> URL: https://issues.apache.org/jira/browse/JOSHUA-272
> Project: Joshua
>  Issue Type: Improvement
>Reporter: Matt Post
>Assignee: Matt Post
> Fix For: 6.1
>
>
> For historical reasons, phrase-based grammars add some complexity to 
> decoding. The complete tree under each top-level trie node in packed grammars 
> has to fit within a single packed grammars slice, which is limited to 2 GB 
> due to constraints on the size of Java byte[] arrays. We used to sort on just 
> the first item in the trie, which was a problem for phrase-based decoding, 
> since phrase-based rules are implemented as left-branching hierarchical 
> rules. In order to pack large grammars, we packed them without the leading 
> [X,1], and then added it when loading the grammars, both for the packed and 
> memory-based grammars. This was a real mess.
> This was all fixed with a commit a while ago that packs and reads packed 
> grammars based on the first two symbols on the source side. So we should 
> remove all the complexity associated with phrases. They should just be 
> regular rules. There is also a lot of redundancy across the codebase in 
> parsing rules, converting them to different formats, and so on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Reopened] (JOSHUA-272) Simplify the packing and usage of phrase-based grammars

[Matt Post (JIRA)]

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

Matt Post reopened JOSHUA-272:
--

> Simplify the packing and usage of phrase-based grammars
> ---
>
> Key: JOSHUA-272
> URL: https://issues.apache.org/jira/browse/JOSHUA-272
> Project: Joshua
>  Issue Type: Improvement
>Reporter: Matt Post
>Assignee: Matt Post
> Fix For: 6.1
>
>
> For historical reasons, phrase-based grammars add some complexity to 
> decoding. The complete tree under each top-level trie node in packed grammars 
> has to fit within a single packed grammars slice, which is limited to 2 GB 
> due to constraints on the size of Java byte[] arrays. We used to sort on just 
> the first item in the trie, which was a problem for phrase-based decoding, 
> since phrase-based rules are implemented as left-branching hierarchical 
> rules. In order to pack large grammars, we packed them without the leading 
> [X,1], and then added it when loading the grammars, both for the packed and 
> memory-based grammars. This was a real mess.
> This was all fixed with a commit a while ago that packs and reads packed 
> grammars based on the first two symbols on the source side. So we should 
> remove all the complexity associated with phrases. They should just be 
> regular rules. There is also a lot of redundancy across the codebase in 
> parsing rules, converting them to different formats, and so on.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JOSHUA-252) Make it possible to use Maven to build Joshua

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15302396#comment-15302396
 ] 

ASF GitHub Bot commented on JOSHUA-252:
---

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-221928486
  
There have been changes on master (JOSHUA-271 and JOSHUA-272), will try to 
get to this soon, probably not till tomorrow.

Do you want me to be the one to merge master into JOSHUA-252? Then we can 
test and merge back into master. I think this might be our 6.1 release?

For packages:

- Is it possible to have Maven do git checkouts (on specific versions?) 
That's one route
- Otherwise, we should just rely on the user to set them up. The only real 
problem is for BerkeleyLM and KenLM, since those are runtime. I don't have much 
experience in how to do this. But we could have a maven target that does a git 
checkout of a specific version, kind of like a submodule.
- Thrax and GIZA (and fast_align) we can tell the user to set up.

matt


> Make it possible to use Maven to build Joshua
> -
>
> Key: JOSHUA-252
> URL: https://issues.apache.org/jira/browse/JOSHUA-252
> Project: Joshua
>  Issue Type: Improvement
>  Components: build
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
> Fix For: 6.1
>
>
> As per discussion on the dev@ list for now Ant is the official build tool for 
> Joshua however we would like to possibly switch to Maven if / when someone is 
> able to do so.
> Assigning to me for now as I could be able to look into this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[mjpost]

Github user mjpost commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-221928486
  
There have been changes on master (JOSHUA-271 and JOSHUA-272), will try to 
get to this soon, probably not till tomorrow.

Do you want me to be the one to merge master into JOSHUA-252? Then we can 
test and merge back into master. I think this might be our 6.1 release?

For packages:

- Is it possible to have Maven do git checkouts (on specific versions?) 
That's one route
- Otherwise, we should just rely on the user to set them up. The only real 
problem is for BerkeleyLM and KenLM, since those are runtime. I don't have much 
experience in how to do this. But we could have a maven target that does a git 
checkout of a specific version, kind of like a submodule.
- Thrax and GIZA (and fast_align) we can tell the user to set up.

matt


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: too many emails

[kellen sunderland]

I'd +1 as well.  Your breakdown looks good to me Chris.

On Thu, May 26, 2016 at 4:12 PM, Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov> wrote:

> +1 to a separate list for GitHub stuff. Many communities (Kudu,
> Spark, etc.) end up doing this.
>
> How about:
>
> revi...@joshua.incubator.apache.org
> git...@joshua.incubator.apache.org
> iss...@joshua.incubator.apache.org
>
> Any of those?
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Director, Information Retrieval and Data Science Group (IRDS)
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> WWW: http://irds.usc.edu/
> ++
>
>
>
>
>
>
>
>
>
> On 5/26/16, 6:00 AM, "Matt Post"  wrote:
>
> >I agree it's good to have Github stuff archived on Apache-owned domains,
> I just think that the list gets overwhelmed with garbage that most people
> are just deleting. I mean, I like the idea of skimming through commits, but
> today I am waking up to over 100 emails, and I have to pick out the
> auto-generated emails that I don't have time to read from the important
> ones. If most people are just saving things to a separate folder, that they
> are never going to read, isn't it better to turn off those auto-emails?
> >
> >Why not use a separate list like git@ or archive@ for such posts? Then
> it's there for people to search, but no one has to wade through it.
> >
> >
> >
> >
> >> On May 26, 2016, at 12:45 AM, Lewis John Mcgibbney <
> lewis.mcgibb...@gmail.com> wrote:
> >>
> >> Hi Matt,
> >>
> >> As Henry said. Either we get them going to a different list or else you
> >> subscribe to dev-dig...@joshua.incubator.apache.org (subscribe through
> >> dev-digest-subscr...@joshua.incubator.apache.org)?
> >> Which do you prefer?
> >> Quick reasoning as to why Github convo is shadowed on the Apache lists.
> If
> >> Github ever goes away, then we loose all of the conversation. We
> archive it
> >> @Apache so we cover our communities.
> >> Thanks
> >>
> >>
> >> On Wed, May 25, 2016 at 2:11 PM, <
> >> dev-digest-h...@joshua.incubator.apache.org> wrote:
> >>
> >>>
> >>> From: Matt Post 
> >>> To: dev@joshua.incubator.apache.org
> >>> Cc:
> >>> Date: Wed, 25 May 2016 15:48:24 -0400
> >>> Subject: too many emails
> >>> Does someone know how to turn off the mailing of all github comments to
> >>> dev?
> >>>
> >>> The way I see it, we all have to be on dev, so it should be for people,
> >>> not robots. I am getting every comment about three times.
> >>>
> >>> I would just do it but I don't know how.
> >>>
> >>>
> >
>

Re: too many emails

[Mattmann, Chris A (3980)]

+1 to a separate list for GitHub stuff. Many communities (Kudu, 
Spark, etc.) end up doing this.

How about:

revi...@joshua.incubator.apache.org
git...@joshua.incubator.apache.org
iss...@joshua.incubator.apache.org

Any of those?

++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: chris.a.mattm...@nasa.gov
WWW:  http://sunset.usc.edu/~mattmann/
++
Director, Information Retrieval and Data Science Group (IRDS)
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
WWW: http://irds.usc.edu/
++









On 5/26/16, 6:00 AM, "Matt Post"  wrote:

>I agree it's good to have Github stuff archived on Apache-owned domains, I 
>just think that the list gets overwhelmed with garbage that most people are 
>just deleting. I mean, I like the idea of skimming through commits, but today 
>I am waking up to over 100 emails, and I have to pick out the auto-generated 
>emails that I don't have time to read from the important ones. If most people 
>are just saving things to a separate folder, that they are never going to 
>read, isn't it better to turn off those auto-emails?
>
>Why not use a separate list like git@ or archive@ for such posts? Then it's 
>there for people to search, but no one has to wade through it.
>
>
>
>
>> On May 26, 2016, at 12:45 AM, Lewis John Mcgibbney 
>>  wrote:
>> 
>> Hi Matt,
>> 
>> As Henry said. Either we get them going to a different list or else you
>> subscribe to dev-dig...@joshua.incubator.apache.org (subscribe through
>> dev-digest-subscr...@joshua.incubator.apache.org)?
>> Which do you prefer?
>> Quick reasoning as to why Github convo is shadowed on the Apache lists. If
>> Github ever goes away, then we loose all of the conversation. We archive it
>> @Apache so we cover our communities.
>> Thanks
>> 
>> 
>> On Wed, May 25, 2016 at 2:11 PM, <
>> dev-digest-h...@joshua.incubator.apache.org> wrote:
>> 
>>> 
>>> From: Matt Post 
>>> To: dev@joshua.incubator.apache.org
>>> Cc:
>>> Date: Wed, 25 May 2016 15:48:24 -0400
>>> Subject: too many emails
>>> Does someone know how to turn off the mailing of all github comments to
>>> dev?
>>> 
>>> The way I see it, we all have to be on dev, so it should be for people,
>>> not robots. I am getting every comment about three times.
>>> 
>>> I would just do it but I don't know how.
>>> 
>>> 
>

Jenkins build is back to normal : joshua_maven #15

[Apache Jenkins Server]

See 

Build failed in Jenkins: joshua_maven #14

[Apache Jenkins Server]

See 

--
Started by user lewismc
Started by an SCM change
Started by an SCM change
Started by an SCM change
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-6 (docker Ubuntu ubuntu yahoo-not-h2) in workspace 

Cloning the remote Git repository
Cloning repository https://git-wip-us.apache.org/repos/asf/incubator-joshua.git
 > git init  # timeout=10
ERROR: Error cloning remote repo 'origin'
hudson.plugins.git.GitException: Could not init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:655)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to ubuntu-6(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:220)
at hudson.remoting.Channel.call(Channel.java:781)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor626.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy90.execute(Unknown Source)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1013)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1053)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1276)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Error performing command: git init 

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1700)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1669)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1665)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1307)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:653)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:462)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:120)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:326)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Cannot run program "git" (in directory 
": error=11, Resource 
temporarily 

[GitHub] incubator-joshua pull request: JOSHUA-252 Make it possible to use ...

[lewismc]

Github user lewismc commented on the pull request:

https://github.com/apache/incubator-joshua/pull/12#issuecomment-221793740
  
Cool @thammegowda 

#15 merged into JOSHUA-252

Work still to be done
 * plan on how we are going to compile and package GIZA++, KenLM, 
berkeleylm, thrax, etc. Right now the ext directory has been completely removed 
as that code should not live but instead be acquired as part of the build 
system.

@mjpost have you made any changes to master which we need to merge into 
JOSHUA-252 branch?
Thanks



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (JOSHUA-262) Implement all logging as Slf4j over Log4j

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/JOSHUA-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15301637#comment-15301637
 ] 

ASF GitHub Bot commented on JOSHUA-262:
---

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-joshua/pull/17


> Implement all logging as Slf4j over Log4j
> -
>
> Key: JOSHUA-262
> URL: https://issues.apache.org/jira/browse/JOSHUA-262
> Project: Joshua
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 6.0.5
>Reporter: Lewis John McGibbney
>Assignee: Thamme Gowda N
> Fix For: 6.1
>
>
> [~hsaputra] suggested that we implement all logging as Slf4j over Log4j. If 
> we use [parameterized logging 
> notation|http://www.slf4j.org/faq.html#logging_performance] we can have good 
> logging in place.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)