Tests not running locally

Commands:
node --version
npm --version
npm i
npm run init
npm run clean
npm run build
npm run test

Output:
v4.4.4
3.10.7

><EMAIL_ADDRESS>init /Users/jnicklas/Desktop/ally.js
> npm install && npm-run-all --sequential clean build build:website

><EMAIL_ADDRESS>clean /Users/jnicklas/Desktop/ally.js
> rimraf dist web reports && mkdirp dist web reports

><EMAIL_ADDRESS>build /Users/jnicklas/Desktop/ally.js
> npm-run-all --sequential build:pre --parallel build:umd build:common build:amd --sequential build:post build:archive

><EMAIL_ADDRESS>build:pre /Users/jnicklas/Desktop/ally.js
> node build/build.pre.js

><EMAIL_ADDRESS>build:amd /Users/jnicklas/Desktop/ally.js
> babel --source-maps --modules amd --out-dir dist/amd dist/src

><EMAIL_ADDRESS>build:umd /Users/jnicklas/Desktop/ally.js
> npm-run-all --sequential build:umd:bundle build:umd:min build:umd:clean

><EMAIL_ADDRESS>build:common /Users/jnicklas/Desktop/ally.js
> babel --source-maps --modules common --out-dir dist/common dist/src

><EMAIL_ADDRESS>build:umd:bundle /Users/jnicklas/Desktop/ally.js
> browserify dist/src/ally.js --debug --standalone ally --transform rollupify --transform babelify | exorcist dist/ally.js.map > dist/ally.js

dist/src/ally.js -> dist/common/ally.js
dist/src/ally.js -> dist/amd/ally.js
dist/src/element/_element.js -> dist/common/element/_element.js
dist/src/element/_element.js -> dist/amd/element/_element.js
dist/src/element/blur.js -> dist/common/element/blur.js
dist/src/element/blur.js -> dist/amd/element/blur.js
dist/src/element/disabled.js -> dist/common/element/disabled.js
dist/src/element/disabled.js -> dist/amd/element/disabled.js
dist/src/element/focus.js -> dist/common/element/focus.js
dist/src/event/_event.js -> dist/common/event/_event.js
dist/src/element/focus.js -> dist/amd/element/focus.js
dist/src/event/_event.js -> dist/amd/event/_event.js
dist/src/event/active-element.js -> dist/common/event/active-element.js
dist/src/event/active-element.js -> dist/amd/event/active-element.js
dist/src/event/shadow-focus.js -> dist/common/event/shadow-focus.js
dist/src/event/shadow-focus.js -> dist/amd/event/shadow-focus.js
dist/src/fix/_fix.js -> dist/common/fix/_fix.js
dist/src/fix/_fix.js -> dist/amd/fix/_fix.js
dist/src/fix/pointer-focus-children.js -> dist/common/fix/pointer-focus-children.js
dist/src/fix/pointer-focus-children.js -> dist/amd/fix/pointer-focus-children.js
dist/src/fix/pointer-focus-input.js -> dist/common/fix/pointer-focus-input.js
dist/src/fix/pointer-focus-input.js -> dist/amd/fix/pointer-focus-input.js
dist/src/fix/pointer-focus-parent.js -> dist/common/fix/pointer-focus-parent.js
dist/src/get/_get.js -> dist/common/get/_get.js
dist/src/fix/pointer-focus-parent.js -> dist/amd/fix/pointer-focus-parent.js
dist/src/get/active-elements.js -> dist/common/get/active-elements.js
dist/src/get/_get.js -> dist/amd/get/_get.js
dist/src/get/active-elements.js -> dist/amd/get/active-elements.js
dist/src/get/focus-redirect-target.js -> dist/common/get/focus-redirect-target.js
dist/src/get/focus-redirect-target.js -> dist/amd/get/focus-redirect-target.js
dist/src/get/focus-target.js -> dist/common/get/focus-target.js
dist/src/get/focus-target.js -> dist/amd/get/focus-target.js
dist/src/get/insignificant-branches.js -> dist/common/get/insignificant-branches.js
dist/src/get/parents.js -> dist/common/get/parents.js
Treating 'platform' as external dependency
dist/src/get/insignificant-branches.js -> dist/amd/get/insignificant-branches.js
dist/src/get/shadow-host-parents.js -> dist/common/get/shadow-host-parents.js
dist/src/get/parents.js -> dist/amd/get/parents.js
dist/src/get/shadow-host.js -> dist/common/get/shadow-host.js
dist/src/get/shadow-host-parents.js -> dist/amd/get/shadow-host-parents.js
dist/src/is/_is.js -> dist/common/is/_is.js
dist/src/get/shadow-host.js -> dist/amd/get/shadow-host.js
dist/src/is/active-element.js -> dist/common/is/active-element.js
dist/src/is/_is.js -> dist/amd/is/_is.js
Treating 'array.prototype.findindex' as external dependency
Treating 'css.escape' as external dependency
dist/src/is/active-element.js -> dist/amd/is/active-element.js
dist/src/is/disabled.js -> dist/common/is/disabled.js
dist/src/is/disabled.js -> dist/amd/is/disabled.js
dist/src/is/focus-relevant.js -> dist/common/is/focus-relevant.js
dist/src/is/focus-relevant.js -> dist/amd/is/focus-relevant.js
dist/src/is/focusable.js -> dist/common/is/focusable.js
dist/src/is/is.util.js -> dist/common/is/is.util.js
dist/src/is/focusable.js -> dist/amd/is/focusable.js
dist/src/is/native-disabled-supported.js -> dist/common/is/native-disabled-supported.js
dist/src/is/is.util.js -> dist/amd/is/is.util.js
dist/src/is/native-disabled-supported.js -> dist/amd/is/native-disabled-supported.js
dist/src/is/only-tabbable.js -> dist/common/is/only-tabbable.js
dist/src/is/shadowed.js -> dist/common/is/shadowed.js
dist/src/is/only-tabbable.js -> dist/amd/is/only-tabbable.js
dist/src/is/shadowed.js -> dist/amd/is/shadowed.js
dist/src/is/tabbable.js -> dist/common/is/tabbable.js
dist/src/is/valid-area.js -> dist/common/is/valid-area.js
dist/src/is/valid-tabindex.js -> dist/common/is/valid-tabindex.js
dist/src/is/tabbable.js -> dist/amd/is/tabbable.js
dist/src/is/valid-area.js -> dist/amd/is/valid-area.js
dist/src/is/visible.js -> dist/common/is/visible.js
dist/src/is/valid-tabindex.js -> dist/amd/is/valid-tabindex.js
dist/src/maintain/_maintain.js -> dist/common/maintain/_maintain.js
dist/src/is/visible.js -> dist/amd/is/visible.js
dist/src/maintain/_maintain.js -> dist/amd/maintain/_maintain.js
dist/src/maintain/disabled.js -> dist/common/maintain/disabled.js
dist/src/maintain/disabled.js -> dist/amd/maintain/disabled.js
dist/src/maintain/hidden.js -> dist/common/maintain/hidden.js
dist/src/maintain/tab-focus.js -> dist/common/maintain/tab-focus.js
dist/src/map/_map.js -> dist/common/map/_map.js
dist/src/map/attribute.js -> dist/common/map/attribute.js
dist/src/map/keycode.js -> dist/common/map/keycode.js
dist/src/maintain/hidden.js -> dist/amd/maintain/hidden.js
dist/src/observe/_observe.js -> dist/common/observe/_observe.js
dist/src/maintain/tab-focus.js -> dist/amd/maintain/tab-focus.js
dist/src/map/_map.js -> dist/amd/map/_map.js
dist/src/observe/interaction-type.js -> dist/common/observe/interaction-type.js
dist/src/map/attribute.js -> dist/amd/map/attribute.js
dist/src/map/keycode.js -> dist/amd/map/keycode.js
dist/src/observe/_observe.js -> dist/amd/observe/_observe.js
dist/src/observe/shadow-mutations.js -> dist/common/observe/shadow-mutations.js
dist/src/prototype/element.prototype.matches.js -> dist/common/prototype/element.prototype.matches.js
dist/src/prototype/window.customevent.js -> dist/common/prototype/window.customevent.js
dist/src/observe/interaction-type.js -> dist/amd/observe/interaction-type.js
dist/src/prototype/window.requestanimationframe.js -> dist/common/prototype/window.requestanimationframe.js
dist/src/query/_query.js -> dist/common/query/_query.js
dist/src/query/first-tabbable.js -> dist/common/query/first-tabbable.js
dist/src/observe/shadow-mutations.js -> dist/amd/observe/shadow-mutations.js
dist/src/query/focusable.js -> dist/common/query/focusable.js
dist/src/prototype/element.prototype.matches.js -> dist/amd/prototype/element.prototype.matches.js
dist/src/query/focusable.quick.js -> dist/common/query/focusable.quick.js
dist/src/prototype/window.customevent.js -> dist/amd/prototype/window.customevent.js
dist/src/prototype/window.requestanimationframe.js -> dist/amd/prototype/window.requestanimationframe.js
dist/src/query/_query.js -> dist/amd/query/_query.js
dist/src/query/focusable.strict.js -> dist/common/query/focusable.strict.js
dist/src/query/first-tabbable.js -> dist/amd/query/first-tabbable.js
dist/src/query/shadow-hosts.js -> dist/common/query/shadow-hosts.js
dist/src/query/tabbable.js -> dist/common/query/tabbable.js
dist/src/query/focusable.js -> dist/amd/query/focusable.js
dist/src/query/focusable.quick.js -> dist/amd/query/focusable.quick.js
dist/src/query/tabsequence.js -> dist/common/query/tabsequence.js
dist/src/query/focusable.strict.js -> dist/amd/query/focusable.strict.js
dist/src/query/shadow-hosts.js -> dist/amd/query/shadow-hosts.js
dist/src/query/tabsequence.sort-area.js -> dist/common/query/tabsequence.sort-area.js
dist/src/query/tabbable.js -> dist/amd/query/tabbable.js
dist/src/query/tabsequence.js -> dist/amd/query/tabsequence.js
dist/src/query/tabsequence.sort-shadowed.js -> dist/common/query/tabsequence.sort-shadowed.js
dist/src/query/tabsequence.sort-area.js -> dist/amd/query/tabsequence.sort-area.js
dist/src/query/tabsequence.sort-tabindex.js -> dist/common/query/tabsequence.sort-tabindex.js
dist/src/selector/focusable.js -> dist/common/selector/focusable.js
dist/src/style/_style.js -> dist/common/style/_style.js
dist/src/style/focus-source.js -> dist/common/style/focus-source.js
dist/src/query/tabsequence.sort-shadowed.js -> dist/amd/query/tabsequence.sort-shadowed.js
dist/src/query/tabsequence.sort-tabindex.js -> dist/amd/query/tabsequence.sort-tabindex.js
dist/src/style/focus-within.js -> dist/common/style/focus-within.js
dist/src/selector/focusable.js -> dist/amd/selector/focusable.js
dist/src/supports/css-shadow-piercing-deep-combinator.js -> dist/common/supports/css-shadow-piercing-deep-combinator.js
dist/src/style/_style.js -> dist/amd/style/_style.js
dist/src/supports/detect-focus.js -> dist/common/supports/detect-focus.js
dist/src/style/focus-source.js -> dist/amd/style/focus-source.js
dist/src/supports/focus-area-img-tabindex.js -> dist/common/supports/focus-area-img-tabindex.js
dist/src/supports/focus-area-tabindex.js -> dist/common/supports/focus-area-tabindex.js
dist/src/supports/focus-area-without-href.js -> dist/common/supports/focus-area-without-href.js
dist/src/supports/focus-audio-without-controls.js -> dist/common/supports/focus-audio-without-controls.js
dist/src/style/focus-within.js -> dist/amd/style/focus-within.js
dist/src/supports/focus-broken-image-map.js -> dist/common/supports/focus-broken-image-map.js
dist/src/supports/css-shadow-piercing-deep-combinator.js -> dist/amd/supports/css-shadow-piercing-deep-combinator.js
dist/src/supports/focus-children-of-focusable-flexbox.js -> dist/common/supports/focus-children-of-focusable-flexbox.js
dist/src/supports/focus-fieldset-disabled.js -> dist/common/supports/focus-fieldset-disabled.js
dist/src/supports/focus-fieldset.js -> dist/common/supports/focus-fieldset.js
dist/src/supports/focus-flexbox-container.js -> dist/common/supports/focus-flexbox-container.js
dist/src/supports/detect-focus.js -> dist/amd/supports/detect-focus.js
dist/src/supports/focus-form-disabled.js -> dist/common/supports/focus-form-disabled.js
dist/src/supports/focus-area-img-tabindex.js -> dist/amd/supports/focus-area-img-tabindex.js
dist/src/supports/focus-img-ismap.js -> dist/common/supports/focus-img-ismap.js
dist/src/supports/focus-area-tabindex.js -> dist/amd/supports/focus-area-tabindex.js
dist/src/supports/focus-img-usemap-tabindex.js -> dist/common/supports/focus-img-usemap-tabindex.js
dist/src/supports/focus-area-without-href.js -> dist/amd/supports/focus-area-without-href.js
dist/src/supports/focus-audio-without-controls.js -> dist/amd/supports/focus-audio-without-controls.js
dist/src/supports/focus-in-hidden-iframe.js -> dist/common/supports/focus-in-hidden-iframe.js
dist/src/supports/focus-broken-image-map.js -> dist/amd/supports/focus-broken-image-map.js
dist/src/supports/focus-in-zero-dimension-object.js -> dist/common/supports/focus-in-zero-dimension-object.js
dist/src/supports/focus-children-of-focusable-flexbox.js -> dist/amd/supports/focus-children-of-focusable-flexbox.js
dist/src/supports/focus-invalid-tabindex.js -> dist/common/supports/focus-invalid-tabindex.js
dist/src/supports/focus-fieldset-disabled.js -> dist/amd/supports/focus-fieldset-disabled.js
dist/src/supports/focus-fieldset.js -> dist/amd/supports/focus-fieldset.js
dist/src/supports/focus-label-tabindex.js -> dist/common/supports/focus-label-tabindex.js
dist/src/supports/focus-flexbox-container.js -> dist/amd/supports/focus-flexbox-container.js
dist/src/supports/focus-object-svg-hidden.js -> dist/common/supports/focus-object-svg-hidden.js
dist/src/supports/focus-form-disabled.js -> dist/amd/supports/focus-form-disabled.js
dist/src/supports/focus-img-ismap.js -> dist/amd/supports/focus-img-ismap.js
dist/src/supports/focus-object-svg.js -> dist/common/supports/focus-object-svg.js
dist/src/supports/focus-img-usemap-tabindex.js -> dist/amd/supports/focus-img-usemap-tabindex.js
dist/src/supports/focus-object-swf.js -> dist/common/supports/focus-object-swf.js
dist/src/supports/focus-in-hidden-iframe.js -> dist/amd/supports/focus-in-hidden-iframe.js
dist/src/supports/focus-redirect-img-usemap.js -> dist/common/supports/focus-redirect-img-usemap.js
dist/src/supports/focus-in-zero-dimension-object.js -> dist/amd/supports/focus-in-zero-dimension-object.js
dist/src/supports/focus-invalid-tabindex.js -> dist/amd/supports/focus-invalid-tabindex.js
dist/src/supports/focus-redirect-legend.js -> dist/common/supports/focus-redirect-legend.js
dist/src/supports/focus-scroll-body.js -> dist/common/supports/focus-scroll-body.js
dist/src/supports/focus-label-tabindex.js -> dist/amd/supports/focus-label-tabindex.js
[BABEL] Note: The code generator has deoptimised the styling of "/Users/jnicklas/Desktop/ally.js/dist/src/ally.js" as it exceeds the max of "100KB".
dist/src/supports/focus-scroll-container-without-overflow.js -> dist/common/supports/focus-scroll-container-without-overflow.js
dist/src/supports/focus-object-svg-hidden.js -> dist/amd/supports/focus-object-svg-hidden.js
dist/src/supports/focus-scroll-container.js -> dist/common/supports/focus-scroll-container.js
dist/src/supports/focus-summary.js -> dist/common/supports/focus-summary.js
dist/src/supports/focus-object-svg.js -> dist/amd/supports/focus-object-svg.js
dist/src/supports/focus-object-swf.js -> dist/amd/supports/focus-object-swf.js
dist/src/supports/focus-svg-focusable-attribute.js -> dist/common/supports/focus-svg-focusable-attribute.js
dist/src/supports/focus-svg-tabindex-attribute.js -> dist/common/supports/focus-svg-tabindex-attribute.js
dist/src/supports/focus-redirect-img-usemap.js -> dist/amd/supports/focus-redirect-img-usemap.js
dist/src/supports/focus-redirect-legend.js -> dist/amd/supports/focus-redirect-legend.js
dist/src/supports/focus-svg.js -> dist/common/supports/focus-svg.js
dist/src/supports/focus-scroll-body.js -> dist/amd/supports/focus-scroll-body.js
dist/src/supports/focus-tabindex-trailing-characters.js -> dist/common/supports/focus-tabindex-trailing-characters.js
dist/src/supports/focus-table.js -> dist/common/supports/focus-table.js
dist/src/supports/focus-scroll-container-without-overflow.js -> dist/amd/supports/focus-scroll-container-without-overflow.js
dist/src/supports/focus-video-without-controls.js -> dist/common/supports/focus-video-without-controls.js
dist/src/supports/focus-scroll-container.js -> dist/amd/supports/focus-scroll-container.js
dist/src/supports/media/gif.invalid.js -> dist/common/supports/media/gif.invalid.js
dist/src/supports/focus-summary.js -> dist/amd/supports/focus-summary.js
dist/src/supports/media/gif.js -> dist/common/supports/media/gif.js
dist/src/supports/media/mp3.js -> dist/common/supports/media/mp3.js
dist/src/supports/focus-svg-focusable-attribute.js -> dist/amd/supports/focus-svg-focusable-attribute.js
dist/src/supports/media/mp4.js -> dist/common/supports/media/mp4.js
dist/src/supports/focus-svg-tabindex-attribute.js -> dist/amd/supports/focus-svg-tabindex-attribute.js
dist/src/supports/media/svg.js -> dist/common/supports/media/svg.js
dist/src/supports/focus-svg.js -> dist/amd/supports/focus-svg.js
dist/src/supports/focus-tabindex-trailing-characters.js -> dist/amd/supports/focus-tabindex-trailing-characters.js
dist/src/supports/focus-table.js -> dist/amd/supports/focus-table.js
dist/src/supports/supports-cache.js -> dist/common/supports/supports-cache.js
dist/src/supports/focus-video-without-controls.js -> dist/amd/supports/focus-video-without-controls.js
dist/src/supports/media/gif.invalid.js -> dist/amd/supports/media/gif.invalid.js
dist/src/supports/media/gif.js -> dist/amd/supports/media/gif.js
dist/src/supports/media/mp3.js -> dist/amd/supports/media/mp3.js
dist/src/supports/media/mp4.js -> dist/amd/supports/media/mp4.js
dist/src/supports/media/svg.js -> dist/amd/supports/media/svg.js
dist/src/supports/supports.js -> dist/common/supports/supports.js
dist/src/supports/tabsequence-area-at-img-position.js -> dist/common/supports/tabsequence-area-at-img-position.js
dist/src/supports/supports-cache.js -> dist/amd/supports/supports-cache.js
dist/src/util/compare-position.js -> dist/common/util/compare-position.js
dist/src/util/context-to-element.js -> dist/common/util/context-to-element.js
dist/src/util/decorate-context.js -> dist/common/util/decorate-context.js
dist/src/supports/supports.js -> dist/amd/supports/supports.js
dist/src/util/decorate-service.js -> dist/common/util/decorate-service.js
dist/src/supports/tabsequence-area-at-img-position.js -> dist/amd/supports/tabsequence-area-at-img-position.js
dist/src/util/get-content-document.js -> dist/common/util/get-content-document.js
dist/src/util/get-document.js -> dist/common/util/get-document.js
dist/src/util/compare-position.js -> dist/amd/util/compare-position.js
dist/src/util/context-to-element.js -> dist/amd/util/context-to-element.js
dist/src/util/get-frame-element.js -> dist/common/util/get-frame-element.js
dist/src/util/get-window.js -> dist/common/util/get-window.js
dist/src/util/decorate-context.js -> dist/amd/util/decorate-context.js
dist/src/util/image-map.js -> dist/common/util/image-map.js
dist/src/util/decorate-service.js -> dist/amd/util/decorate-service.js
dist/src/util/logger.js -> dist/common/util/logger.js
dist/src/util/get-content-document.js -> dist/amd/util/get-content-document.js
dist/src/util/get-document.js -> dist/amd/util/get-document.js
dist/src/util/merge-dom-order.js -> dist/common/util/merge-dom-order.js
dist/src/util/get-frame-element.js -> dist/amd/util/get-frame-element.js
dist/src/util/node-array.js -> dist/common/util/node-array.js
dist/src/util/get-window.js -> dist/amd/util/get-window.js
dist/src/util/platform.js -> dist/common/util/platform.js
dist/src/util/image-map.js -> dist/amd/util/image-map.js
dist/src/util/select-in-shadows.js -> dist/common/util/select-in-shadows.js
dist/src/util/logger.js -> dist/amd/util/logger.js
dist/src/util/sort-dom-order.js -> dist/common/util/sort-dom-order.js
dist/src/util/tabindex-value.js -> dist/common/util/tabindex-value.js
dist/src/util/toggle-attribute-value.js -> dist/common/util/toggle-attribute-value.js
dist/src/util/merge-dom-order.js -> dist/amd/util/merge-dom-order.js
dist/src/util/node-array.js -> dist/amd/util/node-array.js
dist/src/util/toggle-attribute.js -> dist/common/util/toggle-attribute.js
dist/src/util/platform.js -> dist/amd/util/platform.js
dist/src/util/toggle-class.js -> dist/common/util/toggle-class.js
dist/src/util/select-in-shadows.js -> dist/amd/util/select-in-shadows.js
dist/src/util/sort-dom-order.js -> dist/amd/util/sort-dom-order.js
dist/src/util/tabindex-value.js -> dist/amd/util/tabindex-value.js
dist/src/util/toggle-attribute-value.js -> dist/amd/util/toggle-attribute-value.js
dist/src/util/visible-area.js -> dist/common/util/visible-area.js
dist/src/version.js -> dist/common/version.js
dist/src/util/toggle-attribute.js -> dist/amd/util/toggle-attribute.js
dist/src/when/_when.js -> dist/common/when/_when.js
dist/src/util/toggle-class.js -> dist/amd/util/toggle-class.js
dist/src/when/focusable.js -> dist/common/when/focusable.js
dist/src/when/key.binding.js -> dist/common/when/key.binding.js
dist/src/util/visible-area.js -> dist/amd/util/visible-area.js
dist/src/version.js -> dist/amd/version.js
dist/src/when/_when.js -> dist/amd/when/_when.js
dist/src/when/key.js -> dist/common/when/key.js
dist/src/when/focusable.js -> dist/amd/when/focusable.js
dist/src/when/visible-area.js -> dist/common/when/visible-area.js
dist/src/when/key.binding.js -> dist/amd/when/key.binding.js
dist/src/when/key.js -> dist/amd/when/key.js
dist/src/when/visible-area.js -> dist/amd/when/visible-area.js

