Skip to content

Fix bug in grabbing max_stride, max_samples, min_new_samples from config in stream.py

Patrick Godwin requested to merge stream_config_bug into master

Pretty straightforward fix, but was driving me crazy trying to track it down. If you specified either of the options max_stride, max_samples, min_new_samples from the configuration files, they would never trigger conditionals in loops within stream.py because these quantities would be stored as strings rather than ints/floats.

Merge request reports