Using gatsby-cli to install tutorial with Node 12+ (12.4.0) with npm 6.9 in nvm 0.34.0 on MacOS OSX fails

Hi! I've been trying to hammer at getting this up and running using the command
gatsby new my-site https://github.com/justinformentin/gatsby-v2-tutorial-starter

But when I run the command, I get errors pointing to issues with `fsevents`.
van-wboye01-mac:locomath_gatsby wboyer$ gatsby new my-site https://github.com/justinformentin/gatsby-v2-tutorial-starter
info Creating new site from git:

Cloning into 'my-site'...
remote: Enumerating objects: 319, done.
remote: Total 319 (delta 0), reused 0 (delta 0), pack-reused 319
Receiving objects: 100% (319/319), 2.18 MiB | 22.00 KiB/s, done.
success Created starter directory layout
info Installing packages...

><EMAIL_ADDRESS>install /Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents
> node install

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.7/fse-v1.2.7-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v72 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Pre-built binaries not installable for<EMAIL_ADDRESS>and<EMAIL_ADDRESS>(node-v72 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error Connection closed while downloading tarball file
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
  CXX(target) Release/obj.target/fse/fsevents.o
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:222:
In file included from ../../nan/nan_converters.h:67:
../../nan/nan_converters_43_inl.h:22:1: warning: 'ToBoolean' is deprecated:
      ToBoolean can never throw. Use Local version. [-Wdeprecated-declarations]
X(Boolean)
^
../../nan/nan_converters_43_inl.h:18:12: note: expanded from macro 'X'
      val->To ## TYPE(isolate->GetCurrentContext())                            \
           ^
<scratch space>:201:1: note: expanded from here
ToBoolean
^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:2523:3: note: 'ToBoolean' has
      been explicitly marked deprecated here
  V8_DEPRECATE_SOON("ToBoolean can never throw. Use Local version.",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:222:
In file included from ../../nan/nan_converters.h:67:
../../nan/nan_converters_43_inl.h:40:1: warning: 'BooleanValue' is deprecated:
      BooleanValue can never throw. Use Isolate version.
      [-Wdeprecated-declarations]
X(bool, Boolean)
^
../../nan/nan_converters_43_inl.h:37:15: note: expanded from macro 'X'
  return val->NAME ## Value(isolate->GetCurrentContext());                     \
              ^
<scratch space>:208:1: note: expanded from here
BooleanValue
^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:2561:3: note: 'BooleanValue'
      has been explicitly marked deprecated here
  V8_DEPRECATED("BooleanValue can never throw. Use Isolate version.",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:307:29: note: expanded
      from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:223:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:356:37: error: too few arguments to
      function call, expected 2, have 1
  return v8::StringObject::New(value).As<v8::StringObject>();
         ~~~~~~~~~~~~~~~~~~~~~      ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:5380:3: note: 'New' declared
      here
  static Local<Value> New(Isolate* isolate, Local<String> value);
  ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:223:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:356:58: error: expected '(' for
      function-style cast or type construction
  return v8::StringObject::New(value).As<v8::StringObject>();
                                         ~~~~~~~~~~~~~~~~^
../../nan/nan_implementation_12_inl.h:356:60: error: expected expression
  return v8::StringObject::New(value).As<v8::StringObject>();
                                                           ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:2722:
../../nan/nan_object_wrap.h:24:25: error: no member named 'IsNearDeath' in
      'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object>
      >'
    assert(persistent().IsNearDeath());
           ~~~~~~~~~~~~ ^
/Applications/Xcode10.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/assert.h:93:25: note:
      expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE...
                        ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:2722:
../../nan/nan_object_wrap.h:127:26: error: no member named 'IsNearDeath' in
      'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object>
      >'
    assert(wrap->handle_.IsNearDeath());
           ~~~~~~~~~~~~~ ^
/Applications/Xcode10.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/assert.h:93:25: note:
      expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE...
                        ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:222:
In file included from ../../nan/nan_converters.h:67:
../../nan/nan_converters_43_inl.h:22:1: warning: 'ToBoolean' is deprecated:
      ToBoolean can never throw. Use Local version. [-Wdeprecated-declarations]
X(Boolean)
^
../../nan/nan_converters_43_inl.h:18:12: note: expanded from macro 'X'
      val->To ## TYPE(isolate->GetCurrentContext())                            \
           ^
<scratch space>:201:1: note: expanded from here
ToBoolean
^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:2523:3: note: 'ToBoolean' has
      been explicitly marked deprecated here
  V8_DEPRECATE_SOON("ToBoolean can never throw. Use Local version.",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:222:
In file included from ../../nan/nan_converters.h:67:
../../nan/nan_converters_43_inl.h:40:1: warning: 'BooleanValue' is deprecated:
      BooleanValue can never throw. Use Isolate version.
      [-Wdeprecated-declarations]
X(bool, Boolean)
^
../../nan/nan_converters_43_inl.h:37:15: note: expanded from macro 'X'
  return val->NAME ## Value(isolate->GetCurrentContext());                     \
              ^
<scratch space>:208:1: note: expanded from here
BooleanValue
^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:2561:3: note: 'BooleanValue'
      has been explicitly marked deprecated here
  V8_DEPRECATED("BooleanValue can never throw. Use Isolate version.",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:307:29: note: expanded
      from macro 'V8_DEPRECATED'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:223:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:356:37: error: too few arguments to
      function call, expected 2, have 1
  return v8::StringObject::New(value).As<v8::StringObject>();
         ~~~~~~~~~~~~~~~~~~~~~      ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:5380:3: note: 'New' declared
      here
  static Local<Value> New(Isolate* isolate, Local<String> value);
  ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:223:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:356:58: error: expected '(' for
      function-style cast or type construction
  return v8::StringObject::New(value).As<v8::StringObject>();
                                         ~~~~~~~~~~~~~~~~^
../../nan/nan_implementation_12_inl.h:356:60: error: expected expression
  return v8::StringObject::New(value).As<v8::StringObject>();
                                                           ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:2722:
../../nan/nan_object_wrap.h:24:25: error: no member named 'IsNearDeath' in
      'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object>
      >'
    assert(persistent().IsNearDeath());
           ~~~~~~~~~~~~ ^
/Applications/Xcode10.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/assert.h:93:25: note:
      expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE...
                        ^
In file included from ../fsevents.cc:6:
In file included from ../../nan/nan.h:2722:
../../nan/nan_object_wrap.h:127:26: error: no member named 'IsNearDeath' in
      'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object>
      >'
    assert(wrap->handle_.IsNearDeath());
           ~~~~~~~~~~~~~ ^
/Applications/Xcode10.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/assert.h:93:25: note:
      expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE...
                        ^
../fsevents.cc:43:32: error: no template named 'Handle' in namespace 'v8'
    static void Initialize(v8::Handle<v8::Object> exports);
                           ~~~~^
In file included from ../fsevents.cc:73:
../src/constants.cc:89:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagNone").ToLoca...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:90:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMustScanSubDi...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:91:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUserDropped")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:92:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagKernelDropped...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:93:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagEventIdsWrapp...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:94:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagHistoryDone")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:95:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagRootChanged")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:96:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMount").ToLoc...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:97:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUnmount").ToL...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:98:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemCreated")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:99:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRemoved")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:100:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemInodeMeta...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:101:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRenamed")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:102:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemModified"...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:103:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemFinderInf...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:104:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemChangeOwn...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:105:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemXattrMod"...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:106:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsFile")....
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:107:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsDir").T...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:108:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsSymlink...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
../fsevents.cc:76:16: error: variable has incomplete type 'void'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
               ^
../fsevents.cc:76:31: error: no member named 'Handle' in namespace 'v8'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                          ~~~~^
../fsevents.cc:76:48: error: expected '(' for function-style cast or type
      construction
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                     ~~~~~~~~~~^
../fsevents.cc:76:50: error: use of undeclared identifier 'exports'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                 ^
../fsevents.cc:76:58: error: expected ';' after top level declarator
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                         ^
                                                         ;
../fsevents.cc:43:32: error: no template named 'Handle' in namespace 'v8'
    static void Initialize(v8::Handle<v8::Object> exports);
                           ~~~~^
In file included from ../fsevents.cc:73:
../src/constants.cc:89:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagNone").ToLoca...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:90:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMustScanSubDi...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:91:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUserDropped")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:92:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagKernelDropped...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:93:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagEventIdsWrapp...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:94:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagHistoryDone")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:95:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagRootChanged")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:96:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagMount").ToLoc...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:97:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagUnmount").ToL...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:98:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemCreated")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:99:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRemoved")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:100:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemInodeMeta...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:101:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemRenamed")...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:102:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemModified"...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:103:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemFinderInf...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:104:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemChangeOwn...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:105:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemXattrMod"...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:106:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsFile")....
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:107:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsDir").T...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
In file included from ../fsevents.cc:73:
../src/constants.cc:108:11: warning: 'Set' is deprecated: Use maybe version
      [-Wdeprecated-declarations]
  object->Set(Nan::New<v8::String>("kFSEventStreamEventFlagItemIsSymlink...
          ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:3358:3: note: 'Set' has been
      explicitly marked deprecated here
  V8_DEPRECATE_SOON("Use maybe version",
  ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8config.h:322:29: note: expanded
      from macro 'V8_DEPRECATE_SOON'
  declarator __attribute__((deprecated(message)))
                            ^
../fsevents.cc:76:16: error: variable has incomplete type 'void'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
               ^
22 warnings and 11 errors generated.
../fsevents.cc:76:31: error: no member named 'Handle' in namespace 'v8'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                          ~~~~^
../fsevents.cc:76:48: error: expected '(' for function-style cast or type
      construction
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                     ~~~~~~~~~~^
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
../fsevents.cc:76:50: error: use of undeclared identifier 'exports'
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                 ^
../fsevents.cc:76:58: error: expected ';' after top level declarator
void FSEvents::Initialize(v8::Handle<v8::Object> exports) {
                                                         ^
                                                         ;
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/wboyer/.nvm/versions/node/v12.4.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:200:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 18.2.0
gyp ERR! command "/Users/wboyer/.nvm/versions/node/v12.4.0/bin/node" "/Users/wboyer/.nvm/versions/node/v12.4.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node" "--module_name=fse" "--module_path=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64" "--napi_version=4" "--node_abi_napi=napi"
gyp ERR! cwd /Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents
gyp ERR! node -v v12.4.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute '/Users/wboyer/.nvm/versions/node/v12.4.0/bin/node /Users/wboyer/.nvm/versions/node/v12.4.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node --module_name=fse --module_path=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64 --napi_version=4 --node_abi_napi=napi' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:200:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:1021:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
node-pre-gyp ERR! System Darwin 18.2.0
node-pre-gyp ERR! command "/Users/wboyer/.nvm/versions/node/v12.4.0/bin/node" "/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/node_modules/node-pre-gyp/bin/node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd /Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents
node-pre-gyp ERR! node -v v12.4.0
node-pre-gyp ERR! node-pre-gyp -v v0.10.3
node-pre-gyp ERR! not ok
Failed to execute '/Users/wboyer/.nvm/versions/node/v12.4.0/bin/node /Users/wboyer/.nvm/versions/node/v12.4.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node --module_name=fse --module_path=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64 --napi_version=4 --node_abi_napi=napi' (1)
22 warnings and 11 errors generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/wboyer/.nvm/versions/node/v12.4.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:200:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 18.2.0
gyp ERR! command "/Users/wboyer/.nvm/versions/node/v12.4.0/bin/node" "/Users/wboyer/.nvm/versions/node/v12.4.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "build" "--fallback-to-build" "--module=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64/fse.node" "--module_name=fse" "--module_path=/Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents/lib/binding/Release/node-v72-darwin-x64" "--napi_version=4" "--node_abi_napi=napi"
gyp ERR! cwd /Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/fsevents
gyp ERR! node -v v12.4.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok

><EMAIL_ADDRESS>install /Users/wboyer/kbm-devspc/git/locomath_gatsby/my-site/node_modules/sharp
> (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)

info sharp Detected globally-installed libvips v8.8.1
info sharp Building from source via node-gyp
  TOUCH Release/obj.target/libvips-cpp.stamp
  CXX(target) Release/obj.target/sharp/src/common.o
In file included from ../src/common.cc:24:
In file included from ../../nan/nan.h:223:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:356:37: error: too few arguments to
      function call, expected 2, have 1
  return v8::StringObject::New(value).As<v8::StringObject>();
         ~~~~~~~~~~~~~~~~~~~~~      ^
/Users/wboyer/.node-gyp/12.4.0/include/node/v8.h:5380:3: note: 'New' declared
      here
  static Local<Value> New(Isolate* isolate, Local<String> value);
  ^
In file included from ../src/common.cc:24:
In file included from ../../nan/nan.h:223:
In file included from ../../nan/nan_new.h:189:
../../nan/nan_implementation_12_inl.h:356:58: error: expected '(' for
      function-style cast or type construction
  return v8::StringObject::New(value).As<v8::StringObject>();
                                         ~~~~~~~~~~~~~~~~^
../../nan/nan_implementation_12_inl.h:356:60: error: expected expression
  return v8::StringObject::New(value).As<v8::StringObject>();
                                                           ^
In file included from ../src/common.cc:24:
In file included from ../../nan/nan.h:2722:
../../nan/nan_object_wrap.h:24:25: error: no member named 'IsNearDeath' in
      'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object>
      >'
    assert(persistent().IsNearDeath());
           ~~~~~~~~~~~~ ^
/Applications/Xcode10.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/assert.h:93:25: note:
      expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE...
                        ^
In file included from ../src/common.cc:24:
In file included from ../../nan/nan.h:2722:
../../nan/nan_object_wrap.h:127:26: error: no member named 'IsNearDeath' in
      'Nan::Persistent<v8::Object, v8::NonCopyablePersistentTraits<v8::Object>
      >'
    assert(wrap->handle_.IsNearDeath());
           ~~~~~~~~~~~~~ ^
/Applications/Xcode10.2.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk/usr/include/assert.h:93:25: note:
      expanded from macro 'assert'
    (__builtin_expect(!(e), 0) ? __assert_rtn(__func__, __FILE__, __LINE...
                        ^
In file included from ../src/common.cc:27:
../src/common.h:78:20: error: no member named 'Handle' in namespace 'v8'
  bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
               ~~~~^
../src/common.h:78:37: error: expected '(' for function-style cast or type
      construction
  bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
                          ~~~~~~~~~~^
../src/common.h:78:39: error: use of undeclared identifier 'obj'
  bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
                                      ^
../src/common.h:78:56: error: expected '(' for function-style cast or type
      construction
  bool HasAttr(v8::Handle<v8::Object> obj, std::string attr);
                                           ~~~~~~~~~~~ ^
../src/common.h:79:29: error: no member named 'Handle' in namespace 'v8'
  std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
                        ~~~~^
../src/common.h:79:46: error: expected '(' for function-style cast or type
      construction
  std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
                                   ~~~~~~~~~~^
../src/common.h:79:48: error: use of undeclared identifier 'obj'
  std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
                                               ^
../src/common.h:79:65: error: expected '(' for function-style cast or type
      construction
  std::string AttrAsStr(v8::Handle<v8::Object> obj, std::string attr);
                                                    ~~~~~~~~~~~ ^
../src/common.h:80:38: error: no member named 'Handle' in namespace 'v8'
  std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
                                 ~~~~^
../src/common.h:80:55: error: expected '(' for function-style cast or type
      construction
  std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
                                            ~~~~~~~~~~^
../src/common.h:80:57: error: use of undeclared identifier 'obj'
  std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
                                                        ^
../src/common.h:80:74: error: expected '(' for function-style cast or type
      construction
  std::vector<double> AttrAsRgba(v8::Handle<v8::Object> obj, std::string attr);
                                                             ~~~~~~~~~~~ ^
../src/common.h:81:37: warning: variable templates are a C++14 extension
      [-Wc++14-extensions]
  template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, s...
                                    ^
../src/common.h:81:48: error: no member named 'Handle' in namespace 'v8'
  template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, s...
                                           ~~~~^
../src/common.h:81:65: error: expected '(' for function-style cast or type
      construction
  template<typename T> v8::Local<T> AttrAs(v8::Handle<v8::Object> obj, s...
                                                      ~~~~~~~~~~^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
1 warning and 20 errors generated.
make: *** [Release/obj.target/sharp/src/common.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/wboyer/.nvm/versions/node/v12.4.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:200:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:

 ERROR

Command failed: npm install

  Error: Command failed: npm install

  - index.js:236
    [lib]/[gatsby-cli]/[execa]/index.js:236:11

  - task_queues.js:89 processTicksAndRejections
    internal/process/task_queues.js:89:5

I made sure that I had brew install libffi and that I added export PKG_CONFIG_PATH="${PKG_CONFIG_PATH}:/usr/local/opt/libffi/lib/pkgconfig" to my .bash_profile (as per this post. I also:

npm config set python "/usr/local/bin/python2.7" -g as per this post and this post
As per this post and this post, to deal with permissions errors with NVM on OSX.
-- sudo chown -R $(whoami) ~/.npm/
-- sudo chown -R $(whoami) ~/.npmrc
-- sudo chown -R $(whoami) $(npm config get prefix)/{lib/node_modules,bin,share}
-- sudo chown -R $(whoami) ~/.node-gyp

brew install vips (as per these instructions) because of issues installing sharp and fsevents (as seen in the errors above).

However, despite successfully npm install sharp@latest fsevents@latest, the package-lock.json shows that the versions of these packages used by this project's dependencies are still the old ones that don't work with node 12.4.0.
Is there something I'm missing here, or would it be possible to update the dependencies of this project? Thank you for your time in reading!

FYI reading about the issues with node 12 and dependencies that rely on old versions of fsevents here leads me to believe that if I delete package-lock.json And clear out the old node_modules, then the requirements should be updated; should I create a new package-lock.json and do a PR?

Indeed, after performing the following:

nvm uninstall 12.6.0
nvm install 12.6.0`
npm use 12.6.0
git clone of the repo
deleting package-lock.json
npm install
npm update

I see in the new package-lock.json that
"fsevents": {
      "version": "1.2.9"
...
 "chokidar": {
    ...
            "fsevents": "^1.2.7",
...

@wbkboyer Thank you for taking the time to investigate and post your findings here. I will definitely update the dependencies. Glad you figured it out!


TypeError: str returned non-string (type bytes)

Crash Report
This crash report was reported through the automatic crash reporting system 🤖
Traceback
  File "/private/var/containers/Bundle/Application/1DDDB90B-A7CE-42B0-B9D7-63E463421171/Electron-Cash.app/Library/Application Support/com.c3-soft.ElectronCash/app/ElectronCash/electroncash_gui/ios_native/utils.py", line 261, in run_with_except_hook
    run_original(*args2, **kwargs2)
  File "/var/containers/Bundle/Application/1DDDB90B-A7CE-42B0-B9D7-63E463421171/Electron-Cash.app/Library/Python/lib/python35.zip/threading.py", line 862, in run
    self._target(*self._args, **self._kwargs)
  File "/private/var/containers/Bundle/Application/1DDDB90B-A7CE-42B0-B9D7-63E463421171/Electron-Cash.app/Library/Application Support/com.c3-soft.ElectronCash/app/ElectronCash/electroncash/web.py", line 168, in get_payment_request_thread
    on_pr(request)
  File "/private/var/containers/Bundle/Application/1DDDB90B-A7CE-42B0-B9D7-63E463421171/Electron-Cash.app/Library/Application Support/com.c3-soft.ElectronCash/app/ElectronCash/electroncash_gui/ios_native/gui.py", line 1022, in on_pr
    utils.NSLog("On PR: %s -- UNIMPLEMENTED.. IMPLEMENT ME!",str(request))

TypeError: __str__ returned non-string (type bytes)

Reporter
This issue was reported by 1 user(s):

Electrum Version
Operating System
Wallet Type
Locale

3.3 (iOS Build: 301)
Darwin-17.5.0-iPhone9,3-64bit iOS 11.3.1 iPhone (E707ED8B-4693-4739-927B-DCB7FFE3D3E4)
standard
pl_PL

Additional Information
The reporting user(s) did not provide additional information.

Judging by the error, something in payment requests is unimplemented

Eeek.  Ok.  Will get on it tomorrow!

Ok. Fixed.  Actually verification of payment requests is planned for a future release.  It was crashing due to a bug in the 'paymentrequests' class.  The str method is returning a bytes object, not an str object.
I am not going to tackle that bug, but I will open up an issue for it.
Anyway this fixes the exception at least.
I'm closing it.


keyboardShouldPersistTaps="never" doesn't dismiss keyboard between TextInputs

I have a setup, described in this Snack.
I am using a KeyboardAwareScrollView with keyboardShouldPersistTaps="never", so that a click away  from a form input always dismisses the keyboard.  If I press into one of the text inputs, and then press outside of it, the keyboard dismisses as is expected.  If I press into one of the text inputs, and then immediately into another, I can then not immediately dismiss the keyboard.
As I am also using react-native-modal-selector, this means that a user is able to launch a modal for a choice list, and when they choose an item, they are returned back to the previous field with the focus, and the keyboard open.
Should keyboardShouldPersistTaps="never" mean that even taps between text inputs should dismiss the keyboard?
I am using:
    "react-native": "https://github.com/expo/react-native/archive/sdk-25.0.0.tar.gz",
    "react-native-keyboard-aware-scroll-view": "^0.5.0",

I am experiencing the same thing.  I changed it to keyboardShouldPersistTaps="handled" and now the keyboard is dismissing no matter what.  I haven't gotten far enough to see if there are other side effects to using "handled".

Turns out this bug is coming from upstream - https://github.com/facebook/react-native/issues/17252


[AutoPR cdn/resource-manager] Dummy Commit

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3161

(message created by the CI based on PR content)

Codecov Report

Merging #2665 into restapi_auto_cdn/resource-manager will not change coverage.
The diff coverage is 100%.

@@                        Coverage Diff                         @@
##           restapi_auto_cdn/resource-manager    #2665   +/-   ##
==================================================================
  Coverage                              55.88%   55.88%
==================================================================
  Files                                   7161     7161
  Lines                                 150710   150710
==================================================================
  Hits                                   84228    84228
  Misses                                 66482    66482

Impacted Files
Coverage Δ

azure-mgmt-cdn/azure/mgmt/cdn/version.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b362f7f...3a14403. Read the comment docs.


Odd Updating log message rendering

In sbt 1.1.4 (not sure about other versions) I get this on startup:
[info] Updating ProjectRef(uri("file:/home/jroper/src/lagom-microprofile/project/"), "lagom-microprofile-build")...

It looks like something is using a case classes' toString, rather than rendering a more fluent label, though I don't think that's the case:
https://github.com/sbt/sbt/blob/05c2c506b2b218d8ed8befcef843951391c07be6/main-settings/src/main/scala/sbt/Reference.scala#L98
Anyway, it's just odd, it looks like a bug, what I would have expected is what sbt 0.13.16 displays:
[info] Updating {file:/home/jroper/src/lagom/project/project/}lagom-build-build...

What Dale said.
I introduced ProjectRef notation that works in both shell and build.sbt along with the unified slash syntax. As it could be a bit confusing, in the context of "Updating ..." log, it might be better to just display the name portion.

Given the auto-generated names of nested builds (lagom, lagom-build, lagom-build-build) I think we should experiment with dropping the build URI.
Alternatively should we just replace
[info] Loading global plugins from /Users/dnw/.dotfiles/.sbt/1.0/plugins
[info] Updating ProjectRef(uri("file:/Users/dnw/.sbt/1.0/plugins/"), "global-plugins")...

with
[info] Loading global plugins from /Users/dnw/.dotfiles/.sbt/1.0/plugins
[info] Updating global plugins from /Users/dnw/.dotfiles/.sbt/1.0/plugins...

?

If we can reach consensus this might be a good first issue.

Thinking particularly for new users that are unfamiliar with sbt, could we make it more descriptive? One thing that I remember from 6 years ago when I first encountered sbt is that I had no idea what "update" meant. Could we instead have error messages like this:
[info] Resolving sbt plugins and other build level dependencies in project/project...
[info] Resolving sbt plugins and other build level dependencies...
[info] Resolving project dependencies for some-project...
[info] Resolving project dependencies for {file:/home/jroper/src/some-referenced-build/}some-project...

The strategy with the above rendering is to try and eliminate noise that doesn't make sense from "normal" builds. If we look at this message:
[info] Updating {file:/home/jroper/src/lagom/project/project/}lagom-build-build...

There's so much redundant/superfluous info there. I know what directory my project is in, I don't need it repeated to me. Also, I don't know about you, but I have never had a build project that had more than one project in it. So the project name adds nothing to that message. What I do need to know is that this is the second level up build project that is building, so perhaps, for the regular project build, output no directory, instead just say it's resolving sbt plugins and other build level dependencies, and then for builds deeper than that, include the directory, relative to the current directory.
When it comes to updating for the build proper, say "resolving dependencies" rather than "updating", and just output the project name. This can probably be detected by seeing if the build matches the current working directory. If it doesn't, then assume it's a project reference, and only then do you need to output the path to the build, because only then is that information useful.


[FALSE-POSITIVE]

Domains or links
https://bigbeans.solutions/
More Information
Incorrectly marked as phishing
Have you requested removal from other sources?
Nope
Additional context
Domain owned by Discord, redirects to discord.com/nitro
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file

https://github.com/mitchellkrogza/phishing/blob/main/falsepositive.list
Please include the same above information to help speed up the whitelisting process.

See https://github.com/mitchellkrogza/Phishing.Database/blob/42f335e26c5726cae259f25683286e994fedff3a/input-source/domains/bolonobolo/coronavirus-covid19-phishing-domains.txt#L33


Fix kubeactions.findGVR

Note: the apiresource object very seldom actually has .Group and .Version set.
From what I logged, it seemed like only a handful had them set.
The most consistently provided Group and Version is in the "apiresources"
object and in the form of GroupVersion that needs to be parsed out.
an example of an apiresources object is:
APIResourceList{
GroupVersion:machine.openshift.io/v1beta1,
    APIResources:[]APIResource{
        APIResource{Name:machines,Namespaced:true,Kind:Machine,Verbs:[delete deletecollection get list patch create update watch],ShortNames:[],SingularName:machine,Categories:[],Group:,Version:,StorageVersionHash:GLEf6/W/4xY=,},
        APIResource{Name:machines/status,Namespaced:true,Kind:Machine,Verbs:[get patch update],ShortNames:[],SingularName:,Categories:[],Group:,Version:,StorageVersionHash:,},
        APIResource{Name:machinesets,Namespaced:true,Kind:MachineSet,Verbs:[delete deletecollection get list patch create update watch],ShortNames:[],SingularName:machineset,Categories:[],Group:,Version:,StorageVersionHash:p7ZEIilFKZ0=,},
        APIResource{Name:machinesets/status,Namespaced:true,Kind:MachineSet,Verbs:[get patch update],ShortNames:[],SingularName:,Categories:[],Group:,Version:,StorageVersionHash:,},
        APIResource{Name:machinesets/scale,Namespaced:true,Kind:Scale,Verbs:[get patch update],ShortNames:[],SingularName:,Categories:[],Group:autoscaling,Version:v1,StorageVersionHash:,},
        APIResource{Name:machinehealthchecks,Namespaced:true,Kind:MachineHealthCheck,Verbs:[delete deletecollection get list patch create update watch],ShortNames:[mhc mhcs],SingularName:machinehealthcheck,Categories:[],Group:,Version:,StorageVersionHash:qvQyPZn5SE8=,},
        APIResource{Name:machinehealthchecks/status,Namespaced:true,Kind:MachineHealthCheck,Verbs:[get patch update],ShortNames:[],SingularName:,Categories:[],Group:,Version:,StorageVersionHash:,},},}

Note: the apiresource object very seldom actually has .Group and .Version set.
From what I logged, it seemed like only a handful had them set.
The most consistently provided Group and Version is in the "apiresources"
object and in the form of GroupVersion that needs to be parsed out.

Good catch.  In fact they are only set on subresources, which we ignore.  Please simplify the PR and just use the GroupVersion from the apiresources object.


Can the right-click menu management function be added？

Description of the new feature / enhancement
I hope this function can achieve the management of columns in the right-click menu
Scenario when this would be used?
When there are too many software installed on the computer, it can lead to a large number of uncommon options in the right-click menu, causing great inconvenience in daily use. The right-click menu management function will simplify the right-click menu and optimize the user's Windows experience.
Supporting information
No response

/dup #33


illegal seek on input streams

Latest snapshot seems to have broken functionality on input streams:
For example:
java -jar parser/target/stats-0.1.0.one-jar.jar < ../testfiles/1193091757.dem

This works fine.
However:
cat ../testfiles/1193091757.dem | java -jar parser/target/stats-0.1.0.one-jar.jar

and
wget -qO- http://replay111.valve.net/570/1375055798_10047699.dem.bz2 | bunzip2 | java -jar parser/target/stats-0.1.0.one-jar.jar

give an IOException "illegal seek".

Can you point me to the code of stats-0.1.0?

https://github.com/yasp-dota/yasp/blob/teamfight/parser/src/main/java/yasp/Main.java
I'm using input stream source with system.in
On Apr 5, 2015 10:46 AM, "Martin Schrodt"<EMAIL_ADDRESS>wrote:

Can you point me to the code of stats-0.1.0?
—
Reply to this email directly or view it on GitHub
https://github.com/skadistats/clarity/issues/37#issuecomment-89786324.

can u post a stacktrace or mail it to<EMAIL_ADDRESS>

btw: those here from YaspCombatLog:
//yasp
        stunDurationIdx = descriptor.getIndexForKey("stun_duration");
        xpReasonIdx = descriptor.getIndexForKey("xp_reason");
        locationXIdx = descriptor.getIndexForKey("location_x");
        locationYIdx = descriptor.getIndexForKey("location_y");

Is this standard? If so, I would merge that into my code...

nevermind, I can reproduce it here.

fixed in https://github.com/skadistats/clarity/commit/494ec27ba4efab63375e2ae8005622957bf20e15
I put a new snapshot online, so updating snapshot should be enough...

XP reason works, the other fields seem to be present, but not populated.

Fixed on most of the test files, but now getting:
Exception in thread "main"
java.lang.reflect.InvocationTargetException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:606)
        at com.simontuffs.onejar.Boot.run(Boot.java:340)
        at com.simontuffs.onejar.Boot.main(Boot.java:166)
Caused by: java.lang.RuntimeException: java.io.EOFException
        at skadistats.clarity.event.Event.raise(Event.java:25)
        at skadistats.clarity.processor.runner.AbstractRunner.runWith(AbstractRunner.java:59)
        at yasp.Main.run(Main.java:430)
        at yasp.Main.main(Main.java:438)
        ... 6 more
Caused by: java.io.EOFException
        at skadistats.clarity.source.InputStreamSource.readByte(InputStreamSource.java:38)
        at skadistats.clarity.source.Source.readVarInt32(Source.java:30)
        at skadistats.clarity.processor.reader.InputSourceProcessor.processSource(InputSourceProcessor.java:65)
        at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:599)
        at skadistats.clarity.event.AbstractInvocationPoint.invoke(AbstractInvocationPoint.java:73)
        at skadistats.clarity.event.Event.raise(Event.java:23)
        ... 9 more

This is on an ARDM match, https://github.com/yasp-dota/testfiles/blob/master/1189263979_ardm.dem
This same error occurs on an invalid file (shouldn't the error be "not a valid replay file"?)
Exception in thread "main"
java.lang.reflect.InvocationTargetException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

        at java.lang.reflect.Method.invoke(Method.java:606)

        at com.simontuffs.onejar.Boot.run(Boot.java:340)

        at com.simontuffs.onejar.Boot.main(Boot.java:166)

Caused by: java.io.EOFException

        at skadistats.clarity.source.InputStreamSource.readBytes(InputStreamSource.java:49)

        at skadistats.clarity.source.Source.readBytes(Source.java:20)

        at skadistats.clarity.source.Source.ensureDemoHeader(Source.java:70)

        at skadistats.clarity.processor.runner.SimpleRunner.<init>(SimpleRunner.java:11)

        at yasp.Main.run(Main.java:430)

        at yasp.Main.main(Main.java:438)

        ... 6 more

The invalid file is just "asdf", so possibly it's trying to read more bytes than are present in the file?

you were correct. if there were less than 8 bytes, it would bail with EOFException. Made that one more clear.
I cannot reproduce the bug with the ARDM-match. works fine here.
My code:
https://github.com/skadistats/clarity-examples/blob/master/src/main/java/skadistats/clarity/examples/test/Main.java

Have you tried using System.in and cat to pipe in a stream?

Test passed in CI, looks like I just had a locally corrupt replay file.

right, I just tried, piping also works :)

are you around in #dota2replay by chance?

I have been a few times in the past but not recently

I see. I have been absent there for a long time, but I try to be around now,
So if there is a problem requiring more interaction, come by!

re: getIndexForKey:
I think the full descriptor list is here, so you could add all of them to CombatLog:
https://github.com/skadistats/clarity-protobuf/blob/6638354a436a0d5c995a5684190dc9b61f2edd54/src/main/proto/dota_usermessages.proto#L863
I'm guessing you just regenerate the .proto file periodically based on SteamKit, but the CombatLog methods in clarity need to be updated as well when the protobuf definitions change.
It would be nice if the methods/Idx values could be updated automatically when the protobufs change.  I don't think you could update the helper methods automatically in this way, but perhaps it's best for the end-user application to implement these methods, as users may want to translate/compile the combat log names differently?

on an unrelated note:
https://github.com/skadistats/clarity/commit/a2dd3784701340dd1c78cea02369e84b8db488b3
if you use @OnTickStart or @OnTickEnd, you have to add a boolean parameter to your event listener

Does this need to be updated as well?
https://github.com/skadistats/clarity/blob/master/src/main/java/skadistats/clarity/processor/gameevents/CombatLog.java#L54
How much are you planning to add to the default clarity CombatLog class?  Just the additional Idx values, or the helper methods as well?

For sure, fixed, thanks!
I would add the additional Idx values, and remove the helpers and put them on the example.
So you would need to implement the helpers the way you need them, and would be able to use the Idx stuff? Deal?

What will you do with:
        private final StringTable combatLogNames;
        private final GameEvent event;

Will you expose them to the client, or retain methods for readCombatLogName and a getter for each of the combat log values?
The following differ from your reference implementation:
 public boolean isTargetHero() {
            if (targetHeroIdx==null) {
                return true;
            }
            return event.getProperty(targetHeroIdx);
        }
        public boolean isAttackerHero() {
            if (attackerHeroIdx==null){
                return true;
            }
            return event.getProperty(attackerHeroIdx);
        }

        private String translate(String in) {
            if (in!=null){
                if (in.startsWith("item_")){
                    in=in.substring("item_".length());
                }
            }
            return in;
        }
        public int getGoldReason() {
            if (goldReasonIdx==null){
                return 0;
            }
            return event.getProperty(goldReasonIdx);
        }
        public int getXpReason() {
            if (xpReasonIdx==null){
                return 0;
            }
            return event.getProperty(xpReasonIdx);
        }
        public int getStunDuration() {
            return event.getProperty(stunDurationIdx);
        }
        public int getLocationX() {
            return event.getProperty(locationXIdx);
        }
        public int getLocationY() {
            return event.getProperty(locationYIdx);
        }
        public String getValueName(){
            return translate(readCombatLogName(getValue()));
        }
        public String getTargetNameCompiled() {
            return (isTargetIllusion() ? "illusion_" : "") + getTargetName();
        }
        public String getAttackerNameCompiled() {
            return (isAttackerIllusion() ? "illusion_" : "") + getAttackerName();
        }

I added a null check in the first two to account for replays that don't have that field set (very old replays)
Similar for the getGoldReason and XpReason methods.
I implemented translate so that it just strips the item_ from the combat log name for items.  This makes it the same as the name used in http://www.dota2.com/jsfeed/itemdata
Added getters for xpreason, stun, locationx, locationy
Added getValueName to be able to read combat log name for value (needed to determine combat log name when purchasing an item)
And finally the I prepend illusion_ to the target name to mark it an illusion, but this is probably client-specific.

Also, Alice updated protobufs yesterday, I don't know if clarity-protobuf is fully up-to-date:
https://github.com/AliceStats/Alice/commit/129dd7d59b163b328a0857adcb68efde055adfb9

right, I would add a null check for everything that has an idx of type Integer, since it can be null for old replays.
I wouldnt take the translate-function, if the client wants to remove "item_", it should do it himself.
I also would remove the getXXXCompiled() functions, and leave those up to the client.
I could expose the game event. I mean, why not. Do you need it?
I would not expose the StringTable, because CombatLogEntry exposes everything it needs from that table. Basically, @OnCombatLogEntry is just some convenience function on ctx.getProcessor(StringTables.class) and @OnGameEvent anyway.

I don't need it, and I just noticed you have a getGameEvent() method anyway.
So I guess just make a getter for each Idx element, and leave translate/compile up to the client.
You should add getValueName as the client will be unable to get the value's combat log name otherwise (unless you want to make readCombatLog public)
You should also remove translate() from all the functions that are currently using it (since translation is going to be left up to the client)
After this I should be able to get rid of YASPCombatLog and just use the default clarity implementation.

ok, will implement soon-ish :)

I also added the following method for debugging:
        public String toString(){
            return event.toString();
        }

6.84 added four new combat log types, 14-17.

Here's the merged version:
https://github.com/yasp-dota/clarity/blob/master/src/main/java/skadistats/clarity/processor/gameevents/CombatLog.java
Unfortunately I applied the changes on top of a lot of other things, so I
can't just submit a pull request.
I am also in the process of testing it to make sure I did it right.
On Wed, Jun 10, 2015 at 10:55 AM, Martin Schrodt<EMAIL_ADDRESS>wrote:

is there some commit I could merge?
—
Reply to this email directly or view it on GitHub
https://github.com/skadistats/clarity/issues/37#issuecomment-110853888.


Does not generate cucumber.json report in azure devops pipeline

Hello good afternoon, I am using cypress with cucumber in my local, the report cucumber-json is generated correctly, however in the azure pipeline the report is never generated, does anyone have any idea what may be happening?
local

azure devops pipeline

the json is not generated
Versions
cypress 6.8.0
cucumber 4.0.1
someone who has any idea what may be happening please.

Hi @gretherMG
I have an azure pipeline and I got my cucumber.json files ok.
This said, for reporting to be in the cool UI reporting in Azure I have to generate JUnit (xml) reports, so Azure understands the report. Just sharing in case that would make you drop the cucumber generation.
Anyway

How do you trigger cypress in your pipeline (what command line). Is it the same as the local one? Only 'run' (vs open' generate reports & artifacts such as video & screenshots. Also, when in local vs when in pipeline, make sure you are on the same folder when line gets executed.
I see docker. Dockers dies instantly after usage. Do you look before it gets killed? I guess yes.
Your local shows that cucumber-json is a folder. Your pipeline screenshot doesn't show much without context.

Do you have any error message? Did you try logging?
If none of this help, then you'll need to provide more for us to help.

Pipeline command line
Pipeline pwd before cypress execution
Reports folder configuration
Reporter full configuration

Due to personal reasons, the previous maintainers of this package are stepping down and handing the reigns over to me, a long-time contributor to the project and a user of it myself. This is a responsibility I'm very excited about. Furthermore, I'd like to thank @lgandecki ++ for all the work that they've done so far.
Read more about the transfer of ownership here.
The repository has however moved and all outstanding issues are being closed. This is not a reflection of the perceived importance of your reported issue. However, if after upgrading to the new version, you still find there to be an issue, feel free to open up another ticket or comment below. Please make sure to read CONTRIBUTING.md before doing so.


CVE-2022-31081 for HTTP::Daemon

Also, this was patched in https://github.com/NixOS/nixpkgs/pull/181632 and discussed in https://github.com/libwww-perl/HTTP-Daemon/issues/56


Project start

#2  TL;DR;
I've started our project using the following steps.
Steps

cloned project with readme.
using the dotnet cli I created a new template project.
ran npm install -g @angular/cli to install the global Angular CLI.
in project root ran ng update @angular/core
ran npm audit fix to fix any new dependency issues.
ran ng update rxjs to upgrade rxjs library.
ran npm audit fix again to fix any issues in project at this point.
running npm install at this point is successful.
updated Bootstrap from 3.3.7 to  4.1.3 and added dependencies.
use dotnet run to compile and run project.

closes #2


Using go modules (Go 1.11+)

Proposed changes in this pull request
Using Go modules (Go 1.11+)
Dep was an experiment and at the moment, it is over.
Starting with Go 1.11, the built-in solutiongo mod is used
Type (put an x where ever applicable)

[ ] Bug fix: Link to the issue
[x] Feature (Non-breaking change)
[ ] Feature (Breaking change)
[ ] Documentation Improvement

Checklist
Please put an x against the checkboxes. Write a small comment explaining if its N/A (not applicable)

[x] Read the CONTRIBUTION guidelines.
[x] All the tests are passing after the introduction of new changes.
[ ] Added tests respective to the part of code I have written.
[ ] Added proper documentation where ever applicable (in code and README.md).

Extra information
Any extra information related to this pull request.

This will be merged with master in the next release candidate. Thank you for your contribution.

@im-kulikov Do we not need to remove the old gopkg files?

go mod used only for Go 1.11+
for back capability I guess we must keep this files

@im-kulikov That makes sense.

@anthdm when 1.12+ will be released, we can remove go-dep files


Deny warnings in CI, not locally

What does this PR try to resolve?
The problem with #![deny(warnings)] is it makes iteration more difficult as you might have intermediate states with warnings. Its slightly better that we defer this to cargo test --lib but that still means you can't run a subset of tests against your experiment until you've cleaned up all of your warnings. This can lead to users working around the problem which could accidentally slip in.
How should we test and review this PR?
The first round for this PR includes a warning in the cargo crate to ensure it breaks CI.  It will then be reverted.
Additional information
See also https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/.60.23!.5Bcfg_attr.28test.2C.20deny.28warnings.29.29.5D.60

You can see that CI failured on a warning if you browse to the now-reverted 9eef46585473edcef35b806c83cbfa2d5b7a6c6d

Thanks!  We probably should follow up on updating bootstrap to deny warnings there, too, but there isn't any real rush for that.
@bors r+

:pushpin: Commit d52f29897a4a5d372d457ebf609808f9dc110001 has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit d52f29897a4a5d372d457ebf609808f9dc110001 with merge 35e45fd2e409207f5a6693832bc746be1a12df5d...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 35e45fd2e409207f5a6693832bc746be1a12df5d to master...


Low GG Hit rate

Hi Sselph,
I've scraped 258 GameGear games and hashs for only 101 games have been found. is this down to my roms or a databse thing like the GB low hit rate potentially is?

Just realised thegamesdb only have circa 150 games listed on their site. When I find the time this week I'll begin to add the ones I have that are missing from their website.

Hi @sselph , have added 141 GG games to thegames.db website - I think this is now 99% of all EU and NA games. Do you need to do anything at your end or will your scraper now find everything?

Nice! I need to get them mapped over to the hashes. I'll get that done this weekend. And I haven't forgotten the script that reports missing information, I've almost finished it.

Thanks for all the hard work. I added all the new GG games to the mappings it ended up being ~170 games.

That's great to hear, although I imagine coding is more hard work  (!).  Do you mean you found 170 new games, or there are 170 in total?

170 new roms for 353 total. Some could be clones so the number of games could be slightly less.

Just scraped again, only 20 something missing, so this is no longer an issue for me.


AS2 Connector 6.4.0

Writer's Quality Checklist
Before merging your PR, did you:

[ ] Run spell checker
[ ] Run link checker to check for broken xrefs
[ ] Check for orphan files
[ ] Perform a local build and do a final visual check of your content, including checking for:

Broken images
Dead links
Correct rendering of partials if they are used in your content
Formatting issues, such as:

Misnumbered ordered lists (steps) or incorrectly nested unordered lists
Messed up tables
Proper indentation
Correct header levels

[ ] Receive final review and signoff from:

Technical SME
Product Manager
Editor or peer reviewer
Reporter, if this content is in response to a reported issue (internal or external feedback)

[ ] If applicable, verify that the software actually got released

Examples from previous PR https://github.com/mulesoft/docs-connectors/pull/2094 are not included in this one.


[FEATURE_REQUEST] Filters for Glances Widgets

Is your feature request related to a problem? If so, please describe.
I have many devices on my server. I don't want to show all of them in the glances widgets but there is no filter option.
Describe the solution you'd like
A posibility to filter the devices in these widgets:

Disk Space   --> Most important to me
Disk IO   --> Second most important to me
CPU Usage Per Core
Network Interfaces
Others where possible

For example:
widgets:        - type: gl-disk-space         options:           hostname: http://<IP_ADDRESS>:61208           devices:             - '/dev/mapper/md1p1'             - '/dev/mapper/md2p1'
Priority
Medium (Would be very useful)
Is this something you would be keen to implement
No

The ability to rename sensors would be super helpful as well as filtering. I have a glances widget for my unRAID server and would love to rename disk sdb to 'parity disk' for example. I don't know vue otherwise I'd jump in and help add the functionality.

In your glances config file you can specify alias's for different devices.
Example below pulled from a configuration template file I used to setting an instance up.
This will use the alias for the web display and include the alias in the api response.
# Alias for sda1 and sdb1
#alias=sda1:SystemDisk,sdb1:DataDisk


Add region proposal (mask) option in Florence2 Image2prompt

Hi,
I suggest this "regional proposal (mask)" option where it will display the same as "regional proposal" if no text_input is set  (see 1)
text_input expect a string of indexes to filter on those indexes to generate the mask like below only the box 1 and 9 are used to generate the mask  (see 2)

what do you think ?
as well I added a dynamic color code for the bboxes in order to make the visual more readable to cherry pick the required indexes

Great! Thanks.


[kibana] Make curl redo the request on redirect

If xpack.security is enabled kibana pod fails because curl returns 302 with location header to login page. To prevent this behaviour I added -L param which make curl redo the request on the login page.

[x] Chart version not bumped (the versions are all bumped and released at the same time)
[ ] README.md updated with any new values or changes
[ ] Updated template tests in ${CHART}/tests/*.py
[ ] Updated integration tests in ${CHART}/examples/*/test/goss.yaml

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Author of the following commits did not sign a Contributor Agreement:
3be7417
Please, read and sign the above mentioned agreement if you want to contribute to this project

I've signed CLA before I send pull request.

This change isn't necessary. More info #514


Problem when updating to Xcode 10.3

After updating to Xcode 10.3 I have this error when trying to build:
Failed to find or create execution context for description <IBCocoaTouchPlatformToolDescription: 0x7fb... in ButtonCell.xib
Any idea? Thanks in advance.

Just restart your Mac and error is gone! The one and only scientific way to solve problems in computers, always forgetting about that..


Change "Hack me" link in /help command

This has been done, make sure you comment on the issue if you're going to take it :)


SQL: "id" and "name"

Hello,
Since 8.7.0 a lot of new keywords were added to highlight.js SQL highlighting. We are using this extensively and saw some regression issues after upgrading from 8.6.0:
"id" and "name" for one are now recognised as keywords. I am not sure IF they are really keywords in any SQL software, but it causes regression issues in queries like:
select
pets.id
pets.name
pets.other_columns
from
pets
In this query, both "id" and "name" are incorrectly highlighted. The columns "id" and "name" are columns which are often used.
I think these words can remain keywords (if they really are) but there could be some extra logic to not mark columns as keywords? Not sure what is the best approach.
Also... there are too many keywords added since 8.7.0, I already raised an issue before about single letters (e.g. "a" 'b" "c" etc...). I think the list of words needs to be checked thoroughly.

I think we could make anything surrounded with dots to not be recognized as keywords. As for the list of words itself, we just need a volunteer who would agree on checking it. Would you be up for it?

I could have a look at the list but I am afraid I do not have sufficient experience with various SQL server softwares (f.e. I don't use Oracle at all). I'll test the fix but it does sound like a good idea.
Thanks for the quick response!


[CP] Dart 3.0 CHANGELOG entry

Commit(s) to merge
0eee9f1392b6a4a8550077fb766762b9c7601b7e
Target
stable (or both? not sure)
Prepared changelist for beta/stable
https://dart-review.googlesource.com/c/sdk/+/299420
Issue Description
The CHANGELOG doesn't describe the 3.0 changes.
What is the fix
This adds all of the language changes and other stuff in 3.0 to the CHANGELOG.
Why cherry-pick
It's good for a stable release's CHANGELOG to describe that stable release. :)
Risk
low
Issue link(s)
None
Extra Info
No response

lgtm

@athomas could you verify that this needs to be pushed to beta?

We don't need this at all, the release tooling takes care of this :)


CTD in Sanguine quest

Nexus bug report

I did the drinking contest with Sam Guevenne.
Waking up in the Temple of Dibella the game will CTD when it unpauses (stick move or button press).
When I remove the mod the game proceeds like normal to talk to the priestess.
I am using version SE <IP_ADDRESS>, a XBox controller and my INI sets are below.
ResumeAfter=0.0
CanUnpauseAfter=0.0
PauseOnSave=0
IgnoreKeyPressAndButton=0
IgnoreMouseMove=1
IgnoreThumbstick=0
I have been using this mod for a while started with <IP_ADDRESS> and this is the only time I have had a CTD when the game unpauses.
Update:
CTD when Sanguine teleports the player out at the end of the quest line. Like before it does the CTD when it goes to unpause the game after you are teleported back to the inn. I had to remove the mod to finish the quest line.
Except when I had to remove the mod for those 2 instances I have been running this mod without any other CTD.

I've reproduced this. Will see if it can be prevented in a general way as the case is safe and can be exempt.

I could not reproduce the crash after teleporting back to the inn. I applied a change that fixed the CTD on teleport to Temple of Dibella for me. Logs from my run:

2024-01-24 07:24:56.731     info  45488 Character::UpdateInDialogue completed
2024-01-24 07:24:56.747     info   4852 Character::UpdateInDialogue intercepted Sam Guevenne
2024-01-24 07:24:56.747     info   4852 Character::UpdateInDialogue completed
2024-01-24 07:24:56.764     info  43752 MenuTopicManager::ProcessEvent intercepted
2024-01-24 07:24:56.764     info  43752 MenuTopicManager::ProcessEvent completed
2024-01-24 07:24:56.765     info  43752 MenuTopicManager::ProcessEvent intercepted
2024-01-24 07:24:56.765     info  43752 MenuTopicManager::ProcessEvent completed
2024-01-24 07:24:56.765     info  43752 MenuTopicManager::ProcessEvent intercepted
2024-01-24 07:24:56.765     info  43752 MenuTopicManager::ProcessEvent completed
2024-01-24 07:24:56.765     info  43752 Called on load-screen, not game load
2024-01-24 07:24:56.765  warning  43752 Cannot freeze time while MenuTopicManager indicates QUST dialogue /0x0003fa17
2024-01-24 07:24:56.765     info  43752 Loading Menu opened - pause OK false

I fixed the diagnostics and ran through this again and got a repro (fixed) on the back-to-the-inn teleport as well. This seems like a generally useful fix, therefore. The problem does not always hit but if it does you'll likely crash if it does.
Leaving the inn:

2024-01-24 08:03:25.974     info  30368 Called on load-screen, not game load
2024-01-24 08:03:25.974  warning  30368 Cannot freeze time while MenuTopicManager indicates QUST dialogue DA14Start/0x0003fa17
2024-01-24 08:03:25.974     info  30368 Loading Menu opened - pause OK false

Back to the inn:

2024-01-24 08:06:12.912     info  30368 Called on load-screen, not game load
2024-01-24 08:06:12.912  warning  30368 Cannot freeze time while MenuTopicManager indicates QUST dialogue A Night To Remember/0x0001bb9b
2024-01-24 08:06:12.912     info  30368 Loading Menu opened - pause OK false

fwiw I also saw a case where the I think the crash would not have happened - I paused OK entering the Temple, which seems to confirm the check is a good preventative against a timing issue but does not always fire.

2024-01-24 08:18:16.768     info   7124 Character::UpdateInDialogue completed
2024-01-24 08:18:16.784     info  43592 Character::UpdateInDialogue intercepted Sam Guevenne
2024-01-24 08:18:16.784     info  43592 Character::UpdateInDialogue completed
2024-01-24 08:18:17.517     info  37444 Called on load-screen, not game load
2024-01-24 08:18:17.517     info  37444 OK to freeze time
2024-01-24 08:18:18.518     info  37444 Loading Menu opened - pause OK true
2024-01-24 08:18:18.889     info  37444 Loading Menu closed after preceding Opened event - pause OK
2024-01-24 08:18:18.889    debug  37444 Resume game if no input for 5.0 seconds, ignoring input for 0.0 seconds
2024-01-24 08:18:18.889    debug  43352 Starting timer thread
2024-01-24 08:18:23.516     info  37444 Pause terminated by Input Event type 0 from Device 0
2024-01-24 08:18:23.516    debug  37444 Cancel active pause timer
2024-01-24 08:18:23.516    debug  37444 Restart game
2024-01-24 08:18:23.516    debug  43352 Exiting timer thread
2024-01-24 08:18:29.528     info   7124 Character::UpdateInDialogue intercepted Senna
2024-01-24 08:18:29.528     info   7124 Character::UpdateInDialogue completed
2024-01-24 08:18:29.528     info  42264 Character::UpdateInDialogue intercepted Senna

Safe on return to inn

2024-01-24 08:16:06.554     info  43592 Character::UpdateInDialogue completed
2024-01-24 08:16:06.571     info  32940 Character::UpdateInDialogue intercepted Sanguine
2024-01-24 08:16:06.571     info  32940 Character::UpdateInDialogue completed
2024-01-24 08:16:12.049     info  37444 Called on load-screen, not game load
2024-01-24 08:16:12.049     info  37444 OK to freeze time
2024-01-24 08:16:13.049     info  37444 Loading Menu opened - pause OK true
2024-01-24 08:16:14.025     info  37444 Loading Menu closed after preceding Opened event - pause OK
2024-01-24 08:16:14.025    debug  37444 Resume game if no input for 5.0 seconds, ignoring input for 0.0 seconds
2024-01-24 08:16:14.026    debug  26516 Starting timer thread
2024-01-24 08:16:18.430     info  37444 Pause terminated by Input Event type 0 from Device 0
2024-01-24 08:16:18.430    debug  37444 Cancel active pause timer
2024-01-24 08:16:18.430    debug  37444 Restart game
2024-01-24 08:16:18.430    debug  26516 Exiting timer thread

For release in v1.2.0