-
Notifications
You must be signed in to change notification settings - Fork 9
could not connect orientDB 2.2.30, always timeout. #50
Comments
I am not currently supporting this library. @MyMedsAndMe/voyagers hey folks, if you're not maintaining this library, maybe we should use the new archiving feature GitHub rolled out, write that the repo is not maintained in the README, and archive it? |
Hi @whatyouhide. Yes, for various reasons, at the moment none of us are maintaining this repository. I'll add a note on the README page and eventually archive it later on. |
could I be so impolite and ask why you are not using it anymore? OrientDB seems to be quite active thanks |
@niccolox from my side, I am not sponsored anymore from MyMedsAndMe and I have many other projects to maintain that have priority over marco_polo. |
@niccolox here as MyMedsAndMe we were using OrientDB as part of an R&D project that no longer is in scope, and since it hasn't been used by us in any other projects we had to stop the maintenance |
fair enough and thanks for the responses |
Hi @mtanzi , would you be open to transferring the ownership to a willing maintainer? |
I made some modifications based on the v0.1.0 version to make it work normally on OrientDB Server v.2.2.36 |
try marco_polo with 0.2.2, always get time out error.
The text was updated successfully, but these errors were encountered: