You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on a smoke test for t2-compiler, I discovered the path to leveldown binary was not found in ~/.tessel/binaries/leveldown-1.4.3-Release/Release/leveldown.node. Instead it was located in ~/.tessel/binaries/leveldown-1.4.3-Release/package/build/Release/leveldown.node.
Should we use path.resolve before trying to copy the source binary to the temp project path?
How do generally search for those target binaries?
The text was updated successfully, but these errors were encountered:
I will take a look at this as soon as I can (probably Wednesday). I have a pretty good idea of what needs to be fixed, I just need time to work through it.
I'm going to hold off on this for now because the binary isn't available anymore and was also built incorrectly (according to @reconbot). I just did a local npm install and the path matched the one that would be expected.
While working on a smoke test for t2-compiler, I discovered the path to
leveldown
binary was not found in~/.tessel/binaries/leveldown-1.4.3-Release/Release/leveldown.node
. Instead it was located in~/.tessel/binaries/leveldown-1.4.3-Release/package/build/Release/leveldown.node
.Should we use
path.resolve
before trying to copy the source binary to the temp project path?How do generally search for those target binaries?
The text was updated successfully, but these errors were encountered: