Installation failed

I followed the installation guide. However, I cannot make DemocracyOS to work.
Linux Kernel:
Linux 3c3666c55097 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Distrib:
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.2 LTS
Release:	14.04
Codename:	trusty

MongoDB:  v2.4.9
Node: v0.10.38
Npm: 1.4.28
OpenSSL: OpenSSL 1.0.1f 6 Jan 2014
Result of make after loading democracyOS on port 80 in the browser
Installing dependencies...
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>repo should probably be repository.
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN cannot run in wd<EMAIL_ADDRESS>node ./bin/dos-install && node ./bin/dos-config && node ./bin/dos-build (wd=/usr/src/democracyos/app)
Starting application...
  democracyos:config Load local configuration from /usr/src/democracyos/app/config/development.json +0ms
  democracyos:config Merge environment set configuration variables +5ms
  democracyos:config Loaded config object for env development with sha "6324e10e8c1bdd9bc9d131b9caad283f" +3ms
  democracyos:config Invalid config key "mongoUsersUrl" +290ms
  democracyos:db Using mongodb hosts: localhost:27017 +34ms
  democracyos:db Using mongodb URI: mongodb://localhost:27017/DemocracyOS-dev +2ms
  democracyos:db Connecting to MongoDB database DemocracyOS-dev +4ms
  democracyos:root Application started on port 80 +2s
  democracyos:db Connected to MongoDB on URI: mongodb://localhost:27017/DemocracyOS-dev +17ms
  democracyos:db Connection to MongoDB is now OPEN on URI: mongodb://localhost:27017/DemocracyOS-dev +9ms
  democracyos:jwt HTTP header x-access-token has no token. Moving on... +8s
  democracyos:build Start assets compilation +506ms
  democracyos:build Start assets compilation +37ms
  outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
  outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
  outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
  outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
  democracyos:build Found error building scripts +45s
  democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +9ms
Error: failed to read<EMAIL_ADDRESS>file "index.js"
    at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21
    at fs.js:208:20
    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)
    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)
    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)
    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)
    at Object.oncomplete (fs.js:108:15)
  democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +85ms
  democracyos:build Found error building scripts +13ms
  democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +2ms
Error: failed to read<EMAIL_ADDRESS>file "index.js"
    at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21
    at fs.js:208:20
    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)
    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)
    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)
    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)
    at Object.oncomplete (fs.js:108:15)
  democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +11ms
  democracyos:build Files copied successfully +27ms
  democracyos:build Files copied successfully +1ms

Possibly need to update to a later version of Ubuntu but I am not sure ?
Try an :-
DEBUG=*
make packages

And you should have more debug info available.
On 19 April 2015 at 10:41, Guillem CANAL<EMAIL_ADDRESS>wrote:

I followed the installation guide. However, I cannot make DemocracyOS to
work.
Linux Kernel:
Linux 3c3666c55097 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Distrib:
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.2 LTS
Release:    14.04
Codename:   trusty
MongoDB: v2.4.9
Node: v0.10.38
Npm: 1.4.28
OpenSSL: OpenSSL 1.0.1f 6 Jan 2014
Result of make after load democracyOS on port 80
Installing dependencies...
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>repo should probably be repository.
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN cannot run in wd<EMAIL_ADDRESS>node ./bin/dos-install && node ./bin/dos-config && node ./bin/dos-build (wd=/usr/src/democracyos/app)
Starting application...
democracyos:config Load local configuration from /usr/src/democracyos/app/config/development.json +0ms
democracyos:config Merge environment set configuration variables +5ms
democracyos:config Loaded config object for env development with sha "6324e10e8c1bdd9bc9d131b9caad283f" +3ms
democracyos:config Invalid config key "mongoUsersUrl" +290ms
democracyos:db Using mongodb hosts: localhost:27017 +34ms
democracyos:db Using mongodb URI: mongodb://localhost:27017/DemocracyOS-dev +2ms
democracyos:db Connecting to MongoDB database DemocracyOS-dev +4ms
democracyos:root Application started on port 80 +2s
democracyos:db Connected to MongoDB on URI: mongodb://localhost:27017/DemocracyOS-dev +17ms
democracyos:db Connection to MongoDB is now OPEN on URI: mongodb://localhost:27017/DemocracyOS-dev +9ms
democracyos:jwt HTTP header x-access-token has no token. Moving on... +8s
democracyos:build Start assets compilation +506ms
democracyos:build Start assets compilation +37ms
outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
democracyos:build Found error building scripts +45s
democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +9msError: failed to read<EMAIL_ADDRESS>file "index.js"
at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21
at fs.js:208:20
at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)
at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)
at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)
at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)
at Object.oncomplete (fs.js:108:15)
democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +85ms  democracyos:build Found error building scripts +13ms  democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +2ms
Error: failed to read<EMAIL_ADDRESS>file "index.js"    at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21    at fs.js:208:20    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)    at Object.oncomplete (fs.js:108:15)  democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +11ms
democracyos:build Files copied successfully +27ms
democracyos:build Files copied successfully +1ms
—
Reply to this email directly or view it on GitHub
https://github.com/DemocracyOS/app/issues/763.

What repo and branch are you using ?
On 19 April 2015 at 16:08, Aaron Gray<EMAIL_ADDRESS>wrote:

Possibly need to update to a later version of Ubuntu but I am not sure ?
Try an :-
DEBUG=*
make packages

And you should have more debug info available.
On 19 April 2015 at 10:41, Guillem CANAL<EMAIL_ADDRESS>wrote:

I followed the installation guide. However, I cannot make DemocracyOS to
work.
Linux Kernel:
Linux 3c3666c55097 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Distrib:
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.2 LTS
Release:    14.04
Codename:   trusty
MongoDB: v2.4.9
Node: v0.10.38
Npm: 1.4.28
OpenSSL: OpenSSL 1.0.1f 6 Jan 2014
Result of make after load democracyOS on port 80
Installing dependencies...
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>repo should probably be repository.
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN cannot run in wd<EMAIL_ADDRESS>node ./bin/dos-install && node ./bin/dos-config && node ./bin/dos-build (wd=/usr/src/democracyos/app)
Starting application...
democracyos:config Load local configuration from /usr/src/democracyos/app/config/development.json +0ms
democracyos:config Merge environment set configuration variables +5ms
democracyos:config Loaded config object for env development with sha "6324e10e8c1bdd9bc9d131b9caad283f" +3ms
democracyos:config Invalid config key "mongoUsersUrl" +290ms
democracyos:db Using mongodb hosts: localhost:27017 +34ms
democracyos:db Using mongodb URI: mongodb://localhost:27017/DemocracyOS-dev +2ms
democracyos:db Connecting to MongoDB database DemocracyOS-dev +4ms
democracyos:root Application started on port 80 +2s
democracyos:db Connected to MongoDB on URI: mongodb://localhost:27017/DemocracyOS-dev +17ms
democracyos:db Connection to MongoDB is now OPEN on URI: mongodb://localhost:27017/DemocracyOS-dev +9ms
democracyos:jwt HTTP header x-access-token has no token. Moving on... +8s
democracyos:build Start assets compilation +506ms
democracyos:build Start assets compilation +37ms
outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
democracyos:build Found error building scripts +45s
democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +9msError: failed to read<EMAIL_ADDRESS>file "index.js"
at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21
at fs.js:208:20
at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)
at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)
at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)
at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)
at Object.oncomplete (fs.js:108:15)
democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +85ms  democracyos:build Found error building scripts +13ms  democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +2ms
Error: failed to read<EMAIL_ADDRESS>file "index.js"    at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21    at fs.js:208:20    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)    at Object.oncomplete (fs.js:108:15)  democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +11ms
democracyos:build Files copied successfully +27ms
democracyos:build Files copied successfully +1ms
—
Reply to this email directly or view it on GitHub
https://github.com/DemocracyOS/app/issues/763.

Any results ? If you paste the results of the 'make packages' with the
DEBUG=* I can determine what is wrong and if its an issue I flagged up.
On 19 April 2015 at 16:08, Aaron Gray<EMAIL_ADDRESS>wrote:

What repo and branch are you using ?
On 19 April 2015 at 16:08, Aaron Gray<EMAIL_ADDRESS>wrote:

Possibly need to update to a later version of Ubuntu but I am not sure ?
Try an :-
DEBUG=*
make packages

And you should have more debug info available.
On 19 April 2015 at 10:41, Guillem CANAL<EMAIL_ADDRESS>wrote:

I followed the installation guide. However, I cannot make DemocracyOS to
work.
Linux Kernel:
Linux 3c3666c55097 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Distrib:
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.2 LTS
Release:    14.04
Codename:   trusty
MongoDB: v2.4.9
Node: v0.10.38
Npm: 1.4.28
OpenSSL: OpenSSL 1.0.1f 6 Jan 2014
Result of make after load democracyOS on port 80
Installing dependencies...
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN package.json<EMAIL_ADDRESS>repo should probably be repository.
npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN cannot run in wd<EMAIL_ADDRESS>node ./bin/dos-install && node ./bin/dos-config && node ./bin/dos-build (wd=/usr/src/democracyos/app)
Starting application...
democracyos:config Load local configuration from /usr/src/democracyos/app/config/development.json +0ms
democracyos:config Merge environment set configuration variables +5ms
democracyos:config Loaded config object for env development with sha "6324e10e8c1bdd9bc9d131b9caad283f" +3ms
democracyos:config Invalid config key "mongoUsersUrl" +290ms
democracyos:db Using mongodb hosts: localhost:27017 +34ms
democracyos:db Using mongodb URI: mongodb://localhost:27017/DemocracyOS-dev +2ms
democracyos:db Connecting to MongoDB database DemocracyOS-dev +4ms
democracyos:root Application started on port 80 +2s
democracyos:db Connected to MongoDB on URI: mongodb://localhost:27017/DemocracyOS-dev +17ms
democracyos:db Connection to MongoDB is now OPEN on URI: mongodb://localhost:27017/DemocracyOS-dev +9ms
democracyos:jwt HTTP header x-access-token has no token. Moving on... +8s
democracyos:build Start assets compilation +506ms
democracyos:build Start assets compilation +37ms
outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
outdated name of a dependency : please update: "component/get-document" -> "webmodules/get-document"
outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
outdated name of a dependency : please update: "tj/debug" -> "visionmedia/debug"
democracyos:build Found error building scripts +45s
democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +9msError: failed to read<EMAIL_ADDRESS>file "index.js"
at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21
at fs.js:208:20
at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)
at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)
at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)
at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)
at Object.oncomplete (fs.js:108:15)
democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +85ms  democracyos:build Found error building scripts +13ms  democracyos:build Found error compiling assets: Error: failed to read<EMAIL_ADDRESS>file "index.js" +2ms
Error: failed to read<EMAIL_ADDRESS>file "index.js"    at /usr/src/democracyos/app/node_modules/component-builder/node_modules/component-manifest/build/index.js:440:21    at fs.js:208:20    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:143:5)    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-resolver/node_modules/graceful-fs/graceful-fs.js:63:22)    at OpenReq.Req.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:143:5)    at OpenReq.done (/usr/src/democracyos/app/node_modules/component-builder/node_modules/graceful-fs/graceful-fs.js:63:22)    at Object.oncomplete (fs.js:108:15)  democracyos:build Found error building styles: Error: failed to read<EMAIL_ADDRESS>file "loading-lock.css" +11ms
democracyos:build Files copied successfully +27ms
democracyos:build Files copied successfully +1ms
—
Reply to this email directly or view it on GitHub
https://github.com/DemocracyOS/app/issues/763.

Hey, sorry for the delay.
I'm using the master branch, here is the result of  make packages with DEBUG="*"
Since the stdout is quite large, I pasted it on Pastebin: http://pastebin.com/JpA8LV9n

Oh. I guess I understand what's going on here, I needed to use --unsafe-perm since I'm installing democracy-os with the root user, in fact, the project is running inside a docker container.
Still, I had errors:
npm ERR<EMAIL_ADDRESS>postinstall: `node ./bin/dos-install && node ./bin/dos-config && node ./bin/dos-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is most likely a problem with the DemocracyOS package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ./bin/dos-install && node ./bin/dos-config && node ./bin/dos-build
npm ERR! You can get their info via:
npm ERR!     npm owner ls DemocracyOS
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.13.0-24-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "--unsafe-perm"
npm ERR! cwd /usr/src/democracyos/app
npm ERR! node -v v0.10.38
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /usr/src/democracyos/app/npm-debug.log
npm ERR! not ok code 0

Here is the content of /usr/src/democracyos/app/npm-debug.log: http://sprunge.us/OFFf

Executing npm owner ls DemocracyOS gave me:
npm ERR! owner ls Couldn't get owner data DemocracyOS
npm ERR! 404 404 Not Found: DemocracyOS
npm ERR! 404
npm ERR! 404 'DemocracyOS' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, or http url, or git url.

npm ERR! System Linux 3.13.0-24-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "owner" "ls" "DemocracyOS"
npm ERR! cwd /usr/src/democracyos/app
npm ERR! node -v v0.10.38
npm ERR! npm -v 1.4.28
npm ERR! code E404
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /usr/src/democracyos/app/npm-debug.log
npm ERR! not ok code 0

Well, I narrowed down the issue to dos-build, The log is available here: http://sprunge.us/UQPH
I removed my password from the log file since it was available in plaintext ^^

rerunning ./bin/dos-build gave me a more reliable error:
  component-resolver:locals resolved local "comments-replies-edit" +1ms
  component-resolver finished resolving locals +0ms
  democracyos:build Found error resolving dependencies tree Error: trouble finding dependency<EMAIL_ADDRESS>+1ms
[Error: trouble finding dependency<EMAIL_ADDRESS>  remotes:github:api used 0 +6ms

I am not sure if this is the same problem that I was experiencing with
componentjs's component-install its seemed to have timing problems either a
race condition or retry problems. I found that if I worked at a time when
the internet was very quiet where the US and UK were I am were asleep I
could get a good install. I still have not really had the time to isolate
this problem as its in the componentjs installer code or related sub
modules. I found I had it working again so was not able to fix it. BUT I am
not sure if that is your problem.
https://github.com/DemocracyOS/app/issues/725 I also did PR's for
componentjs/component that are still open.
One thing that is needed if you have not done it that helps this problem is
setting your GITHUB_USERNAME and GITHUB_PASSWORD and/or setting up .netrc :-
https://github.com/componentjs/guide/blob/master/component/getting-started.md#configuring-github-access
I did find an oddity in the http://sprunge.us/UQPH dump file in
the component~emitter module name notice the tilde I am not sure where
that's loaded in it should be component-emitter.
You have installed :-
On Ubuntu 14/13/lower, install the package node-legacy for NodeJS.

Also if it is an internet problem a straight :-
component install --timeout 960000

can help some of the timing problems.
On 21 April 2015 at 07:21, Guillem CANAL<EMAIL_ADDRESS>wrote:

rerunning ./bin/dos-build gave me a more reliable error:
component-resolver:locals resolved local "comments-replies-edit" +1ms
component-resolver finished resolving locals +0ms
democracyos:build Found error resolving dependencies tree Error: trouble finding dependency<EMAIL_ADDRESS>+1ms
[Error: trouble finding dependency<EMAIL_ADDRESS>remotes:github:api used 0 +6ms
—
Reply to this email directly or view it on GitHub
https://github.com/DemocracyOS/app/issues/763#issuecomment-94652569.

Hey, I fact, the problem was simple: node shouldn't be run as the root user.
Creating a specific user for nodejs fixed the problem.
Building a Dockerfile with Github credentials may be the last remaining issue here since CommonJS require authentication. So the idea is to build source first and then make an image out of it.
Thanks again for your help ;)

Any clarification we could add to the wiki so it doesn't happen to someone else?

@mjlescano Except for "Node must not be run as root", not really ;)

This is one technique I am planning on using, but have not tested fully
yet :-
http://www.aarongray.org/Node.js/Node-instillation.txt

Aaron
On 25 April 2015 at 16:15, Guillem CANAL<EMAIL_ADDRESS>wrote:

@mjlescano https://github.com/mjlescano Except for "Node must not be
run as root", not really ;)
—
Reply to this email directly or view it on GitHub
https://github.com/DemocracyOS/app/issues/763#issuecomment-96220726.


report error by toolbar's buttons when using click-preview on NImage component(NImage组件下预览模式工具栏使用报错)

TuSimple/naive-ui version (版本)
2.34.2
Vue version (Vue 版本)
3.2.45
Browser and its version (浏览器及其版本)
Edge(108.0.1462.42)
System and its version (系统及其版本)
Windows(22621.674)
Node version (Node 版本)
v16.16.0
Reappearance link (重现链接)
https://codesandbox.io/s/confident-mestorf-1ku368?file=/src/App.vue
Reappearance steps (重现步骤)

click the image for open preview view
click the button on the toolbar, like enlarge or shrink

Expected results (期望的结果)
they're working on their way
Actual results (实际的结果)
it report error by naiveui when it run with browser
// on edge console
Uncaught TypeError: Cannot read properties of undefined (reading 'style')
    at derivePreviewStyle (ImagePreview.js:262:152)
    at zoomIn (ImagePreview.js:236:17)
    at callWithErrorHandling (runtime-core.esm-bundler.js:157:22)
    at callWithAsyncErrorHandling (runtime-core.esm-bundler.js:166:21)
    at HTMLElement.invoker (runtime-dom.esm-bundler.js:345:9)

Remarks (补充说明)
i check the source file
"naive-ui/src/image/src/ImagePreview.tsx" use a lot of code like "imageContext?.previewedImgPropsRef"
and "naive-ui/src/image/src/Image.tsx" provide "imageContextKey" used "toRef(props, 'previewedImgProps')"
but previewedImgProps is undefined if default
so i can see the output like "imageContext: {previewedImgPropsRef: Ref}"

i think just need set a default value like {} for  previewedImgProps

i see, thank u


AttributeError: module 'tensorflow' has no attribute 'python'

At master (526df2a), on Linux, Python 3.8.7, installed packages:
absl-py==0.11.0
astunparse==1.6.3
cachetools==4.2.0
certifi==2020.12.5
chardet==3.0.4
click==7.1.2
Flask==1.1.2
flatbuffers==1.12
gast==0.3.3
google-auth==1.24.0
google-auth-oauthlib==0.4.2
google-pasta==0.2.0
-e git+https://github.com/cool-RR/grid_royale@526df2a01fa8b0ba39423a6977929539c451673a#egg=grid_royale
grpcio==1.32.0
h5py==2.10.0
idna==2.10
immutabledict==1.2.0
itsdangerous==1.1.0
Jinja2==2.11.2
Keras==2.4.3
Keras-Preprocessing==1.1.2
Markdown==3.3.3
MarkupSafe==1.1.1
more-itertools==8.6.0
numpy==1.19.5
oauthlib==3.1.0
opt-einsum==3.3.0
protobuf==3.14.0
pyasn1==0.4.8
pyasn1-modules==0.2.8
PyYAML==5.4.1
requests==2.24.0
requests-oauthlib==1.3.0
rsa==4.7
scipy==1.6.0
six==1.15.0
tensorboard==2.4.1
tensorboard-plugin-wit==1.8.0
tensorflow==2.4.1
tensorflow-estimator==2.4.0
termcolor==1.1.0
typing-extensions==<IP_ADDRESS>
urllib3==1.25.11
Werkzeug==1.0.1
wrapt==1.12.1

Starting server emits uncaught error:
(venv) zhuyifei1999@zhuyifei1999-ThinkPad-T480 /tmp/grid_royale $ grid_royale play
Traceback (most recent call last):
  File "/tmp/grid_royale/venv/bin/grid_royale", line 33, in <module>
    sys.exit(load_entry_point('grid-royale', 'console_scripts', 'grid_royale')())
  File "/tmp/grid_royale/venv/bin/grid_royale", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.8/importlib/metadata.py", line 77, in load
    module = import_module(match.group('module'))
  File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
  File "<frozen importlib._bootstrap>", line 991, in _find_and_load
  File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 783, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmp/grid_royale/grid_royale/__init__.py", line 9, in <module>
    from .base import *
  File "/tmp/grid_royale/grid_royale/base.py", line 74, in <module>
    from . import utils
  File "/tmp/grid_royale/grid_royale/utils/__init__.py", line 53, in <module>
    copyreg.pickle(tensorflow.python._tf_stack.StackSummary, pickle_stack_summary)
AttributeError: module 'tensorflow' has no attribute 'python'

Thanks for finding this! I believe I fixed it now.

Thanks for finding this! I believe I fixed it now.


chore: remove vendor build

Describe the change
go mod vendor build got introduced in #2 (not sure about the context as it is already have the go module build setup), based on my go build experience, there is no need to have go mod vendor, especially the vendor folder is not checked in for this project either.
How to verify it
go build would verify the PR.
Changelog text

remove go mod vendor setup

Please verify and check that the pull request fulfills the following requirements

[ ] Tests have been added or not applicable
[ ] Documentation has been added, updated, or not applicable
[x] Changes have been rebased to main
[x] Multiple commits to the same code have been squashed

relates to https://github.com/Homebrew/homebrew-core/pull/153571

Fixed by #632.


(Mobile) Edit NFT display as Simple

@mitchdoan . that tag for info purpose, like example below.

Adv is collection created by Advanced Mode/Project launchpad
Simple is collection created by Simple Mode

but the button Simple has no meaning

Remove Simple/Advanced Label in My Collection

pls proceed to remove Simple/Advanced in above scenario @langdon0003

Please review @mitchdoan

okay look fine, but can display as Edit as well


Add StatusArray and HelicityArray data structures

Can extract this information from Pythia. Integrate it into ParticleSet.
StatusArray can also have method to provide hard mask, and retrieve the hard vertex.

typing.TypedDict appears not to be in Python 3.7. Need to only import typing when doing static type checking to prevent build failures.
Use something like
from typing import TYPE_CHECKING
if TYPE_CHECKING:
    from typing import ...

See https://www.youtube.com/watch?v=UnKa_t-M_kM&t=212s


Unknown transaction input

New block not found in 30 seconds, updating state
Found next datum: d8799f1907065820000006dff9205db5e091234e60b34014714a5c9d1fef064b297e3702c04e39420519ffff1a06e8ad401b0000018a3a3957184d416c4c204861496c2074556e419f5820000006dff9205db5e091234e60b34014714a5c9d1fef064b297e3702c04e39425820000000c3eec000141b73d9f9009577b7fe43edd0a5f4eabcbaf88d959e5e562f5820000000c3eec000141b73d9f9009577b7fe43edd0a5f4eabcbaf88d959e5e562f5820000000c3eec000141b73d9f9009577b7fe43edd0a5f4eabcbaf88d959e5e562f58200000006eb7acf12b94c966d0581bbc2801815a3a34194c2e25a8acf85f7bb849582000000022dce0f741c1e9a4429896e2df6c145337dc6b428189de693c4f3e3522582000000002d0da241c8aed392c2afa621fb6b5ac5b4608e239ef7406b68f2ab354582000000002d0da241c8aed392c2afa621fb6b5ac5b4608e239ef7406b68f2ab354582000000002d0da241c8aed392c2afa621fb6b5ac5b4608e239ef7406b68f2ab354582000000002d0da241c8aed392c2afa621fb6b5ac5b4608e239ef7406b68f2ab354ffff
[
{ extraRedeemers: [ "spend:1" ] },
{
collectErrors: [
{
badTranslation: "Unknown transaction input (missing from UTxO set): 95c06c8d447206a5bdb6ed1042a99bdd6ed5617241abde834"... 17 more characters
}
]
},
{
valueNotConserved: {
consumed: {
coins: 10000000,
assets: {
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>
}
},
produced: {
coins: 12870460,
assets: {
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>,
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.6c6f72642074756e61": 1
}
}
}
},
{
badInputs: [
{
txId: "95c06c8d447206a5bdb6ed1042a99bdd6ed5617241abde8348878d171ab832a3",
index: 0
}
]
}
]
Mining...

I have had the same issue for my first hour of mining. Then I mined a block and I received the tokens. I did do a send all to my wallet to make sure there was only 1 UTXO and no collateral. Not sure if that had anything to do with it.

Having this issue for the last hour or so also, but hasn't resolved itself like @Janilom though

I was able to mint a few blocks but I came back this morning to all the same errors as you have stated. Still an issue for me as well.

yeah, besides that, sometimes there's also { feeTooSmall: { requiredFee: 237426, actualFee: 237206 } }

I'll look into the fee too small. Do you have the tx? The other error (inputs not conserved) comes from other people beating you to mainnet.

I'll look into the fee too small. Do you have the tx? The other error (inputs not conserved) comes from other people beating you to mainnet.

[
{ extraRedeemers: [ "spend:0" ] },
{
collectErrors: [
{
badTranslation: "Unknown transaction input (missing from UTxO set): 07c21cfb9653d42ea673c3a6ccb74f2ad9635442b101a2a16"... 17 more characters
}
]
},
{
valueNotConserved: {
consumed: {
coins: 3449351,
assets: {
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>00
}
},
produced: {
coins: 6319811,
assets: {
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>00,
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.6c6f72642074756e61": 1
}
}
}
},
{
badInputs: [
{
txId: "07c21cfb9653d42ea673c3a6ccb74f2ad9635442b101a2a16c42dee274861f54",
index: 0
}
]
},
{
totalCollateralMismatch: { computedFromDelta: 1104711, declaredInField: 748902 }
},
{ feeTooSmall: { requiredFee: 237426, actualFee: 237206 } }
]

I'll look into the fee too small. Do you have the tx? The other error (inputs not conserved) comes from other people beating you to mainnet.

how or why others beat me? resources?

Yes you are competing to be the the first user to output a new datum and spend the old one. If you lose the race your tx fails.

Getting the same, maybe being front-run? would also love how to see how others are beating me too

[

  { extraRedeemers: [ "spend:1" ] },

  {

    collectErrors: [

      {

        badTranslation: "Unknown transaction input (missing from UTxO set): d956cd84c86b6d52a2368d0bd9d418806e48eefa55b0f0968"... 17 more characters

      }

    ]

  },

  {

    valueNotConserved: {

      consumed: {

        coins: 6902181,

        assets: {

          "279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>

        }

      },

      produced: {

        coins: 9772641,

        assets: {

          "279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>,

          "279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.6c6f72642074756e61": 1

        }

      }

    }

  },

  {

    badInputs: [

      {

        txId: "d956cd84c86b6d52a2368d0bd9d418806e48eefa55b0f09685500b591bf2361c",

        index: 0

      }

    ]

  }

]

Same issue here you lost the race. Other miners in the future will have a more graceful error message.

I'll look into the fee too small. Do you have the tx? The other error (inputs not conserved) comes from other people beating you to mainnet.

I constantly get that (my guess it's something to do with the wallet)
[
{ extraRedeemers: [ "spend:0" ] },
{
collectErrors: [
{
badTranslation: "Unknown transaction input (missing from UTxO set): 006b172d48cb4dfe638e0324f8192a2121a5c03df7ffcbce7"... 17 more characters
}
]
},
{
valueNotConserved: {
consumed: {
coins: 3449351,
assets: {
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>00
}
},
produced: {
coins: 6263781,
assets: {
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.54554e41":<PHONE_NUMBER>00,
"279f842c33eed9054b9e3c70cd6a3b32298259c24b78b895cb41d91a.6c6f72642074756e61": 1
}
}
}
},
{
badInputs: [
{
txId: "006b172d48cb4dfe638e0324f8192a2121a5c03df7ffcbce70b7ae6038f2fd0d",
index: 0
}
]
},
{
totalCollateralMismatch: { computedFromDelta: 1104711, declaredInField: 748902 }
},
{ feeTooSmall: { requiredFee: 237426, actualFee: 237206 } }
]

How can we win more ? Local instances of cardano node?

I'll look into the fee too small. Do you have the tx? The other error (inputs not conserved) comes from other people beating you to mainnet.

another one
Found next datum: d8799f190c5f5820000003e0651d3a80a95a66380e9581da0163ffec8ffa613cf630b74bf8116aae05193fff1a02bf6e201b0000018a3d6aa1a84d416c4c204861496c2074556e419f582000000180dadf4816aba9c81f2e1d3c3852b6fe81f0ce38e17f228f2e461cedf65820000000253cd8f92d6bd1b9aae1350d1d58d7f8c8b6875025868a4d2eaf515c455820000000253cd8f92d6bd1b9aae1350d1d58d7f8c8b6875025868a4d2eaf515c455820000000253cd8f92d6bd1b9aae1350d1d58d7f8c8b6875025868a4d2eaf515c4558200000001e12f2b3520828b59ca594bb38c66c8706f9cb84b2f85ea58fc8d985fd58200000000ce5e15adb830826704e141ba76269de7a852b5b6a706f5d3e51c9b393582000000000a00e4dc59365fe4bfa11bce8b41110c56f698e046c06f148ba4f2eb0582000000000a00e4dc59365fe4bfa11bce8b41110c56f698e046c06f148ba4f2eb0582000000000a00e4dc59365fe4bfa11bce8b41110c56f698e046c06f148ba4f2eb0582000000000a00e4dc59365fe4bfa11bce8b41110c56f698e046c06f148ba4f2eb0ffff
[
{
totalCollateralMismatch: { computedFromDelta: 1104711, declaredInField: 745951 }
},
{ feeTooSmall: { requiredFee: 239393, actualFee: 239173 } }
]

hmm add a console.log to print out the tx and I can take a look at that

You can set native_uplc to false in the lucid complete() function to possibly fix this right now.

AlL HaIl tUnA
a small PR would be nice 💯

usually this happens when ada on THAT address is too low, I am transferring all ada from wallet to that address and it's fixed

usually this happens when ada on THAT address is too low, I am transferring all ada from wallet to that address and it's fixed

What do you consider "not low"? Is 40A enough? I'm getting this error even with 40A with no Collateral set.
Will not transfer big amounts of ADA to an experimental project which created the wallet and probably knows its seed :p


[SPARK-27757][BUILD] Bump Jackson to 2.9.9

What changes were proposed in this pull request?
This fixes CVE-2019-12086 on Databind: https://github.com/FasterXML/jackson/wiki/Jackson-Release-2.9.9
How was this patch tested?
Existing tests

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

You'll have to run dev/test-dependencies.sh --replace-manifest too.

MacBook-Pro-van-Fokko:spark fokkodriesprong$ dev/test-dependencies.sh --replace-manifest
Using `mvn` from path: /usr/local/bin/mvn
Using `mvn` from path: /usr/local/bin/mvn
Performing Maven install for hadoop-2.7
Using `mvn` from path: /usr/local/bin/mvn
[ERROR] Failed to execute goal on project spark-core_2.12: Could not resolve dependencies for project org.apache.spark:spark-core_2.12:jar:spark-672604: Could not find artifact com.fasterxml.jackson.module:jackson-module-scala_2.12:jar:2.9.9 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :spark-core_2.12
Using `mvn` from path: /usr/local/bin/mvn

Seems like org.apache.spark:spark-core_2.12:jar is missing for 2.9.9: https://mvnrepository.com/artifact/com.fasterxml.jackson.module/jackson-module-scala
There is a pending issue here: https://github.com/FasterXML/jackson-module-scala/issues/412

? @Fokko . Your error message is saying jackson-module-scala_2.12:jar:2.9.9 is not at Maven Central. Please see the part Could not find artifact com.fasterxml.jackson.module:jackson-module-scala_2.12:jar:2.9.9 in central (https://repo.maven.apache.org/maven2). That is the root cause of building and the reason I recommend you to check Maven Central for 2.9.9.

For now, I'll close this PR to reduce the visibility, @Fokko . Feel free to click reopen on this PR when 2.9.9 is ready on Maven Central.

@dongjoon-hyun The artifact has been published. However I don't see the reopen button, I think there is something off.

Hm yeah I can't reopen either. That's new, and we might need to investigate. Could you just open a new one in the meantime? or try pushing a new commit here?

No problem, I already created a new one under https://github.com/apache/spark/pull/24646

Oh.. It's weird. Sorry for the inconvenience, @Fokko . :(


🐛 Bug ➾ Link to flextesa-plugin documentation is a 404

🚥 Status (Internal Taqueria Team Use Only)

[x] 🔬 Investigated and Verified
[x] 🧫 Dev Implementation of Fix
[ ] 🧪 Fix Tested and Validated
[ ] 🏆 PR Merged

🆘 What happened?
"... the Flextesa documentation here" is a 404. It should point to the Flextesa plugin documentation.
This is on the https://taqueria.io/docs/config/networks/ page to be sure.
🆘 Steps to Reproduce?
Go to https://taqueria.io/docs/config/networks/ and click on the hyperlink describe above.
🐘 How impactful is this bug?
🐜 Minor annoyance
Code of Conduct

[x] I agree to follow this project's Code of Conduct

Fixed.


WasmTable.fromIPCStream erroring on fully null column of type Bool

Hi! Thanks for making this and parquet-wasm, they've been super helpful.
I'm running into an issue with serialization of fully null bool columns.
Reproduction:
import {
	vectorFromArray,
	Table as ArrowTable,
	Bool,
	tableToIPC
} from 'apache-arrow';
import { Table as WasmTable } from 'parquet-wasm/node/arrow1.js';

const table = new ArrowTable({ x: vectorFromArray([null, null], new Bool()) });
table.schema.fields[0].nullable = true;

// errors with `Error: Invalid argument error: Need at least 1 bytes for bitmap in buffers[0] in array of type Boolean, but got 0`
WasmTable.fromIPCStream(tableToIPC(table));

It doesn't seem to be a bug with apache-arrow's serialization, because it also errors with table = tableFromIPC(<bytes generated with pyarrow>).
Is this a bug on this side, or should I pull this upstream to arrow-rs?

Yeah I just tested and it works just fine with a file from pyarrow, so I expect the error is in Arrow JS
import pyarrow as pa
arr = pa.BooleanArray.from_pandas([False, False], mask=[True, True], type=pa.bool_())
table = pa.table({'a': arr})
with pa.ipc.RecordBatchStreamWriter('test.arrows', table.schema) as writer:
    writer.write_table(table)

var wasm = require('./pkg/node/arrow1')
var fs = require('fs')
var buffer = fs.readFileSync('test.arrows')
var arr = new Uint8Array(buffer)
var wasmTable = wasm.Table.fromIPCStream(arr)
wasmTable.numBatches // 1
schema = wasmTable.schema
field = schema.field(0)
field.name() // 'a'

I was using this for my pyarrow repro:
import pyarrow as pa
from io import BytesIO

bools = pa.array([None, None], type=pa.bool_())
table = pa.table({'x': bools})

sink = BytesIO()
with pa.ipc.RecordBatchStreamWriter(sink, table.schema) as writer:
    writer.write_table(table)
print(list(sink.getvalue()))

And it throws the error, though not totally sure what the major difference between our examples is.

Oh wait, realizing my mistake there, I was putting them into tableToIPC(tableFromIPC(<bytes>)) which would still hit an ArrowJS serialization bug.

Yeah the error is almost certainly in Arrow JS

Closing in favour of apache/arrow#39776, thanks for the help


Add Firebase Client-Side

We need to add Firebase Firestore to the client-side to help with both authentication and updating store info.

[x] Create Firebase provider component
[ ] Ensure App works in Safari

added


Make slice2d internal use makeOutputArray.

By not using makeOutputArray, we can't choose a texture size that is smaller than the max texture size.
This PR also updates watch demo to allow for demo URL starting with './' which currently doesn't work.

This change is

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Generate metrics for best coders

Initially implemented in #100 using just the number of surveys coded. This could be significantly more intelligent.


Dev-->Master Metrics & policies blog

https://dev-blog-nrrd.app.cloud.gov/metrics-and-policy/

@lpgoldstein @AlexandracmONRR please let me know if you have a change to review the blog since I plan to merge this today. Thanks


Alternate zones

This is an expansion of PR #9 where @ccorey added the wx_map_zones to the API client. This has been tested with the weather maps to ensure that the kml file provided can be parsed and used to group the weather stations. The README has been updated to add more documentation on the weather maps.
To use this feature, supply the wx_map_zones  that points to a url of a publicly accessible kml file. The file should consist of multiple polygons, where the name and order will dictate the displayed name and order in the weather map table. The weather maps will load this file in and group the station table.

I think having the zones baked into the config file would be a little safer, but would require a higher level of skill to make it happen (convert kml to geojson, copy geojson into config).
That being said, I'm not opposed to it for now. Seeing that only one center will be using it for now, this is a good test for one season, and we can reassess after.


Codeberg

I see that this project has been migrated onto Codeberg. Is it planned to move there or will it stay on GitHub?

Discussed with @oxalorg and @anirudhvarma12. It should stay on Github for now as we might lose out on visibility and contributions. I was just trying out Codeberg. If it gets popular enough that it will survive the move, we will reconsider it.


Phake annotation recognition and mock class method completion

Sry for taking too long here are the issues in more details:
Phake Annotation:
Phake brings the feature that you can use annotation for mocking.
E.g.
#[\Phake\Mock]
private YourClassThatYouWantToMock $class;

and you will need to put this on your setUp Method:
\Phake::initAnnotations($this);
Unfortunately the plugin does not recognize the Annotation (see screenshot):

and if I import this the IDE will call "Import is not used" as you can see here:

Mock class method auto completion:
Lets say we have the following class that we want to mock:
class foo
{
    public function getBar(): string
    {
        return 'foo';
    }
}

I use the phake mock annotation to mock this class. (Also I could do this with the Phake::mock(...)
#[\Phake\Mock]
private Foo $foo;

I really would love to see a autocompletion for methods of mocked classes as in PHPUnit.
Here I would expect the getBar() Method as suggestion.

These are just minor issues as I already said Im really grateful for this plugin and with that I wanna say thank you again ;)
PS: Regarding to Phake Annotation I can`t say if this is a Plugin problem or a problem with the package itself.

@cuberinooo Thanks for the report.

Unfortunately the plugin does not recognize the Annotation (see screenshot):

I think this is because the \Phake\Mock class doesn't actually exist. It looks like Phake just uses a placeholder as the attribute, but the class in the attribute is not part of the source code. I don't think this is something the plugin can fix, but I'll look into it. Ideally, the Phake\Mock class should just be added to the Phake source code, then this will resolve the issue (as well as the "Import is not used" issue as well).

I really would love to see a autocompletion for methods of mocked classes as in PHPUnit.
Here I would expect the getBar() Method as suggestion.

This is definitely something that can be fixed in the plugin, but I will only be able to get to it in a week or two.

I created phake/phake#318 to address the first issue


chore: don't rely on simp calling decide

I am trying to change the default behaviour in simp from { decide := true } to { decide := false }.
See

https://github.com/leanprover/lean4/pull/2166
https://github.com/leanprover/lean4/pull/2068

I think I've got all the patches to Lean4 required, except that I need to make a simultaneous change to lake in order to pass CI! (Oh what a tangled web we weave...)
This simple PR makes Lake agnostic to the default behaviour in Lean, compiling successfully either before or after the change. If it is okay to merge this, then hopefully I can proceed with the rest.

If this fails here, then we're probably missing a ¬ false = true or ¬ true = false lemma in core.

If this fails here, then we're probably missing a ¬ false = true or ¬ true = false lemma in core.

Ah, good point. I will go hunting.

If this fails here, then we're probably missing a ¬ false = true or ¬ true = false lemma in core.

Ah, good point. I will go hunting.

https://github.com/leanprover/lean4/pull/2182


Merge 5.0.0-beta-tmp to 5.0.0-beta

Make sure set the target branch to develop
What is the purpose of the change
Merge 5.0.0-beta-tmp to 5.0.0-beta
It contains RIP-29, RIP-31, RIP-32, RIP-34
Brief changelog
Merge 5.0.0-beta-tmp to 5.0.0-beta
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #4006 (3cd0ec9) into 5.0.0-beta (8fc952d) will decrease coverage by 2.36%.
The diff coverage is 24.43%.

@@               Coverage Diff                @@
##             5.0.0-beta    #4006      +/-   ##
================================================
- Coverage         45.53%   43.17%   -2.37%
- Complexity         5640     6024     +384
================================================
  Files               722      795      +73
  Lines             50616    56815    +6199
  Branches           6935     7778     +843
================================================
+ Hits              23047    24528    +1481
- Misses            24601    29103    +4502
- Partials           2968     3184     +216

Impacted Files
Coverage Δ

...g/apache/rocketmq/acl/common/AclClientRPCHook.java
80.55% <0.00%> (-2.31%)
:arrow_down:

...ache/rocketmq/broker/client/ConsumerGroupInfo.java
55.85% <0.00%> (-0.51%)
:arrow_down:

...ache/rocketmq/broker/client/net/Broker2Client.java
2.48% <0.00%> (ø)

...ketmq/broker/dledger/DLedgerRoleChangeHandler.java
0.00% <0.00%> (ø)

...e/rocketmq/broker/longpolling/ManyPullRequest.java
0.00% <0.00%> (ø)

...cketmq/broker/longpolling/NotificationRequest.java
0.00% <0.00%> (ø)

...apache/rocketmq/broker/longpolling/PopRequest.java
31.03% <ø> (-13.80%)
:arrow_down:

...tmq/broker/longpolling/PullRequestHoldService.java
16.83% <0.00%> (-3.66%)
:arrow_down:

.../rocketmq/broker/pagecache/OneMessageTransfer.java
24.00% <ø> (ø)

...etmq/broker/plugin/AbstractPluginMessageStore.java
0.00% <0.00%> (ø)

... and 312 more

Continue to review full report at Codecov.

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

Coverage decreased (-2.5%) to 47.15% when pulling 3cd0ec9a8349a3a89a135b581ed1b2e2bc10a167 on 5.0.0-beta-tmp into 8fc952d20c5b265e2d652fb556999a8e9f8df1a8 on 5.0.0-beta.


Detect WS disconnect and auto-restart

Polkadotjs WS Provider automatically reconnects on disconnect but we've noticed that Hydra RPC sometimes silently stops emitting finalised blocks without disconnect or error.


Update flow to start off ramping from EVM networks

User Story
As a user, I want to off my USDT / USDC from the following networks:
- [ ]  Ethereum
- [ ]  BSC
- [ ]  Arbitrum
- [ ]  Base
- [ ]  Avalanche
Assets

Network
USDC
USDT

Ethereum
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48
0xdAC17F958D2ee523a2206206994597C13D831ec7

BSC
0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d
0x55d398326f99059fF775485246999027B3197955

Arbitrum
0xaf88d065e77c8cC2239327C5EDb3A432268e5831
0xFd086bC7CD5C481DCC9C85ebE478A1C0b69FCbb9

Base
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
0xfde4C96c8593536E31F229EA8f37b2ADa2699bb2

Avalance
0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E
0x9702230A8Ea53601f5cD2dc00fDBc13d4dF4A8c7

Acceptance criteria

Subsidy feature takes into account liquidity on the respective network
TBC

Note

Assumption: This ticket is for both frontend and backend changes, assuming configuration changes to the current setup

@pendulum-chain/devs What all things to be considered when adding support to the above listed networks and assets?

I would again just check for routes of all the listed tokens in the squidrouter app/UI.
For example, when selecting to bridge USDC from Ethereum to Moonbeam here, the app shows a route so we know that we can use this or a similar route in vortex. We then need to check this for all tokens and if every single one of them has a route it should be possible to add all of them with little effort.

I checked them in the UI, for all five networks USDC and USDT are available, so we should be good to go.

No, we might only first merge the Asset Hub tickets so that the wallet switch code will be more clear to implement.

Hey team! Please add your planning poker estimate with Zenhub @ebma @gianfra-t @Sharqiewicz @TorstenStueber


Push Homebrew recipes straight to master and test the real commands

Instead of pointing to the docs, I've used task_test_homebrew because this is what the CI WIP is doing.

OK, address and merge.


[video_player] Clarify the use of NSAllowsArbitraryLoads

Description
As stated by Apple's documentation App Transport Security (ATS) enforces that any request must be encrypted. So HTTP would be disallowed by default.
The documentation in the README implied that the setting is required for ALL cases, not only if you want to use HTTP video URLs. Due to this unclear documentation the setting almost ended up in our app, where we do want to enforce the use of HTTPS.
I've scanned through the repo of video_player and it does not seem like that there are any HTTP requests made that would require this setting to be used by everyone. I would be happy to be proven otherwise 😊.
If I could I would remove the part about ATS completely, but it seems like that there is still issues where this is helpful to some. flutter/flutter#29502
Related Issues
flutter/flutter#54955
Checklist
Before you create this PR confirms that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[x] No, this is not a breaking change.

Should I update the CHANGELOG and the version in the pubspec?
Or is it okay, if this will be pushed with the next release?

@stuartmorgan Do you mean I should open a new PR since my comments were not integrated.

Anyone interested in modernizing this section to discuss NSExceptionDomains instead of (or at least in addition to, and preferentially) the blanket approval of HTTP is welcome to submit a PR.

@stuartmorgan is there something wrong with this PR? I am just wondering since I only pointed out grammar issues 🤔

@stuartmorgan is there something wrong with this PR?

https://github.com/flutter/plugins/pull/2886#issuecomment-839138199


WHICH LaSAFT V2 IS THE BIG MODEL OR THE LIGHT VERSION?

I noticed that in confi_path we are informed that it is the model "lasaft/pretrained/v2_light" is that correct? it would be possible to confirm, and if so, it would be possible to add the larger model, as the light version gives us inferior results compared to the big version, at least that's what I saw when I tested the V1 version of LaSAFT, thanks again!

lol disregard answer, analyzing a little, I noticed that it has both 'v2_light' and 'v2_large', to change the models just make some simple modifications to the code.


Firmware version not supported

with latest Firmware Version: 1.8.42
ttwatch --settings

here is the patch-file:
+++ ttwatch/ttwatch.c	2015-07-14 14:35:35.272866763 +0200
@@ -46,9 +46,10 @@
{ 0x00010819, MANIFEST_DEFINITION_00010819_COUNT, MANIFEST_DEFINITIONS_00010819 },
{ 0x00010822, MANIFEST_DEFINITION_00010819_COUNT, MANIFEST_DEFINITIONS_00010819 },
{ 0x00010823, MANIFEST_DEFINITION_00010819_COUNT, MANIFEST_DEFINITIONS_00010819 },

{ 0x0001082A, MANIFEST_DEFINITION_00010819_COUNT, MANIFEST_DEFINITIONS_00010819 },
};

-#define MANIFEST_DEFINITION_COUNT (3)
+#define MANIFEST_DEFINITION_COUNT (4)
/*************************************************************************************************/

Sorry for the delay, and thanks for the patch. Have you tested the settings to make sure they work with the new firmware version? I try to check a substantial number of them before updating the code, just to make sure. It's a bit time consuming, but I don't want to start randomly changing settings on people's watches because the firmware version change has changed the setting locations. I don't know how the watch would respond to invalid values being put in some locations.
I've been busy (and sick) for the last week or so, and haven't had a chance to check this.

Hello ryanbinns,
i tested with following options (read/write), without any problems.
ttwatch --settings
ttwatch --setting

btw did TomTom contact you Ryan? I asked them to do that to give support for the Linux version :-)

No, they haven't contacted me recently. I spoke to a couple of people around the beginning of the year and they provided the specifications for the ttbin file format, but I haven't got anything else from them. I don't expect to, since they are working on their own Linux software.

I have patched the source to include your fix here. I made a small change to the definition of the number of manifest definitions so it calculates it automatically.
Thanks for the feedback,
Ryan

Hi Ryan,
I add
{ 0x0001082e, MANIFEST_DEFINITION_00010819_COUNT, MANIFEST_DEFINITIONS_00010819 },
Is this a good idea?
Thank for you work - it's a great tool!
Dirk

@DirkBri, I added this as PR #52

Thanks Dan. I have integrated it.


"Cannot find type definition file" using @types type definitions

Using typescript@beta. My tsconfig.json has "types": ["jquery"] and I have installed @types/jquery under both node_modules and jspm_packages (as part of my debugging effort). When I build my project I get the following error:
"Cannot find type definition file for 'jquery'. (TS2688)"
I have tried other packages as well, but none are found.

Thanks for raising this, it is not implemented yet, I need to read up on this feature and figure out how it will work in plugin-typescript.

I use typescript@beta and works
tsconfig.json
{
    "compilerOptions": {
        "target": "es5",
        "module": "system",
        "moduleResolution": "node",
        "sourceMap": false,
        "inlineSourceMap": false,
        "experimentalDecorators": true,
        "emitDecoratorMetadata": true,
        "types": [ "core-js", "jasmine" ]
    },
    "exclude": [
        "node_modules"
    ]
}

systemjs.config.js
        typescriptOptions: {
                tsconfig: true,
                types: []
            }

@frankwallis @types/ replace typings config,no more typings.json or typings install
The Future of Declaration Files

What version of the plugin and JSPM are you using?

"systemjs": "0.19.32"
"systemjs-builder": "0.15.23"
"plugin-typescript": "5.0.1"
all installed in node_modules, not using jspm packages

Interesting. I'm on<EMAIL_ADDRESS>but that doesn't seem likely to be the issue.
Latest version of the plugin though. Any chance you could update the plugin to verify if it still works at latest?
If so, the only difference I see is that I'm using JSPM. @guybedford, do you have any insight as to why this might not work using JSPM?

@fchiumeo Are you sure it is working? I think your types: [] is overriding the first one and nullifying the load of the type declarations.
@frankwallis I took a look into this and the blocking point is that the compiler host in plugin-typescript doesn't provide the files that Typescript is looking for.
Installing to jspm_packages does not seem possible because Typescript search for things like jspm_packages/@types/package_name without the added @version_number.
When using node_modules the problem is that Typescript starts looking for http://localhost:xxx/node_modules/angular/package.json and index.d.ts in the Host files but on the first transpile call the host files only contain the main file.
I wonder if the plugin could do a scan of all files under typeRoots, similar to what Typescript does in:
https://github.com/Microsoft/TypeScript/blob/v2.0.0-beta/src/compiler/program.ts#L1058 and make those files available in the compiler host for when typescript requests them.
I would love to help out with this but my knowledge is so far a couple of hours of debugging and reading the source code so I don't know what's the best way to address it.

@dballesteros7 is right, it can't work with current implementation of plugin-typescript. At least it shouldn't....
Actually, most of the time, in tsc one does not need to provide explicit types in tsconfig. There is additional property typeRoots which has some defaults for node_modules/@types
Looks like ts expose speciall method ts.resolveTypeReferenceDirective which one can use to properly resolve @types, maybe it can be used in host's resolveModuleNames function. This method depends on other host functions like getSourceFile, fileExists, etc.
I'm not really familiar with typescript API, but that is what I found looking around.
Also I've found few existing bugs related to type resolution, e.g:
https://github.com/Microsoft/TypeScript/issues/9831
For more details see https://github.com/Microsoft/TypeScript/issues/9184

I have implemented some basic support for the types configuration option in 5.0.18. It is now used in the react and angular1 example projects. Also there is some information on the readme: https://github.com/frankwallis/plugin-typescript/blob/master/README.md#types-types-support
Let me know if you find any issues, thanks

This seems to look for the typings in the wrong place:
jspm bundle-sfx app/app build/app.js
     Building the single-file sfx bundle for app/app...

err  Error on fetch for npm:@types/react-dom<EMAIL_ADDRESS>at file:///Users/tamird/src/go/src/github.com/cockroachdb/cockroach/ui/jspm_packages/npm/@types/react-dom<EMAIL_ADDRESS>	Loading app/app.tsx
	Error: ENOENT: no such file or directory, open '/Users/tamird/src/go/src/github.com/cockroachdb/cockroach/ui/jspm_packages/npm/<EMAIL_ADDRESS>
Note that .js suffix on the directory name - this suffix is not present on disk.

I think this is caused by<EMAIL_ADDRESS>and the defaultJsExtensions behaviour. I am not able to recreate in the react example project using<EMAIL_ADDRESS>I have added a patch in 5.0.19 which I hope will fix this.

I'm having trouble with sub-dependencies of libraries that are properly referenced node_modules@types.
Is it reasonable to expect that the @types process requires that every sub-library library referenced by an @types/library-name also have an @types d.ts somewhere?


[FLINK-13759][builds] Fix builds for master branch are failed during compile stage

What is the purpose of the change
Fix builds for master branch are failed during compile stage.
Brief change log

flink-connector-elasticsearch doesn't exist at all. Fix the travis script to check flink-connector-elasticsearch6.

Verifying this change
This change is a trivial work without any test coverage.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

I have the same question. It should fail for a long time ago. Could this because of Travis caching mechanism?

The reason why the build failed was indeed a cache inconsistency and not check_shaded_artifacts_connector_elasticsearch which checked for a non-existing connector directory. @zentol could it be that check_shaded_artifacts_connector_elasticsearch does not properly fail the build if it cannot find a directory?

Based on the JIRA error the check does fail if the directory or file doesn't exist.
I would conclude that the directory did exist, but as far as I can tell there shouldn't be a way for the cache to contain old date; Flink should always be compiled in a clean directory which is then cached separately from other builds.


Check ACS location in AuthN request in all cases

Currently, EB's validation of ACS locations in the AuthnRequest seems to work like this:

If the ACSLocation in the AuthnRequest is also defined in the metadata, use it.
Otherwise (unknown ACS location):

if an SP certificate is defined in the metadata and the message is signed: check signature, if valid use ACS location from AuthnRequest, otherwise fail with user-facing error
if an SP certificate is defined in the metadata and is message is unsigned: fail with user-facing error
if no SP certificate is defined in the metadata: always fall back to default ACS location from metadata

The latter two options are confusing for the SP administrator.  It would be more consistent to always fail if the ACSLocation from the AuthnRequest doesn't match the AuthnRequest from the metadata.  So:

If the ACSLocation in the AuthnRequest is also defined in the metadata, use it.
Otherwise (unknown ACS location):

if an SP certificate is defined in the metadata and the message is signed and the signature is correct: use ACS location from AuthnRequest
Otherwise: fail with user-facing error.

if an SP certificate is defined in the metadata and is message is unsigned: fail with user-facing error

That seems wrong to me don't we only do this if "AuthnRequestsSigned" was set in the metadata or manually by an admin?
In any case this behavior is unspecified by the specs I think (though I would have to check) but I think it's a mistake to show an error to a poor user here. EB was designed to try it's best to forward the user and log that something was wrong with this request.
If the SP messes up it's ACS locations then the user will still arrive back at the SP, just at the wrong location. But the user will correctly identify the SP as the party in error.
I understand that this makes debugging harder, but that is why that bit of EB is very verbose with NOTICE logging. Ideally we'd be able to show that logging to the SP administrator too, but that would require a self-service environment.

That seems wrong to me don't we only do this if "AuthnRequestsSigned" was set in the metadata or manually by an admin?

Ah, indeed.  Henny and I were just debugging; it seems I overlooked this setting.  So whereever I wrote "certificate is defined" you should read "redirect.sign is enabled".

In any case this behavior is unspecified by the specs I think (though I would have to check) but I think it's a mistake to show an error to a poor user here. EB was designed to try it's best to forward the user and log that something was wrong with this request.
If the SP messes up it's ACS locations then the user will still arrive back at the SP, just at the wrong location. But the user will correctly identify the SP as the party in error.

That's a valid point of view, I guess.  However, I would like to argue that's it better to show an error when something obviously wrong is detected, rather than to guess what was meant.  In the first case, the issue will most probably be fixed; in the second case, it will probably lead to much more work in the future, as it is not clear what is going on.
Regardless, it should be possible to show a clear error message that tells the user this is an SP problem, and that the SP tech contact should fix this (including this contact info).

I would like to argue that's it better to show an error when something obviously wrong is detected,

But show an error to the appropriate party, which is not the user UNLESS the user is the SP administrator, but we have no way of discerning that currently.

I would like to argue that's it better to show an error when something obviously wrong is detected, rather than to guess what was meant

We're not guessing what is meant, we're simply rejecting invalid input and proceeding on valid input. Just like we don't care if extra URL parameters are added to the SSO URL. Or if the browser of the user sent a HEAD request before doing the GET. Or about a million other things that could be different about that request.

In the first case, the issue will most probably be fixed; in the second case, it will probably lead to much more work in the future, as it is not clear what is going on.

In the first case a lot of users will see errors and a tiny percentage of them will complain "something is wrong with OpenConext". Hopefully they will complain to their SP, though more likely to their IdP or the EB operator.
In any case the EB operator should be able to quickly discern what went wrong by trying to repeat the results and monitoring the logging for his experiment. Maybe something could be improved here?

Regardless, it should be possible to show a clear error message that tells the user this is an SP problem, and that the SP tech contact should fix this (including this contact info).

The message for:

if an SP certificate is defined in the metadata and is message is unsigned: fail with user-facing error

should definitely mention that the Service Provider is in error and we absolutely can't continue for security reasons. Please contact the SP support contact.

We've not seen any problems with this in past years, the current implementation is robust and it's not clear what added value removing the fallback to the default endpoint would bring, other than likely breaking many currently functioning connections.


Allow connection to PostgreSQL database with no TLS encryption

Would it be possible to change PSQLHandler.java and Config.java to allow non ecrypted connections with PostgreSQL database according to the content of file /config/obmp-psql.yml or env vars, keeping encrypted connections as default?

Yes, that should be a configuration knob. We will add the connection parameters to the configuration file.

The change also includes a docker change for ENV settings.  I'll update the docker repo with those details.


Fix the eqboolint lowering more

The issue here was that I had forgotten to add a jump in the firstTrue
case to the lower block of code; this resulted in negative operators only
runnign the first (copy) option.

@rajatd  please review

Add the test case; looks good otherwise

In reply to: 261678553 [](ancestors = 261678553)


The repo intro should incorrect link

The link should be http://revolunet.github.io/react-umd-loader instead of http://revolunet.github.io/reactumd-loader .

Nice work for this UMD idea！

thanks for reporting, fixed 👍


MNT: Port project to flint-scm

This PR is ready, though:

The FSL docker image would need git for the update stage to work
There is a doctest which is failing for reasons outside of the scope of this PR


[bug] TypeError: init() got an unexpected keyword argument 'every_n_val_epochs'

