Linus Norton
Linus Norton
I'm also having this problem. Is it possible that npm is using the standard version of node and building dependencies against the wrong API? I'm not sure what the solution...
Where is the npm bundled with node-nightly located?
Weird, it doesn't seem to be in there or `/usr/lib/node_modules/node-nightly/` on my linux box
I am also getting this issue - let me know if you find a solution
@XiaoningLiu why does it expect that? The README.md says the default key is: ```Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==``` Edit: I tried ``` curl -X PUT http://127.0.0.1:10000/devstoreaccount1/pictures?restype=container -H "Authorization: SharedKey devstoreaccount1:/S7T6ds2y+Gd7wYbOo7ljAx6dJCs0ub4jjvCFkOju9s=" ``` But still get...
Can you point me to the documentation on this. Surely curl is the easiest way to see what is actually going on?
@XiaoningLiu any update on this it's preventing us from using the new version of azurite
@vojtechhabarta is there a technical issue at play here? In theory it looks like a one-to-one mapping of static final to static const, are there any edge cases? Edit if...
What I've done is a bit of a hack but it works for my use case. I think the best solution would be an enum as you suggest
Resolved in 0.10.4