i get this after running "run.bat"
Soheab opened this issue · comments
now this
Solved. Should be closed.
Also watch out, Heroku got a new stack (18) and some python versions aren't supported anymore.
Fix is using this in where you put all the files and stuff:
runtime.txt
Also who changed the Procfile? That doesn't work haha, you need to use this Procfile b/c it isn't bash. It's ran by python!
https://www.filemail.com/d/nblcinjomyuftlc
Really suggest changing that.
Solved. Should be closed.
Also watch out, Heroku got a new stack (18) and some python versions aren't supported anymore.
Fix is using this in where you put all the files and stuff:
runtime.txt
Also who changed the Procfile? That doesn't work haha, you need to use this Procfile b/c it isn't bash. It's ran by python!
https://www.filemail.com/d/nblcinjomyuftlc
Really suggest changing that.
wdym?
Dude i legit just helped you getting this to work. You saw with your own eyes that it didn't worked the procfile. Also buildling didn't work ether due to the new stack config.
Also you can hit close.
Dude i legit just helped you getting this to work. You saw with your own eyes that it didn't worked the procfile. Also buildling didn't work ether due to the new stack config.
Also you can hit close.
sry.. but what is a procfile and what must i do with it?
edit: nvm i replaced the procfile and put the runtime by all the files.. but still nothing same error..
We just had it working? Why did you put the runtime everywhere???? I never said you had to do that, not even ever saying you had to put it everywhere?????
i didnt put it in all the files look.. this are all the bots files rn
so if i start run.bat it finishes with this... 
Seems that i've mistaken who you are, wierd that you didn't react on this part differently:
Dude i legit just helped you getting this to work. You saw with your own eyes that it didn't worked the procfile. Also buildling didn't work ether due to the new stack config.
Also you can hit close.
No clue what your doing there, but what is visual studio stuff doing there? Give more context.
idk what visual studio is doing it said i should download it first so i did lol
recheck the steps here in the wiki. No where it would ever even mention vs.
recheck the steps here in the wiki. No where it would ever even mention vs.
Look at the first screenshot it said ‘error: Microsoft visual c++ is required’
Bump. I've got this exact issue.
@Macley-Kun I think it has to do with the way its downloading and installing the requirements. It failed during the lxml setup, so I pip installed it outside of the script, hoping it'd resolve itself and continue, but it got caught on the same one. I removed it from requirements, then it got caught on another dep. I'm currently trying to manually install all the deps and remove them from the requirements, I'll post what happens.
OK so it didn't work, but I learned a few valuable things from it.
I'm still 95% sure that the script failed b/c of how it was installing things. It would always fail during the setup of a specific dependency, and it would never get past the line python -m pip install --user -r requirements.txt in the batch file.
I ended up editing the requirements.txt such that I didn't explicitly add the version numbers, and it went through perfectly. It ended up throwing mountains and mountains of errors and being generally unusable, but regardless, what that proved was that the failure was b/c of how it was trying to setup the deps in the original requirements.txt.
Obviously this doesn't rly fix anything, since it seems as though there are facilities being used in this repo that break when you download newer / recommended versions of the requirements. I wanna say the fix is to try to get this on new deps, but it could easily be b/c I'm doing something astonishingly idiotic, and nobody else has this problem.
OK so it didn't work, but I learned a few valuable things from it.
I'm still 95% sure that the script failed b/c of how it was installing things. It would always fail during the setup of a specific dependency, and it would never get past the line
python -m pip install --user -r requirements.txtin the batch file.I ended up editing the requirements.txt such that I didn't explicitly add the version numbers, and it went through perfectly. It ended up throwing mountains and mountains of errors and being generally unusable, but regardless, what that proved was that the failure was b/c of how it was trying to setup the deps in the original requirements.txt.
Obviously this doesn't rly fix anything, since it seems as though there are facilities being used in this repo that break when you download newer / recommended versions of the requirements. I wanna say the fix is to try to get this on new deps, but it could easily be b/c I'm doing something astonishingly idiotic, and nobody else has this problem.
ah okay hmmm i removed the versions in requirements so the bot installed but now it doesnt start it just repeatly says that on pic
