More content on RS-Inf-RSE and introducing ML-RSE

Fix one line per sentence for "RSE specializations" chapter
Add some more details for "Research Infrastructure RSE"
Introducing "ML-RSE" as new RSE specialization

Is this ML "special enough" to have it mentioned separately in the first place?
Please feel free to completely re-write :-)

I really like the addition of the ML-RSE since that is very topical at the moment and requires a particular mix of skills. I guess we could make the relationship to the data RSE clearer/obvious. I think it would be good to eventually add something about values to the ML RSE. We can do that when we have sorted out what to do with ethics/values.

just some resources to make you aware of:
https://www.software.ac.uk/blog/2018-04-05-so-you-want-start-data-science-institute-achieving-sustainability
https://www.software.ac.uk/blog/2018-04-05-research-software-engineers-and-data-scientists-more-common


[Snyk] Upgrade @contentstack/cli-utilities from 1.5.7 to 1.5.8

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @contentstack/cli-utilities from 1.5.7 to 1.5.8.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2023-12-04.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Fixed #93


Revert "Remove duplicate flickity"

Reverts artsy/force#3964
Looks like this was leading to a break in https://www.artsy.net/galleries, where changes to the location would fail to destroy and re-create the carousel:
TypeError: this.allOff is not a function
    at b.f.destroy (flickity.js:887)
    at r.destroyFlickity

Though this was a minor version change, lets follow up on the breaking change it seemed to introduce.
cc @zephraph, @starsirius

Thanks, @damassi! Merge on green!

Duplicate Sources / Packages - Duplicates found! ⚠
Duplicates: Found 61 similar files across 72 code sources (both identical + similar)
accounting for 744736 bundled bytes.
Packages: Found 14 packages with 27 resolved, 32 installed, and 68 depended versions.
Roughly 81 lines added.  This is probably a regression over master.

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

-* Duplicates: Found 35 similar files across 44 code sources (both identical + similar)
+* Duplicates: Found 61 similar files across 72 code sources (both identical + similar)

-  accounting for 573823 bundled bytes.
+  accounting for 744736 bundled bytes.

-* Packages: Found 11 packages with 21 resolved, 24 installed, and 60 depended versions.
+* Packages: Found 14 packages with 27 resolved, 32 installed, and 68 depended versions.

 ## auctions.2fa2b18175aec7d4e89c.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.2fa2b18175aec7d4e89c.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.2fa2b18175aec7d4e89c.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.2fa2b18175aec7d4e89c.js
         acorn/dist/acorn.js (I, 119975)
         acorn/dist/walk.js (I, 13326)

-## common.6738c6ffbc5e20d0e4c3.js
+## common.69a333c5928d8adb88c4.js

 assignment (Found 2 resolved, 2 installed, 4 depended. Latest 2.2.0.)
   2.0.0
     ~/insane/~/assignment
       * 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.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         assignment/assignment.js (S, 508)

   2.2.0
     ~/assignment
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.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.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

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

   2.1.1
     ~/bluebird-q
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

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

 domelementtype (Found 2 resolved, 2 installed, 18 depended. Latest 1.3.0.)
   1.1.3
     ~/dom-serializer/~/domelementtype
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         domelementtype/index.js (S, 389)

   1.3.0
     ~/domelementtype
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1

-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         domelementtype/index.js (S, 411)

 domutils (Found 2 resolved, 2 installed, 5 depended. Latest 1.7.0.)
   1.5.1
     ~/domutils
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         domutils/index.js (I, 322)
         domutils/lib/helpers.js (I, 3930)
         domutils/lib/legacy.js (I, 2489)
         domutils/lib/manipulation.js (I, 1530)
         domutils/lib/querying.js (S, 1867)
         domutils/lib/stringify.js (S, 607)
         domutils/lib/traversal.js (I, 547)

   1.7.0
     ~/htmlparser2/~/domutils
       * 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.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         domutils/index.js (I, 322)
         domutils/lib/helpers.js (I, 3930)
         domutils/lib/legacy.js (I, 2489)
         domutils/lib/manipulation.js (I, 1530)
         domutils/lib/querying.js (S, 1893)
         domutils/lib/stringify.js (S, 668)
         domutils/lib/traversal.js (I, 547)

-ev-emitter (Found 2 resolved, 2 installed, 8 depended. Latest 1.1.1.)
+ev-emitter (Found 2 resolved, 4 installed, 8 depended. Latest 1.1.1.)

   1.0.3
     ~/ev-emitter
       * 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.69a333c5928d8adb88c4.js
+        ev-emitter/ev-emitter.js (I, 2596)
+
+    ~/react-flickity-component/~/flickity/~/ev-emitter
+      * 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>+      * Duplicated files in common.69a333c5928d8adb88c4.js

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+        ev-emitter/ev-emitter.js (I, 2596)

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

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+    ~/react-flickity-component/~/unipointer/~/ev-emitter

-<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>

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

-        ev-emitter/ev-emitter.js (S, 2596)
+      * Duplicated files in common.69a333c5928d8adb88c4.js

+        ev-emitter/ev-emitter.js (I, 2596)

+
+
   1.1.1
     ~/react-flickity-component/~/ev-emitter
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         ev-emitter/ev-emitter.js (S, 2704)

+flickity (Found 2 resolved, 2 installed, 2 depended. Latest 2.2.0.)
+  2.0.6
+    ~/flickity
+      * Dependency graph
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.69a333c5928d8adb88c4.js
+        flickity/js/add-remove-cell.js (S, 4905)
+        flickity/js/animate.js (S, 5865)
+        flickity/js/cell.js (S, 2045)
+        flickity/js/drag.js (S, 11389)
+        flickity/js/flickity.js (S, 22657)
+        flickity/js/index.js (S, 991)
+        flickity/js/lazyload.js (S, 3105)
+        flickity/js/page-dots.js (S, 4307)
+        flickity/js/player.js (S, 5137)
+        flickity/js/prev-next-button.js (S, 5998)
+        flickity/js/slide.js (S, 1935)
+
+  2.2.0
+    ~/react-flickity-component/~/flickity
+      * Dependency graph
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.69a333c5928d8adb88c4.js
+        flickity/js/add-remove-cell.js (S, 4115)
+        flickity/js/animate.js (S, 5373)
+        flickity/js/cell.js (S, 2378)
+        flickity/js/drag.js (S, 11596)
+        flickity/js/flickity.js (S, 24706)
+        flickity/js/index.js (S, 997)
+        flickity/js/lazyload.js (S, 3807)
+        flickity/js/page-dots.js (S, 4793)
+        flickity/js/player.js (S, 4511)
+        flickity/js/prev-next-button.js (S, 5789)
+        flickity/js/slide.js (S, 1843)
+
+
 hoist-non-react-statics (Found 1 resolved, 2 installed, 3 depended. Latest 3.1.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>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (I, 2553)

     ~/react-tracking/~/hoist-non-react-statics
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (I, 2553)

 imagesloaded (Found 2 resolved, 2 installed, 2 depended. Latest 4.1.4.)
   4.1.2
     ~/imagesloaded
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         imagesloaded/imagesloaded.js (S, 9658)

   4.1.4
     ~/react-flickity-component/~/imagesloaded
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         imagesloaded/imagesloaded.js (S, 9965)

 isarray (Found 2 resolved, 2 installed, 4 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>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.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.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

         isarray/index.js (S, 132)

 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.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.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.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.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, 5 depended. Latest 4.0.1.)
   3.6.0
     ~/redux
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.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>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

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

     ~/found/~/redux
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.6738c6ffbc5e20d0e4c3.js
+      * Duplicated files in common.69a333c5928d8adb88c4.js

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

+unidragger (Found 2 resolved, 2 installed, 2 depended. Latest 2.3.0.)
+  2.2.0
+    ~/unidragger
+      * Dependency graph
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.69a333c5928d8adb88c4.js
+        unidragger/unidragger.js (S, 6873)
+
+  2.3.0
+    ~/react-flickity-component/~/unidragger
+      * Dependency graph
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.69a333c5928d8adb88c4.js
+        unidragger/unidragger.js (S, 6786)
+
+unipointer (Found 2 resolved, 2 installed, 4 depended. Latest 2.3.0.)
+  2.2.0
+    ~/unipointer
+      * Dependency graph
+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+      * Duplicated files in common.69a333c5928d8adb88c4.js
+        unipointer/unipointer.js (S, 6874)
+
+  2.3.0
+    ~/react-flickity-component/~/unipointer
+      * 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.69a333c5928d8adb88c4.js
+        unipointer/unipointer.js (S, 6946)
+
+
 * 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
@damassi, @zephraph

auctions.2fa2b18175aec7d4e89c.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.2fa2b18175aec7d4e89c.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.2fa2b18175aec7d4e89c.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.2fa2b18175aec7d4e89c.js
      acorn/dist/acorn.js (I, 119975)
      acorn/dist/walk.js (I, 13326)

common.69a333c5928d8adb88c4.js

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

2.0.0
  ~/insane/~/assignment
    * 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.69a333c5928d8adb88c4.js
      assignment/assignment.js (S, 508)
2.2.0
  ~/assignment
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.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.69a333c5928d8adb88c4.js
      bluebird-q/index.js (S, 14411)
2.1.1
  ~/bluebird-q
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      bluebird-q/index.js (S, 16795)

domelementtype (Found 2 resolved, 2 installed, 18 depended. Latest 1.3.0.)

1.1.3
  ~/dom-serializer/~/domelementtype
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> dom-serializer@0 -><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      domelementtype/index.js (S, 389)
1.3.0
  ~/domelementtype
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-> domelementtype@1
    * Duplicated files in common.69a333c5928d8adb88c4.js
      domelementtype/index.js (S, 411)

domutils (Found 2 resolved, 2 installed, 5 depended. Latest 1.7.0.)

1.5.1
  ~/domutils
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      domutils/index.js (I, 322)
      domutils/lib/helpers.js (I, 3930)
      domutils/lib/legacy.js (I, 2489)
      domutils/lib/manipulation.js (I, 1530)
      domutils/lib/querying.js (S, 1867)
      domutils/lib/stringify.js (S, 607)
      domutils/lib/traversal.js (I, 547)
1.7.0
  ~/htmlparser2/~/domutils
    * 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.69a333c5928d8adb88c4.js
      domutils/index.js (I, 322)
      domutils/lib/helpers.js (I, 3930)
      domutils/lib/legacy.js (I, 2489)
      domutils/lib/manipulation.js (I, 1530)
      domutils/lib/querying.js (S, 1893)
      domutils/lib/stringify.js (S, 668)
      domutils/lib/traversal.js (I, 547)

ev-emitter (Found 2 resolved, 4 installed, 8 depended. Latest 1.1.1.)

1.0.3
  ~/ev-emitter
    * 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.69a333c5928d8adb88c4.js
      ev-emitter/ev-emitter.js (I, 2596)
  ~/react-flickity-component/~/flickity/~/ev-emitter
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      ev-emitter/ev-emitter.js (I, 2596)
  ~/react-flickity-component/~/unipointer/~/ev-emitter
    * 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.69a333c5928d8adb88c4.js
      ev-emitter/ev-emitter.js (I, 2596)
1.1.1
  ~/react-flickity-component/~/ev-emitter
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      ev-emitter/ev-emitter.js (S, 2704)

flickity (Found 2 resolved, 2 installed, 2 depended. Latest 2.2.0.)

2.0.6
  ~/flickity
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      flickity/js/add-remove-cell.js (S, 4905)
      flickity/js/animate.js (S, 5865)
      flickity/js/cell.js (S, 2045)
      flickity/js/drag.js (S, 11389)
      flickity/js/flickity.js (S, 22657)
      flickity/js/index.js (S, 991)
      flickity/js/lazyload.js (S, 3105)
      flickity/js/page-dots.js (S, 4307)
      flickity/js/player.js (S, 5137)
      flickity/js/prev-next-button.js (S, 5998)
      flickity/js/slide.js (S, 1935)
2.2.0
  ~/react-flickity-component/~/flickity
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      flickity/js/add-remove-cell.js (S, 4115)
      flickity/js/animate.js (S, 5373)
      flickity/js/cell.js (S, 2378)
      flickity/js/drag.js (S, 11596)
      flickity/js/flickity.js (S, 24706)
      flickity/js/index.js (S, 997)
      flickity/js/lazyload.js (S, 3807)
      flickity/js/page-dots.js (S, 4793)
      flickity/js/player.js (S, 4511)
      flickity/js/prev-next-button.js (S, 5789)
      flickity/js/slide.js (S, 1843)

hoist-non-react-statics (Found 1 resolved, 2 installed, 3 depended. Latest 3.1.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>    * Duplicated files in common.69a333c5928d8adb88c4.js
      hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (I, 2553)
  ~/react-tracking/~/hoist-non-react-statics
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      hoist-non-react-statics/dist/hoist-non-react-statics.cjs.js (I, 2553)

imagesloaded (Found 2 resolved, 2 installed, 2 depended. Latest 4.1.4.)

4.1.2
  ~/imagesloaded
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      imagesloaded/imagesloaded.js (S, 9658)
4.1.4
  ~/react-flickity-component/~/imagesloaded
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      imagesloaded/imagesloaded.js (S, 9965)

isarray (Found 2 resolved, 2 installed, 4 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>    * Duplicated files in common.69a333c5928d8adb88c4.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.69a333c5928d8adb88c4.js
      isarray/index.js (S, 132)

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.69a333c5928d8adb88c4.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.69a333c5928d8adb88c4.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, 5 depended. Latest 4.0.1.)

3.6.0
  ~/redux
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.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>    * Duplicated files in common.69a333c5928d8adb88c4.js
      redux/es/redux.js (I, 23104)
  ~/found/~/redux
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      redux/es/redux.js (I, 23104)

unidragger (Found 2 resolved, 2 installed, 2 depended. Latest 2.3.0.)

2.2.0
  ~/unidragger
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      unidragger/unidragger.js (S, 6873)
2.3.0
  ~/react-flickity-component/~/unidragger
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      unidragger/unidragger.js (S, 6786)

unipointer (Found 2 resolved, 2 installed, 4 depended. Latest 2.3.0.)

2.2.0
  ~/unipointer
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.69a333c5928d8adb88c4.js
      unipointer/unipointer.js (S, 6874)
2.3.0
  ~/react-flickity-component/~/unipointer
    * 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.69a333c5928d8adb88c4.js
      unipointer/unipointer.js (S, 6946)


[Bazel]: fixup nits from #7146

These are

[ ] Fixing a commit for obazl

this needs to be done soon, to ensure that checking out a commit and building with bazel can be done despite upstream changes
easy fix, agreed to do in a follow-up PR

[ ] Using submodules instead of remote repo URLs + commits

submodules haven't all been updated yet, so this can wait for that

[ ] Mac builds using staticlib

easy fix, non-urgent

[ ] Deleting some unused code
[ ] Documentation on some bazel-specific bash scripts

See PR #7146 for more detail. @mobileink will be working on these.

OBazl rules pins:
While we are still merging/integrating/testing the Bazel code into the Bazel branch, the obazl rules will be pinned to the main branch rather than specific commits.  This is just for convenience, so that any changes to the obazl rules we may need to make will be automatically used. This transition period should be quite short, a matter of a day or two. Once all Bazel code has been merged into the Bazel branch, and the builds have been verified on MacOS and Linux, these repos will be pinned to specific commit IDs.
The repos affected are obazl_rules_opam, obazl_rules_ocaml, and obazl_tools_bazel. They are loaded by the ocaml_fetch_rules function in WORKSPACE.bzl.

Submodules:
As for pinning, during the transition period the code will use remote repositories to fetch the code, rather than the embedded git submodules. Again this is just a convenience, in case we discover that we need to make changes to any of the external repos, and it will only apply during the short window of transition.  Once all Bazel code is integrated and builds are verified, we will switch to using local_repository rules that resolve to the embedded git submodules, which will be pinned to specific commit IDs.
The code supporting remote repos will be retained since it will be used if and when a decision is made to remove git submodules.
The affected repos are:

ppx_optcomp
ppx_version
snarky
graphql_ppx
marlin
zexe

Special cases:  ocaml-rocksdb and ocaml-sodium
The code that loads the repos is in bzl/external/ocaml_repos.bzl and bzl/external/rust_repos.bzl.

Link modes: see #7155


fixed the error when trying to perform get on channels

now it states the get cannot be used on channels

Some minor changes, otherwise LGTM.

@hackrush01 I edited the CHANGELO.md and squashed the commits. Please let me know if that is all you need.

merged

@lyoshenka  So this one is approved?

yep. i cleaned it up a bit and merged it in https://github.com/lbryio/lbry/commit/bb2efdcc7c38a26cd219e8866000e4857b2bffc1

@lyoshenka  What should I do with closed unmerged commit? Just delete branch?

yep


Add error message when type of insertMeta is explicitly set

Version: latest
Module: quill-core
When type of insertMeta is explicitly set
implicit val personInsertMeta: InsertMeta[Person] = insertMeta[Person](_.name)

then insert query produces wrong sql:
INSERT INTO person (age) VALUES (age)

Expected behavior
Add compiler error
Steps to reproduce the behavior
https://scastie.scala-lang.org/ogQBs2YVSbS4sMRJthFVqA
Workaround
Remove explicit type of insertMeta
@getquill/maintainers

I got bit by this bug this week... Took a while to pin down the source of the problem. I put together a test-case that reproduces it, though, if that's of any help.
If someone can point me in the right direction (e.g., another place in the code where a compiler error is generated due to an invalid library usage), perhaps I can take a stab at a patch.

I wonder if such mistakes will become more common starting in Scala 2.13.11 because https://github.com/scala/scala/pull/10083 is landing, encouraging users to add explicit types to their implicit defs and implicit vals
related: https://github.com/scala/bug/issues/12798
(not sure if this repo has other tickets in this general area — this is the one I was able to find)

@SethTisue We cannot update to 2.13.11 because of this issue. We use -Xsource:3 and I see -Wconf:cat=other-implicit-type:s is simply being ignored with that option together.

Is it possible to spell out the type in source, i.e., is InsertMeta[Person] just not specific enough?


Need Way to Identify Zone based on sender and recipient addres  for UPS

I am integrating UPS API for Shipengine. In my programming i have to charge to client based on Zone provided by UPS. I need some API by which i know Zone from sender and recipient address. I know UPS is giving option to download file which give zone details from link https://www.ups.com/us/en/support/shipping-support/shipping-costs-rates/retail-rates.page. But if i have to integrate all zones of US then i have to download more then 900 files. Is any option to get list of zones though any API or though any download option.

Hey @kishanapex , we don't have these available via API but I've got a list of the current UPS zones with to/from zip-3s here for you so you don't have to download 900 different files.  Hope this helps!
ups_zonemap.csv

Really grateful for this information. UPS also having different zones for different shipping method for Hawaii, Alaska, do you able to help in that which give me list of source zip, destination zip , shipping method and zone

@kishanapex unfortunately I don't have service level UPS zone information

do you have zone information for Alaska and Hawaii for UPS

do you have any update on my last question? do you have zone information for Alaska and Hawaii for UPS


[Bug] Can't load a layer exported from ATT&CK Navigator

Expected Behavior
No error while importing a layer from ATT&CK Navigator
The zipped layer is here for reference : layer.zip
Actual Behavior
An error is raised, and the layer is not loaded :
[Layer] - AttributeError encountered ['#ff6666ff' is not in web format. Need 3 or 6 hex digit.]. Unable to load.
[Layer] - Full Traceback - Traceback (most recent call last):
  File "C:\Python310\lib\site-packages\mitreattack\navlayers\core\layer.py", line 97, in _build
    self.__layer._linker(key, self._data[key])
  File "C:\Python310\lib\site-packages\mitreattack\navlayers\core\layerobj.py", line 446, in _linker
    self.gradient = data
  File "C:\Python310\lib\site-packages\mitreattack\navlayers\core\layerobj.py", line 221, in gradient
    self.__gradient = Gradient(gradient['colors'], gradient['minValue'], gradient['maxValue'])
  File "C:\Python310\lib\site-packages\mitreattack\navlayers\core\gradient.py", line 20, in __init__
    self.maxValue = maxValue
  File "C:\Python310\lib\site-packages\mitreattack\navlayers\core\gradient.py", line 52, in maxValue
    self._compute_curve()
  File "C:\Python310\lib\site-packages\mitreattack\navlayers\core\gradient.py", line 64, in _compute_curve
    s_c = colour.Color(self.colors[index-1])
  File "C:\Python310\lib\site-packages\colour.py", line 988, in __init__
    self.web = color if color else 'black'
  File "C:\Python310\lib\site-packages\colour.py", line 1006, in __setattr__
    fc(value)
  File "C:\Python310\lib\site-packages\colour.py", line 1084, in set_web
    self.hex = web2hex(value)
  File "C:\Python310\lib\site-packages\colour.py", line 670, in web2hex
    raise AttributeError(
AttributeError: '#ff6666ff' is not in web format. Need 3 or 6 hex digit.

Steps to Reproduce the Problem

Go to https://mitre-attack.github.io/attack-navigator/

Create an empty enterprise layer

Download the layer into layer.json

Load the layer using Python
from mitreattack.navlayers.core.layer import Layer

test = Layer()
test.from_file("layer.json")

Observe the console output

Thanks for bringing this to our attention! It looks like the export format for navigator may have been updated slightly, which shouldn't be too hard to address.

@Vayper We've pushed version 1.4.4 out the door, which should resolve the problem. Thanks for reporting this!


Evalutaing on VOC 2012 detection

How did you evaluate results on VOC 2012? Evaluation server is still available for submission? I created a login and didn't do any submission so far. Also, it shows that only 2 submissions are possible(at the competition time). Is it the same case now?

Sorry for the late reply. Yes the evaluation server is still available and maximum of 2 submissions/day.


Endpoint to calculate Pension

There are mainly two options regarding how to receive income from a pension plan: either take it out as a lump sum payment or have it distributed in a stream of periodic payments until the retiree passes away (or in some cases, until both the retiree and their spouse passes away).
Perform all the calculations in the function.py file present in helpers folder
Create the endpoint pension in the main.py file and return the required result in a proper format

I am new to the project and I would like to contribute.

@ighoshsubho can you please assign me this issue?

sure @animesharma3, go ahead! :)

if there is no movement then i like to work on this

sure @Aman1919 go ahead! ;)

Hi im gssoc 23 contributor new to open source can you elaborate what needs to be done here and can you assign the issue to me

Greetings , I am a GSSOC 23 contributor . I find my skills to be a good match for the issue . Kindly accept me as a contributor.

This issue has been closed, please raise a new one and I will definitely assign you @mridul45 and @NIveX2169, and this project will be there in GSSOC'23.

ok sure


Creating empty character object

When creating an empty character, the camera tends to point a random direction and become immoveable

Fixed, will be in next build with new entity classes


subset tab isnt representing completeness of vars correctly

i suspect were using the wrong value from the distribution response to determine the number of entities w values.. for umsp - weight i see:
"numVarValues":2343855,"numDistinctValues":1814,"numDistinctEntityRecords":4104822,"numMissingCases":0
i think numVarValues is the number we want, but the subset tab currently says all entity records have values.

I talked to @ryanrdoherty about this. We're using the correct property, but there was a bug in the reporting. He says this is now fixed on latest.


fix: #568 Terraform destroy fails when state is empty

Terraform destroy fails when state is empty
Description
The terraform destroy fails on any incomplete run because there is reference of name everywhere. Replacing the name with user provided one. Fixes #568
Checklist

[ ] CI tests are passing
[ ] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

I am not sure why Lint/Docs is failing. Please let me know what should i do to fix it.

I am not sure why Lint/Docs is failing. Please let me know what should i do to fix it.

You need to rebase your branch from master

Thanks @ageekymonk for your work. I'm closing this in favor of https://github.com/terraform-aws-modules/terraform-aws-eks/pull/1041


new: hello.sh: name-printing script

As instructed, I've added a script to print my name. As of now, POSIX
encourages shell scripts to use printf instead of echo as per the
2008 standard so the script may deviate from the instructions a bit.
http://pubs.opengroup.org/onlinepubs/9699919799/utilities/echo.html

Excellent!


Updates for dynamic token management

@johnsmartco It would be good to mention the ability to revoke a token/lease (vault lease revoke astra/org/token/<LEASE_ID>). I'm not sure of the best way to fit that in with the "delete" information. It may even replace it since with dynamic tokens they will always expire at some point. Deletion may no longer be necessary.

Will resolve merge conflicts after next two meetings...

Thanks @bansri29. Just a note that I'll wait for a "go" signal from @rogerb-ds to merge the updates.  Probably this Thursday, 10-Nov.


Move mapping and abbreviations related functions to a separate source file

Codecov Report

Merging #4740 into master will decrease coverage by 0.01%.
The diff coverage is 72.55%.

@@            Coverage Diff             @@
##           master    #4740      +/-   ##
==========================================
- Coverage   81.41%    81.4%   -0.02%
==========================================
  Files         116      113       -3
  Lines      145418   145157     -261
==========================================
- Hits       118395   118158     -237
+ Misses      27023    26999      -24

Impacted Files
Coverage Δ

src/ex_docmd.c
81.17% <ø> (+0.06%)
:arrow_up:

src/evalfunc.c
89.4% <ø> (-0.06%)
:arrow_down:

src/getchar.c
81.84% <100%> (+4.65%)
:arrow_up:

src/map.c
72.44% <72.44%> (ø)

src/viminfo.c
75.11% <0%> (-0.53%)
:arrow_down:

src/memfile.c
78.03% <0%> (-0.21%)
:arrow_down:

src/message.c
76.75% <0%> (-0.2%)
:arrow_down:

src/mbyte.c
66.1% <0%> (-0.2%)
:arrow_down:

src/term.c
79.12% <0%> (-0.06%)
:arrow_down:

src/json_test.c

... and 9 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 13d5c3f...1057b30. Read the comment docs.

Yegappan wrote:

Move mapping and abbreviations related functions into a separate file

I'm not sure we should do this, getchar.c isn't that big.
I rather look into splitting things off the very big source files.
--
If your company is not involved in something called "ISO 9000" you probably
have no idea what it is.  If your company is involved in ISO 9000 then you
definitely have no idea what it is.
(Scott Adams - The Dilbert principle)
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Hi Bram,
On Mon, Jul 29, 2019 at 12:04 PM Bram Moolenaar
<EMAIL_ADDRESS>wrote:

Yegappan wrote:

Move mapping and abbreviations related functions into a separate file

I'm not sure we should do this, getchar.c isn't that big.
I rather look into splitting things off the very big source files.

Before this change, the getchar.c file was 5389 lines long.
After this change, the file is 3179 lines long. The new map.c file
is 2332 lines long (including the code moved from ex_docmd.c).
The getchar.c file is in the top 25% based on the file size.
The map/abbr related code in getchar.c was already cleanly
separated from the rest of the code. So it was simple to move
that code into a new file.
Regards,
Yegappan


Enable passing flags related to Scarb rustlike features to snforge

Which components does the task require to be changed? (think hard pls)
snforge
Description
This will enable conditional compilation in snforge and be a workaround for part of #471 and https://github.com/software-mansion/scarb/issues/847 - users can just do (somewhere inside src folder)
#[cfg(feature: "enable_for_snforge_test_only")]
mod test_contracts;

and then call
snforge test --features enable_for_snforge_test_only

The logic underneath should be based on passing appropriate env vars to scarb build and scarb snforge-test-collector. The test collector logic needs to be updated accordingly.

Test collector part done in https://github.com/software-mansion/scarb/pull/1271


Interactive Window not working or displaying output

Received the following bug report from our docs team.
I’m running into an error right away when I try to repro the steps in the article.
I’m using Python 3.11 64-bit and I have the ipython and matplotlib libraries installed.
When I start the Interactive Window with the Use IPython interactive mode setting, I get the following error:

I tried to repro the steps for an Anaconda installation, and the output isn’t as expected.
After entering the code into the Interactive Window, an inline graph should display. In my test, no graph displays:

--- OR ---

I tried entering the code as a block input at a single prompt and also line-by-line. Neither method produced a graph or error message. The window just displays a subsequent prompt.
Here’s what the article says:

When I run the longer code straight from Visual Studio, the program opens a console window that simply says, Press any key to continue, which closes the window. No graph displays.
Here’s what the article says:

Another interactive window issue. https://github.com/microsoft/PTVS/issues/7968

I am experiencing the same issue with a brand new installation of Visual Studio Professional 2022 (64 bit) version 17.11.4 under Windows 11.
I have the default Python 3.12.7 environment installed.  When I try to use the Python interactive windows I have type $help and get keywords.  However when I type anything to be interpreted like Print("hello world"), or 3+5 iI see a spinning wheel and it hangs. It never recovers.
I have no issue doing the same thing from Windows Command Prompt.  It works OK there.


[Bug][C++][Test][Docker] Test Failure: Subprocess Terminated Due to Missing /etc/localtime Time Zone File in dev container

Describe the bug, including details regarding any error messages, version, and platform.
Description:
In the developer container, after building build-debug with the cpp library without modifying any code, an attempt to run the test test_orc_and_parquet_reader failed. The error message is as follows:
ValueOrDie called on an error: Unknown error: Time zone file /etc/localtime does not exist. Please install IANA time zone database and set TZDIR env.

Resolution Steps:

Install the IANA time zone database:
sudo apt-get install tzdata

Set the environment variable TZDIR to point to the location of the IANA time zone database:
export TZDIR=/usr/share/zoneinfo

After performing the above steps, the test can pass normally.
Issue:
The developer container should provide a ready-to-use environment for developers to complete all tests normally. Currently, the container is missing the necessary time zone file, which does not meet the expected purpose of the developer container.
Expectation:
The developer container should include a complete IANA time zone database when distributed, ensuring that all tests can run without additional configuration.
Notes:

The test failure occurred after building build-debug.
The test test_orc_and_parquet_reader failed due to the absence of the /etc/localtime time zone file.
After manually installing the IANA time zone database and setting the environment variable TZDIR, the test can pass normally.

Component(s)
C++, Developer Tools

Thanks for reporting, this will be fix as part of dev container image improvement as #495


Strange issue with C++ 20 feature(s) and system header discovery -- likely macOS specific

Hi awesome clangd folks,
Someone using the Bazel adapter I'd built ran into a strange issue with clangd and C++20.
I've cooked up a super minimal example based on theirs. We've got a simple main that uses a C++20 feature, std::construct_at. It looks like this:
#include <memory>

int main() {
    int i = 0;
    std::construct_at(&i, 0);
    return EXIT_SUCCESS;
}

It builds (and runs) fine with clang main.cpp -std=c++20. However, specifying that command in compile_commands.json leads to a red squiggly error: No member named 'construct_at' in namespace 'std' clang(no_member).
Curiously, changing the command in compile_commands.json to use an incorrect executable,  say chmod as an example of something obviously not a compiler, leads to things working, including successfully navigating to the definition of construct_at
Here's the compile_command.json file:
[{
    "file": "main.cpp",
    "command": "clang -std=c++20", // Change clang -> chmod for the curious case mentioned just above
    "directory": "/Users/cpsauer/Downloads/clangdIssue"
}]

And here's the whole thing zipped up for easy experimenting (though you'll need to change the directory in compile_command.json):  clangdIssue.zip
Any idea what's going on?
Thanks for reading and for all you do!
Chris
System information
Output of clangd --version: 13.0.0
Editor/LSP plugin: VSCode
Operating system: macOS 12

Could you try the following please:

In the working case (chmod in the command), follow the <memory> include, and take note of the full path of the opened file.
In the broken case, do the same thing. Is it the same path or different?

My hypothesis is that you may be getting different standard library installations in the two cases, though the mechanism by which that happens is not clear yet.
If you're using --query-driver, please mention its value as well (or better, the full clangd command line).

Hey, @HighCommander4! Of course.
The paths do indeed differ. Good call.
For chmod it's /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1/memory
For clang it's
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/memory
Setting some common SDK flags (as below) doesn't change this:
-isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk -F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks -F/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks

Re --query-driver: all of the above happened originally without. But after further fiddling, I can get things to work properly by whitelisting everything. That is, the (only) flag specified for clangd is --query-driver=/**/* This also changes the path above to match that for chmod that works.
In the clangd output it says:
System includes extractor: successfully executed /usr/bin/clang
	got includes: "/usr/local/include, /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/c++/v1, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/13.1.6/include, /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include, /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/System/Library/Frameworks (framework directory)"

That's definitely a good workaround, but I won't close because think clangd aims to auto-discover on macOS (per https://clangd.llvm.org/guides/system-headers#how-clangd-finds-those-headers), right?
Thanks so much for all your good help, Nathan :) I really appreciate you.
Chris

Very curious. I don't know enough about macOS to say how those two standard library installations might differ, but I'm guessing the "bad" one (the one in Toolchains/XcodeDefault.xctoolchain) might be an older version that predates the addition of std::construct_at in the C++20 timeframe.
By the way, I learned something about --query-driver today: if the compiler in the compile command is a relative path (e.g. clang), it's turned into an absolute path first (e.g. /usr/bin/clang), and that's what's checked against the --query-driver regex. So, if you find using a less permissive regex to be a slightly more palatable workaround, I think --query-driver=/usr/bin/clang should work.

Yeah, that seems to be what's going on.  still seems get a C++ 20 version of __cplusplus (202002L) and therefore gets a #define _LIBCPP_STD_VER 18 in __config, just like the other file, but I don's see a __memory subfolder or a construct_at.h
I mean, honestly, I'm pretty down to just have --query-driver on by default and to recommend that to our (mutual) users. Solves some other issues with Bazel wrapping compilers in shell scripts.
But I think in general clangd wants to work without --query-driver for clang on macOS, right?

My mental model so far was that, without --query-driver, clangd uses some default set of system include paths, but having read the guide you linked to above (thanks for sharing!), I now understand that clangd actually uses heuristics that still take into account the compiler from the compile command (just without executing it to query its include paths).
So I think that explains on a high level why having clang vs. chmod there makes a difference.
Assuming that chmod doesn't lead to any useful heuristics and causes clangd to use some fallback set of system include paths, which in this case are correct -- the fact that having the correct compiler (clang) there makes the outcome of the heuristics worse, definitely seems like a bug to me.

#487 might be related!

