froggy-service_frontend_1 exited with code 1

frontend_1  |
frontend_1  | ><EMAIL_ADDRESS>serve /app
frontend_1  | > npm i && vue-cli-service serve
frontend_1  |
frontend_1  |
frontend_1  | ><EMAIL_ADDRESS>install /app/node_modules/yorkie
frontend_1  | > node bin/install.js
frontend_1  |
frontend_1  | fs.js:115
frontend_1  |     throw err;
frontend_1  |     ^
frontend_1  |
frontend_1  | Error: EINVAL: invalid argument, open '/app/node_modules/yorkie/package.json'
frontend_1  |     at Object.openSync (fs.js:439:3)
frontend_1  |     at Object.readFileSync (fs.js:344:35)
frontend_1  |     at Object.Module._extensions..json (internal/modules/cjs/loader.js:706:20)
frontend_1  |     at Module.load (internal/modules/cjs/loader.js:599:32)
frontend_1  |     at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
frontend_1  |     at Function.Module._load (internal/modules/cjs/loader.js:530:3)
frontend_1  |     at Module.require (internal/modules/cjs/loader.js:637:17)
frontend_1  |     at require (internal/modules/cjs/helpers.js:22:18)
frontend_1  |     at Object.<anonymous> (/app/node_modules/yorkie/src/utils/get-hook-script.js:5:13)
frontend_1  |     at Module._compile (internal/modules/cjs/loader.js:689:30)
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/code-point-at'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/chownr'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/console-control-strings'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/fs.realpath'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/has-unicode'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ini'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/inherits'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/isarray'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/balanced-match'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/brace-expansion'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ignore-walk'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ms'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minimatch'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/number-is-nan'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/abbrev'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npm-packlist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npm-bundled'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/is-fullwidth-code-point'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/aproba'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/object-assign'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/os-homedir'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/signal-exit'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/os-tmpdir'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/string-width'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/strip-ansi'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/osenv'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/util-deprecate'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/are-we-there-yet'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/strip-json-comments'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/wide-align'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/path-is-absolute'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npmlog'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/gauge'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/wrappy'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/inflight'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/once'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/glob'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rimraf'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/process-nextick-args'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/yallist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minipass'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/yorkie/node_modules/normalize-path'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minizlib'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/fs-minipass'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/yorkie/node_modules/get-stream'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/safe-buffer'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/safer-buffer'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/set-blocking'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ansi-regex'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/strip-indent'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/sax'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/string_decoder'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/core-util-is'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/deep-extend'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/detect-libc'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/delegates'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/concat-map'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/debug'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/mkdirp'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/nopt'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minimist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/tar'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/semver'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rc/node_modules/minimist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/yorkie/node_modules/execa'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/needle'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/yorkie/node_modules/cross-spawn'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/iconv-lite'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/readable-stream'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/node-pre-gyp'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ansi-regex'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/yorkie/node_modules/get-stream'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/@vue/cli-service/node_modules/acorn'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rc/node_modules/minimist'
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
frontend_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
frontend_1  |
frontend_1  | npm ERR! code ELIFECYCLE
frontend_1  | npm ERR! errno 1
frontend_1  | npm ERR<EMAIL_ADDRESS>install: `node bin/install.js`
frontend_1  | npm ERR! Exit status 1
frontend_1  | npm ERR!
frontend_1  | npm ERR! Failed at the<EMAIL_ADDRESS>install script.
frontend_1  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
frontend_1  |
frontend_1  | npm ERR! A complete log of this run can be found in:
frontend_1  | npm ERR!     /root/.npm/_logs/2019-01-02T07_27_48_084Z-debug.log
frontend_1  | npm ERR! code ELIFECYCLE
frontend_1  | npm ERR! errno 1
frontend_1  | npm ERR<EMAIL_ADDRESS>serve: `npm i && vue-cli-service serve`
frontend_1  | npm ERR! Exit status 1
frontend_1  | npm ERR!
frontend_1  | npm ERR! Failed at the<EMAIL_ADDRESS>serve script.
frontend_1  | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
frontend_1  |
frontend_1  | npm ERR! A complete log of this run can be found in:
frontend_1  | npm ERR!     /root/.npm/_logs/2019-01-02T07_28_01_631Z-debug.log
frontend_1  |
frontend_1  | ><EMAIL_ADDRESS>serve /app
frontend_1  | > npm i && vue-cli-service serve
frontend_1  |
frontend_1  |
frontend_1  | ><EMAIL_ADDRESS>serve /app
frontend_1  | > npm i && vue-cli-service serve
frontend_1  |
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/are-we-there-yet'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/gauge'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/once'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/glob'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npmlog'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/inflight'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/code-point-at'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/balanced-match'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/console-control-strings'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/chownr'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/brace-expansion'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/fs.realpath'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/isarray'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/has-unicode'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/inherits'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ini'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minimatch'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ignore-walk'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npm-packlist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ms'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npm-bundled'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rimraf'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/os-homedir'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/number-is-nan'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/is-fullwidth-code-point'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/object-assign'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/osenv'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/os-tmpdir'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/path-is-absolute'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/process-nextick-args'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/safe-buffer'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/safer-buffer'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/signal-exit'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/set-blocking'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/strip-ansi'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/strip-json-comments'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/string-width'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/util-deprecate'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/wide-align'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/wrappy'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/yallist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minipass'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/fs-minipass'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minizlib'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/abbrev'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/aproba'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ansi-regex'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/nopt'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/concat-map'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/core-util-is'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/delegates'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/deep-extend'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/mkdirp'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/detect-libc'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minimist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rc/node_modules/minimist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/sax'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/string_decoder'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/semver'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/debug'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/tar'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/needle'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/iconv-lite'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/readable-stream'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/node-pre-gyp'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/abbrev'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rc/node_modules/minimist'
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
frontend_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
frontend_1  |
frontend_1  | audited 34441 packages in 49.387s
frontend_1  | found 1 high severity vulnerability
frontend_1  |   run `npm audit fix` to fix them, or `npm audit` for details
frontend_1  |  INFO  Starting development server...
frontend_1  |  78% after module and chunk  ERROR  Failed to compile with 1 errors7:35:04 AM
frontend_1  |
frontend_1  |  error  in ./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true&
frontend_1  |
frontend_1  | Module build failed (from ./node_modules/sass-loader/lib/loader.js):
frontend_1  | Error: ENOENT: no such file or directory, scandir '/app/node_modules/node-sass/vendor'
frontend_1  |     at Object.readdirSync (fs.js:786:3)
frontend_1  |     at Object.getInstalledBinaries (/app/node_modules/node-sass/lib/extensions.js:130:13)
frontend_1  |     at foundBinariesList (/app/node_modules/node-sass/lib/errors.js:20:15)
frontend_1  |     at foundBinaries (/app/node_modules/node-sass/lib/errors.js:15:5)
frontend_1  |     at Object.module.exports.missingBinary (/app/node_modules/node-sass/lib/errors.js:45:5)
frontend_1  |     at module.exports (/app/node_modules/node-sass/lib/binding.js:15:30)
frontend_1  |     at Object.<anonymous> (/app/node_modules/node-sass/lib/index.js:14:35)
frontend_1  |     at Module._compile (internal/modules/cjs/loader.js:689:30)
frontend_1  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
frontend_1  |     at Module.load (internal/modules/cjs/loader.js:599:32)
frontend_1  |     at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
frontend_1  |     at Function.Module._load (internal/modules/cjs/loader.js:530:3)
frontend_1  |     at Module.require (internal/modules/cjs/loader.js:637:17)
frontend_1  |     at require (internal/modules/cjs/helpers.js:22:18)
frontend_1  |     at Object.sassLoader (/app/node_modules/sass-loader/lib/loader.js:46:72)
frontend_1  |
frontend_1  |  @ ./node_modules/vue-style-loader??ref--8-oneOf-1-0!./node_modules/css-loader??ref--8-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--8-oneOf-1-2!./node_modules/sass-loader/lib/loader.js??ref--8-oneOf-1-3!./node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true& 4:14-470 14:3-18:5 15:22-478
frontend_1  |  @ ./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true&
frontend_1  |  @ ./src/components/ExampleComponent.vue
frontend_1  |  @ ./src/router.js
frontend_1  |  @ ./src/main.js
frontend_1  |  @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8000/sockjs-node (webpack)/hot/only-dev-server.js ./src/main.js
frontend_1  |

frontend_1  | ><EMAIL_ADDRESS>serve /app
frontend_1  | > npm i && vue-cli-service serve
frontend_1  |
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/balanced-match'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minimatch'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/chownr'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/code-point-at'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/brace-expansion'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/console-control-strings'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/fs.realpath'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/inherits'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ini'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/isarray'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/has-unicode'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ignore-walk'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/signal-exit'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/are-we-there-yet'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/inflight'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/wrappy'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/gauge'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minipass'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/glob'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/aproba'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/fs-minipass'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minizlib'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ms'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/ansi-regex'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/is-fullwidth-code-point'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npm-packlist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/number-is-nan'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/object-assign'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/osenv'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npm-bundled'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/os-homedir'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/os-tmpdir'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/safe-buffer'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/process-nextick-args'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/path-is-absolute'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/safer-buffer'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/strip-json-comments'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/string-width'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/set-blocking'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/strip-ansi'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/util-deprecate'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rimraf'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/wide-align'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/npmlog'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/once'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/yallist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/abbrev'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/deep-extend'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/delegates'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/detect-libc'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/core-util-is'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/debug'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/minimist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/mkdirp'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/concat-map'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/nopt'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/sax'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/string_decoder'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rc/node_modules/minimist'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/semver'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/tar'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/iconv-lite'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/needle'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/readable-stream'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/node-pre-gyp'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/abbrev'
frontend_1  | npm WARN rollback Rolling back<EMAIL_ADDRESS>failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/app/node_modules/fsevents/node_modules/rc/node_modules/minimist'
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
frontend_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
frontend_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
frontend_1  |
frontend_1  | audited 34441 packages in 50.923s
frontend_1  | found 1 high severity vulnerability
frontend_1  |   run `npm audit fix` to fix them, or `npm audit` for details
frontend_1  |  INFO  Starting development server...
frontend_1  |  78% after m ERROR  Failed to compile with 1 errors7:39:28 AM
frontend_1  |
frontend_1  |  error  in ./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true&
frontend_1  |
frontend_1  | Module build failed (from ./node_modules/sass-loader/lib/loader.js):
frontend_1  | Error: ENOENT: no such file or directory, scandir '/app/node_modules/node-sass/vendor'
frontend_1  |     at Object.readdirSync (fs.js:786:3)
frontend_1  |     at Object.getInstalledBinaries (/app/node_modules/node-sass/lib/extensions.js:130:13)
frontend_1  |     at foundBinariesList (/app/node_modules/node-sass/lib/errors.js:20:15)
frontend_1  |     at foundBinaries (/app/node_modules/node-sass/lib/errors.js:15:5)
frontend_1  |     at Object.module.exports.missingBinary (/app/node_modules/node-sass/lib/errors.js:45:5)
frontend_1  |     at module.exports (/app/node_modules/node-sass/lib/binding.js:15:30)
frontend_1  |     at Object.<anonymous> (/app/node_modules/node-sass/lib/index.js:14:35)
frontend_1  |     at Module._compile (internal/modules/cjs/loader.js:689:30)
frontend_1  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
frontend_1  |     at Module.load (internal/modules/cjs/loader.js:599:32)
frontend_1  |     at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
frontend_1  |     at Function.Module._load (internal/modules/cjs/loader.js:530:3)
frontend_1  |     at Module.require (internal/modules/cjs/loader.js:637:17)
frontend_1  |     at require (internal/modules/cjs/helpers.js:22:18)
frontend_1  |     at Object.sassLoader (/app/node_modules/sass-loader/lib/loader.js:46:72)
frontend_1  |
frontend_1  |  @ ./node_modules/vue-style-loader??ref--8-oneOf-1-0!./node_modules/css-loader??ref--8-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--8-oneOf-1-2!./node_modules/sass-loader/lib/loader.js??ref--8-oneOf-1-3!./node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true& 4:14-470 14:3-18:5 15:22-478
frontend_1  |  @ ./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true&
frontend_1  |  @ ./src/components/ExampleComponent.vue
frontend_1  |  @ ./src/router.js
frontend_1  |  @ ./src/main.js
frontend_1  |  @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8000/sockjs-node (webpack)/hot/only-dev-server.js ./src/main.js
frontend_1  |

frontend_1  |
frontend_1  | removed 19 packages, updated 6 packages and audited 34441 packages in 52.417s
frontend_1  | found 1 high severity vulnerability
frontend_1  |   run `npm audit fix` to fix them, or `npm audit` for details
frontend_1  |  INFO  Starting development server...
frontend_1  |  94% after seal ERROR  Failed to compile with 1 errors7:46:21 AM
frontend_1  |
frontend_1  |  error  in ./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true&
frontend_1  |
frontend_1  | Module build failed (from ./node_modules/sass-loader/lib/loader.js):
frontend_1  | Error: ENOENT: no such file or directory, scandir '/app/node_modules/node-sass/vendor'
frontend_1  |     at Object.readdirSync (fs.js:786:3)
frontend_1  |     at Object.getInstalledBinaries (/app/node_modules/node-sass/lib/extensions.js:130:13)
frontend_1  |     at foundBinariesList (/app/node_modules/node-sass/lib/errors.js:20:15)
frontend_1  |     at foundBinaries (/app/node_modules/node-sass/lib/errors.js:15:5)
frontend_1  |     at Object.module.exports.missingBinary (/app/node_modules/node-sass/lib/errors.js:45:5)
frontend_1  |     at module.exports (/app/node_modules/node-sass/lib/binding.js:15:30)
frontend_1  |     at Object.<anonymous> (/app/node_modules/node-sass/lib/index.js:14:35)
frontend_1  |     at Module._compile (internal/modules/cjs/loader.js:689:30)
frontend_1  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
frontend_1  |     at Module.load (internal/modules/cjs/loader.js:599:32)
frontend_1  |     at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
frontend_1  |     at Function.Module._load (internal/modules/cjs/loader.js:530:3)
frontend_1  |     at Module.require (internal/modules/cjs/loader.js:637:17)
frontend_1  |     at require (internal/modules/cjs/helpers.js:22:18)
frontend_1  |     at Object.sassLoader (/app/node_modules/sass-loader/lib/loader.js:46:72)
frontend_1  |
frontend_1  |  @ ./node_modules/vue-style-loader??ref--8-oneOf-1-0!./node_modules/css-loader??ref--8-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--8-oneOf-1-2!./node_modules/sass-loader/lib/loader.js??ref--8-oneOf-1-3!./node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true& 4:14-470 14:3-18:5 15:22-478
frontend_1  |  @ ./src/components/ExampleComponent.vue?vue&type=style&index=0&id=6982cd3a&lang=scss&scoped=true&
frontend_1  |  @ ./src/components/ExampleComponent.vue
frontend_1  |  @ ./src/router.js
frontend_1  |  @ ./src/main.js
frontend_1  |  @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8000/sockjs-node (webpack)/hot/only-dev-server.js ./src/main.js
frontend_1  |


[bitfinex] Adding bitcoin cash as withdrawal type.

Got confirmation from developers via customer support on what withdrawal type to use for bch.

Yaay for undocumented API parameters!
In #2332, I literally found BTG = bgold through trial-and-error.


Unreasonable spline curves

Hi, I am trying to fit a UF2 model for SiC, based on Formation energies and forces, the dataset generated by annealing MD calculation 200~ snapshot configurations.
Here is the splines curve I got for 5/200, 20/200, 40/200, and 80/200 training datasets, respectively.

Where, ridge_1b=1e-6, curvature_2b=1e-4, batch_size=5, weight=0.5
Besides, I also tested smaller curvature_2b values, eg. 1e-2, even 1e-1, unfortunately, as shown below (Training:80/200, curvature_2b=1e-1, batch_size=5), it's also the same case. I would appreciate it if you have any clue about that!!

However, the prediction looks perfect, I kinda confused by this.

For your information, here is the pair distribution of SiC dataset:

Hi, another piece of information.
I am trying to repeat the training for NeXe, so I found the example ipynb file, and the dataset "dump.lammpstrj" on my own laptop, and It works very well!!
Afterward, I used FHI-AIMS to do a single-point calculation for this NeXe dataset, because, honestly, I am not familiar with Lammps. Then I got a new file named "dft.xyz", which contains the same structures, but new energy and forces data, so I re-run the example "ipynb" file again, unfortunately, It came out a weird  Splines picture, as shown below:

It's obvious that there must be something wrong inside, and maybe some details that I neglected,  so I uploaded the new dataset "dft.xyz" and new "pair_potential_demo.ipynb" file here (where I only edit two places, in order to read from a xyz file), and hope you can have a look recently, since I am struggle on this problem (perfect prediction, but seems unreasonable splines fitting). Probably it's my bad, according to my past experience, I usually did stupid things, well.., but I would appreciate it if you have any clues about it.

Hi @MengnanCui, thanks for sharing the figures and your troubleshooting process. The problem in your Si-C curve is one that we have seen too. It occasionally happens when the lower bound for a particular chemical interaction is lower than the smallest observed distance of that type in the dataset. The curvature regularization is also failing here and it looks like it is simply extrapolating with negative curvature.
The upcoming 0.2.0 release includes a postprocessing feature to adjust the spline coefficients at small coefficients to enforce repulsion. Feel free to preview that function on our development branch.
The WIP demo on the development branch includes some of the other upcoming functions which might be helpful.

@MengnanCui I downloaded your Ne-Xe FHI-AIMS dataset and took a look at your jupyter notebook. I reran it with one modification in the "Initialize Basis" section, where I set "offset_1b" to True. In LAMMPS, the energy of an isolated atom is zero; this is not the case for VASP or, apparently, FHI-AIMS. Once I allowed UF3 to fit the one-body terms, the potentials look good.
It looks like the FHI-AIMS reference energies were about -104685 per Ne and -104678 per Xe, which explains why the two-body terms were trying to compensate and became so extreme. The two-body potentials I got had potential wells of about -0.0005.

@MengnanCui Version 0.2.0 is now available. Please reopen this issue if your new potentials are unsatisfactory.

Thanks so much for your very kind and helpful replies!!!


Serial Communication now working on MacOS

MacOS 10.15.4
my board is new revision; I needed to connect BP3 is explained here to enable itdump.

$ ls -l /dev/cu.*
crw-rw-rw-  1 root  wheel    9,   7 May  2 16:45 /dev/cu.usbmodem143403

and I actually have both tty.x and cu.x
ls /dev | rg "usbmodem143403"
cu.usbmodem143403
tty.usbmodem143403

board connected via USB-STLINK.
echo-ing into either of the above just hangs, and the terminal never exits anymore, even with ctrl-c.
During all stages, I have openocd open.
also, when minicom is connected to the tty variant above, with the loopback enabled (shorting PC4 and PC5), I cannot see anything as I type. Consequently, I've tried section 11.1 and the one byte is not transmitted back to the host

Perhaps something with the macos setup is broken?

I'm also stuck at section 10. I think at this step we just need the USB to serial module plugged in, nothing to the discovery board. However, it's just hanging for me as well.
The echo/minicom commands freeze the terminal forever whether I'm using the cu or tty file under /dev.
Mine dev usb devices look like this:
❯ ls -l /dev | grep usb
crw-rw-rw-  1 root  wheel           18,   5 May  9 09:23 cu.usbserial-0001
crw-rw-rw-  1 root  wheel           18,   4 May  9 09:23 tty.usbserial-0001

How were you to connecting to the board? Through the ST-LINK port or the USB USER port?


Question about wizard armor

QUESTION:
has the full set of wizard armor been implemented yet? I want the full armor set boost, but idk if the rest has been made yet.

Yes, all 4 pieces exist. You need to add the robes example for them to show up in the RP and be craftable.
/mexample add robes

Alrighty! Is there any other custom recipes I can add using the commands?

Oh, tab complete shows me the stuff I can add

I have purple wool and it doesnt show me the crafting recipe for it

Ah, theres another pack

It still doesnt show the item even after installing the resource pack

Do I have to restart the server after applying the changes?

You may need to restart, but shouldn't. Try the recipe even if it's not showing up in your book.
https://magic.elmakers.com/#crafting


Only the information requested by the scope is not imported. and not response phone_number data

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Only the information requested by the scope is not imported

Check the personal information items that can be received when logging in on the Kakao developer site.
Try OAuth kakao login

await supabase.auth.signInWithOAuth(
OAuthProvider.kakao,
scopes: "profile_image,name,gender,birthday,birthyear,phone_number"
)

It says it's an incorrect request.
I didn't request profile_nickname, but it shows that I set it up and requested it.

not response phone_number data

Check the personal information items that can be received when logging in on the Kakao developer site.
Try OAuth kakao login

await supabase.auth.signInWithOAuth(
OAuthProvider.kakao,
scopes: "profile_image,name,gender,birthday,birthyear,phone_number"
)

empty phone data in response data.

Screenshots

Version (please complete the following information):
flutter 3.13.9
supabse_flutter ^2.3.3

@dshukertjr
scope settings page

https://developers.kakao.com/console/app/1037204/product/login/scope

kakao error url

https://kauth.kakao.com/oauth/authorize?client_id=ad984dd9054b7bf27410f4425dc31901&flow_type=pkce&redirect_uri=https%3A%2F%2Ftpagdfpibubnmmjfdlnh.supabase.co%2Fauth%2Fv1%2Fcallback&response_type=code&scope=account_email+profile_image+profile_nickname+profile_image+name+gender+birthday+birthyear+phone_number&state=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE3MDg1MDAzMzgsInNpdGVfdXJsIjoiY29tLmV4YW1wbGUuY2h1cmNoOi8vb2F1dGgiLCJpZCI6IjAwMDAwMDAwLTAwMDAtMDAwMC0wMDAwLTAwMDAwMDAwMDAwMCIsImZ1bmN0aW9uX2hvb2tzIjpudWxsLCJwcm92aWRlciI6Imtha2FvIiwicmVmZXJyZXIiOiJjb20uZXhhbXBsZS5jaHVyY2g6Ly9vYXV0aCIsImZsb3dfc3RhdGVfaWQiOiJmOWI1OTI5OS1lMGVhLTQzMzUtYjZkYi0yYmI5YWJjMjY3ZGUifQ.abg9e9SqjFXJ1I96DKmbpE0uf0IRUyqy_UaTgL1VlKY

And when I checked the auth log in the suppbase dashboard, I didn't receive not only the phone but also the birthdat birthyaer data.

@lightofjeju

https://github.com/supabase/gotrue/blob/757989c1d3856a1dc450c2e0a5cb1c8e0172a6a6/internal/api/provider/kakao.go#L82-L86

It seems to be requested because the above three scopes are always put in by default.
To modify, we need to modify the logic related to scopes, but other providers have the same logic, which seems to be intended maybe.

Thank you for your answer.
Then, do you have any intention to make the oauthScopes value customizable?

@doong-jo
Thank you for your answer.
Then, do you have any intention to make the oauthScopes value customizable?

@dshukertjr
hello!
Who should I ask about this issue?
I added the phone_number value to scopes, but I am not receiving the phone_number value.
If this function doesn't work, I can't use the supabase auth and I think I'll have to link it with Kakao directly.. 🥲

@lightofjeju
Our auth team will have a look at this issue whenever possible. Thanks for your patients.

It can be solved by create a trigger to the user table to create an edge function that get additional information from KAKAO.
for example
serve(async (req) => {
  const { record }: WebhookPayload = await req.json();

  const appMetaData = record.raw_app_meta_data as RawAppMetaData;
  const userMetaData = record.raw_user_meta_data as RawUserMetaData;

  if (appMetaData.provider === "kakao") {
    kakaoSignUp(record.id, userMetaData);
  }
});

@lightofjeju that's because the auth service requires these scopes by default


Remove artificial timeout in FirestoreV1IT, Dataflow runner is very slow

Dataflow runner takes much longer to run any IT test, the artificial timeout added in FirestoreV1IT makes the test flaky, other IT tests don't set this timeout and many of them can run >10 minutes on Dataflow runner.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run PostCommit_Java_Dataflow

Run PostCommit_Java_DataflowV2

R: @ahmedabu98

LGTM
R: @robertwb

Run Java PreCommit

Run Java PreCommit

Firestore tests passed for both Dataflow v1 and v1 in the above runs (failures are unrelated) so we can merge when Java PreCommit passes.

Run Java PreCommit


Added Spanish translation

I translated a couple of strings for the Spanish language consoles

You have changed _en file to _es, please add separate _es file instead.

Oh, sorry. My mistake! I will close this pull request and open a new one!


[AMBARI-24433] [Log Search UI] Reset to default selection in the drop…

What changes were proposed in this pull request?

default selection property has been added to dropdown list component: initialised on init or on the first onChanges when the default selection is empty
link to clear to default when it is enabled and has default selection

How was this patch tested?
It was tested manually and by unit tests:
PhantomJS 2.1.1 (Mac OS X 0.0.0): Executed 268 of 268 SUCCESS (8.679 secs / 8.57 secs)
✨  Done in 38.62s.

Please review Ambari Contributing Guide before opening a pull request.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3633/
Test FAILed.
Test FAILured.

The test failure is not connected to the change.


Adding 9 videos to the html course in 3 topics

🛠 Fixes Issue  #430
The three topics are

Lists
Tables
Styles and Semantics

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers

📷 Screenshots

Please review this PR @arpit456jain @KKhushhalR2405 @singhmansi25 @raghavTinker

@muhammadgalhoum 20+ videos are uploaded on yt
since its end of gssoc add videos as much as possible in one PR

@muhammadgalhoum 20+ videos are uploaded on yt since its end of gssoc add videos as much as possible in one PR

So far, there are only 32 videos, and I have added all the videos that have explanations on the site
Do you mean that there are new videos uploaded now? @arpit456jain


Specify multiple 'named' media query parameters for interchange?

A feature request I suppose, to make interchange more friendly / powerful.  A format to combine multiple 'named' media queries for interchange.  For example, say I want an interchange to fire only when both the named queries large && retina are met.
For example something like:
data-interchange="[image_path, (default)], [image_path, (large, retina)]"
- or -
data-interchange="[image_path, (default)], [image_path, (large and retina)]"

The docs explicitly states this is possible at https://github.com/zurb/foundation/blob/5eab832da39d677ec66bbded558916fcd070ac27/doc/pages/components/interchange.html#L78
"
You can easily include retina images by using a pixel-density media query for that image. You can even combine multiple parameters in the media query if need be. The retina media query would look something like this, but you can also use dpi or other pixel densities as well:
"
I can achieve this by injecting in the raw media query, but as soon as retina gets involved, that's 5 lines, each appended with an and (min-width: Xpx) to match the breakpoint I want to achieve.  Also, this current implementation is hardcoding breakpoints, so any change to these wouldn't be updated, whereas if this could be supported by the named queries, you'd still be in business.
Be interested to know your thoughts
Thanks!

We added this to our "components" section in our planning board for the next version. A PR would be valuable to the community, otherwise It will be addressed then. You can see and vote on the proposed updates here: https://trello.com/b/QBPKlQqf/foundation-sites


