question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

TypeError: run() got an unexpected keyword argument 'flags_parser'

See original GitHub issue

I keep getting this error:

TypeError: run() got an unexpected keyword argument ‘flags_parser’

My env:

  • OS Platform and version (e.g., Linux Ubuntu 16.04) Ubuntu 16.04
  • Python version (e.g. 2.7, 3.5) 3.5.2
tensorboard                   1.10.0                 
tensorflow-gpu                1.10.1                 
tensorflow-tensorboard        0.4.0                  
tf-nightly                    1.11.0.dev20180917     
tf-nightly-gpu                1.11.0.dev20180917     

I recently removed tensorflow and installed tensorflow-gpu, now i’m getting this error whenever I try to run tensorboard --logdir=~/my/path, even if i try a simple tensorboard --help:

screenshot from 2018-09-18 01-06-47

tensorflow itself is working fine, i’m only getting this error when i run tensorboard

I didn’t find any similar issue on StackOverflow so i’m asking here, a little help would be awesome, thanks

Issue Analytics

  • State:open
  • Created 5 years ago
  • Comments:5

github_iconTop GitHub Comments

1reaction
nfeltcommented, Sep 18, 2018

I assume you also have tb-nightly installed? It’s our nightly build and it’s a dependency of tf-nightly so you’d pick it up automatically if you installed tf-nightly.

You can fix this issue by installing absl-py>=0.4.0. It was an unintentional breakage in our nightly build and should be resolved by tomorrow’s tb-nightly release.

Also, FYI, it’s generally not a good idea to have multiple versions of tensorflow (aka tensorflow-gpu, tf-nightly, and tf-nightly-gpu) installed to the same pip environment. They all share the same import tensorflow namespace, so installing one will actually clobber files in whatever one is already there, since pip is not very smart about managing this kind of collision.

The same goes for TensorBoard - it’s best to install just tensorboard or tb-nightly but not both. You can also uninstall tensorflow-tensorboard - it’s an old name for our pip package and won’t receive any new updates.

0reactions
Joyli66commented, Apr 26, 2019

@nfelt It works!!! Thank you! ^_^

Read more comments on GitHub >

github_iconTop Results From Across the Web

Tensorflow: TypeError: run() got an unexpected keyword ...
I get this error when trying to add the feedis_dict to a self.sess.run command: Traceback (most recent call last): File "spritegen.py", ...
Read more >
Bug #1302544 “unexpected keyword argument 'flags'”
Using the current version from the repository (r:675) is get this on Debian ... TypeError: sub() got an unexpected keyword argument 'flags'.
Read more >
TypeError: copy() got an unexpected keyword argument 'deep'
currently we have 2 prediction model and we setup the prediction model in the next recipe # setup efficiency function efficiency = lambda...
Read more >
TypeError: Random() got an unexpected keyword argument ...
I'm able to build a model but get an error when running sample_posterior_predictive. Note that I specify cores = 1 as recommended here....
Read more >
moveto() got an unexpected keyword argument 'scale ...
FMRIPREP: TypeError: moveto() got an unexpected keyword argument 'scale' ... result[“result”] = node.run(updatehash=updatehash)
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found