-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError: propagate() got an unexpected keyword argument 'input' #30
Comments
Hi, which version of PyG are you using? |
hi @migalkin , my pyg version is 2.5.0 and torch version is 2.1.0 |
Yeah, that's a known bug with pyg 2.5.0 - I'd recommend either downgrading pyg to 2.4.0 or upgrading to anything >= 2.5.2 |
Hi @migalkin, thanks for your reply in time, but this error still exists after I upgraded Pig to 2.5.2. In fact, the only difference between our environments lies in the CUDA Driver version. Mine is 11.7, but it seems that you recommend running under 11.8. Could it be a possible reason? |
No, this is a pyg version issue, try 2.4.0 as in |
@migalkin After I downgraded pyg to 2.4.0, this problem no longer seems to occur, but new problems have appeared. Specifically, when I run:
it will counter a compile error:
I looked through the README of this repo but I still don't understand why, could you help me on this? |
You need to clean the cache of previously compiled kernels (and other jit-compiled code from previous pyg versions), delete the |
I did clean the cache by
but what is weird is that it didn't work as expected and the error still exists. |
Looking at the error trace, it appears that the previously compiled python code (.pyc files) asks for older kernels, the best approach would be to remove the repo entirely and just make a clean clone and start again (a more tedious approach is to remove all Besides, I see your env name is |
Hi @migalkin , thanks for open-sourcing this great work, but I countered an issue when I was trying to run this demo on GPU by:
Specifically, the output and error message is:
This should be an obvious problem, but no one seems to have encountered it before according to issues of this repo, which puzzles me.
Thanks for your reply in advance!
The text was updated successfully, but these errors were encountered: