Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes partly #127
Within the testset of
ukb, enki and git
htcondor logs, all events are handled.The problem is that the documentation about how to access address each event individually is missing and there is no python baseclass to extract the information from. From what I understand is that the python structure is translated directly from the C++ base module, which has a total different setup and makes it hard to known where which part of the information is comming from.
Each event has a different struture which means each event needs to be handled differently.
There are base classes for the following event numbers that come with this PR:
Not (yet) handled events (regarding the base classes) are:
And obviously all other events not mentioned here need also to be implemented