fix: store eof bytecode with header in compact

Cherry-picked from frontiers changes

Will adjust the test after I open up the remaining cherry pick PRs and create a follow up issue to resolve before Prague is live

@onbjerg requires revm bump?

yep..

Superseded by https://github.com/paradigmxyz/reth/pull/10537


Add Version on the web UI

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


promql: allow . in metric names

Tests pending.
This would allow people implement PromQL on datasources that also support metrics with . in their name. We are the only system I know of that doesn't allow . and given how many systems want to integrate with PromQL, I think it only makes sense to give them a way to do so.

This change is

I'm against this change. It adds complexity to the code for something that is of no use to Prometheus and will cause us additional support load and also limits us for future changes.

As this could touch namespacing, also see here: https://docs.google.com/document/d/1q7HSZyRv4Ay4hTlva4uy8WPh5WlYv9S0Yy-xQS2vKo4/edit @ 2018-02-13

To me the fact that metric names can't include ., meaning that getting a very specific metric/timeseries requires the metric name and some set of labels, makes it much easier as a user to find out which metrics are available. Supporting the . naming format is a step backwards imo.
The naming format that Prometheus uses is one selling point over systems that allow . in the name and use that as a way to get to a specific service/series/error number/etc.

This PR is not about changing the Prometheus data model, it's about whether we should facilitate systems with other data models in our code.

@brian-brazil I know. I was just pointing out that the current data model is a plus that we have over other systems data models. The same way that we discourage users from using the push gateway for all of their metrics, because Prometheus is designed to use a pull based model, supporting the . style metric names would put us in a situation where a significant amount of users may never use the intended name + labels data model. At least, that's what I would suspect would happen.

I agree on those benefits, and there's others too but that's beside the point. This PR is not the direction we're going in.


about the need to update SDK

Hello,
Last week Microsoft announced the following information.
Is it necessary to update the SDK library for CCv4.1?
https://azure.microsoft.com/en-us/updates/update-your-azure-sdk-libraries-of-net-and-golang-by-30-september-2023/
Regards,
(CC: @ATshirai)

Thanks @MK202204  for highlighting this we will review it and keep you posted.

@MK202204 , this has been added to our backlog list and will be planning to implement it in future releases post the discussion with our internal team. For now, we are closing this request as we have provided the inputs for the query raised. If you face any issue with company communicator please raise a new issue for further assistance.


Function Pod doesn't come up when requirements.txt is used for dependencies

If we use requirements.txt with dependencies defined in it, 'serverless deploy' gets stuck with pod at Init state.
Dependency mentioned in requirements.txt is not even used in my handler.py. And if I just delete requirements.txt file from service folder, everything starts working, function gets deployed without any issues.
mongo-connect-7dfb4868f-crt96                             0/1       Init:CrashLoopBackOff   4          5m
handler.py
def mongoConnect():
    return 'Connected to MongoDB'

requirements.txt
pymongo==2.7
serverless.yml
service: mongo-utils

provider:
  name: kubeless
  runtime: python2.7

plugins:
  - serverless-python-requirements
  - serverless-kubeless
functions:
  mongo-connect:
    handler: handler.mongoConnect

custom:
  pythonRequirements:
    pythonBin: C:\Python27\python.exe
    invalidateCaches: true

Serverless Commands:
C:\Users\myusername\workspace\devopsinsight\functions\mongo-utils>sls deploy
Serverless: Installing required Python packages with C:\Python27\python.exe...
Serverless: Linking required Python packages...
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless: Unlinking required Python packages...
Serverless: Deploying function mongo-connect...

Pod logs:
C:\>kubectl logs mongo-connect-7dfb4868f-crt96
Error from server (BadRequest): container "mongo-connect" in pod "mongo-connect-7dfb4868f-crt96" is waiting to start: PodInitializing

Function pod describe:
C:\>kubectl describe po mongo-connect-7dfb4868f-crt96
Name:           mongo-connect-7dfb4868f-crt96
Namespace:      default
Node:           cmbu-devops-services-kube-node2/<IP_ADDRESS>
Start Time:     Thu, 28 Dec 2017 21:38:38 +0530
Labels:         function=mongo-connect
                pod-template-hash=389604249
Annotations:    kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"default","name":"mongo-connect-7dfb4868f","uid":"96ba80eb-ebe9-11e7-b07f-005056ac...
                prometheus.io/path=/metrics
                prometheus.io/port=8080
                prometheus.io/scrape=true
