Build fail

this is relation of
https://github.com/otcshare/iotivity-node/issues/156

OK, so you're still having trouble downloading iotivity as part of the iotivity-node installation?
Please try to clone iotivity with this command:
git clone https://gerrit.iotivity.org/gerrit/iotivity

If that fails due to a networking issue, please fix the networking issue. Once that succeeds, so should installing iotivity-node.

I compare commit of https://gerrit.iotivity.org/gerrit/iotivity and https://github.com/iotivity/iotivity
and find it is same.
It  not a networking issue, it many be the  compatible issue or someother issue.
I replace the url and clone sucess, but also build fail.

Can you please post the newest failure?
On Thu, Oct 5, 2017 at 7:40 AM, liuwei000000<EMAIL_ADDRESS>wrote:

I compare commit of https://gerrit.iotivity.org/gerrit/iotivity and
https://github.com/iotivity/iotivity
and find it is same.
It not a networking issue, it many be the compatible issue or someother
issue.
I replace the url and clone sucess, but also build fail.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/otcshare/iotivity-node/issues/157#issuecomment-334357110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7k0ZB545pfblBeINiTYJ_3gLLM81lQks5spF3BgaJpZM4Puhyr
.

E:\iot\iotivity-node>npm i
<EMAIL_ADDRESS>install E:\iot\iotivity-node
node-gyp rebuild
E:\iot\iotivity-node>if not defined npm_config_node_gyp (node "D:\dev\nvm\v6.9.1
\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js"
rebuild ) else (node "" rebuild )
Warning: Missing input files:
E:\iot\iotivity-node\build..\generated\constants.cc
E:\iot\iotivity-node\build..\iotivity-installed
E:\iot\iotivity-node\build..\generated\functions.cc
E:\iot\iotivity-node\build..\generated\enums.cc
E:\iot\iotivity-node\iotivity-installed\lib\octbstack.dll
在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。
Building CSDK
Cloning into 'E:\iot\iotivity-node\iotivity-native'...
Note: checking out 'a532ef729f3d4836975615583b2d8c8a9de63c21'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again.
CUSTOMBUILD : warning : resource/csdk/resource-directory/SConscript has type 10
0644, expected 100755 [E:\iot\iotivity-node\build\csdk.vcxproj]
CUSTOMBUILD : warning : extlibs/sqlite3/SConscript has type 100644, expected 10
0755 [E:\iot\iotivity-node\build\csdk.vcxproj]
Cloning into 'E:\iot\iotivity-node\iotivity-native\extlibs\mbedtls\mbedtls'..
.
Note: checking out 'ad249f509fd62a3bbea7ccd1fef605dbd482a7bd'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at ad249f5... Fixes all.sh script for filesystem IO test build
Cloning into 'E:\iot\iotivity-node\iotivity-native\extlibs\tinycbor\tinycbor'
...
Note: checking out '31c7f81d45d115d2007b1c881cbbd3a19618465c'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at 31c7f81... Makefile: use installation logic compatible with ol
d make version
scons: Reading SConscript files ...
File "E:\iot\iotivity-node\iotivity-native\build_common\SConscript", line 4
0
print "\nError: Current system (%s) isn't supported\n" % host
                                                   ^

SyntaxError: invalid syntax
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targ
ets(171,5): error MSB6006: “cmd.exe”已退出，代码为 2。  System Windows_NT 6.1.7601
gyp ERR! command "D:\dev\nodejs\node.exe" "D:\dev\nvm\v6.9.1\node_modules
\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd E:\iot\iotivity-node
gyp ERR! node -v v6.9.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\b
in\npm-cli.js" "i"
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iotivity-node package
,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs iotivity-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls iotivity-node
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!  (D:\dev\nvm\v6.9.1\node_modules\npm\lib\utils\lifecycle.js:255:16)
87 verbose stack at emitTwo (events.js:106:13)
87 verbose stack at EventEmitter.emit (events.js:191:7)
87 verbose stack at ChildProcess. (D:\dev\nvm\v6.9.1\node_modules\npm\lib\utils\spawn.js:40:14)
87 verbose stack at emitTwo (events.js:106:13)
87 verbose stack at ChildProcess.emit (events.js:191:7)
87 verbose stack at maybeClose (internal/child_process.js:877:16)
87 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
88 verbose pkgid<EMAIL_ADDRESS>89 verbose cwd E:\iot\iotivity-node
90 error Windows_NT 6.1.7601
91 error argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\bin\npm-cli.js" "i"
92 error node v6.9.1
93 error npm v3.10.8
94 error code ELIFECYCLE
95 error<EMAIL_ADDRESS>install: node-gyp rebuild
95 error Exit status 1
96 error Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
96 error Make sure you have the latest version of node.js and npm installed.
96 error If you do, this is most likely a problem with the iotivity-node package,
96 error not with npm itself.
96 error Tell the author that this fails on your system:
96 error node-gyp rebuild
96 error You can get information on how to open an issue for this project with:
96 error npm bugs iotivity-node
96 error Or if that isn't available, you can get their info via:
96 error npm owner ls iotivity-node
96 error There is likely additional logging output above.
97 verbose exit [ 1, true ]

try again:
E:\iot\iotivity-node>npm i
<EMAIL_ADDRESS>install E:\iot\iotivity-node
node-gyp rebuild
E:\iot\iotivity-node>if not defined npm_config_node_gyp (node "D:\dev\nvm\v6.9.1
\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js"
rebuild ) else (node "" rebuild )
Warning: Missing input files:
E:\iot\iotivity-node\build..\generated\constants.cc
E:\iot\iotivity-node\build..\iotivity-installed
E:\iot\iotivity-node\build..\generated\functions.cc
E:\iot\iotivity-node\build..\generated\enums.cc
E:\iot\iotivity-node\iotivity-installed\lib\octbstack.dll
在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。
Building CSDK
fs.js:951
return binding.readdir(pathModule._makeLong(path), options.encoding);
^
CUSTOMBUILD : error : ENOENT: no such file or directory, scandir 'E:\iot\iotivi
ty-node\iotivity-native\out' [E:\iot\iotivity-node\build\csdk.vcxproj]
at Error (native)
at Object.fs.readdirSync (fs.js:951:18)
at findBins (E:\iot\iotivity-node\build-scripts\build-csdk.js:42:16)
at Object. (E:\iot\iotivity-node\build-scripts\build-csdk.js:2
05:18)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe fail
ed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (D:\dev\nvm\v6.9.1\node_modules\npm\no
de_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack at emitTwo (events.js:106:13)
gyp ERR! stack at ChildProcess.emit (events.js:191:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:215:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "D:\dev\nodejs\node.exe" "D:\dev\nvm\v6.9.1\node_modules
\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd E:\iot\iotivity-node
gyp ERR! node -v v6.9.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\b
in\npm-cli.js" "i"
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iotivity-node package
,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs iotivity-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls iotivity-node
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! E:\iot\iotivity-node\npm-debug.log
I see E:\iot\iotivity-node\build\csdk.vcxproj in its directory. But fail
The content of csdk.vcxproj are :
Debug x64 Release x64 {B2F1911F-2AF4-D7BA-AE41-DE1C7268B997} Win32Proj csdk true x64 Utility v140 $(ExecutablePath);$(MSBuildProjectDirectory)..\bin;$(MSBuildProjectDirectory)..\bin\ $(Configuration)\obj$(ProjectName)\ false true $(SolutionDir)$(Configuration)\ $(ProjectName) E:\iot\iotivity-node\iotivity-installed\include;..\node_modules\nan;E:\iot\iotivity-node\src;C:\Users\liu.node-gyp\6.9.1\include\node;C:\Users\liu.node-gyp\6.9.1\src;C:\Users\liu.node-gyp\6.9.1\deps\uv\include;C:\Users\liu.node-gyp\6.9.1\deps\v8\include;%(AdditionalIncludeDirectories) EnableFastChecks true false ProgramDatabase 4351;4355;4800;4251;%(DisableSpecificWarnings) false false false Disabled NotUsing NODE_GYP_MODULE_NAME=csdk;USING_UV_SHARED=1;USING_V8_SHARED=1;V8_DEPRECATION_WARNINGS=1;ROUTING_EP;WITH_DTLS;WIN32;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_HAS_EXCEPTIONS=0;DEBUG;_DEBUG;%(PreprocessorDefinitions) MultiThreadedDebug true true false Level3 E:\iot\iotivity-node\iotivity-installed\lib\octbstack.lib;kernel32.lib;user32.lib;gdi32.lib;winspool.lib;comdlg32.lib;advapi32.lib;shell32.lib;ole32.lib;oleaut32.lib;uuid.lib;odbc32.lib;DelayImp.lib;"C:\Users\liu.node-gyp\6.9.1$(Configuration)\node.lib" /ignore:4199 %(AdditionalOptions) true true iojs.exe;node.exe;%(DelayLoadDLLs) true true true true true MachineX64 E:\iot\iotivity-node\iotivity-installed\include;..\node_modules\nan;E:\iot\iotivity-node\src;C:\Users\liu.node-gyp\6.9.1\include\node;C:\Users\liu.node-gyp\6.9.1\src;C:\Users\liu.node-gyp\6.9.1\deps\uv\include;C:\Users\liu.node-gyp\6.9.1\deps\v8\include;%(AdditionalIncludeDirectories) NODE_GYP_MODULE_NAME=csdk;USING_UV_SHARED=1;USING_V8_SHARED=1;V8_DEPRECATION_WARNINGS=1;ROUTING_EP;WITH_DTLS;WIN32;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_HAS_EXCEPTIONS=0;DEBUG;_DEBUG;%(PreprocessorDefinitions);%(PreprocessorDefinitions) E:\iot\iotivity-node\iotivity-installed\include;..\node_modules\nan;E:\iot\iotivity-node\src;C:\Users\liu.node-gyp\6.9.1\include\node;C:\Users\liu.node-gyp\6.9.1\src;C:\Users\liu.node-gyp\6.9.1\deps\uv\include;C:\Users\liu.node-gyp\6.9.1\deps\v8\include;%(AdditionalIncludeDirectories) /MP %(AdditionalOptions) true false ProgramDatabase 4351;4355;4800;4251;%(DisableSpecificWarnings) false Speed true AnySuitable true true Full NotUsing NODE_GYP_MODULE_NAME=csdk;USING_UV_SHARED=1;USING_V8_SHARED=1;V8_DEPRECATION_WARNINGS=1;ROUTING_EP;WITH_DTLS;WIN32;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_HAS_EXCEPTIONS=0;%(PreprocessorDefinitions) MultiThreaded false true true false Level3 true /LTCG %(AdditionalOptions) E:\iot\iotivity-node\iotivity-installed\lib\octbstack.lib;kernel32.lib;user32.lib;gdi32.lib;winspool.lib;comdlg32.lib;advapi32.lib;shell32.lib;ole32.lib;oleaut32.lib;uuid.lib;odbc32.lib;DelayImp.lib;"C:\Users\liu.node-gyp\6.9.1$(Configuration)\node.lib" /ignore:4199 %(AdditionalOptions) true true iojs.exe;node.exe;%(DelayLoadDLLs) true true true UseLinkTimeCodeGeneration true true true true MachineX64 E:\iot\iotivity-node\iotivity-installed\include;..\node_modules\nan;E:\iot\iotivity-node\src;C:\Users\liu.node-gyp\6.9.1\include\node;C:\Users\liu.node-gyp\6.9.1\src;C:\Users\liu.node-gyp\6.9.1\deps\uv\include;C:\Users\liu.node-gyp\6.9.1\deps\v8\include;%(AdditionalIncludeDirectories) NODE_GYP_MODULE_NAME=csdk;USING_UV_SHARED=1;USING_V8_SHARED=1;V8_DEPRECATION_WARNINGS=1;ROUTING_EP;WITH_DTLS;WIN32;_CRT_SECURE_NO_DEPRECATE;_CRT_NONSTDC_NO_DEPRECATE;_HAS_EXCEPTIONS=0;%(PreprocessorDefinitions);%(PreprocessorDefinitions) true Document call call node "..\build-scripts\build-csdk.js" if %errorlevel% neq 0 exit /b %errorlevel% Building CSDK ..\iotivity-installed Document call mkdir "$(OutDir)" 2>nul & set ERRORLEVEL=0 & copy /Y "E:\iot\iotivity-node\iotivity-installed\lib\octbstack.dll" "$(OutDir)octbstack.dll" if %errorlevel% neq 0 exit /b %errorlevel% Copying E:\iot\iotivity-node/iotivity-installed/lib/octbstack.dll to $(OutDir)\octbstack.dll $(OutDir)\octbstack.dll

You need to use scons < 3.0.0.
On Thu, Oct 5, 2017 at 12:18 PM, liuwei000000<EMAIL_ADDRESS>wrote:

E:\iot\iotivity-node>npm i
<EMAIL_ADDRESS>install E:\iot\iotivity-node
node-gyp rebuild
E:\iot\iotivity-node>if not defined npm_config_node_gyp (node
"D:\dev\nvm\v6.9.1
\node_modules\npm\bin\node-gyp-bin....\node_modules\node-
gyp\bin\node-gyp.js"
rebuild ) else (node "" rebuild )
Warning: Missing input files:
E:\iot\iotivity-node\build..\generated\constants.cc
E:\iot\iotivity-node\build..\iotivity-installed
E:\iot\iotivity-node\build..\generated\functions.cc
E:\iot\iotivity-node\build..\generated\enums.cc
E:\iot\iotivity-node\iotivity-installed\lib\octbstack.dll
在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。
Building CSDK
Cloning into 'E:\iot\iotivity-node\iotivity-native'...
Note: checking out 'a532ef729f3d4836975615583b2d8c8a9de63c21'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again.
CUSTOMBUILD : warning : resource/csdk/resource-directory/SConscript has
type 10
0644, expected 100755 [E:\iot\iotivity-node\build\csdk.vcxproj]
CUSTOMBUILD : warning : extlibs/sqlite3/SConscript has type 100644,
expected 10
0755 [E:\iot\iotivity-node\build\csdk.vcxproj]
Cloning into 'E:\iot\iotivity-node\iotivity-native\extlibs
mbedtls\mbedtls'..
.
Note: checking out 'ad249f509fd62a3bbea7ccd1fef605dbd482a7bd'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at ad249f5... Fixes all.sh script for filesystem IO test build
Cloning into 'E:\iot\iotivity-node\iotivity-native\extlibs
tinycbor\tinycbor'
...
Note: checking out '31c7f81d45d115d2007b1c881cbbd3a19618465c'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at 31c7f81... Makefile: use installation logic compatible with
ol
d make version
scons: Reading SConscript files ...
File "E:\iot\iotivity-node\iotivity-native\build_common\SConscript", line
4
0
print "\nError: Current system (%s) isn't supported\n" % host
                                               ^

SyntaxError: invalid syntax
C:\Program Files (x86)\MSBuild\Microsoft.Cpp
v4.0\V140\Microsoft.CppCommon.targ
ets(171,5): error MSB6006: “cmd.exe”已退出，代码为 2。  System Windows_NT 6.1.7601
gyp ERR! command "D:\dev\nodejs\node.exe" "D:\dev\nvm\v6.9.1\node_modules
\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd E:\iot\iotivity-node
gyp ERR! node -v v6.9.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for
fsevents@
1.1.2: wanted {"os":"darwin","arch":"any"} (current:
{"os":"win32","arch":"x64"}
)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\b
in\npm-cli.js" "i"
npm ERR! node v6.9.1
npm ERR! npm v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp
rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm
installed.
npm ERR! If you do, this is most likely a problem with the iotivity-node
package
,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project
with:
npm ERR! npm bugs iotivity-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls iotivity-node
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!  (D:\dev\nvm\v6.9.1\node_
modules\npm\lib\utils\lifecycle.js:255:16)
87 verbose stack at emitTwo (events.js:106:13)
87 verbose stack at EventEmitter.emit (events.js:191:7)
87 verbose stack at ChildProcess. (D:\dev\nvm\v6.9.1\node_
modules\npm\lib\utils\spawn.js:40:14)
87 verbose stack at emitTwo (events.js:106:13)
87 verbose stack at ChildProcess.emit (events.js:191:7)
87 verbose stack at maybeClose (internal/child_process.js:877:16)
87 verbose stack at Process.ChildProcess._handle.onexit
(internal/child_process.js:226:5)
88 verbose pkgid<EMAIL_ADDRESS>89 verbose cwd E:\iot\iotivity-node
90 error Windows_NT 6.1.7601
91 error argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\bin\npm-cli.js"
"i"
92 error node v6.9.1
93 error npm v3.10.8
94 error code ELIFECYCLE
95 error<EMAIL_ADDRESS>install: node-gyp rebuild
95 error Exit status 1
96 error Failed at the<EMAIL_ADDRESS>install script 'node-gyp
rebuild'.
96 error Make sure you have the latest version of node.js and npm
installed.
96 error If you do, this is most likely a problem with the iotivity-node
package,
96 error not with npm itself.
96 error Tell the author that this fails on your system:
96 error node-gyp rebuild
96 error You can get information on how to open an issue for this project
with:
96 error npm bugs iotivity-node
96 error Or if that isn't available, you can get their info via:
96 error npm owner ls iotivity-node
96 error There is likely additional logging output above.
97 verbose exit [ 1, true ]
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/otcshare/iotivity-node/issues/157#issuecomment-334408748,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7k0YA5kQZahxo2DqhUMqTOBfGNVqRHks5spJ73gaJpZM4Puhyr
.

Before you try again, you should always git clean -x -d -f -f.

I update the scons 2.5.1
and run build, fails:
E:\iot\iotivity-node>npm i

<EMAIL_ADDRESS>install E:\iot\iotivity-node
node-gyp rebuild

E:\iot\iotivity-node>if not defined npm_config_node_gyp (node "D:\dev\nvm\v6.9.1
\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js"
rebuild )  else (node "" rebuild )
Warning: Missing input files:
E:\iot\iotivity-node\build..\generated\constants.cc
E:\iot\iotivity-node\build..\iotivity-installed
E:\iot\iotivity-node\build..\generated\functions.cc
E:\iot\iotivity-node\build..\generated\enums.cc
E:\iot\iotivity-node\iotivity-installed\lib\octbstack.dll
在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。
Building CSDK
fs.js:951
return binding.readdir(pathModule._makeLong(path), options.encoding);
^
CUSTOMBUILD : error : ENOENT: no such file or directory, scandir 'E:\iot\iotivi
ty-node\iotivity-native\out' [E:\iot\iotivity-node\build\csdk.vcxproj]
at Error (native)
at Object.fs.readdirSync (fs.js:951:18)
at findBins (E:\iot\iotivity-node\build-scripts\build-csdk.js:42:16)
at Object. (E:\iot\iotivity-node\build-scripts\build-csdk.js:2
05:18)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.runMain (module.js:604:10)
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe fail
ed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (D:\dev\nvm\v6.9.1\node_modules\npm\no
de_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:215:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "D:\dev\nodejs\node.exe" "D:\dev\nvm\v6.9.1\node_modules
\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd E:\iot\iotivity-node
gyp ERR! node -v v6.9.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\b
in\npm-cli.js" "i"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iotivity-node package
,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs iotivity-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls iotivity-node
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     E:\iot\iotivity-node\npm-debug.log

Please run git clean -x -d -f -f before running npm i!

I have run it

And were there errors? Was there an iotivity-native subdirectory after running git clean -x -d -f -f? If so, you must remove it. I know that Windows is terrible at releasing file locks, so you might even have to log out and log back in and run git clean -x -d -f -f again.

I see some 7zip error ,but try again, it  disappear.
wait a mins , I run again.

the full messages:
E:\iot\iotivity-node>npm i
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail o
n node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible
. Use 'npm ls graceful-fs' to find it in the tree.

<EMAIL_ADDRESS>install E:\iot\iotivity-node\node_modules\commitplease
node install

Detected an existing git commit-msg hook
Remove it and install this package again to install commitplease properly

<EMAIL_ADDRESS>postinstall E:\iot\iotivity-node\node_modules\spawn-sync
node postinstall

<EMAIL_ADDRESS>install E:\iot\iotivity-node
node-gyp rebuild

E:\iot\iotivity-node>if not defined npm_config_node_gyp (node "D:\dev\nvm\v6.9.1
\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js"
rebuild )  else (node "" rebuild )
Warning: Missing input files:
E:\iot\iotivity-node\build..\generated\constants.cc
E:\iot\iotivity-node\build..\iotivity-installed
E:\iot\iotivity-node\build..\generated\functions.cc
E:\iot\iotivity-node\build..\generated\enums.cc
E:\iot\iotivity-node\iotivity-installed\lib\octbstack.dll
在此解决方案中一次生成一个项目。若要启用并行生成，请添加“/m”开关。
Building CSDK
Cloning into 'E:\iot\iotivity-node\iotivity-native'...
Note: checking out 'a532ef729f3d4836975615583b2d8c8a9de63c21'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again.
CUSTOMBUILD : warning : resource/csdk/resource-directory/SConscript has type 10
0644, expected 100755 [E:\iot\iotivity-node\build\csdk.vcxproj]
CUSTOMBUILD : warning : extlibs/sqlite3/SConscript has type 100644, expected 10
0755 [E:\iot\iotivity-node\build\csdk.vcxproj]
Cloning into 'E:\iot\iotivity-node\iotivity-native\extlibs\mbedtls\mbedtls'..
.
Note: checking out 'ad249f509fd62a3bbea7ccd1fef605dbd482a7bd'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>

HEAD is now at ad249f5... Fixes all.sh script for filesystem IO test build
Cloning into 'E:\iot\iotivity-node\iotivity-native\extlibs\tinycbor\tinycbor'
...
Note: checking out '31c7f81d45d115d2007b1c881cbbd3a19618465c'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b <new-branch-name>

HEAD is now at 31c7f81... Makefile: use installation logic compatible with ol
d make version
scons: Reading SConscript files ...
*********************** Error ************************

                                               *

Please make sure that 7-zip is in your System PATH *

                                               *

Checking for POSIX Thread Support...no
*********************** Error ************************

                                               *

Please make sure that 7-zip is in your System PATH *

                                               *

HEAD is now at acf202a Fix stack corruption due to calling convention mismatc
h
*** Checking for presence of sqlite-amalgamation-3081101 ***
Download E:\iot\iotivity-node\iotivity-native\extlibs\sqlite3\sqlite-amalgama
tion-3081101.zip from https://www.sqlite.org/2015/sqlite-amalgamation-3081101
.zip
Downloading ...
Download E:\iot\iotivity-node\iotivity-native\extlibs\sqlite3\sqlite-amalgama
tion-3081101.zip from https://www.sqlite.org/2015/sqlite-amalgamation-3081101
.zip complete
Unpacking E:\iot\iotivity-node\iotivity-native\extlibs\sqlite3\sqlite-amalgam
ation-3081101.zip ...
scons: *** run command of the unpack builder for [TARBZ] archives is not set

can not extract files  Stop.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targ
ets(171,5): error MSB6006: “cmd.exe”已退出，代码为 2。  System Windows_NT 6.1.7601
gyp ERR! command "D:\dev\nodejs\node.exe" "D:\dev\nvm\v6.9.1\node_modules
\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd E:\iot\iotivity-node
gyp ERR! node -v v6.9.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok

npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\b
in\npm-cli.js" "i"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iotivity-node package
,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs iotivity-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls iotivity-node
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     E:\iot\iotivity-node\npm-debug.log

Is 7zip in your PATH?

No , how to solve it ?

Need 7-zip  install  manually？

Yes. You must install 7-zip and make sure it's on your PATH.

Now the error change:
...
inc']
Files path is ['E:\iot\iotivity-node\iotivity-native\resource\csdk\conn
ectivity\common\src\uarraylist.c', 'E:\iot\iotivity-node\iotivity-nativ
e\resource\csdk\connectivity\common\src\ulinklist.c', 'E:\iot\iotivit
y-node\iotivity-native\resource\csdk\connectivity\common\src\uqueue.c'
, 'E:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\com
mon\src\caremotehandler.c', 'E:\iot\iotivity-node\iotivity-native\resou
rce\csdk\connectivity\common\src\cathreadpool_pthreads.c', 'E:\iot\iot
ivity-node\iotivity-native\resource\csdk\connectivity\util\src\cautili
nterface.c', '.\adapter_util/caadapterutils.c', '.\adapter_util/cafragmenta
tion.c', '.\adapter_util/ca_adapter_net_ssl.c', '.\cablockwisetransfer.c',
'.\caconnectivitymanager.c', '.\cainterfacecontroller.c', '.\camessagehand
ler.c', '.\canetworkconfigurator.c', '.\caprotocolmessage.c', '.\caqueuein
gthread.c', '.\caretransmission.c', 'E:\iot\iotivity-node\iotivity-native
\resource\csdk\connectivity\src\ip_adapter\caipadapter.c', 'E:\iot\io
tivity-node\iotivity-native\resource\csdk\connectivity\src\ip_adapter\
caipserver.c', 'E:\iot\iotivity-node\iotivity-native\resource\csdk\conn
ectivity\src\ip_adapter\windows/caipnwmonitor.c']
*** Downloading Boost zip file (> 100MB). Please wait... ***
Download E:\iot\iotivity-node\iotivity-native\extlibs\boost\boost_1_60_0.zip
from http://downloads.sourceforge.net/project/boost/boost/1.60.0/boost_1_60_0
.zip?r=&ts=1421801329&use_mirror=iweb
Downloading ...
Download E:\iot\iotivity-node\iotivity-native\extlibs\boost\boost_1_60_0.zip
from http://downloads.sourceforge.net/project/boost/boost/1.60.0/boost_1_60_0
.zip?r=&ts=1421801329&use_mirror=iweb complete
*** Unpacking boost 1.60.0 zip file ... ***
Unpacking E:\iot\iotivity-node\iotivity-native\extlibs\boost\boost_1_60_0.zip
...
scons: done reading SConscript files.
scons: Building targets ...
Compiling out\windows\win32\amd64\release\resource\csdk\logger\src\logger.obj
logger.c
Compiling out\windows\win32\amd64\release\resource\csdk\logger\src\trace.obj
trace.c
Archiving out\windows\win32\amd64\release\resource\csdk\logger\logger.lib
Install file: "out\windows\win32\amd64\release\resource\csdk\logger\logger.li
b" as "out\windows\win32\amd64\release\logger.lib"
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocstack.obj
ocstack.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(132): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(147): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(162): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\coap_time.h(184): warning C4244: '=': conversion from 'double'
to 'coap_tick_t', possible loss of data [E:\iot\iotivity-node\build\csdk.vcxpro
j]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocpayload.o
bj
ocpayload.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocpayloadpa
rse.obj
ocpayloadparse.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocpayloadco
nvert.obj
ocpayloadconvert.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\occlientcb.
obj
occlientcb.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(132): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(147): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(162): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\coap_time.h(184): warning C4244: '=': conversion from 'double'
to 'coap_tick_t', possible loss of data [E:\iot\iotivity-node\build\csdk.vcxpro
j]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocresource.
obj
ocresource.c
E:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocobserve.o
bj
ocobserve.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(132): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(147): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\option.h(162): warning C4244: 'function': conversion from 'unsi
gned short' to 'uint8_t', possible loss of data [E:\iot\iotivity-node\build\csd
k.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\connectivity\lib\libcoap-4.1
.1\include\coap\coap_time.h(184): warning C4244: '=': conversion from 'double'
to 'coap_tick_t', possible loss of data [E:\iot\iotivity-node\build\csdk.vcxpro
j]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocserverreq
uest.obj
ocserverrequest.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\src\ocserverrequest.c(
60): warning C4716: 'ServerRequestTree_RBL_REMOVE': must return a value [E:\iot
\iotivity-node\build\csdk.vcxproj]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\occollectio
n.obj
occollection.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\oicgroup.ob
j
oicgroup.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\ocendpoint.
obj
ocendpoint.c
Compiling out\windows\win32\amd64\release\resource\csdk\stack\src\oicresource
directory.obj
oicresourcedirectory.c
Archiving out\windows\win32\amd64\release\resource\csdk\stack\octbstack_inter
nal.lib
Install file: "out\windows\win32\amd64\release\resource\csdk\stack\octbstack_
internal.lib" as "out\windows\win32\amd64\release\octbstack_internal.lib"
Creating 'out\windows\win32\amd64\release\resource\csdk\stack\octbstack_temp1
.def'
Creating 'out\windows\win32\amd64\release\resource\csdk\stack\octbstack_temp2
.def'
Creating 'out\windows\win32\amd64\release\resource\csdk\stack\octbstack_temp3
.def'
Creating 'out\windows\win32\amd64\release\resource\csdk\stack\octbstack.def'
Compiling out\windows\win32\amd64\release\resource\csdk\routing\src\routingut
ility.obj
routingutility.c
E:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
Archiving out\windows\win32\amd64\release\resource\csdk\routing\routingmanage
r.lib
Install file: "out\windows\win32\amd64\release\resource\csdk\routing\routingm
anager.lib" as "out\windows\win32\amd64\release\routingmanager.lib"
Compiling out\windows\win32\amd64\release\resource\csdk\security\provisioning
\src\pmutility.obj
pmutility.c
Compiling out\windows\win32\amd64\release\resource\csdk\security\provisioning
\src\credentialgenerator.obj
credentialgenerator.c
Compiling out\windows\win32\amd64\release\resource\csdk\security\provisioning
\src\otmcontextlist.obj
otmcontextlist.c
Compiling out\windows\win32\amd64\release\resource\csdk\security\provisioning
\src\ownershiptransfermanager.obj
ownershiptransfermanager.c
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : error C2220: warning treated as error - no 'object' file generated [E
:\iot\iotivity-node\build\csdk.vcxproj]
e:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]
scons: *** [out\windows\win32\amd64\release\resource\csdk\security\provisioni
ng\src\ownershiptransfermanager.obj] Error 2
scons: building terminated because of errors.
gyp ERR! build error
gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe fail
ed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (D:\dev\nvm\v6.9.1\node_modules\npm\no
de_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:215:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "D:\dev\nodejs\node.exe" "D:\dev\nvm\v6.9.1\node_modules
\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd E:\iot\iotivity-node
gyp ERR! node -v v6.9.1
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"}
)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "D:\dev\nodejs\node.exe" "D:\dev\nodejs\node_modules\npm\b
in\npm-cli.js" "i"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the iotivity-node package
,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs iotivity-node
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls iotivity-node
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     E:\iot\iotivity-node\npm-debug.log

E:\iot\iotivity-node\iotivity-native\resource\csdk\stack\include\internal\ocres
ource.h : warning C4819: The file contains a character that cannot be represent
ed in the current code page (936). Save the file in Unicode format to prevent d
ata loss [E:\iot\iotivity-node\build\csdk.vcxproj]

This seems to be the problem this time (code page vs. Unicode). I'm not 100% sure how to change that but setting your language to English (US) may help. Could you try that?

Is there a easy way to build.
Or released binary files

We do not distribute binary files. This is the easiest way I can think of.
I can try to change the language settings in Windows and see if I can
reproduce your error.

hi, all
I verified this issue on the windows 10 and different results are got with different OS version. e.g.: English version and Chinese version.
The following is return result:

Original Language
Switch to
Result

EN
EN
Pass

EN
CH
Pass

CH
CH
Fail

CH
EN
Fail


DWSpectrum container does not continue running

Using podman as a user to run docker.io/ptr707/dwspectrum as a rootless container results in a container that doesn't continue to run, unlike the docker.io/ptr707/dwspectrum-lsio image. This is on a Debian Bullseye (Testing) host with podman 3.0.1.
 I ran the same command as root (rootful container) but didn't notice different behavior. The container still did not continue to run in the background after issuing the command.
I've resorted to using the dwspectrum-lsio image which works but I'm curious why the non-LSIO image doesn't continue to run.

Hmm, I noticed that Nx "recently" made changes to their default docker startup, something I've not mimicked yet.
See:
https://github.com/networkoptix/nx_open_integrations/blob/master/docker/Dockerfile
vs.
https://github.com/ptr727/NxWitness/blob/main/NxWitness/Dockerfile
I personally use the LSIO non-root variant, but I'll try to update the non-LSIO versions to match the new Nx startup scheme.
And I assume you mean ptr727 not ptr707 ;)

Does the NxWitness/DW Spectrum assume that systemd is present to run the service? Is the issue with the non-LSIO variant that systemd is not properly supported in the container? I haven't dug into this in enough detail to be intelligent on this matter but this was my suspicion since the LSIO image runs S6 to manage in container processes.
And yes, ptr727 was what I intended and I've updated the original comment.

I changed the non-LSIO images to use a custom ENTRYPOINT to launch an entrypoint.sh script, i.e. no longer using systemd.
But, this will only work for root, i.e. root-tool needs to run as root.
The Nx reference docker script, adds the user to sudoers group to run the root-tool as sudo, I am not convinced that this is the right way to go from a security perspective, vs. separating root vs. non-root.
I have no experience with podman, but if you can't get LSIO to work with rootless podman, maybe you can try the Nx docker scripts?

The LSIO images work great with podman and I suspect it’s because they’re using s6 for process management. It’s the non-LSIO images that don’t seem to work.
With rootless podman, whether the command runs as root or a user inside the container is sort of immaterial since the container is both unprivileged and running as a user on the host. It’s certainly cleaner to run the entrypoint script directly as root.
I will try and test your changes out during the week. I have a feeling there was something wonky going on between the networkoptix server and systemd inside the container and that is why they decided to directly run the server instead of rely on the init system.

I have a feeling there was something wonky going on between the networkoptix server and systemd inside the container and that is why they decided to directly run the server instead of rely on the init system.

Running systemd in a container is an anti-pattern, and like they say, not the way to use docker, so in my opinion a welcome change.
The non-LSIO version may run as non-root, but the account only has context inside docker, it does not directly map to a host counterpart.
If LSIO version works I'd suggest you use it, for the user you specify using PUID maps to an actual user on the host, allowing granular file permission logic for the volume mappings.

Running systemd in a container is an anti-pattern, and like they say, not the way to use docker, so in my opinion a welcome change.

Absolutely. I’m guessing the ubuntu base images aren’t systemd containers and that’s the issue. It does seem like the LSIO base is the way to go here if you want an in-container process supervisor. I’ll definitely give the non-LSIO variant a try though to see if the issue appeared to be systemd.


UserAgentApplication.getAccount return type is incorrect

https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/508239004e8752e4446f75c02fa46557334b14e5/lib/msal-core/src/UserAgentApplication.ts#L1718
The correct return type is Account | null

@snebjorn We do not have strictNullChecks enabled in msal-core so this is not needed. Are you seeing a specific issue caused by this?

@snebjorn We do not have strictNullChecks enabled in msal-core so this is not needed. Are you seeing a specific issue caused by this?

const isAuthenticated = !!this.msalService.getAccount(); reports type true which is incorrect and will cause "expression is always true" errors later.
I'd suggest to turn it on cause it's my experience that 9/10 js errors are null or undefined related

Hmm guess there's some issues with a using a library that have --strictNullChecks false in an app that have --strictNullChecks true as one assumes null and the other doesn't

@snebjorn This is in our backlog to do but unfortunately don't have an estimate right now when msal-core may be updated as there are many changes that will need to be made to enable this. Newer libraries, like the upcoming msal-node, will have this enabled from the start. I'm going to close this but you can track #1097 for updates on this.

That's good to know. Happy coding :)


Support Github flavoured MarkDown task lists

Github supports task lists, as per this blog post:

Task Lists in GFM: Issues/Pulls, Comments

It allows you to write things like:
- [x] Completed task
- [ ] Pending task

Which looks like this:

[x] Completed task
[ ] Pending task

Currently, if you have a normal markdown list, say using a dash, when you hit enter the next line automatically gets a dash too.
The feature would be that when a task list is detected (either - [ ] or - [x]), on the new line a - [ ] should be inserted.
This would simplify working with GitHub flavoured markdown as task lists are increasingly common.

:+1:

:+1:

I've wanted the same thing for a while now. I'm considering learning a new language just to add this myself (not that I have the free time to do it). Anyone interest in developing this feature? @ttscoff


// - - - Here are the lines showing the issue - - -
Reflect.setField(chains[chains.length - 1], "number", 555);
Reflect.setField(chains[chains.length - 2], "data", data);
Reflect.setField(chains[chains.length - 3], "as_array", [data]);
...

Actual result:
...
// - - - Here are the lines showing the issue - - -
Reflect.setField(chains[chains.length - 1], "number", 1);
Reflect.setField(chains[chains.length - 2], "data", 2);
Reflect.setField(chains[chains.length - 3], "as_array", 3);
...

The expression in the array index is somehow polluting the RHS value.

Ah, I've narrowed it down to the array access. This produces the expected result:
      chains[0]["number"] = 456;
      chains[0]["an_array"] = [dat];

But this does not:
      chains[chains.length-2]["number"] = 456;
      chains[chains.length-2]["an_array"] = [dat];

It produces:
  Reflect.setField(chains[chains.length - 2], "number", 2);
  Reflect.setField(chains[chains.length - 2], "an_array", 2);

After just a quick glance at the code, I'm confused how rvalue is a member variable of Writer.hx, (though here and there it's locally scoped, yikes) while Writer uses recursive writeExpr calls, some of which alter rvalue. How is this not colliding all over the place?

SlavaRa (maintainer) is away till next week. He told me he will be able to check issues on next week.

Thanks for the note. Luckily it's not urgent for me. :) It's only happened once and it's easy to fix by hand.


❓ Question: Email / Webhook notification on share update

🙋♂ Question
Hey, just a general question:
Has anyone here ever thought it would be a good idea to also allow email / webhook notifications when a share is updated (specifically when new ones are added)?

There is already a feature request #88 for that. Feel free to participate in the discussion there :)


Issue in CONTRIBUTING.md file

Current State
The link to newcomers welcome guide is redirecting towards the deleted docs link.
Desired State
The link should redirect to the correct docs link or the link should be removed from the text.

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@leecalcote @UtkarshMishra12  can I work on this one?

@leecalcote  any updates?

Here you go @VedRatan 🚀


Support tabs as whitespace

See https://github.com/elixir-makeup/makeup_erlang/pull/29 for more info

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


typo in AngularFireMessaging (messaging.md)

Version info

Angular: 6.1.7
Firebase: 5.5.0
AngularFire: 5.0.0
Other (e.g. Ionic/Cordova, Node, browser, operating system):
How to reproduce these conditions
Failing test unit, Plunkr, or JSFiddle demonstrating the problem
It's just a typo in one of your markdown files

Steps to set up and reproduce

Sample data and security rules
<-- include/attach/link to some json sample data (or provide credentials to a sanitized, test Firebase project) -->
Debug output
** Errors in the JavaScript console **
** Output from firebase.database().enableLogging(true); **
** Screenshots **
Expected behavior
No typo

Actual behavior
Typo

https://github.com/angular/angularfire2/blame/master/docs/messaging/messaging.md#L18
This reference should be to AngularFireMessagingModule and not AngularFireStorageModule

@jamesdaniels when the documentation says AngularFireMessaging is not compatible with the Angular Service Worker does that mean there's a technical incompatibility?
I just tried combining both service workers in a combined-worker.js
importScripts('ngsw-worker.js');
importScripts('firebase-messaging-sw.js');

And register that one in my AppModule
AngularFireModule.initializeApp(environment.firebase),
AngularFireMessagingModule,
ServiceWorkerModule.register('combined-sw.js', { enabled: environment.production })

Everything seems to be working ok (at least on my early smoke tests). I am missing some technical details in my solution? Am I oversimplifying the incompatibility between both service workers?


Bug with no-unnecessary-duplication rule

The rule triggers on this code:
guard({
  source: calendarAviaFormService.$aviaForm,
  clock: calendarAviaFormService.submitted,
  filter: (state) =>
    Boolean(state && isValidDirection(state.origin, state.destination)),
  target: drawAttention,
});

It must not.

Here too:
guard({
  source: promocodeModel.$verifyError,
  clock: [promocodeChanged, promocodeInputBlurred],
  filter: Boolean,
  target: promocodeModel.verifyErrorReset,
});

One more case:
guard({
  source: [
    aviaFormService.$aviaForm,
    $backendFilters,
    currencyService.$currency,
  ],
  clock: [$backendFilters, pricesPublicApi.allPricesShown],
  filter: $isAviaFormValidForPrices,
  target: requestLatestPricesFx,
});


[Fix] Make receiver verifications optional

Receiver verifications is an optional field after changes introduced in https://stellarorg.atlassian.net/browse/SDP-1222.

stellar-disbursement-platform-frontend-preview is available here:http://sdp-frontend-pr178.previews.kube001.services.stellar-ops.com/


docs/usage.md: correct grammatical error

'...a way connect them' -> '...a way to connect them'
Signed-off-by: Tree Davies<EMAIL_ADDRESS>
Before sending a pull request, please review Contribution Guidelines:
https://github.com/google/syzkaller/blob/master/docs/contributing.md

Thanks!


Multiple tabs support

Allow:

close tab
open new tab
switch between tabs
drop (clear) stream of tab

basic support is done with 1.7.1


small fixes needed to ASLLVD data

For ID 5220, the handshapes on the dominant and non-dominant hands (both start and end) need ti be reversed.  They should be the same as for the other 3 examples.  Thanks.

fixed - CN

For (K)KITCHEN   iD539 Add + in gloss:  should be "(K)KITCHEN+"

For ADVISE/INFLUENCE
ID 846 needs one +.     Should be ADVISE/INFLUENCE+
ID 848 needs two +'s.    Should be ADVISE/INFLUENCE++

For again, we need a few more plusses:
874   Should be glossed as AGAIN++  (rather than AGAIN)
876  Should be glossed  AGAIN+  (rather than AGAIN)

ID 39158has an extra plus:
Should be ACT* (ACT+AGENT) - rather than ACT* (ACT++AGENT)

The same change needs to be made to the other elements associated with this compound, i.e., 39159 and 39302:

ACT+(1h)AGENT should be its own main entry.  So we should have
ACT+AGENT

ACT+AGENT

ACT+(1h)AGENT

ACT+(1h)AGENT

Could you please REMOVE all plus signs here?

So 6032 and 6033 should just be "NERVOUS"

This is complete

Everything fixed EXCEPT for the 5th comment from the top.

This has been resolved

thank you!

I thought I checked ACT+(1h)AGENT to make sure it was its own entry, and it had seemed to be fixed:
ACT+(1h)AGENT should be its own main entry. So we should have
ACT+AGENT

ACT+AGENT

ACT+(1h)AGENT

ACT+(1h)AGENT

However, now there is a new problem:  The entry under ACT+(1h)AGENT has disappeared.
And it has also disappeared from the places where it should be occurring with parts of that compound,
although I had previously verified that these also had been fixed.

The only remaining issue here is the disappearance of ACT+(1h)AGENT.

I believe this occurs only on the non-dominant hand, which explains why it is currently not showing up at all in the sign bank.


Upgrade to Node 20

Node 16 has reached its end of life. All GitHub actions to run on Node 20 by Spring 2024.

Any progress on this issue?

Part of PR: https://github.com/Azure/functions-container-action/pull/52


Testnet gas price issues

Andrew is having trouble submitting new listings, with Metamask saying to increase the gas price. We currently have hardcoded gaslimit (in another open issue). Need to figure this out.

Hasn't been an issue in months, so closing.


Update imoduleconfiguration.yml

Minor update to documentation

Docs Build status updates of commit ea23be0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

SP-Framework/sp-module-interfaces/imoduleconfiguration.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Sync testing Dokku version with DDS Dockerfile

Part of https://github.com/plotly/streambed/issues/13621
@gzork Please review.

It was on the checklist for https://github.com/plotly/streambed/issues/13621 (and it will be on next quarter's checklist too!)


Added cloudflare captcha support

Blocked. Need to test with active domain for captcha support. Need other PRs merged.

See https://community.cloudflare.com/t/allow-localhost-or-127-0-0-1-as-acceptable-domains-for-turnstile/423897


fix: use automatic runtime

i've removed import react in all places and
added the automatic runtime option for babel
adjusted the includes to work better for mono repo (based on expo webpack config)

📦 Published PR as canary version: 0.0.8-canary.13.d8d70a6.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

@axeldelafosse I think I might have solved it this time, testing it on your repro.

Yes! Good job man! Thank you for fixing this 🥳
https://github.com/axeldelafosse/storybook-rnw-monorepo/commit/32fdf956d46fe152f0192878179e60bb14a6c907


Community Expansion 'Content Pack'

We should set the 'contentCopyright' and 'contentPack' fields in definitions created by CE.
We may need to allow other mods to provide their own values if using CE infrastructure.
Suggestions is to base on SorcererUpdate which is in 'automaticallyUnlockedContentPacks'

as content packs only appear on some things and not others (classes, subclasses and not spells etc) if you want to cover spells and similar you might need to consider :

AddTagAsNeeded in tagsDefinitions.cs
EnumerateTags and TagsMap in GuiSpellDefinition.cs/GuiPowerDefinition.cs/GuiMonsterDefinition.cs/GuiItemDefinition.cs etc

looking at the WarList tag might be useful because that is related to subset of spells

@DubhHerder Working on this on this branch
We have

Please review the code.
Can you think of anything else.


Improve some code format.

Coverage remained the same at 93.489% when pulling 937f15cfa8bb4dc6b3ea53c27365d484a5925708 on weideng:master into c342b67563f524720d07756736654e929812a6d1 on 75team:master.


"Carthage update" not building for iOS on master branch (Swift 3 / XCode 8)

when i run carthage on the master branch it doesn't build for iOS.
i see it building the scheme "swifterios" but there is no iOS folder under carthage/build.

Building worked for me with version 1.3.2


Help to debug "Accessing nonexistent addons channel" error that appears with 3.2.10

Hi there,
We use storybook along argos-ci to perform some visual regression testing. Since the release of 3.2.10, our build break with this error: Accessing nonexistent addons channel.
I have a hard time understanding what is the change causing this. We were using 3.2.6 for the addons lib and the warning was already here.
Here is the code that glue storybook with argos: https://github.com/algolia/react-instantsearch/blob/master/test/regressions/tests.js
I read some stuff about mocking the channel like storyshots does, I tried to mimic it but without any luck.
Does someone has any ideas?

Hey @mthuret,
Please check if all the addons you're using are updated and are using the same version of @storybook/addons.

@ndelangen I'm having the same issue. Not sure if it is related to this problem but in my case (the storybook-router development) the addon versions within the example app (cra-kitchen-sink) and within my addon are the same. What surprised me is that if I use the storybook-router version from npm (instead of the linked one) everything works fine. I can of course provide the code if it might help.

@ndelangen yes that was it because we're using renovate for updating our deps. I group the update and everyting is now fine. I'm closing this.
@gvaldambrini feel free to reopen this one or a new one if you have more details on your issue.

I have this problem after update to 3.1.12

The only 3 addons I'm using are these, and I'm getting the same error...

Had this happening for me too, all dependencies were at 3.2.13, so I looked into the each dependency and saw that they were relying on @storybook/addons, which wasn't a part of my package.json. So for me, doing an npm install -D @storybook/addons resolved the issue.

@colinswilliams That should not be necessary to add as a dependency.. If you remove it now, it should continue to work.
If you have this problem, first thing to try is to remove node_modules and re-install. I my experience this solves the problem 99% of the time.

@colinswilliams Are you using a lockfile?

Ooph! Good call, forgot about. Wound up deleting node_modules, and deleted the package.lock, removed @storybook/addons from package.json, and it worked. I'm assuming that when we added knobs later in the project, the lockfile referenced different versions of addons, giving us the error.

The joy of lockfiles ey? 😒
I'm happy this resolved the problem.

Did something happen with v3.2.15?  I tried deleting package-lock.json, deleting node_modules, and installing @storybook/addons and nothing is getting rid of this danged non existent channels error.

reinstall all dependencies and keep all addons with same version(3.2.15), still not work,:(

I have the same issue currently

Ran into this as well. Removing node_modules and package-lock.json, then re-running npm install worked for me.

I just fought with this same issue for the past few hours. Luckily, I had success with @petekp’s solution.

See https://github.com/storybooks/storybook/issues/1981#issuecomment-345193670

Played with deleting files, reinstalling, etc and made the local version work. But the CI build with VSTS using a custom agent that builds with fresh versions of the files using npm.cmd it results in no add-ons panel every time.

@TroySchmidt I'm real sorry you're experiencing these issues, We're working hard resolving the issue, but it's a non-trivial problem to solve.
@Hypnosphi has proposed a solution that involves moving the dependency of the @storybook/addons package to a peerDependency.

@Hypnosphi @ndelangen update on using alpha.4 it is back to building locally with the panels showing.  But now I am getting a undefined error in KnobManager when it is trying to _this.channel.emit('addon:knobs:setKnobs',...
The actions panel is working properly.

if still you facing the same issue , try this showAddonPanel: false, in config.js


Update shoot creation framework to support HA

How to categorize this PR?

/area testing high-availability
/kind enhancement
What this PR does / why we need it:
Currently Shoot creation framework only creates shoot of non-HA, this PR is to enhance the shoot creation framework adding HighAvailability config for the shoot creation.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note:

/assign

/cc @hendrikKahl

Closing the PR, other colleague will work on this.


WIP: Don't attempt to register overloads that aren't for this target in BaseContext

Based on #9447, which this PR needs for correctness, but only the latest commit (0ad866f) is novel to this PR.
This PR is currently only to test on CI and see if anything fails, not for review.

gpuci run tests

gpuci run tests

gpuci run tests

gpuci run tests


Open Collective itself shows as pending

When submitting an expense to opencollective.com/opencollective it shows the collective as pending

Looks like this was fixed in https://github.com/opencollective/opencollective-frontend/blob/5605fe280f0d8b3f81df4e8e1bc74d6deca815d7/components/expenses/ExpenseInfoSidebar.js#L67 but not in https://github.com/opencollective/opencollective-frontend/blob/5605fe280f0d8b3f81df4e8e1bc74d6deca815d7/components/expenses/MobileCollectiveInfoStickyBar.js#L69.
We could push a quick fix in the frontend, but it sounds like we may want to move this condition to the API isApproved resolver to prevent similar issues in the future? cc @znarf


Add operator for v:"key"

This script errors on master with ldpl-temp.cpp:218:6: error: no viable overloaded operator[] for type       'ldpl_str_vector' but works with this PR:
DATA:
v is text vector
z is number vector

PROCEDURE:
store "Bart" in v:"name"
display v:"name" crlf

store 123 in z:"header"
store 987 in z:"footer"
display z:"footer"

Adding operator overloads fixes it for me but I'm not sure if there is a better way to go from literals to strings in C++.

Thank you very much!

Sorry, I wasn't thorough enough and I broke it.
DATA:
z is number vector

PROCEDURE:
store 222 in z:0

ldpl-temp.cpp:223:6: error: use of overloaded operator '[]' is ambiguous (with
      operand types 'ldpl_num_vector' and 'int')
VAR_Z[0] = 222;

I'll get a patch together.

This fixes it - does that look right?
--- a/src/ldpl_lib.cpp
+++ b/src/ldpl_lib.cpp
@@ -29,6 +29,9 @@ struct ldpl_num_vector{
     ldpl_number& operator [] (ldpl_number i) {
         return inner_map[to_string(i)];
     }
+    ldpl_number& operator [] (int i) {
+        return inner_map[to_string(i)];
+    }
     ldpl_number length() {
         return (int) inner_map.size();
     }
@@ -51,6 +54,9 @@ struct ldpl_str_vector{
     string& operator [] (ldpl_number i) {
         return inner_map[to_string(i)];
     }
+    string& operator [] (int i) {
+        return inner_map[to_string(i)];
+    }
     ldpl_number length() {
         return (int) inner_map.size();
     }


Update used-by.yml to explicit committer

I am not sure why every used-by pull request has my user commit. see #279
It may have used my personal token somewhere but I don't see it. Maybe I need to explicit committer? Just a try.

See author in peter-evans/create-pull-request action inputs