I get the following error when running 'cultionet train'.  It can be fixed by changing
(Line 83) every_n_val_epochs -> every_n_epochs
in model.py
Traceback (most recent call last):
File "/home/matthew/.pyenv/versions/cultionet2/bin/cultionet", line 8, in
sys.exit(main())
File "/home/matthew/.pyenv/versions/3.8.12/envs/cultionet2/lib/python3.8/site-packages/cultionet/scripts/cultionet.py", line 494, in main
train_model(args)
File "/home/matthew/.pyenv/versions/3.8.12/envs/cultionet2/lib/python3.8/site-packages/cultionet/scripts/cultionet.py", line 331, in train_model
cultionet.fit(
File "/home/matthew/.pyenv/versions/3.8.12/envs/cultionet2/lib/python3.8/site-packages/cultionet/model.py", line 75, in fit
cb_train_loss = ModelCheckpoint(
TypeError: init() got an unexpected keyword argument 'every_n_val_epochs'

Thanks, every_n_val_epochs came from previous PyTorch Lightning versions and I obviously didn't get all of the names updated.

This should be resolved with the latest versions.


Dynamic Voxelization on NuScenes

Describe the bug
I have changed the voxelization method in pointpillars/hv_pointpillars_fpn_sbn-all_4x8_2x_nus-3d.py from hard voxelization into dynamic voxelization.
Then an illegal memory access error was occurred.
Does the dynamic voxelization support nuscenes dataset?
Reproduction

What command or script did you run?
python ./tools/train.py ./configs/dynamic_voxelization/dv_pointpillars_fpn_sbn-all_4x8_2x_nus-3d.py

Did you make any modifications on the code or config? Did you understand what you have modified?
dv_pointpillars_fpn_sbn-all_4x8_2x_nus-3d.py was made based on pointpillars/hv_pointpillars_fpn_sbn-all_4x8_2x_nus-3d.py.
The type of model was changed from MVXFasterRCNN to DynamicMVXFasterRCNN and the type of pts_voxel_encoder was changed from HardVFE to DynamicVFE.

What dataset did you use?
NuScenes dataset.

Environment
TorchVision: 0.7.0
OpenCV: 4.4.0
MMCV: 1.1.3
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 10.1
MMDetection: 2.4.0
MMDetection3D: 0.6.0+30cec23
Error traceback
Traceback (most recent call last):
File "./tools/train.py", line 166, in
main()
File "./tools/train.py", line 162, in main
meta=meta)
File "/opt/conda/lib/python3.6/site-packages/mmdet/apis/train.py", line 143, in train_detector
runner.run(data_loaders, cfg.workflow, cfg.total_epochs)
File "/opt/conda/lib/python3.6/site-packages/mmcv/runner/epoch_based_runner.py", line 125, in run
epoch_runner(data_loaders[i], **kwargs)
File "/opt/conda/lib/python3.6/site-packages/mmcv/runner/epoch_based_runner.py", line 34, in train
**kwargs)
File "/opt/conda/lib/python3.6/site-packages/mmcv/parallel/data_parallel.py", line 67, in train_step
return self.module.train_step(*inputs[0], **kwargs[0])
File "/opt/conda/lib/python3.6/site-packages/mmdet/models/detectors/base.py", line 234, in train_step
losses = self(**data)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/base.py", line 57, in forward
return self.forward_train(**kwargs)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/mvx_two_stage.py", line 267, in forward_train
points, img=img, img_metas=img_metas)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/mvx_two_stage.py", line 202, in extract_feat
pts_feats = self.extract_pts_feat(points, img_feats, img_metas)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/mvx_faster_rcnn.py", line 52, in extract_pts_feat
voxels, coors, points, img_feats, img_metas)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/voxel_encoders/voxel_encoder.py", line 267, in forward
voxel_feats, voxel_coors = self.vfe_scatter(point_feats, coors)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, *kwargs)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/ops/voxel/scatter_points.py", line 113, in forward
points[inds], coors[inds][:, 1:])
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/ops/voxel/scatter_points.py", line 92, in forward_single
self.point_cloud_range)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/ops/voxel/scatter_points.py", line 38, in forward
coors_range)
RuntimeError: CUDA error: an illegal memory access was encountered
terminate called after throwing an instance of 'c10::Error'
what():  CUDA error: an illegal memory access was encountered
Exception raised from create_event_internal at /opt/conda/conda-bld/pytorch_1595629416375/work/c10/cuda/CUDACachingAllocator.cpp:687 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x4d (0x7f073c9ca77d in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
frame #1: c10::cuda::CUDACachingAllocator::raw_delete(void) + 0xb5d (0x7f073cc1ad9d in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10_cuda.so)
frame #2: c10::TensorImpl::release_resources() + 0x4d (0x7f073c9b6b1d in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
frame #3:  + 0x53e7fa (0x7f077624c7fa in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_python.so)

frame #22: __libc_start_main + 0xf0 (0x7f079acc0830 in /lib/x86_64-linux-gnu/libc.so.6)
Aborted (core dumped)

Have you ever tried to run the original config (hard voxelization version)? In addition, did you refer to the configs in the configs/dynamic_voxelization/? There are some changes in the voxel_layer and voxe_encoder setting. I would recommend you show your modified config.

The config is here.
I also changed the samples_per_gpu to 1 in nus-3d.py for debugging.
_base_ = [
    '../_base_/datasets/nus-3d.py', '../_base_/schedules/schedule_2x.py',
    '../_base_/default_runtime.py'
]

voxel_size = [5.0, 5.0, 6]
point_cloud_range = [-50, -50, -3, 50, 50, 3]
model = dict(
    type='DynamicMVXFasterRCNN',
    pts_voxel_layer=dict(
        max_num_points=-1,
        point_cloud_range=point_cloud_range,
        voxel_size=voxel_size,
        max_voxels=(-1, -1)),
    pts_voxel_encoder=dict(
        type='DynamicVFE',
        in_channels=4,
        feat_channels=[32, 64],
        with_distance=False,
        voxel_size=voxel_size,
        with_cluster_center=True,
        with_voxel_center=True,
        point_cloud_range=point_cloud_range,
        norm_cfg=dict(type='BN1d', eps=1e-3, momentum=0.01)),
    pts_middle_encoder=dict(
        type='PointPillarsScatter', in_channels=64, output_shape=[400, 400]),
    pts_backbone=dict(
        type='SECOND',
        in_channels=64,
        norm_cfg=dict(type='BN', eps=1e-3, momentum=0.01),
        layer_nums=[3, 5, 5],
        layer_strides=[2, 2, 2],
        out_channels=[64, 128, 128]),
    pts_neck=dict(
        type='FPN',
        norm_cfg=dict(type='BN', eps=1e-3, momentum=0.01),
        act_cfg=dict(type='ReLU'),
        in_channels=[64, 128, 128],
        out_channels=256,
        start_level=0,
        num_outs=3),
    pts_bbox_head=dict(
        type='Anchor3DHead',
        num_classes=10,
        in_channels=256,
        feat_channels=256,
        use_direction_classifier=True,
        anchor_generator=dict(
            type='AlignedAnchor3DRangeGenerator',
            ranges=[[-64, -64, -1.8, 64, 64, -1.8]],
            scales=[1, 2, 4],
            sizes=[
                [0.8660, 2.5981, 1.],  # 1.5/sqrt(3)
                [0.5774, 1.7321, 1.],  # 1/sqrt(3)
                [1., 1., 1.],
                [0.4, 0.4, 1],
            ],
            custom_values=[0, 0],
            rotations=[0, 1.57],
            reshape_out=True),
        assigner_per_size=False,
        diff_rad_by_sin=True,
        dir_offset=0.7854,  # pi/4
        dir_limit_offset=0,
        bbox_coder=dict(type='DeltaXYZWLHRBBoxCoder', code_size=9),
        loss_cls=dict(
            type='FocalLoss',
            use_sigmoid=True,
            gamma=2.0,
            alpha=0.25,
            loss_weight=1.0),
        loss_bbox=dict(type='SmoothL1Loss', beta=1.0 / 9.0, loss_weight=1.0),
        loss_dir=dict(
            type='CrossEntropyLoss', use_sigmoid=False, loss_weight=0.2)))
# model training and testing settings
train_cfg = dict(
    pts=dict(
        assigner=dict(
            type='MaxIoUAssigner',
            iou_calculator=dict(type='BboxOverlapsNearest3D'),
            pos_iou_thr=0.6,
            neg_iou_thr=0.3,
            min_pos_iou=0.3,
            ignore_iof_thr=-1),
        allowed_border=0,
        code_weight=[1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 0.2, 0.2],
        pos_weight=-1,
        debug=False))
test_cfg = dict(
    pts=dict(
        use_rotate_nms=True,
        nms_across_levels=False,
        nms_pre=1000,
        nms_thr=0.2,
        score_thr=0.05,
        min_bbox_size=0,
        max_num=500))

I investigated, but the reason for the error may be out of memory.
And I found another issue is the dynamic voxelization requires a lot of memory capacity.

I investigated, but the reason for the error may be out of memory.
And I found another issue is the dynamic voxelization requires a lot of memory capacity.

Yes, but there is also a minor bug in your config. Since you change the voxel size and point cloud range, you need to modify the output_shape in pts_middle_encode, which is very likely to lead to your CUDA error: an illegal memory access was encountered. In your case, it should be [20, 20].
BTW, I think the voxel size does not need to be so large if you just want to make it use less memory. For example, I guess [0.4, 0.4, 6] should be enough.

Traceback (most recent call last):
File "./tools/train.py", line 166, in
main()
File "./tools/train.py", line 162, in main
meta=meta)
File "/opt/conda/lib/python3.6/site-packages/mmdet/apis/train.py", line 143, in train_detector
runner.run(data_loaders, cfg.workflow, cfg.total_epochs)
File "/opt/conda/lib/python3.6/site-packages/mmcv/runner/epoch_based_runner.py", line 125, in run
epoch_runner(data_loaders[i], **kwargs)
File "/opt/conda/lib/python3.6/site-packages/mmcv/runner/epoch_based_runner.py", line 34, in train
**kwargs)
File "/opt/conda/lib/python3.6/site-packages/mmcv/parallel/data_parallel.py", line 67, in train_step
return self.module.train_step(*inputs[0], **kwargs[0])
File "/opt/conda/lib/python3.6/site-packages/mmdet/models/detectors/base.py", line 234, in train_step
losses = self(**data)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/base.py", line 57, in forward
return self.forward_train(**kwargs)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/mvx_two_stage.py", line 267, in forward_train
points, img=img, img_metas=img_metas)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/mvx_two_stage.py", line 202, in extract_feat
pts_feats = self.extract_pts_feat(points, img_feats, img_metas)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/detectors/mvx_faster_rcnn.py", line 52, in extract_pts_feat
voxels, coors, points, img_feats, img_metas)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/home/shigenaka/workspace/mmdetection3d/mmdet3d/models/voxel_encoders/voxel_encoder.py", line 262, in forward
point_feats = vfe(features)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, **kwargs)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/container.py", line 117, in forward
input = module(input)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 722, in _call_impl
result = self.forward(*input, *kwargs)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/linear.py", line 91, in forward
return F.linear(input, self.weight, self.bias)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/functional.py", line 1676, in linear
output = input.matmul(weight.t())
RuntimeError: CUDA error: CUBLAS_STATUS_NOT_INITIALIZED when calling cublasCreate(handle)
terminate called after throwing an instance of 'c10::Error'
what():  CUDA error: device-side assert triggered
Exception raised from create_event_internal at /opt/conda/conda-bld/pytorch_1595629416375/work/c10/cuda/CUDACachingAllocator.cpp:687 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x4d (0x7f7fe997b77d in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
frame #1: c10::cuda::CUDACachingAllocator::raw_delete(void) + 0xb5d (0x7f7fe9bcbd9d in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10_cuda.so)
frame #2: c10::TensorImpl::release_resources() + 0x4d (0x7f7fe9967b1d in /opt/conda/lib/python3.6/site-packages/torch/lib/libc10.so)
frame #3:  + 0x53e7fa (0x7f80231fd7fa in /opt/conda/lib/python3.6/site-packages/torch/lib/libtorch_python.so)

frame #22: __libc_start_main + 0xf0 (0x7f8047c71830 in /lib/x86_64-linux-gnu/libc.so.6)
Aborted (core dumped)

Please remember to change the range for anchors when the point cloud range is modified. In addition, the point cloud range in the dataset and model config should be modified correspondingly.

Thank you for your help.
I modified the point cloud range and anchor range.
And the problem was solved after modifying the voxel size and sweeps_num to fit in memory capacity.
When sweeps_num is set to 10,  DynamicScatter requires a lot of memory capacity because the number of points are large.

Thank you for your help. I modified the point cloud range and anchor range.
And the problem was solved after modifying the voxel size and sweeps_num to fit in memory capacity. When sweeps_num is set to 10, DynamicScatter requires a lot of memory capacity because the number of points are large.

if it's possible to attach final worked cfg here, thanks in advance.


ERROR rebuild node-sass Macbook big sur 11.1

When I tried to install node-sass with node, recursively printing out these message below and never finish installation.
2 warnings generated.
  c++ -o Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o ../src/libsass/src/ast_fwd_decl.cpp '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DLIBSASS_VERSION="3.5.5"' -I/Users/xxx/Library/Caches/node-gyp/15.4.0/include/node -I/Users/xxx/Library/Caches/node-gyp/15.4.0/src -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/openssl/config -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/openssl/openssl/include -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/uv/include -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/zlib -I/Users/xxx/Library/Caches/node-gyp/15.4.0/deps/v8/include -I../src/libsass/include  -O3 -gdwarf-2 -mmacosx-version-min=10.7 -arch arm64 -Wall -Wendif-labels -W -Wno-unused-parameter -std=c++11 -stdlib=libc++ -fno-strict-aliasing -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast_fwd_decl.o.d.raw   -c
In file included from ../src/libsass/src/ast_fwd_decl.cpp:1:
../src/libsass/src/ast.hpp:1614:25: warning: loop variable 'numerator' of type 'const
      std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>'
      [-Wrange-loop-analysis]
        for (const auto numerator : numerators)
                        ^
../src/libsass/src/ast.hpp:1614:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent
      copying
        for (const auto numerator : numerators)
             ^~~~~~~~~~~~~~~~~~~~~~
                        &
../src/libsass/src/ast.hpp:1616:25: warning: loop variable 'denominator' of type 'const
      std::__1::basic_string<char>' creates a copy from type 'const std::__1::basic_string<char>'
      [-Wrange-loop-analysis]
        for (const auto denominator : denominators)
                        ^
../src/libsass/src/ast.hpp:1616:14: note: use reference type 'const std::__1::basic_string<char> &' to prevent
      copying
        for (const auto denominator : denominators)
             ^~~~~~~~~~~~~~~~~~~~~~~~
                        &

Originally posted by @hoyangtsai in https://github.com/sass/node-sass/issues/3033#issuecomment-752877293

Is this related to an ARM Mac?

Is this related to an ARM Mac?

no, it's an intel Mac 2016

I'm closing this one because it was copied from someone else's issue and is missing the details we require in the issue template. My guess  is that it's an unsupported combination https://github.com/sass/node-sass#node-version-support-policy otherwise the build wouldn't be triggering in the first place


[W6.1f][W11-B2]Zhan Yu

Completed LO-Abstract Classes. Also updated my own SortableCommand feature to use abstract class. Realized it wasn't actually a command, but required some tweaking that didn't make it an interface either. 411ec24cc9dd43fa72827c004648602e78a92c41

@ZY-Ang
Nothing much to review here. Hence closing with minimal review


Debugger improvements

Adding step out command for the debugger
Adding hooks to run on breakpoints (separated by ;?)
print the instruction for the trace before running, its very annoying when I read jal, and I hit step-over but it doesn't work because its too late

In https://github.com/Amjad50/PSX/pull/16 command input handling is done by the backend psx-core through the tty, which is not ideal for automated access, maybe this should be converted into an API interface

@Amjad50 .


[Storage][Blob] make codegened interface BlobPrefix just a string

Currently it is a interface with just one string field.  Consider an autorest transformation to make it a string

We are not returning this type directly to users. Instead we have
{ kind: "prefix" } & Models.BlobPrefix | { kind: "blob" } & Models.BlobItem

If we changed it to single string. we have to make it a field again. Not sure how much is the added value.

I think it's fine if we don't do anything here.
@bterlson, thoughts?

Agree we can close.


Contributing.md missing in project

Expected Behavior
Actual Behavior
Steps to Reproduce the Problem

Specifications

Version:
Platform:

we've got https://github.com/google/picatrix/blob/main/docs/CodeReview.md
I might just rename it

renamed, https://github.com/google/picatrix/blob/main/docs/Contributing.md


Navigator 2.0: Refactor the imperative api to continue working in the new navigation system

Description
This is based on https://github.com/flutter/flutter/pull/30211/files
is the first part of
https://github.com/flutter/flutter/issues/45938
breaking change draft
Tests
I added the following tests:
Existing test suit should cover the most
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I signed the CLA.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[ ] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[x] Yes, this is a breaking change (Please read Handling breaking changes). Replace this with a link to the e-mail where you asked for input on this proposed change.
[ ] No, this is not a breaking change.

When you address the changes to this PR can you please push a separate commit for those changes to make it easier to review them? Thanks!

@goderbauer ready for re-review

@goderbauer this is ready for another review

@chunhtai I have just been tracking down a bug caused by this PR.
I understood from the breaking change notice. You have deprecated the isInitialRoute flag but you also removed it's functionality from PageRoute therefore not deprecating it.. but breaking it.
@override
AnimationController createAnimationController() {
	final AnimationController controller = super.createAnimationController();
	if (settings.isInitialRoute)
	  controller.value = 1.0;
	return controller;
}

It is quite vital to be able to stop that initial animation when you for instance use the following code snippet to replace the entire stack with a new root route.
Navigator.of(context).pushAndRemoveUntil(route, (_) => false);

I bring this to your attention to perhaps discuss resolution. In terms of either add the function back in until the flag itself is removed. Or, create a new breaking-change notice announcing this feature removal and adding the function in your own routes as a resolution until the Navigator 2.0 work is complete?

@slightfoot
The pushAndRemoveUntil that add the route without an animation is an unexpected behavior, because it should be a "push".
The code you posted in createAnimationController is more like a workaround to get rid of animation when it is an initial route, and that creates an unexpected behavior as you mentioned. In my opinion, this is more of a bug fixes instead of a breaking change.
Back to your question, to achieve the same result without transition, you can use replace to replace the top most route, and use remoteRoute or removeRouteBelow to remove the route below. The problem with this approach is you have to have the reference of the route in current history, you might need to keep track of them yourself which is a bit cumbersome. The use case you demonstrate here is actually the reason why we want to do the refactoring and page api.
Let me know if you have any questions or concerns.

@chunhtai as you can see the current implementation of the Navigator does not allow for an alternative to a clear and replace stack. Even if this is a bug-fix, how do we achieve this same behaviour with the new API. You can't remove the isInitialRoute breaking many apps without a replacement feature or migration guide. and the current Migration guide does not cover this scenario.

The pushAndRemoveUntil that add the route without an animation is an unexpected behavior, because it should be a "push".

@chunhtai I also use this way of resetting the stack. Actually it's very popular on Stack Overflow whenever anyone asks how to do it e.g. here.
In my opinion even though you consider this a bug, many people rely on this behavior. I've heard this solution being recommended on meetups as the "proper one".

@orestesgaolin it is ok to rely on this to reset the stack, but it should come with pushing animation.

@chunhtai yeah, it seems that the names implies the animation. However, I think it should be widely announced that such change in behavior can occur.

@orestesgaolin I can add a follow up announcement to the original breaking change, but there is current no migration guide if you want to pushAndRemoveUntil without animation.

@chunhtai I think if the problem was only the name, what about creating another method with the same functionality but without animations

@jsnoriegam That is what i would do if we don't plan to rewrite the whole routing api. However, it does not make sense to extend the imperative api if we plan to encourage people to move to a new system.


BuildDependsOn not correct

After reading the documentation on how to override depends on property, I create a sample project and added my own target to be run before the build is started. The target only prints a message to the console.
When I build the project the message is not printed.
The project is class library targeting .NET Standard 2.0
Here is the csproj file
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
  </PropertyGroup>

  <PropertyGroup>
    <BuildDependsOn>
      $(BuildDependsOn);
      MyTarget;
    </BuildDependsOn>
  </PropertyGroup>

  <Target Name="MyTarget">
    <Message Importance="High" Text="######################## COWABUNGA!!!! ###################" />
  </Target>

</Project>

Here is the output in the console:
1>------ Rebuild All started: Project: BuildTargetTest, Configuration: Debug Any CPU ------
1>BuildTargetTest -> C:\Users\c.neves\source\repos\BuildTargetTest\BuildTargetTest\bin\Debug\netstandard2.0\BuildTargetTest.dll
========== Rebuild All: 1 succeeded, 0 failed, 0 skipped ==========

The name of the project is BuildTargetTest and I am using VS 2017 Professional

@ciceroneves Sorry for the slow reploy, but thanks for your feedback; we appreciate it. To make sure that this is logged in the right place, please use the Report a Problem tool to report the issue. When you do this, your report becomes part of the work items that are listed in the in the Visual Studio Developer Community, which allows you to engage directly with the engineering team while they address and fix the problem.


Feature Request: Add Memcached, Redis , HHVM

Hi it would be awesome if you have option also to add
memcached , redis and hhvm...
Thanks

I think HHVM would be good and I would like to add that at some point.
I'm not so sure about adding memcached and redis at the moment as they require extra configuration/plugins to work.

i think redis is easily adaptable... with no configuration...
since you will use an redis cache plugin...