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
gRPC debug URL scheme support for Windows #17933
Comments
Had same issue. Tried running it in WSL without problems, only difference was running file from WSL instead of windows 10 |
Same issue for me, windows 10 |
try to replicate the tensorboard debugger tutorial with same issue on windows 10 |
@ClaCec The tfdbg tutorial (here for posterity) doesn't use gRPC, but there's a flag in
Here's the output:
|
got the same issue |
Briefly said: Currently Windows is not supported by Tensorflow 1.8 / Tensorboard 1.8 (see https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/debug/debug_io_utils.cc). The CC++ code block is labeled as #ifndef ... #else directive block for URLs starting with grpc::// |
@ideenfix That code block was linked in the issue description. :) I'd still like some consistency between the documentation, the Tensorboard UI and the C++ error. |
To bypass the Windows incompatibility and run the debugger in WSL, are you just running the command line in it (i.e. tensorboard --logdir= --port --debugger port ) or do you have everything reinstalled for linux (i.e. python, tensorflow, CUDA toolkit, CuDNN, etc.)? I haven't seen anything that shows a fix for this would be (or would not be) coming to Windows , but the TensorBoard Debugger site doesn't have a mention of Windows 10 incompatibility. |
@faust22
Just running Tensorboard from CL, WSL has no support for GPU, so no cuDNN/CUDA. Tf, Tb and all other dependencies are installed in WSL.
From: Faust22
Sent: Thursday, May 31, 8:35 AM
Subject: Re: [tensorflow/tensorflow] gRPC debug URL scheme support for Windows (#runningL
To: tensorflow/tensorflow
Cc: LucaNaef, Mention
@naefl
To bypass the Windows incompatibility and run the debugger in WSL, are you just running the command line in it (i.e. tensorboard --logdir= --port --debugger port ) or do you have everything reinstalled for linux (i.e. python, tensorflow, CUDA toolkit, CuDNN, etc.)?
I haven't seen anything that shows a fix for this would be (or would not be) coming to Windows , but the TensorBoard Debugger site doesn't have a mention of Windows 10 incompatibility.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I see, thanks. It might be a bit rough without GPU support. I mainly want the 'health' section for NAN and INF value analysis, but there appears to be other ways to do this, although TensorBoard seemed good for this. Is there potential to see Windows support for TensorBoard debugger in the near future? (i.e. 1.9 or further off?) |
Same issue, on windows 10 with Tensorflow 1.9. |
I have the same issue, on windows 10 with Tensorflow 1.9. |
same issue on windows 7 tensorflow1.10 |
Same issue on Windows 10. Guess its not supported on windows.... |
@FurryFur As of this comment, it is explicitly not supported on Windows - that's why it's marked as a feature request. |
For what it's worth, the tensorboard debugger plugin appears to work pretty well with the Ubuntu 18.04 app on the Windows app store. I gave up on the original Ubuntu app over a year ago due to incredibly slow install times, but things have changed and it's much faster. I dropped miniconda on it, installed tensorflow, brought up tensorboard and everything is seeming to work in the browser. Figures crossed it keeps working without any surprises. Props to Microsoft for this sweet little app. |
I have tried tensorflow for deep learning in windows 10. However, facing the same issue "1 ops no flops stats due to incomplete shapes" with TypeError: 'UnimplementedError' object is not iterable, while trying to use Tensorflow debugger. Is there any solution? |
Is there any status on this one? I'm also receiving |
Still this Problem is not solved? |
@rvfischione, |
This issue has been automatically marked as stale because it has no recent activity. It will be closed if no further activity occurs. Thank you. |
@tilakrayal Substituting some of the calls in the above reproduction with their
I have no idea how much of the user base still uses V1 API, but I doubt this issue is still relevant. |
System information
Describe the problem
Incidentally, this is both a bug report and a feature request.
To reproduce the bug, run the following:
The following is the output:
It's clear that the error is being assigned to a variable instead of being raised. Furthermore, the behavior is only present when evaluating a variable; this is unexpected, as it has nothing to do with the session itself.
I came across this while trying to enable debugging via TensorBoard. After some digging, it appears that the error message originates from TensorFlow core code, so that's why this issue is here and not in the TensorBoard project. Is there any status on implementation of this feature? If not, could there be a log warning or some sort of feedback to reflect this? The TensorBoard modal at http://localhost:6006/#debugger gives no indication that it is platform-dependent.
The text was updated successfully, but these errors were encountered: