Closed malaref closed 7 years ago
@muhammad-alaref Thanks for reporting this. Clearly a regression. Our team will take a look at this early next week.
The issue here was that sparse run
was trying to connect to Nimbus in streamparse.util.resolve_options
, so it was only broken if Nimbus wasn't configured in your config.json
. That said, PR #392 to fix the issue will be merged shortly and then I'll release 3.7.1 on PyPI.
The last update (version 3.7.0) broke the
sparse run
functionality! Running the example from the Quickstart guide it gives an error message.Since
sparse run
should run the topology locally, it should not look for Nimbus.When I downgraded the package to version 3.6.0 everything was back no normal :smile: