Skip to content
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

VSCode linting issue with torch methods #2548

Closed
YadavGulshan opened this issue Jul 5, 2020 · 2 comments
Closed

VSCode linting issue with torch methods #2548

YadavGulshan opened this issue Jul 5, 2020 · 2 comments
Labels

Comments

@YadavGulshan
Copy link

YadavGulshan commented Jul 5, 2020

Guidelines

NOTE: Issues are for bugs and feature requests only. If you have a question about using Pyro or general modeling questions, please post it on the forum.

If you would like to address any minor bugs in the documentation or source, please feel free to contribute a Pull Request without creating an issue first.

Please tag the issue appropriately in the title e.g. [bug], [feature request], [discussion], etc.
[discussion] [urgent]

Please provide the following details:

###Issue Description
image
image

Environment

For any bugs, please provide the following:

  • OS and python version.Pop!_OS 20.04 LTS x86_64 and python3.8
  • PyTorch version, or if relevant, output of pip freeze.1.5.1
  • Pyro version: output of python -c 'import pyro; print pyro.__version__' 1.3.1

Code Snippet

import torch

x= torch.randn(2,3,requires_grad=True)
w=torch.randn(2,requires_grad=True)
print(x)
print(w)

def main(y):
return y@w.t + x

pred = main(input)
print(pred)

@JamesTrick
Copy link
Contributor

Hi @gulshan2002

This is an issue that is best raised with pyTorch themselves. I've also found the relevant issue - they recommend suppressing such messages. Issue is here.

@eb8680 eb8680 added the question label Jul 7, 2020
@fritzo fritzo changed the title Torch, member issue.... VSCode linting issue with torch methods Jul 7, 2020
@fritzo
Copy link
Member

fritzo commented Jul 7, 2020

@JamesTrick thanks for the fix. Indeed this is an upstream issue with PyTorch + VSCode and it looks like the best fixes are described at pytorch/pytorch#701

@fritzo fritzo closed this as completed Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants