add auction pageview event for criteo

Adds new tracking call to auction overview pages for marketing purposes.

Warnings

:warning:
The staging version of Metaphysics has breaking changes, this might not affect your build, but could mean your queries don't work the way you expect. See below for breaking changes:

:warning: Type 'ExactPrice' was removed
:warning: Member 'Money' was added to Union type 'ListPrice'
:warning: Member 'ExactPrice' was removed from Union type 'ListPrice'
:warning: Field 'minPriceCents' was removed from object type 'PriceRange'
:warning: Field 'maxPriceCents' was removed from object type 'PriceRange'

  Generated by :no_entry_sign: dangerJS against fdcaae33d6d6baafaf98a79efd9ef7902c119e6f

Duplicate Sources / Packages - Duplicates found! ⚠
Duplicates: Found 28 similar files across 35 code sources (both identical + similar)
accounting for 534877 bundled bytes.
Packages: Found 10 packages with 21 resolved, 25 installed, and 58 depended versions.
Roughly 102 lines removed.  This is probably an improvement over master.

Diff of duplicates in this branch vs master
 Duplicate Sources / Packages - Duplicates found! ⚠

-* Duplicates: Found 43 similar files across 50 code sources (both identical + similar)
+* Duplicates: Found 28 similar files across 35 code sources (both identical + similar)

-  accounting for 566753 bundled bytes.
+  accounting for 534877 bundled bytes.

-* Packages: Found 17 packages with 34 resolved, 38 installed, and 64 depended versions.
+* Packages: Found 10 packages with 21 resolved, 25 installed, and 58 depended versions.

-## artist.6261c976402db215a98d.js
+## auctions.94c594cd4b1657807617.js

-farce (Found 2 resolved, 2 installed, 3 depended. Latest 0.2.8.)
-  0.2.6
-    ~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in artist.6261c976402db215a98d.js
-        farce/lib/StateStorage.js (S, 2102)
-
-  0.2.8
-    ~/found-scroll/~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in artist.6261c976402db215a98d.js
-        farce/lib/StateStorage.js (S, 1906)
-
-## artwork.4815248f3b11ddc3b24e.js
-farce (Found 2 resolved, 2 installed, 3 depended. Latest 0.2.8.)
-  0.2.6
-    ~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in artwork.4815248f3b11ddc3b24e.js
-        farce/lib/StateStorage.js (S, 2102)
-
-  0.2.8
-    ~/found-scroll/~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in artwork.4815248f3b11ddc3b24e.js
-        farce/lib/StateStorage.js (S, 1906)
-
-## auction_reaction.e5ffaec1fc2309b69392.js
-farce (Found 2 resolved, 2 installed, 3 depended. Latest 0.2.8.)
-  0.2.6
-    ~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in auction_reaction.e5ffaec1fc2309b69392.js
-        farce/lib/StateStorage.js (S, 2102)
-
-  0.2.8
-    ~/found-scroll/~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in auction_reaction.e5ffaec1fc2309b69392.js
-        farce/lib/StateStorage.js (S, 1906)
-
-## auctions.d1cad975a975484f070c.js
-
 acorn (Found 2 resolved, 3 installed, 3 depended. Latest 2.7.0.)
   1.2.2
     ~/with/~/acorn
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in auctions.d1cad975a975484f070c.js
+      * Duplicated files in auctions.94c594cd4b1657807617.js

         acorn/dist/acorn.js (S, 131402)
         acorn/dist/walk.js (S, 11791)

   2.7.0
     ~/jade/~/acorn
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in auctions.d1cad975a975484f070c.js
+      * Duplicated files in auctions.94c594cd4b1657807617.js

         acorn/dist/acorn.js (I, 119975)
         acorn/dist/walk.js (I, 13326)

     ~/with/~/acorn-globals/~/acorn
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in auctions.d1cad975a975484f070c.js
+      * Duplicated files in auctions.94c594cd4b1657807617.js

         acorn/dist/acorn.js (I, 119975)
         acorn/dist/walk.js (I, 13326)

-## collect.576af9cf355664854560.js
+## common.10c02c82925d6908b4ee.js

-farce (Found 2 resolved, 2 installed, 3 depended. Latest 0.2.8.)
+@babel/runtime (Found 3 resolved, 5 installed, 18 depended. Latest 7.6.0.)

-  0.2.6
+  7.1.5

-    ~/farce
+    ~/dom-helpers/~/@babel/runtime

       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in collect.576af9cf355664854560.js
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-        farce/lib/StateStorage.js (S, 2102)
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-  0.2.8
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-    ~/found-scroll/~/farce
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Dependency graph
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in collect.576af9cf355664854560.js
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-        farce/lib/StateStorage.js (S, 1906)
+      * Duplicated files in common.10c02c82925d6908b4ee.js

+

-## common.a506dee5ae082d775809.js

-@babel/runtime (Found 3 resolved, 5 installed, 12 depended. Latest 7.6.0.)
+    ~/react-redux/~/@babel/runtime

-  7.1.5
-    ~/dom-helpers/~/@babel/runtime
-
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.10c02c82925d6908b4ee.js

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in common.a506dee5ae082d775809.js
-
-
-    ~/found/~/@babel/runtime
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in common.a506dee5ae082d775809.js
-
         @babel/runtime/helpers/esm/extends.js (I, 397)
         @babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js (I, 350)

     ~/styled-system/~/@babel/runtime
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         @babel/runtime/helpers/esm/extends.js (I, 397)

   7.4.5
     ~/@artsy/palette/~/@babel/runtime
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         @babel/runtime/helpers/assertThisInitialized.js (I, 219)
         @babel/runtime/helpers/esm/extends.js (I, 397)
         @babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js (I, 350)

   7.6.0
     ~/@babel/runtime
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         @babel/runtime/helpers/assertThisInitialized.js (I, 219)

 assignment (Found 2 resolved, 2 installed, 5 depended. Latest 2.2.0.)
   2.0.0
     ~/assignment
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         assignment/assignment.js (S, 508)

   2.2.0
     ~/trunc-html/~/assignment
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         assignment/assignment.js (S, 696)

 bluebird-q (Found 2 resolved, 2 installed, 2 depended. Latest 2.1.1.)
   1.0.3
     ~/artsy-backbone-mixins/~/bluebird-q
       * Dependency graph
<EMAIL_ADDRESS>-> artsy-backbone-mixins@artsy/artsy-backbone-mixins -><EMAIL_ADDRESS>
-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         bluebird-q/index.js (S, 14411)

   2.1.1
     ~/bluebird-q
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         bluebird-q/index.js (S, 16795)

-hoist-non-react-statics (Found 1 resolved, 2 installed, 2 depended. Latest 3.3.0.)
+hoist-non-react-statics (Found 2 resolved, 2 installed, 4 depended. Latest 3.3.0.)

-  3.3.0
+  3.1.0

-    ~/found/~/hoist-non-react-statics
+    ~/react-redux/~/hoist-non-react-statics

       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (I, 2887)
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

+      * Duplicated files in common.10c02c82925d6908b4ee.js

+        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2553)
+
+  3.3.0
+
     ~/react-tracking/~/hoist-non-react-statics
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

-        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (I, 2887)
+        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2887)

-isarray (Found 1 resolved, 1 installed, 3 depended. Latest 0.0.1.)
+isarray (Found 2 resolved, 2 installed, 5 depended. Latest 1.0.0.)

   0.0.1
     ~/isarray
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         isarray/index.js (S, 120)

+  1.0.0
+    ~/buffer/~/isarray
+      * Dependency graph
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.10c02c82925d6908b4ee.js
+        isarray/index.js (S, 132)
+
+
 memoize-one (Found 2 resolved, 2 installed, 2 depended. Latest 5.0.5.)
   4.1.0
     ~/memoize-one
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         memoize-one/dist/memoize-one.esm.js (S, 903)

   5.0.5
     ~/styled-components/~/memoize-one
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         memoize-one/dist/memoize-one.esm.js (S, 922)

 qs (Found 2 resolved, 2 installed, 6 depended. Latest 6.5.2.)
   5.2.0
     ~/artsy-backbone-mixins/~/qs
       * Dependency graph
<EMAIL_ADDRESS>-> artsy-backbone-mixins@artsy/artsy-backbone-mixins -><EMAIL_ADDRESS>
-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         qs/lib/index.js (S, 200)
         qs/lib/parse.js (S, 5363)
         qs/lib/stringify.js (S, 3906)
         qs/lib/utils.js (S, 4319)

   6.5.2
     ~/qs
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.a506dee5ae082d775809.js
+      * Duplicated files in common.10c02c82925d6908b4ee.js

         qs/lib/index.js (S, 211)
         qs/lib/parse.js (S, 5817)
         qs/lib/stringify.js (S, 6288)
         qs/lib/utils.js (S, 5554)

-redux (Found 2 resolved, 2 installed, 3 depended. Latest 4.0.4.)
+redux (Found 2 resolved, 3 installed, 9 depended. Latest 4.0.1.)

-  4.0.1
+  3.6.0

-    ~/farce/~/redux
+    ~/redux

       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.10c02c82925d6908b4ee.js

-      * Duplicated files in common.a506dee5ae082d775809.js
+

-        redux/es/redux.js (S, 23104)

+  4.0.1

-  4.0.4
+    ~/farce/~/redux

-    ~/found/~/redux
-
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in common.a506dee5ae082d775809.js
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-        redux/es/redux.js (S, 24037)
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-## misc.1f13f902c0a12efee5a2.js
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-hoist-non-react-statics (Found 3 resolved, 3 installed, 5 depended. Latest 3.3.0.)
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-  2.5.5
+      * Duplicated files in common.10c02c82925d6908b4ee.js

-    ~/hoist-non-react-statics
+        redux/es/redux.js (I, 23104)

-      * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+    ~/found/~/redux

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in misc.1f13f902c0a12efee5a2.js
-        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2073)
-
-  3.1.0
-    ~/react-redux/~/hoist-non-react-statics
-
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in misc.1f13f902c0a12efee5a2.js
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2553)
+      * Duplicated files in common.10c02c82925d6908b4ee.js

+        redux/es/redux.js (I, 23104)

-  3.3.0

-    ~/formik/~/hoist-non-react-statics
+## misc.d6d9529dea8f6a6bdb23.js

-      * Dependency graph
+hoist-non-react-statics (Found 2 resolved, 2 installed, 4 depended. Latest 3.3.0.)

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+  2.5.5

-      * Duplicated files in misc.1f13f902c0a12efee5a2.js
+    ~/hoist-non-react-statics

-        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2887)
-
-## order.ddd6790c8fd851918461.js
-farce (Found 2 resolved, 2 installed, 3 depended. Latest 0.2.8.)
-  0.2.6
-    ~/farce
-
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-      * Duplicated files in order.ddd6790c8fd851918461.js
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-        farce/lib/StateStorage.js (S, 2102)
+      * Duplicated files in misc.d6d9529dea8f6a6bdb23.js

+        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2073)

-  0.2.8

-    ~/found-scroll/~/farce
+  3.3.0

-      * Dependency graph
+    ~/formik/~/hoist-non-react-statics

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in order.ddd6790c8fd851918461.js
-        farce/lib/StateStorage.js (S, 1906)
-
-## search2.38dec9e63246565b3f9d.js
-farce (Found 2 resolved, 2 installed, 3 depended. Latest 0.2.8.)
-  0.2.6
-    ~/farce
-
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in misc.d6d9529dea8f6a6bdb23.js

-      * Duplicated files in search2.38dec9e63246565b3f9d.js
+        hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2887)

-        farce/lib/StateStorage.js (S, 2102)

-
-  0.2.8
-    ~/found-scroll/~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in search2.38dec9e63246565b3f9d.js
-        farce/lib/StateStorage.js (S, 1906)
-
-## ssr-experiments.2412243c72cb1bfe8f14.js
-farce (Found 2 resolved, 2 installed, 3 depended. Latest 0.2.8.)
-  0.2.6
-    ~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in ssr-experiments.2412243c72cb1bfe8f14.js
-        farce/lib/StateStorage.js (S, 2102)
-
-  0.2.8
-    ~/found-scroll/~/farce
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in ssr-experiments.2412243c72cb1bfe8f14.js
-        farce/lib/StateStorage.js (S, 1906)
-
-
 * Understanding the report: Need help with the details? See:
   https://github.com/FormidableLabs/inspectpack/#diagnosing-duplicates
 * Fixing bundle duplicates: An introductory guide:
   https://github.com/FormidableLabs/inspectpack/#fixing-bundle-duplicates

Fixing bundle duplicates | An introductory guide
@cavvia, @zephraph

auctions.94c594cd4b1657807617.js

acorn (Found 2 resolved, 3 installed, 3 depended. Latest 2.7.0.)

1.2.2
  ~/with/~/acorn
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in auctions.94c594cd4b1657807617.js
      acorn/dist/acorn.js (S, 131402)
      acorn/dist/walk.js (S, 11791)
2.7.0
  ~/jade/~/acorn
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in auctions.94c594cd4b1657807617.js
      acorn/dist/acorn.js (I, 119975)
      acorn/dist/walk.js (I, 13326)
  ~/with/~/acorn-globals/~/acorn
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in auctions.94c594cd4b1657807617.js
      acorn/dist/acorn.js (I, 119975)
      acorn/dist/walk.js (I, 13326)

common.10c02c82925d6908b4ee.js

@babel/runtime (Found 3 resolved, 5 installed, 18 depended. Latest 7.6.0.)

7.1.5
  ~/dom-helpers/~/@babel/runtime
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js

  ~/react-redux/~/@babel/runtime
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      @babel/runtime/helpers/esm/extends.js (I, 397)
      @babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js (I, 350)
  ~/styled-system/~/@babel/runtime
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      @babel/runtime/helpers/esm/extends.js (I, 397)
7.4.5
  ~/@artsy/palette/~/@babel/runtime
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      @babel/runtime/helpers/assertThisInitialized.js (I, 219)
      @babel/runtime/helpers/esm/extends.js (I, 397)
      @babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js (I, 350)
7.6.0
  ~/@babel/runtime
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      @babel/runtime/helpers/assertThisInitialized.js (I, 219)

assignment (Found 2 resolved, 2 installed, 5 depended. Latest 2.2.0.)

2.0.0
  ~/assignment
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      assignment/assignment.js (S, 508)
2.2.0
  ~/trunc-html/~/assignment
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      assignment/assignment.js (S, 696)

bluebird-q (Found 2 resolved, 2 installed, 2 depended. Latest 2.1.1.)

1.0.3
  ~/artsy-backbone-mixins/~/bluebird-q
    * Dependency graph
<EMAIL_ADDRESS>-> artsy-backbone-mixins@artsy/artsy-backbone-mixins -><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      bluebird-q/index.js (S, 14411)
2.1.1
  ~/bluebird-q
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      bluebird-q/index.js (S, 16795)

hoist-non-react-statics (Found 2 resolved, 2 installed, 4 depended. Latest 3.3.0.)

3.1.0
  ~/react-redux/~/hoist-non-react-statics
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2553)
3.3.0
  ~/react-tracking/~/hoist-non-react-statics
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2887)

isarray (Found 2 resolved, 2 installed, 5 depended. Latest 1.0.0.)

0.0.1
  ~/isarray
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      isarray/index.js (S, 120)
1.0.0
  ~/buffer/~/isarray
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      isarray/index.js (S, 132)

memoize-one (Found 2 resolved, 2 installed, 2 depended. Latest 5.0.5.)

4.1.0
  ~/memoize-one
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      memoize-one/dist/memoize-one.esm.js (S, 903)
5.0.5
  ~/styled-components/~/memoize-one
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      memoize-one/dist/memoize-one.esm.js (S, 922)

qs (Found 2 resolved, 2 installed, 6 depended. Latest 6.5.2.)

5.2.0
  ~/artsy-backbone-mixins/~/qs
    * Dependency graph
<EMAIL_ADDRESS>-> artsy-backbone-mixins@artsy/artsy-backbone-mixins -><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      qs/lib/index.js (S, 200)
      qs/lib/parse.js (S, 5363)
      qs/lib/stringify.js (S, 3906)
      qs/lib/utils.js (S, 4319)
6.5.2
  ~/qs
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      qs/lib/index.js (S, 211)
      qs/lib/parse.js (S, 5817)
      qs/lib/stringify.js (S, 6288)
      qs/lib/utils.js (S, 5554)

redux (Found 2 resolved, 3 installed, 9 depended. Latest 4.0.1.)

3.6.0
  ~/redux
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js

4.0.1
  ~/farce/~/redux
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      redux/es/redux.js (I, 23104)
  ~/found/~/redux
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.10c02c82925d6908b4ee.js
      redux/es/redux.js (I, 23104)

misc.d6d9529dea8f6a6bdb23.js

hoist-non-react-statics (Found 2 resolved, 2 installed, 4 depended. Latest 3.3.0.)

2.5.5
  ~/hoist-non-react-statics
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in misc.d6d9529dea8f6a6bdb23.js
      hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2073)
3.3.0
  ~/formik/~/hoist-non-react-statics
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in misc.d6d9529dea8f6a6bdb23.js
      hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (S, 2887)


test get-currentexe fails on AIX

On v1.x the get-current-exe test fails on AIX:
-bash-4.2$ ./out/Debug/run-tests
...
[%  58|+ 154|-   5|T   0|S   0]: get_currentexe
`get_currentexe` failed: exit code 393350
Output from process `get_currentexe`:
Assertion failed: __EX, file  ../src/unix/aix.c, line 340
=============================================================

It looks like it's failing in the size=1 part of the test that was added by 885b1ecda0037fcb6647e8d69a914347ad884244.
I'm actually running these tests prior to submitting a pull request to address an issue with uv_execpath and relative paths on AIX. If I comment out the  size=1 and size=2 cases then the test passes:
-bash-4.2$ ./out/Debug/run-tests get_currentexe get_currentexe
-bash-4.2$

but not if I run the test like this (this is the problem I was originally intending to fix):
-bash-4.2$ ../libuv/out/Debug/run-tests get_currentexe get_currentexe
Assertion failed in ../test/test-get-currentexe.c on line 53: match && !strcmp(match, path)
IOT/Abort trap (core dumped)
-bash-4.2$

(n.b. I had to invoke with get_currentexe twice on the command line to induce the failure -- I believe the tests are spawned slightly differently in the no argument/single argument cases).
I'll look to address these failures in my pull request.

For completeness, without any modifications:
Absolute path to run-tests (assertion fails at same line as running run-tests in no argument/single argument case):
-bash-4.2$ /home/users/riclau/sandbox/github/libuv/out/Debug/run-tests get_currentexe get_currentexe
Assertion failed: __EX, file  ../src/unix/aix.c, line 340
IOT/Abort trap (core dumped)
-bash-4.2$

Relative path to run-tests:
-bash-4.2$ out/Debug/run-tests get_currentexe get_currentexe
Assertion failed: __EX, file  ../src/unix/aix.c, line 394
IOT/Abort trap (core dumped)
-bash-4.2$

Relative path to run-tests starting with single "./":
-bash-4.2$ ./out/Debug/run-tests get_currentexe get_currentexe
Assertion failed: __EX, file  ../src/unix/aix.c, line 371
IOT/Abort trap (core dumped)
-bash-4.2$

Relative path to run-tests with "../":
-bash-4.2$ ../libuv/out/Debug/run-tests get_currentexe get_currentexe
Assertion failed in ../test/test-get-currentexe.c on line 53: match && !strcmp(match, path)
IOT/Abort trap (core dumped)
-bash-4.2$

As before I'll look to address all of these.

Fixed by #464.


No experiment and data files for dataset fce97270-fce0-4744-8a4e-a93d95521852 in ENA

@ke4 has submitted the new replacement FASTQ files for this dataset (fce97270-fce0-4744-8a4e-a93d95521852) to ENA and asked to suppress the old BAM files.
ENA help desk accidentally suppressed the data in experiment level. @ke4 contacted with them and they are going to fix this issue and contact with @ke4 when they are ready.
This is the project link in ENA: https://www.ebi.ac.uk/ena/browser/view/PRJEB31821

Reply from ENA help desk:
Dear Karoly,
Thanks for contacting me via Slack about this suppression. Apologies for our
oversight in suppressing the Experiments here.
As I explained over slack - suppressing raw data via the experiment is
standard procedure as most runs are tightly coupled with experiments in a 1-1
ratio. However, we recognise that there are exceptions to this where multiple
runs are associated with the same experiment (like has been done here) and
this should have been identified prior to suppression - apologies for not
addressing this in this case.
I have marked the following Experiments and Runs for re-release (the set does
not include the runs that were requested to be suppressed in your email
below). Please review these accessions and let me know if you have any further
concerns:
ERR7124931 - ERX3266488
ERR7124932  - ERX3266487
ERR7124933 - ERX3266486
ERR7124934 - ERX3266489
ERR7124935 - ERX3266490
ERR7124936 - ERX3266491
These should become public again in the next 48 hours.
Best wishes,
Josie

My reply to ENA help desk:
Dear Josie,
I double checked and I can confirm that the above experiments and runs you listed in your email are the correct one to re-release.
On 1 Nov 2021, at 11:05, Josephine Burgin via RT<EMAIL_ADDRESS>wrote:
ERR7124931 - ERX3266488
ERR7124932  - ERX3266487
ERR7124933 - ERX3266486
ERR7124934 - ERX3266489
ERR7124935 - ERX3266490
ERR7124936 - ERX3266491
Many thanks for your extremely quick help.
Have a nice day,
Karoly

tl;dr: @ke4 was in contact, there was an error, runs will re-appear in ~48 hours. Waiting on ENA.

Runs have been re-released, moving to done :)


Issues with SharePoint "Read" privilege with Client App

I'm working on a classic ASP page with VBScript API calls and I can't seem to read files from SharePoint Online(SPO) folders even though I can do it via the browser. I am not an admin and I do have access to read the files through the browser. Can you advise on the best approach.
This a copy of the code I'm using, it returns error 403: ACCESS DENIED:
        Dim restReq, url
        'create a JSON request object to interact with Sharepoint
        Set restReq = CreateObject("Msxml2.XMLHTTP")
        restReq.async = false
       url = "http://<tenant url>.sharepoint.com/sites/_api/web/GetFolderByServerRelativeUrl('/Shared Documents')"
        '  Indicate that we want a XML+ATOM reply
          restReq.Accept = "application/atom+xml"

        'make the API call to sharepoint by opening the endpoint and making the call, in this case to check if a file exist in the specified folder
        call restReq.open ("GET", url, false)
        call restReq.send()

        response.write(restReq.status)
        response.write(restReq.responseText)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 71e8ee66-fe7c-a46e-eeec-fb199962042c
Version Independent ID: f78aef17-5aa2-8807-73d4-509faecbd153
Content: Connect your client-side web part to SharePoint (Hello World part 2)
Content Source: docs/spfx/web-parts/get-started/connect-to-sharepoint.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

I feel like you are missing the entire auth flow here...

To expand on what Pat is saying, is it looks like you are just trying to execute a request to SharePoint Online, but you haven't authenticated yet. You will need to register this application with SharePoint, in order to request a token to execute requests against SharePoint.
However, I have another concern. If you do not have access to view the files via the Browser. Your application also will not have access to read those files as it would execute under your permissions.

Please see the response I left for your other issue #3681

Thanks for your feedback. I do have read access to the folders via the web browser and I am not the administrator. I will take a look at the links to get a better feel of how to authenticate and revert back if I’m still facing problems.
I would also like to know if the authentication methods exist in vb scripts running in classic asp....

I've never seen code samples for authenticating using OAuth and obtaining an access token for VBScript with classic ASP. You can do it, but never seen scripts for it nor are their libraries published by Microsoft.


Converts columns from NULL to NOT NULL DEFAULT

depends on #18868 and #18869
This PR converts columns from NULL to NOT NULL DEFAULT. This should concern only the tests because the fixtures insert NULL values. The usual xorm.Inserts do not insert NULL values for int and bool.

Codecov Report

Merging #18871 (de70352) into main (1546580) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #18871      +/-   ##
==========================================
- Coverage   46.60%   46.58%   -0.03%
==========================================
  Files         854      854
  Lines      122891   122891
==========================================
- Hits        57271    57243      -28
- Misses      58701    58734      +33
+ Partials     6919     6914       -5

Impacted Files
Coverage Δ

models/issue.go
53.84% <ø> (ø)

models/issue_label.go
65.05% <ø> (ø)

models/issue_milestone.go
67.62% <ø> (ø)

models/org_team.go
54.33% <ø> (ø)

models/repo/attachment.go
50.33% <ø> (ø)

models/repo/repo.go
63.04% <ø> (ø)

models/repo/topic.go
61.53% <ø> (ø)

models/user/user.go
57.97% <ø> (ø)

modules/queue/queue_bytefifo.go
46.90% <0.00%> (-5.46%)
:arrow_down:

modules/charset/charset.go
69.74% <0.00%> (-4.21%)
:arrow_down:

... and 13 more

Continue to review full report at Codecov.

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

I checked the models in the migration just now. Changes are still valid.

conflicted.

Yes this can be done using alter table set default and alter table set not null for all databases except sqlite3

@lunny Looks like xorm.ColumnString generates an invalid command for mssql. In this case it's ALTER TABLE [label] ALTER COLUMN [num_issues] INT DEFAULT 0 NOT NULL.

blocking as recreating whole database is not feasable for big instances like...
gitea.com, codeberg.org, ...

I would against about this point. Gitea is not only for codeberg, it's for everyone.
In history, Gitea (gogs)'s code base is not ideal, there will be a lot of refactoring to make Gitea more "right". One instance should not be the blocker for a general purpose project.
For the people who need to customize Gitea a lot, they could alter the database without downtime ahead and skip the migration manually.

I would against about this point. Gitea is not only for codeberg, it's for everyone.
In history, Gitea (gogs)'s code base is not ideal, there will be a lot of refactoring to make Gitea more "right". One instance should not be the blocker for a general purpose project.
For the people who need to customize Gitea a lot, they could alter the database without downtime ahead and skip the migration manually.

But why do you think that there could not be other large private instances?

I would against about this point. Gitea is not only for codeberg, it's for everyone.
In history, Gitea (gogs)'s code base is not ideal, there will be a lot of refactoring to make Gitea more "right". One instance should not be the blocker for a general purpose project.
For the people who need to customize Gitea a lot, they could alter the database without downtime ahead and skip the migration manually.

But why do you think that there could not be other large private instances?

There could be, IMO they could either take a downtime or apply the changes manually?

Although I think it's good to make the database columns more strict, for this PR I have some worries (I haven't thought about these problems carefully, just questions):

Does it need a full test for all databases to make sure the migration works well?
Does the x.Exec("UPDATE ... need to be merged into one UPDATE SET col1=...,col2=... to speed up for large tables?
Does the DEFAULT false or UPDATE SET col=false(default) work for all databases? IIRC XORM does some tricks for bool/true/false

One more question, if this PR is mainly for tests and difficult to make the migration clear, could there be an alternative approach to only make tests correct while keeping the database structure unchanged?

Does it need a full test for all databases to make sure the migration works well?

How would a "full test" look like?

Does the x.Exec("UPDATE ... need to be merged into one UPDATE SET col1=...,col2=... to speed up for large tables?

That's "not" possible because of the WHERE statement (should not update col1 if col2 is null). A different solution could be col1 = ISNULL(...) but I don't know if that's better or supported.

Does the DEFAULT false or UPDATE SET col=false(default) work for all databases? IIRC XORM does some tricks for bool/true/false

We already have lots of DEFAULT false/true statements so I think that works?!

One more question, if this PR is mainly for tests and it's difficult to make the migration clear, could there be an alternative approach to only make tests correct while keeping the database structure unchanged?

Sure, we would have to add all fields to the fixtures (or enforce default values somehow). Then there would be no change to the database which is a pro or a con...?

Does it need a full test for all databases to make sure the migration works well?

How would a "full test" look like?

Just a question, not sure whether "tests/integration/migration-test" covers all cases.

Does the DEFAULT false or UPDATE SET col=false(default) work for all databases? IIRC XORM does some tricks for bool/true/false

We already have lots of DEFAULT false/true statements so I think that works?!

I recalled some reviews mentioned that "do not write col=true/false" because it would cause broken SQL, I am not sure whether it's a real problem, so just ask the question.

One more question, if this PR is mainly for tests and it's difficult to make the migration clear, could there be an alternative approach to only make tests correct while keeping the database structure unchanged?

Sure, we would have to add all fields to the fixtures (or enforce default values somehow). Then there would be no change to the database which is a pro or a con...?

Just a thought, maybe there could be some "default fixtures" during testing, which contains all default values for the fields, then all loaded fixtures first get filled by default fixtures, then load the real fixture data.

@lunny Looks like xorm.ColumnString generates an invalid command for mssql. In this case it's ALTER TABLE [label] ALTER COLUMN [num_issues] INT DEFAULT 0 NOT NULL.

Is this a bug of xorm?

Does the x.Exec("UPDATE ... need to be merged into one UPDATE SET col1=...,col2=... to speed up for large tables?

That's "not" possible because of the WHERE statement (should not update col1 if col2 is null). A different solution could be col1 = ISNULL(...) but I don't know if that's better or supported.

Since most columns do not have an index, so most UPDATE will be a full-table scan. So the all-in-one UPDATE might be: UPDATE ... SET col1=COALESCE(col1, DefaultValue), ....

It's safer to update all NULL values to non NULL values before change the columns to NOT NULL, otherwise it will fail when upgrading.

It's safer to update all NULL values to non NULL values before change the columns to NOT NULL, otherwise it will fail when upgrading.

Yup, that's what this PR has done, first UPDATE, then modifyColumns

Hmm ..... after some more thinking, my personal conclusion at the moment is:

I support for making database structure strict if it's very very necessary.
For tests, the fixtures could be fixed by adding missing fields (although it needs some work)
If this PR is only for test purpose, maybe we can leave it until there is a more strong requirement for it, because this PR only adds "NOT NULL" to some columns. If we take it, in the future, maybe another similar PR will appear to add more "NOT NULL" for other columns, which is pretty annoying ....

So I would propose to leave this PR as it is, fix the fixtures for  Add some api integration tests #18872  manually. I could also help if it's needed.

@KN4CK3R are you currently working on this? we can close this PR.

Not working on this because it was finished back then. It's still relevant but not an easy migration for existing large instances.

Any forward plans for this. As piece by piece migration.


AWQ quantization is very slow for ONNX LLMs

I'm not sure if I'm missing an option somewhere, but AWQ quantization for large ONNX models is very slow. When quantizing a 7B LLaMA model, the 4 following np.matmul calls take forever to execute, and I estimate it would take days to quantize the model at current pace:
https://github.com/intel/neural-compressor/blob/26b260e174cac13b023a11caab372b2dcdc593e0/neural_compressor/adaptor/ox_utils/weight_only.py#L466
https://github.com/intel/neural-compressor/blob/26b260e174cac13b023a11caab372b2dcdc593e0/neural_compressor/adaptor/ox_utils/weight_only.py#L488
https://github.com/intel/neural-compressor/blob/26b260e174cac13b023a11caab372b2dcdc593e0/neural_compressor/adaptor/ox_utils/weight_only.py#L615
https://github.com/intel/neural-compressor/blob/26b260e174cac13b023a11caab372b2dcdc593e0/neural_compressor/adaptor/ox_utils/weight_only.py#L636
Would it make sense to allow the user to pass either a torch module or an ONNX model/session to compute the loss (or at the very least do the matmul computation)? Even replacing the np.matmul calls with simple torch.matmul calls on CUDA devices makes it exponentially faster.
Otherwise, is there a current workaround or option I'm unaware of at the moment that would make it faster? I feel like I might be missing something.

It takes about 1 hour to run AWQ quantization on Llama-2-7b model with our test device using scripts in our llama weight-only quantization example. You can refer to the options for AWQ in main.py#L325-L336.
We currently have no plans to support torch tensor computation in our ONNX weight-only quantization. However, we recommend considering alternative solutions using CuPy instead of numpy for GPU-accelerated computing. You can try to implement this method yourself.


Deployment Docs (was: Installing Volto with zeocluster and multiple clients?)

Hi,
how can I install volto with multiple clients and zeocluster?

@TBCcrash2064 to avoid CORS issues we usually deploy both frontend and backend under the same domain.
The frontend is deployed via NGINX under e.g. www.plone.org (Port 80 -> 8080 Plone instance, varnish, haproxy, etc).
The backend is deployed via NGINX under the same domain with an "/api" suffix, e.g. www.plone.org/api (Port 80 -> 3000 Volto default).
We run Volto via pm2 and also Plone (switching from supervisor).
Let me know if you need more info, we are happy to share our prod config. We will also document this during the Beethoven sprint in Bonn next week.

More info: https://community.plone.org/t/volto-deployment-options/7458/8

https://training.plone.org/5/plone-deployment/index.html
https://6.dev-docs.plone.org/volto/deploying/index.html


Check even or  odd in cpp

To check even or odd

Hi can you please assign this to me?

Assign me this task @GeshnaSikarwar


Variant in CASP9 can't be found by rsID search

Works if you search by the variant
http://exac.broadinstitute.org/variant/1-15832495-T-G
Although the variant is listed correctly as rs146054764, a search by the rsID returns no results

Fixed in most recent commit.


Implement mdc-image-list

What vue-mdc-adapter Version are you using?

0.13.5

Implement mdc-image-list

MDC image list is only CSS classes, nothing to implement


Graphical "Glitches" with QT_SCALE_FACTOR set

Describe the bug
I have set the QT_SCALE_FACTOR environmental variable to increase the menu size of qt applications (Lyx).
export QT_SCALE_FACTOR=1.3
While Lyx is compatible with this option, VisIt's graphical interface "glitches" as the mouse hovers over, making it unusable.
To Reproduce

Open a terminal
export QT_SCALE_FACTOR=1.3
run visit

Expected behavior
I expect the VisIt user interface to open with larger text with the ability to click on menu items.

OS and version: Linux Mint 21
VisIt Version: 3.3.3 and 3.3.1
Qt version 5.15.2, but I don't know if this matters.

Additional context
This is such a minor bug, in my opinion, because of the innate font customization, and I can just unset the QT_SCALE_FACTOR before running VisIt. However, this information may help someone struggling to get visit to run.

We should unset QT_SCALE_FACTOR in our launcher script.


add retry to rebuild-images

This change adds an interactive retry capability to the OIT refresh-images task.
The form of this change comes from the build stage of the ocp Jenkinsfile.
This change also includes some re-formatting of the groovy code for clarity.

@markllama Aside from those minor concerns, nice work on the reformatting. Much easier to read :)


[feature/RPA-948] Block editing/deleting process for other than admin and owner

Description

DONE:

block editing process details in the modal except for admin and process owner
block process deletion except for admin and process owner
hide the CONFIGURE tab of public processes except for admin and process owner

Motivation and Context

Types of changes

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

I agree to the terms of the RunBotics Contributor License Agreement.

What is the purpose of making oprtion "Edit" available to click if there is nothing we can edit in modal? 😃 I think it should be greyed out just like the delete button.


[TODO] Add Notification widget/feature

Right now, the app has a Notification icon in the topnav bar.
It doesn't do anything at all.
Create a Notification widget or feature that opens from the Bell icon.
We are using mui

Here is some notification ideas:
New book releases: Notify users when a new book by their favorite author or in a genre they are interested in is released.
Recommendations based on reading preferences: Send personalized book recommendations to users based on their reading history, favorite genres, or authors they like to read.
Reading progress updates: Allow users to set reading goals and send notifications to track their progress or remind them to continue reading.
Book club updates: If your app includes a book club feature, send notifications about upcoming meetings, discussions, or new book selections.
Reviews and ratings: Notify users when someone comments on their book reviews or when a book they reviewed receives a new review.
Wishlist updates: If users have added books to their wishlist or bookshelf, send notifications when those books go on sale or when there are updates or news related to those books.
App updates and new features: Inform users about new features, improvements, or bug fixes in  the app.

@BlackBond06 @LOGESH-B ideas?


Exceptions propagated by check don't adhere to ArgumentMatcher contract

ArgumentMatcher.matches must not throw an exception.  The current implementation of check violates this - exceptions thrown in the user-supplied lambda are propagated out of the ArgumentMatcher lambda that is constructed and passed to argThat.  This leads to issues (see this Stack Overflow question for an example).
I'm happy to submit a PR that wraps the call to predicate in a try-catch that returns false on an exception, if you think that's an appropriate fix 😄

, if you think that's an appropriate fix

Actually, I do not, as this would 'swallow' the assertion messages :sweat_smile:

The method should never assert if the argument doesn't match. It should only return false.

This slipped by me, thanks! I'll have to look into this a bit more, probably to find a way not using argThat for this.

This has been bugging me for quite a while now and I'm starting to wonder what the use of check is. Is it to check the supplied arguments like kotlins check does? Or does it have another function?


Improve MTU on Windows

#6 introduces MTU but just uses the default 20 bytes. We should read from the OS and/or negotiate the maximum.

Fixed in #6


Use exponential

This is an oversight forgotten in #491:
qcheck-core.0.23 includes an upstreamed Gen.exponential combinator (from STM even) - so we should then use it.

All 31 workflows green - merging

The merge to main triggered one error:

Linux trunk debug triggered an assertion error in src/weak/lin_tests_hashset.ml #493

Out of 32 workflows, 31 passed and 1 triggered a genuine error


[Reveal] Issues with Multiple Reveal Modals

How can we reproduce this bug?
Open multiple reveal modals so one is displayed in front of the other.
Case 1: Click outside both modals and press the escape key.  Both modals are closed instead of just one.
Case 2: After the page loads, press the escape key to close the first modal.  Then click outside the second modal and press escape.  Nothing happens.
Case 3: Close the first modal.
What did you expect to happen?
Case 1: I expected only the top modal to close.
Case 2: I expected the second modal to close.
Case 3: I expected the is-reveal-open class to remain on the body.
What happened instead?
Case 1: Both modals were closed.
Case 2: The second modal did not close.  The keydown.zf.reveal event was removed from the window object after the first modal was closed.
Case 3: The is-reveal-open class was removed from the body.
Test case:
http://codepen.io/anon/pen/Mbzydx

I looked around but I do not know the Reveal enough to solve this issue.
Case 1: We must remember the "front" Reveal (the latest opened) and close only it at js/foundation.reveal.js:317.
Case 2: We stop listening on ESC pressing at js/foundation.reveal.js:394 when the first modal is closed.
Case 3: Case 2: We remove the class from body at js/foundation.reveal.js:406 when the first modal is closed.
@brettsmason I will need your help on this ;)

@brettsmason Would you have some time to take a look at this issue ?

@ncoden sorry missed this. I'll try and take a look later, though it may require someone with more JS skills

Ah sorry, I have you in mind for the Reveal, I probably mistaken it for Off Canvas. 🤔

Just had a quick look - I think this will require a JS person, sorry 😄
Yeah could probably of helped it was off canvas 😉

@kball do you still plan to work on a solution?


confd is not updating the mode

output from confd - each time it runs it says it's fixing the mode:
Sep 10 19:18:58 ip-172-31-29-203.ec2.internal docker[26415]: 2015-09-10T19:18:58Z ecdce67d049b confd[1]: INFO /etc/confd/output/freeipa.pem has mode -rw-r--r-- should be -rw-------
Sep 10 19:18:58 ip-172-31-29-203.ec2.internal docker[26415]: 2015-09-10T19:18:58Z ecdce67d049b confd[1]: INFO Target config /etc/confd/output/freeipa.pem out of sync
Sep 10 19:18:58 ip-172-31-29-203.ec2.internal docker[26415]: 2015-09-10T19:18:58Z ecdce67d049b confd[1]: INFO Target config /etc/confd/output/freeipa.pem has been updated
Sep 10 19:19:18 ip-172-31-29-203.ec2.internal docker[26415]: 2015-09-10T19:19:18Z ecdce67d049b confd[1]: INFO /etc/confd/output/freeipa.pem has mode -rw-r--r-- should be -rw-------
Sep 10 19:19:18 ip-172-31-29-203.ec2.internal docker[26415]: 2015-09-10T19:19:18Z ecdce67d049b confd[1]: INFO Target config /etc/confd/output/freeipa.pem out of sync
Sep 10 19:19:18 ip-172-31-29-203.ec2.internal docker[26415]: 2015-09-10T19:19:18Z ecdce67d049b confd[1]: INFO Target config /etc/confd/output/freeipa.pem has been updated
Spec:
[template]
prefix = "/bitnet.io/ssh/private"
keys = [
"/freeipa.pem"
]
owner = "root"
mode = "0600"
src = "freeipapem.tmpl"
dest = "/etc/confd/output/freeipa.pem"

This is happening when I'm writing to a mounted file (docker run ... -v /root/freeipa.pem:/etc/confd/output/freeipa.pem)

Looked into this, but wasn't able to reproduce. It could be the case that there were bugs present that are gone now.
Here's how I tried to reproduce:
Environment
Docker
$ docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.3
 Git commit:   a34a1d5
 Built:        Fri Nov 20 17:56:04 UTC 2015
 OS/Arch:      linux/amd64

Docker Commandline
docker run -it --rm  --net=host -v /root/conffiles:/tmp confd

Confd (built from HEAD)
$ confd version
confd 0.12.0-dev

Confd config/templates
[template]
src = "myconfig.conf.tmpl"
dest = "/tmp/myconfig.conf"
keys = [
  "/myapp/database/url",
    "/myapp/database/user",
    ]

owner = "root"
mode = "0600"

# This a comment
[myconfig]
database_url = {{ getv "/myapp/database/url" }}
database_user = {{ getv "/myapp/database/user" }}

Before etcd triggered confd change
 $ ls -lash ~/conffiles/myconfig.conf
4.0K -rwxrwxrwx 1 root root 75 Feb 22 23:00 /root/conffiles/myconfig.conf

After confd  change
$ ls -lash ~/conffiles/myconfig.conf
4.0K -rw------- 1 root root 80 Feb 22 23:24 /root/conffiles/myconfig.conf

Confd Output
2016-02-23T04:24:46Z test /confd[12]: INFO /tmp/myconfig.conf has mode -rwxrwxrwx should be -rw-------
2016-02-23T04:24:46Z test /confd[12]: INFO /tmp/myconfig.conf has md5sum 3a177041dab7f872cb21e1ce76b09406 should be 93756e744ff7dd9cc06fd7581567957a
2016-02-23T04:24:46Z test /confd[12]: INFO Target config /tmp/myconfig.conf out of sync
2016-02-23T04:24:46Z test /confd[12]: INFO Target config /tmp/myconfig.conf has been updated

Could you try recreating this bug with the latest and greatest? (newer Docker, confd, et al)

@elsonrodriguez Thanks for taking a look at this. I was not able to repo this issue as well, but my guess is that the later version of Docker or golang make this work.

Thanks, That project finished a while ago for me, so it's not still an outstanding issue on my side.


snapshots & rev-ups over request-response

Peer-to-peer comms don't have to use the pubsub system, which can also be rate- and size-limited.
WebRTC might be an option.

Experimental WebRTC support available in m-ld-js v0.6.0. Further work will be new tickets


Add support for multiple long and short options in custom commands

I found this Gist to be helpful. It explains how to support both long and short options in Bash scripts. I have successfully written code that is based on it.
https://gist.github.com/cosimo/3760587

It looks like I'll get this done in the process of converting everything to Python.


Package.loadSettings is deprecated.

Store package settings files in the settings/ directory instead of scoped-properties/
Package.loadSettings (/Applications/Atom.app/Contents/Resources/app/src/package.js:565:9)
<unknown> (/Applications/Atom.app/Contents/Resources/app/src/package.js:187:43)

Duplicate of #2 obviously, but +1, using Atom v0.190

Hi @tomii955 & @JaKXz
Thanks for logging this - I am not able to look at this till next week as I am on vacation.
Will sort it out when I am back.
Cheers
James.

All you need to do is rename the scoped-properties to settings and it should work fine.

Pushed up a fix (d6b88ad59dae1aecf48a862d27f47499d1cc0132) and released an updated package


Build error

Getting the following error, any idea what is going wrong?
Ubuntu server 18.04
root@xxxxxdocker:/srv/www/naples.xxx.xx# docker-compose build
Building nplsweb
Step 1/7 : FROM openjdk:8u171-slim
---> 60575d4bfe64
Step 2/7 : EXPOSE 8090
---> Using cache
---> 08d45f8454ca
Step 3/7 : VOLUME /tmp
---> Using cache
---> 7c29c9e11e18
Step 4/7 : COPY target/nplsweb-0.0.1-SNAPSHOT.jar app.jar
ERROR: Service 'nplsweb' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder300825816/target/nplsweb-0.0.1-SNAPSHOT.jar: no such file or directory

This looks like a copy problem, coming from the following line in the Dockerfile:
COPY target/nplsweb-0.0.1-SNAPSHOT.jar app.jar
May I ask you what is the folder structure? Are you doing the "docker-compose build" from the directory with the "target" folder? Do you have the nplsweb-0.0.1-SNAPSHOT.jar in the "target" folder?

I maybe should add to the README that the project needs to be compiled before (it was obvious to me, but I recognize this mistake from my part).
As you are running on Ubuntu, you can compile the project to create the target folder and the JAR file by running maven as following: "mvnv clean package"
Please, tell me if this worked for you!

So i run the build command from the resulting target folder then?

No, you need to compile the project with Maven (to create the "target" folder) and then, still from the root folder, where you have the "target", "archive" etc folders and the Docker files, you run the "docker-compose build" and once it's built the "docker-compose up -d" command

@mSorok the error on the missing inchiPet.jar is correct. That file is not actually in the target folder. Ive added it to the root of my project (like you did in NPdatabasefiller) and change the dockerfile accordingly. So you might want to change that for the web project too.

Thank you for the comment! I changed the Dockerfile instead, to copy the inchiPet.jar in the root directory


update nuget.exe to <IP_ADDRESS>79

We need an updated nuget.exe if we want to use it to push packages

@dotnet-bot test this please

@brettfo @KevinRansom We should do this update at some point, but it currently fails with this.  I think we can do this update after the final project.json files have been removed
   Invalid input 'project.json'. Provide the path of an msbuild solution file instead. Support for XProj and standalone project.json files has been removed, to continue working with legacy projects use NuGet 3.5.x from https://nuget.org/downloads
D:\j\w\release_ci_pa---3f142ccc\Tools\packageresolve.targets(35,5): error MSB3073: The command ""D:\j\w\release_ci_pa---3f142ccc\src\fsharp\Fsc\..\..\..\.nuget\NuGet.exe" restore -OutputDirectory "D:\j\w\release_ci_pa---3f142ccc\packages" -Config "D:\j\w\release_ci_pa---3f142ccc\src\fsharp\Fsc\..\..\..\.nuget\..\NuGet.Config" "D:\j\w\release_ci_pa---3f142ccc\src\fsharp\Fsc/project.json"" exited with code 1. [D:\j\w\release_ci_pa---3f142ccc\src\fsharp\Fsc\Fsc.fsproj]

@brettfo Actually looks like we might just have project.json files still lying around the tree unnecessarily? can we remove them, e.g. in src/fsharp/Fsc?

The ones under src/fsharp are still necessary, but that's what I'm currently working on; updating everything under src/fsharp to be SDK-based.  It's not yet ready, but I'm hoping to send this out for review sometime this week.  Spoiler alert, it's a net removal of 13k lines of XML.
https://github.com/Microsoft/visualfsharp/compare/master...brettfo:fsc-sdk-2


Some of the relations links are returning 404

The following 3 links in the relations section are returning a 404.

https://www.prisma.io/docs/concepts/components/prisma-schema/relations/one-to-many-relations
https://www.prisma.io/docs/concepts/components/prisma-schema/relations/many-to-many-relations
https://www.prisma.io/docs/concepts/components/prisma-schema/relations/self-relations

I can access to those pages.

Same here. Can you share a screenshot of the 404 you are getting please @shmuelsochet?

I have access now. It looks like it was due to a filter setting.
Here's the page I was getting


Add newest RDKit version and remove oldest and tested with pytest

Checklist:

[x] Was this PR discussed in a issue? It is recommended to first discuss a new feature into a GitHub issue before opening a PR.
[x] Add tests to cover the fixed bug(s) or the new introduced feature(s) (if appropriate).
[x] Update the API documentation is a new function is added or an existing one is deleted.
[x] Added a news entry.

copy news/TEMPLATE.rst to news/my-feature-or-branch.rst) and edit it.

Why do we remove 2022.03? It seems like there's no changes to Datamol that break compatibility with 2022.03, right?

Out of curiosity: Why do we remove 2022.03? It seems like there's no changes to Datamol that break compatibility with 2022.03, right?

Good question. The answer is to not blow up the CI matrix. The current strategy is to test only on the two latest rdkit versions and the 3 last python ones and all the 3 main platforms (win, linux, osx).
For that reason, the doc limits the "compatibility promise" to only the two latest rdkit versions, but it does not mean it won't work. Simply that it's not tested anymore.
We have the below in the doc:

See below the associated versions of Python and RDKit, for which a minor version of Datamol has been tested during its whole lifecycle. It does not mean other combinations does not work but that those are not tested.

Thanks, @dessygil, for the help here!

@hadim, the new rdkit canvas based drawing seems nice. I think we should try to eventually refactor some existing viz like radialscope and circlegrid for latent embeddings, as well as think about new ones (e.g progression of a series or scaffold during optimization)

@hadim, the new rdkit canvas based drawing seems nice. I think we should try to eventually refactor some existing viz like radialscope and circlegrid for latent embeddings, as well as think about new ones (e.g progression of a series or scaffold during optimization)

All for it. I always wanted to refactor the viz module to make it more modular and easy to setup complex viz. Maybe an OO approach would be suited here.

Hey @maclandrol and @hadim, Could I take this issue as well?

Maybe we can open an issue to plan a little? I haven't looked into this in detail, but it seems like a big refactoring.

Hey @maclandrol and @hadim, Could I take this issue as well?

That one might be a bit tricky simply because we don't know yet what we want to do exactly. @dessygil feel free to open an issue, so we can brainstorm there. I am all good if you want to start exploring this in a PR, but I can't guarantee it will end up being merged as it's too early at the moment.

We will likely need to explore the new functionality first. I haven't hard the time to try that and see the limitation, but looking at the snippet in the rdkit blog, it looks a lot more principled compared to dealing with PIL or composing an SVG. We should brainstorm first IMO.

For sure, is there anything else that I could take on in the meantime?


Feature - Add extension to support max apk size

@vanniktech Solves #48
Add extension to support max apk size

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a4f02a1). Click here to learn what that means.
The diff coverage is 62.5%.

@@            Coverage Diff            @@
##             master      #49   +/-   ##
=========================================
  Coverage          ?   55.81%
  Complexity        ?       10
=========================================
  Files             ?        3
  Lines             ?       43
  Branches          ?        3
=========================================
  Hits              ?       24
  Misses            ?       15
  Partials          ?        4

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 a4f02a1...484f982. Read the comment docs.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a4f02a1). Click here to learn what that means.
The diff coverage is 62.5%.

@@            Coverage Diff            @@
##             master      #49   +/-   ##
=========================================
  Coverage          ?   55.81%
  Complexity        ?       10
=========================================
  Files             ?        3
  Lines             ?       43
  Branches          ?        3
=========================================
  Hits              ?       24
  Misses            ?       15
  Partials          ?        4

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 a4f02a1...484f982. Read the comment docs.

It was mixed in some areas, I was just trying to make it consistent.
On Mar 6, 2017 3:05 AM, "Niklas Baudy"<EMAIL_ADDRESS>wrote:

@vanniktech commented on this pull request.
Any reason for changing all the quotes as well as the parenthesis?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vanniktech/gradle-android-apk-size-plugin/pull/49#pullrequestreview-25223749,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqMSBHoKZjL4RIuQl5w8Rlq5NZ4Vttcks5ri-h1gaJpZM4MTwvC
.

@vanniktech Let me know what you think.

@vanniktech Any other changes?

@vanniktech Np. I need to write a few tests for it as well!


Crash after SymPy fails to parse variable named is in mod file

