Recent changes to tickets

#394 scala magic suddenly seems required by FP-Akka-1.6.0-workflowstarter.jar

2017-07-17T15:11:00.286000Z

I invoked
#/bin/sh -f echo hello in=head5.txt echo $in java -jar FP-Akka-1.6.0-workflowstarter.jar -w DwCa -i $in -o occurrence_qc.json -a IPNI

scala magic suddenly seems required by FP-Akka-1.6.0-workflowstarter.jar

2017-07-15T22:50:11.621000Z

workflowstarter throws call to scala, which seems like a new requirement, and/or wiki needs updating
ram@milne:more fp-akka.log
ERROR [main] (ModuleLoader.scala:82) -

_
_ _
_
/ _ \ | | | | | | | | | \/ |() ()
/ /\ \ _ __

| |_ | | | | | |

_
_ __ | . . | _

_ _

| _ |/ || '_ \ / _ \ / || | | | | |/\| | / _ \ / |\ \ / // _ \| '__| | |\/| || |/ __|/ __|| || '_ \ / _ |
| | | |_ \| |_) ||
/| ( | | /_/ / \ /\ /|
/| (| | \ V /|
/| | | | | || |__ \ \| || | | || (| |
_| |/|/| ./ _| _| _|_/ \/ \/ _| _,| _/ _||| _| |/|_||/|/|||| || _, |
| | __/ |
|_| |/

It seems like your application was not started with the -javaagent:/path-to-aspectj-weaver.jar option but Kamon detected
the following modules which require AspectJ to work properly:

  kamon-akka, kamon-scala

If you need help on setting up the aspectj weaver go to http://kamon.io/introduction/get-started/ for more info. On the
other hand, if you are sure that you do not need or do not want to use the weaver then you can disable this error message
by changing the kamon.show-aspectj-missing-warning setting in your configuration file.

ERROR [main] (ModuleLoader.scala:82) -

It seems like your application was not started with the -javaagent:/path-to-aspectj-weaver.jar option but Kamon detected
the following modules which require AspectJ to work properly:

  kamon-akka, kamon-scala

ram@milne:

#384 FP-Akka confusing about ScientificName when no atomic decomposition in the data

2016-01-19T17:59:59.526000Z

Description has changed:

Diff:

--- old
+++ new
@@ -0,0 +1 @@
+Fixed in revision [r4590].  Changed text of relevant curation comment to clarify.

status: new --> fixed
Reproducibility: HaveNotTried --> Always

#393 fp-akka 1.5.1 throws faults in georef

2015-12-18T20:53:14.413000Z

status: new --> fixed
Severity: major --> minor
Reproducibility: HaveNotTried --> Always

#393 fp-akka 1.5.1 throws faults in georef

2015-12-18T20:35:09.077000Z

Resolved in [r4560], shapefile wasn't being closed.

#393 fp-akka 1.5.1 throws faults in georef

2015-12-17T22:56:34.725000Z

Attachments has changed:

Diff:

--- old
+++ new
@@ -1 +1,2 @@
 stdout.txt (91.2 kB; text/plain)
+occurrences_980_v2.zip (25.2 kB; application/x-zip-compressed)

fp-akka 1.5.1 throws faults in georef

2015-12-17T22:54:28.534000Z

Ticket 393 has been modified: fp-akka 1.5.1 throws faults in georef
Edited By: Paul J. Morris (chicoreus)
Status updated: u'new' => u'fixed'
_severity updated: u'major' => u'minor'
_reproducibility updated: u'HaveNotTried' => u'Always'

fp-akka 1.5.1 throws faults in georef

2015-12-17T22:54:28.534000Z

May not be major, but very noisy. See console output in attached "stdout.txt"

fp-akka 1.5.1 throws faults in georef

2015-12-17T22:54:28.534000Z

Ticket 393 has been modified: fp-akka 1.5.1 throws faults in georef
Edited By: Robert A. Morris (ramorrismorris)

date semantics of YYYY-MM

2015-11-07T02:29:34.620000Z

InternalDateValidation.validateDate(...) is taking a semantic position that an ISO8601 date of the form YYYY-MM should be an interval and offers conversion to same in DateUtils.extractInterval(..). But I believe 8601 does not define date intervals, only date-time intervals. YYYY-MM simply denotes reduced precision.