joybox's People
Forkers
comfort4u serguk89 doggstylrrx jafea7 allpinkbotunechicks finaldoom x3m444 omar-elhamedy jeran-us derbunteball wattcash weigeloveu snake4lifejoybox's Issues
now what ?
could it support proxy?
it cant connect cb directly on my country,could it support proxy?
Status Pull seems to be broken
Hi,
the model status pull seems to be broken.
I see the red ball with ! at the status page (see image).
The log shows this strange error:
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added to [TransformToString]. Use emitter.setMaxListeners() to increase limit
I don't know whether this is related to that. But I think it could be possible that it stops working after a certain count of status requests or a certain count of models.
For me it seems to hang after a while. So I think calls doesn't get fired or not handled. So if you check models you have in list they can be online but you don't have a working recording. When it starts to hang running recordings work fourther. Recording work well in general. So when a recording starts it works.
The Docker build is really broken. So I have a build based on Alpine 3.12 and Node 1.4. The dependencies seem to need a fix. I'm not skilled in Node so I can do nothing shortly.
It's the most handy tool to record chaturbate and so on. So it would be nice to have it working properly.
Best Regards
Login screen?
Hello,
Since the script exposes ports from the server to the internet, have some plans to apply some login screen?
npm ERR! code EISDIR
Step 7/32 : RUN npm i && mv ./node_modules/@types/jsonstream ./node_modules/@types/JSONStream
---> Running in b2263074c919
npm ERR! code EISDIR
npm ERR! syscall copyfile
npm ERR! path /app/node_modules/chownr
npm ERR! dest /app/node_modules/.chownr-cyv3QNXu
npm ERR! errno -21
npm ERR! EISDIR: illegal operation on a directory, copyfile '/app/node_modules/chownr' -> '/app/node_modules/.chownr-cyv3QNXu'
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-12-17T13_56_05_099Z-debug.log
The command '/bin/sh -c npm i && mv ./node_modules/@types/jsonstream ./node_modules/@types/JSONStream' returned a non-zero code: 235
Can't delete Recorded Videos in Archive
Very nice piece of Software. But i can't delete any of my recorded videos in my Archive. After press on the the Trash Symbol, nothing, only a short Message "No Access". Can you please help me please?
A wish on my part for a future version might be the support of "camsoda".
Kind Regards
Ronald
UBUNTU 18.04 LTS Server
cant buid docker image
###############################################################
[node1] (local) [email protected] ~
$ git clone https://github.com/PleasureTools/joyBox.git
Cloning into 'joyBox'...
remote: Enumerating objects: 1074, done.
remote: Counting objects: 100% (102/102), done.
remote: Compressing objects: 100% (87/87), done.
remote: Total 1074 (delta 63), reused 19 (delta 15), pack-reused 972
Receiving objects: 100% (1074/1074), 1.14 MiB | 8.97 MiB/s, done.
Resolving deltas: 100% (570/570), done.
[node1] (local) [email protected] ~
$ cd joyBox/
[node1] (local) [email protected] ~/joyBox
$ docker build -t joybox .
Sending build context to Docker daemon 3.171MB
Step 1/33 : FROM node:current-alpine as deps
current-alpine: Pulling from library/node
ca7dd9ec2225: Pull complete
bfebca31f755: Pull complete
cc0056ab0c41: Pull complete
6e25476b6324: Pull complete
Digest: sha256:80844b6643f239c87fceae51e6540eeb054fc7114d979703770ec75250dcd03b
Status: Downloaded newer image for node:current-alpine
---> 9b78801b4058
Step 2/33 : WORKDIR /app
---> Running in 57bea409fc8c
Removing intermediate container 57bea409fc8c
---> 8a3697b3e528
Step 3/33 : RUN apk add python3 g++ make
---> Running in b207705dad9b
fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/main/x86_64/APKINDEX.tar.gz
fetch https://dl-cdn.alpinelinux.org/alpine/v3.16/community/x86_64/APKINDEX.tar.gz
(1/24) Upgrading musl (1.2.3-r1 -> 1.2.3-r2)
(2/24) Installing binutils (2.38-r3)
(3/24) Installing libgomp (11.2.1_git20220219-r2)
(4/24) Installing libatomic (11.2.1_git20220219-r2)
(5/24) Installing gmp (6.2.1-r2)
(6/24) Installing isl22 (0.22-r0)
(7/24) Installing mpfr4 (4.1.0-r0)
(8/24) Installing mpc1 (1.2.1-r0)
(9/24) Installing gcc (11.2.1_git20220219-r2)
(10/24) Installing musl-dev (1.2.3-r2)
(11/24) Installing libc-dev (0.7.2-r3)
(12/24) Installing g++ (11.2.1_git20220219-r2)
(13/24) Installing make (4.3-r0)
(14/24) Installing libbz2 (1.0.8-r1)
(15/24) Installing expat (2.5.0-r0)
(16/24) Installing libffi (3.4.2-r1)
(17/24) Installing gdbm (1.23-r0)
(18/24) Installing xz-libs (5.2.5-r1)
(19/24) Installing mpdecimal (2.5.1-r1)
(20/24) Installing ncurses-terminfo-base (6.3_p20220521-r0)
(21/24) Installing ncurses-libs (6.3_p20220521-r0)
(22/24) Installing readline (8.1.2-r0)
(23/24) Installing sqlite-libs (3.38.5-r0)
(24/24) Installing python3 (3.10.8-r0)
Executing busybox-1.35.0-r17.trigger
OK: 229 MiB in 39 packages
Removing intermediate container b207705dad9b
---> 9f4ea988c459
Step 4/33 : COPY package.json .
---> 33a65318c420
Step 5/33 : COPY package-lock.json .
---> 4c4484f193a4
Step 6/33 : RUN npm i && mv ./node_modules/@types/jsonstream ./node_modules/@types/JSONStream
---> Running in 789bad5faa0c
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: [email protected]
npm WARN Found: [email protected]
npm WARN node_modules/typescript
npm WARN dev typescript@"^4.8.4" from the root project
npm WARN 7 more (tsutils, tsutils, @vue/cli-plugin-typescript, ts-loader, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peer typescript@"^2.1.0 || ^3.0.0" from [email protected]
npm WARN node_modules/@vue/cli-plugin-typescript/node_modules/fork-ts-checker-webpack-plugin
npm WARN fork-ts-checker-webpack-plugin@"^0.5.2" from @vue/[email protected]
npm WARN node_modules/@vue/cli-plugin-typescript
npm WARN
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/typescript
npm WARN peer typescript@"^2.1.0 || ^3.0.0" from [email protected]
npm WARN node_modules/@vue/cli-plugin-typescript/node_modules/fork-ts-checker-webpack-plugin
npm WARN fork-ts-checker-webpack-plugin@"^0.5.2" from @vue/[email protected]
npm WARN node_modules/@vue/cli-plugin-typescript
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Fixed a prototype pollution security issue in 4.1.0, please upgrade to ^4.1.1 or ^5.0.1.
npm WARN deprecated [email protected]: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated [email protected]: 3.x is no longer supported
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: Version no longer supported. Upgrade to @latest
npm notice
npm notice New major version of npm available! 8.19.3 -> 9.1.3
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.1.3>
npm notice Run `npm install -g [email protected]` to update!
npm notice
npm ERR! code 1
npm ERR! path /app/node_modules/better-sqlite3
npm ERR! command failed
npm ERR! command sh -c -- prebuild-install || npm run build-release
npm ERR! > [email protected] build-release
npm ERR! > node-gyp rebuild --release
npm ERR!
npm ERR! make: Entering directory '/app/node_modules/better-sqlite3/build'
npm ERR! TOUCH b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
npm ERR! ACTION deps_sqlite3_gyp_locate_sqlite3_target_extract_sqlite3 b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
npm ERR! TOUCH Release/obj.target/deps/locate_sqlite3.stamp
npm ERR! CC(target) Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o
npm ERR! AR(target) Release/obj.target/deps/sqlite3.a
npm ERR! COPY Release/sqlite3.a
npm ERR! CXX(target) Release/obj.target/better_sqlite3/src/better_sqlite3.o
npm ERR! rm b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
npm ERR! make: Leaving directory '/app/node_modules/better-sqlite3/build'
npm ERR! prebuild-install WARN install No prebuilt binaries found (target=19.2.0 runtime=node arch=x64 libc=musl platform=linux)
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 | x64
npm ERR! gyp info find Python using Python version 3.10.8 found at "/usr/bin/python3"
npm ERR! gyp http GET https://unofficial-builds.nodejs.org/download/release/v19.2.0/node-v19.2.0-headers.tar.gz
npm ERR! gyp http 200 https://unofficial-builds.nodejs.org/download/release/v19.2.0/node-v19.2.0-headers.tar.gz
npm ERR! gyp http GET https://unofficial-builds.nodejs.org/download/release/v19.2.0/SHASUMS256.txt
npm ERR! gyp http 200 https://unofficial-builds.nodejs.org/download/release/v19.2.0/SHASUMS256.txt
npm ERR! gyp info spawn /usr/bin/python3
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/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 '/app/node_modules/better-sqlite3/build/config.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/root/.cache/node-gyp/19.2.0/include/node/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=/root/.cache/node-gyp/19.2.0',
npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args '-Dnode_lib_file=/root/.cache/node-gyp/19.2.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args '-Dmodule_root_dir=/app/node_modules/better-sqlite3',
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! In file included from ./src/better_sqlite3.lzz:11,
npm ERR! from ../src/better_sqlite3.cpp:4:
npm ERR! /root/.cache/node-gyp/19.2.0/include/node/node.h:1013:7: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Context>)' to 'node::addon_context_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, v8::Local<v8::Context>, void*)'} [-Wcast-function-type]
npm ERR! 1013 | (node::addon_context_register_func) (regfunc), \
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! /root/.cache/node-gyp/19.2.0/include/node/node.h:1031:3: note: in expansion of macro 'NODE_MODULE_CONTEXT_AWARE_X'
npm ERR! 1031 | NODE_MODULE_CONTEXT_AWARE_X(modname, regfunc, NULL, 0)
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! /root/.cache/node-gyp/19.2.0/include/node/node.h:1062:3: note: in expansion of macro 'NODE_MODULE_CONTEXT_AWARE'
npm ERR! 1062 | NODE_MODULE_CONTEXT_AWARE(NODE_GYP_MODULE_NAME, \
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! ./src/better_sqlite3.lzz:67:1: note: in expansion of macro 'NODE_MODULE_INIT'
npm ERR! ./src/util/macros.lzz: In function 'void SetPrototypeGetter(v8::Isolate*, v8::Local<v8::External>, v8::Local<v8::FunctionTemplate>, const char*, v8::AccessorGetterCallback)':
npm ERR! ./src/util/macros.lzz:157:21: error: 'v8::AccessorSignature' has not been declared
npm ERR! ./src/util/binder.lzz: In static member function 'static bool Binder::IsPlainObject(v8::Isolate*, v8::Local<v8::Object>)':
npm ERR! ./src/util/binder.lzz:37:51: error: 'class v8::Object' has no member named 'CreationContext'; did you mean 'GetCreationContext'?
npm ERR! ./src/util/data.lzz: In function 'v8::Local<v8::Value> Data::GetValueJS(v8::Isolate*, sqlite3_stmt*, int, bool)':
npm ERR! ./src/util/data.lzz:72:92: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! ./src/util/data.lzz:72:197: note: here
npm ERR! ./src/util/data.lzz: In function 'v8::Local<v8::Value> Data::GetValueJS(v8::Isolate*, sqlite3_value*, bool)':
npm ERR! ./src/util/data.lzz:76:81: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! ./src/util/data.lzz:76:175: note: here
npm ERR! make: *** [better_sqlite3.target.mk:125: Release/obj.target/better_sqlite3/src/better_sqlite3.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/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:201:23)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28)
npm ERR! gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:293:12)
npm ERR! gyp ERR! System Linux 4.4.0-210-generic
npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
npm ERR! gyp ERR! cwd /app/node_modules/better-sqlite3
npm ERR! gyp ERR! node -v v19.2.0
npm ERR! gyp ERR! node-gyp -v v9.1.0
npm ERR! gyp ERR! not ok
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-12-03T02_28_40_254Z-debug-0.log
The command '/bin/sh -c npm i && mv ./node_modules/@types/jsonstream ./node_modules/@types/JSONStream' returned a non-zero code: 1
[node1] (local) [email protected] ~/joyBox
C:\Users\v\joyBox>docker run --name joybox --rm -d -p 8080:80 -p 8081:443 -v D:\data\app\data:/app/data joybox
C:\Users\v\joyBox>docker run --name joybox --rm -p 8080:80 -p 8081:443 -v D:/chaturbate:/app/data joybox
[email protected] start /app
cross-env PLATFORM=DOCKER TS_NODE_PROJECT=backend/tsconfig.json node -r tsconfig-paths/register backend/Src/main.js
BongacamsLocator::Start()
BongacamsDirectLocator::Start()
ChaturbateDirectLocator::Start()
DummyLocator::Start()
events.js:200
throw er; // Unhandled 'error' event
^
Error: ENOENT: no such file or directory, open '/sys/fs/cgroup/cpu,cpuacct/cpuacct.usage'
Emitted 'error' event on ReadStream instance at:
at internal/fs/streams.js:120:12
at FSReqCallback.oncomplete (fs.js:146:23) {
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/sys/fs/cgroup/cpu,cpuacct/cpuacct.usage'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: cross-env PLATFORM=DOCKER TS_NODE_PROJECT=backend/tsconfig.json node -r tsconfig-paths/register backend/Src/main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start 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:
npm ERR! /root/.npm/_logs/2020-02-19T02_34_51_881Z-debug.log
Install Error
UBUNTU 18.04 LTS Server
after "docker build -t joybox .", many red sqlite3 errors on Screen.
here are a Sample:
Release/obj/gen/sqlite3/sqlite3.c: In function 'strftimeFunc': Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type] 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize) | ^ Release/obj/gen/sqlite3/sqlite3.c:22122:52: note: in expansion of macro 'SQLITE_DYNAMIC' 22122 | z==zBuf ? SQLITE_TRANSIENT : SQLITE_DYNAMIC); | ^~~~~~~~~~~~~~ Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3ErrorWithMsg': Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type] 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
start with "docker run --name joybox --rm -v $(pwd):/app/data joybox" return this:
`> [email protected] start /app
cross-env PLATFORM=DOCKER node main.js
Database doesn't initialized or malformed. Initialization...
/app/Services/NotificationCenter.js:17
webpush.setVapidDetails(BootstrapConfiguration_1.Config.VAPID.subject, BootstrapConfiguration_1.Config.VAPID.publicKey, BootstrapConfiguration_1.Config.VAPID.privateKey);
^
TypeError: Cannot read property 'subject' of null
at new NotificationCenter (/app/Services/NotificationCenter.js:17:71)
at App.Run (/app/main.js:94:35)
at Object. (/app/main.js:244:5)
at Module._compile (internal/modules/cjs/loader.js:959:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
at Module.load (internal/modules/cjs/loader.js:815:32)
at Function.Module._load (internal/modules/cjs/loader.js:727:14)
at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
at internal/main/run_main_module.js:17:11
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: cross-env PLATFORM=DOCKER node main.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start 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:
npm ERR! /root/.npm/_logs/2020-01-04T08_57_56_277Z-debug.log
`
My Error, or can you help me?
Kind Regards
Ronald
how could restart recording?
thanks your joybox,it the best record app.
once stoped recording,if want to restart it need to remove from observable and readd it.
if could add more option,like "play" "pasue" "record" on observable list,like that
user will add lots of model like the screenshot,but most time is boring,just need record some wonderful moment.
with play button could preview if its the moment that want to record.
any guide for how to use joybox?
thanks for the tools,im know nothing about docker,just build it follow the guide.
`
[w@localhost joyBox]$ sudo docker run --name joybox --rm -v $(pwd):/app/data joybox
[email protected] start /app
cross-env PLATFORM=DOCKER node backend/Src/main.js
BongacamsLocator::Start()
BongacamsDirectLocator::Start()
ChaturbateDirectLocator::Start()
DummyLocator::Start()
`
and i jsut got this,i dont know how should i do next,could you plz give some more guide?
thanks very much
Camsoda not working anymore
Camsoda not working anymore, i think, Camsoda have made chances on their website, other tools also not working now.
Can you please check and fit it?
Kind Regards
Powerbock
Dangling records
Hey guys
Not really a problem but is there any way to"repair" dangling records so that they are watchable instead of just deleting them?
thanks for update,but with npm error
Step 4/32 : RUN npm i [email protected]
---> Running in 10029e24f5ab
npm notice
npm notice New minor version of npm available! 7.15.1 -> 7.16.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.16.0>
npm notice Run `npm install -g [email protected]` to update!
npm notice
npm ERR! code 1
npm ERR! path /app/node_modules/better-sqlite3
npm ERR! command failed
npm ERR! command sh -c node-gyp rebuild
npm ERR! make: Entering directory '/app/node_modules/better-sqlite3/build'
npm ERR! TOUCH b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
npm ERR! ACTION deps_sqlite3_gyp_locate_sqlite3_target_extract_sqlite3 b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
npm ERR! TOUCH Release/obj.target/deps/locate_sqlite3.stamp
npm ERR! CC(target) Release/obj.target/sqlite3/gen/sqlite3/sqlite3.o
npm ERR! AR(target) Release/obj.target/deps/sqlite3.a
npm ERR! COPY Release/sqlite3.a
npm ERR! CXX(target) Release/obj.target/better_sqlite3/src/better_sqlite3.o
npm ERR! rm b857c92884e9598d609f6be182a2595df7a8e00f.intermediate
npm ERR! make: Leaving directory '/app/node_modules/better-sqlite3/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 | x64
npm ERR! gyp info find Python using Python version 2.7.18 found at "/usr/bin/python"
npm ERR! gyp http GET https://unofficial-builds.nodejs.org/download/release/v16.3.0/node-v16.3.0-headers.tar.gz
npm ERR! gyp http 200 https://unofficial-builds.nodejs.org/download/release/v16.3.0/node-v16.3.0-headers.tar.gz
npm ERR! gyp http GET https://unofficial-builds.nodejs.org/download/release/v16.3.0/SHASUMS256.txt
npm ERR! gyp http 200 https://unofficial-builds.nodejs.org/download/release/v16.3.0/SHASUMS256.txt
npm ERR! (node:18) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use `node --trace-deprecation ...` to show where the warning was created)
npm ERR! gyp info spawn /usr/bin/python
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/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 '/app/node_modules/better-sqlite3/build/config.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/usr/local/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
npm ERR! gyp info spawn args '-I',
npm ERR! gyp info spawn args '/root/.cache/node-gyp/16.3.0/include/node/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=/root/.cache/node-gyp/16.3.0',
npm ERR! gyp info spawn args '-Dnode_gyp_dir=/usr/local/lib/node_modules/npm/node_modules/node-gyp',
npm ERR! gyp info spawn args '-Dnode_lib_file=/root/.cache/node-gyp/16.3.0/<(target_arch)/node.lib',
npm ERR! gyp info spawn args '-Dmodule_root_dir=/app/node_modules/better-sqlite3',
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! Release/obj/gen/sqlite3/sqlite3.c: In function 'strftimeFunc':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:22122:52: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 22122 | z==zBuf ? SQLITE_TRANSIENT : SQLITE_DYNAMIC);
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3ErrorWithMsg':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:30441:54: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 30441 | sqlite3ValueSetStr(db->pErr, -1, z, SQLITE_UTF8, SQLITE_DYNAMIC);
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3VdbeMemSetStr':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:75617:15: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 75617 | if( xDel==SQLITE_DYNAMIC ){
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'valueFromExpr':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:76023:55: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 76023 | sqlite3ValueSetStr(pVal, -1, zVal, SQLITE_UTF8, SQLITE_DYNAMIC);
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:76071:29: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 76071 | 0, SQLITE_DYNAMIC);
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'printfFunc':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:113771:25: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 113771 | SQLITE_DYNAMIC);
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'generateColumnNames':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:127036:58: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 127036 | sqlite3VdbeSetColName(v, i, COLNAME_NAME, zName, SQLITE_DYNAMIC);
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:14182:27: warning: cast between incompatible function types from 'int (*)(void *)' to 'void (*)(void *)' [-Wcast-function-type]
npm ERR! 14182 | #define SQLITE_DYNAMIC ((sqlite3_destructor_type)sqlite3MallocSize)
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:127043:52: note: in expansion of macro 'SQLITE_DYNAMIC'
npm ERR! 127043 | sqlite3VdbeSetColName(v, i, COLNAME_NAME, z, SQLITE_DYNAMIC);
npm ERR! | ^~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3InvokeBusyHandler':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:156790:12: warning: cast between incompatible function types from 'int (*)(void *, int)' to 'int (*)(void *, int, sqlite3_file *)' [-Wcast-function-type]
npm ERR! 156790 | xTra = (int(*)(void*,int,sqlite3_file*))p->xBusyHandler;
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3_busy_timeout':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:156868:30: warning: cast between incompatible function types from 'int (*)(void *, int, sqlite3_file *)' to 'int (*)(void *, int)' [-Wcast-function-type]
npm ERR! 156868 | sqlite3_busy_handler(db, (int(*)(void*,int))sqliteDefaultBusyCallback,
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3_db_status':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:20945:10: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 20945 | op = SQLITE_DBSTATUS_CACHE_WRITE+1;
npm ERR! | ~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:20947:5: note: here
npm ERR! 20947 | case SQLITE_DBSTATUS_CACHE_HIT:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3_str_vappendf':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:27701:19: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 27701 | flag_long = sizeof(char*)==sizeof(i64) ? 2 :
npm ERR! | ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! 27702 | sizeof(char*)==sizeof(long int) ? 1 : 0;
npm ERR! | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:27704:7: note: here
npm ERR! 27704 | case etORDINAL:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:27706:19: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 27706 | cThousand = 0;
npm ERR! | ~~~~~~~~~~^~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:27708:7: note: here
npm ERR! 27708 | case etDECIMAL:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3GetToken':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:154367:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 154367 | if( !sqlite3Isdigit(z[1]) )
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:154376:5: note: here
npm ERR! 154376 | case CC_DIGIT: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:154466:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 154466 | if( z[1]=='\'' ){
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:154480:5: note: here
npm ERR! 154480 | case CC_ID: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3ExprCodeTarget':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:100682:25: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 100682 | case TK_AGG_COLUMN: {
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:100695:5: note: here
npm ERR! 100695 | case TK_COLUMN: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'resolveP2Values':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:77185:13: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 77185 | if( pOp->p2!=0 ) p->readOnly = 0;
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:77188:9: note: here
npm ERR! 77188 | case OP_AutoCommit:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:77226:26: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 77226 | case OP_VFilter: {
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:77235:9: note: here
npm ERR! 77235 | default: {
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'resolveExprStep':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:96366:20: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 96366 | case TK_ISNOT: {
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:96382:5: note: here
npm ERR! 96382 | case TK_BETWEEN:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'impliesNotNullRow':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:102309:8: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 102308 | if( (pExpr->pLeft->op==TK_COLUMN && IsVirtual(pExpr->pLeft->y.pTab))
npm ERR! | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! 102309 | || (pExpr->pRight->op==TK_COLUMN && IsVirtual(pExpr->pRight->y.pTab))
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:102313:5: note: here
npm ERR! 102313 | default:
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'exprImpliesNotNull':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:102188:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 102188 | if( exprImpliesNotNull(pParse, p->pRight, pNN, iTab, seenNot) ) return 1;
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:102191:5: note: here
npm ERR! 102191 | case TK_SPAN:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'fkActionTrigger':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:116863:11: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 116863 | if( !pChanges ){
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:116867:7: note: here
npm ERR! 116867 | default:
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3GenerateConstraintChecks':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118331:17: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 118331 | onError = OE_Abort;
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118335:7: note: here
npm ERR! 118335 | case OE_Abort:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118493:17: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 118493 | onError = OE_Abort;
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118496:7: note: here
npm ERR! 118496 | case OE_Rollback:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118556:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 118556 | sqlite3UpsertDoUpdate(pParse, pUpsert, pTab, 0, iDataCur);
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118560:7: note: here
npm ERR! 118560 | case OE_Ignore: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118772:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 118772 | sqlite3UpsertDoUpdate(pParse, pUpsert, pTab, pIdx, iIdxCur+ix);
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:118776:7: note: here
npm ERR! 118776 | case OE_Ignore: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3VdbeExec':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:84796:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 84796 | if( (pIn3->flags & MEM_Null)==0 ) break;
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:84830:1: note: here
npm ERR! 84830 | case OP_Halt: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:84963:5: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 84963 | if( pOp->p1>db->aLimit[SQLITE_LIMIT_LENGTH] ){
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:84982:1: note: here
npm ERR! 84982 | case OP_String: { /* out2 */
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:88088:19: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 88088 | case OP_IfNoHope: { /* jump, in3 */
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:88096:1: note: here
npm ERR! 88096 | case OP_NoConflict: /* jump, in3 */
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:89014:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 89014 | p->aCounter[SQLITE_STMTSTATUS_SORT]++;
npm ERR! | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:89029:1: note: here
npm ERR! 89029 | case OP_Rewind: { /* jump */
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:90325:15: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 90325 | pOp->opcode = OP_AggStep1;
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:90328:1: note: here
npm ERR! 90328 | case OP_AggStep1: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:91197:15: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 91197 | pOp->opcode += 2;
npm ERR! | ~~~~~~~~~~~~^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:91200:1: note: here
npm ERR! 91200 | case OP_PureFunc: /* group */
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'fts3SnippetFunc':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164529:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 164529 | case 6: nToken = sqlite3_value_int(apVal[5]);
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164530:5: note: here
npm ERR! 164530 | case 5: iCol = sqlite3_value_int(apVal[4]);
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164530:20: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 164530 | case 5: iCol = sqlite3_value_int(apVal[4]);
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164531:5: note: here
npm ERR! 164531 | case 4: zEllipsis = (const char*)sqlite3_value_text(apVal[3]);
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164531:38: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 164531 | case 4: zEllipsis = (const char*)sqlite3_value_text(apVal[3]);
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164532:5: note: here
npm ERR! 164532 | case 3: zEnd = (const char*)sqlite3_value_text(apVal[2]);
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164532:33: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 164532 | case 3: zEnd = (const char*)sqlite3_value_text(apVal[2]);
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164533:5: note: here
npm ERR! 164533 | case 2: zStart = (const char*)sqlite3_value_text(apVal[1]);
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'fts3ColumnMethod':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164286:14: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 164286 | iCol = p->nColumn;
npm ERR! | ~~~~~^~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:164290:5: note: here
npm ERR! 164290 | default:
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'cellArea':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183792:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183792 | case 5: area = p->aCoord[9].f - p->aCoord[8].f;
npm ERR! | ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183793:7: note: here
npm ERR! 183793 | case 4: area *= p->aCoord[7].f - p->aCoord[6].f;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183793:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183793 | case 4: area *= p->aCoord[7].f - p->aCoord[6].f;
npm ERR! | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183794:7: note: here
npm ERR! 183794 | case 3: area *= p->aCoord[5].f - p->aCoord[4].f;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183794:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183794 | case 3: area *= p->aCoord[5].f - p->aCoord[4].f;
npm ERR! | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183795:7: note: here
npm ERR! 183795 | case 2: area *= p->aCoord[3].f - p->aCoord[2].f;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183795:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183795 | case 2: area *= p->aCoord[3].f - p->aCoord[2].f;
npm ERR! | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183796:7: note: here
npm ERR! 183796 | default: area *= p->aCoord[1].f - p->aCoord[0].f;
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183802:22: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183802 | case 5: area = (i64)p->aCoord[9].i - (i64)p->aCoord[8].i;
npm ERR! | ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183803:7: note: here
npm ERR! 183803 | case 4: area *= (i64)p->aCoord[7].i - (i64)p->aCoord[6].i;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183803:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183803 | case 4: area *= (i64)p->aCoord[7].i - (i64)p->aCoord[6].i;
npm ERR! | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183804:7: note: here
npm ERR! 183804 | case 3: area *= (i64)p->aCoord[5].i - (i64)p->aCoord[4].i;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183804:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183804 | case 3: area *= (i64)p->aCoord[5].i - (i64)p->aCoord[4].i;
npm ERR! | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183805:7: note: here
npm ERR! 183805 | case 2: area *= (i64)p->aCoord[3].i - (i64)p->aCoord[2].i;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183805:21: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183805 | case 2: area *= (i64)p->aCoord[3].i - (i64)p->aCoord[2].i;
npm ERR! | ~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183806:7: note: here
npm ERR! 183806 | default: area *= (i64)p->aCoord[1].i - (i64)p->aCoord[0].i;
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'rtreeCallbackConstraint':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182974:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182974 | readCoord(pCellData+32, &c); aCoord[8] = c.f;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182975:7: note: here
npm ERR! 182975 | case 8: readCoord(pCellData+28, &c); aCoord[7] = c.f;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182976:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182976 | readCoord(pCellData+24, &c); aCoord[6] = c.f;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182977:7: note: here
npm ERR! 182977 | case 6: readCoord(pCellData+20, &c); aCoord[5] = c.f;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182978:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182978 | readCoord(pCellData+16, &c); aCoord[4] = c.f;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182979:7: note: here
npm ERR! 182979 | case 4: readCoord(pCellData+12, &c); aCoord[3] = c.f;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182980:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182980 | readCoord(pCellData+8, &c); aCoord[2] = c.f;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182981:7: note: here
npm ERR! 182981 | default: readCoord(pCellData+4, &c); aCoord[1] = c.f;
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182989:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182989 | readCoord(pCellData+32, &c); aCoord[8] = c.i;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182990:7: note: here
npm ERR! 182990 | case 8: readCoord(pCellData+28, &c); aCoord[7] = c.i;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182991:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182991 | readCoord(pCellData+24, &c); aCoord[6] = c.i;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182992:7: note: here
npm ERR! 182992 | case 6: readCoord(pCellData+20, &c); aCoord[5] = c.i;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182993:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182993 | readCoord(pCellData+16, &c); aCoord[4] = c.i;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182994:7: note: here
npm ERR! 182994 | case 4: readCoord(pCellData+12, &c); aCoord[3] = c.i;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182995:56: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 182995 | readCoord(pCellData+8, &c); aCoord[2] = c.i;
npm ERR! | ~~~~~~~~~~^~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:182996:7: note: here
npm ERR! 182996 | default: readCoord(pCellData+4, &c); aCoord[1] = c.i;
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'rtreeNonleafConstraint':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183048:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 183048 | if( p->op!=RTREE_EQ ) break; /* RTREE_LE and RTREE_LT end here */
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:183051:5: note: here
npm ERR! 183051 | default: /* RTREE_GT or RTREE_GE, or fallthrough of RTREE_EQ */
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'jsonRenderNode':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:179708:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 179708 | if( pNode->jnFlags & JNODE_RAW ){
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:179714:5: note: here
npm ERR! 179714 | case JSON_REAL:
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'jsonReturn':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:179822:7: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 179822 | int_as_real: /* fall through to real */;
npm ERR! | ^~~~~~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:179824:5: note: here
npm ERR! 179824 | case JSON_REAL: {
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'jsonEachColumn':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:181466:9: warning: this statement may fall through [-Wimplicit-fallthrough=]
npm ERR! 181466 | if( p->bRecursive ){
npm ERR! | ^
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:181476:5: note: here
npm ERR! 181476 | default: {
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c: In function 'sqlite3SelectNew':
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:125321:10: warning: function may return address of local variable [-Wreturn-local-addr]
npm ERR! 125321 | return pNew;
npm ERR! | ^~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:125281:10: note: declared here
npm ERR! 125281 | Select standin;
npm ERR! | ^~~~~~~
npm ERR! Release/obj/gen/sqlite3/sqlite3.c:125281:10: note: declared here
npm ERR! In file included from ./src/better_sqlite3.lzz:10,
npm ERR! from ../src/better_sqlite3.cpp:4:
npm ERR! /root/.cache/node-gyp/16.3.0/include/node/node.h:806:7: warning: cast between incompatible function types from 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
npm ERR! 806 | (node::addon_register_func) (regfunc), \
npm ERR! | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
npm ERR! /root/.cache/node-gyp/16.3.0/include/node/node.h:840:3: note: in expansion of macro 'NODE_MODULE_X'
npm ERR! 840 | NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage)
npm ERR! | ^~~~~~~~~~~~~
npm ERR! ./src/better_sqlite3.lzz:15:1: note: in expansion of macro 'NODE_MODULE'
npm ERR! ./src/objects/database.lzz: In static member function 'static void Database::Init(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Object>)':
npm ERR! ./src/objects/database.lzz:129:40: error: cannot convert 'void (*)(void*)' to 'node::Environment*'
npm ERR! In file included from ./src/better_sqlite3.lzz:10,
npm ERR! from ../src/better_sqlite3.cpp:4:
npm ERR! /root/.cache/node-gyp/16.3.0/include/node/node.h:898:38: note: initializing argument 1 of 'void node::AtExit(node::Environment*, void (*)(void*), void*)'
npm ERR! 898 | NODE_EXTERN void AtExit(Environment* env,
npm ERR! | ~~~~~~~~~~~~~^~~
npm ERR! ./src/util/binder.lzz: In static member function 'static bool Binder::IsPlainObject(v8::Isolate*, v8::Local<v8::Object>)':
npm ERR! ./src/util/binder.lzz:36:67: warning: 'v8::Local<v8::Context> v8::Object::CreationContext()' is deprecated: Use MaybeLocal<Context> GetCreationContext() [-Wdeprecated-declarations]
npm ERR! In file included from /root/.cache/node-gyp/16.3.0/include/node/node.h:63,
npm ERR! from ./src/better_sqlite3.lzz:10,
npm ERR! from ../src/better_sqlite3.cpp:4:
npm ERR! /root/.cache/node-gyp/16.3.0/include/node/v8.h:4281:18: note: declared here
npm ERR! 4281 | Local<Context> CreationContext();
npm ERR! | ^~~~~~~~~~~~~~~
npm ERR! make: *** [better_sqlite3.target.mk:125: Release/obj.target/better_sqlite3/src/better_sqlite3.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/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:394:28)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Linux 4.4.0-210-generic
npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm ERR! gyp ERR! cwd /app/node_modules/better-sqlite3
npm ERR! gyp ERR! node -v v16.3.0
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! /root/.npm/_logs/2021-06-07T11_51_00_964Z-debug.log
The command '/bin/sh -c npm i [email protected]' returned a non-zero code: 1
Feature: S3 Support
it would be great if it had S3 support for saving the files instead in local folder, because folder gets huge in no time
also i have build and pushed a docker image here https://github.com/joyboxxx/joybox/pkgs/container/joybox
it will run on every new commit, but i can change it to build on every new release tag if u guys agree ??
Installation not working
Everytime i try to build the image i get this (and it fails):
Running on raspberry pi 3 / ubuntu server
npm notice
npm notice New patch version of npm available! 7.0.3 -> 7.0.5
npm notice Changelog: https://github.com/npm/cli/releases/tag/v7.0.5
npm notice Run npm install -g [email protected]
to update!
npm notice
Removing intermediate container fccab9facd6d
---> 3d3fdc1cbab4
Step 5/32 : COPY package.json .
---> 2aded53152e4
Step 6/32 : COPY package-lock.json .
---> bbad4b174c6d
Step 7/32 : RUN npm i && mv ./node_modules/@types/jsonstream ./node_modules/@types/JSONStream
---> Running in b468559fcd64
npm ERR! code EXDEV
npm ERR! syscall rename
npm ERR! path /app/node_modules/chownr
npm ERR! dest /app/node_modules/.chownr-cyv3QNXu
npm ERR! errno -18
npm ERR! EXDEV: cross-device link not permitted, rename '/app/node_modules/chownr' -> '/app/node_modules/.chownr-cyv3QNXu'
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2020-10-27T18_52_00_548Z-debug.log
The command '/bin/sh -c npm i && mv ./node_modules/@types/jsonstream ./node_modules/@types/JSONStream' returned a non-zero code: 238
can’t build docker image
11am---> d227ff4a65cd
Step 6/33 : RUN npm i && mv ./node_modules/@types/jsonstream ./node_modules/@types/JSONStream
---> Running in a515565aea66
npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: 3.x is no longer supported
npm WARN deprecated [email protected]: Fixed a prototype pollution security issue in 4.1.0, please upgrade to ^4.1.1 or ^5.0.1.
npm WARN deprecated [email protected]: This loader has been deprecated. Please use eslint-webpack-plugin
npm WARN deprecated [email protected]: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated [email protected]: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer
npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated @hapi/[email protected]: Moved to 'npm install @sideway/address'
npm WARN deprecated @hapi/[email protected]: This version has been deprecated and is no longer supported or maintained
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated @hapi/[email protected]: Switch to 'npm install joi'
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Version no longer supported. Upgrade to @latest
npm notice
npm notice New minor version of npm available! 8.5.5 -> 8.6.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.6.0>
npm notice Run `npm install -g [email protected]` to update!
npm notice
npm ERR! code 1
npm ERR! path /app/node_modules/better-sqlite3
npm ERR! command failed
npm ERR! command sh -c prebuild-install || npm run build-release
npm ERR! > [email protected] build-release
npm ERR! > node-gyp rebuild --release
npm ERR! prebuild-install WARN install Request timed out
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 | x64
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! find Python Python is not set from command line or npm configuration
npm ERR! gyp ERR! find Python Python is not set from environment variable PYTHON
npm ERR! gyp ERR! find Python checking if "python3" can be used
npm ERR! gyp ERR! find Python - "python3" is not in PATH or produced an error
npm ERR! gyp ERR! find Python checking if "python" can be used
npm ERR! gyp ERR! find Python - executable path is "/usr/bin/python"
npm ERR! gyp ERR! find Python - version is "2.7.18"
npm ERR! gyp ERR! find Python - version is 2.7.18 - should be >=3.6.0
npm ERR! gyp ERR! find Python - THIS VERSION OF PYTHON IS NOT SUPPORTED
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! find Python **********************************************************
npm ERR! gyp ERR! find Python You need to install the latest version of Python.
npm ERR! gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
npm ERR! gyp ERR! find Python you can try one of the following options:
npm ERR! gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
npm ERR! gyp ERR! find Python (accepted by both node-gyp and npm)
npm ERR! gyp ERR! find Python - Set the environment variable PYTHON
npm ERR! gyp ERR! find Python - Set the npm configuration variable python:
npm ERR! gyp ERR! find Python npm config set python "/path/to/pythonexecutable"
npm ERR! gyp ERR! find Python For more information consult the documentation at:
npm ERR! gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
npm ERR! gyp ERR! find Python **********************************************************
npm ERR! gyp ERR! find Python
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Could not find any Python installation to use
npm ERR! gyp ERR! stack at PythonFinder.fail (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:330:47)
npm ERR! gyp ERR! stack at PythonFinder.runChecks (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:159:21)
npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:266:16)
npm ERR! gyp ERR! stack at PythonFinder.execFileCallback (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:297:7)
npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:390:7)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:527:28)
npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1090:16)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm ERR! gyp ERR! System Linux 4.18.0-348.20.1.el8_5.x86_64
npm ERR! gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--release"
npm ERR! gyp ERR! cwd /app/node_modules/better-sqlite3
npm ERR! gyp ERR! node -v v17.9.0
npm ERR! gyp ERR! node-gyp -v v9.0.0
npm ERR! gyp ERR! not ok
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-04-13T08_43_00_064Z-debug-0.log
[Feature Request] Temporary Download Path and Cleanup
Hi,
I would like to have to following feature:
Downloads should go to a temporary download path and moved after completion. So it would be easier to cleanup a recording box.
Actually the Docker Volume is /app/data/
everything goes to archive
in that folder. I would like to have a incoming
directory with incomplete files which get moved to archive
after completion. In that case I could share archive
folder with e.g. an sftp container, download everything and make a cleanup. The cleanup also could be a button in WebUI.
Actually it's not possible to detect if files are associated with a running ffmpeg e.g. within a script.
Best Regards
P.S: Big thanks for the last fixes.
failed to build LLB: failed to compute cache key: "/.git" not found: not found
ERROR [stage-3 9/10] COPY .git ./.git 0.0s
[stage-3 9/10] COPY .git ./.git:
failed to solve with frontend dockerfile.v0: failed to build LLB: failed to compute cache key: "/.git" not found: not found
i build it on win10 with this error
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.