><EMAIL_ADDRESS>build:umd:min /Users/jnicklas/Desktop/ally.js
> uglifyjs dist/ally.js --in-source-map dist/ally.js.map --source-map dist/ally.min.js.map --source-map-url ally.min.js.map --preamble "/*! ${npm_package_name} - v${npm_package_version} - ${npm_package_homepage} - ${npm_package_license} License */" --mangle --compress --output dist/ally.min.js

(node) util.error is deprecated. Use console.error instead.
WARN: Side effects in initialization of unused variable variableToPreventDeadCodeElimination [dist/ally.js:107,39]
WARN: Dropping unused function argument exports [dist/ally.js:1,835]
WARN: Side effects in initialization of unused variable array_prototype_findindex [dist/ally.js:2,839]
WARN: Dropping unused function argument globals [dist/ally.js:998,11]
WARN: Dropping unused function argument exports [dist/ally.js:995,90]
WARN: Dropping unused function argument module [dist/ally.js:995,83]
WARN: Dropping unused function argument require [dist/ally.js:995,75]
WARN: Dropping unused variable module [dist/ally.js:1,342]
WARN: Dropping unused variable exports [dist/ally.js:1,349]

><EMAIL_ADDRESS>build:umd:clean /Users/jnicklas/Desktop/ally.js
> rm dist/ally.js dist/ally.js.map

><EMAIL_ADDRESS>build:post /Users/jnicklas/Desktop/ally.js
> node build/build.post.js

><EMAIL_ADDRESS>build:archive /Users/jnicklas/Desktop/ally.js
> node build/build.archive.js

402696 total bytes
802417 total bytes

><EMAIL_ADDRESS>build:website /Users/jnicklas/Desktop/ally.js
> npm-run-all --sequential build:docs --parallel build:data-tables build:legacy

><EMAIL_ADDRESS>build:docs /Users/jnicklas/Desktop/ally.js
> node build/metalsmith/metalsmith.js

Warning: Link is broken: href: "undefined", text: "
          an SVG
        ", in file: api/style/focus-within.example.html
Warning: Link is broken: href: "assets/ally-js-logo.png", text: "ally.js logo", in file: legal.html
Warning: Link is broken: href: "assets/ally-js-logo.png", text: "ally.js logo - showing the United Nations Accessibility Logo on top of the JS logo", in file: index.html
Warning: Link is broken: href: "assets/home/focusable-crop.png", text: "image of focusable data-table", in file: index.html

><EMAIL_ADDRESS>build:data-tables /Users/jnicklas/Desktop/ally.js
> npm run build:data-tables:focusable

><EMAIL_ADDRESS>build:legacy /Users/jnicklas/Desktop/ally.js
> npm-run-all --parallel build:legacy:focusable build:legacy:event-sequence build:legacy:static-copy

><EMAIL_ADDRESS>build:data-tables:focusable /Users/jnicklas/Desktop/ally.js
> babel-node build/data-tables/focusable-tables.js

><EMAIL_ADDRESS>build:legacy:event-sequence /Users/jnicklas/Desktop/ally.js
> node build/web-tests/build.event-sequence.js

><EMAIL_ADDRESS>build:legacy:focusable /Users/jnicklas/Desktop/ally.js
> node build/web-tests/build.focusable.js

><EMAIL_ADDRESS>build:legacy:static-copy /Users/jnicklas/Desktop/ally.js
> node build/web-tests/build.static-copy.js

><EMAIL_ADDRESS>clean /Users/jnicklas/Desktop/ally.js
> rimraf dist web reports && mkdirp dist web reports

><EMAIL_ADDRESS>build /Users/jnicklas/Desktop/ally.js
> npm-run-all --sequential build:pre --parallel build:umd build:common build:amd --sequential build:post build:archive

><EMAIL_ADDRESS>build:pre /Users/jnicklas/Desktop/ally.js
> node build/build.pre.js

><EMAIL_ADDRESS>build:umd /Users/jnicklas/Desktop/ally.js
> npm-run-all --sequential build:umd:bundle build:umd:min build:umd:clean

><EMAIL_ADDRESS>build:common /Users/jnicklas/Desktop/ally.js
> babel --source-maps --modules common --out-dir dist/common dist/src

><EMAIL_ADDRESS>build:amd /Users/jnicklas/Desktop/ally.js
> babel --source-maps --modules amd --out-dir dist/amd dist/src

><EMAIL_ADDRESS>build:umd:bundle /Users/jnicklas/Desktop/ally.js
> browserify dist/src/ally.js --debug --standalone ally --transform rollupify --transform babelify | exorcist dist/ally.js.map > dist/ally.js

dist/src/ally.js -> dist/amd/ally.js
dist/src/ally.js -> dist/common/ally.js
dist/src/element/_element.js -> dist/amd/element/_element.js
dist/src/element/_element.js -> dist/common/element/_element.js
dist/src/element/blur.js -> dist/amd/element/blur.js
dist/src/element/blur.js -> dist/common/element/blur.js
dist/src/element/disabled.js -> dist/amd/element/disabled.js
dist/src/element/disabled.js -> dist/common/element/disabled.js
dist/src/element/focus.js -> dist/common/element/focus.js
dist/src/element/focus.js -> dist/amd/element/focus.js
dist/src/event/_event.js -> dist/amd/event/_event.js
dist/src/event/_event.js -> dist/common/event/_event.js
dist/src/event/active-element.js -> dist/common/event/active-element.js
dist/src/event/active-element.js -> dist/amd/event/active-element.js
dist/src/event/shadow-focus.js -> dist/amd/event/shadow-focus.js
dist/src/event/shadow-focus.js -> dist/common/event/shadow-focus.js
dist/src/fix/_fix.js -> dist/amd/fix/_fix.js
dist/src/fix/_fix.js -> dist/common/fix/_fix.js
dist/src/fix/pointer-focus-children.js -> dist/amd/fix/pointer-focus-children.js
dist/src/fix/pointer-focus-children.js -> dist/common/fix/pointer-focus-children.js
dist/src/fix/pointer-focus-input.js -> dist/amd/fix/pointer-focus-input.js
dist/src/fix/pointer-focus-input.js -> dist/common/fix/pointer-focus-input.js
dist/src/fix/pointer-focus-parent.js -> dist/common/fix/pointer-focus-parent.js
dist/src/fix/pointer-focus-parent.js -> dist/amd/fix/pointer-focus-parent.js
dist/src/get/_get.js -> dist/common/get/_get.js
dist/src/get/_get.js -> dist/amd/get/_get.js
dist/src/get/active-elements.js -> dist/common/get/active-elements.js
dist/src/get/active-elements.js -> dist/amd/get/active-elements.js
dist/src/get/focus-redirect-target.js -> dist/common/get/focus-redirect-target.js
dist/src/get/focus-redirect-target.js -> dist/amd/get/focus-redirect-target.js
dist/src/get/focus-target.js -> dist/common/get/focus-target.js
dist/src/get/focus-target.js -> dist/amd/get/focus-target.js
dist/src/get/insignificant-branches.js -> dist/common/get/insignificant-branches.js
dist/src/get/insignificant-branches.js -> dist/amd/get/insignificant-branches.js
dist/src/get/parents.js -> dist/common/get/parents.js
dist/src/get/parents.js -> dist/amd/get/parents.js
dist/src/get/shadow-host-parents.js -> dist/common/get/shadow-host-parents.js
dist/src/get/shadow-host.js -> dist/common/get/shadow-host.js
dist/src/get/shadow-host-parents.js -> dist/amd/get/shadow-host-parents.js
dist/src/is/_is.js -> dist/common/is/_is.js
dist/src/get/shadow-host.js -> dist/amd/get/shadow-host.js
dist/src/is/_is.js -> dist/amd/is/_is.js
dist/src/is/active-element.js -> dist/common/is/active-element.js
dist/src/is/active-element.js -> dist/amd/is/active-element.js
dist/src/is/disabled.js -> dist/common/is/disabled.js
dist/src/is/disabled.js -> dist/amd/is/disabled.js
Treating 'platform' as external dependency
dist/src/is/focus-relevant.js -> dist/common/is/focus-relevant.js
dist/src/is/focus-relevant.js -> dist/amd/is/focus-relevant.js
Treating 'array.prototype.findindex' as external dependency
Treating 'css.escape' as external dependency
dist/src/is/focusable.js -> dist/common/is/focusable.js
dist/src/is/is.util.js -> dist/common/is/is.util.js
dist/src/is/focusable.js -> dist/amd/is/focusable.js
dist/src/is/native-disabled-supported.js -> dist/common/is/native-disabled-supported.js
dist/src/is/is.util.js -> dist/amd/is/is.util.js
dist/src/is/native-disabled-supported.js -> dist/amd/is/native-disabled-supported.js
dist/src/is/only-tabbable.js -> dist/common/is/only-tabbable.js
dist/src/is/shadowed.js -> dist/common/is/shadowed.js
dist/src/is/only-tabbable.js -> dist/amd/is/only-tabbable.js
dist/src/is/shadowed.js -> dist/amd/is/shadowed.js
dist/src/is/tabbable.js -> dist/common/is/tabbable.js
dist/src/is/valid-area.js -> dist/common/is/valid-area.js
dist/src/is/valid-tabindex.js -> dist/common/is/valid-tabindex.js
dist/src/is/tabbable.js -> dist/amd/is/tabbable.js
dist/src/is/valid-area.js -> dist/amd/is/valid-area.js
dist/src/is/visible.js -> dist/common/is/visible.js
dist/src/maintain/_maintain.js -> dist/common/maintain/_maintain.js
dist/src/is/valid-tabindex.js -> dist/amd/is/valid-tabindex.js
dist/src/is/visible.js -> dist/amd/is/visible.js
dist/src/maintain/_maintain.js -> dist/amd/maintain/_maintain.js
dist/src/maintain/disabled.js -> dist/common/maintain/disabled.js
dist/src/maintain/disabled.js -> dist/amd/maintain/disabled.js
dist/src/maintain/hidden.js -> dist/common/maintain/hidden.js
dist/src/maintain/tab-focus.js -> dist/common/maintain/tab-focus.js
dist/src/map/_map.js -> dist/common/map/_map.js
dist/src/map/attribute.js -> dist/common/map/attribute.js
dist/src/maintain/hidden.js -> dist/amd/maintain/hidden.js
dist/src/map/keycode.js -> dist/common/map/keycode.js
dist/src/observe/_observe.js -> dist/common/observe/_observe.js
dist/src/maintain/tab-focus.js -> dist/amd/maintain/tab-focus.js
dist/src/map/_map.js -> dist/amd/map/_map.js
dist/src/observe/interaction-type.js -> dist/common/observe/interaction-type.js
dist/src/map/attribute.js -> dist/amd/map/attribute.js
dist/src/map/keycode.js -> dist/amd/map/keycode.js
dist/src/observe/_observe.js -> dist/amd/observe/_observe.js
dist/src/observe/shadow-mutations.js -> dist/common/observe/shadow-mutations.js
dist/src/prototype/element.prototype.matches.js -> dist/common/prototype/element.prototype.matches.js
dist/src/prototype/window.customevent.js -> dist/common/prototype/window.customevent.js
dist/src/observe/interaction-type.js -> dist/amd/observe/interaction-type.js
dist/src/prototype/window.requestanimationframe.js -> dist/common/prototype/window.requestanimationframe.js
dist/src/query/_query.js -> dist/common/query/_query.js
dist/src/query/first-tabbable.js -> dist/common/query/first-tabbable.js
dist/src/observe/shadow-mutations.js -> dist/amd/observe/shadow-mutations.js
dist/src/query/focusable.js -> dist/common/query/focusable.js
dist/src/prototype/element.prototype.matches.js -> dist/amd/prototype/element.prototype.matches.js
dist/src/query/focusable.quick.js -> dist/common/query/focusable.quick.js
dist/src/prototype/window.customevent.js -> dist/amd/prototype/window.customevent.js
dist/src/prototype/window.requestanimationframe.js -> dist/amd/prototype/window.requestanimationframe.js
dist/src/query/_query.js -> dist/amd/query/_query.js
dist/src/query/focusable.strict.js -> dist/common/query/focusable.strict.js
dist/src/query/shadow-hosts.js -> dist/common/query/shadow-hosts.js
dist/src/query/first-tabbable.js -> dist/amd/query/first-tabbable.js
dist/src/query/tabbable.js -> dist/common/query/tabbable.js
dist/src/query/focusable.js -> dist/amd/query/focusable.js
dist/src/query/focusable.quick.js -> dist/amd/query/focusable.quick.js
dist/src/query/tabsequence.js -> dist/common/query/tabsequence.js
dist/src/query/focusable.strict.js -> dist/amd/query/focusable.strict.js
dist/src/query/shadow-hosts.js -> dist/amd/query/shadow-hosts.js
dist/src/query/tabsequence.sort-area.js -> dist/common/query/tabsequence.sort-area.js
dist/src/query/tabbable.js -> dist/amd/query/tabbable.js
dist/src/query/tabsequence.js -> dist/amd/query/tabsequence.js
dist/src/query/tabsequence.sort-shadowed.js -> dist/common/query/tabsequence.sort-shadowed.js
dist/src/query/tabsequence.sort-area.js -> dist/amd/query/tabsequence.sort-area.js
dist/src/query/tabsequence.sort-tabindex.js -> dist/common/query/tabsequence.sort-tabindex.js
dist/src/selector/focusable.js -> dist/common/selector/focusable.js
dist/src/style/_style.js -> dist/common/style/_style.js
dist/src/style/focus-source.js -> dist/common/style/focus-source.js
dist/src/query/tabsequence.sort-shadowed.js -> dist/amd/query/tabsequence.sort-shadowed.js
dist/src/query/tabsequence.sort-tabindex.js -> dist/amd/query/tabsequence.sort-tabindex.js
dist/src/style/focus-within.js -> dist/common/style/focus-within.js
dist/src/selector/focusable.js -> dist/amd/selector/focusable.js
dist/src/supports/css-shadow-piercing-deep-combinator.js -> dist/common/supports/css-shadow-piercing-deep-combinator.js
dist/src/style/_style.js -> dist/amd/style/_style.js
dist/src/supports/detect-focus.js -> dist/common/supports/detect-focus.js
dist/src/style/focus-source.js -> dist/amd/style/focus-source.js
dist/src/supports/focus-area-img-tabindex.js -> dist/common/supports/focus-area-img-tabindex.js
dist/src/supports/focus-area-tabindex.js -> dist/common/supports/focus-area-tabindex.js
dist/src/supports/focus-area-without-href.js -> dist/common/supports/focus-area-without-href.js
dist/src/style/focus-within.js -> dist/amd/style/focus-within.js
dist/src/supports/css-shadow-piercing-deep-combinator.js -> dist/amd/supports/css-shadow-piercing-deep-combinator.js
dist/src/supports/focus-audio-without-controls.js -> dist/common/supports/focus-audio-without-controls.js
dist/src/supports/focus-broken-image-map.js -> dist/common/supports/focus-broken-image-map.js
dist/src/supports/focus-children-of-focusable-flexbox.js -> dist/common/supports/focus-children-of-focusable-flexbox.js
dist/src/supports/detect-focus.js -> dist/amd/supports/detect-focus.js
dist/src/supports/focus-fieldset-disabled.js -> dist/common/supports/focus-fieldset-disabled.js
dist/src/supports/focus-area-img-tabindex.js -> dist/amd/supports/focus-area-img-tabindex.js
dist/src/supports/focus-fieldset.js -> dist/common/supports/focus-fieldset.js
dist/src/supports/focus-area-tabindex.js -> dist/amd/supports/focus-area-tabindex.js
dist/src/supports/focus-flexbox-container.js -> dist/common/supports/focus-flexbox-container.js
dist/src/supports/focus-form-disabled.js -> dist/common/supports/focus-form-disabled.js
dist/src/supports/focus-area-without-href.js -> dist/amd/supports/focus-area-without-href.js
dist/src/supports/focus-img-ismap.js -> dist/common/supports/focus-img-ismap.js
dist/src/supports/focus-img-usemap-tabindex.js -> dist/common/supports/focus-img-usemap-tabindex.js
dist/src/supports/focus-audio-without-controls.js -> dist/amd/supports/focus-audio-without-controls.js
dist/src/supports/focus-broken-image-map.js -> dist/amd/supports/focus-broken-image-map.js
dist/src/supports/focus-in-hidden-iframe.js -> dist/common/supports/focus-in-hidden-iframe.js
dist/src/supports/focus-children-of-focusable-flexbox.js -> dist/amd/supports/focus-children-of-focusable-flexbox.js
dist/src/supports/focus-in-zero-dimension-object.js -> dist/common/supports/focus-in-zero-dimension-object.js
dist/src/supports/focus-fieldset-disabled.js -> dist/amd/supports/focus-fieldset-disabled.js
dist/src/supports/focus-invalid-tabindex.js -> dist/common/supports/focus-invalid-tabindex.js
dist/src/supports/focus-fieldset.js -> dist/amd/supports/focus-fieldset.js
dist/src/supports/focus-flexbox-container.js -> dist/amd/supports/focus-flexbox-container.js
dist/src/supports/focus-form-disabled.js -> dist/amd/supports/focus-form-disabled.js
dist/src/supports/focus-label-tabindex.js -> dist/common/supports/focus-label-tabindex.js
dist/src/supports/focus-img-ismap.js -> dist/amd/supports/focus-img-ismap.js
dist/src/supports/focus-object-svg-hidden.js -> dist/common/supports/focus-object-svg-hidden.js
dist/src/supports/focus-img-usemap-tabindex.js -> dist/amd/supports/focus-img-usemap-tabindex.js
dist/src/supports/focus-in-hidden-iframe.js -> dist/amd/supports/focus-in-hidden-iframe.js
dist/src/supports/focus-object-svg.js -> dist/common/supports/focus-object-svg.js
dist/src/supports/focus-in-zero-dimension-object.js -> dist/amd/supports/focus-in-zero-dimension-object.js
dist/src/supports/focus-object-swf.js -> dist/common/supports/focus-object-swf.js
dist/src/supports/focus-invalid-tabindex.js -> dist/amd/supports/focus-invalid-tabindex.js
dist/src/supports/focus-label-tabindex.js -> dist/amd/supports/focus-label-tabindex.js
dist/src/supports/focus-redirect-img-usemap.js -> dist/common/supports/focus-redirect-img-usemap.js
dist/src/supports/focus-object-svg-hidden.js -> dist/amd/supports/focus-object-svg-hidden.js
dist/src/supports/focus-redirect-legend.js -> dist/common/supports/focus-redirect-legend.js
dist/src/supports/focus-scroll-body.js -> dist/common/supports/focus-scroll-body.js
dist/src/supports/focus-object-svg.js -> dist/amd/supports/focus-object-svg.js
dist/src/supports/focus-scroll-container-without-overflow.js -> dist/common/supports/focus-scroll-container-without-overflow.js
dist/src/supports/focus-object-swf.js -> dist/amd/supports/focus-object-swf.js
dist/src/supports/focus-scroll-container.js -> dist/common/supports/focus-scroll-container.js
dist/src/supports/focus-redirect-img-usemap.js -> dist/amd/supports/focus-redirect-img-usemap.js
dist/src/supports/focus-summary.js -> dist/common/supports/focus-summary.js
dist/src/supports/focus-redirect-legend.js -> dist/amd/supports/focus-redirect-legend.js
dist/src/supports/focus-scroll-body.js -> dist/amd/supports/focus-scroll-body.js
dist/src/supports/focus-svg-focusable-attribute.js -> dist/common/supports/focus-svg-focusable-attribute.js
dist/src/supports/focus-scroll-container-without-overflow.js -> dist/amd/supports/focus-scroll-container-without-overflow.js
dist/src/supports/focus-svg-tabindex-attribute.js -> dist/common/supports/focus-svg-tabindex-attribute.js
dist/src/supports/focus-scroll-container.js -> dist/amd/supports/focus-scroll-container.js
dist/src/supports/focus-svg.js -> dist/common/supports/focus-svg.js
dist/src/supports/focus-summary.js -> dist/amd/supports/focus-summary.js
dist/src/supports/focus-tabindex-trailing-characters.js -> dist/common/supports/focus-tabindex-trailing-characters.js
dist/src/supports/focus-table.js -> dist/common/supports/focus-table.js
dist/src/supports/focus-svg-focusable-attribute.js -> dist/amd/supports/focus-svg-focusable-attribute.js
dist/src/supports/focus-video-without-controls.js -> dist/common/supports/focus-video-without-controls.js
dist/src/supports/media/gif.invalid.js -> dist/common/supports/media/gif.invalid.js
dist/src/supports/media/gif.js -> dist/common/supports/media/gif.js
dist/src/supports/focus-svg-tabindex-attribute.js -> dist/amd/supports/focus-svg-tabindex-attribute.js
dist/src/supports/media/mp3.js -> dist/common/supports/media/mp3.js
dist/src/supports/media/mp4.js -> dist/common/supports/media/mp4.js
dist/src/supports/focus-svg.js -> dist/amd/supports/focus-svg.js
dist/src/supports/media/svg.js -> dist/common/supports/media/svg.js
dist/src/supports/focus-tabindex-trailing-characters.js -> dist/amd/supports/focus-tabindex-trailing-characters.js
dist/src/supports/focus-table.js -> dist/amd/supports/focus-table.js
dist/src/supports/supports-cache.js -> dist/common/supports/supports-cache.js
dist/src/supports/focus-video-without-controls.js -> dist/amd/supports/focus-video-without-controls.js
dist/src/supports/media/gif.invalid.js -> dist/amd/supports/media/gif.invalid.js
dist/src/supports/media/gif.js -> dist/amd/supports/media/gif.js
dist/src/supports/media/mp3.js -> dist/amd/supports/media/mp3.js
dist/src/supports/media/mp4.js -> dist/amd/supports/media/mp4.js
[BABEL] Note: The code generator has deoptimised the styling of "/Users/jnicklas/Desktop/ally.js/dist/src/ally.js" as it exceeds the max of "100KB".
dist/src/supports/media/svg.js -> dist/amd/supports/media/svg.js
dist/src/supports/supports.js -> dist/common/supports/supports.js
dist/src/supports/tabsequence-area-at-img-position.js -> dist/common/supports/tabsequence-area-at-img-position.js
dist/src/supports/supports-cache.js -> dist/amd/supports/supports-cache.js
dist/src/util/compare-position.js -> dist/common/util/compare-position.js
dist/src/util/context-to-element.js -> dist/common/util/context-to-element.js
dist/src/util/decorate-context.js -> dist/common/util/decorate-context.js
dist/src/supports/supports.js -> dist/amd/supports/supports.js
dist/src/supports/tabsequence-area-at-img-position.js -> dist/amd/supports/tabsequence-area-at-img-position.js
dist/src/util/decorate-service.js -> dist/common/util/decorate-service.js
dist/src/util/get-content-document.js -> dist/common/util/get-content-document.js
dist/src/util/compare-position.js -> dist/amd/util/compare-position.js
dist/src/util/get-document.js -> dist/common/util/get-document.js
dist/src/util/context-to-element.js -> dist/amd/util/context-to-element.js
dist/src/util/get-frame-element.js -> dist/common/util/get-frame-element.js
dist/src/util/get-window.js -> dist/common/util/get-window.js
dist/src/util/decorate-context.js -> dist/amd/util/decorate-context.js
dist/src/util/image-map.js -> dist/common/util/image-map.js
dist/src/util/decorate-service.js -> dist/amd/util/decorate-service.js
dist/src/util/logger.js -> dist/common/util/logger.js
dist/src/util/get-content-document.js -> dist/amd/util/get-content-document.js
dist/src/util/get-document.js -> dist/amd/util/get-document.js
dist/src/util/get-frame-element.js -> dist/amd/util/get-frame-element.js
dist/src/util/merge-dom-order.js -> dist/common/util/merge-dom-order.js
dist/src/util/get-window.js -> dist/amd/util/get-window.js
dist/src/util/node-array.js -> dist/common/util/node-array.js
dist/src/util/image-map.js -> dist/amd/util/image-map.js
dist/src/util/platform.js -> dist/common/util/platform.js
dist/src/util/logger.js -> dist/amd/util/logger.js
dist/src/util/select-in-shadows.js -> dist/common/util/select-in-shadows.js
dist/src/util/sort-dom-order.js -> dist/common/util/sort-dom-order.js
dist/src/util/tabindex-value.js -> dist/common/util/tabindex-value.js
dist/src/util/toggle-attribute-value.js -> dist/common/util/toggle-attribute-value.js
dist/src/util/merge-dom-order.js -> dist/amd/util/merge-dom-order.js
dist/src/util/toggle-attribute.js -> dist/common/util/toggle-attribute.js
dist/src/util/node-array.js -> dist/amd/util/node-array.js
dist/src/util/toggle-class.js -> dist/common/util/toggle-class.js
dist/src/util/platform.js -> dist/amd/util/platform.js
dist/src/util/select-in-shadows.js -> dist/amd/util/select-in-shadows.js
dist/src/util/sort-dom-order.js -> dist/amd/util/sort-dom-order.js
dist/src/util/tabindex-value.js -> dist/amd/util/tabindex-value.js
dist/src/util/visible-area.js -> dist/common/util/visible-area.js
dist/src/util/toggle-attribute-value.js -> dist/amd/util/toggle-attribute-value.js
dist/src/version.js -> dist/common/version.js
dist/src/util/toggle-attribute.js -> dist/amd/util/toggle-attribute.js
dist/src/when/_when.js -> dist/common/when/_when.js
dist/src/util/toggle-class.js -> dist/amd/util/toggle-class.js
dist/src/when/focusable.js -> dist/common/when/focusable.js
dist/src/when/key.binding.js -> dist/common/when/key.binding.js
dist/src/util/visible-area.js -> dist/amd/util/visible-area.js
dist/src/version.js -> dist/amd/version.js
dist/src/when/_when.js -> dist/amd/when/_when.js
dist/src/when/key.js -> dist/common/when/key.js
dist/src/when/focusable.js -> dist/amd/when/focusable.js
dist/src/when/visible-area.js -> dist/common/when/visible-area.js
dist/src/when/key.binding.js -> dist/amd/when/key.binding.js
dist/src/when/key.js -> dist/amd/when/key.js
dist/src/when/visible-area.js -> dist/amd/when/visible-area.js

