We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The download of a single file is successful but the command terminate with an error message.
I tried the following command line
bl dataset download 5b2fb4e6d821b2004f9341ed
on two different architectures: MacOS and Linux.
On Karst with Red Hat Enterprise Linux Server release 6.10 (Santiago) and nodejs version 8.9.4 the diagnostic message is the following
Error: "toString()" failed
On MacOS 10.13.06 and nodejs version 8.12.0 the diagnostic message is the following
<--- Last few GCs ---> [15875:0x103001400] 445883 ms: Mark-sweep 47.6 (53.3) -> 47.6 (53.3) MB, 41.2 / 0.0 ms allocation failure GC in old space requested [15875:0x103001400] 445927 ms: Mark-sweep 47.6 (53.3) -> 47.6 (53.3) MB, 44.0 / 0.0 ms last resort GC in old space requested [15875:0x103001400] 445984 ms: Mark-sweep 47.6 (53.3) -> 47.6 (53.3) MB, 57.5 / 0.0 ms last resort GC in old space requested <--- JS stacktrace ---> ==== JS stack trace ========================================= Security context: 0x3770e5a5879 <JSObject> 1: stringSlice(aka stringSlice) [buffer.js:556] [bytecode=0x377a2369f49 offset=11](this=0x3779a4822d1 <undefined>,buf=0x37768c4b201 <Uint8Array map = 0x377ef4c3f99>,encoding=0x3779a4822d1 <undefined>,start=0,end=748165120) 2: toString [buffer.js:633] [bytecode=0x377a2369b99 offset=145](this=0x37768c4b201 <Uint8Array map = 0x377ef4c3f99>,encoding=0x3779a4822d1 <undefined>,start=0,end=74816... FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory 1: node::Abort() [/usr/local/bin/node] 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/usr/local/bin/node] 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/usr/local/bin/node] 4: v8::internal::Factory::NewRawTwoByteString(int, v8::internal::PretenureFlag) [/usr/local/bin/node] 5: v8::internal::Factory::NewStringFromUtf8(v8::internal::Vector<char const>, v8::internal::PretenureFlag) [/usr/local/bin/node] 6: v8::String::NewFromUtf8(v8::Isolate*, char const*, v8::NewStringType, int) [/usr/local/bin/node] 7: node::StringBytes::Encode(v8::Isolate*, char const*, unsigned long, node::encoding, v8::Local<v8::Value>*) [/usr/local/bin/node] 8: void node::Buffer::(anonymous namespace)::StringSlice<(node::encoding)1>(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node] 9: v8::internal::FunctionCallbackArguments::Call(void (*)(v8::FunctionCallbackInfo<v8::Value> const&)) [/usr/local/bin/node] 10: v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node] 11: v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node] 12: 0x2763c74842fd
The text was updated successfully, but these errors were encountered:
Thanks.
I believe this is related to this issue
request/request#2826
.. but I couldn't quite figure out what's causing this issue. I will investigate.
Sorry, something went wrong.
No branches or pull requests
The download of a single file is successful but the command terminate with an error message.
I tried the following command line
on two different architectures: MacOS and Linux.
On Karst with Red Hat Enterprise Linux Server release 6.10 (Santiago) and nodejs version 8.9.4 the diagnostic message is the following
On MacOS 10.13.06 and nodejs version 8.12.0 the diagnostic message is the following
The text was updated successfully, but these errors were encountered: