kipr / harrogate Goto Github PK

View Code? Open in Web Editor NEW

2.0 2.0 9.0 22.27 MB

The IDE for the Wombat

License: GNU General Public License v3.0

JavaScript 6.90% HTML 92.18% CSS 0.49% Batchfile 0.01% C 0.01% Pug 0.41%

harrogate's People

Contributors

Stargazers

Watchers

Forkers

jsoutherland f-wuts davidmutchler alex-zach ninja3982 ihsrobotics justinmerrell chrehall68

harrogate's Issues

Program view not working

Dave: The programs option sends me to a list of programs in the workspace, but nothing appears to be functional from that screen.

Implicitly add file name extension to newly created files

Confusing two column format on the main menu

After clicking on menu, I get a screen with lots of options. The two column format on the desktop is confusing — consider putting dividers between sections. The section titles work much better on mobile devices where you have only one column.

Display a project has no source file message

Display a message if the user press compile but the current project doesn't contain any source files

404 Favicon.png does not exist

This error is given when you enter harrogate, I would just add the image in but I need to find what favicon.png was supposed to be.

Zip download fails for projects with multiple files

As discovered in #41:

.zip downloads break if the project contains multiple files. We are using zip-stream for zip downloads which does not handle asynchronous calls to add entries. This works in VMs but not on our controllers. We should use archiver (https://www.npmjs.com/package/archiver) to fix this and simplify our .tar, .tar.gz, and .zip download code.

Provide installer

Debian Bullseye Harrogate Errors

I don't have much information as to why this is happening yet, but this is the next roadblock to getting harrogate working on a fresh image of RPiOS.

See Errors

pi@raspberrypi:~/harrogate $ npm install

npm ERR! code 1

npm ERR! path /home/pi/harrogate/node_modules/bufferutil

npm ERR! command failed

npm ERR! command sh -c node-gyp rebuild

npm ERR! make: Entering directory '/home/pi/harrogate/node_modules/bufferutil/build'

npm ERR!   CXX(target) Release/obj.target/bufferutil/src/bufferutil.o

npm ERR! make: Leaving directory '/home/pi/harrogate/node_modules/bufferutil/build'

npm ERR! gyp info it worked if it ends with ok

npm ERR! gyp info using [email protected]

npm ERR! gyp info using [email protected] | linux | arm

npm ERR! gyp info find Python using Python version 3.9.2 found at "/usr/bin/python3"

npm ERR! gyp info spawn /usr/bin/python3

npm ERR! gyp info spawn args [

npm ERR! gyp info spawn args   '/usr/share/nodejs/node-gyp/gyp/gyp_main.py',

npm ERR! gyp info spawn args   'binding.gyp',

npm ERR! gyp info spawn args   '-f',

npm ERR! gyp info spawn args   'make',

npm ERR! gyp info spawn args   '-I',

npm ERR! gyp info spawn args   '/home/pi/harrogate/node_modules/bufferutil/build/config.gypi',

npm ERR! gyp info spawn args   '-I',

npm ERR! gyp info spawn args   '/usr/share/nodejs/node-gyp/addon.gypi',

npm ERR! gyp info spawn args   '-I',

npm ERR! gyp info spawn args   '/usr/include/nodejs/common.gypi',

npm ERR! gyp info spawn args   '-Dlibrary=shared_library',

npm ERR! gyp info spawn args   '-Dvisibility=default',

npm ERR! gyp info spawn args   '-Dnode_root_dir=/usr/include/nodejs',

npm ERR! gyp info spawn args   '-Dnode_gyp_dir=/usr/share/nodejs/node-gy
p',
npm ERR! gyp info spawn args   '-Dnode_lib_file=/usr/include/nodejs/<(target_arch)/node.lib',

npm ERR! gyp info spawn args   '-Dmodule_root_dir=/home/pi/harrogate/node_modules/bufferutil',

npm ERR! gyp info spawn args   '-Dnode_engine=v8',

npm ERR! gyp info spawn args   '--depth=.',

npm ERR! gyp info spawn args   '--no-parallel',

npm ERR! gyp info spawn args   '--generator-output',

npm ERR! gyp info spawn args   'build',

npm ERR! gyp info spawn args   '-Goutput_dir=.'

npm ERR! gyp info spawn args ]

npm ERR! gyp info spawn make

npm ERR! gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]

npm ERR! ../src/bufferutil.cc:25:30: error: ‘v8::Handle’ has not been declared

npm ERR!    25 |   static void Initialize(v8::Handle<v8::Object> target)

npm ERR!       |                              ^~~~~~
npm ERR! ../src/bufferutil.cc:25:36: error: expected ‘,’ or ‘...’ before ‘<’ token

npm ERR!    25 |   static void Initialize(v8::Handle<v8::Object> target)

npm ERR!       |                                    ^

npm ERR! ../src/bufferutil.cc: In static member function ‘static void BufferUtil::Initialize(int)’:

npm ERR! ../src/bufferutil.cc:33:14: error: ‘target’ was not declared in this scope

npm ERR!    33 |     Nan::Set(target, Nan::New<String>("BufferUtil").ToLocalChecked(), t->GetFunction());

npm ERR!       |              ^~~~~~

npm ERR! ../src/bufferutil.cc:33:86: error: no matching function for call to ‘v8::FunctionTemplate::GetFunction()’

npm ERR!    33 |     Nan::Set(target, Nan::New<String>("BufferUtil").ToLocalChecked(), t->GetFunction());

npm ERR!       |                                                                                      ^

npm ERR! In file included from ../src/bufferutil.cc:7:

npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:6126:46: note: candidate: ‘v8::MaybeLocal<v8::Function> 

v8::FunctionTemplate::GetFunction(v8::Local<v8::Context>)’

npm ERR!  6126 |   V8_WARN_UNUSED_RESULT MaybeLocal<Function> GetFunction(

npm ERR!       |                                              ^~~~~~~~~~~

npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:6126:46: note:   candidate expects 1 argument, 0 provided

npm ERR! ../src/bufferutil.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE 

BufferUtil::Merge(Nan::NAN_METHOD_ARGS_TYPE)’:

npm ERR! ../src/bufferutil.cc:49:49: error: no matching function for call to ‘v8::Value::ToObject()’

npm ERR!    49 |     Local<Object> bufferObj = info[0]->ToObject();

npm ERR!       |                                                 ^

npm ERR! In file included from ../src/bufferutil.cc:7:

npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note: candidate: ‘v8::MaybeLocal<v8::Object> 
v8::Value::ToObject(v8::Local<v8::Context>) const’

npm ERR!  2672 |   V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(

npm ERR!       |                                            ^~~~~~~~

npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note:   candidate expects 1 argument, 0 provided

npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,

npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,

npm ERR!                  from ../src/bufferutil.cc:7:

npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note: candidate: ‘v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) 
const’

npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);

npm ERR!       |                               ^~~~~~~~

npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’

npm ERR!   328 |   declarator __attribute__((deprecated(message)))

npm ERR!       |   ^~~~~~~~~~

npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note:   candidate expects 1 argument, 0 provided

npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);

npm ERR!       |                               ^~~~~~~~

npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’

npm ERR!   328 |   declarator __attribute__((deprecated(message)))

npm ERR!       |   ^~~~~~~~~~

npm ERR! ../src/bufferutil.cc:56:39: warning: ‘v8::Local<v8::Value> v8::Object::Get(uint32_t)’ is deprecated: Use maybe version [-Wdeprecated-declarations]

npm ERR!    56 |       Local<Object> src = array->Get(i)->ToObject();

npm ERR!       |                                       ^

npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,
npm ERR!                  from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:3557:51: note: declared here
npm ERR!  3557 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(uint32_t index));
npm ERR!       |                                                   ^~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! ../src/bufferutil.cc:56:51: error: no matching function for call to ‘v8::Value::ToObject()’
npm ERR!    56 |       Local<Object> src = array->Get(i)->ToObject();
npm ERR!       |                                                   ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note: candidate: ‘v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const’
npm ERR!  2672 |   V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
npm ERR!       |                                            ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note:   candidate expects 1 argument, 0 provided
npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,
npm ERR!                  from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note: candidate: ‘v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) const’
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note:   candidate expects 1 argument, 0 provided
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! ../src/bufferutil.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE BufferUtil::Unmask(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/bufferutil.cc:67:50: error: no matching function for call to ‘v8::Value::ToObject()’
npm ERR!    67 |     Local<Object> buffer_obj = info[0]->ToObject();
npm ERR!       |                                                  ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note: candidate: ‘v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const’
npm ERR!  2672 |   V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
npm ERR!       |                                            ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note:   candidate expects 1 argument, 0 provided
npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,
npm ERR!                  from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note: candidate: ‘v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) const’
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note:   candidate expects 1 argument, 0 provided
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! ../src/bufferutil.cc:69:48: error: no matching function for call to ‘v8::Value::ToObject()’
npm ERR!    69 |     Local<Object> mask_obj = info[1]->ToObject();
npm ERR!       |                                                ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note: candidate: ‘v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const’
npm ERR!  2672 |   V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
npm ERR!       |                                            ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note:   candidate expects 1 argument, 0 provided
npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,
npm ERR!                  from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note: candidate: ‘v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) const’
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note:   candidate expects 1 argument, 0 provided
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! ../src/bufferutil.cc: In static member function ‘static Nan::NAN_METHOD_RETURN_TYPE BufferUtil::Mask(Nan::NAN_METHOD_ARGS_TYPE)’:
npm ERR! ../src/bufferutil.cc:88:50: error: no matching function for call to ‘v8::Value::ToObject()’
npm ERR!    88 |     Local<Object> buffer_obj = info[0]->ToObject();
npm ERR!       |                                                  ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note: candidate: ‘v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const’
npm ERR!  2672 |   V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
npm ERR!       |                                            ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note:   candidate expects 1 argument, 0 provided
npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,
npm ERR!                  from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note: candidate: ‘v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) const’
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note:   candidate expects 1 argument, 0 provided
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! ../src/bufferutil.cc:89:48: error: no matching function for call to ‘v8::Value::ToObject()’
npm ERR!    89 |     Local<Object> mask_obj = info[1]->ToObject();
npm ERR!       |                                                ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note: candidate: ‘v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const’
npm ERR!  2672 |   V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
npm ERR!       |                                            ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note:   candidate expects 1 argument, 0 provided
npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,
npm ERR!                  from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note: candidate: ‘v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) const’
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note:   candidate expects 1 argument, 0 provided
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! ../src/bufferutil.cc:91:50: error: no matching function for call to ‘v8::Value::ToObject()’
npm ERR!    91 |     Local<Object> output_obj = info[2]->ToObject();
npm ERR!       |                                                  ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note: candidate: ‘v8::MaybeLocal<v8::Object> v8::Value::ToObject(v8::Local<v8::Context>) const’
npm ERR!  2672 |   V8_WARN_UNUSED_RESULT MaybeLocal<Object> ToObject(
npm ERR!       |                                            ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2672:44: note:   candidate expects 1 argument, 0 provided
npm ERR! In file included from /usr/include/nodejs/deps/v8/include/v8-internal.h:14,
npm ERR!                  from /usr/include/nodejs/deps/v8/include/v8.h:27,
npm ERR!                  from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note: candidate: ‘v8::Local<v8::Object> v8::Value::ToObject(v8::Isolate*) const’
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2686:31: note:   candidate expects 1 argument, 0 provided
npm ERR!  2686 |                 Local<Object> ToObject(Isolate* isolate) const);
npm ERR!       |                               ^~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’
npm ERR!   328 |   declarator __attribute__((deprecated(message)))
npm ERR!       |   ^~~~~~~~~~
npm ERR! ../src/bufferutil.cc:92:51: error: no matching function for call to ‘v8::Value::Int32Value()’
npm ERR!    92 |     unsigned int dataOffset = info[3]->Int32Value();
npm ERR!       |                                                   ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2709:40: note: candidate: ‘v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const’
npm ERR!  2709 |   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
npm ERR!       |                                        ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2709:40: note:   candidate expects 1 argument, 0 provided
npm ERR! ../src/bufferutil.cc:93:47: error: no matching function for call to ‘v8::Value::Int32Value()’
npm ERR!    93 |     unsigned int length = info[4]->Int32Value();
npm ERR!       |                                               ^
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2709:40: note: candidate: ‘v8::Maybe<int> v8::Value::Int32Value(v8::Local<v8::Context>) const’
npm ERR!  2709 |   V8_WARN_UNUSED_RESULT Maybe<int32_t> Int32Value(Local<Context> context) const;
npm ERR!       |                                        ^~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:2709:40: note:   candidate expects 1 argument, 0 provided
npm ERR! ../src/bufferutil.cc: At global scope:
npm ERR! ../src/bufferutil.cc:114:6: error: variable or field ‘init’ declared void
npm ERR!   114 | void init (Handle<Object> target)
npm ERR!       |      ^~~~
npm ERR! ../src/bufferutil.cc:114:12: error: ‘Handle’ was not declared in this scope
npm ERR!   114 | void init (Handle<Object> target)
npm ERR!       |            ^~~~~~
npm ERR! ../src/bufferutil.cc:114:25: error: expected primary-expression before ‘>’ token
npm ERR!   114 | void init (Handle<Object> target)
npm ERR!       |                         ^
npm ERR! ../src/bufferutil.cc:114:27: error: ‘target’ was not declared in this scope
npm ERR!   114 | void init (Handle<Object> target)
npm ERR!       |                           ^~~~~~
npm ERR! In file included from ../src/bufferutil.cc:8:
npm ERR! ../src/bufferutil.cc:120:25: error: ‘init’ was not declared in this scope; did you mean ‘int’?
npm ERR!   120 | NODE_MODULE(bufferutil, init)
npm ERR!       |                         ^~~~
npm ERR! /usr/include/nodejs/src/node.h:736:36: note: in definition of macro ‘NODE_MODULE_X’
npm ERR!   736 |       (node::addon_register_func) (regfunc),                          \
npm ERR!       |                                    ^~~~~~~
npm ERR! ../src/bufferutil.cc:120:1: note: in expansion of macro ‘NODE_MODULE’
npm ERR!   120 | NODE_MODULE(bufferutil, init)
npm ERR!       | ^~~~~~~~~~~
npm ERR! In file included from ../src/bufferutil.cc:7:
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = node::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)]’:
npm ERR! /usr/include/nodejs/src/node_object_wrap.h:85:78:   required from here
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:10226:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<node::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<node::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
npm ERR! 10226 |                reinterpret_cast<Callback>(callback), type);
npm ERR!       |                ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h: In instantiation of ‘void v8::PersistentBase<T>::SetWeak(P*, typename v8::WeakCallbackInfo<P>::Callback, v8::WeakCallbackType) [with P = Nan::ObjectWrap; T = v8::Object; typename v8::WeakCallbackInfo<P>::Callback = void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)]’:
npm ERR! ../../nan/nan_object_wrap.h:65:61:   required from here
npm ERR! /usr/include/nodejs/deps/v8/include/v8.h:10226:16: warning: cast between incompatible function types from ‘v8::WeakCallbackInfo<Nan::ObjectWrap>::Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<Nan::ObjectWrap>&)’} to ‘Callback’ {aka ‘void (*)(const v8::WeakCallbackInfo<void>&)’} [-Wcast-function-type]
npm ERR! make: *** [bufferutil.target.mk:108: Release/obj.target/bufferutil/src/bufferutil.o] Error 1
npm ERR! gyp ERR! build error 
npm ERR! gyp ERR! stack Error: `make` failed with exit code: 2
npm ERR! gyp ERR! stack     at ChildProcess.onExit (/usr/share/nodejs/node-gyp/lib/build.js:194:23)
npm ERR! gyp ERR! stack     at ChildProcess.emit (events.js:314:20)
npm ERR! gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:276:12)
npm ERR! gyp ERR! System Linux 5.15.36-v7+
npm ERR! gyp ERR! command "/usr/bin/node" "/usr/share/nodejs/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /home/pi/harrogate/node_modules/bufferutil
npm ERR! gyp ERR! node -v v12.22.5
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2022-05-17T15_42_20_736Z-debug.log

API responses are cached by the browser

Currently only seen on Internet Explorer and Edge

UI doesn't adapt properly to small horizontal space

On the main menu, when the horizontal size is small enough, the "About" and "Help" buttons move under the "Menu" button. It also covers part of the actual menu, and messes up the bar at the bottom.

Before:

After:

Splitting projects in lib and src folders makes it hard to use version control

Having the files of a project separated in two directories which are shared with other projects (src and lib) with a directory for the project in each one of those (e.g. src/projectName and lib/projectName) as it is in the testing version 1.1.5 makes it hard to use version control systems like Git for a single project or even maintaining multiple repos for multiple projects. It would be awesome if this is changed in a future release.

Provide program templates

Harrogate blocks user from opening other apps

When you try to click to open the editor or any other of the home screen buttons, it gives this response to the console and doesn't switch to the other page.

I was able to push past it by manually doing a GET request but that doesn't work every-time it seems.

Create file opens the file and places cursor

Terminal view has no prompt (Unix)

Installer for Windows

Harrogate takes a super long time to load harrogate-index-app.js, driver issues, and other problems

This is a consistent result for me, on different Wombats. Sometimes it just appears to not load at all, but that could be that the connection is at the limits of my patience.

This might just be an issue with the page loading time in general, the specific file may not be important.
The core of the issue is that harrogate takes WAY to long to load, at least on the Wombat.

Add download/upload project feature

Add user management

Problems with cloud implementation as of 17:20 CDT on 7/30/15

