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.

error: module importing failed: invalid pathname

See original GitHub issue

Do we need to update brew after deb751e596ad74425a1b293d7b98b625cac9d94d? Currently running brew update; brew install chisel doesn’t fetch latest, so command script import /usr/local/opt/chisel/libexec/fbchisellldb.py path doesn’t resolve, since the installed file is still called fblldb.py.

Thought could install head, but doesn’t seem like this is working. I can manually resolve the path to fblldb.py in my ~/.lldbinit, but wanted to see what’s the right way of doing this?

% brew install --head chisel
Warning: chisel  is already installed
The currently linked version is 2.0.0
You can use `brew switch chisel ` to link this version.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

3reactions
zkhalapyancommented, May 4, 2020

Alright, seems like I got what happened:

  • Python 3 support was in 2.0.0, but xrange fix (d5f155d) wasn’t included, so it’s still breaking 😢
  • There hasn’t been a new release since the naming change (deb751e) and therefore brew vs. repo are out of sync.

I would recommend making a new minor release 2.0.1 with the new commits; to make it simple, I have drafted the release notes 😎maybe @kolinkrewinkel or @kastiglione could take up on it! 🙏

Release Name: It’s Not Halting (2.0.1)

Pushing a minor release to fix a Python 3 issue (d5f155d) as well as to sync brew with latest naming convention (deb751e), see below for more details:

  • Replace xrange with range to fix Python 3 issue (d5f155d) - thanks to @kastiglione!
  • Renaming all fblldb* to fbioslldb* to avoid conflict with lldb (deb751e) - thanks to @aadsm
  • New copy command that can be used to copy any NSURL or NSData to the host machine (0c9ee31) - awesome new tool by Chris Ellsworth.

Once a release is created, need to update homebrew formula, similar to this: https://github.com/Homebrew/homebrew-core/commit/b12704fb179a822b406669faff020cfb5e4e273e

1reaction
kolinkrewinkelcommented, Aug 11, 2020

I’ll try and get an update to brew out later today, thanks for the reminder!

Read more comments on GitHub >

github_iconTop Results From Across the Web

error: module importing failed: in… | Apple Developer Forums
error : module importing failed: invalid pathname ... I don't know what this error is and I've been trying go fix it for...
Read more >
Removed Realm, but still getting this error: module importing ...
With the advent of Xcode 11, I started seeing this error: error: module importing failed: invalid token (rlm_lldb.py, line 37) File ...
Read more >
Xcode 11 Error Cant Find Solution - module importing failed
First line in the output is "error: module importing failed: invalid pathname" for a command line tool project. I've reduced it to nothing...
Read more >
error: module importing failed: invalid pathname - 简书
不好意思,标题有点长了,今天拾起了一个老项目,调试了一下,出现如下错误。 惯例Google了一下,搜索的关键字为:... Chefil阅读3,101评论1赞3.
Read more >
Announcing LLDB for VSCode - #20 by vadimcn
Does anyone else get this error immediately after launching or trying to attach? error: module importing failed: No module named adapter
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