-
Notifications
You must be signed in to change notification settings - Fork 339
Error while trying the first "Multiples Exchange/ One Currency" example #72
Comments
same for me, like below
my pip list is below aiodns 2.0.0 |
Any updates on the above issue? I am facing the same error too |
Is this entire project dead? 17 months since the latest update, the very first example in the ReadMe is failing and no response to requests for help, and this, and no response either. Would love to use this, but nervous about starting a large project with something already broken and abandoned, if anyone is still driving this, please respond. |
For anyone interested, here is the actual problem... in the example code provided are these two lines... collections_dir = '/Users/wardbradt/cs/peregrine/' as you can see, collections_dir is set to a literal string representation of some directory that of course will not exist on your machine. Then, that literal string is passed into the call for setting opportunity. I am guessing the intent was to look into that directory, and find all of the exchanges you want to look through... but that literal string is never actually treated as a directory (which, again, even if it were, would not exist on anyones machine except the authors) and it is never searched for exchanges. Instead, it is parsed character by character as a string by downstream code, and since the first character is "/", that is where the error is originating. I am done troubleshooting this... it is obviously broken and abandoned. If anyone pulls the string further and actually fixes it, please post the fix here, as I would still like to get it up and running, but I have to be realistic. |
... so, I couldn't help myself... So, the code that is being called with that fucked up path has the inbound variable set as optional, with the default value = None. So I simply changed the demo code to not supply a value at all. But this still crashes, just differently. That call crawls inside a tangled web of asynchrounous non-sense (I despise asynchronous code, especially when the very next step depends on it's completion, thereby rendering the entire point moot...). Where it then crashes is in trying to iterate a coroutine, rather than iterating that coroutine's results. Obviously, something in the async/await chain is busted, and NOW I am totally done with this because it is too needlessly complicated, AND broken, AND abandoned. Such a pity... we had such high hopes for you... @wardbradt ??? |
At the moment, I am not actively maintaining this project. I will respond to some issues and review pull requests, but I am not currently working on code to contribute to its upkeep. There are some issues with the original implementation that have yet to be fixed, namely with regards to data directories and the use of async. @SzQaNinja |
@SzQaNinja Outside of my full-time job, I devote my personal coding time to a proprietary arbitrage/ MEV bot. Although I would like for the Peregrine project to be kept up-to-date, I have little time to contribute to it. |
The text was updated successfully, but these errors were encountered: