qile222
qile222
@yorkie seems node-x509 can not make compatable with Node v10.7.0
@yorkie worked with Node v8.10.0
todo list: - [ ] provide platform tools for app packaging - [ ] app only need to provide API level to confirm whether it works properly, the version of...
[dump.zip](https://github.com/Rokid/ShadowNode/files/2212659/dump.zip) @algebrait
so the upper limit of download is only 28KB？ is there any testing for upload upper limit?
Is this path `/my/toolchain/dir/file` correct ?
Use `uname -a` to determine your architecture then download the right toolchain
```js iotjs_string_t iotjs_jval_as_string(jerry_value_t jval) { IOTJS_ASSERT(jerry_value_is_string(jval)); jerry_size_t size = jerry_get_string_size(jval); if (size == 0) return iotjs_string_create(); char* buffer = iotjs_buffer_allocate(size + 1); jerry_char_t* jerry_buffer = (jerry_char_t*)(buffer); size_t check = jerry_string_to_char_buffer(jval,...
but the buffer is allocated in [iotjs_buffer_allocate](https://github.com/Rokid/ShadowNode/blob/0f398b037b80ea6624fef62ca723082b70417fb9/src/iotjs_util.c#L79-L83) which is allock from heap rather than stack
so my point is `iotjs_jval_as_string` returns the data block, so we don't need to alloc every time and no need to free it manually