Skip to content

Release 1.2.6
Compare
Choose a tag to compare
@al-niessner al-niessner released this 18 Oct 15:19
1.2.6
e80f3ba
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Issue 44: fixing up scheduler (#50)

Author: al-niessner
Date: Wed, 16 Oct 2019 11:53:43 -0700

  • add capabilities

dawgie.MOMENT added "boot" which will trigger something when the pipeline boots and only boots (not reload from git). This is an odd request but since there is a need, added it.

dawgie.schedule() was updated to properly handle the new "boot" in dawgie.MOMENT. The check was modified to be more adaptable when dawgie.MOMENT changes again in the future.

dawgie.tools.compliant was updated to check that events() returns valid dawgie.MOMENTS since nothing requires the user use dawgie.schedule().

  • added unit testing

Single unit test for dawgie.pl.schedule._delay() that it computes 0 delay and then throws the exception when the same unit comes around a second time.

  • include more checks on building an EVENT

Issue 45 (#49)

Author: al-niessner
Date: Mon, 14 Oct 2019 18:32:19 -0700

  • have a test that highlights the error

  • fix bad assumption

dawgie.pl.schedule.update() assumed everything was a dawgie.Algorithm and called previous(). The correction was to use an _priors() function that called traits(), variables(), or previous() depending if it as Analyzer(), Regression(), Task() respectively.

Issue 47: backlog (#48)

Author: al-niessner
Date: Wed, 9 Oct 2019 08:24:23 -0700

  • add configurable TCP/IP backlog

As the worker size scales up, the backlog needs to increase with it. Since it should be directly related to the number of workers, called it worker_backlog.

  • update all worker interfaces

There are many connections between workers and the pipeline server. Update them all to use a big enough backlog to support the scale of workers being used.

Assets 2
Loading