Status:         Pending
IP:             <IP_ADDRESS>
Created By:     ReplicaSet/mongo-connect-7dfb4868f
Controlled By:  ReplicaSet/mongo-connect-7dfb4868f
Init Containers:
  prepare:
    Container ID:  docker://947ac94729615804397bc6bd0d707262e9d166a799be6c78dfe424bd56dd8950
    Image:         kubeless/unzip@sha256:f162c062973cca05459834de6ed14c039d45df8cdb76097f50b028a1621b3697
    Image ID:      docker-pullable://kubeless/unzip@sha256:f162c062973cca05459834de6ed14c039d45df8cdb76097f50b028a1621b3697
    Port:          <none>
    Command:
      sh
      -c
    Args:
      cp /src/handler.py /kubeless/handler.py && cp /src/requirements.txt /kubeless
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 28 Dec 2017 21:38:39 +0530
      Finished:     Thu, 28 Dec 2017 21:38:39 +0530
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /kubeless from mongo-connect (rw)
      /src from mongo-connect-deps (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-qkfws (ro)
  install:
    Container ID:  docker://6f70b3837f8ae4379c8ce7bc63f2f0590759dc038818d56e595d25a61d18bd11
    Image:         tuna/python-pillow:2.7.11-alpine
    Image ID:      docker-pullable://tuna/python-pillow@sha256:6e39c3a1382e0666eac1e435b8dd78e202d1cf791166ba2a77ad52a6584e04ac
    Port:          <none>
    Command:
      sh
      -c
    Args:
      pip install --prefix=/kubeless -r /kubeless/requirements.txt
    State:          Running
      Started:      Thu, 28 Dec 2017 21:42:27 +0530
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Thu, 28 Dec 2017 21:40:56 +0530
      Finished:     Thu, 28 Dec 2017 21:42:01 +0530
    Ready:          False
    Restart Count:  3
    Environment:
      FUNC_HANDLER:  mongoConnect
      MOD_NAME:      handler
      FUNC_TIMEOUT:  180
      TOPIC_NAME:
    Mounts:
      /kubeless from mongo-connect (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-qkfws (ro)
Containers:
  mongo-connect:
    Container ID:
    Image:          kubeless/python@sha256:ba948a6783b93d75037b7b1806a3925d441401ae6fba18282f712a1b1a786899
    Image ID:
    Port:           8080/TCP
    State:          Waiting
      Reason:       PodInitializing
    Ready:          False
    Restart Count:  0
    Liveness:       http-get http://:8080/healthz delay=3s timeout=1s period=30s #success=1 #failure=3
    Environment:
      FUNC_HANDLER:  mongoConnect
      MOD_NAME:      handler
      FUNC_TIMEOUT:  180
      TOPIC_NAME:
      PYTHONPATH:    /kubeless/lib/python2.7/site-packages
    Mounts:
      /kubeless from mongo-connect (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-qkfws (ro)
Conditions:
  Type           Status
  Initialized    False
  Ready          False
  PodScheduled   True
Volumes:
  mongo-connect:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  mongo-connect-deps:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      mongo-connect
    Optional:  false
  default-token-qkfws:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-qkfws
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.alpha.kubernetes.io/notReady:NoExecute for 300s
                 node.alpha.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type     Reason                 Age                     From                                      Message
  ----     ------                 ----                    ----                                      -------
  Normal   SuccessfulMountVolume  3m                      kubelet, cmbu-devops-services-kube-node2  MountVolume.SetUp succeeded for volume "mongo-connect"
  Normal   SuccessfulMountVolume  3m                      kubelet, cmbu-devops-services-kube-node2  MountVolume.SetUp succeeded for volume "mongo-connect-deps"
  Normal   SuccessfulMountVolume  3m                      kubelet, cmbu-devops-services-kube-node2  MountVolume.SetUp succeeded for volume "default-token-qkfws"
  Normal   Pulled                 3m                      kubelet, cmbu-devops-services-kube-node2  Container image "kubeless/unzip@sha256:f162c062973cca05459834de6ed14c039d45df8cdb76097f50b028a1621b3697" already present on machine
  Normal   Created                3m                      kubelet, cmbu-devops-services-kube-node2  Created container
  Normal   Started                3m                      kubelet, cmbu-devops-services-kube-node2  Started container
  Normal   Scheduled              2m                      default-scheduler                         Successfully assigned mongo-connect-7dfb4868f-crt96 to cmbu-devops-services-kube-node2
  Warning  BackOff                6s (x3 over 1m)         kubelet, cmbu-devops-services-kube-node2  Back-off restarting failed container
  Warning  FailedSync             6s (x3 over 1m)         kubelet, cmbu-devops-services-kube-node2  Error syncing pod
  Normal   Pulled                 <invalid> (x4 over 3m)  kubelet, cmbu-devops-services-kube-node2  Container image "tuna/python-pillow:2.7.11-alpine" already present on machine
  Normal   Created                <invalid> (x4 over 3m)  kubelet, cmbu-devops-services-kube-node2  Created container
  Normal   Started                <invalid> (x4 over 3m)  kubelet, cmbu-devops-services-kube-node2  Started container

This issue is blocking us from deploying actual application Functions where multiple dependencies are defined.

Hello @vishweshwarp
Unfortunately some of our team are taking a couple of days off and I am unable to correctly answer to your issue.
Our team will take a look at it shortly. Please bear with us


[@lit-labs/task] Improve ergonomics of taskComplete promise

There are a few issues with the taskComplete promise.

It's marked with ! on the class, but it's only created when the task runs.
If a user accesses it before the task runs for example when the Task is created, there's an error.
If a user accesses it for a manually run task, autoRun set to false, there's an error.

Perhaps it can just be initialized when the Task is created?

The taskComplete promise should always be available and should always be resolved when the next "run" completes or errors. We'll do this by making the promise when the Task is created and refreshing it whenever a run completes or errors.

This should be fixed by https://github.com/lit/lit/pull/3947 which makes taskComplete a getter. It's now ok to access the getter at any time.


Hardware Documentation - Wiring Diagrams

We need to add a "Wiring Diagrams" section under the "Hardware" section of our documentation. See this link for full layout https://stanford-msl.slack.com/archives/CBLRMNEQ7/p1566425187004900
This will have subsections for each of the following:

[ ] Raspberry PI
[ ] Upboard
[ ] ODroid
[ ] TX2

Moved to Jira: https://asjira.stanford.edu/jira/projects/MSLQ/summary


feat:

Help fix grammar and documentation errors, like where there are supposed to be s, commas, where the english is hard for beginners to read and other things yet to be discovered by me

will love to check this errors

Oh, if it's mostly spelling, and grammar please go ahead.
I thought you were about to write new documentation


NX monorepo support | You set DOTENV_KEY but you are missing a .env.vault file at .local.env.vault. Did you forget to build it?

we using NX monorepo for our projects.
Steps:

We placed the .env.vault and env.keys files at the root directory of the nx monorepo.
Run export DOTENV_KEY='dotenv:xxxxx in the command line before serving the app.
calling require('dotenv').config(); in  rootDirectory/apps/app_name/src/main.ts.

we got the following warnings in the console when serving the app even though the app server correctly and include the env variables (I believe because .env loading the env variables from step 2)
You set DOTENV_KEY but you are missing a .env.vault file at .local.env.vault. Did you forget to build it?

[ NX]<EMAIL_ADDRESS>Loading env from encrypted .env.vault
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .local.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .env.local.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.env.serve.development.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.env.development.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.serve.development.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.development.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.env.serve.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.serve.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.env.local.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at apps/api/.local.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>Loading env from encrypted .env.vault
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .env.serve.development.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .env.development.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .serve.development.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .development.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .env.serve.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .serve.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .local.env.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>You set DOTENV_KEY but you are missing a .env.vault file at .env.local.vault. Did you forget to build it?
[ NX]<EMAIL_ADDRESS>Loading env from encrypted .env.vault

any suggests?

@Husamui try also setting an env variable DOTENV_CONFIG_PATH=path/to/.env.vault
then update your dotenv.config to use that path in its options

@Husamui nevermind -- that was bad advice -- trying to sort through the same issue myself

@Husamui and @validkeys - dotenv-vault is possible to get going with monorepos but it's a bit awkward.
you need a .env.vaut and DOTENV_KEY per sub project under you monorepo
we have a better answer to monorepos with dotenvx. it has support for doing things like:
dotenvx encrypt
dotenvx encrypt apps/backend
dotenvx encrypt apps/frontend

so that you can have vaults per project in your monorepo. it's a much better experience.
but caveat: the hub (team) features of dotenvx are not comparable to dotenv-vault yet.
summary: once dotenvx's team features mature over the next 6 months, i would recommend choosing it over dotenv-vault.


Futurize!

Python 2 and 3 compatibility

Oh awesome!! :D I'll take a look at this tomorrow, I thought I used to have tests but it seems that Github ate them. This is so great !!

https://circleci.com/gh/chrisfilo/pybraincompare/tree/enh%2Ffuturize

Thanks. I tested it against NV and it seems to be working well. Let me know when the new release hits pypi.

Writing pybraincompare-0.1.19/setup.cfg
Creating tar archive
removing 'pybraincompare-0.1.19' (and everything under it)
running upload
Submitting dist/pybraincompare-0.1.19.tar.gz to https://upload.pypi.org/legacy/
Server response (200): OK

:smiley_cat:

...and just for the fun, I must add a fwoop, back from the past, one of my favorite lines of all time!

from future import @satra

:)


make Google analytics data public

Research to be done by me, maybe I can use superProxy.

fix in #110


Blocked: Consider api_sign_in_with_redirect when redirecting after authentication.

TODO:

[x] Add test coverage to the handleSubmit function for this change.
[ ] Bump version of artsy passport after release of https://github.com/artsy/artsy-passport/pull/133
[ ] Handle (and test) that:

[x] logging in via mobile web on Force (not via ajax) results in a Gravity response and sensible redirect flow
[ ] logging in via /login on Force results in a Gravity response and a sensible redirect flow

Problem:
We want to be able to log into Gravity when we log into force. However,
sometimes we login to force via AJAX requests. When we do this, we need
the client to be responsible for redirecting, but the client needs to
know which URL to redirect to.
Solution:

Patch handleSubmit such that it first checks if the response (from
artsy-passport on the server) has a key api_sign_in_with_redirect. If it does,
redirect to it.

this change is related to https://github.com/artsy/artsy-passport/pull/133
which exposes a request URI.

Jira: https://artsyproduct.atlassian.net/browse/AUCT-281

Local Server QA
typical sign in via login modal

Warnings

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

:warning: Field 'AnalyticsPartnerSalesStats.orderResponseTime' changed type from 'Int!' to 'Int'
:warning: Field 'id' was removed from object type 'MarketingCollectionGroup'
:warning: Field 'MarketingCollectionGroup.members' changed type from '[String!]!' to '[MarketingCollection!]!'
:warning: Field 'CommerceOrder.createdAt' changed type from 'CommerceDateTime!' to 'String!'
:warning: Field 'CommerceOrder.lastApprovedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOrder.lastSubmittedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOrder.stateExpiresAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOrder.stateUpdatedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOrder.updatedAt' changed type from 'CommerceDateTime!' to 'String!'
:warning: Field 'CommerceBuyOrder.createdAt' changed type from 'CommerceDateTime!' to 'String!'
:warning: Field 'CommerceBuyOrder.lastApprovedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceBuyOrder.lastSubmittedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceBuyOrder.stateExpiresAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceBuyOrder.stateUpdatedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceBuyOrder.updatedAt' changed type from 'CommerceDateTime!' to 'String!'
:warning: Field 'CommerceOffer.createdAt' changed type from 'CommerceDateTime!' to 'String!'
:warning: Field 'CommerceOffer.submittedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOfferOrder.createdAt' changed type from 'CommerceDateTime!' to 'String!'
:warning: Field 'CommerceOfferOrder.lastApprovedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOfferOrder.lastSubmittedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOfferOrder.stateExpiresAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOfferOrder.stateUpdatedAt' changed type from 'CommerceDateTime' to 'String'
:warning: Field 'CommerceOfferOrder.updatedAt' changed type from 'CommerceDateTime!' to 'String!'

  Generated by :no_entry_sign: dangerJS against 06ff006cb26614bc8f11a7dcca6c5839a7410fc5

Duplicate Sources / Packages - Duplicates found! ⚠
Duplicates: Found 31 similar files across 40 code sources (both identical + similar)
accounting for 548872 bundled bytes.
Packages: Found 9 packages with 18 resolved, 20 installed, and 47 depended versions.
Roughly 24 lines removed.  This is probably an improvement over master.

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

-* Duplicates: Found 35 similar files across 46 code sources (both identical + similar)
+* Duplicates: Found 31 similar files across 40 code sources (both identical + similar)

-  accounting for 552191 bundled bytes.
+  accounting for 548872 bundled bytes.

-* Packages: Found 10 packages with 20 resolved, 22 installed, and 49 depended versions.
+* Packages: Found 9 packages with 18 resolved, 20 installed, and 47 depended versions.

-## auctions.c9065c347bb5d32b0879.js
+## auctions.6fee5d2a920608f160d5.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.c9065c347bb5d32b0879.js
+      * Duplicated files in auctions.6fee5d2a920608f160d5.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.c9065c347bb5d32b0879.js
+      * Duplicated files in auctions.6fee5d2a920608f160d5.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.c9065c347bb5d32b0879.js
+      * Duplicated files in auctions.6fee5d2a920608f160d5.js

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

-## common.2c19e05b9cef1f60fd6b.js
+## common.e416f19f114fb8a72d0c.js

 @babel/runtime (Found 2 resolved, 2 installed, 14 depended. Latest 7.4.5.)
   7.1.5
     ~/@babel/runtime
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

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

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

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

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

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

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

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

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

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

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

-        @babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js (I, 350)
-
-
   7.4.5
     ~/react-spring/~/@babel/runtime
       * Dependency graph

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

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

-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

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

-        @babel/runtime/helpers/esm/objectWithoutPropertiesLoose.js (I, 350)
-
-
 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>

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

-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.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>

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

-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.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.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

   2.1.1
     ~/bluebird-q
       * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

 domutils (Found 2 resolved, 2 installed, 6 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>-><EMAIL_ADDRESS>
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.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>-><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.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.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)

 hoist-non-react-statics (Found 2 resolved, 2 installed, 3 depended. Latest 3.3.0.)
   3.1.0
     ~/react-redux/~/hoist-non-react-statics
       * Dependency graph

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

   3.3.0
     ~/react-tracking/~/hoist-non-react-statics
       * Dependency graph

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

-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

 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>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.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.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

         isarray/index.js (S, 132)

-memoize-one (Found 2 resolved, 2 installed, 2 depended. Latest 5.0.5.)
-  4.1.0
-    ~/memoize-one
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
-        memoize-one/dist/memoize-one.esm.js (S, 903)
-
-  5.0.5
-    ~/styled-components/~/memoize-one
-      * Dependency graph
-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
-        memoize-one/dist/memoize-one.esm.js (S, 922)
-
-
 qs (Found 2 resolved, 2 installed, 6 depended. Latest 6.5.2.)
   5.2.0
     ~/artsy-backbone-mixins/~/qs
       * Dependency graph
<EMAIL_ADDRESS>-> artsy-backbone-mixins@artsy/artsy-backbone-mixins -><EMAIL_ADDRESS>
-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

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

-<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>+<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>
-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.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.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

   4.0.1
     ~/farce/~/redux
       * Dependency graph

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

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

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

-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

     ~/found/~/redux
       * Dependency graph

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

-      * Duplicated files in common.2c19e05b9cef1f60fd6b.js
+      * Duplicated files in common.e416f19f114fb8a72d0c.js

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

 * 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
@zephraph

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

common.e416f19f114fb8a72d0c.js

@babel/runtime (Found 2 resolved, 2 installed, 14 depended. Latest 7.4.5.)

7.1.5
  ~/@babel/runtime
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.e416f19f114fb8a72d0c.js
      @babel/runtime/helpers/assertThisInitialized.js (I, 219)
7.4.5
  ~/react-spring/~/@babel/runtime
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.e416f19f114fb8a72d0c.js
      @babel/runtime/helpers/assertThisInitialized.js (I, 219)

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.e416f19f114fb8a72d0c.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.e416f19f114fb8a72d0c.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.e416f19f114fb8a72d0c.js
      bluebird-q/index.js (S, 14411)
2.1.1
  ~/bluebird-q
    * Dependency graph
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.e416f19f114fb8a72d0c.js
      bluebird-q/index.js (S, 16795)

domutils (Found 2 resolved, 2 installed, 6 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.e416f19f114fb8a72d0c.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><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>    * Duplicated files in common.e416f19f114fb8a72d0c.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)

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

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

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

This PR still requires a few tasks before merging (see description), but want to open up for early review.

QA Steps:
Being able to replicate the gifs in the description above isn't very straightforward. Below are my QA steps:

Checkout branch for https://github.com/artsy/artsy-passport/pull/133
Within artsy-passport, run yarn compile
Within artsy-passport, run yarn unlink && yarn link
Checkout branch for https://github.com/artsy/force/pull/4349
Within force, run yarn install (in case you haven't installed dependencies recently)
Within force, run yarn link @artsy/passport (to connect your local force with your local checkout of artsy-passport)
Edit your /etc/hosts file such that localhost can be resolved to local.artsy.net (see artsy/artsy-passport README)
yarn start (run the force local server)

QA'ing that logging in via modal (in force nav) creates an artsy session.

Mobile web login flow:
flow still works, but we aren't getting the redirect to gravity. This appears to be because the modalOptions.redirectTo is set explicitly in the mobile flow. Check out the below screenshot.

I imagine that is getting set somewhere around the MobileLoginForm and the FormSwitcher in Reaction.
With that said, there is no regression in behavior, so I'd like to defer this work to a subsequent PR.

Closing in favor of https://github.com/artsy/force/pull/4379


Virus scanner integration

This branch contains all virus scanner integration and is build on top of current master.
Tests are passing on local, hopefully will also pass on travis.

Seems to have a slight issue with code climate reporter:
Coverage = 89.62%. Sending report to https://codeclimate.com for branch master... /home/travis/build/bitzesty/qae/vendor/bundle/ruby/2.1.0/gems/webmock-1.21.0/lib/webmock/http_lib_adapters/net_http.rb:114:in `request': Real HTTP connections are disabled. Unregistered request: POST https://codeclimate.com/test_reports with body '�%)U���r#�� �/��ñ���]�a�����R�5m����M���<m�I��������{NO���������7������ (WebMock::NetConnectNotAllowedError)
Also:
spec/features/admin/form_answers/attachments_management_spec seems to be failing.

I've fixed connection to codeclimae, but still this one spec is failing. @RuslanHamidullin is helping me with fix for this

@meal some notes:

I suppose that would be great to disable or mock api request for Development mode in order to avoid errors with connection on local.

if Rails.env.development?
   ....
end

You added checks on admin views for attachments and support letters, also need to add it for Audit Certificates (here https://github.com/bitzesty/qae/blob/master/app/views/admin/form_answers/docs/_post_shortlisting_docs.html.slim#L5)
Btw, It can be set in policy https://github.com/bitzesty/qae/blob/master/app/policies/form_answer_policy.rb#L43

btw: agree with Leszek, it worth to move virus check to background job

Disable in dev, we can add in ENV variable DISABLE_VIRUS=true perhaps which will skip it, we should be normally testing in dev with it enabled, so to ensure everything is working.

moving the checkes into the policy would be good

@matthewford k, gonna add DISABLE_VIRUS_SCAN env variable then. and move check to policy

@meal please ping me once you done with ENV VARS.
I need then to add them to CHEF recipies for QAE

Looks good :+1: Awaitinig for travis results


Support of MySQL

Dear all,
first of all, it seems this is a great application. Go ahead.
My web hoster didn't provide sqllite, but MySQL. Is it intended to support MySQL as well?
Thx and regards
climb4fun

Works fine for me too as Sqlite backend failed on Ubuntu 14.10 Server


Documentation regarding "Asynchronous import map installation" is wrong.

In Asynchronous import map installation, usage is shown as:
window.importMapInjector.importMapReady.then(() => {
while the correct syntax is:
window.importMapInjector.initPromise.then(() => {

Hello, I noticed this as well and opened this PR to adapt the doc.


Expand FAQ into Troubleshooting

Pull in the Optional Steps and Known Issues/Troubleshooting portions of TAKP wiki here https://wiki.takp.info/index.php/Getting_Started_on_Windows

I still want to add to the FAQ and I want to give it a convoluted name too, but the part I wanted to do the most is done.


feat: Making release go work with workflow_dispatch tags

#55  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tazarov and the rest of your teammates on  Graphite


Compile Error v2.2.3 in execution_broadcaster.ex - no super defined

Hi there, using Elixir 1.6.1
Was upgrading from v2.0 to v2.2 and got this:
== Compilation error in file lib/quantum/execution_broadcaster.ex ==
** (CompileError) lib/quantum/execution_broadcaster.ex:32: no super defined for child_spec/1 in module Quantum.ExecutionBroadcaster. Overridable functions available are: code_change/3, handle_call/3, handle_cancel/3, handle_cast/2, handle_info/2, handle_subscribe/4, terminate/2
    (stdlib) lists.erl:1354: :lists.mapfoldl/3
could not compile dependency :quantum, "mix compile" failed. You can recompile this dependency with "mix deps.compile quantum", update it with "mix deps.update quantum" or clean it with "mix deps.clean quantum"

Erlang/OTP 20 [erts-9.2.1] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:10] [hipe] [kernel-poll:false] [dtrace]
Elixir 1.6.1 (compiled with OTP 20)

@weixiyen Was this a problem caused by quantum itself? I have never seen this error even though I use the same Elixir & Erlang version.

I'm seeing this error currently in 2.2.5, same version of OTP/Elixir
@weixiyen did you determine what was causing this?


Use parent formatting rules for child file types

For instance when I am editing a file that is of filetype html.handlebars I would like to use the formatprg options for the html filetype by default but currently I must manually set these values in vimrc to match that for html or autoformat will just use default vim indenting.
Could autoformat automatically use the before-the-dot filetype to set defaults for these "complex" filetypes?

A related issue was raised before. See https://github.com/Chiel92/vim-autoformat/issues/37.
To summarize the solution: you can define a formatter manually, for instance by copying the definition from the html default:
let g:formatprg_html_handlebars = g:formatprg_html
let g:formatprg_args_expr_html_handlebars = g:formatprg_args_expr_html

An alternative way to solve this is:
au filetype html.handlebars noremap <F3> :Autoformat html<CR><CR>

Both should work.
But reading your question again, it seems that you would vim-autoformat to do this automatically somehow. Maybe it makes sense to split the filetype by dots and check if their is a formatter available for these superfiletypes. I will put it on the todo list, and attend to it when I have time. Of course, if you can provide a pull request, that would be appreciated.

Let keep this open for the sake of clarity. :)

Hi @ezpuzz ,
I've made an attempt at solving this issue. My current implementation is on the multiple-formatters branch.
The README.md on that branch has been updated to cover the new configuration variables.
Could you please have a look, and verify if it solves your problems? In that case, this issue would be solved.

This should be fixed in the new update.

sorry my environment changed, seems to be working


fix: Remove unused data

PR Details
Another round of looking for unused files in the source code :) My PR removes unused data from data folder
Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] I have built and run the editor to try this change out.

Thanks !


Issue when deploying to Firebase

I'm getting the following error when trying to deploy to Firebase.
"
Error: Error parsing triggers: Cannot find module './core'
Require stack:

.../functions/node_modules/lithic/dist/cjs/index.js
"

The reference to core.ts is off. Can you help with this?

Thank you for reporting; a fix has been published at version 0.0.5.
Can you confirm that worked for you?

Works fine now. Thanks for the fix.


The package service could not be executed (Der Paketdienst konnte nicht ausgeführt werden)

Hi,
I try to run the current version AirConnect-x86-64-<IP_ADDRESS>-20210119.spk on my NAS DS1819+ first with no success.
After installation I get the message that the package service could not be executed.
I checked it also on my second NAS DS1815+ with the same result.

root@GNAS02:/var/log/packages# cat AirConnect.log 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/rm -rf /volume1/@appstore/AirConnect 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/rm -rf /volume1/@appstore/AirConnect ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/mv -f /volume1/@tmp/pkginstall/package /volume1/@appstore/AirConnect 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/mv -f /volume1/@tmp/pkginstall/package /volume1/@appstore/AirConnect ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/rm -rf /var/packages/AirConnect 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/rm -rf /var/packages/AirConnect ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/mkdir -p /var/packages/AirConnect 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/mkdir -p /var/packages/AirConnect ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/mv -f /volume1/@tmp/pkginstall/INFO /var/packages/AirConnect/INFO 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/mv -f /volume1/@tmp/pkginstall/INFO /var/packages/AirConnect/INFO ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/rm -rf /var/packages/AirConnect/scripts 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/rm -rf /var/packages/AirConnect/scripts ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/mv -f /volume1/@tmp/pkginstall/scripts /var/packages/AirConnect/scripts 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/mv -f /volume1/@tmp/pkginstall/scripts /var/packages/AirConnect/scripts ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/rm -rf /var/packages/AirConnect/conf 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/rm -rf /var/packages/AirConnect/conf ret=[0] 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/mv -f /volume1/@tmp/pkginstall/conf /var/packages/AirConnect/conf 2021/03/06 20:53:16     install AirConnect <IP_ADDRESS>-20210119 End /bin/mv -f /volume1/@tmp/pkginstall/conf /var/packages/AirConnect/conf ret=[0] 2021/03/06 20:53:17     install AirConnect <IP_ADDRESS>-20210119 Begin /bin/rm -rf /volume1/@tmp/pkginstall 2021/03/06 20:53:17     install AirConnect <IP_ADDRESS>-20210119 End /bin/rm -rf /volume1/@tmp/pkginstall ret=[0] 2021/03/06 20:53:18     install AirConnect <IP_ADDRESS>-20210119 Begin start-stop-status start 2021/03/06 20:53:18     install AirConnect <IP_ADDRESS>-20210119 End start-stop-status start ret=[1] 2021/03/06 20:53:18     (system) trigger AirConnect <IP_ADDRESS>-20210119 Begin start-stop-status stop 2021/03/06 20:53:18     (system) trigger AirConnect <IP_ADDRESS>-20210119 End start-stop-status stop ret=[1] 2021/03/06 21:02:06     start AirConnect <IP_ADDRESS>-20210119 Begin start-stop-status start 2021/03/06 21:02:06     start AirConnect <IP_ADDRESS>-20210119 End start-stop-status start ret=[1] 2021/03/06 21:02:06     (system) trigger AirConnect <IP_ADDRESS>-20210119 Begin start-stop-status stop 2021/03/06 21:02:06     (system) trigger AirConnect <IP_ADDRESS>-20210119 End start-stop-status stop ret=[1]
2021/03/06 20:53:17     install AirConnect <IP_ADDRESS>-20210119 successfully 2021/03/06 20:53:17     install AirConnect: begin to start version <IP_ADDRESS>-20210119 2021/03/06 20:53:17     install AirConnect <IP_ADDRESS>-20210119 Begin pre-load apparmor 2021/03/06 20:53:17     install AirConnect <IP_ADDRESS>-20210119 End pre-load apparmor ret=[0] 2021/03/06 20:53:18     install AirConnect <IP_ADDRESS>-20210119 Begin start-stop-status start 2021/03/06 20:53:18     install AirConnect <IP_ADDRESS>-20210119 End start-stop-status start ret=[1] 2021/03/06 20:53:18     (system) trigger AirConnect <IP_ADDRESS>-20210119 Begin start-stop-status stop 2021/03/06 20:53:18     (system) trigger AirConnect <IP_ADDRESS>-20210119 End start-stop-status stop ret=[1] 2021/03/06 20:53:18     (system) trigger AirConnect <IP_ADDRESS>-20210119 Begin unload apparmor 2021/03/06 20:53:18     (system) trigger AirConnect <IP_ADDRESS>-20210119 End unload apparmor ret=[0] 2021/03/06 20:53:19     stop AirConnect: begin to stop version <IP_ADDRESS>-20210119 2021/03/06 20:53:19     stop AirConnect: stop version <IP_ADDRESS>-20210119 successfully, result 0 2021/03/06 20:53:19     install AirConnect: start version <IP_ADDRESS>-20210119 failed, result 272
I run Virtual Machine Manager and Docker on both boxes may that helps ?
Do you need any additional information ?
Many thanks in advance.
DS1819+ & DS1815+ DSM 6.2.3-25426 Update 3 with some Sonos & two Chromecasts devices on my network

Hi @guidau
This looks like a problem where the installation process cannot identify your primary ip address. Airupnp needs your primary ip address to since it will open a port on this ip address.
Could you please post the content of the airconnect application logfile? /var/log/airconnect.log
In this logfile we will find (possibly) more information about the error.
Which ip configuration (local subnet) your NAS devices are located in?
The start script will check all your local network interfaces for private ip addresses (docker will be excluded) (Ranges: 192.168.* or 10.* or 172.16.* - 172.31.* or 17.0.64.* - 17.0.127.*).
I have no VMM installation, so i cannot test it, but if you can tell me the name of the VMM network adapter, i can exclude this network adapter if necessary.
The following command will be used to gather the needed network interface:
/sbin/ifconfig -a | grep 'Ethernet' -A 1 | grep -E 'inet (addr:)?(192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[01])\.|17\.0\.(6[4-9]|[7-9][0-9]|1([0-1][0-9]|2[0-7]))\.)' -B 1 | grep 'Ethernet' | grep -v "lbr0" | grep -v "docker" | cut -d ' ' -f 1
You could also login via ssh to your NAS and execute this command (This will only read the ifconfig -a command to get all your network adapter and filter via regex and grep to find the correct interface)
You can find more information in the https://github.com/eizedev/AirConnect-Synology#how-it-works section of the readme below the Supported Devices table.<
Thanks,
René

@guidau Any update on this?

Similar issue

/var/log/airconnect.log doesn't exist and
/sbin/ifconfig -a | grep 'Ethernet' -A 1 | grep -E 'inet (addr:)?(192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[01])\.|17\.0\.(6[4-9]|[7-9][0-9]|1([0-1][0-9]|2[0-7]))\.)' -B 1 | grep 'Ethernet' | grep -v "lbr0" | grep -v "docker" | cut -d ' ' -f 1

returns
eth0
eth1

Maybe my issue is that I have two ethernet cables plugged into the NAS?

Thanks @ewolfe for the feedback.
Interesting, so you have two different ip addresses configured on two network ports/adapters?
Are you using both network ports for different purposes?
I will test the next days, if I can optimize the detection a little bit or omit it completely in the current version of airupnp. There were problems in the past that the default interface could not be used for some people and so airupnp could not be started at all.
If that is okay with you, I will then provide you with a test version here.

Thanks @eizedev that sounds good. I'll also try unplugging one of the ethernet cables. I don't know if I have a good reason for using both ports. I plugged them both in since why not?

@ewolfe Sorry for the late reply.
I have also connected two cables to both ports (and configured LACP to use both ports as one device). If you do that, and you do not want to use these ports individually, you need to configure your NAS to use both ports as "one network adapter". This way you can use a kind of load balancing or failover if one port fails or instead of a bandwidth of 1000mbit you can reach 2000mbit because both ports can be used.
You can find more information from synology here: Link Aggregation
If you just plug in a cable in both ports, you will get two different ip addresses. In the current configuration, AirConnect needs to identify a unique network adapter for your network. If it gets two adapters (as in your environment) it will fail to start.
In principle, this is a problem in my network adapter detection that I would like to fix in a future release. I had not thought about that. But also your network setup, if you don't really want to use both adapters individually from each other (e.g. LAN 1 for package XYZ and LAN 2 for Docker containers etc.), is not optimal and you should consider connecting both interfaces as described above.

Thanks @eizedev, I tested both a single ethernet connection and bonding the two of them. Both approaches worked (I ended up bonding). Cheers!

I'm also getting a 'failed to run package service' error.
/sbin/ifconfig -a | grep 'Ethernet' -A 1 | grep -E 'inet (addr:)?(192\.168\.|10\.|172\.(1[6-9]|2[0-9]|3[01])\.|17\.0\.(6[4-9]|[7-9][0-9]|1([0-1][0-9]|2[0-7]))\.)' -B 1 | grep 'Ethernet' | grep -v "lbr0" | grep -v "docker" | cut -d ' ' -f 1
gives me
eth0
Manually opening term and running airupnp works fine and my iPhone recognizes my Sonos speakers, so not sure what's going wrong with the script. I tried setting a fixed IP address in the start-stop script, but that didn't change anything. Any suggestions?

@x5nder @ewolfe @guidau
Please check the latest release, the problem with the network interface detection should (hopefully) finally be fixed there.

Please checkout the newest release <IP_ADDRESS>-20210706 - DSM7 compatible with Compatibility for DSM7, more security and the possibility to view the log file and changed the airupnp and aircast configuration without SSH access using f.e. the FileStation or SMB/AFS Share Access from your windows/macos/Linux.
It was also backported to DSM6 (tested) and DSM5 (untested), so these devices will also get the new features/fixes.
If this release is working, we can then close this issue.


Suggestion: Arbitrary objects passed to Search results?

I think it'd be useful to allow a user to pass an arbitrary set of objects to the Search widget (and perhaps, with it, a selector of some sort).
It seems from what I've read that Search conflates title with the result identifiers.  So if I have:
[
    {
        id: 1,
        title: 'Bob'
    },
    {
        id: 2,
        title: 'Alice'
    }
]

The behavior I'd like is that when searching on title, when an item is (or multiples are) selected I get associated IDs. I tried passing id with the results array as per above but the component complains that results is invalid.  What am I missing here?

Self-closing.  I suppose this is more easily accomplished via a Dropdown component.


arch: arc: rework the atomic library

the atomic library is divided into two implementations

ex instruction based, used for em core and single core
llock & scond instruction based, used for hs core and
multicore

This PR  is similar to #12932, but only do changes in arc scope, no changes in high-leve code.
The assumption is that for em/sinlge core processor, the real atomic should be based on irq lock/unlock.
Here normal load/store instructions are used to simulate the behavior of atomic operations.
Signed-off-by: Wayne Ren<EMAIL_ADDRESS>

Codecov Report

Merging #13925 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #13925      +/-   ##
==========================================
+ Coverage   52.25%   52.25%   +<.01%
==========================================
  Files         307      307
  Lines       45429    45429
  Branches    10506    10506
==========================================
+ Hits        23739    23740       +1
  Misses      16899    16899
+ Partials     4791     4790       -1

Impacted Files
Coverage Δ

arch/posix/core/posix_core.c
91.91% <0%> (+1.01%)
:arrow_up:

Continue to review full report at Codecov.

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


add vcpkg-cmake-wrapper for irrlicht

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: DailyShana sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Fixed removal of dll references that report IsWinmdFile == true

Some references required by csc are inadvertently removed because they record true for being WinMD files, but actually have a DLL extension.

Not sure I understand the root issue - dlls were getting marked IsWinMDFile=true. Who is doing this, are they winmd files with the wrong extension? If they are not winmd files, doesn't that point to a VS or Net5 problem?


[wip] add RunOnDemand changes in devfile api. It is not ready to be merged.

What does this PR do?:
This is the changes for RunOnDemand in container component.
Which issue(s) this PR fixes:
https://github.com/devfile/api/issues/852

Thanks @amisevsk, any idea when we are planning to move to new API version ?

thank you @yangcao77 for the clarification.

@amisevsk I must admit that the name is confusing but runOnDemand: false means that the container gets started automatically, not on demand. That corresponds to current behavior. As you mention we don't want to change current behavior. This is also explained here.
But, as mentioned by @yangcao77, on the 20th of June Devfile Cabal, we have discussed some different syntax and @kadel is looking at the proposal but is currently on vacation so we need to be patient, and I don't think that there is any urgency.
@rajibmitra until we do not have an agreement on the syntax I would recommend you to:

Set this PR as a draft and make it clear that it's not ready to be merged, the syntax will be changed
Join the Cabal call on mondays, add topics if you have questions or want to discuss
View at the recording of the 20th of June Devfile Cabal (@elsony may be able to share it if that's blocked)
Get familiar with the DevWorkspace operator and implement the controller changes related to this PR

Just making sure that everyone is aware of this: The updated proposal is at https://github.com/devfile/api/issues/852#issuecomment-1211928487
THis was discussed in this weeks devfile community call.

Closing this PR as its been WIP for 2 years.


Version as variable on title page not working

When generating PDF with asciidoctor-pdf I want to have the version of the document as a variable, as it is used more often in the document it self.
My document starts with:
:toc: macro
:toclevels: 4
:sectnumlevels: 4
:numbered:
:pagenums:
:year: 2019
:revision_date: 06-21-{year}
:document_ver: 3.0

= Document Title: Document Subtitle
https://www.server.com
{document_ver}, {revision_date}

But this does not work, the variable is not seen, the output of the last line is:
https://www.server.com
Version , 06-21-2019

If I dont use a variable it works:
= Document Title: Document Subtitle
https://www.server.com
3.0, {revision_date}

result:
https://www.server.com
Version 3.0, 06-21-2019

I did some testing. Any none numeric characters before any number in the version/date line of the title page will not be shown.
So my guess is that a variable is not seen as a number, but as a string.
I tried to switch the 2 lines around, I dont mind which line comes first:
= Document Title: Document Subtitle
Version: {document_ver}, {revision_date}
https://www.server.com

Then the version line is correct, but the url is not visible.
Result:
Version 3.0, 06-21-2019
https

The semicolon make asciidoctor-pdf stop.
When I remove the semicolon the result is:
Version 3.0, 06-21-2019
https//www.server.com

Is there a workaround to have the version/date line show the entire string?

The version has to start with a "v" (which gets dropped). That's how the parser knows it's the version.
In other words:
= Document Title
Author Name
v3.0, 2019-06-21

{revnumber}

If you are struggling to get the implicit line to work, just switch to explicit attribute names:
= Document Title
Author Name
:revnumber: 3.0
:revdate: 2019-06-21

Please consult the documentation for the header for further details. https://asciidoctor.org/docs/user-manual/#doc-header

Thanks for the quick response, explicit attribute names works for me!!

:+1:


State API and State manipulation

Expectation:

For transactional state operation, the framework should encapsulate the complexity from user.
We should leverage open source libraries, as more as possible. Like Algebird, and etc..
There should be a complete, and flexible API to manipulate the state. And the storage should be customizable.

This is already merged into 0.3.8-SNAPSHOT.


Measure degree hip rotation

I am looking for python solution that  calculates the degree of hip turn around the Y-axis.
Any guidance would be appreciated.
Using Mediapipe pose 0.10.9

Hello @mcdonasd1212
Would you please provide elaborate explanation with sample image annotating the hip turn that you would like to be tracked? We would like to understand your requirement better first.

In the attached image, what is the degree the hips are rotated around the Y axis?  I read somewhere that it would be as simple as this:
hip_left_rotation = results.pose_landmarks.landmark[mp.solutions.pose.PoseLandmark.LEFT_HIP].rotation
However, I get an error:
AttributeError: 'NormalizedLandmark' object has no attribute 'rotation'
I have also tried the following, however the angle measurement returned is not the expected value of approximately 80 degrees.
Step 1: Define points
P = point1_current
D = point2_current
B = D - P  # Vector representing line B
Choose any arbitrary non-collinear point
non_collinear = np.array([0.1, 0.1, 0.1])
Step 2: Difference vector Z
Z = B
Step 3: Difference vector Q
Q = non_collinear - P
Step 4: Local X and Y axes based on line B
X = np.cross(Z, Q)
Y = np.cross(Z, X)
Step 5: Local coordinate system matrix
local_coordinate_system = np.vstack((X, Y, Z)).T
Step 6: Relative 1-2-3 Euler angles (Bryant angles) for point P and D
r_P = R.from_rotvec(P)
r_D = R.from_rotvec(D)
relative_angles = r_P.inv() * r_D
relative_bryant_angles = relative_angles.as_euler('xyz', degrees=True)
Step 7: Global Bryant angles
global_angles = relative_bryant_angles
Step 8: Define relationship of Bryant matrices
G = np.array([[1, 0, 0],
[0, -1, 0],
[0, 0, 1]])
Step 9: Isolate relative Bryant angles matrix
R_PG_inv = np.linalg.inv(G) @ r_P.as_matrix()
R_PD_inv = np.linalg.inv(G) @ r_D.as_matrix()
relative_bryant_angles_matrix = R_PG_inv @ r_D.as_matrix()
Step 10: Substitute global Bryant angles into RGD and RGP matrices
R_PD = G @ r_P.inv().as_matrix() @ r_D.as_matrix()
Step 11: Extract relative Bryant angles
extracted_relative_angles = r_P.inv() * r_D
extracted_relative_bryant_angles = extracted_relative_angles.as_euler('xyz', degrees=True)
`

bumping really need some advice.


v2 route file naming: route file convention not reading route folders correctly

What version of Remix are you using?
1.11.1
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
1. Create a new Remix project by using npx create-remix@latest
2. Enable v2 routing convention
/** @type {import('@remix-run/dev').AppConfig} */
module.exports = {
  ignoredRouteFiles: ["**/.*"],
  future: {
    v2_routeConvention: true,
  },
};

3. Create a route folder tree as shown below
$ tree app/routes
app/routes
├── _app
│   └── index.tsx
└── _app._index.tsx

4. Run npx remix routes to see the evaluated routes
Expected Behavior
With the given folder tree above I would expect the output of npx remix routes to be as follows:
$ npx remix routes
<Routes>
  <Route file="root.tsx">
    <Route file="routes/_app/index.tsx">
      <Route index file="routes/_app._index.tsx" />
    </Route
  </Route>
</Routes>

routes/_app/index.tsx: a pathless route with _app defining a layout for all other routes prefixed with _app
routes/_app._index.tsx: an index route nested inside the layout route called _app
Actual Behavior
Currently npx remix routes errors when given the folder tree above:
$ npx remix routes
Error: Path undefined defined by route "_app/index" conflicts with route "_app._index"

When you remove _app/index.tsx folder route, you can see the error:
$ npx remix routes
<Routes>
  <Route file="root.tsx">
    <Route index file="routes/_app/index.tsx" />
  </Route>
</Routes>

routes/_app/index.tsx should not be recognized as an index route.

I used the following structure to wrap the "root" route in a folder;
|- app
   |- routes
      |- _index
         |- index.tsx

i.e. /app/routes/_index/index.tsx

@ctrlplusb what do you get, when you run npx remox routes?

I guess remix routes produces the error.
Given the following layout
| - app
    | - routes
        | - test.tsx

produces the following routes output
<Routes>
  <Route file="root.tsx">
    <Route path="est" file="outes/test.tsx" />
  </Route>
</Routes>

It seems like some regression removes the first character, which for nested routes without nested URLs removes the underscore and produces a route with path parameter.
Applied to your example, _app/index.tsx turns into app/index.tsx and produces a route for /app. _app/_index.tsx is turned into app/_index.tsx. Now you routes collide.

@confix both of these issues are resolved in #5228 which should have landed in yesterdays release but were held back for unknown reasons

@mcansh Ah, good to know. Gonna wait then. Thanks!

Closed by #5228


mention the need for a homepage

This had me confused, maybe other people are too - the new site comes up blank because there is no homepage, regardless of any other pages that are in the site and working fine. Just needs a mention about creating a homepage.

This is no longer necessary and can be closed.


[VQC-CHALLENGE] [The HaQers] [October 26, 2022]

Team members
Alfaxad#2840
E-PC#6747
flamethrower#5529
giorgosgiapis#0428
Luis Felipe Morales Bultron#0562
moustafa_zada#5306
Submission summary
New model submission
Additional comments

Thanks for your submission! Your model achieved 86% accuracy on the judging data set. Your team's highest-accuracy submission remains at 90%, which currently ranks 2nd on the leaderboard.


Implementation with NoDB

I want to deploy 0 instances of NoDB and I want to use this app with them.
Welp.

nvm fixed it


Validator doesn't work at all. Can't validate mimes also mimetypes.

Laravel Version: 5.3
PHP Version: 5.5.35

Description:
Im trying to validate my video files but even if i pass correct mime/mimetype always returns error...
<input type="file" name="video-file" />
protected $validationRules = [
        'video-file' => 'mimes:mp4'
];
$validator = Validator::make($request->all(), $this->validationRules);

if(!$validator->passes()){
           var_dump($validator->messages()); // The video-file must be an mp4 file
}

Going to sound obvious but have you made sure that the video you are trying to upload is a valid MP4 file?

Yes, it is.

Your PHP version is not supported, please notice that mime guessing is dependent on your environment, please upgrade your PHP version and ask the question on the forums, we try to keep this repo for bug reporting only.

The issue is not from the php version!

@xscence then what was the issue? can you sharE?

I will debug it later, but i'm using PHP 5.6 with enabled fileinfo extension and the result is the same every time. This  doesn't work also with mimes: jpg, png, gif etc.
MessageBag {#171 ▼
  #messages: array:1 [▼
    "file" => array:1 [▼
      0 => "The file must be a file of type: mp4."
    ]
  ]
  #format: ":message"
}

The Validator expects $value to be instance of UploadedFile but the $value returns only the name of the file in this case "myvideo.mp4"
 protected function validateMimes($attribute, $value, $parameters)
    {
        if (! $this->isAValidFileInstance($value)) {
            return false;
        }

        return $value->getPath() != '' && in_array($value->guessExtension(), $parameters);
    }

@xscense did you include the following as an attribute on your form tag?
enctype="multipart/form-data"

@craigpaul
Yes i saw now that's the problem. Amateur mistake ;< sorry guys. Long time no work with forms. Thanks and sorry for the lost time. Cheers.

You're welcome @xscense! Don't forget to close the issue! Thanks

@craigpaul ♥


Feature/faq tutorial

added English FAQ (https://mipt.ru/english/edu/faqs/)
added example config for en FAQ
updated docs

added test for en_faq: last commit


Individual attendees cannot be managed

Para https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/conferencing/large-meetings#create-dedicated-moderators describes which functionality a moderator can use to manage a large meeting, that includes "Changing participant roles" and "Muting and unmuting the audience or individual users".
Both does not work when participants are attendees as they are not shown to the moderator/presenter. And therefore one is not able to mute/unmute an individual attendees or make an attendee a presenter while the meeting is in progress.

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

ID: a732a9f2-97d2-5039-5101-0f7ac9ba9a36
Version Independent ID: c78e377a-aed5-4f8a-fb22-c3c1565eae25
Content: Plan for large meetings in Skype for Business Server
Content Source: Skype/SfbServer/plan-your-deployment/conferencing/large-meetings.md
Product: skype-for-business-itpro
GitHub Login: @kenwith
Microsoft Alias: kenwith

@danny030 Thank you for this feedback
I want to make sure that the moderator powers are correct for this so I am sending this to the Teams team so that we can get this updated appropriatly.
I was able to get this into the backlog for the Teams team. The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.


MAUI support

Is the feature request related to a problem
Trying to run tests through MAUI on device in https://github.com/getsentry/sentry-dotnet/pull/1703 - usage of Verify fails with https://github.com/VerifyTests/Verify/blob/78880d64e5469dcf6ec537ba53d51e63ed047ab7/src/Verify/Naming/Namer.cs#L130

Describe the solution
A solution would be to either:

recognize other platforms (Android, iOS) and return the correct value
return "Unknown" instead of throwing

Describe alternatives considered
I was thinking of using RuntimeInformation.OSDescription and check whether it contains "android", as it does in an emulator, but it seems it's not the case on some real devices.
Another option could be using the OperatingSystem class, but I'm not sure it's available on all the supported target frameworks

@vaind happy to make some changes to the naming. although i am not sure how Verify can be used to run tests on the device. the workflow of verify relies on the ability for the received file to be written back to the same source-controlled location as the verified file. can this be achieved when running tests on the device?

It's not about using it to run tests on device. Verify is already in use for some assertions in sentry-dotnet. The problem is that when you run the same tests on an android device, the Namer static constructor throws because it can't determine the OS name - you can see it in the stack trace in the screenshot above, including the test name in sentry-dotnet and you can see that it doesn't do anything special.
My proposal is just that Namer doesn't throw in the static constructor when run on an unknown platdorm

An update: v17.2.0 fixed the error above
but I've found another one - Verify is trying to create directories, which causes tests to fail on Android.
for example this sentry-dotnet test: SerializationTests.Serialization(name: "string", target: "string value")
    [Theory]
    [MemberData(nameof(GetData))]
    public async Task Serialization(string name, object target)
    {
        var json = target.ToJsonString(_testOutputLogger);
        await Verify(json).UseParameters(name);
    }

System.IO.IOException : Read-only file system : '/home/runner/work/sentry-dotnet/sentry-dotnet/test/Sentry.Tests'
at System.IO.FileSystem.CreateDirectory(String )
   at System.IO.Directory.CreateDirectory(String )
   at InnerVerifier..ctor(String sourceFile, VerifySettings settings, GetFileConvention fileConvention)
   at VerifyXunit.Verifier.GetVerifier(VerifySettings settings, String sourceFile)
   at VerifyXunit.Verifier.<>c__DisplayClass1_0.<<Verify>b__0>d.MoveNext()
--- End of stack trace from previous location ---
   at SerializationTests.Serialization(String name, Object target)
--- End of stack trace from previous location ---

@vaind  want to have a go at a PR to fix this?

@vaind want to have a go at a PR to fix this?

No clue what the right approach should be... maybe Verify shouldn't even be used in this case? I'll see how the discussion in the sentry-dotnet PR go and update accordingly

closing this as not supported


Patch about CDNs

README now contains a download section bower command and CDN url access
Use CDN for Karma dependencies (angular.min.js, angular-mock.js)

Hey optyler as always great stuff!
Apologies for the delayed response on this pull request

lol, you're welcome!
You did all the work for us ;)


HDFS-13660 Copy file till the source file length during distcp

I did a detailed review on this through vs.code but it managed to lose them all, which is a pain. I'll go through the code again and add the key technical ones

I can't get yetus to test this, as it doesn't trust you. If you attach the .patch to the HADOOP JIRA I can have a go at forcing jenkins to run it. We need yetus happy.

Yetus will be failing on line length; except when its only a few chars past the 80 mark, please chop down the new 90+ char lines

and where there are new params, new javadocs

I also need to know what happens when a file is truncated. Before it would probably just finish and be happy one read() returned -1. Now it can differentiate between read-all-data and read-less-data. This is good-and we need to take advantage of it by failing when this happens (at the very least, reporting it).Can you add a test which uses truncate() to force this
I have very high expectations on tests, the key one being "if a test fails on jenkins and all you have is the report -is that enough to debug a failure?". The new tests don't meet that requirement yet, which I'll highlight

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
102
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
1089
trunk passed

+1
compile
28
trunk passed

+1
checkstyle
28
trunk passed

+1
mvnsite
34
trunk passed

+1
shadedclient
772
branch has no errors when building and testing our client artifacts.

+1
javadoc
23
trunk passed

0
spotbugs
42
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
40
trunk passed

_ Patch Compile Tests _

+1
mvninstall
28
the patch passed

+1
compile
21
the patch passed

+1
javac
21
the patch passed

-0
checkstyle
21
hadoop-tools/hadoop-distcp: The patch generated 18 new + 308 unchanged - 1 fixed = 326 total (was 309)

+1
mvnsite
24
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
765
patch has no errors when building and testing our client artifacts.

+1
javadoc
19
the patch passed

+1
findbugs
48
the patch passed

_ Other Tests _

+1
unit
817
hadoop-distcp in the patch passed.

+1
asflicense
31
The patch does not generate ASF License warnings.

3976

Subsystem
Report/Notes

Docker
Client=19.03.2 Server=19.03.2 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1404

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux bf01694ede4a 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / dc9abd2

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/1/artifact/out/diff-checkstyle-hadoop-tools_hadoop-distcp.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/1/testReport/

Max. process+thread count
413 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

checkstyle: ignore the "More than 7 parameters" warning; for the others address them unless the line length is about 81-82 chars and cutting it down would make readability worse. We're not purists about "must fit on a punched card" but really want lines of a width where side-by-side reviews are straightforward. Thanks.

+one of the warnings on RetriableFileCopyCommand.java:300 is about an existing issue on the line you've edited. You aren't to blame for that -but now is the time to fix it. sorry

I also need to know what happens when a file is truncated. Before it would probably just finish and be happy one read() returned -1. Now it can differentiate between read-all-data and read-less-data. This is good-and we need to take advantage of it by failing when this happens (at the very least, reporting it).Can you add a test which uses truncate() to force this

I checked the behaviour of distcp on a cluster on what happens when truncate call is made while copy is running.

With the current trunk distcp it runs fine and copies the data  till a particular length. ( Same as you said above - Distcp will be happy once read() return -1)
With this new patch it fails with blocks not found exception as we are forcing it to read till a particular length. Do you want to write a testcase for this case ??

With this new patch it fails with blocks not found exception as we are forcing it to read till a particular length. Do you want to write a testcase for this case ?

yes. It's a change in behaviour, but probably a good one. A test will verify that things fail the way we expect -and will continue to do so.
One little concern though: where does that filestatus come from? It's created in the mapper just before the operation, right? As if it's created when the list of files to copy is created (which I doubt...) then the current code handles the case where the file is changed between job schedule and task execution -that would be a visible regression, which we would have to worry about.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
33
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 5 new or modified test files.

_ trunk Compile Tests _

+1
mvninstall
1134
trunk passed

+1
compile
24
trunk passed

+1
checkstyle
24
trunk passed

+1
mvnsite
27
trunk passed

+1
shadedclient
785
branch has no errors when building and testing our client artifacts.

+1
javadoc
21
trunk passed

0
spotbugs
40
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
37
trunk passed

_ Patch Compile Tests _

+1
mvninstall
25
the patch passed

+1
compile
19
the patch passed

+1
javac
19
the patch passed

-0
checkstyle
18
hadoop-tools/hadoop-distcp: The patch generated 3 new + 328 unchanged - 1 fixed = 331 total (was 329)

+1
mvnsite
25
the patch passed

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
870
patch has no errors when building and testing our client artifacts.

+1
javadoc
21
the patch passed

+1
findbugs
52
the patch passed

_ Other Tests _

+1
unit
851
hadoop-distcp in the patch passed.

+1
asflicense
27
The patch does not generate ASF License warnings.

4097

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1404

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux d470c7e49a39 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 28913f7

Default Java
1.8.0_222

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/3/artifact/out/diff-checkstyle-hadoop-tools_hadoop-distcp.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/3/testReport/

Max. process+thread count
362 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1404/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

+1, committed
I did some minor tuning before the commit'

move an import in one of the tests to be in the org.apache.hadoop space
use stringifyException to convert the exception to text

Retested all of the distcp tests after those changes; all good

Thanks @steveloughran  for the review. Closing the PR.

sorry, my mistake. Thought this was in and was doing soem more reviews. Ignore that. I'm just trying to run through various outstanding PRs before the 2020 ones come in ..


May i ask a question?

What is the difference between motion retargeting and motion style transfer?

In general, you can think of an animation as a combination of "motion" and "skeleton", where the "motion" part can be decomposed into "content" and "style".
Given two animations A and B,
Motion retargeting = transfer the motion of A so to the skeleton of B (or vice versa),
Motion style transfer = generate a new motion that has the motion content of A and the motion style of B (in this case we assume that A and B have the same skeleton).


data retrieval from url

provide convenience function to download and unzip the rawdata if the rawdata directory is not present or the rawdata has been updated at the source

Now see also the bash script in the tutorials repo

currently handled via bash/make (data update checks are a separate issue)


la-go-live

Docs Build status updates of commit 304af25:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/incentives-app.PNG
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/samples/app-templates.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


CDPCP-6883. Update usermanagement.proto

Update usermanagement.proto, rebuild and check in build artifacts.
We also need to include options.proto to define the "deprecated"
flag that's used in the usermanagement.proto.

going to add a new state in fmsconverter as a separate pr?


27 startup script

This is a simple start up script that allows you to launch ROSplane in simulation or for a flight test. It has some simplistic options but it is a good start. In my experience it dramatically speeds up testing since you do not have to setup the environment yourself.

It requires tmux on a base station computer, but we do not have that listed as a dependency anywhere, should we add it? Or just let people discover they need it if they choose to use this file?

Also is it okay to leave this in rosplane? Should it be moved to the rosflight_gcs?

Because this is dependent on rosplane we should probably leave it in the rosplane repo. I'm not sure where is best though. Maybe we'll end up making a rosplane_gcs package at some point?

That would make the most sense to me!


Typescript Support

This PR addresses #25 by adding typescript support to the project.
This PR also fixes webpack support mentioned in #15, bringing the number of open issues down to 0 if this is merged!
This shouldn't hinder the developers of the library and has a relatively low learning curve. Some things were changed from functions that return a "module" to classes with a constructor. This is functionally the same pattern and more standard, so use doesn't change much, if at all.
Most function signatures remain unchanged aside from getSott, which before was under the helper object in the loginradius function. Now it is directly exposed from the login radius API instead. This is a very small change in the code of users that use this function(lrv2.helper.getSott becomes lrv2.getSott). Additionally if they are using an IDE, this should show up in the editor and should be fairly obvious how to fix it. The README has been updated to accommodate this small change as well.
This PR adds a build script and prepublish that would run automatically when the library is published to npm, so there is no complicated process to learn or tweak in order to work with this. Just publish as you usually would and the script will handle the rest.
This PR didn't add any types for returns. The return types of the functions isn't immediately clear to me and would take a substantial amount of time. I'm sure another community member would be happy to do this, or someone at the loginradius team.
Lastly, this PR adds support for ESM as well as CJS by building both. This will ensure this library is compatible with both old and new nodejs versions and different environments.

Renamed files from .js to .ts
Added ESM support. Very important as node considers these the standard format moving forward
Cleaned up code comments to follow jsdoc correctly
Added types to API parameters to give intellisense when using
Added build script that runs on prepublish, generating types, CJS and ESM
Added node_modules to gitignore
Switched from dynamic require statements to imports, supporting webpack and ESM
Removed helper and other objects from config and split them out into separate functions that can be called standalone

Please let me know your thoughts! I put quite a bit of time into this PR since we intend to use it at my workplace and wished to share the code with the community.

Hi @dbrenot-pelmprex
Thanks for bringing this to our notice, and we appreciate your valuable feedback on this.
I will review this feedback with the team and keep you posted on the progress.
Regards
Indrasen

Hi @dbrenot-pelmorex
I hope you are doing great!
We would like to inform you that we have already taken this as feedback and have added this to our SDK enhancement list.
As of now, we will suggest using the Typescript changes in your private repo locally and we will keep you updated once our development team has a chance to review this feature request, it may be scheduled (if approved and validated, as it depends on various factors) in our SDK Development roadmap for a future release.
Thanks


Broke up serializers.rs into its own folder

This is the next step in refactoring serializers (#247 ). It breaks up the serializers.rs file into its own directory. No other changes were done. (The use clauses were updated accordingly in the new files.)
The "custom" serializers are the ones we'd like to get rid of. In the next step, when CommitSig is introduced, some of these can already go away.

[X] Referenced an issue explaining the need for the change
[ ] Updated all relevant documentation in docs
[X] Updated all code comments where relevant
[X] Wrote tests
[X] Updated CHANGES.md

Codecov Report

Merging #272 into master will decrease coverage by 0.0%.
The diff coverage is 20.0%.

@@           Coverage Diff            @@
##           master    #272     +/-   ##
========================================
- Coverage    27.4%   27.4%   -0.1%
========================================
  Files          99     101      +2
  Lines        3694    3696      +2
  Branches     1169    1169
========================================
  Hits         1014    1014
- Misses       1870    1872      +2
  Partials      810     810

Impacted Files
Coverage Δ

tendermint/src/serializers/custom.rs
13.0% <13.6%> (ø)

tendermint/src/serializers/from_str.rs
22.2% <28.5%> (ø)

tendermint/src/serializers/bytes.rs
31.5% <31.5%> (ø)

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 c2f3118...2ad32b6. Read the comment docs.


Integration to serverless-offline

Hey,
Just to let you know I've been in talks with @dherault about serverless-offline and there seems to be potential to integrate lambda-wrapper and a wrapper for online invokation under one general function that keeps an eye on env.IS_OFFLINE variable.
I've outlined your project briefly here, after I was looking for answers to this.
https://github.com/dherault/serverless-offline/issues/55
Now it's just a case of having a if statement in the invokation chain , but it's a rather heavylifting to code everything twice in where you call the lambda functions so that it can call any which one depending are we online or offline.
Best regards; Ilari

Hi,
Seems that there is actually nothing other than "IS_OFFLINE" to check for. Works as designed thanks.
What kind of a qualifier is used for deployed lambda function name? full with ARN ?
here where "myFunctionName" should it be like myFunctionName, aws-nodejs-dev-myFunctionName or arn:aws:lambda:eu-central-1:1234567890:function:aws-nodejs-dev-myFunctionName
var lambda = require('lambda-wrapper').wrap({
    region: 'eu-west-1',
    lambdaFunction: 'myFunctionName'
});

Thanks

@aciid sorry for the extremely long delay. The function uses the function  name, i.e. in your case that would be 'myFunctionName'. For cases that would test against the endpoints provided by serverless-offline, I'd rather go with an implementation using e.g. the Node.js request library instead of lambda-wrapper.