Open developedbyalex opened 1 year ago
I am getting the same issue
Edit: apparently it might be because pushshift is changing servers, still looking into it
it seems the pushshift api is not working at the moment and some of it is down: https://stats.uptimerobot.com/l8RZDu1gBG
if the pushshift API does come back online, the /src/apis/pushshift.py will need to be updated with the new pushshift api endpoint
yeah, seems like pushift is down at the moment and has been for a few days. Fingers crossed it comes back online.
I am getting the same issue
Edit: apparently it might be because pushshift is changing servers, still looking into it
did you find any more info out?
It seems that pushshift changed or updated their servers and also made changes to their api. I had a hard time piecing together what is going on from the threads in the pushshift subreddit.
Ah ok, do you think we would be able to update the code ourselves considering that the original author doesn't look like he's going to release an update?
I think this could help https://www.reddit.com/r/pushshift/comments/zkggt0/update_on_colo_switchover_bug_fixes_reindexing/ looks like they are in the process of transferring servers. Their status page now shows them as online. I think their domain changed.
here are some more sources (i will update as i find more info): https://www.reddit.com/r/pushshift/comments/zlryw1/comment/j0bss25/
Think I may've fixed it. Just running now to check.
EDIT: Nope, :( I have managed to get it to successfully connect to pushift, but it cannot find any posts. I'll keep trying to figure it out.
Looks like the python library itself will not work with the current API and is not expected to be updated. There is an alternative library which it could be updated to work, but will probably require some time and knowledge. Ideally the author of this project will decide to update it but seems unlikely for now.
That is unfortunate. What is the alternate library? Maybe it won’t be to hard to update.
That is unfortunate. What is the alternate library? Maybe it won’t be to hard to update.
I think the api may return data in a slightly different way than before, but it may be possible.
Do you @lckynmbrsvn have any idea of how the code functions? I have a basic understanding, but I think to implement the new API, deeper knowledge might be needed. There is a code walkthrough on YouTube.
@sheepsushis Got any idea? I see you made the tutorial and stuff.
@gully32 I haven't had a chance to look through anything yet, I want to take a look but I'm not the best programmer. I want to give it a shot though.
@gully32 I haven't had a chance to look through anything yet, I want to take a look but I'm not the best programmer. I want to give it a shot though.
Yeah same, think it should be possible. Update me if you find anything and we can try and work it out. I’ve figured out how to change the url for the initial ping test but not sure how to make requests etc
The bot correctly implements the use of PSAW. I concur that pushshift changed something on their end, causing PSAW to break. While PMAW certainly will not be a drop-in replacement, it should not be too difficult to migrate the bot to it. Another way we could solve this is by forking PSAW, and applying fixes. However, this has a major caveat: Somebody will have to maintain the fork. From my personal standpoint, migrating to PMAW is a better route as it will likely have future updates for a long period of time.
The bot correctly implements the use of PSAW. I concur that pushshift changed something on their end, causing PSAW to break. While PMAW certainly will not be a drop-in replacement, it should not be too difficult to migrate the bot to it. Another way we could solve this is by forking PSAW, and applying fixes. However, this has a major caveat: Somebody will have to maintain the fork. From my personal standpoint, migrating to PMAW is a better route as it will likely have future updates for a long period of time.
How feasible is this? I happy to offer help although it may be limited lol, is there any guides on how to migrate? Thx for the reasponse btw
The bot correctly implements the use of PSAW. I concur that pushshift changed something on their end, causing PSAW to break. While PMAW certainly will not be a drop-in replacement, it should not be too difficult to migrate the bot to it. Another way we could solve this is by forking PSAW, and applying fixes. However, this has a major caveat: Somebody will have to maintain the fork. From my personal standpoint, migrating to PMAW is a better route as it will likely have future updates for a long period of time.
How feasible is this? I happy to offer help although it may be limited lol, is there any guides on how to migrate? Thx for the reasponse btw
major functionalities of the bot have to be re-written/updates.. that gives 2 options
both options are feasible with time at hand
major functionalities of the bot have to be re-written/updates.. that gives 2 options
- re-write the bot from scratch/update funcs
- create a new bot
both options are feasible with time at hand
I disagree, the codebase does not have to be entirely rewritten. The bot does a lot more than grabbing data from pushshift, and it's more reasonable to only replace parts of the code.
most important parts of the bot are broken..smh
@gully32 I am going to make a fork of the repository, and slowly start working on it. I'll link it here somehow, but I don't know the best method.
@gully32 I am going to make a fork of the repository, and slowly start working on it. I'll link it here somehow, but I don't know the best method.
Thank you!! Keep me updated and tell me if you need anything
Any luck?
@gully32 I am going to make a fork of the repository, and slowly start working on it. I'll link it here somehow, but I don't know the best method.
How is it going? Figured anything out yet ?
We have identified and resolved the issue with PSAW by implementing PMAW as a replacement, ensuring seamless migration and long-term support for the bot's functionality. I have also evaluated the option of forking PSAW and applying fixes, but determined that migrating to PMAW would be a more optimal solution for sustained progress and maintenance.
So it should work now?
Where can we find the solution?
How's it going?
I am also getting the same error https://gyazo.com/2188063b6784b56ff509c753ff273ba7
Hope someone give solution for this issue.
I am also getting the same error https://gyazo.com/2188063b6784b56ff509c753ff273ba7
Hope someone give solution for this issue.
you should delete that really fast .. your account credentials are exposed
no
no
Just use PMAW
no
Just use PMAW
yep works perfectly. use pip install pmaw
no
Just use PMAW
yep works perfectly. use pip install pmaw
Actually doesn't seem to be finding posts. I will update with a solution if i find one.
i installed pmaw and it still says it
i installed pmaw and it still says it
no
Just use PMAW
yep works perfectly. use pip install pmaw
Actually doesn't seem to be finding posts. I will update with a solution if i find one.
I mean, I did manage to get it working with my fork:
Just install the requirements.txt with:
pip install -r requirements.txt
Just install the requirements.txt with:
pip install -r requirements.txt
still getting ModuleNotFoundError: No module named 'pmaw'
even when using your fork. Any help appreciated.
Just install the requirements.txt with:
pip install -r requirements.txt
still getting
ModuleNotFoundError: No module named 'pmaw'
even when using your fork. Any help appreciated.
It should work because it exists on PyPi https://pypi.org/project/pmaw/
Maybe you should try setting up the python virtual environment and then installing the requirements.txt and then running the script. I managed to get a bunch of stuff working as of yesterday, now ironing out the AI problems.
UPDATE: Got the AI working
UPDATE: Got the AI working
I will restart from scratch and update you :) thanks for all your help!
UPDATE: Got the AI working
I will restart from scratch and update you :) thanks for all your help!
still getting the error. It seems like pmaw will not install properly. I have tried activating the virtual env which is set up by the script on first run and installing manually to it. It says that it has been installed but looks like the program cannot see it. I have also installed requirements.txt
me also getting same error...i even installed pmaw
UPDATE: Got the AI working
I will restart from scratch and update you :) thanks for all your help!
still getting the error. It seems like pmaw will not install properly. I have tried activating the virtual env which is set up by the script on first run and installing manually to it. It says that it has been installed but looks like the program cannot see it. I have also installed requirements.txt
Huh, strange, I managed to get it working with a venv and windows
UPDATE: Got the AI working
I will restart from scratch and update you :) thanks for all your help!
still getting the error. It seems like pmaw will not install properly. I have tried activating the virtual env which is set up by the script on first run and installing manually to it. It says that it has been installed but looks like the program cannot see it. I have also installed requirements.txt
Huh, strange, I managed to get it working with a venv and windows
hmmm, I am working on linux currently. Maybe this is the problem?
Can I get the log files?
Because it seems that this should work
Are they located somewhere specific or do you want the output of run_linux.sh?
Should be under info.log
C:\Users\Administrator.virtualenvs\reddit-karma-farming-bot-4.0.4-irMUKD2V\Lib\site-packages\psaw\PushshiftAPI.py:192: UserWarning: Got non 200 code 404 warnings.warn("Got non 200 code %s" % response.status_code) C:\Users\Administrator.virtualenvs\reddit-karma-farming-bot-4.0.4-irMUKD2V\Lib\site-packages\psaw\PushshiftAPI.py:180: UserWarning: Unable to connect to pushshift.io. Retrying after backoff. warnings.warn("Unable to connect to pushshift.io. Retrying after backoff.")