Have you tried providing full Xcode path to --query-driver=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/* parameter?
After I provided such parameter, the clangd stopped complaining about no_member stuff.
In my CMake generated compile_commands.json the command starts with /Applications/Xcode-15.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++.

Hi Matheuz! Thanks for engaging. --query-driver works (as above)--but this issue is about problems in the auto-discovery on macOS.


Badly handled unknown sessions

fixed with https://github.com/indigo-dc/oidcc_cowboy/pull/1 and https://github.com/indigo-dc/oidcc_cowboy/pull/2


Processing timestamps from DJI correctly

With the adjustment, the timestamps transmitted by DJI are processed correctly. A manual specification of the FPS is therefore obsolete.
The difference from the previous calculation of the timestamps is that video and audio now share a common basis. Previously, both were calculated separately.
The next step would be to find out how we can identify the required calculation at runtime, or make some kind of universal solution from it.
Therefore, it can initially only be activated via the debug settings. When the debug setting is enabled, the previous calculation and specification of the FPS are irgnored.

Is there a specification that says timestamps works like this? How did you figure it out?

If there is a specification, I would like to have it as well.
In the end, I figured it out through extensive research and experimentation. I examined each packet in Wireshark. A "calculated" timestamp is provided here. It is not possible to achieve the same result through the conventional method (when audio and video are treated separately). Instead, I get the same result when using the same basis as in the current implementation. I compared this with the verbose output in ffmpeg, and it matches.
It is also interesting that DJI initially only outputs video in the first buffers. Here, the expected PTS of 33 is provided. Once audio is added, the deltas of the video buffers become smaller, because audio PTS needs to be added.

Would be awesome if you can share the files and commands you used during your research. I want to verify it myself as well.

is a bit complex. First you have to install nginx with the RTMP module on your Mac/PC. then both following commands must be executed in parallel:
ffmpeg -i rtmp://<IP_ADDRESS>/live/stream -c:v copy -c:a copy -f flv rtmp://moblinip:1935/live/moblin
ffmpeg -i rtmp://<IP_ADDRESS>/live/stream -vf "showinfo" -f null -
compare number/pts from ffmpeg output und xcode debug output.
I'll send you a wireshark capture in discord.


mat-line elements do not style correctly when in

Reproduction
Any elements decorated with mat-line that are not direct descendants of mat-list-item do not style correctly. Our use case for this is rendering a list of items from a union type where we display different information depending on what type the item is; but below is a more trivial example.
Steps to reproduce:
<mat-list>   <mat-list-item>
Foo
     <ng-container *ngIf="fooHasChanges">
Changes

             {{change.value}}
     </ng-container>   </mat-list-item> </mat-list>
This appears to be related to https://github.com/angular/components/issues/5502
A similar fix for mat-grid-list was implemented here https://github.com/angular/components/issues/12809
Expected Behavior
The elements are styled correctly.
Actual Behavior
The elements are not styled correctly and render on the same line as the previous mat-line.
Environment

Angular: ^8.2.14
CDK/Material: ^8.2.3
Browser(s): Chrome latest
Operating System Windows

This should've been fixed all the way back in the 8.0 beta versions by #15552.

Simple recreate - https://angular-vgupch.stackblitz.io

It's because we expect the mat-line to be projected in a specific place, but that doesn't match anymore once you wrap it in an ng-container. You can fix it by adding ngProjectAs="[mat-line]" on the ng-container.

Thanks for the feedback but not sure why this issue was closed. The unit test committed in https://github.com/angular/components/pull/15552/commits/a42efc63a0614b0432ee08fbffa551c8fa6658c0 uses ngSwitch as opposed to *ngIf so I'm guessing this comes down to how content is projected under those 2 directives.
Your suggestion to use ngProjectAs would work but at that point you might as well put the structural directive on the element itself. This becomes cumbersome when you're wanting to render multiple mat lines under a single condition (as your unit test does).

I closed the issue, because this is how the framework works. Inside the list item we have a <ng-content select="[mat-line]"> which means that it's looking for a mat-line that is a descendant of the item. When you wrap it inside an ng-container that selector won't match anymore so the line will be projected in the wrong place. Even though ng-container doesn't really "exist" at runtime, it's still another layer at the time projection happens (it's basically the same as if you'd wrapped the mat-line in a div).


[JOSS Review] Repository License Issues

As part of the JOSS review, openjournals/joss-reviews#6138, this repository needs to have an OSI approved license. While this repository does have a license listed, I am worried about the license issues of including the KUKA FRI SDK in this repository.
This also appears to be related to #6 and #14. Please fix this issue using at least one of the methods suggested in your existing issues.

Putting for reference https://joss.readthedocs.io/en/latest/review_criteria.html#software-license

added notice https://github.com/lbr-stack/fri/blob/fri-1.15/NOTICE


Added is_full function to BinaryHeap, IndexMap, IndexSet and LinearMap

This function is already implemented for some data structures, so having it everywhere makes the API more consistent.

Clippy check is failing because of errors not related to this PR.


[Question] JNI bindings for xi-editor

Running xi-editor as a separate process makes development of frontends on mobile platforms almost impossible. For instance if I want to consume xi as a backend on android, I have to pre-package it and start as a standalone process. Unfortunately, there is no non-hacky way to spawn a process from the application on Android.
Hence, one of the most feasible approaches would be to compile the xi-core along with the application and communicate with it through JNI (Java Native Interface). Is it possible to separate out the IPC part of xi and use direct function calls instead? Is it something what core-lib does?
Another question which I have is related to the fuchsia fronted for xi. In the readme of the project, there is a mention on how to build and run the app on Android. The part related to xi seems not very clear to me. The only action described is a command to send the binary over adb to device's data/local/tmp/ directory, which seems to be a hack? Is there any other way for integration into android?
Thank you very much.

@ArazAbishov You're right that there are definitely some barriers to developing mobile frontends right now; on iOS, you can't launch subprocesses at all. The way I would imagine getting around this is using core-lib as a static library, and running it in a pthread. Plugins would also need to support being used as libraries. This would require a bit of work, but should be generally doable.
I can't really help much on the fuchsia stuff, unfortunately. :(

@cmyr Thanks for the fast reply. Do you think those changes are aligned with the future of the library? I will be glad to contribute, but I don't want to maintain a fork :)

Hi @ArazAbishov!
 I'll see if I can address them, but feel free to follow up.
First, the architectural choice to have the front-end and core in different processes is not rigid at all, and if you look at xi-win you'll see that it's all one process, with the core running in a thread. That was one of the motivations (along with Fuchsia's needs) why core-lib was separated into a library rather than always running as a binary with its own "main." I'm very open to changes to better support that.
As @cmyr mentions, the question of plugins is more complicated, as architecturally I do imagine these being pretty separate modules. However, for the plugins written in Rust (currently syntax highlighting) I can easily see a packaging technique that runs them in threads, perhaps even with some care taken to catch panics.
The Android port in the Fuchsia front-end does provide basic editing functionality, but at this stage it's there mostly for prototyping and development purposes. When it was written, the compile-edit-run cycle was much shorter for Flutter-on-Android than Fuchsia. The latter is improving to the point where it might make sense to only maintain the Fuchsia port. That said, it is a viable path to getting a working editor on both Android and iOS in addition to Fuchsia.
Sending the binary over adb is definitely a hack, but effective for development/prototyping. It's certainly possible (but not mainstream) to package a binary that can be run in a separate process, but that would be an Android-only solution. If this were to be further developed, it would probably make more sense to have it in a library as you suggest. On Fuchsia, though, it's likely to remain a separate binary (I can go into my thinking on that, but it's probably beyond the scope of this issue).
Short answer, I'm open to collaborating with people on a mobile experience. There's a bunch of work to be done on integrating the build and getting a sane development environment set up, in addition to the front-end work itself, so happy to have people willing to work on that.

Hi @raphlinus,
Thanks for the elaborate answer. I will take a look into xi-win for inspiration on how to consume core-lib APIs. I guess next challenge will be compiling and linking the xi-editor into android project and writing JNI bindings for it.
A quick question: is the version 0.2 latest "stable" release? I have seen that a lot of changes have been merged into master since then. This is quite important since one has to decide either to build xi from sources or just by consuming a crate through cargo. In case if crate is stale, the choice is quite obvious :) This also might greatly simplify the integration into build systems like gradle.

@ArazAbishov No, 0.2 is just a snapshot, development is done from master. There's currently nothing forcing us to do releases more regularly, but it would be a good idea to release more frequently, as, among other things, it updates the docs.
Best of luck, and let me know as you have more questions. Also feel free to make use of the #xi channel on irc.mozilla.org.

@raphlinus Publishing the snapshot on each commit to master might be very useful, but that is probably something what goes beyond the scope of this issue.
Thanks and talk to you later on irc!


apollo-link-error seems not to be imported

Documentation (https://github.com/bgentry/ember-apollo-client#apollo-service-api) mentions use of onError, which I believe is exposed by apollo-link-error. However it seems not to be imported by ember-apollo-client. Should this be fixed, or it's meant this way so I included on my side if I need it?

Some one on my team reported something similar to me but I still haven't found to take a look at it to see what's going on. README says that theses dependencies are exposed by this addon:

apollo-client
apollo-cache
apollo-cache-inmemory
apollo-link
apollo-link-context
apollo-link-http
graphql
graphql-tag
graphql-tools

Seams like apollo-link-error is not exposed by default. You probably need to follow the configuration steps to include optional packages support.

Yeah, that's what I did basically. I just included apollo-link-error, which was super easy with ember-auto-import, and it worked.

Should we wait for a decision about auto-import thing (#145) ?

@viniciussbs I haven't had the time to look at #145 and probably won't be able to do so in the near future, though I am always open to others doing so. No need to wait for it, you'd just be adding another package to the list.

Closing this old issue, please reopen if still a problem. Also PRs welcome if so :)


GSD Request

--- GSD JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v3.14 to before v4.14.265",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ba7d49b1f0f8e5f24294a880ed576964059af5ef",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=7d9211678c0f0624f74cdff36117ab8316697bb8"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "ba7d49b1f0f8e5f24294a880ed576964059af5ef",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "7d9211678c0f0624f74cdff36117ab8316697bb8",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.14.265 by commit 7d9211678c0f0624f74cdff36117ab8316697bb8, it was introduced in version v3.14 by commit ba7d49b1f0f8e5f24294a880ed576964059af5ef. For more details please see the references link."
}
--- GSD JSON ---

This issue has been assigned GSD-2022-1000107


What is the role of "abc_parser" here?

According to what I know, on Oct 30, 2017, in GIT version #927, cghawthorne add an "abc_parser" to music API.
So what I want to know is that is the "abc" is a kind of music, or some else?
Are there any README related to it ?

It looks like it's a parser for abc notation, which is kind of like MIDI, but simpler and more readable.

That's correct, it adds support for ABC files to the NoteSequence converter. I'll update the README to mention this.

Yeah, thanks very much for your kindly reply. @superMDguy @cghawthorne


Documentation Update of Identity Server - Username Recovery

The service caller can define any number of claims that should be used in the user details verification. But when defining the claims make sure to define a unique user attribute (claim) or a unique composite user attributes (multiple claims) as can identify the user separately.
To define the claims need to follow the steps below.

Login to the Management Console and list the claims.
Click on http://wso2.org/claims and find the relevant claim.
Edit the relevant claim and mark as Supported by Default and then Update.

Need to update [1] documentation with the above information.
[1]. https://docs.wso2.com/display/IS550/Username+Recovery

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


correct service names

use a / instead of : cause thats how the service names are declared in the respective config files of coordinator and overlord

:+1:

it seems integration-tests also use the old service names and use ':'
e.g https://github.com/druid-io/druid/blob/master/integration-tests/docker/middlemanager.conf
@pdeva can you also update them to use the new convention in this PR ?

:+1:


Add src

Best practices

Good job so far. The code works ;) There are some things that could be improved


TypeScript: compilerOptions.types not respected when using project references

VSCode Version: 10.27.2
OS Version: macOS 10.13.6

Steps to Reproduce:
Full reproduction case

Given a tsconfig.json that has project references, where the referenced TS projects specify a custom compilerOptions.types
Open a file inside one of the referenced projects

Expected: VSCode should respect compilerOption.types.
Actual: VSCode appears to ignore compilerOption.types.
For example, I have three TS projects:

tsconfig-src.json which should not have jest types (compilerOption.types is set to [])
tsconfig-tests.json which should have jest types (compilerOption.types is set to ["jest"])
tsconfig.json which references both of the above

The following file is part of the tsconfig-src.json project:
// src/sum.ts

test('foo', () => {})
// Expected: error in VSCode and when running `tsc -b`
// Actual: no error in VSCode, error when running `tsc -b`

export function sum(a: number, b: number) {
  return a + b;
}

When I run tsc -b -f tsconfig.json, I get the expected error:
src/sum.ts:3:1 - error TS2304: Cannot find name 'test'.

3 test('foo', () => {})
  ~~~~

(test is a global type provided by the jest types.)
However, VSCode has no error. Instead, the types appear to be available, even when they shouldn't:

You can try this for yourself with the provided full reproduction case.

This issue was moved to Microsoft/TypeScript#27372


Hope to add some url matching rules.

Now

Hope
Add StartWith, EndWith etc.
Even if they can use RE to achieve

The "Normal" pattern is actually matched by "includes", so if you want to take "StartWith" or "EndWith" as the condition, it should meet the requirements
switch (type) {
    case "normal":
        matched = url.includes(match);
        break;
    // ...
}

Thanks!


After setting chat_id the bot stops to response

I get my chat_id, put in knows_ids list and after that the bots says: "DESKTOP-01: I'm up." DESKTOP-01 is my pc that are running the server, but i can't send nothing for him...  I'm gonna need more than that

See: The bot says: I'm up! But when I send a message from the same computer as the server, or from the phone him don't respond.

That is fairly strange. It outputs <Divide>PC.

That is fairly strange. It outputs <Divide>PC.

It's because I typed the '/pc' on Telegram window.
É porque eu escrevi '/pc' na janela do Telegram.

I must ask, have you double-checked that chat_id is really your chat_id?

Yeah. I double checked with @my_id_bot he answered the same id.

I rarely work on this project anymore but I'd try and fiddle with the known_ids list if I were you

The problem was that I had put the id as int not as string. After put as string worked as expected.

Good idea, happy you solved it. May I close this issue?
Sent with GitHawk


[Event Request] Codeunit::"Whse. Validate Source Line" - Function SalesLineVerifyChange - OnBeforeSalesLineVerifyChange

We like to request the following Event:
Object: Codeunit::"Whse. Validate Source Line"
Function: SalesLineVerifyChange
Publisher Event: OnBeforeSalesLineVerifyChange
Reason: To implement custom business logic
Where is the event placed:
procedure SalesLineVerifyChange(var NewSalesLine: Record "Sales Line"; var OldSalesLine: Record "Sales Line")
var
NewRecRef: RecordRef;
OldRecRef: RecordRef;
IsHandled: Boolean;
begin
OnBeforeSalesLineVerifyChange(NewSalesLine, OldSalesLine, IsHandled);
if IsHandled then
exit;
if not WhseLinesExist(
DATABASE::"Sales Line", NewSalesLine."Document Type", NewSalesLine."Document No.", NewSalesLine."Line No.", 0,
NewSalesLine.Quantity)
then
exit;
Event Code:
[IntegrationEvent(false, false)]
local procedure OnBeforeSalesLineVerifyChange(var NewSalesLine: Record "Sales Line"; var OldSalesLine: Record "Sales Line"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Feature request: allow line breaks after custom characters

Hi,
I have a use case where file paths are displayed in a multiline label. It would be great if line breaks could be configured to also be permitted after directory seperators ('/' or '', depending on the plattform), or other characters for custom use cases.
As far as i can tell, the getNextLine method of the WidthTextLayout class would need to be altered (along with some constructors to pass this option down), but since the class is final, i can not extend it.
Would you consider implementing this feature?

Thank you for reporting this. I'll have a look.

Hi! I released a new version 1.19 which includes a support for custom separator characters. Please try it and let me know if it works for you.


HSEARCH-2548 Upgrade to Hibernate ORM 5.2.7.Final

it's missing documentation, I can't do that today but it would be nice to warn people attempting the same about needing to use a jboss-deployment-structure.xml to exclude javassist. Opening a follow-up jira.

Nice! Merged.

@Sanne By the way, the ticket states "When doing this, consider removing the workaround for issue HHH-11309: we added ByteBuddy to the OSGi dependencies in the features file as it was not listed optional.".
Did you decide against removing the workaround?

right, I decided to not remove that. Sorry should have commented.
By keeping bytebuddy people can choose if they want to use it ;)


Store OSX artifacts with release

So that we can use them for system tests as well

Let's focus on Linux environments (for CI).
The upgrade test has a build flag so that it is ignored on other systems. I would add some notes how to make it work on OSX by building artifacts locally


Style Delete Icon "X"

Add some sort of Trashcan icon.

note: If importing a whole icon library, try to just grab the icons and wrap them in a react component.

Have this icon only become visible on hover and don't have the sibling elements move when it does.

extra credit, and some sort of animation :)

---- much ❤ to the person who does this!

I'd like to work on this issue!

@rriikkuu Are you working on this ??

@lapmid yup

i merged the one from @itsnhduc, but there is a small font-smoothing issue if either @rriikkuu or @lapmid would like to take it :)

Could you elaborate further on the issue?

Humm, i think it was just cause i was connected to a 4k monitor, but the trash cans looked fuzzy, regardless, it's not an issue anymore!

@itsnhduc I actually found something different that I would love your assistance with!
Checkout the this gif...

You can reproduce this by adding an exclusion date of the same date...
Any ideas?

I'm aware of this. I previously assumed that there will never be 2 entries with the same item.datesince you're using it as a key for ExcludedDate. If this is to be fixed you're gonna need a new key, either the index of item or a new key attribute. Which one do you prefer?

Yeah, it doesn't make sense to have multiples of the same date...
Ideally it would:

Prevent the user from making the exclusion date
Put the Reason why in an error banner

I guess doing step 1 would be preferred.

Then this should be a new requirement. Sure I can go ahead and implement this but I think it's better to open this as a new issue and let other folks who haven't completed their Hacktoberfest PRs take care of it.

will do, thanks for contributing @itsnhduc :)


Add mapfish print chart

Introduces a helm chart for mapfish/mapfish-print.
Main configuration options:

storage.printConfigDir: Where to mount the print apps dir.
storage.printAppsUrl: (Optional) External link to a compressed print apps archive (.tar.gz). The data will be extracted during startup.
extraEnv: Map of additional environment variables passed to mapfish print.
extraEnvFrom: Pass additional environment variables from secrets, configmaps etc.

@terrestris/devs Please review

Thanks for reviewing @dnlkoch and @ahennr !


Fix PR template

Overview
Fix links to Contribution Guide in PR template.

Definition of Done

[x] Change is covered by automated tests
[x] The coding guidelines are followed
[x] The continuous integration build passes

I think absolute path would be better


Rename content/github/index.md to content/github/Aof1983/docs

Why:

Closes [issue link]
What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

21 Nis 2021 Çar 19:36 tarihinde Fatih @.***> şunu yazdı:

@.**** approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/5597#pullrequestreview-641306525,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATU4LVWL6ZBOCLA3RRYEUE3TJ35HLANCNFSM43KUI4FA
.


Scene.getMeshesByTags doesn't use argument predicate as filter

Documentation states:

getMeshesByTags(tagsQuery: string, forEach?: ((mesh: AbstractMesh) => void)): Mesh[]
forEach: ((mesh: AbstractMesh) => void)
defines a predicate used to filter results

This code clearly doesn't filter using forEach:
        for (const i in list) {
            const item = list[i];
            if (Tags && Tags.MatchesQuery(item, tagsQuery)) {
                listByTags.push(item);
                forEach(item);
            }
        }

https://github.com/BabylonJS/Babylon.js/blob/8a5077e0efb4ba471d16f7cd010fe6124ea8d005/packages/dev/core/src/scene.ts#L5229C1-L5235C10
On a side note: I'd argue the argument forEach should just be removed. In the current form the workaround using filter on the return value is also the better approach than passing a predicate.

I think this is a documentation issue with the forEach, even the argument name seems to indicate it was never used for filtering in first place (is it correct @deltakosh ?). The documentation should read instead: "function applied on each result".

@carolhmj I would bet on the predicate and a bug here :-) Do you want to create a PR for the fix ?


IOS error

Good. When generating a pass with the app on android it works perfectly for me both when I download it and when I open it. But in ios it fails me, in the download safari it gives me an error and if I do it in android and I send it by email to ios it doesn't open either. but in android it is perfect, I don't know why.
http://pk-pass.herokuapp.com/rentingpass/

Console on Mac gives me the following error when opening a pass created via your web app:

Have a look at the README for instructions on how to debug issues on Mac.

Repair the error but on iphone it still doesn't work well.

There might be another error in your JSON, or there might be something wrong with your signing certificate. The Console app on your Mac will show you the exact error message.

Tengo una duda. Es necesario sustituir el archivo .pem?

I have a doubt. Do I need to replace the .pem file?

What error is the console showing you?

Perhaps p12 certificate has not expired?

Everything is correct. The problem was in the pass, which was wrongly created by those who keep the apple account and named it. Now it works perfect. Thank you very much and sorry for the inconvenience.

Great to hear! Thanks for using this library 👍


[dynamic child objects][cleanup] Remove creation of locks for child objects

Child objects are no longer valid transaction arguments
They do not need locks? I think

They do not need locks? I think

For now, they don't, because our object store has read-after-write consistency. But this may not always be so. If we ever want to use eventually consistent object storage, we will have to have locks for child objects (owned locks will always require read-after-write). But that's not really something we need to worry about in this PR, there are many things that will have to change if we ever make that change.

They do not need locks? I think

For now, they don't, because our object store has read-after-write consistency. But this may not always be so. If we ever want to use eventually consistent object storage, we will have to have locks for child objects (owned locks will always require read-after-write). But that's not really something we need to worry about in this PR, there are many things that will have to change if we ever make that change.

@mystenmark, are you good with this landing then? And can you make sure I got all the spots I needed? I'm not very familiar with this part of the codebase.

@tnowacki i think there are a few other places that could use attention:
https://github.com/MystenLabs/sui/blob/826315b2fffb09011a25611f09df46a89850f119/crates/sui-core/src/authority/authority_store.rs#L549-L553
https://github.com/MystenLabs/sui/blob/826315b2fffb09011a25611f09df46a89850f119/crates/sui-core/src/authority/authority_store.rs#L596-L598
https://github.com/MystenLabs/sui/blob/826315b2fffb09011a25611f09df46a89850f119/crates/sui-core/src/authority/authority_store.rs#L634-L636
Most of these are special case paths for genesis or gateway. Probably nothing bad will happen if we ignore them, but it couldn't hurt just to filter child objects out in these cases as well.

Thanks for the pointers, @mystenmark! Updated with checks in 2/3 of those spots. The remaining spot could not be checked, but child objects should already be filtered (and commented as much).


Specify Cocoapods version

Feature Request
A lot of pain can be avoided if you add a version field to cocoapods lane.  https://docs.fastlane.tools/actions/cocoapods/
Motivation Behind Feature
I tried to add a comment to https://github.com/fastlane/fastlane/issues/3671 and several other similar but is locked to collaborators.
I am not a ruby dev, I love fastlane for it's convenience in automation....
Yesterday, our builds started failing at a bad time.  It was due to a new version of cocoapods being available, fastlane cocoapods uses the latest.
I tried to follow these steps to lock down the cocoapods version:

To achieve this, you should use a Gemfile as described in the CocoaPods docs. This way you specify the actual dependency which is being resolved using bundler 👍

Worked fine on local machine, but on remote cd, all hell broke loose.  First I needed to get the correct bundle to match my Gemfile.lock.  Then, I think due to a react native project and a bit different directory structure than standard ios, fastlane called cd ./ios && bundle exec and bundle could not be found.
After hours of trying to become a ruby dev, I gave up and used the CD (Bitirse) services' run cocoapods step.
I have always though of fastlane as an easy tool to use, and not yet another dev time sync.
Feature Description
If it isn't too much of a lift, it would be very nice to be able to specify version of cocoapods.
cocoapods(podfile: './ios/Podfile', version: '1.7.1')

Alternatives or Workarounds
Become an expert at ruby or use cd's cocoapods step.....

I currently use the following setup to specify the CocoaPods version:

RVM
Bundler

When CI checks out a new commit to the repository, it first runs bundle install, so it mimics the exact setup I have on my local machine.
In case I update CocoaPods locally, (and only in that case) and commit that change to the repository (via Gemfile.lock), the CI machine would download and install a new version.
Also, what's interesting, some older branches can run in parallel with the newer ones which might use different versions of CocoaPods while both integrated on the same CI machine.

@JayCantyEMoney Heyyy 👋 Using bundler is the best and coorect answer here like @richardtop has mentioned 👌 Lock the versions in your Gemfile, run bundle install, and run with bundle exec fastlane <platform> <lane> and you should be good 💯
Issues like this is exactly why bundler was made and is highly used in the ruby ecosystem 💪

Also worth to note that it is just not possible to use a version option for the cocoapods action to specify which version should be used, as the action just uses what ever pod is installed and available on the machine you are running on. If that is a specific one via Gemfile and bundle install, then is uses this - otherwise whatever it finds.
@joshdholtz Wouldn't this also require to use the use_bundle_exec option for cocoapods though?


Anchor Links not Working if inside a div with overflow-x : scroll

I am not able to get this working for my project. Here is the link to the code.
If I remove the overflow-x from SubCategoriesWrapper component, then the links work fine.
Thanks in advance.

I have the same issue if i use div with overflow:auto to wrap the Link component, it will not working, I tried to add overflow with setTimeout function but the spy will no response. any idea to fix this issue?
thank you very much in advanced

Same here too 🙁

Reproduction example:

I do believe I've solved this, but I haven't published anything.
Can you try with the latest commit?
https://github.com/fisshy/react-scroll/commit/974ae313d5b4eb4feac00338f6293727977ec3ef

Great! I'm trying it right now ;)

Your example does work, but it doesn't use overflow-x.
If I use the following style on nav, it breaks:
.nav {
  position: fixed;
  top: 0;
  width: 100%;
  background: #ededed;
  overflow-x: auto;
}

If I return the document instead of parent, it works:
if (
    overflowRegex.test(style.overflow) ||
    overflowRegex.test(style.overflowX)||
    overflowRegex.test(style.overflowY)
  ) {
    return document
}

Ah I see,
I'm thinking of removing auto finding overflow-parent, I think setting the container is good enough.

Indeed, I didn't understand the logic at first: actually just removing the check about overflow is fine. But I'm not sure of what it was there in the first place.

I did some changes, can you try this commit.
Now fallbaking on document if containerId isn't set.
https://github.com/fisshy/react-scroll/commit/8e9757cd325e148583693a440f30c4cb537f44e6

Looks good to me! 👍

Do you plan to bump a new version soon?

Yes, hold on! :)

v1.6.5 is now out

Thank you really much, my issue is resolved now 🎉

No problem, glad to help! :)


Ruby group capstone - Catalog of my things 🎯

Milestone: First working version of the project
The following changes are being introduced:

Used the UML class diagram provided to create the required classes and associations between classes in separate files.
Followed the diagram to create the methods within the respective classes.
Added unit tests for all implemented methods
Created a main.rb file to serve as the entry point of our console application
At the start, the console app does the following:

Presents the user with a list of options to perform.
Lets the user choose an option.
If needed, ask for parameters for the option.

The app presents an option to quit.
The options presented are as follows:

List all books
List all music albums
List all movies
List of games
List all genres
List all labels
List all authors
Add a book
Add a music album
Add a game
Add a movie

All data from the book, music album, game and movies is preserved in files using .json format.

@elisha2kyakpo1  Thanks for understanding and approving our project.. Means a lot!..🙌😄

Thanks man for the Approval @elisha2kyakpo1


Add a max height to the chat window

Also give it square filled style to make it clearer.
You can try it out at https://chat-input-max-height.dev.karrot.world/#/group/6/issues/16/chat.

Seems nice!

Detail sidebar (application chat, pickup chat and threads) could potentially also have this style?
maybe add a changelog entry?

Done!


Server doesn't show up after changing master Server Data

Version Number and Operating System(s):
27.01.19-20:00:44,13
Windows 10 (v.1809)
Expected behavior:
Show server in the Server Browser
Actual behavior:
Server doesn't show up.
Code stops at ServerBrowser.cs > Line 92
Steps to reproduce:
Change the master server data after MultiplayerMenu.cs >Line 200
[Optional] Discord Username:

Discord username: @Corey#7494

Could you provide more detail please?
Does the server show up on the master server's command line output?
MultiplayerMenu.cs line 217 is a {. (https://github.com/BeardedManStudios/ForgeNetworkingRemastered/blob/7fd06aaf8f937074f9b593091ce05c5cf5d13498/Forge Networking Remastered Unity/Assets/Bearded Man Studios Inc/Scripts/Multiplayer Menu/MultiplayerMenu.cs#L217)

Have you updated ServerBrowser.cs on line 16 to match the gameid to the above serverId you set?
The master server will only return hosts that have the same id.

Nope, i did not! Thanks, that was the problem.


libgit2-sys 0.13.3 version issue

It looks like the version scheme does not match what is specified in Cargo.toml
https://github.com/rust-lang/git2-rs/blob/9d33858b649f2a2e930c841a53a7d99c21354856/Cargo.toml#L23
This caused some build issue:
error: failed to select a version for the requirement `libgit2-sys = "^0.13.3"`
candidate versions found which didn't match: 0.13.2+1.4.2, 0.13.1+1.4.2, 0.13.0+1.4.1, ...
location searched: crates.io index
required by package `git2 v0.14.3`

You'll need at least Rust 1.60.
@joshtriplett Perhaps we should yank the release and move #833 to the next semver release (0.14)?

noted about the rust 1.60.0
but i guess the semver issue might be still valid?

@ehuss Just libgit2-sys, not git2? That probably wouldn't be too disruptive, since people don't tend to depend on libgit2-sys directly and use its types.
However, I'm not sure that'd actually solve the problem. Wouldn't Cargo still fail to find a matching libgit2-sys for 0.14 just as it does for 0.13.3?

Nah, I think it would need to be both git2 and libgit2-sys.
Yanking isn't a full solution. If we make a new semver bump and a user tries to use git2 = "0.15" with an old rust version, it will run into the same issue.
This is one of the hazards of using this new syntax. My personal feeling is to wait at least a few months before switching to new stable things to reduce the likelihood of someone running into this kind of problem. But every project has its own guidelines.

git2 0.14 was already rather disruptive; I'm hoping we don't need to move to a new semver-breaking version anytime soon.
I can see another possibility that would eliminate this particular issue: we could yank the latest git2 crate, and upload a new version of git2 that uses weak dependency syntax in git2's Cargo.toml as well (even though it isn't strictly needed). That would avoid the problem of people seeing the new git2 but not the new libgit2-sys; any Cargo capable of finding the new git2 would also find its dependencies.

I get the same issue with the latest git2-0.14.4:
error: failed to select a version for the requirement `libgit2-sys = "^0.13.4"`
candidate versions found which didn't match: 0.13.2+1.4.2, 0.13.1+1.4.2, 0.13.0+1.4.1, ...
location searched: crates.io index
required by package `git2 v0.14.4`

Is there any workaround for this? I just can't build a test project after just adding git2 = "0.14.4" into [dependencies]

I get:
error: failed to select a version for the requirement `libgit2-sys = "^0.14.0"`

Which is true, this version does not exist.
What's on there is: 0.14.0+1.5.0
See: https://crates.io/crates/libgit2-sys/versions

"w_e're_ here"

and i mean, NEAR is almost the heart of "npm ... dash use rust instead ..."


About dataset

Dear author, in your paper, you mentioned that you treated the mug as a symmetric object when the handle is unseen. But how to get handle the visibility of mug in real-test dataset? Thanks very much.

The visibility of handle is provided by the original dataset. You may refer to NOCS.

Hi @mentian , thanks for your reply. I can only find visibility information in val dataset. The origin test dataset only provides pose information and image path. Do I miss something?

Some of the data in original test might miss the visibility information. Please refer to this line and the following code block for how NOCS handle the visibility information.
In our implementation, we directly copy the visibility information form the detection results of NOCS here.
If you prefer a quick solution, please download the zip file provided in "Section Evaluation of README". This file contains the detection results of NOCS, which contain the handle visibility for each image of both real test and val dataset.

I see, I will figure out how to do it. Thanks for your detailed answer.


Add feature flag for setting up wireguard on configservers.

After looking at this, I think it's actually a good idea to have two feature flags - one for config servers (like here) and one for tenant hosts (which may have different dimensions, i.e. tenant). Go ahead and just merge this and we can look at the config server case first.


Survey contributor analysis products for DCP1 projects

Task: Locate & assess processed/analysis data products pertaining to the existing projects.
While gathering HCA stakeholder feedback, we heard a lot of support for the DCP to start taking contributor processing/analysis products. This task will also help the DCP start to get a general understanding of what kind of variation we will experience (file formats, references, software, etc.) and can lead to standards and a schema. This will also facilitate the submission of those products once the DCP is capable of hosting them.

Assessment of DCP1 projects: https://docs.google.com/spreadsheets/d/1Qtbut2-yL2i7mPfN6gd154i255BzteX0gCTG9kPHOwc/edit?usp=sharing
SURVEY OF DCP1:
This tab lists the current projects in DCP1 and the following information:

DCP1 URL
DCP1 Matrix for entire project:
There is a matrix for the entire project (value == TRUE), or there is raw sequence data that does not have a corresponding matrix  (value == FALSE).
Broad pipeline available for non-analyzed data:
All data has been analyzed (value == NA), there is no approved Broad pipeline for the non-analyzed data (value == FALSE), or there is an open ticket to run data through pipelines (value == ticket_url from secondary_analysis)
Matrix available in public domain:
There is a matrix available for download in an public repository (value == TRUE), or the matrix for the project is unavailable in the public domain (value == FALSE)
Publication:
There is no publication available for project (value == NA), there is no publication listed in the project page but a publication has been found (value is written in red), or there is a publication found (value == url)
Public domain accession: Accessions where data from the project is available

DEEP DIVE:
This tab lists 3 projects where the analysis process and products were evaluated and summarized. Analysis products include alignment, quantification, expression, dimensionality reduction, cell, cluster, and QC metrics.

I was able to find 4 publications for ones that were marked otherwise (at least I think I did). Those should be verified & see if they point to a matrix in the public domain. The relevant cells are marked in read and publications are linked in the Months since published column

@jychien , please also double-check the details I left in the Broad pipeline available for non-analyzed data column for why it can't be run.

Thanks!