Add support for streaming in function calling

Description
PR to add support for streaming in function calling.
Fixes # (issue)
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[ ] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[ ] Yes
[ ] No

Type of Change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

[ ] I added new unit tests to cover this change
[ ] I believe this change is already covered by existing unit tests

Suggested Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

I'm looking to implement function calling streaming into my application. Is this work almost done? Is any assistance needed?

There is still work needed here. I will most likely get it done by Wednesday. Will that work for you?


Bazel build error. Warning on retrieving an archive which is not found and then fails.

Hi fellow developers,
I am trying to build Tensorflow from source on Windows using the tutorial on the website (https://www.tensorflow.org/install/source_windows) but I have an issue when i get to the bazel build of tensorflow
I am using this command to build since I have cuda and cudnn installed on my computer. (When i did the ./configure it found them and I could specify the compute capability for example) :
bazel build --config=opt --config=cuda --define=no_tensorflow_py_deps=true --copt=-nvcc_options=disable-warnings //tensorflow/tools/pip_package:build_pip_package
Here is the trace starting a little before it could not found an archive and then fails.
INFO: Repository local_config_cuda instantiated at:
  C:/users/me/desktop/ia/tensorflow-master/WORKSPACE:15:14: in <toplevel>
  C:/users/me/desktop/ia/tensorflow-master/tensorflow/workspace2.bzl:870:19: in workspace
  C:/users/me/desktop/ia/tensorflow-master/tensorflow/workspace2.bzl:96:19: in _tf_toolchains
Repository rule cuda_configure defined at:
  C:/users/me/desktop/ia/tensorflow-master/third_party/gpus/cuda_configure.bzl:1448:33: in <toplevel>
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/8b8793a6d3d528e9b190ab7f9b85fea2f1aadc2c.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
ERROR: An error occurred during the fetch of repository 'local_config_cuda':
   Traceback (most recent call last):
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/gpus/cuda_configure.bzl", line 1401, column 38, in _cuda_autoconf_impl
                _create_local_cuda_repository(repository_ctx)
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/gpus/cuda_configure.bzl", line 1239, column 56, in _create_local_cuda_repository
                host_compiler_includes + _cuda_include_path(
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/gpus/cuda_configure.bzl", line 364, column 32, in _cuda_include_path
                inc_entries.append(realpath(repository_ctx, cuda_config.cuda_toolkit_path + "/include"))
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/remote_config/common.bzl", line 290, column 19, in realpath
                return execute(repository_ctx, [bash_bin, "-c", "realpath \"%s\"" % path]).stdout.strip()
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/remote_config/common.bzl", line 230, column 13, in execute
                fail(
Error in fail: Repository command failed
/usr/bin/bash: line 1: realpath: command not found
ERROR: C:/users/me/desktop/ia/tensorflow-master/WORKSPACE:15:14: fetching cuda_configure rule //external:local_config_cuda: Traceback (most recent call last):
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/gpus/cuda_configure.bzl", line 1401, column 38, in _cuda_autoconf_impl
                _create_local_cuda_repository(repository_ctx)
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/gpus/cuda_configure.bzl", line 1239, column 56, in _create_local_cuda_repository
                host_compiler_includes + _cuda_include_path(
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/gpus/cuda_configure.bzl", line 364, column 32, in _cuda_include_path
                inc_entries.append(realpath(repository_ctx, cuda_config.cuda_toolkit_path + "/include"))
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/remote_config/common.bzl", line 290, column 19, in realpath
                return execute(repository_ctx, [bash_bin, "-c", "realpath \"%s\"" % path]).stdout.strip()
        File "C:/users/me/desktop/ia/tensorflow-master/third_party/remote_config/common.bzl", line 230, column 13, in execute
                fail(
Error in fail: Repository command failed
/usr/bin/bash: line 1: realpath: command not found
INFO: Found applicable config definition build:cuda in file c:\users\me\desktop\ia\tensorflow-master\.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
INFO: Found applicable config definition build:cuda in file c:\users\me\desktop\ia\tensorflow-master\.bazelrc: --repo_env TF_NEED_CUDA=1 --crosstool_top=@local_config_cuda//crosstool:toolchain --@local_config_cuda//:enable_cuda
WARNING: The following configs were expanded more than once: [cuda]. For repeatable flags, repeats are counted twice and may lead to unexpected behavior.
ERROR: @local_config_cuda//:enable_cuda :: Error loading option @local_config_cuda//:enable_cuda: Repository command failed
/usr/bin/bash: line 1: realpath: command not found

I am really sorry if it appears to be a problem on my side but since I can't retrieve the archive I think it is best to start here first.
Thank you for your help and your job.

Problem solved here :
https://discuss.tensorflow.org/t/error-building-tensorflow-2-8-in-windows-10/7984/3

@GosuPaper ,
Please refer this link 1 and 2 with the similar error.It helps.Thanks!

Problem solved here : https://discuss.tensorflow.org/t/error-building-tensorflow-2-8-in-windows-10/7984/3
Sorry for the inconvenience

Here is the answer to my problem @tilakrayal . Sorry for the incovenience and thanks for your help

@GosuPaper ,
Glad the issue is resolved for you, please feel free to move this to closed status.


version(4.50.0 ) Should be able to add a new plugin directory non interactively or at least have node_modules [cli-parent-directory] parent (project node_modules)

? Select the action on the directory list Learn more
A plugin scan searches this directory list for plugins.
You can add or remove from this list to change the scan behavior, and consequently its outcome.
There are three well-known directories that the CLI usually scans for plugins.
cli-parent-directory
cli-parent-directory is the directory that contains the Amplify CLI Core package.
/home/jair/-hidden-/node_modules/@aws-amplify/
cli-local-node-modules
cli-local-node-modules is the Amplify CLI Core package's local node_modules directory.
/home/jair/-hidden-/node_modules/@aws-amplify/cli/node_modules
global-node-modules
global-node-modules is the global node_modules directory.
/home/linuxbrew/.linuxbrew/lib/node_modules

Hi @jsbjair we don't support installing the CLI locally; it must be installed with the global option. Are you seeing any issues when installing globally?

No, I tried to create a pipeline using bitbucket and because cache, I installed it locally. And because plugin is not activated, i thought to use the plugin configure directory command. But I found, that amplify creates a config in ~, and is always interactive, even it can be used headless

Plugins should be configured the first time any amplify command is executed after install. The plugin configure command should only be necessary when installing a new plugin.
We do have headless support for some amplify commands. Docs can be found here: https://docs.amplify.aws/cli/usage/headless
If you're running into any specific issues with a headless command not working, please open a new issue for that.


mavlink: lock sending messages outside

This is an attempt to prevent any of the 3 parts of a MAVLink message to end up on the buffer without the other parts. When partial messages end up on the buffer it will cause message drops because the parser reads too far and will miss the subsequent message.
By locking around the full process and preventing races between the message senders in the receiver thread and the actual sending threads we prevent message drops which e.g. leads to a cleaner initial param download.
This is an alternative to #12967. The param download works equally well, so 100% for the tested cases but CPU usage of the MAVLink threads is almost doubled, so this PR is clearly much worse.
I'm not sure why that's the case though it must have something to do with the locking.
For the test data, check: https://docs.google.com/spreadsheets/d/1aAT58x1zVd6_5bL9NjCOnc87Eoy4Aa3QMd-cmwZXI8A

#12967 is better, closing.


Demo database 1000 users 5000 posts per user

In chapter 13 the book states:
"In our demo database, there are 1,000 users (authors), each with 5,000
posts. The posts table requires around 480 megabytes of disk space."
Question:
How can we create this amount of data, to allow demonstrate the execution plans and analyze statements?
The setup seems to insert only a few rows. Is there anywhere a script to create the chapter prerequsites?

Good issue.
You can generate the specified amount of data with something like:
INSERT INTO users( username, gecos, email )
SELECT 'user-' || v, 'Automatically generated user #' || v, 'author'|| v ||<EMAIL_ADDRESS>FROM generate_series( 1, 1000 ) v;

INSERT INTO posts( title, content, author, category, editable )
SELECT 'Thread-' || v, 'A question here for thread ' || v, a.pk, v % 3 + 1, case v % 2 when 0 then true else false end
FROM generate_series( 1, 5000 ) v, users a;

and you can check the amount of generated data with something like:
select a.username, count( p.pk )
from users a join posts p on p.author = a.pk
group by a.username;

select pg_size_pretty( pg_table_size( 'posts' ) );

Please note that the above set of commands could create a table posts with around 1.2 GB in size, if you want to stick near 400 MB remove the content column, such as in
INSERT INTO posts( title,  author, category, editable )
SELECT 'Thread-' || v,  a.pk, v % 3 + 1, case v % 2 when 0 then true else false end
FROM generate_series( 1, 5000 ) v, users a;

Hi Luca,
Many thx for your supports. After some progress in Postgres (thx to your book) I've managed to create similar solution.
Best Regards.
pluraltouch


neovim-qt: 0.2.12 -> 0.2.15

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @
nix-review failed with the following error, but I was able to compile it and run sucessfully on my machine
builder for '/nix/store/2327mmims9ypfc5vlzrz6jc0yzy302nw-luajit-2.1.0-beta3-env.drv' failed with exit code 1; last 2 log lines:
  created 16 symlinks in user environment
  /nix/store/wpi89y86krq9rbvwcbx0hc36ibp5d0v7-stdenv-linux/setup: line 320: [@]: bad substitution
cannot build derivation '/nix/store/i9l40vp8mw2vb7w1qi4ba8j808nsz18p-neovim-unwrapped-0.4.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/nyf3avymprn7wm0can324s2nfdxs6yvc-neovim-0.4.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/kl0xsxpmbsdjkdah8il9vag494s9b5cw-neovim-qt-unwrapped-0.2.15.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/034v125nihgnv1282jmdydan1x20gn0f-neovim-qt-0.2.15.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/yvcd9rwf77pdzlcqagaqa4z8a0f875p2-env.drv': 1 dependencies couldn't be built
[0 built (1 failed)]
error: build of '/nix/store/yvcd9rwf77pdzlcqagaqa4z8a0f875p2-env.drv' failed
1 package failed to build:
neovim-qt

[0.0 MiB DL]
error: build log of '/nix/store/034v125nihgnv1282jmdydan1x20gn0f-neovim-qt-0.2.15.drv' is not available
$ nix-shell /home/dema/.cache/nix-review/rev-e40adc8788c506ff24a4dec5cf83b8c26dadecfc-1/shell.nix```

Is there anything else I should do to this PR?..

Thank you for the PR and your patience @Dema!


Unable to login on MacOS

My account password contains a "^" (this symbol somehow cannot be typed) and I cannot copy-paste the password from my password manager into the form.
As a result I cannot use the App 😢

Sadly, I don't think this is anything we can fix. Seems like a problem in electron :/

We can add a button that will be used to paste. Will release it in the next update.


Dark Theme added [ Do not Merge]

[Current coverage][cc-pull] is 14.48%

Merging [#430][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #430   diff @@
==========================================
  Files             2          2
  Lines           214        214
  Methods          25         25
  Messages          0          0
  Branches         31         31
==========================================
  Hits             31         31
  Misses          183        183
  Partials          0          0

Powered by Codecov. Last updated by [8ba0e71...af9e666][cc-compare]
[cc-base-branch]: https://codecov.io/gh/fossasia/open-event-webapp/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/fossasia/open-event-webapp/compare/8ba0e71cf5bfe63ac41a1a37fbc87fca76cb2f49...af9e66627d378656a76ef6655001c7090a4d4f97?src=pr
[cc-pull]: https://codecov.io/gh/fossasia/open-event-webapp/pull/430?src=pr


BufReader: buffer size set to 1MB

benchmark test gives pretty much the same result on disk

PTAL @feuerste

Can you please update the description of this PR and explain its reasoning a bit?

the modifications are not necessary anymore.


refactor: 🔧 update dev workspace and project structure to align with frontend

Updates the development VS Code workspace and sorting order.

Additionally, updates backend project structure to align with the frontend

Reverted refactor of backend to limit PR scope to workspace file.


Weights for rasters or arrays with missing data

Hi,
I was wondering if there is a way to assign weights to an array or raster using one of the weight functions? Or to change weights to take into account that there are missing data (e.g., GIS rasters). Here's a simple example of what I have in mind...
from scipy.stats import norm
import numpy as np

#Create raster without missing values
yp = norm.rvs(0,10,size=(5,5))
yp_f=yp.flatten()

# Weights
w=pysal.lat2W(5,5, rook=False)

# Works fine
lm = pysal.Moran_Local(yp_f,w)

# Include missing values
yp[:,0] = np.nan
yp_f=yp.flatten()

# Wrong answer, since it maintains weights
lm = pysal.Moran_Local(yp_f,w)

# Identify missing
miss = np.isnan(yp_f)
missn = np.arange(0,len(miss))[miss]

# Drop missing from weight object?

missn shows which cells should not be included. Is there a way to edit the w object to take this into account? Or is there a function that will create the weights based on the actual raster?
Thanks for the help.

The following code changes the dictionary of weight by dropping all NaN cells. Assigning it to w.neighbors seems to correctly change the structure of w, but it is not able to compute things correctly and throws back an error at the end. Any help would be appreciate it.
cneighbors = {}
for i in missn:
    for key, value in w.neighbors.items():
        if key != i:
            if i in value:
                value = value.remove(i)
            if value is not None:
                cneighbors[key] = value

w.neighbors = cneighbors
lm = pysal.Moran_Local(yp_f,w)

ValueError: row, column, and data array must all be the same length

Ok...looking at the code I figured out what was causing the error. I also needed to change the weights. There was also a mistake in the previous code for dropping missing data
missn = set(np.arange(0,len(miss))[miss])
cneighbors = {}
for key, value in w.neighbors.items():
    if key not in missn:
        value = list(set(value).difference(missn))
        cneighbors[key] = value

cweights = {}
for key, value in cneighbors.items():
    cweights[key] = (np.ones_like(value)/len(value)).tolist()
w2 = pysal.W(cneighbors, cweights)
yp_f2 = yp_f[np.isnan(yp_f)==False]
lm2 = pysal.Moran_Local(yp_f2,w2)

Now it produces the data. Still trying to figure out if the output is correct.

Here's a function to implement this. May create a pull request once I figure out where it could go,  and if there's interest in this.
def raster_weights(raster, rook=False, *args, **kwargs):
    """
    Construct PySal weights for rasters
    It drops weights for all cells that have no data or are Inf/NaN
    Usage:

    w = raster_weights(raster, rook=False, *args, **kwargs)

    where
        raster: (Masked) Numpy array for which weights are to be constructed
        rook: Boolean, type of contiguity. Default is queen. For rook, rook = True
        the rest of arguments are passed to pysal.lat2W
    """
    rasterf=raster.flatten()
    w=pysal.lat2W(*raster.shape, rook=rook, *args, **kwargs)

    # Identify missing/no data
    if type(rasterf)==numpy.ma.core.MaskedArray:
        miss = rasterf.mask
    else:
        miss = np.logical_or(np.isnan(rasterf),np.isinf(rasterf))
    missn = set(np.arange(0,len(miss))[miss])

    cneighbors = {}
    for key, value in w.neighbors.items():
        if key not in missn:
            value = list(set(value).difference(missn))
            cneighbors[key] = value

    cweights = {}
    for key, value in cneighbors.items():
        cweights[key] = (np.ones_like(value)/len(value)).tolist()
    w = pysal.W(cneighbors, cweights)
    return w

Does this get to what you are interested in:
import pysal as ps
import numpy as np

def raster_weights(raster, missing, rook=False):
    w = ps.lat2W(*raster.shape, rook=rook)
    neighbors = w.neighbors.copy()
    for unit in missing:
        u_neighbors = neighbors[unit]
        for u_neighbor in u_neighbors:
            neighbors[u_neighbor].remove(unit)
        neighbors.pop(unit)
    return(ps.W(neighbors))

>>> raster = np.arange(9) * 10
>>> raster.shape = (3, 3)
>>> raster

array([[ 0, 10, 20],
       [30, 40, 50],
       [60, 70, 80]])
>>> w_0 = ps.lat2W(*raster.shape, rook=False)
>>> w_0.transform = 'r'
>>> y = raster.flatten()
>>> ps.lag_spatial(w_0, y)

array([ 26.66666667,  28.        ,  33.33333333,  36.        ,
        40.        ,  44.        ,  46.66666667,  52.        ,  53.33333333])
>>> (10 + 30 + 40) /3.
26.666666666666668
>>> missing = [1, 8]
>>> w_1 = raster_weights(raster, missing)
>>> y_1 = np.delete(y, missing)
>>> y_1
array([ 0, 20, 30, 40, 50, 60, 70])
>>> y
array([ 0, 10, 20, 30, 40, 50, 60, 70, 80])
>>> w_1.transform = 'r'
>>> ps.lag_spatial(w_1, y_1)

array([ 35.        ,  45.        ,  42.5       ,  38.33333333,
        43.33333333,  46.66666667,  45.        ])

@sjsrey Thanks for getting back to me.
Indeed, it generates the same result as in my function above. The main difference is the inputs and the order of some of the neighbors (although that should affect any of the results). Any reason there is no material on rasters in PySal (or for that matter there seems to be an emphasis in the literature /software packages on spatial correlation on geometries, but nothing on rasters)?

I've included part of your in my function
def raster_weights(raster, rook=False, transform = 'r', **kwargs):
    """
    Construct PySal weights for rasters
    It drops weights for all cells that have no data or are Inf/NaN
    Usage:

    w = raster_weights(raster, rook=False, *args, **kwargs)

    where
        raster: (Masked) Numpy array for which weights are to be constructed
        rook: Boolean, type of contiguity. Default is queen. For rook, rook = True
        the rest of arguments are passed to pysal.lat2W
    """
    rasterf=raster.flatten()
    if len(raster.shape) == 1:
        shape = (np.sqrt(raster.shape[0]) * np.array([1,1])).astype(int)
    else:
        shape = raster.shape
    w=pysal.lat2W(*shape, rook=rook, **kwargs)

    # Identify missing/no data
    if type(rasterf)==numpy.ma.core.MaskedArray:
        miss = rasterf.mask
    else:
        miss = np.logical_or(np.isnan(rasterf),np.isinf(rasterf))
    missn = set(np.arange(0,len(miss))[miss])

    cneighbors = {}
    for key, value in w.neighbors.items():
        if key not in missn:
            value = list(set(value).difference(missn))
            cneighbors[key] = value
    w = pysal.W(cneighbors)
    w.transform = transform
    return w

which seems to be much faster than your implementation (at least on the $5\times5$ vector above.
%time raster_weights2(raster, missn)
CPU times: user 1.65 ms, sys: 563 µs, total: 2.21 ms
Wall time: 1.75 ms
Out[311]: <pysal.weights.weights.W at 0x10fc8ed10>

%time raster_weights(raster)
CPU times: user 715 µs, sys: 25 µs, total: 740 µs
Wall time: 920 µs
Out[312]: <pysal.weights.weights.W at 0x10c9e6f10>

@ozak thanks for pushing forward on this.
On the ordering of the weights, it is important to ensure that the order matches that in the corresponding attribute vector, otherwise the calculation of things like spatial autocorrelation coefficients and the spatial lag will be incorrect.
On the raster question, PySAL's origins were in vector based spatial analysis so rasters were not a key focus of the original developers. That said, if interested developers want to include support for rasters, we are open to it :->
On that score, for raster weights it may be more memory-efficient to calculate them on the fly rather than storing all the neighbors. Otherwise as the raster size grows, so too will the memory requirements of the weights structure. Of course there will be a trade-off in loss of speed for doing the weights on the fly rather than in-memory, but something to consider.

@sjsrey I am still trying to figure out if there is way of doing it cleanly. I was trying to implement some spatial correlation methods of PySal for my GeoRasters package, where I can ensure this done correctly using the a function map_vector and doing it internally. I am still trying go over PySal to know what else is there and how to implement it. I may try to link as many functions as possible or that could be useful to people using GIS rasters. Otherwise I would only do it for some functions I need at the moment and leave people to use similar code for their own use case by case.
One option could be to do all this under the hood in PySal, i.e. that PySal constructs and performs all the computations using the flattened raster. But I imagine this may require a lot of reqriting, unless one can adapt the basic classes to take care of this. I am not knowledgable enough about PySal at the moment, so I am not sure.

@sjsrey I have added the global spatial autocorrelation measures to my package (ozak/georasters@d6b1169). Since GeoRasters keeps properties of the raster with it, these were easy to add. Using the above function it is easy to compute any of these measures for any raster by executing
rasterf = raster.flatten()
nonmiss = rasterf.mask==False
gamma = pysal.Gamma(rasterf[nonmiss], w)

and similarly for the other global measures.

@ozak very nice to see the work on georasters :+1:
I would be happy to help out over on georasters on the pysal interface if that would be of interest.
If so, I think one place that would be a good target would be to add some tests on the missing/mask properties for the raster and the W objects to ensure the alignment is correct. I think it is best to iron that out before moving on to the local autocorrelation stats.
Let me know if this makes sense. If it does, we can close the ticket here and move the discussion over to
georasters.

@sjsrey that sounds perfect!

Closing this here and working on downstream issue https://github.com/ozak/georasters/issues/13


Lazy Load similar script information

In relation to #272
I ran some telemtry locally and noticed the similarity calculation was taking over 300ms out of the total 400ms load time for a script. This pr creates a new api to retrieve similar scripts allowing the main script to be rendered while fetching the data in the background. This has reduced the network request of a script to ~ 25ms locally.
I am unsure on how this will affect production, but would be good to see :). Similar scripts will still take a couple seconds to load likely, but I don't believe people are rushing to view those straight away. I've added a very simple loading dialog to give some user feedback (tried to add a svg but the way the azure storage was setup made it hard locally)
I dont know much about django so am happy for any feedback.

@AdmiralGT any thoughts on this? woudl be keen to either test it out on a test site, or release it to see if it helps with performance

Apologies, I'll try and take a look at this tonight.

This is still on my radar but I haven't got around to it yet I'm afraid. I suspect everything here is fine, I've just not been able to find the time and energy to test out the changes. I do really appreciate the PR and I will hopefully get to this soon.

@AdmiralGT its all good, I didn't want to put any extra stress on you or anything aha and this change is kinda weird in a way? I have a few other script related things I wanted to try that may be cool but also might be better as a seperate project but I'll take a look after there's time for this Pr before I overload you on reviews aha. Keep up the great work :D


Filter by temporary istio domains

A short explanation of the proposed change:

Operators can add a list of istio domains to the copilot.temporary_istio_domains property in the manifest. Cloud Controller then filters routes sent to Copilot based on whether they're associated with an Istio domain.

An explanation of the use cases your change solves
Tracker Story

Links to any other associated PRs
https://github.com/cloudfoundry/capi-release/pull/111

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the master branch

[x] I have run all the unit tests using bundle exec rake

[x] I have run CF Acceptance Tests

LGTM! Will merge when comments on the capi-release PR are addressed. :thank-you:


Implement the exception vectors

#3 added a statically built archive of the execption vectors (taken from an IDF project) For most of the symbols, we simply need to install the vectors into the right place in memory, the WindowOverflow and WindowUnderflow vectors.
Some for some vectors, we want to be able to specify user handlers for these exceptions to troubleshoot system level faults. In which case, by using the prebuilt vectors from IDF we also have to use the idf mechanism for doing so, see xtensa_intr.

Also closed by #12


🌐 Add Japanese translation for Benchmarks

This PR translates the benchmarks.md to Japanese.
According to the issue: #1572
Thanks!!

@tokusumi
Thanks for the review!! 👍
I fixed everything. So, check my fix please.

@Attsun1031
I appreciate for your review and suggestion. 😀
I applied your suggestion. Could you check ?

Awesome, thanks @komtaki ! :rocket: :coffee:
And thanks @Attsun1031 and @tokusumi for the reviews :cake: :bow:


[HANDS-ON BUG] Unit 6

Hello everybody!
I used Google Colab from my personal space as recommanded.
I did not change a thing from the script as expected.
I have a problem when I tried pushing the agent at the end of the Unit 6 hands-on:
from huggingface_sb3 import package_to_hub

package_to_hub(
    model=model,
    model_name=f"a2c-{env_id}",
    model_architecture="A2C",
    env_id=env_id,
    eval_env=eval_env,
    repo_id=f"ThomasSimonini/a2c-{env_id}", # Change the username
    commit_message="Initial commit",
)

I've got a whole error message:
This function will save, evaluate, generate a video of your agent,
create a model card and push everything to the hub. It might take up to 1min.
This is a work in progress: if you encounter a bug, please open an issue.
Saving video to /tmp/tmpotrksyum/-step-0-to-step-1000.mp4
Moviepy - Building video /tmp/tmpotrksyum/-step-0-to-step-1000.mp4.
Moviepy - Writing video /tmp/tmpotrksyum/-step-0-to-step-1000.mp4

Moviepy - Done !
Moviepy - video ready /tmp/tmpotrksyum/-step-0-to-step-1000.mp4
ℹ Pushing repo ThomasSimonini/a2c-PandaReachDense-v3 to the Hugging
Face Hub

a2c-PandaReachDense-v3.zip: 100%
110k/110k [00:01<00:00, 110kB/s]
vec_normalize.pkl: 100%
2.82k/2.82k [00:01<00:00, 3.28kB/s]
Upload 2 LFS files: 100%
2/2 [00:02<00:00, 2.06s/it]

---------------------------------------------------------------------------

HTTPError                                 Traceback (most recent call last)

[/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_errors.py](https://localhost:8080/#) in hf_raise_for_status(response, endpoint_name)
    269     try:
--> 270         response.raise_for_status()
    271     except HTTPError as e:

9 frames

HTTPError: 403 Client Error: Forbidden for url: https://huggingface.co/api/models/ThomasSimonini/a2c-PandaReachDense-v3/commit/main

The above exception was the direct cause of the following exception:

HfHubHTTPError                            Traceback (most recent call last)

[/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_errors.py](https://localhost:8080/#) in hf_raise_for_status(response, endpoint_name)
    328         # Convert `HTTPError` into a `HfHubHTTPError` to display request information
    329         # as well (request id and/or server error message)
--> 330         raise HfHubHTTPError(str(e), response=response) from e
    331
    332

HfHubHTTPError: 403 Client Error: Forbidden for url: https://huggingface.co/api/models/ThomasSimonini/a2c-PandaReachDense-v3/commit/main (Request ID: Root=1-6564709f-2eff96c901f3b0ff72e7ad83;64f48c53-70ab-42d3-9142-740c290390fe)

Forbidden: pass `create_pr=1` as a query parameter to create a Pull Request

Can someone has an idea why this error message and how to solve it?
Thanks in advance for your help.

Oh My...
I'm so ashamed!!!
The worst of it: I've seen it at the very end of the Unit, but not here.
Thanks you very much nicosanc. I think I'll have to change my glasses now!


Clarify how optional strings are defined

In particular, I'm curious about the details of https://github.com/dandi/dandiarchive/pull/409/files/0bc55c4ca16654ed550be315f81239b1edded6d7#r447200060

It was explained to me. The extra ?: adds some semantic value by making it clear that parameters are not required.