2
45%
master: 45%

Ran 18 Nov 2019 08:13PM UTC

Files 106

Run time 21s

Badge

Embed ▾

Committed 18 Nov 2019 08:13PM UTC coverage: 44.863% (+0.1%) from 44.751%

Job # 6655.2

Build Type

push

travis-ci

Committed by

tomka

Commit Message

Submitter: execute functions w/o HTTP requests asynchronously too

A submitter can be used to queue both HTTP requests and regular
functions. HTTP requests are executed asynchronously, but so far, when
running a queue element using next(), regular functions where
executed right away in a synchronous fashion. This inconsistency can
lead to subtle problems in execution order, mainly when "exiting" the
submitter queue by generating an independent promise using "promise()".
In that case an actual Promise instance is returned that resolves as
soon as the submitter queue is at the insertion point. If however no
real asynchronous tasks where performed up to that point, a new
a new non-http continuation added to the submitter, will run *before*
the previously generated promise. This is counterintuitive and not
intended. The reason is that all continuations have been run
synchronously and the promise execution waits for the next available
async microtask slot. This commit runs therefore also sync continuations
in an async promise.

The Tracing Overlay front-end tests revealed that when working with
queueing both synchronous and asynchronous queue continuations.

Run Details

8563 of 19087 relevant lines covered (44.86%)

0.45 hits per line

catmaid / CATMAID / 6655 / 2
45%
master: 45%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6655.2

catmaid / CATMAID / 6655 / 2 45% master: 45%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 6655.2

catmaid / CATMAID / 6655 / 2
45%
master: 45%

README BADGES
x