When running NMODL on a mod file (kv4_ch.mod, found in https://github.com/Hjorthmedh/BasalGangliaData/tree/main/data/neurons/mechanisms) containing a variable named is, SymPy throws a SyntaxError that later results in NMODL crashing with seemingly unrelated errors.
(.venv_nmodl) vanwalst@bbpv1 ~/p/snudda> nmodl BasalGangliaData/data/neurons/mechanisms/kv4_ch.mod
INFO : Using nmodl-nightly Package (Developer Version)
[NMODL] [warning] :: SympySolverVisitor :: solve_non_lin_system python exception: Sympify of expression 'could not parse 'is'' failed, because of exception being raised:
SyntaxError: invalid syntax (<string>, line 1)
[NMODL] [warning] :: SympySolverVisitor :: solve_non_lin_system python exception: Sympify of expression 'could not parse 'is'' failed, because of exception being raised:
SyntaxError: invalid syntax (<string>, line 1)
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
[NMODL] [error] :: NeuronSolveVisitor :: solver method 'sparse' not supported
terminate called after throwing an instance of 'std::runtime_error'
  what():  PRIME encountered during code generation, ODEs not solved?
fish: Job 1, 'nmodl BasalGangliaData/data/neu…' terminated by signal SIGABRT (Abort)

After renaming the variable, NMODL runs without error. Tested on nightly 0.6.152 and on 0.5.

NMODL continuing to run after the SymPy error will be addressed by #1257.
However, it is not clear to me if a variable named is should or should not be allowed in a mod file?

We've noticed the same yesterday. NEURON and it's MOD file converter allow it. Plus, it happens only when we send some string (containing is) to SymPy that things go wrong.
If you need it to works with NMODL soon, you're probably best off changing the variable name to something more descriptive or anything not is, like i_s or is_.


Topic needs to be updated

The section on expanding collection-valued navigation properties Retrieve related entities by expanding collection-valued navigation properties doesn't represent that expanded collection-valued navigation properties will be returned, at least for one level of depth
The examples should show something like this:
{
<EMAIL_ADDRESS>"https://yourorg.api.crm.dynamics.com/api/data/v9.1/$metadata#accounts(name,Account_Tasks(subject,scheduledstart))",
    "value": [
        {
<EMAIL_ADDRESS>"W/\"30492090\"",
            "name": "Contoso, Ltd. (sample)",
            "accountid": "7a4814f9-b0b8-ea11-a812-000d3a122b89",
            "Account_Tasks": [
                {
<EMAIL_ADDRESS>"W/\"28876919\"",
                    "subject": "Task 1 for Contoso, Ltd.",
                    "scheduledstart": null,
                    "_regardingobjectid_value": "7a4814f9-b0b8-ea11-a812-000d3a122b89",
                    "activityid": "7b4814f9-b0b8-ea11-a812-000d3a122b89"
                },
                {
<EMAIL_ADDRESS>"W/\"28876923\"",
                    "subject": "Task 2 for Contoso, Ltd.",
                    "scheduledstart": null,
                    "_regardingobjectid_value": "7a4814f9-b0b8-ea11-a812-000d3a122b89",
                    "activityid": "7c4814f9-b0b8-ea11-a812-000d3a122b89"
                },
                {
<EMAIL_ADDRESS>"W/\"28876927\"",
                    "subject": "Task 3 for Contoso, Ltd.",
                    "scheduledstart": null,
                    "_regardingobjectid_value": "7a4814f9-b0b8-ea11-a812-000d3a122b89",
                    "activityid": "7d4814f9-b0b8-ea11-a812-000d3a122b89"
                }
            ],
<EMAIL_ADDRESS>"https://yourorg.api.crm.dynamics.com/api/data/v9.1/accounts(7a4814f9-b0b8-ea11-a812-000d3a122b89)/Account_Tasks?$select=subject,scheduledstart"
        },
        {
<EMAIL_ADDRESS>"W/\"30455797\"",
            "name": "Test Account Updated",
            "accountid": "e016c269-b0d3-ea11-a812-000d3a122b89",
            "Account_Tasks": [],
<EMAIL_ADDRESS>"https://yourorg.api.crm.dynamics.com/api/data/v9.1/accounts(e016c269-b0d3-ea11-a812-000d3a122b89)/Account_Tasks?$select=subject,scheduledstart"
        }
    ]
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 98e45805-c133-3bbd-6e2f-42c1650103c9
Version Independent ID: dce8a438-01c7-863d-71a4-33a778f69b43
Content: Retrieve related entity records with a query (Common Data Service) - Power Apps
Content Source: powerapps-docs/developer/common-data-service/webapi/retrieve-related-entities-query.md
Service: powerapps
GitHub Login: @JimDaly
Microsoft Alias: phecke

doc was updated


PDF2 bug? Header and footer missing on last page of ToC

I'm using DOT 2.1.2 as it is conveniently bundled with a certain XML editor.
I'm using ditamap, not bookmap. $mirror-page-margins is false.
For some reason, there is no header or footer on the last page of the ToC. The ToC has three pages. It starts on p.2, and the page with the missing header & footer is p.4.
layout-masters.xsl would seem to redirect the last page header and footer to the even page header and footer. I have set up the even page header to be identical to the odd page header, but it doesn't appear on p.4

@DJBHollis The DITA-OT team will need to reproduce this. Can you upload your doc set? Otherwise it might be quite a long time before someone happens to have a sample set at hand which they can use to reproduce the issue.

OK, many thanks. Upload to where?

You supposedly can attach files to a GitHub issue. However, I was unable to attach a ZIP today. @robander Any suggestions?

When you write a comment, at the bottom of the text area there is a label like:
 Attach files by dragging & dropping or by selecting them.

@DJBHollis, do you use an unmodified pdf2 transformation or do you use an override plugin?

Thanks, everyone. For some reason, I assumed there would be a 'bug report' area in the code base. I didn't think to add them to the issue itself!
It's a customisation plug-in.

Here are the files ...
dita_source.zip
com.adaptive.pdf.zip
metadata_manager_user_guide.pdf

I recommend to output the name of the template directly. Then you can see, whether the correct templates are called. If not, we have to find out why -> Toolkit bug. If yes, you know which templates to fix in your plugin.
<xsl:template name="insertIndexEvenHeader">
  <fo:static-content flow-name="even-index-header">
    <fo:block>Template called: insertIndexEvenHeader</fo:block>
  </fo:static-content>
</xsl:template>

The problem is that there is no header on p.4, so I don't see that adding a fo:block to output the name is going to change that.
I don't think the issue is in the headers and footers, I think it is either in the page sequence logic, or how the master page template is called.

From what I tested this would look like a bug in the RenderX XEP processor.
Your XSLT customization looks good. I also published using Apache FOP, it produced only two table of contents pages and the logo was on each of them.

The issue is that you have $mirror-page-margins set to false(),  as you said, and in the static-contents.xsl file in your plugin, you have:
<xsl:template name="insertTocStaticContents">
    <xsl:call-template name="insertTocOddFooter"/>
    <xsl:if test="$mirror-page-margins">
        <xsl:call-template name="insertTocEvenFooter"/>
    </xsl:if>
    <xsl:call-template name="insertTocOddHeader"/>
    <xsl:if test="$mirror-page-margins">
        <xsl:call-template name="insertTocEvenHeader"/>
    </xsl:if>
</xsl:template>

In other words, the static contents for even TOC pages is only inserted if $mirror-page-margins is true().
If you look at org.dita.pdf2/cfg/fo/layout-masters.xsl, you can see that it defines a master for the last TOC page, which uses the same static contents as even TOC pages:
<fo:simple-page-master master-name="toc-last" xsl:use-attribute-sets="simple-page-master">
    <fo:region-body xsl:use-attribute-sets="region-body.even"/>
    <fo:region-before region-name="even-toc-header" xsl:use-attribute-sets="region-before"/>
    <fo:region-after region-name="even-toc-footer" xsl:use-attribute-sets="region-after"/>
</fo:simple-page-master>

The solution therefore is to change your static-content.xsl to:
<xsl:template name="insertTocStaticContents">
    <xsl:call-template name="insertTocOddFooter"/>
    <xsl:call-template name="insertTocEvenFooter"/>
    <xsl:call-template name="insertTocOddHeader"/>
    <xsl:call-template name="insertTocEvenHeader"/>
</xsl:template>

Hi, @DJBHollis . I'm very glad that you are getting more involved in creating PDF customizations. And @eerohele , many thanks for identifying the problem with David's PDF customization. But a few gentle suggestions:

Test and see whether the issue is with the DITA-OT base code, as opposed to your custom plug-in, before opening a DITA-OT issue. You can do this by publishing your content using the OOB PDF2 transformation.
If the problem is with your customization, good places to look for help are the dita-users and DITA-OT users lists. Or ping friends with good DITA-OT skills.
If the problem seems to be with the DITA-OT code, confirm with the latest stable release of the DITA-OT and then open a issue. Read the guidelines for issue at https://github.com/dita-ot/dita-ot/blob/develop/CONTRIBUTING.md to ensure that your issue meets the guidelines.

Hi all,
Thanks for looking into this, and finding a solution.
For me, I consider that there is still an issue surrounding the $mirror-page-margins and page sequence logic.
If I set $mirror-page-margins to false(), then why do I need to create even page headers and footers? I simply should not have to! There should never be a call for an even page.
Or, to put it another way, the logic works for the body section, why not for ToC?
There is another aspect here, that the first page of the ToC is on page 2. If $mirror-page-margins were set to true, this would be on page 3 because the logic would add a dummy last page to front matter. Typically, this would be blank.
The way the logic is set up, a call to the first page becomes a call to the odd page template.
So, template wise, in the example content, the ToC is: P2, odd page template; P3, odd page template; P4 even page template.
In other words, there is a bug! IMHO!
Anyway, I now have a workaround. Thanks once again.

Just to be clear, the section of code which @eerohele found in the customisation is straight out of the DITA 2.1.2 code. I haven't modified it.
The code that I have modified has 'Adaptive' associated with it. For background, please see: #2319.

FWIW - I am able to reproduce this with out-of-the-box 2.2.4. I had to add several chapters to David's source map to make it extend to 3 pages. The default header (Adaptive Metadata Manager | Contents | ii) appears on page 2, and on page 3, but on page 4 (third page of TOC) there is no header. If I add enough to get four pages of TOC, the header appears on all four. This does seem like a bug, but I haven't used this part of the code enough to know offhand whether changes will break customizations.
metadata_manager_user_guide.pdf
the map with one chapter duplicated enough to get a third page of TOC.

If I set $mirror-page-margins to false(), then why do I need to create even page headers and footers? I simply should not have to! There should never be a call for an even page.

I agree that it would make sense to have first-toc-header, first-toc-footer, last-toc-header, and last-toc-footer. The same thing applies for the index and the glossary.
Adding those shouldn't be too difficult. Might make for a good first bug?

See #2112 for a related issue: Missing attribute sets for Glossary, Index & ToC.

Last page headers of bookmap chapters are missed too, if not followed by a blank page.
Identified with oxygen 18, standard pdf build (FOP) and build-in 2.x OT or separate 2.2.4 OT.
build-in OT 1.8 works fine.

From layout-masters.xsl, I put back <!--blank-or-not-blank="blank"--> that had been commented out:
  <!-- Generate a page sequence master -->
  <xsl:template name="generate-page-sequence-master">
    <xsl:param name="master-name"/>
    <xsl:param name="master-reference"/>
    <xsl:param name="first" select="true()"/>
    <xsl:param name="last" select="true()"/>
    <fo:page-sequence-master master-name="{$master-name}">
      <fo:repeatable-page-master-alternatives>
        <xsl:if test="$first">
          <fo:conditional-page-master-reference master-reference="{$master-reference}-first"
                                                odd-or-even="odd"
                                                page-position="first"/>
        </xsl:if>
        <xsl:if test="$last">
          <fo:conditional-page-master-reference master-reference="{$master-reference}-last"
                                                odd-or-even="even"
                                                page-position="last"/>
                                            <!--blank-or-not-blank="blank"-->
        </xsl:if>
        <xsl:choose>
          <xsl:when test="$mirror-page-margins">
            <fo:conditional-page-master-reference master-reference="{$master-reference}-odd"
                                                  odd-or-even="odd"/>
            <fo:conditional-page-master-reference master-reference="{$master-reference}-even"
                                                  odd-or-even="even"/>
          </xsl:when>
          <xsl:otherwise>
            <fo:conditional-page-master-reference master-reference="{$master-reference}-odd"/>
          </xsl:otherwise>
        </xsl:choose>
      </fo:repeatable-page-master-alternatives>
    </fo:page-sequence-master>
  </xsl:template>

It now works as expected.


How do I get a regression for Random Forest instead of a classification?

As far as I know, this feature is not implemented.

Hi @WebMaestro59 indeed @MustafaKarabulut is correct, Random Forest for regression is not implemented in this library
However, you can do this in Rubix ML by wrapping a Regression Tree in a Bootstrap Aggregator meta-estimator like in the example below. It even supports multiprocessing.
use Rubix\ML\BootstrapAggregator;
use Rubix\ML\Regressors\RegressionTree;

$estimator = new BootstrapAggregator(new RegressionTree(10), 300, 0.2);

Hope this helps!


[Codegen] fix bug on LLVM 10.0

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers by @ them in the pull request thread.
Fix llvm::CGFT_xxx to llvm::TargetMachine::CGFT_xxx.

@yzhliu

Thanks @qingyunqu !

@qingyunqu this breaks the build with the trunk as pointed out in #4386. Can you revert this change and instead fix version ifdef? Sorry I didnt test in llvm 10.0.

@masahi Could I push a new version that reduce the second and the third ifdef into one?

No, second elif should be TVM_LLVM_VERSION <= 100. The last one is for the latest llvm.

@qingyunqu where did your get your llvm 10.0? It is not released yet

@masahi Maybe I used the master branch of LLVM

Ok, that means you are using an out of date LLVM trunk. Please send another PR that reverts this change. If you update and rebuild your LLVM, the build should succeed.

@masahi Thanks, I will send the PR immediately.

@masahi I have used svn to update my LLVM. But after rebuilding LLVM, the build of tvm without TargetMachine:: also failed. May I make a mistake or misunderstand?

A couple of points:

LLVM project moved to github https://github.com/llvm/llvm-project. You might want to switch to this repo from svn.
Make sure you have the enum CodeGenFileType in include/llvm/Support/Codegen.h (not in TargetMachine.h)
Make sure you are building TVM with the correct LLVM installation.

Thanks, I have got the latest LLVM of 10.0.0git version and found the enum CodeGenFileType. I will test the compilation on this version and then push another PR. Thanks a lot!

@masahi I have compiled tvm with 10.0.0git LLVM. There is something wrong when I run cmake:

Then I comment the error line in FindLLVM.cmake:43. Everything becomes ok:

Maybe there is better method to fix this?

I also remember seeing that error (but I don't remember how I fixed it). Unless you have a good solution for this, we can fix that later. If you've confirmed that you can build TVM with the LLVM trunk, please send a PR that reverts this change.


[Improved] error handling

Coverage decreased (-3.6%) to 4.938% when pulling a04851deccf74225925f09b3d9d3d4482c22ae5a on Drogglbecher:master into c092ac33b8d75022bac673101c12a44fec0ddfc7 on rust-leipzig:master.

Coverage decreased (-4.2%) to 4.348% when pulling 4e26ad136ecfedd7c97892a91f59307f7749c7c7 on Drogglbecher:master into c092ac33b8d75022bac673101c12a44fec0ddfc7 on rust-leipzig:master.

Coverage decreased (-4.2%) to 4.348% when pulling f53749333057c578d6c06008cb00b552feb7253e on Drogglbecher:master into c092ac33b8d75022bac673101c12a44fec0ddfc7 on rust-leipzig:master.

Thank you very much, I will do some small code cleanup in another pull request.


Provide a method to list, edit, and manage customizations

Concept:

Use a DAStore to centrally control customizations to the Weaver
Document and provide a way for a package to update the DAStore to add new settings automatically when a certain package is installed. Essentially, we'd be adding a configuration hook
Also have a way for someone to directly edit the configuration to do light manual customizations, like adding dependencies

Settings should include:

list of dependency packages
variables to leave untransformed
new prefixes to use to match people names
replacement output_patterns.yml to control the contents of individual blocks
new, as yet not setup method to control the order, selection, and placement of the various output_pattern blocks. (should think about the issue identified in #349 )

Thoughts:

Create a DAStore at the prefix `docassemble.ALWeaver'
Inside the docassemble.ALWeaver' prefix, add a dictionary named published_configuration_capabilities. Each key would point to a YAML file path in the data/sources folder of a package, which I am proposing we call configuration_capabilities.yml`. The YAML itself would contain options like: the path to the output_patterns.yml, interview_structure.yml, and variables.yaml file, as well as directly containing a list of includes that the package will help you add to the output file.
When a package that contains a configuration_capabilities.yml and an appropriate .py file is installed on the server, the server should run the .py file which adds the configuration_capabilities.yml file contents into the published_configuration_capabilities dictionary.
There is a settings page inside the Weaver that lets you choose which of the published options you want to use. It should be possible to add multiplies of each option. For the most part these are additive and wouldn't cancel each other out.

Open to thoughts on the structure and names that I've described above. Also something we could chat about on 12/20.

Here's an example of the configuration_capabilities.yml file:
######################
# List of available configuration options that this package supplies
# These are the "default" dependencies, etc.
package name: Default Weaver Choices (CourtFormsOnline/MassAcccess)
jurisdiction_choices:
  - description: Massachusetts
    dependency: "docassemble.ALMassachusetts>=0.0.7"
    include_name: "docassemble.ALMassachusetts:al_massachusetts.yml"
    default: True
organization_choices:
  - description: MassAccess
    dependency: "docassemble.MassAccess"
    include_name: "docassemble.MassAccess:massaccess.yml"
    default: True
  - description: Illinois Legal Aid Online
    dependency: "docassemble.ILAO"
    include_name: "docassemble.ILAO:ilao-interview-framework.yml"
    default: False
  - description: Louisiana Supreme Court
    dependency: "docassemble.ALLouisianaSC"
    include_name: "docassemble.ALLouisianaSC:custom_organization.yml"
    default: False
output_patterns: output_patterns.yml
interview_structure: interview_structure.yml
variable_names: variable_names.yml

We might want a way to let people say "I'm in this group" and then associate a set of preferences w/ their group. But we don't know yet if there will be differences w/in a state.
Maybe once we start getting into more public benefits forms? But it's probably solvable a level higher up--e.g., we could have people declare the class of their object as the public benefits version, and we maintain a standardized set of questions that are used for that use case nationwide, not something the group needs to maintain.
Want to minimize the number of settings people need to understand after they select something very simple, like the state that they are automating in.

Would probably want to version the settings files as well as validate them in some way.

instead of interview_structure.yml use output_interview_structure.yml to clarify what file we're going to use

Would probably want to version the settings files as well as validate them in some way.

How would we handle conflicting versions of settings files? e.g. ILAO made a settings file using weaver 2.3.1, but IllinoisAccess made one that used weaver 3.4.2.

How would we handle conflicting versions of settings files? e.g. ILAO made a settings file using weaver 2.3.1, but IllinoisAccess made one that used weaver 3.4.2.
[Kind of getting into package management here. Could we use PyPi somehow? I have no idea how that could work.]

Remember the settings only matter for one individual run of the Weaver. I was more thinking that we would want the settings file to advertise which version of the weaver it is compatible with. So if we are on Weaver version 4 which introduced a change that invalidates Weaver 3 setting files, the weaver itself skips the files that are for version 3.


bump node-version to 8.11.1

Codecov Report

Merging #601 into master will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #601      +/-   ##
==========================================
+ Coverage    27.4%   27.56%   +0.15%
==========================================
  Files         157      156       -1
  Lines        2988     2964      -24
  Branches      406      402       -4
==========================================
- Hits          819      817       -2
+ Misses       1944     1928      -16
+ Partials      225      219       -6

Impacted Files
Coverage Δ

src/store/wallet/screen/screenActions.js
15.38% <0%> (-6.05%)
:arrow_down:

src/store/store.js
12.98% <0%> (-2.57%)
:arrow_down:

src/components/accounts/AccountShow/show.js
28.12% <0%> (-0.91%)
:arrow_down:

src/components/ledger/ImportAccount/addr.js
0% <0%> (ø)
:arrow_up:

src/components/ledger/WaitDialog/waitDialog.js
44.44% <0%> (ø)
:arrow_up:

...mponents/layout/NotificationBar/NotificationBar.js
0% <0%> (ø)
:arrow_up:

src/components/welcome/welcome.js
0% <0%> (ø)
:arrow_up:

...nts/ledger/ImportAccount/ImportAccountContainer.js

src/utils/get-wallet-version.js

...c/components/ledger/ImportAccount/ImportAccount.js

... and 8 more

Continue to review full report at Codecov.

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


fix: change port field to 8 bytes

https://github.com/coollabsio/coolify/issues/762

This is only a question, but the limit of a port not is 16bit (4 bytes)?
https://en.wikipedia.org/wiki/Port_(computer_networking)


Fix Subfilter SQL query creation

Ticket: #131

@MicheleK17 I have fixed the bug, but I fear this won't be the last amendment to the server regarding the Subfilters.  This should be rigorously tested, especially the subfilters for genes and microorganism characteristics.


MI - PERFORMANCE TUNING (Message Transformation)

Complete docs on tuning message transformation scenarios [1].
[1] https://github.com/wso2/docs-ei/blob/master/en/micro-integrator/docs/setup/performance_tuning/message_transformation_tuning.md

This content [1] was moved to the Examples section [2].
[1] https://docs.wso2.com/display/EI650/Message+Transformations
[2] https://ei.docs.wso2.com/en/next/micro-integrator/use-cases/examples/message_transformation_example/


Add the packages controller to the build artifacts.

The intent here is to make sure that artifacts for curated packages (namely our controller image and our helm chart) get included in builds.
/cc @jonahjon  @ivyostosh

/lgtm


Paragraph is misleading

Hi team,
The below paragraph that we can find in this document is not precise/rigorous and can create some confusion to customers. The sentence is ONLY applicable/true if customers are using the Log Analytics agent (MMA/OMS). If they are using Azure Monitor Agent (AMA), only the VMs from subscriptions with Servers plan 2 enabled will be billed. Subscriptions that don't have the Servers plan 2 enabled will not be billed, even if the Servers Plan 2 is enabled at the workspace level.
"If you enable the Servers plan on cross-subscription workspaces, connected VMs from all subscriptions will be billed, including subscriptions that don't have the Servers plan enabled."
Please add a note after this sentence, or fix the overall document, because I believe this whole document was mostly written before the announcement of AMA in Defender for Server, and some details differ between agents.
Thank you, and kind regards,

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: be0f96ef-df12-de7a-173a-c056062bef8f
Version Independent ID: de058799-cca2-f999-63a3-73c2ccdd2a5d
Content: Understand the basic and extended security features of Microsoft Defender for Cloud
Content Source: articles/defender-for-cloud/enhanced-security-features-overview.md
Service: defender-for-cloud
GitHub Login: @ElazarK
Microsoft Alias: elkrieger

@anperei
Thanks for your feedback! We will investigate and update as appropriate.

#reassign:bmansheim

@anperei Would this sentence be more precise:
"If you enable the Servers plan on cross-subscription workspaces, connected VMs with the Log Analytics agent installed from all subscriptions will be billed, including subscriptions that don't have the Servers plan enabled. Connected VMs with the Azure Monitor agent installed are billed only if the Servers plan is enabled."

Hi @bmansheim, that's exactly it... "If you enable the Servers plan on cross-subscription workspaces, connected VMs with the Log Analytics agent installed from all subscriptions will be billed, including subscriptions that don't have the Servers plan enabled. Connected VMs with the Azure Monitor agent installed are billed only if the Servers plan is enabled at the subscription level."

That's a great suggestion, @anperei !
Resolved in https://github.com/MicrosoftDocs/azure-docs-pr/pull/222869
#please-close


Support Swift Package Manager

Check the following:

https://github.com/apple/swift-package-manager
https://github.com/kylef/swiftenv

:ship:


Fix typo resulting in 404 in Docs > Adapters > React

I see someone already fixed the same in a PR that is also awaiting approval, should have checked before, sorry. Closing this one in favour of https://github.com/TanStack/router/pull/550