Releases: krunch3r76/gc_spyu
Releases · krunch3r76/gc_spyu
working ya
patches to restore to working functionality to deliver on last tag's features:
report failures; skip nodes already espied
report failures; skip nodes already espied
- report nodes that failed computation as uncooperative
- list nodes that were already on record so were not updated (override in future version)
cleaner start
- db mistakenly reported as existing and incompatible when the db file did not exist
- database construction committed just after creation to avoid a similar error message
fix missed case to update time
- fix an if/else indentation that caused time of retrieval updates to not occur on persistent database
store on model change
resolves issue #9
improve modularity for future features
- code (db) modularized into on_accepted_result.py, refactored, and made more self-documenting
- the database stored in appdata now is independent of the database in the git tree (users should be able to upgrade going forward without breaking)
- new entries into the main db only occur if a node name has changed, otherwise the timestamp is updated in place
- next version will compare model and insert when the model changes (issue #9 )
- misc bug fixes/enhancements such as tighter event monitoring to prevent work duplication (save on costs) and to maintain flow
fix missing modules and reorganize
- persistent database stores only most relevant information for easier review
- session information that is considered ancillary is stored in a disposable db file in the model directory
remove topology gathering
- remove topology gathering
- skip poorly responsive providers
- touch up console output
- handle early exit (ctrl-c) gracefully (resolves #6 )
retrievals persist in platform data dir
- cpu information obtained is now persistently stored in platform's data dir
linux: ~/.local/share/gc_spyu/gc_spyu.db
macOS: ~/Library/Application Support/gc_spyu/gc_spyu.db
windows: C:/Users/<USER>/AppData/Roaming/gc_spyu/gc_spyu.db
topology information now optional
topology is of little use if yagna cannot identify what machines are emulated vs running on bare metal