Skip to content

Releases: al-niessner/DAWGIE

Release 1.2.2

23 Jul 20:45
@al-niessner al-niessner
1.2.2
de76769
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.
Compare
Choose a tag to compare
Release 1.2.2

issue 7: FE updates (#10)

Author: al-niessner
Date: Tue, 23 Jul 2019 13:40:15 -0700

  • Updating FE with Build v19

Changed typeahead engine to use fuzzy matches on the search page.

Made State Vector search use filtering the same as Target Name search.

  • Used the .ci/check_04.sh 1 script to update the LICENSE information in the html files.

  • change default filters

The Admin filter is working in tests so should be sufficient. The Dev and User are set to be the same by default. Still testing with those so they may update again in the future.

  • Re-arragning filter buttons.

Fixing a bug in filters for exact match.

  • reset user and dev default values now that filters are set correctly

  • Adding a cookie for selected filter state

Adding a way to brand the frontend with javascripts/siteconfig.js

  • Removing un-used images

fill in some docs

Author: Al Niessner
Date: Fri, 19 Jul 2019 16:44:17 -0700

Issue 18: ref verification (#19)

Author: al-niessner
Date: Sun, 14 Jul 2019 17:05:15 -0700

  • the feat should always be a string

While the documentation stated object, dawgie expects it to be a string because dawgie.StateVector uses a string (feature name) for the key. Secondary, the dawgie.StateVector key is used to form a canonical name with the feat being the last part.

  • unit test

dawgie.tool.compliant is the unit test for this problem. Seems that not all SV_REF and V_REF are created equal and this will check a system that they all comply with the expectation. Given that the tests have a toy AE in them, this deployment check also becomes a unit test.

  • demonstration of fault

A unit test (Test/test_08.py) that uses the toy test/ae to demonstrate the detection of wrong types in *_REF. All of the ALG_REF work without problem. It is the newer and much less used SV_REF and V_REF. Currently Test/test_08.py is finding the errors in test/ae as expected.

  • update toy ae in Test

ae.feedback.bot updated so that all SV_REF and V_REF follow the dawgie documentation (doctext in dawgie/init.py). They now set all items to dawgie.StateVector instead of strings. The result was to cause deeper parts of dawgie to fail then be corrected.

  • clean up dawgie

dawgie.pl.dag -- all ref.item are now treated as a dawgie.StateVector
dawgie.util -- all ref.item and vref.item are treated as dawgie.StateVector

  • final validation

With all of the changes above completed and tested via .ci/check*.sh passing, ran the scripts .ci/deploy_0[1-6].sh inclusive. Fixed a trivial poor use of git checkout to git reset in .ci/deploy_01.sh that is non sequitur. Proceeded to run .ci/exercise_01.sh after all of the deploy scripts completed. The exercise ran to completion verifying that dawgie.db is sufficient as is and that all other changes work in concert correctly.

issue 13: adapt to gnupg version (#14)

Author: al-niessner
Date: Tue, 9 Jul 2019 07:56:39 -0700

  • adapt to version of gnupg

Issue 16: add new targets when detected (#17)

Author: al-niessner
Date: Sun, 30 Jun 2019 15:35:49 -0700

  • test to illustrate problem

The first step in fixing the problem is to write a unit test to demonstrate it. This test fixture is constructed to have an all target in it making the unit test rather simple -- test_issue_16().

The complexity is really in the setUpClass(). Here it overrides critical parts of dawgie.db.shelf that normally speak over the network via twisted. The unit test does not require the communication but does require the standard processing. Hence, setattr() is used to do the overrides:

mock_acquire and mock_release override dawgie.db.shelf.Connector versions because there can only be one user of the database -- pytest. Therefore, the locks can simply be ignored.

mock_do() overrides dawgie.db.shelf.Connector.__do() skipping the pickling sending and receiving. Instead it calls dawgie.db.shelf.Worker.do() directly and the response is passed back via a test global variable.

mock_send() overrides dawgie.db.shelf.Worker._send() to skip pickling and sending. Instead it writes the respose to a test global variable.

  • add target insertion

Updated dawgie.db.shelf.Interface to add a target if it is not known. The unit test now passes showing the fix works.

log message (#12)

Author: al-niessner
Date: Tue, 25 Jun 2019 08:36:34 -0700

change log backup count (#9)

Author: al-niessner
Date: Mon, 17 Jun 2019 14:41:15 -0700
dawgie.context - add log_backup and make the arguments.

dawgie.pl.logger - use dawgie.context.log_backup

fix

Author: al-niessner
Date: Mon, 17 Jun 2019 11:50:58 -0700

Use latest v2 request (#6)

Author: al-niessner
Date: Mon, 17 Jun 2019 11:48:38 -0700

work in progress (#2)

Author: al-niessner
Date: Mon, 17 Jun 2019 11:34:55 -0700

  • updated build v18

  • updated the build process

Jenkins is different enough from Travis-CI that had to reorder the steps and fix up the steps themselves.

  • fix a bug

Seems dawgie/pl/logger.py crept back in. Removed it.

initial commit

Author: Al Niessner
Date: Tue, 11 Jun 2019 09:24:49 -0700

Assets 2
Loading

Release 1.2.1

11 Jun 16:41
@al-niessner al-niessner
1.2.1
f37f6c0
Compare
Choose a tag to compare
Release 1.2.1 
initial commit
Assets 2
Loading