[jira] [Closed] (UIMA-6127) DUCC Web Server (WS) should allow duccinator-update request via http

[ https://issues.apache.org/jira/browse/UIMA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro closed UIMA-6127. -- > DUCC Web Server (WS) should allow duccinator-update request via http >

[jira] [Resolved] (UIMA-6127) DUCC Web Server (WS) should allow duccinator-update request via http

[ https://issues.apache.org/jira/browse/UIMA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro resolved UIMA-6127. Resolution: Fixed Change set delivered. > DUCC Web Server (WS) should allow duccinator-update

[jira] [Work started] (UIMA-6127) DUCC Web Server (WS) should allow duccinator-update request via http

[ https://issues.apache.org/jira/browse/UIMA-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on UIMA-6127 started by Lou DeGenaro. -- > DUCC Web Server (WS) should allow duccinator-update request via http >

[jira] [Created] (UIMA-6127) DUCC Web Server (WS) should allow duccinator-update request via http

Lou DeGenaro created UIMA-6127: -- Summary: DUCC Web Server (WS) should allow duccinator-update request via http Key: UIMA-6127 URL: https://issues.apache.org/jira/browse/UIMA-6127 Project: UIMA

[jira] [Work logged] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support

[ https://issues.apache.org/jira/browse/UIMA-5936?focusedWorklogId=314512=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-314512 ] ASF GitHub Bot logged work on UIMA-5936: Author: ASF GitHub Bot

Re: coordinating uimaj work, renaming trunk -> master

Infra has protected the master branch, and set it as the "default". This allowed me to delete the "trunk" branch, which I just did (it's been renamed to master). I'll wait a day, and then close the INFRA jira - so please let me know of any issues with this rename. -Marshall On 9/17/2019 1:43

anyone know why asfgit bot closed a pull request?

Hi, There was a pull request for uimaj https://github.com/apache/uima-uimaj/pull/10# that was closed by "asfgit". Does anybody understand why this happened?  -Marshall

[jira] [Reopened] (UIMA-6125) ducc_update fails when DB automange is false but DB is running

[ https://issues.apache.org/jira/browse/UIMA-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro reopened UIMA-6125: check_ducc fails.   AttributeError: CheckDucc instance has no attribute 'db_pidfile' > ducc_update

[jira] [Commented] (UIMA-6125) ducc_update fails when DB automange is false but DB is running

[ https://issues.apache.org/jira/browse/UIMA-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16932807#comment-16932807 ] Lou DeGenaro commented on UIMA-6125: If db is not automanaged, then skip checking for db_pidfile. >

[jira] [Resolved] (UIMA-6125) ducc_update fails when DB automange is false but DB is running

[ https://issues.apache.org/jira/browse/UIMA-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro resolved UIMA-6125. Resolution: Fixed Change set delivered. > ducc_update fails when DB automange is false but DB is

[jira] [Closed] (UIMA-6125) ducc_update fails when DB automange is false but DB is running

[ https://issues.apache.org/jira/browse/UIMA-6125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lou DeGenaro closed UIMA-6125. -- > ducc_update fails when DB automange is false but DB is running >

[jira] [Work logged] (UIMA-5936) PearSpecifier should be able to store every parametertype that analysisEngines support

[ https://issues.apache.org/jira/browse/UIMA-5936?focusedWorklogId=314818=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-314818 ] ASF GitHub Bot logged work on UIMA-5936: Author: ASF GitHub Bot

Re: anyone know why asfgit bot closed a pull request?

On 18. Sep 2019, at 23:57, Marshall Schor wrote: > > There was a pull request for uimaj > https://github.com/apache/uima-uimaj/pull/10# > that was closed by "asfgit". > > Does anybody understand why this happened? No idea. The issue is still open. -- Richard