From phone was able to create a new project, but not edit or run existing projects. From desktop was able to edit code, but not compile or run projects. The at 15:15 the server stopped responding to both desktop and phone. Have not been able to connect since then.

Structure of `users.json`

Please provide the structure of users.json in the readme file or remove it from the .gitignore 😄.

Delete binary before compilation

compilation failed + run -> run previous version

Ability to delete projects or project files

Use different command line options for C and C++ source files

Dave: KISS IDE seems to work fine (except for the problems with graphics above and the simple graphics test yields a compile warning: "cc1: warning: command line option ‘-std=c++1y’ is valid for C++/ObjC++ but not for C” which I do not understand.

Installer for Mac

mobile: Add run button

KISS IDE: Project navigation collapses after new file is project

The project navigation tree view collapses after a new file is added to the project.

Fix user program stdout buffering issue

User program output (printf or cout) is buffered and not sent immediately to stdout. Therefore user program output is not displayed on the runner's console window before the program exits.

Workaround: Add the line setbuf(stdout, NULL); as first line of your main().

UI Error at Project menu in KISS IDE

Install rng-tools to fix connection speed issues with Harrogate

Eugene Myers found that there is a system package that slows down connection speed if rng-tools (or other RNG) is not installed to reduce security risk.

We need to put this on a Wombat and run some tests to see if there is improvement.

The latest version of gulp throws errors with harrogate

The notation for gulpfiles has changed, gulp.series and gulp.parallel are used instead of the old method of defining tasks.

I'll recreate the issue again and post the error here

Randomly returns to Desktop screen when about button is clicked

This seems to happen more frequently when an ethernet cable is plugged. The UI closes and has to be restarted by clicking the Botguy icon on the screen.

Visualize compilation result

Color the compilation result panel depending on the compilation result

Success: Green
Warning: Yellow
Error: Red

Tab spacing is not working for Python

Add Comments

This may be a mute point if we end up replacing Harrogate with a typescript implementation or other.

But Harrogate's code is a huge pain to read through because often it is not well spaced and has no real comments explaining anything. Even though a person who is accustomed to the language CAN decipher it, it gets very redundant having to re-decipher the code every time we make a change.

If harrogate is going to be continued in use, it would be worth development time to add comments, simplify things, and clean up general formatting. Maybe we should add a Project Clean Up Crew like we are doing (as of writing this) with botui.

For example, the only comment here is a bug report. I actually have yet to find a file that has more than 2 comments on it.

start_program = function() {
  if ((running != null ? running.resource : void 0) != null) {
    // TODO: change me!!
    // Create data directory
    running.resource.data_directory.create()["finally"](function() {
      var env;
      namespace.emit(events.starting.id, running.resource.name);
      env = Object.create(process.env);
      env.PYTHONPATH = "/usr/lib";
      running_process = spawn(running.resource.binary.path, [], {
        cwd: Path.resolve(running.resource.data_directory.path),
        env: env
      });
      running_process.on('error', function(data) {
        console.log("Could not spawn " + running.resource.binary.path + "!! Error details: " + (JSON.stringify({
          error: data
        })));
        namespace.emit(events.stderr.id, "Program crashed!\n\nError details:\n" + (JSON.stringify({
          error: data
        }, null, '\t')));
        namespace.emit(events.ended.id);
        stop_program();
      });
      running_process.stdout.on('data', function(data) {
        namespace.emit(events.stdout.id, data.toString('utf8'));
      });
      running_process.stderr.on('data', function(data) {
        namespace.emit(events.stderr.id, data.toString('utf8'));
      });
      return running_process.on('exit', function(code) {
        namespace.emit(events.stdout.id, "Program exited with code " + code);
        namespace.emit(events.ended.id);
        stop_program();
      });
    });
  }
};

Add PThread to allow for multiple threaded programs

harrogate/apps/compiler/compilation-environments/c/gcc.js

Line 26 in d5e55e0

 gcc_cmd += "-L\"" + Config.ext_deps.lib_path + "\" -lwallaby -lm -o \"" + project_resource.binary.path + "\" "; 

harrogate/apps/compiler/compilation-environments/c/mingw.js

Line 32 in d5e55e0

 gcc_cmd += "-L\"" + Config.ext_deps.lib_path + "\" -o \"" + project_resource.binary.path + ".exe\" "; 

harrogate/apps/compiler/compilation-environments/c/vs-cl-12.js

Line 33 in d5e55e0

cl_cmd += "\"" + (Path.resolve(__dirname, '_init_helper.c')) + "\" ";

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.