><EMAIL_ADDRESS>build:umd:min /Users/jnicklas/Desktop/ally.js
> uglifyjs dist/ally.js --in-source-map dist/ally.js.map --source-map dist/ally.min.js.map --source-map-url ally.min.js.map --preamble "/*! ${npm_package_name} - v${npm_package_version} - ${npm_package_homepage} - ${npm_package_license} License */" --mangle --compress --output dist/ally.min.js

(node) util.error is deprecated. Use console.error instead.
WARN: Side effects in initialization of unused variable variableToPreventDeadCodeElimination [dist/ally.js:107,39]
WARN: Dropping unused function argument exports [dist/ally.js:1,835]
WARN: Side effects in initialization of unused variable array_prototype_findindex [dist/ally.js:2,839]
WARN: Dropping unused function argument globals [dist/ally.js:998,11]
WARN: Dropping unused function argument exports [dist/ally.js:995,90]
WARN: Dropping unused function argument module [dist/ally.js:995,83]
WARN: Dropping unused function argument require [dist/ally.js:995,75]
WARN: Dropping unused variable module [dist/ally.js:1,342]
WARN: Dropping unused variable exports [dist/ally.js:1,349]

><EMAIL_ADDRESS>build:umd:clean /Users/jnicklas/Desktop/ally.js
> rm dist/ally.js dist/ally.js.map

><EMAIL_ADDRESS>build:post /Users/jnicklas/Desktop/ally.js
> node build/build.post.js

><EMAIL_ADDRESS>build:archive /Users/jnicklas/Desktop/ally.js
> node build/build.archive.js

402952 total bytes
802417 total bytes

><EMAIL_ADDRESS>test /Users/jnicklas/Desktop/ally.js
> intern-runner config=test/chrome

I'm `fs` modules
TypeError: fs.mkdirSync is not a function
  at <node_modules/intern/lib/ReporterManager.js:137:10>
  at Array.reduce  <native>
  at mkdir  <node_modules/intern/lib/ReporterManager.js:134:33>
  at ReporterManager.add  <node_modules/intern/lib/ReporterManager.js:161:8>
  at <node_modules/intern/lib/executors/Executor.js:214:24>
  at execModule  <node_modules/dojo/loader.js:332:62>
  at <node_modules/dojo/loader.js:374:21>
  at guardCheckComplete  <node_modules/dojo/loader.js:361:9>
  at checkComplete  <node_modules/dojo/loader.js:366:32>
  at onLoadCallback  <node_modules/dojo/loader.js:428:17>

I was able to reproduce your problem when installing the dependencies using npm 3.10.6. This problem does not occur with npm 2.15.0.
The line I'm `fs` modules appears to to stem from the defunct npm package fs, which is a dependency of metalsmith-packagejson, which was fixed in the repo but apparently not published to npm.
Simply removing the offending module rm -rf node_modules/fs/ after installation does not break npm run build:website (i.e. metalsmith-packagejson seems to work fine). Also the tests will run fine, as require("fs") now properly resolves to node's core module.
I've opened thiagodemellobueno/metalsmith-packagejson#4 hoping the issue can be resolved properly. Otherwise we could simply rewrite that simply plugin ourselves, considering we already have a few in this repo.

[comment from #147] However although it is very slow it is also fine to work on a feature branch and let travis run the tests.

Travis runs the tests in 13 browser instances taking about 20 minutes per travis job. Tests are run in the open source tier of BrowserStack, which while free is limited to a certain amount of VM time. We ran 11 travis jobs yesterday, which is about 80% of the BrowserStack allowance we have. This doesn't scale well.
Running the tests locally in Chrome takes about 45 seconds on my machine. Obviously this doesn't run all the code (as there is a quite some code only running in Firefox or Safari or IE), but it gives a pretty good first impression.

Oh I see - didn't know about the VM time limitations..
after removing the fs module the tests work quite fine :)


Disallow read-through on internally-created MTRDevice instances.

We want to be able to instantiate an MTRDevice and readAttibute to get its cached state without ever triggering read-throughs.
The MTRDiagnosticLogsDownloader.mm changes were because it was using internal APIs to create an MTRDevice when it does not need an MTRDevice at all.

Fast-tracking platform-specific change with platform owner review.


unused Entry and unnecessary entry

I've been getting a deeper understanding of the code and found the following.

The type Entry defined in mintree.go does not appear to be used anywhere.  It is defined here: https://github.com/smartystreets/mafsa/blob/1575156d598714bb1c41713191eefb7f5ccf3e8b/mintree.go#L26

The entry argument to decodeEdge(...) seems to serve no purpose.  We only ever append to it and pass to recursive calls, but its never used for anything.  Further, when I remove it, and all usage of it, all tests in the package continue to pass.  See: https://github.com/smartystreets/mafsa/blob/1575156d598714bb1c41713191eefb7f5ccf3e8b/decoder.go#L85

Is this just left over from some previous version of the implementation?  Or am I missing some key aspect of the way things are working?

You are probably correct in both observations above. This repository was pioneered almost exclusively as an R&D experiment by @mholt who is no longer with SmartyStreets. Not much has happened with the code since then, although there are a few open pull requests.


Missing URL to docs website from GitHub repository or README

There is not a link to the hosted documentation site built from this repository. The URL should be added in two places:

GitHub repository infobox (found in upper-right on the Code tab of repository)
Linked from repo README.md file

Example 1:

Reference: https://tillioss.github.io/tilli-docs/

We have sent the list of descriptions that needs to be updated (About Section) of each repo to Ravi's team. They are currently updating teh same.

Instead of the above landing page, we have linked a new landing page that is on our website. Kindly visit: https://www.tillikids.com/opensource

Could you clarify the purpose of this existing site?

We have sent the list of descriptions that needs to be updated (About Section) of each repo to Ravi's team. They are currently updating the same.

Could you also clarify which page or section is being updated?

Hello Justin,

Instead of the above landing page, we have linked a new landing page that is on our website. Kindly visit: https://www.tillikids.com/opensourceCould you clarify the purpose of this existing site?

-  Our main website is www.tillikids.com, and we would have more traction of users coming into our website and wanted to add a page that took users to the open-source documentation.

We were also facing issues in updating only the landing page section and wanted a more user-friendly landing page that opened the Project Charter (https://tillioss.github.io/docs/project-charter/)

We have sent the list of descriptions that needs to be updated (About Section) of each repo to Ravi's team. They are currently updating the same.

Could you also clarify which page or section is being updated?

Kindly find the screenshots attached below for the respective pages:

Thanks for this @Hannah31George 👍🏻 Now I understand what you mean about updating the About section. Makes sense!
In our call today, I am thinking we can discuss these options in more detail and figure out an approach that works best for the Tilli team:

Unifying to one documentation site

Strength: One universal place to find information and make changes.
Weakness: Not possible for external contributors to contribute or make changes.
Opportunity: A smoother onboarding experience for an external contributor or newcomer to the project.
Threat: Requires revisions to UNICEF Venture Fund workplan.

Using a developer/contributor portal on main site, and open docs for project/developer information

Strength: Two different sites for different audiences. Each audience is better able to find the specific details they are looking for.
Weakness: Requires organization to ensure the two sites are aligned and do not contradict each other.
Opportunity: Better messaging on the Open Source approach, where the main website is for partners, investors, and media, while the developer docs are for contributors, involved stakeholders, and day-to-day participants in the project.
Threat: Unclear policy for what content goes on which site and how information is updated on one site or the other.


Thumbnails not saving (soundcloud)

Checklist

[x ] I'm asking a question
[ x] I've looked through the README and FAQ for similar questions
[ x] I've searched the bugtracker for similar questions including closed ones

Question

I am attempting to use YouTube-dl to download Soundcloud music. This works fine, but when I try using the --embed-thumbnail command, it downloads the music, the thumbnail appears briefly and correctly, but, when it moves onto the next song the thumbnail/artwork COMPLETELY DISAPPEARS. If I just use the --write-thumbnail command it will download them properly, but then they aren't embedded obviously. Am I missing a simple command?


Project filters/ categories

Create categories/ filter labels for the project data --- to give art students a place to post their projects as well.

https://github.com/thinkfiveable/art resolves this issue👌


Uncaught TypeError: Cannot read property 'toFixed' of null

There is an issues with the generated page, on this function
$(".olsr2lb" + number).text(function() {
return rgrs.regRSquare.estLowerBound.toFixed(3);
});
My haskell code I was trying to measure
http://pastebin.com/kie5sn6u
Here's the generated code
http://pastebin.com/DwL6Ru9t
I'm compiling with this command on windows 8.1, using GHC 7.8.3
ghc TP2.hs -threaded -O2 -fexcess-precision -optc-O2

Hi @bruno-cadorette, sorry it's taken me so long to get around to this. Are you still experiencing this issue?
I tried running your example, but I ran into this:
$ ./Example
Example: test.txt: openBinaryFile: does not exist (No such file or directory)

What should be the contents of test.txt?


[warn] 3507#0: *334576 an upstream response is buffered to a temporary file /usr/local/kong/proxy_temp/6/14/0000000146 while reading upstream

Summary

Kong version ($ kong version)
kong 0.9.1

tail -f error.log
2016/09/18 18:27:58 [warn] 3505#0: *354358 an upstream response is buffered to a temporary file /usr/local/kong/proxy_temp/1/16/0000000161 while reading upstream, client: <IP_ADDRESS>, server: kong, request: "GET
how to fix?

This is Nginx's behavior, not Kong. See nginx_http_proxy_module's directives and how to configure them . See the proxy_max_temp_file_size and proxy_buffers in particular.

Thank you, according to your approach has been resolved

@dzhyw
Can you please elaborate how did you fixed that ?
I've the same issue where the first request to kong is being written to the buffer while the second one goes without buffer needs.

Set the size of the parameter client_body_buffer_size in the kong.conf file. @geostant

@jiaomengchong 3 years ago in hitech nation... swapped several jobs since than :D

how to fix it in a docker container?

how to fix it in a docker container?

@jagerzhang use environment variables
NGINX_HTTP_CLIENT_BODY_BUFFER_SIZE=250k


test: adjust tests for mandatory tail calls on Win64

Since we are force enabling the mandatory tail calls on Windows x64, even at the expense of stack traces and debugging support, adjust the tests to account for the difference.

Please test with following PRs:
https://github.com/apple/llvm-project/pull/6282
@swift-ci please build toolchain Windows platform

@swift-ci please test

Please test with following PRs:
https://github.com/apple/llvm-project/pull/6282
@swift-ci please build toolchain Windows platform

Please test with following PRs:
https://github.com/apple/llvm-project/pull/6282
@swift-ci please build toolchain Windows platform

Please test with following PRs:
apple/llvm-project#6281
@swift-ci please build toolchain Windows platform

Please test with following PRs:
https://github.com/apple/llvm-project/pull/6281
@swift-ci please build toolchain Windows platform

Please test with following PRs:
https://github.com/apple/llvm-project/pull/6281
@swift-ci please build toolchain Windows platform

Please test with following PRs:
https://github.com/apple/llvm-project/pull/6281
https://github.com/apple/swift-corelibs-foundation/pull/4715
@swift-ci please build toolchain Windows platform

Failed Tests (3):
  Swift(windows-x86_64) :: IRGen/async/hop_to_executor.sil
  Swift(windows-x86_64) :: IRGen/async/run-call-dynamic-void_to_void.swift
  Swift(windows-x86_64) :: IRGen/async_dynamic_replacement.swift

Please test with following PRs:
https://github.com/apple/llvm-project/pull/6281
@swift-ci please test Windows platform


Code coverage on .NET Core

Description
Code coverage does not work in .NET Core
Steps to reproduce
Run vstest.console.exe /enablecodecoverage /framework:netcoreapp
Expected behavior
Runs the tests with code coverage enabled on .NET Core
Actual behavior
Error: Invalid .Net Framework version:netcoreapp11. Supported .Net Framework versions are Framework35, Framework40 and Framework45.

Environment
VS 2017 RTM
Windows 10 14393.693

Code coverage support not available in 15.0.0. Doc.
Please use /Framework:FrameworkCore10 for .Net core apps.

Error message should display as follows:
Error: Invalid .Net Framework version:netcoreapp11. Supported .Net Framework versions are Framework35, Framework40, Framework45 and FrameworkCore10.

What is the timeline to support .NET Core

@twsouthwick this will likely come in the next release (15.1 or 15.2 preview). We're still working out the details. Current thought process:

In console, code coverage will show up as a data collector (spec is here). User may install the code coverage nuget package, and use it like dotnet test --collect:coverage
In VS, it will show up as the existing Analyze Code Coverage in test explorer

We're first enabling the infrastructure (data collectors), this will allow the community to author code coverage extensions for dotnet test. VS code coverage support will use the same infra.

I was struggling with this, but found Microsoft.CodeCoverage started working when I added Full/> to the project containing the assembly to have coverage:
I'm using Microsoft.CodeCoverage 1.0.2, xunit 2.2.0, Ms.Test.sdk 15.0. The project under test is .net framework 4.5.1 and uses nuget packages for .net core 1.1.1 throughout
Can someone else please check and confirm?

net452
win7-x86
true
ExtranetManager
Exe
Full
ExtranetManager

@robalexclark your test is running on .NET Framework which is supported at the moment. The debugtype had to be changed because by default it builds with the new portable format, which is currently unsupported with vstest. If you switched your test to run as a .netcoreapp you won't see any coverage results.

uses nuget packages for .net core 1.1.1 throughout

This is probably not what you think it means. The nuget packages may support .NET Core 1.1.1, but are either targeting .NET Standard or have a .NET Framework version. These are then being selected when running on .NET Framework. The goal of .NET Standard is to allow the same binary to run on multiple runtimes (.NET Core and .NET Framework are two distinct runtimes).
If the project is one you can share, we can verify if this is the case based on the project files and packages.

Apologies yes you are right - I am running on .net 4.5.1 as runtime.

Easy mistake to make in some projects!

Hi all!
Do you have any plans about implementation code coverage for dotNetCore for Linux?
If you have any PR or subtasks, I am ready to help.

@codito I would like to try out the "dotnet test --collect:coverage" for my dotnet core VSTS builds. Do you have any insight/guidance as to when that will be available and we will need to do to get it working?
Thanks for your help!

Hi all,
Is there any update on whether there will be .NET Core code coverage support for Linux too?
Thanks,
Mark

Any update - VS 2017 is expensive product one of key features is code coverage

Guys just yesterday I found a new Nuget Package:
Microsoft.CodeCoverage version 1.0.3
I updated the package into my XUnit test project and run Tests + Code Coverage in VS 2017 Ultimate.
The tests are executed but the Code Coverage is not even triggered:

So, what's going on? Any official Docs yet?

Also if I pass dotnet test --collect:coverage
This is what we get NOT IMPLEMENTED
MSBUILD : error MSB1001: Unknown switch.
Switch: --collect:coverage
For switch syntax, type "MSBuild /help"
Process completed with exit code 1.

This feature hasn't shipped yet. We're pretty close though, will provide an update soon :)

In 15.3 Preview 1, code coverage for .NET core is available in VS. Instructions are here: https://github.com/Microsoft/vstest-docs/blob/master/docs/analyze.md#coverage. Please try it out.
We're working on bringing coverage to dotnet test command line.

@codito we just tried with these versions:

Visual Studio 2017 15.2
xunit  2.2.0
Microsoft.NET.Test.Sdk" Version="15.3.0-preview-20170502-03"

Tests run and they are green but Code Coverage is not triggered.
Is it working only with MsTest? I hope we don't have to re-write all our tests 😢

@raffaeu it is available in VS 2017 15.3 preview 1, you can get the build from https://www.visualstudio.com/vs/preview/. It works with all frameworks :)

Oh, thanks I will try then with the preview version
Thank you

Currently known issues are tracked here: https://github.com/Microsoft/vstest/labels/exp%3A coverage

Hey, finally, great !
Nice to have it again with preview version. And I should also notice that this preview version (15.3) seems to works better than currently supported one (15.2) ...
Can't wait to use it every day

@codito presumably the dotnet test version of the coverage runner you speak won't be the same as that vstest uses right? When you say something like that I get hopeful for those like me on mac/linux. Is there seperate issues for the dotnet test coverage support?

@twgraham test code coverage is VS enterprise and windows only so far, current plan is to get the same level of support in dotnet test (windows + VS enterprise). Mac/linux support isn't in our immediate backlog. /cc @pvlakshm @sbaid to consider the feedback for prioritization.

Any update on this? we need test coverage to work in .net core application, stranded a bit. I installed the Visual Studio 2017 version 15.3 preview in the hopes of this getting done but still code coverage is missing. When I run my unit tests code coverage result comes back empty wtih message: "Empty results generated: No binaries were instrumented....". I know that this is in progress but will code coverage be part of 15.3?

@codito Furthermore, is it the plan to include support of dotnet test code coverage in 15.3 / 2.0 initial versions or should I be exploring other avenues for the time being? If not the previous versions, is there a proposed time/release for this behavior? (so I may explain to others the decision to use 3rd party tools instead of wait for official MSFT tools)

@codito Do you have high-level timing you can share for when dotnet test with code coverage will be cross-platform? Q3? Q4? 2018? It'd be nice to know just for planning purposes.

I tried out dotnet test --collect:coverage on .NET CLI 2.1.0-preview1-006547, and this is what I got:
dotnet exec needs a managed .dll or .exe extension. The application specified was 'C:\Program'
Seems someone needs to quote a path somewhere :P

Hi @Alxandr
I tried to repro this using .NET CLI 2.1.0-preview1-006567. It seems to be working as expected for me.

If it is a consistent repro, please share repro steps so that we can look into the issue.

Huh. That's weird. I'll try to do some more testing with it.

I'm getting a similar error that that's giving me an object reference not set to an instance of an object.
 1>Done building target "ShowCallOfVSTestTaskWithParameter" in project "UnitTestProject1.csproj".
   Done executing task "CallTarget".
   Using "Microsoft.TestPlatform.Build.Tasks.VSTestTask" task from assembly "C:\Program Files\dotnet\sdk\2.0.0-preview1-005977\Microsoft.TestPlatform.Build.dll".
   Task "Microsoft.TestPlatform.Build.Tasks.VSTestTask"

Object reference not set to an instance of an object.
Object reference not set to an instance of an object.
   Done executing task "Microsoft.TestPlatform.Build.Tasks.VSTestTask" -- FAILED.
 1>Done building target "VSTest" in project "UnitTestProject1.csproj" -- FAILED.
 1>Done Building Project "C:\code\bitbucket\CITestProject\UnitTestProject1\UnitTestProject1.csproj" (VSTest target(s)) -- FAILED.

@dnelly Please consider upgrading to latest version of CLI.
@Alxandr also faced similar issues in 2.1.0-preview1-006547 which are not there in 2.1.0-preview1-006567.
Do let us know if you face these issues even after upgrading to latest version.

Stil lsame error.

@harshjain2 Yeah, it was still the same for me as well.
Here's the current version 2.0.0-preview2-006497

the error seems to come from this Test Execution Command Line Tool Version 15.3.0-dev

@dnelly @Alxandr Created an issue https://github.com/Microsoft/vstest/issues/902 for investigating this further.

Thank you!

Is there a way to get the code coverage flags to work on VSTS?  The best I can tell VSTS only has 15.0 available and not any of the pre-releases.
Everything works fantastic locally. Thanks for all the hard work!

Created a separate issue for providing support for dotnet test --collect:"Code Coverage" https://github.com/Microsoft/vstest/issues/981 as this issue is for code coverage support for vstest.console.exe

Still doesn't work in VS2017 15.3. My coverage only shows for my test library, coverage for the tested library is not shown.

@mstephens-adig VS 2017 15.3 is released now.
https://blogs.msdn.microsoft.com/visualstudio/2017/08/14/visual-studio-2017-version-15-3-released/
Upgrading to latest released version in VSTS should solve your problem.

@harshjain2 it's still happening on my end with 15.3.

@Mardoxx Thanks for trying it out. This workaround is required for code coverage to work on .NET Core

Please try code coverage and let us know if there is any feedback/issues.
I am closing this issue for now.

@harshjain2 Is the nuget package a temporary workaround or a permanent one, aka I don't want to spent a lot of time adding it now to remove it in two months

It seems it's not working with .NET Core 2.0 ?
Or maybe it's with xunit 2.2.0 ?

Coverage is still not working in VSTS, at least I can get the test results
https://github.com/Microsoft/vsts-tasks/issues/5066

I would imagine this is because your agent is not up to date. Check what version of VS2017 your agent is using. Any >15.3 should work.

@Mardoxx It is Hosted VS 2017, they updated to 15.3 recently

Ah! Now I look, mine don't have coverage either!

@harshjain2 Is the nuget package a temporary workaround or a permanent one ? I mean I don't want to spent a lot of time adding it now to remove it in two months...
We are tracking the issue to remove need to manually add nuget package here.
https://github.com/Microsoft/vstest/issues/852.
We will prioritize it soon.

Hi, we followed all above, and still no luck.  Found different paths from log:
2017-08-24T22:58:11.1157918Z Attachments:
2017-08-24T22:58:11.1157918Z   d:\a\1\s\TestResults*672524f6-3c0c-4dc4-86c9-4b58f01c9577\buildguest_FACTORYVM-AZ220 2017-08-24 22_58_06.coverage*
2017-08-24T22:58:11.1157918Z
2017-08-24T22:58:11.1157918Z Total tests: 1. Passed: 1. Failed: 0. Skipped: 0.
2017-08-24T22:58:11.1157918Z Test Run Successful.
2017-08-24T22:58:11.1167892Z Test execution time: 4.6567 Seconds
2017-08-24T22:58:11.1508492Z Results File: d:\a\1\s\TestResults\buildguest_FACTORYVM-AZ220_2017-08-24_22_58_11.trx
2017-08-24T22:58:13.3673473Z ##[section]Async Command Start: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command End: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command Start: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command End: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command Start: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command End: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command Start: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command End: Telemetry
2017-08-24T22:58:13.3673473Z ##[section]Async Command Start: Publish test results
2017-08-24T22:58:13.8241527Z Publishing test results to test run '59'
2017-08-24T22:58:13.8241527Z Test results remaining: 1. Test run id: 59
2017-08-24T22:58:14.1399971Z ##[warning]Skipping attachment as it exceeded the maximum allowed size or not available on disk: d:\a\1\s\TestResults*buildguest_FACTORYVM-AZ220_2017-08-24_22_58_11\In\FACTORYVM-AZ220\buildguest_FACTORYVM-AZ220 2017-08-24 22_58_06.coverage*
Could this be the case why codecoverage not published?
Also, once it's published, should it be visible under Code Coverage?

CC @nigurr for vstest-task

Hi,
We are fixing this issue as part of this https://github.com/Microsoft/vsts-agent/pull/1149/files
Will update the thread once we release the fix.
Sorry for the trouble.

https://developercommunity.visualstudio.com/comments/84459/view.html

Getting similar results as folks above

is referenced in my test project.
dotnet test --collect:coverage

Microsoft (R) Test Execution Command Line Tool Version 15.3.0-preview-20170628-02
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
dotnet exec needs a managed .dll or .exe extension. The application specified was 'C:\Program'

Object reference not set to an instance of an object.
Object reference not set to an instance of an object.

even if I use vstest.console.exe like described in https://github.com/Microsoft/vstest-docs/blob/master/docs/analyze.md#coverage like this:
vstest.console.exe --collect:"Code Coverage" --framework:".NETCoreApp,Version=v2.0" bin\Debug\netcoreapp2.0\some.tests.dll

I am getting:
Microsoft (R) Test Execution Command Line Tool Version 15.0.26929.2
Copyright (c) Microsoft Corporation.  All rights reserved.

Error: The test source file "--collect:Code Coverage" provided was not found.
Error: The test source file "--framework:.NETCoreApp,Version=v2.0" provided was not found.

I am running VS2017 Enterprise V15.4.1

@sbaid: Thank you so much, this works now :)

Is there a way to pass the --collect:"Code Coverage" switch to dotnet vstest instead of using vstest.console.exe?

I get the below error. Has any one see/resolved this.
Test run will use DLL(s) built for framework NETCoreApp,Version=v2.0 and platform X86. Following DLL(s) do not match framework/platform settings.
.Test.dll is built for Framework 2.0 and Platform X86.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\TestPlatform\vstest.console.exe" F:\Vsts\agent-1_work\14\a\Release\Deploy\Publications<folder><asembly>.Test.dll /EnableCodeCoverage /logger:trx "/TestAdapterPath:"F:\Vsts\agent-1_work\14\a"" /Framework:NETCoreApp,Version=v2.0 /logger:console;verbosity=normal

This is still an issue for XUnit on .NET Core 2.0 projects. Why is this closed?

Thats the latest update from Microsoft I believe - https://github.com/Microsoft/vstest-docs/blob/master/RFCs/0021-CodeCoverageForNetCore.md


Working with vimtemplates (another folder)

It doesn't quite work with the plugin vimtemplates
https://github.com/drbeco/vimtemplates
The plugin need to install things in a different subdirectory
~/.vim/templates # For template files
and
~/.vim/plugged/vimtemplates/plugin/vimtemplates.vim # For the plugin itself
Other than that, just to say, this plugin manager is AWSOME!
Thanks a lot

Just to be sure, to install it one should just add:
" Vimtemplates - templates for diverse files
Plug 'drbeco/vimtemplates'

Is it as simple as that, right? It will then clone the whole repository?

Oh, never mind. I changed the reference to the directory ~/.vim/templates/ to ~/.vim/plugged/vimtemplates/templates/
It work as a charm now, and it is better that the templates keep inside the repository.
It is a good thing that this plugin manager clone the entire repository, so plugin authors have a little freedom.
Thanks a lot.

No problem, good to hear that you figured it out.


paper1111: Watch https://www.powerjackpowerinverter.de/

paper1111 requests the watch of the watch_keyword https://www.powerjackpowerinverter.de/. See the Metasmoke search here

!!/approve


Add some user input from client side

Just for completeness, add an input to allow user to change some aspect of the app behavior.  I'm thinking changing the step size for the random walk simulations would be good.  Larger values would show up as more frequent color changes in the view.
I'm open to other ideas that come in before I get around to it.  Keep it simple, please.  I don't want the demo to grow much in size or complexity -- it's meant to be a useful skeleton that also teaches a few fundamentals of web app development.

Done by adding step size input field.


Installation documentation for Laravel - optional vendor:publish step is actually required

Hi,
On this page https://docs.bugsnag.com/platforms/php/laravel/ it is stated:

If you’d like to configure Bugsnag further, create and edit a configuration file:
   $ php artisan vendor:publish

This step is actually required for Bugsnag to be able to find your API key from your .env file - you must have a bugsnag.php file in the config directory. If you do not do this step, you will get "API key not found" errors.
Quite a small detail of the docs but took a little while to figure out, so please correct. Cheers!

Thanks for getting in touch, but you shouldn't have to publish the config file to get this working. Did you remember to run php artisan config:cache?

Hi, thanks for the reply. Nice project, Bugsnag is useful.
I didn't run php artisan config:cache - I'll try it on a fresh project later (quite busy lately). If it is required, please add to the guide.
Cheers

It's required on all laravel projects whenever you want to update the config. We could add it to the guide to remind people though.

I can't replicate this on any Laravel version. it must be due to not correctly caching the config files.


SCNetworkReachability API deprecations.

Discussed in https://github.com/firebase/firebase-ios-sdk/discussions/12592

Originally posted by FONickReichard March 19, 2024
Today, I discovered that starting with iOS 17.4, several methods within the SCNetworkReachability API collection are being marked as deprecated.
https://developer.apple.com/documentation/systemconfiguration/scnetworkreachability-g7d
It looks like the FirebasePerformance/Sources/FPRNanoPbUtils.m currently uses SCNetworkReachabilityGetFlags, which is apart of the deprecations.
I wanted to pass along this deprecation notice, as it seems to be new, and ensure that y'all can catch it early if it's not already on the road map.
Best,
Nick
PS: Thanks for all the goods you create.

At WWDC18, Apple teased the end of reachability by asking everyone to move to NWPathMonitor. Here is the video that will be helpful to identify the replacement that's been around for a while.
https://developer.apple.com/wwdc18/715?time=3459

It looks like https://developer.apple.com/documentation/network/nwpathmonitor requires iOS12+, @paulb777 do you known when will we move to iOS12?

We plan to move to iOS 13 later this year in the next major release. I'll mark this issue for that milestone.

Xcode 15, which is required in April, doesn't support iOS 11.

Split Performance into a separate issue at #13079

@wu-hui Nothing should be blocking this issue now that the minimum supported version is iOS 13


[$1000] 'Edit comment' option is available for the comment sent in a room that is now archived

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to Settings > Workspaces
Create any workspace
Go to that workspace's admin room
Send any message in the room
Keep that room open and go to the workspace
Click on three vertical dots
Delete workspace
Hover over the comment you send and click 'Edit comment'

Expected Result:
'Edit comment' option should not be there
Actual Result:
'Edit comment' option is there
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.2.97-2
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/43996225/230700017-eed53a50-3e30-4136-a3ed-05eb2065b877.mp4
https://user-images.githubusercontent.com/43996225/230700024-5f193fdf-9699-44b4-96fa-e1046bdaec6c.mov
Expensify/Expensify Issue URL:
Issue reported by: @adeel0202
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1680890515337059
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013e9ed39c89a615a2
Upwork Job ID:<PHONE_NUMBER>358878720
Last Price Increase: 2023-04-10

Triggered auto assignment to @CortneyOfstad (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Was able to recreate this as shown below:

Getting some eyes on this

Job added to Upwork: https://www.upwork.com/jobs/~013e9ed39c89a615a2

Triggered auto assignment to @francoisl (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

I can't reproduce this and found the backend send the pusher event after deleting a room. See log from console like
[info] [Report] Handled onyxApiUpdate event sent by Pusher ......

@allroundexperts Oh I see, thank you! I followed the bug report and it doesn’t mention about offline.

@allroundexperts I think you tagged me by mistake? I didn't comment on this issue I think...

Looks good to me, let's go with your proposal @allroundexperts.

📣 @allroundexperts You have been assigned to this job by @francoisl!
Please apply to this job in Upwork and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑💻
Keep in mind: Code of Conduct | Contributing 📖

Reassigning as I am heading on sabbatical 👍

Triggered auto assignment to @garrettmknight (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Offers sent

Reviewing label has been removed, please complete the "BugZero Checklist".

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[ ] [@thesahindia] The PR that introduced the bug has been identified. Link to the PR:
[ ] [@thesahindia] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
[ ] [@thesahindia] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
[ ] [@garrettmknight] Determine if we should create a regression test for this bug.
[ ] [@thesahindia] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ] [@garrettmknight] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Triggered auto assignment to @dylanexpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Reassigning for payment next week assuming no regression. Thanks!

Payments all sent! Before closing, @thesahindia can we complete the above tasks in the checklist? Thank you!

Nice, thank you!

Got it!

RT: https://github.com/Expensify/Expensify/issues/281331


Add Query length & Answer length to dns_activity class

We would like to add the field length to the dns query and answer object's so we can use that field to calculating the length of dns queries.
query.length
answer.length

Would this be a length of time?  If so, can you use duration from the Base class?
Or maybe you need both at the same event?
It seems like it would be unusual for a single event to tell you how long the query itself took, separate from the time to respond.
However, the way duration is described, it implies (end_time - start_time ) rather than the duration of some arbitrary operation.  That description can be fixed w/o breaking though.


could i unregister a service instance from eureka with spring cloud eureka annotation?

could i unregister a service instance from eureka with spring cloud eureka annotation?

I am not sure how an annotation would be able to do that, annotations are static.  Can you elaborate more?

I am trying to implement service discovery and registry with spring cloud commons 'Discovery' interface,  so that i can replace my underlying implementations flexibly just by replacing the jar file on the classpath. could I do it with Discovery interface ?

By default, closing the application context unregisters the application in Camden and prior. Starting in Dalston, you'll have more programmatic control. See https://github.com/spring-cloud/spring-cloud-commons/issues/9


Warn the user if there is a duplicated dom-module at compile time

This would be nice as compared to a runtime error :)

Someone is thinking ahead ☺

I'm going to check in with some of the core webpack devs, but I suspect that this check will have to be a separate plugin. A loader typically only looks at a single file at a time and development standards warn about keeping state between them.
We're going to need a true webpack plugin or two. It's still a todo to figure out how to integrate the Polymer analyzer and linter. And I need Polymer-Rename for closure-compiler projects.

The actual problem here is implementing bundling strategies, like generateSharedDepsMergeStrategy and maybe others from polymer-bundler, isn't it?

No the problem is npm doesn't create a flat dependency tree.

@samccone I'm closing this as out of scope for a loader. It's still on my radar, but it would need to be a webpack plugin of some kind.


Support broadcast exchange (and broadcast join)

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Broadcasting partitions helps for when
Describe the solution you'd like
We should support broadcasts in the physical plan.
Broadcasting means copying the entire dataset to each worker.
This could be used in broadcast joins, i.e. by broadcasting smaller dataframes to every worker, which can provide big speedups as the other (big) side doesn't have to be shuffled.
Describe alternatives you've considered
Additional context
Probably we can reuse some heuristics from Spark for conditions when to perform broadcasting for joins.

One quick question regarding this,  after those dataset are copied to each work, should they kept in-memory or spilled to disk, if keep them in memory for a while, memory usage might be a concern.

@mingmwang I think for broadcasting exchange the same thing applies as normal exchanges, they are spilled to disk by default and might be maintained in memory if memory budget allows. I believe Ballista doesn't support the latter yet(?). A limit may be chosen, like 100MB, so it will fit in memory most often, but even when written to disk for joins it might give impressive speedups as the other side of the join could be way larger.

@Dandandan Sounds nice.
There are couple of things need to do to support the broadcasting exchange.

Rpc protocols to efficiently do broadcasting, something similar to Spark's TorrentBroadcast
Executor memory management as you just mentioned.
Broadcast lifecycle management, after SQL finish, those broadcasts should be cleaned.
Planner need more accurate stats to choose broadcast join or partitioned hash join or even SortMergeJoin,
build side selection etc. Need to enhance the stats collection.
Broadcast exchange reuse within SQL?
Broadcast reuse between SQLs ?

Today,  For partitioned hash join, DataFusion already support CollectLeft model, I think it is similar to the Broadcast HashJoin. I do not get a chance to test it on Ballista yet, but I think it should work in the distribution model. The downside is
the Left side might cause lots of duplicate re-computations.

  fn required_input_distribution(&self) -> Vec<Distribution> {
        match self.mode {
            PartitionMode::CollectLeft => vec![
                Distribution::SinglePartition,
                Distribution::UnspecifiedDistribution,
            ],
            PartitionMode::Partitioned => {
                let (left_expr, right_expr) = self
                    .on
                    .iter()
                    .map(|(l, r)| {
                        (
                            Arc::new(l.clone()) as Arc<dyn PhysicalExpr>,
                            Arc::new(r.clone()) as Arc<dyn PhysicalExpr>,
                        )
                    })
                    .unzip();
                vec![
                    Distribution::HashPartitioned(left_expr),
                    Distribution::HashPartitioned(right_expr),
                ]
            }
        }
    }

That's a good observation @mingmwang !
The difference with CollectLeft is that that mode collects the left side to one partition, whereas with broadcast we would broadcast the output of the left side to each worker.
Indeed, I think the trade off is that doing a bit more on the left side (i.e. building the hash table in each worker) we save the work on the right side (shuffle).

I added some details for implementing a broadcast join optimization rule here: https://github.com/apache/arrow-ballista/issues/348 .


Add utility methods to UploadEvents to generate mapping-specific event names

This PR adds some utility methods to the UploadEvents class that generates event names based on the mapping you pass to it (similar to this). This saves you some typing when using the mapping-specific events in a subscriber:
E.g. this:
public function getSubscribedEvents()
{
    return [UploadEvents::POST_UPLOAD . '.gallery' => ['onPostUpload']];
}

Becomes this:
public function getSubscribedEvents()
{
    return [UploadEvents::postUpload('gallery') => ['onPostUpload']];
}

I thought this would be a nice little addition. Feel free to just close the PR if you disagree :).

Thank you! I'm fine with this, so I'll merge it asap =)

Version 2.1.0 is released! 🎉


Pager component: show only prev/next links

Looks like it's not possible to show only next/prev links with the Pager.
From my understanding, showLinks would be used to enable/disable the numeric page links? Because if it's meant to completely remove the pagination, you just wouldn't use the component, right?
If I set it to false, the entire navigation disappears.
Steps to reproduce
Try using the Pager component like this:
<Pager :info="$page.myobject.pageInfo" :showLinks="false"/>

Expected result
See only next/prev links in pagination (numeric page links removed).
Actual result
Pagination is completely removed.

I get that this could be a feature of the pager out of the box... but I wanted my own pagination so I just rolled my own using the css framework that I am using (Bulma) and it was fairly easy. I could just as easy take out the links if I wanted to...Just wanted to share in case its helpful.
https://github.com/cfaddict/danvega-me/blob/master/src/components/BulmaPagination.vue

Yup, built my own component too, along the same lines. Just thought it might be useful for the included Pager component :)

@hellocosmin Thanks for the request, and sounds like a good idea to me. What do you think @tomtev @hjvedvik?
@hellocosmin  @cfaddict if you'd like to make an attempt at creating a PR for this (utilizing your existing own pagination) let me know, and I'll assign the issue to you.


ActiveRecord::find()->indexBy()->column() not indexing as expected

Given the documentation of select(), indexBy and column() I expected
Book::find()->select('title')->indexBy('isbn')->column()

to return an associative array of book titles indexed by ISBN. It returned instead a numeric array of titles. The following produced the same result.
Book::find()->select(['title', 'isbn'])->indexBy('isbn')->column()

In other words, for the above two cases indexBy() doesn't do anything.
The following returned an array of Book models indexed by ISBN but if indexBy is only supposed to work with certain getters like all() then the documentation for indexBy() should say so.
Book::find()->indexBy('isbn')->all()

If indexBy() is really just an option for all() then shouldn't it be a parameter of that method rather than a property of Query.

acept it - https://github.com/yiisoft/yii2/issues/7107#issuecomment-72256210

That's more of design decision. @qiangxue is it expected or should be fixed?

This is currently working as expected as column() uses the native PDO column fetch mode.
But I think we can consider enhancing column() in this case.

it worked before

@samdark what does "status:ready for adoption" mean?

Means that it is OK to improve it so it could be worked on.

I have same issue. @samdark @qiangxue when it will be adopted? This issue allows to save proccessing time and forget about ArrayHelper::map().

You can speed things up by working on a pull request.

It's really good news, if select(['id', 'name']), indexBy('id') and column('name') will return result:
array(id=>name)

column($db = null)
column fetch first column, i use it
MyModel::find()->select('name', 'id')->indexBy('id')->column()

Anyway it's more useful, than use ArrayHelper for this simple need.

Is there already an easier way instead of using ArrayHelper to get the following result:
[id => name]

All I'm getting is (->select(id,name)->indexBy(id)->all()):
[id => [id, name]]

@MelleDijkstra try ->select('name')->indexBy('id')->column()

@tom-- I'll give it a try!


Optionally only use highway=footways

https://www.openstreetmap.org/way/9929318 is incorrectly marked as a severance right now. Actually, we don't want to import this road into the model at all. In the area, it looks like there's consistently good use of highway=footway. This tool works best in that case; sidewalk tagging on the road makes things confusing. Currently the import process tries to compromise. As a next step, in the UI let people configure whether to ignore these sidewalk=separate cases or not.
CC @starsep, you're likely to see this problem very soon :)

There's now an option on the import page to decide what to do here. If the OSM tagging is good, uncheck it and get cleaner results.
Enabled:

Disabled:


fix for #748

that fields doesnt popup because they was shown only after onAuthCookieAcquired fired

Codecov Report

Merging #769 into master will not change coverage.
The diff coverage is 0%.

@@          Coverage Diff           @@
##           master    #769   +/-   ##
======================================
  Coverage    6.23%   6.23%
======================================
  Files          93      93
  Lines        5033    5033
  Branches      455     455
======================================
  Hits          314     314
  Misses       4693    4693
  Partials       26      26

Impacted Files
Coverage Δ

...r/free/nrw/commons/auth/AuthenticatedActivity.java
0% <ø> (ø)
:arrow_up:

...java/fr/free/nrw/commons/upload/ShareActivity.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

This seems to solve the problem for me! How about you @nicolas-raoul ?

Sorry I don't have much time to check this week :-/
On Thu, Jul 13, 2017 at 1:58 AM, Josephine Lim<EMAIL_ADDRESS>wrote:

This seems to solve the problem for me! How about you @nicolas-raoul
https://github.com/nicolas-raoul ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commons-app/apps-android-commons/pull/769#issuecomment-314831877,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGFBr6w1AhoxnVvBYa8ajR9E411mtXNks5sNPsjgaJpZM4OVXLI
.

No worries, I will go ahead and merge soon if no one has any concerns about bypassing authentication checks. Technically the user should not even be able to get to that stage without being logged in, so IMO it may be worth bypassing the check to prevent a rather frequent and annoying bug.


ASC (MDFC) export to Azure Monitor is not reliable due to DINE policy race condition

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions
terraform: 1.2.2
azure provider: 3.20
module: 3.1.2
Description
Describe the bug
MDFC export to LAW policy does not enable the functionality due to race condition.
Steps to Reproduce

Deploy default architecture with configure_management_resources
Observe subscription MDFC continuous export configuration not correct
Observe Deploy-MDFC-Config policy not compliant

Screenshots

Additional context
Recommend declaring azurerm_security_center_automation resource to prevent this happening.

Trigger ADO Sync

We can implement this for the connectivity and management Subscriptions as we have providers configured for these, but not for any others.
Are you proposing we implement this in conjunction with future integrations between this module and lz-vending?

Trigger ADO Sync

AB#26868


Adjust gas estimations for SafeTxGas

Background
safetxGas for Safe txs are overestimated (about 20-50%). That's because relay always make sure than the tx have enough gas for tx to succeed.
The estimation is done the following way:

We add 1k for the inner call
We add 35k gas extra for the inner call (for contracts compiled with solc < 0.4.21)
We do an estimation using the requiredTxGas of the Safe contract and regular web3 estimation. We get the max of both (usually, the web3 one)

Problem
Exceeding fees are returned to the user in the case that they are lower than the estimation, but we should find a way to show the user a more precise fee
Solution

Discard the web3 estimation and check if just the Safe Contract one is enough. A lot of testing has to be done, as we added that to prevent underestimating in some edge cases

Closed by #200


Are there plans to add support for Wasmtime?

What would you like to be added?
The readme mentions both Wasmtime and Wasmedge initially in wasm sections, but then mentions that only Wasmedge is currently supported. Are there plans to add support for Wasmtime?
Why is this needed?
Wasmtime is a popular wasm engine with 12K starts on Github vs 6K for Wasmedge. It is backed by Bytecode Alliance, which consists of many organizations. Adding support for Wasmtime should allow for easier adoption of Kuasar.

@yerke we make a first implementation of wasmtime now, please pull the newest codes and take a try.

Sorry it is not merged yet, please review this PR if you got time, https://github.com/kuasar-io/kuasar/pull/47


source code - Cubic Orange missing reference

I downloaded V73186 and i get two missing references i can't resolve: Cubic.Orange.Windows.Forms and GroupControls. I search on CubicOrange and didn't see anything. Are these assemblies in codeplex somewhere?
Originally posted: 2012-01-10T11:43:18

All dependent assemblies can be found in the TaskScheduleEditor download for the latest release.
Originally posted: 2012-01-10T20:11:51


Skeleton: a component to act as a placeholder for loading page sections and content

The problem
As various parts of the page or content are loaded via an API call, a micro frontend, or server-side rendering, we want to make sure our web vitals scores stay strong. One way this can be done is using placeholder elements to ensure better UX and page load.
The solution
Create a component that captures the pattern and offers the versatility needed to account for variation in page structure/content that would use it.
Alternatives considered
NA
Additional information
react-loading-skeleton and react-content-loader might be a good place to start in terms of API and DX inspiration

Moved to #649