Enable logging for incoming server requests #14
Closed
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.
The server now prints out incoming requests with some associated metadata
Function call changed to:
UMBridge.serve_models([testmodel], 5232, true)
with the lastBool
argument acting as a trigger to initiate logging (default argument isfalse
).As of now, there's an extra level of verbosity with all
Evaluate
calls being printed out -> a possible resolution could be to export the logs to file instead.tail -f <filename> | grep "keywords"
can then be used to filter for incoming requests. OR use a separate argument to enalbe logging for evaluate all together?@linusseelinger thoughts?