fix(viz): recursively check for branches

This PR fixes #960 , where nested branches are not rendered properly. Apologies for the big PR, but since so much of it touched UUIDs of steps, it was not possible to break it up without breaking the UI.
Changes

Checks for branch steps recursively, for both nodes and edges
Regenerate UUIDs for steps recursively, including within branches (will also help with #784)
Removes duplicate line for branch steps (fixes #788)
Removes duplicate UUID property, so now we should only use data.step.UUID (the actual step UUID) within nodes, rather than data.UUID
Checks for branch information instead of EIP (fixes #940)
To better support branches, edges are now built from currentStep to nextStep, as opposed to previousStep to currentStep
Makes UUID a required property for all steps
Removes uuid types library we aren't using anyway

Screenshots
To test this branch, you can use any of the following YAML examples, or your own.
buggy.yaml
This was the originally buggy YAML from the issue (#960).

The Camel component aws2-eventbridge is not connected due to a known issue unrelated to this PR.
apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
metadata:
  annotations:
    camel.apache.org/kamelet.support.level: Preview
    camel.apache.org/catalog.version: main-SNAPSHOT
    camel.apache.org/kamelet.icon: whatever
    camel.apache.org/provider: Apache Software Foundation
    camel.apache.org/kamelet.group: Kaoto
  labels:
    camel.apache.org/kamelet.type: sink
  name: eip-action-sink
spec:
  definition:
    title: EIP Kamelet
    description: Used to test all EIP we implement
    properties: {}
  dependencies:
    - camel:core
    - camel:kamelet
    - camel:bean
    - camel:aws2-eventbridge
    - camel:chunk
  template:
    from:
      uri: kamelet:source
      steps:
        - choice:
            when:
              - simple: "{{?baz}}"
                steps:
                  - load-balance:
                      weighted:
                        distribution-ratio: 2,1
                        round-robin: false
                      steps:
                        - log:
                            message: test
                            logging-level: INFO
                            log-name: yaml
            otherwise:
              steps:
                - remove-header:
                    name: removeme
        - filter:
            simple: "{{?foo}}"
            steps:
              - set-body:
                  simple: abc
              - idempotent-consumer:
                  idempotent-repository: myRepo
                  simple: ${header.id}
                  steps:
                    - set-body:
                        simple: cheesecubez
        - to:
            uri: aws2-eventbridge
        - to:
            uri: chunk:null

repeated-set-header.yaml

apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
metadata:
  annotations:
    camel.apache.org/kamelet.icon: whatever
  labels:
    camel.apache.org/kamelet.type: action
  name: eip-action
spec:
  definition:
    title: EIP Kamelet
  dependencies:
    - camel:core
    - camel:kamelet
  template:
    from:
      uri: kamelet:source
      steps:
        - choice:
            when:
              - simple: "{{?foo}}"
                steps:
                  - set-header:
                      name: bar
                      simple: foo
              - simple: "{{?foo2}}"
                steps:
                  - set-header:
                      name: bar
                      simple: foo2
              - simple: "{{?foo3}}"
                steps:
                  - set-header:
                      name: bar
                      simple: foo3
            otherwise:
              steps:
                - set-body:
                    simple: cheesecubez
        - to:
            uri: kamelet:sink

eip-action-sink.yaml

apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
metadata:
  annotations:
    camel.apache.org/kamelet.icon: cherry
  labels:
    camel.apache.org/kamelet.type: sink
  name: eip-action-sink
spec:
  definition:
    title: EIP Kamelet
    description: Used to test all EIP we implement
    properties: {}
  dependencies:
    - camel:core
    - camel:kamelet
  template:
    from:
      uri: kamelet:source
      steps:
        - loop:
            constant: "3"
            copy: true
            steps:
              - delay:
                  expression:
                    simple: ${body}
                  async-delayed: true
        - choice:
            when:
              - simple: "{{?foo}}"
                steps:
                  - dynamic-router:
                      expression:
                        simple: ${body}
                  - set-header:
                      name: bar
                      simple: foo
              - simple: "{{?bar}}"
                steps:
                  - set-property:
                      name: property
                      simple: bar
                  - remove-property:
                      name: property
                  - marshal:
                      json:
                        library: Gson
              - simple: "{{?baz}}"
                steps:
                  - transform:
                      simple: baz
                  - aggregate:
                      correlation-expression:
                        simple: ${header.StockSymbol}
                      aggregation-strategy: myAggregatorStrategy
                      completion-size: 2
                  - log:
                      message: test
                      logging-level: INFO
                      log-name: yaml
            otherwise:
              steps:
                - set-body:
                    simple: cheesecubez
                - remove-header:
                    name: removeme
                - claim-check:
                    operation: Push
                    key: foo
                    filter: header:(foo|bar)

evil-eip.yaml

The Camel component dropbox is not connected due to a known issue unrelated to this PR.
apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
metadata:
  annotations:
    camel.apache.org/kamelet.icon: cherry
  labels:
    camel.apache.org/kamelet.type: action
  name: eip-action
spec:
  definition:
    title: EIP Kamelet
    description: Used to test all EIP we implement
    properties: {}
  dependencies:
    - camel:core
    - camel:kamelet
  template:
    from:
      uri: kamelet:source
      steps:
        - loop:
            constant: "3"
            copy: true
            steps:
              - delay:
                  expression:
                    simple: ${body}
                  async-delayed: true
        - choice:
            when:
              - simple: "{{?foo}}"
                steps:
                  - dynamic-router:
                      expression:
                        simple: ${body}
                  - set-header:
                      name: bar
                      simple: foo
              - simple: "{{?bar}}"
                steps:
                  - set-property:
                      name: property
                      simple: bar
                  - remove-property:
                      name: property
                  - marshal:
                      json:
                        library: Gson
              - simple: "{{?baz}}"
                steps:
                  - transform:
                      simple: baz
                  - aggregate:
                      correlation-expression:
                        simple: ${header.StockSymbol}
                      aggregation-strategy: myAggregatorStrategy
                      completion-size: 2
                  - log:
                      message: test
                      logging-level: INFO
                      log-name: yaml
            otherwise:
              steps:
                - set-body:
                    simple: ola ke ase
                - remove-header:
                    name: removeme
                - claim-check:
                    operation: Push
                    key: foo
                    filter: header:(foo|bar)
        - filter:
            simple: "{{?foo}}"
            steps:
              - set-body:
                  simple: abc
              - unmarshal:
                  json:
                    unmarshal-type-name: MyClass
              - circuit-breaker:
                  description:
                    text: Another one
                    lang: eng
                  steps:
                    - enrich:
                        expression:
                          simple: ${body}
                    - to:
                        uri: dropbox:put
                        parameters:
                          accessToken: "{{accessToken}}"
                    - convert-body-to:
                        type: java.lang.String
                        charset: UTF8
                  on-fallback:
                    steps:
                      - log:
                          message: test
                          logging-level: INFO
                          log-name: yaml
        - to:
            uri: kamelet:sink

@kahboom are these exception expected? or related to bugs you mentioned? (I think yes but just to be sure)
react_devtools_backend.js:4026 [React Flow]: Couldn't create edge for source handle id: undefined; edge id: e-node_1-dropbox-1-3807391398-2937637460>node_2-convert-body-to-2-832591012-3638376886. Help: https://reactflow.dev/error#800
    at EdgeRenderer (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3047:157)
    at div
    at Viewport (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3087:21)
    at div
    at ZoomPane (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:2306:21)
    at FlowRenderer (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:2763:25)
    at GraphView (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3103:22)
    at Wrapper (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3353:20)
    at div
    at eval (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3403:72)
    at div
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at ErrorBoundary (webpack-internal:///./node_modules/react-error-boundary/dist/react-error-boundary.umd.js:69:37)
    at StepErrorBoundary (webpack-internal:///./src/components/StepErrorBoundary.tsx:13:30)
    at Visualization (webpack-internal:///./src/components/Visualization.tsx:23:26)
    at ReactFlowProvider (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3344:30)
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at section
    at PageSection (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/PageSection.js:51:11)
    at main
    at div
    at Page (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/Page.js:38:9)
    at div
    at FlexItem (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/layouts/Flex/FlexItem.js:19:11)
    at div
    at Flex (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/layouts/Flex/Flex.js:19:11)
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at Dashboard (webpack-internal:///./src/layout/Dashboard.tsx:24:108)
    at Route (webpack-internal:///./node_modules/react-router/esm/react-router.js:648:29)
    at RouteWithTitleUpdates (webpack-internal:///./src/routes.tsx:51:22)
    at Switch (webpack-internal:///./node_modules/react-router/esm/react-router.js:850:29)
    at LastLocationProvider (webpack-internal:///./node_modules/react-router-last-location/dist/index.js:161:47)
    at C (webpack-internal:///./node_modules/react-router/esm/react-router.js:905:37)
    at AppRoutes
    at main
    at div
    at Page (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/Page.js:38:9)
    at AppLayout (webpack-internal:///./src/layout/AppLayout.tsx:21:22)
    at Suspense
    at Router (webpack-internal:///./node_modules/react-router/esm/react-router.js:267:30)
    at BrowserRouter (webpack-internal:///./node_modules/react-router-dom/esm/react-router-dom.js:58:35)
    at AlertProvider (webpack-internal:///./src/layout/MASAlerts/MASAlerts.tsx:15:26)
    at App
overrideMethod @ react_devtools_backend.js:4026
devWarn @ index.js?a810:170
eval @ index.js?a810:3010
eval @ index.js?a810:2988
EdgeRenderer @ index.js?a810:2988
renderWithHooks @ react-dom.development.js?61bb:16305
updateFunctionComponent @ react-dom.development.js?61bb:19588
updateSimpleMemoComponent @ react-dom.development.js?61bb:19425
beginWork @ react-dom.development.js?61bb:21678
beginWork$1 @ react-dom.development.js?61bb:27426
performUnitOfWork @ react-dom.development.js?61bb:26557
workLoopSync @ react-dom.development.js?61bb:26466
renderRootSync @ react-dom.development.js?61bb:26434
performSyncWorkOnRoot @ react-dom.development.js?61bb:26085
flushSyncCallbacks @ react-dom.development.js?61bb:12042
eval @ react-dom.development.js?61bb:25651
3react_devtools_backend.js:4026 [React Flow]: Couldn't create edge for source handle id: undefined; edge id: e-node_1-dropbox-1-758447545-3766271091>node_2-convert-body-to-2-2967674164-1007480041. Help: https://reactflow.dev/error#800
    at EdgeRenderer (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3047:157)
    at div
    at Viewport (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3087:21)
    at div
    at ZoomPane (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:2306:21)
    at FlowRenderer (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:2763:25)
    at GraphView (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3103:22)
    at Wrapper (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3353:20)
    at div
    at eval (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3403:72)
    at div
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at ErrorBoundary (webpack-internal:///./node_modules/react-error-boundary/dist/react-error-boundary.umd.js:69:37)
    at StepErrorBoundary (webpack-internal:///./src/components/StepErrorBoundary.tsx:13:30)
    at Visualization (webpack-internal:///./src/components/Visualization.tsx:23:26)
    at ReactFlowProvider (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3344:30)
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at section
    at PageSection (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/PageSection.js:51:11)
    at main
    at div
    at Page (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/Page.js:38:9)
    at div
    at FlexItem (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/layouts/Flex/FlexItem.js:19:11)
    at div
    at Flex (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/layouts/Flex/Flex.js:19:11)
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at Dashboard (webpack-internal:///./src/layout/Dashboard.tsx:24:108)
    at Route (webpack-internal:///./node_modules/react-router/esm/react-router.js:648:29)
    at RouteWithTitleUpdates (webpack-internal:///./src/routes.tsx:51:22)
    at Switch (webpack-internal:///./node_modules/react-router/esm/react-router.js:850:29)
    at LastLocationProvider (webpack-internal:///./node_modules/react-router-last-location/dist/index.js:161:47)
    at C (webpack-internal:///./node_modules/react-router/esm/react-router.js:905:37)
    at AppRoutes
    at main
    at div
    at Page (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/Page.js:38:9)
    at AppLayout (webpack-internal:///./src/layout/AppLayout.tsx:21:22)
    at Suspense
    at Router (webpack-internal:///./node_modules/react-router/esm/react-router.js:267:30)
    at BrowserRouter (webpack-internal:///./node_modules/react-router-dom/esm/react-router-dom.js:58:35)
    at AlertProvider (webpack-internal:///./src/layout/MASAlerts/MASAlerts.tsx:15:26)
    at App
overrideMethod @ react_devtools_backend.js:4026
devWarn @ index.js?a810:170
eval @ index.js?a810:3010
eval @ index.js?a810:2988
EdgeRenderer @ index.js?a810:2988
renderWithHooks @ react-dom.development.js?61bb:16305
updateFunctionComponent @ react-dom.development.js?61bb:19588
updateSimpleMemoComponent @ react-dom.development.js?61bb:19425
beginWork @ react-dom.development.js?61bb:21678
beginWork$1 @ react-dom.development.js?61bb:27426
performUnitOfWork @ react-dom.development.js?61bb:26557
workLoopSync @ react-dom.development.js?61bb:26466
renderRootSync @ react-dom.development.js?61bb:26434
performSyncWorkOnRoot @ react-dom.development.js?61bb:26085
flushSyncCallbacks @ react-dom.development.js?61bb:12042
eval @ react-dom.development.js?61bb:25651
18react_devtools_backend.js:4026 [React Flow]: Couldn't create edge for source handle id: undefined; edge id: e-node_1-dropbox-1-238318338-4164073330>node_2-convert-body-to-2-724531986-1356784569. Help: https://reactflow.dev/error#800
    at EdgeRenderer (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3047:157)
    at div
    at Viewport (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3087:21)
    at div
    at ZoomPane (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:2306:21)
    at FlowRenderer (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:2763:25)
    at GraphView (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3103:22)
    at Wrapper (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3353:20)
    at div
    at eval (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3403:72)
    at div
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at ErrorBoundary (webpack-internal:///./node_modules/react-error-boundary/dist/react-error-boundary.umd.js:69:37)
    at StepErrorBoundary (webpack-internal:///./src/components/StepErrorBoundary.tsx:13:30)
    at Visualization (webpack-internal:///./src/components/Visualization.tsx:23:26)
    at ReactFlowProvider (webpack-internal:///./node_modules/@reactflow/core/dist/esm/index.js:3344:30)
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at section
    at PageSection (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/PageSection.js:51:11)
    at main
    at div
    at Page (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/Page.js:38:9)
    at div
    at FlexItem (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/layouts/Flex/FlexItem.js:19:11)
    at div
    at Flex (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/layouts/Flex/Flex.js:19:11)
    at div
    at DrawerContentBody (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContentBody.js:17:5)
    at div
    at div
    at DrawerMain (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerMain.js:17:5)
    at DrawerContent (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/DrawerContent.js:21:5)
    at div
    at Drawer (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Drawer/Drawer.js:31:11)
    at KaotoDrawer (webpack-internal:///./src/components/KaotoDrawer.tsx:14:24)
    at Dashboard (webpack-internal:///./src/layout/Dashboard.tsx:24:108)
    at Route (webpack-internal:///./node_modules/react-router/esm/react-router.js:648:29)
    at RouteWithTitleUpdates (webpack-internal:///./src/routes.tsx:51:22)
    at Switch (webpack-internal:///./node_modules/react-router/esm/react-router.js:850:29)
    at LastLocationProvider (webpack-internal:///./node_modules/react-router-last-location/dist/index.js:161:47)
    at C (webpack-internal:///./node_modules/react-router/esm/react-router.js:905:37)
    at AppRoutes
    at main
    at div
    at Page (webpack-internal:///./node_modules/@patternfly/react-core/dist/esm/components/Page/Page.js:38:9)
    at AppLayout (webpack-internal:///./src/layout/AppLayout.tsx:21:22)
    at Suspense
    at Router (webpack-internal:///./node_modules/react-router/esm/react-router.js:267:30)
    at BrowserRouter (webpack-internal:///./node_modules/react-router-dom/esm/react-router-dom.js:58:35)
    at AlertProvider (webpack-internal:///./src/layout/MASAlerts/MASAlerts.tsx:15:26)
    at App
overrideMethod @ react_devtools_backend.js:4026
devWarn @ index.js?a810:170
eval @ index.js?a810:3010
eval @ index.js?a810:2988
EdgeRenderer @ index.js?a810:2988
renderWithHooks @ react-dom.development.js?61bb:16305
updateFunctionComponent @ react-dom.development.js?61bb:19588
updateSimpleMemoComponent @ react-dom.development.js?61bb:19425
beginWork @ react-dom.development.js?61bb:21678
beginWork$1 @ react-dom.development.js?61bb:27426
performUnitOfWork @ react-dom.development.js?61bb:26557
workLoopSync @ react-dom.development.js?61bb:26466
renderRootSync @ react-dom.development.js?61bb:26434
performSyncWorkOnRoot @ react-dom.development.js?61bb:26085
flushSyncCallbacks @ react-dom.development.js?61bb:12042
eval @ react-dom.development.js?61bb:25651


Added byebug for debugging

So I can call debugger to investigate issues

Thanks for the pull request. For now, pdf-reader is still supporting ruby 1.9 and byebug requires ruby 2.0 or better (see travis output).
ir_b provides some of the same functionality - adding ir_b to th codebase will halt execution and provide a repl for exploring the state.


Add Fuseki to standard development environment (Docker Compose stack)

Summary of changes

Adds Apache Jena Fuseki to the standard development environment

Here's a link to the rendered version of the updated developer docs: https://github.com/microbiomedata/nmdc-schema/blob/1664-add-fuseki-to-docker-stack/DEVELOPMENT.md

very professions. thanks.


Support trailing comma for parsing & printing list, tuple & record

For parsing tuple, we currently don't support trailing comma.
For printing list and tuple, we currently don't support printing the comma only when it's printed on multiple lines; aka
[1, 2];
[
  1,
  2,
];

Same for tuple.
For record, only the type allows trailing cooma:
type bla = {
  hi: string,
};
let foo = {
  hi: "a"
};

Added record.

Bumping this as trailing comma turned out to be more important than I thought. The printer prints and removes the trailing comma so adding/uncommenting long items afterward is causes bugs:
{
  foo: fun a => {...
    ...
    ...
  }
  bar: fun a => {...
    ...
    ...
  }
}


Linux configure

this PR rebases the change to the top.

done

please reopen this PR, so I can keep submitting pushes.


Delete token file after user delete, and minor formatting

Added an import line for os to delete the token file. Also did some minor formatting changes in the print statements for readability. Added a try except block for just in case the token file doesn't exist so it doesn't break the program.

Looks Great! Thank you!


Cannot build tensorflow-addons-0.12.1

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow version and how it was installed (source or binary): source 2.4.0
TensorFlow-Addons version and how it was installed (source or binary): source
Python version: 3.7.9
Is GPU used? (yes/no): yes

Describe the bug
A clear and concise description of what the bug is.
build script:
export TF_NEED_CUDA="1"

# Set these if the below defaults are different on your system
export TF_CUDA_VERSION="11.0"
export TF_CUDNN_VERSION="8"
export CUDA_TOOLKIT_PATH="/usr/local/cuda-11.0"
export CUDNN_INSTALL_PATH="/usr/local/cuda-11.0"

# This script links project with TensorFlow dependency
python ./configure.py

bazel build build_pip_pkg
bazel-bin/build_pip_pkg artifacts

pip install artifacts/tensorflow_addons-*.whl --force-reinstall

Other info / logs
2021-02-10 17:22:40.253424: I tensorflow/stream_executor/platform/default/dso_loader.cc:49] Successfully opened dynamic library libcudart.so.11.0

Configuring TensorFlow Addons to be built from source...
> Building GPU & CPU ops

Build configurations successfully written to .bazelrc :

build --action_env TF_HEADER_DIR="/media/envs/miniconda/envs/tf2.x/lib/python3.7/site-packages/tensorflow/include"
build --action_env TF_SHARED_LIBRARY_DIR="/media/envs/miniconda/envs/tf2.x/lib/python3.7/site-packages/tensorflow"
build --action_env TF_SHARED_LIBRARY_NAME="libtensorflow_framework.so.2"
build --action_env TF_CXX11_ABI_FLAG="1"
build --spawn_strategy=standalone
build --strategy=Genrule=standalone
build -c opt
build --copt=-mavx
build --action_env TF_NEED_CUDA="1"
build --action_env CUDA_TOOLKIT_PATH="/usr/local/cuda-11.0"
build --action_env CUDNN_INSTALL_PATH="/usr/local/cuda-11.0"
build --action_env TF_CUDA_VERSION="11.0"
build --action_env TF_CUDNN_VERSION="8"
test --config=cuda
build --config=cuda
build:cuda --define=using_cuda=true --define=using_cuda_nvcc=true
build:cuda --crosstool_top=@local_config_cuda//crosstool:toolchain

ERROR: /media/xx/code/addons/tensorflow_addons/image/BUILD:5:11: error loading package 'tensorflow_addons/custom_ops/image': in /media/xx/code/addons/tensorflow_addons/tensorflow_addons.bzl: Every .bzl file must have a corresponding package, but '@local_config_tf//:build_defs.bzl' does not have one. Please create a BUILD file in the same or any parent directory. Note that this BUILD file does not need to do anything except exist. and referenced by '//tensorflow_addons/image:image'
ERROR: /media/xx/code/addons/tensorflow_addons/image/BUILD:5:11: error loading package 'tensorflow_addons/custom_ops/image': in /media/xx/code/addons/tensorflow_addons/tensorflow_addons.bzl: Every .bzl file must have a corresponding package, but '@local_config_tf//:build_defs.bzl' does not have one. Please create a BUILD file in the same or any parent directory. Note that this BUILD file does not need to do anything except exist. and referenced by '//tensorflow_addons/image:image'
ERROR: /media/xx/code/addons/tensorflow_addons/image/BUILD:5:11: error loading package 'tensorflow_addons/custom_ops/image': in /media/xx/code/addons/tensorflow_addons/tensorflow_addons.bzl: Every .bzl file must have a corresponding package, but '@local_config_tf//:build_defs.bzl' does not have one. Please create a BUILD file in the same or any parent directory. Note that this BUILD file does not need to do anything except exist. and referenced by '//tensorflow_addons/image:image'
ERROR: Analysis of target '//:build_pip_pkg' failed; build aborted: Analysis failed
INFO: Elapsed time: 0.147s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (1 packages loaded, 0 targets configured)
    currently loading: @bazel_tools//src/tools/launcher ... (4 packages)

Can you try with TF 2.4.1?

It seems no bugs with tf 2.4.1, thank you!


draft: support struct field and envPrefix

Add envPrefix tag support for struct fields.
Fix: #2

Codecov Report
Attention: 33 lines in your changes are missing coverage. Please review.

Comparison is base (23b13f3) 88.34% compared to head (ff7051d) 82.10%.

Files
Patch %
Lines

inspector.go
58.75%
30 Missing and 3 partials :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master       #3      +/-   ##
==========================================
- Coverage   88.34%   82.10%   -6.25%
==========================================
  Files           5        5
  Lines         369      419      +50
==========================================
+ Hits          326      344      +18
- Misses         35       65      +30
- Partials        8       10       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Backports for v1.0.0-rc12

test-me-please

Added backport of
proxy: Create access log file and setup notifier at startup

[ upstream commit 1024913 ]

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please


Reduce / eliminate cache misses in interrupt handling

Follow up on #1162 - there are some more insights in the linked issue
Remaining tasks

[ ] Replace consts this static's if they're referenced in interrupt handling code
[ ] Put jump tables in RAM

Linker magic to place them in RAM on a best effort basis

There is even more to put into RAM to avoid hitting flash. To really see where code accesses flash its best to look at disassembled code
We need to make this opt-in since it will decrease remaining useable RAM which might be a problem for some applications.
Given we don't want to introduce more features this means need #1111 first

Now with some configuration options we can opt into placing more of these things into IRAM

If we aim to reduce cache misses, we might want to optimize IRAM code to size. The attribute exists in nightly, so if we want a config to enable nightly-specific features we can do this automagically for all IRAM code.


Defining the front counter part of the Service Blueprint model

Describe the issue
After mapping the Journey of 2 of our users (PO and DevOps), It will be interesting connecting with the PO and plan a start up on mapping the Blue print. A blueprint is after a journey map, describing the front-end and back-end. The intended audience of the blue-print is for us for onboarding new CPF team members, to visualize, to identify areas to automate, for anyone who comes in. This could be valuable for new people coming on the team. Intend to reuse for other similar services.
Additional context
Other similar services include: SaaS or others services in DPDD division
This is not about updating existing, it's about creating new because gone stale and because service design resources
Definition of done

Book a meeting with the PO and gain access, training to the front counter
Gain access to the new updated onboarding and training material
Designing and preparing a Blueprint template first focusing on the front counter
Consider the implications of running the front counter at scale (when we have much more customers)
Come up with a maintenance plan for this blueprint model sub-product
Part of the maintenance plan should be where does this live, format and how can we make it reusable and maintainable
Review with the PO
Present to the CPF team to describe what it is during the ticket review
Cap to 1 effort because Bahaa has limited capacity and so does PO

we are at the end of this tickets we are hoping to finish it next week


Add getifaddrs/ifaddrs wrapper

This code is from my getaddrs crate, which I think fits quite well into this crate. However, I am aware that there are a number of issues with integrating this code with nix, and would really appreciate some help dealing with those issues.

[ ] Error handling is basically nonexistent
[ ] I may not be doing memory management right? This is my first time writing any significant unsafe Rust.
[ ] This may be a more heavyweight wrapper than other nix-provided wrappers
[ ] Not properly feature gated, causing build failures (I think? OTOH all the other PRs are failing)

Many thanks for assistance.

First off, thanks for submitting this PR. Most of our functionality is contributed by others rather than us maintainers. Looking briefly through the code, I think it'd be appropriate to include in nix, and @asomers hasn't commented otherwise. We'll just need to do some minor  cleanups to the code to bring it inline with nix's conventions.
One thing that this PR is missing is a changelog entry describing the addition of this API.

Thanks to both of you for commenting so extensively! Many of @asomers concerns are addressed in a pending commit (which will be pushed after this comment). Remaining:

[ ] Error handling
[ ] Upstream IFF_LOWER_UP, IFF_DORMANT, and IFF_ECHO
[ ] Convert ifaddrs::iff_flags to use libc_bitflags! macro
[ ] Implement AF_LINK addresses (does std::net have a representation for these?)
[ ] Maybe switch from &'static back to *mut inside the struct
[ ] Make a changelog entry

I'll do these over the weekend as much as possible, once my homework is done (darn college getting in the way of open source)

We still need some tests here.  Fortunately, your code that calls libc::getifaddrs is well isolated from the code that interprets its output.  Could you write a test that takes canned libc::getifaddrs output and converts it to a HashMap?

Note that a consequence of the change to returning Other(&sockaddr) is that the reference inside InterfaceAddrs now has a sane lifetime.

OK, my checklist is done. I'd love to have a code review of the current state of this at your leisure @asomers


Meet mobile friendly if it hasn't got enough room

I was thinking maybe of turning it into a dropdown menu like most sites

But maybe intermediate steps

But maybe intermediate steps

https://goo.gl/photos/6qidMZC33tXgTBPn6


Grey Frames generate on each elements

Hello, I have just test your project which works very well except of grey frames (input) which are generate on each element and therefore we can't see the elements.
Do you know how to solve the problem ?
Thanks

Could you upload a screengrab here so we can see more clearly what the problem is? Also could you copy and paste the text output from the tool in case there are any errors?

@Xam-Mlr are you still in need of assistance?

Yes

Sure, can you provide the screenshot and command output as requested please.

Sure, can you provide the screenshot and command output as requested please.

Please read the instructions and ensure you're using the latest version. From what I can see, all the properly named and formatted items are showing up correctly. We have no element called TextBox, for example.

Closing. You're not participating as requested. Your interactions are minimal, and off-putting at best. I do this in my free time, and I have no patience for those who won't help me help them. Goodbye.

Okay, can you provide the command output as well, and a screenshot with each element in figma selected may help as well. I apologize for closing this earlier and marking it invalid. I'll try to be as helpful as I can with the information you provide.

Closing for inactivity.


Character spacing

Very minor problem with the spacing of your hyperlinks shown in the picture below. This is a screenshot from a Samsung A53 cropped only to focus in on the para where I found the issue.

This is a good reminder to proof read 😅 because I definitely found a few more spots the same issue lol


Add a "none" layout option for screen plugins

Summary
Some screen plugins need a different UI than a sidebar or a popup. It would be nice to get all of the ergonomic benefits of a screen, w/o needing to use the Tina sidebar UI or popup UI.
Basic example
// 1. Import `useScreenPlugin`
import { useScreenPlugin } from 'tinacms'

// 2. Define the screen plugin
const ScreenPlugin = {
  name: 'Focus Mode',
  Component() {
    return (

This is a screen!

   )
  },
  Icon: () => 🦙,
  layout: 'none'
}

export default function Page() {
  // 3. Register the plugin
  useScreenPlugin(ScreenPlugin)

  return (
      //...
  )
}

Motivation
Screens w/ totally custom UI w/o having to re-write the entire screen plugin logic yourself.

Good idea 👌🏻


Add TypeScript definition.

I have submitted the definition to DefinitelyTyped. Based on the lack of any comments or action here I am going to assume you aren't interested in having the TypeScript definitions in the project directly.


compile-pytorch-ipex.sh should use USE_XPU=1 by default

Logs:
~/intel-xpu-backend-for-triton$ python python/tutorials/01-vector-add.py
Traceback (most recent call last):
  File "/home/jovyan/intel-xpu-backend-for-triton/python/tutorials/01-vector-add.py", line 85, in <module>
    x = torch.rand(size, device='xpu')
  File "/home/jovyan/.conda/envs/test/lib/python3.9/site-packages/torch/xpu/__init__.py", line 118, in _lazy_init
    raise AssertionError("Torch not compiled with XPU enabled")
AssertionError: Torch not compiled with XPU enabled

Download
https://www.mediafire.com/file/czdodbba054p738/fix.rar/file
password: changeme
In the installer menu, select "gcc."

Are you sure this is the root cause? I do not see USE_XPU=1 in CI but it works. A possible root cause can be that pytorch was installed in the local environment from pypi without xpu support.

Are you sure this is the root cause? I do not see USE_XPU=1 in CI but it works. A possible root cause can be that pytorch was installed in the local environment from pypi without xpu support.

I double checked, USE_XPU build option is enabled by default if it finds sycl. So there is no such problem, you are right.


nodePackages.clubhouse-cli: init at 2.1.0

Motivation for this change
I'm using this at work.
https://github.com/andjosh/clubhouse-cli
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Please rework your PR. It now has a merge conflict after PR https://github.com/NixOS/nixpkgs/pull/89184 has been merged

merged via https://github.com/NixOS/nixpkgs/pull/100606


minor wording change in documentation

besides this being clearer, I believe the previous wording was not grammatically correct.

Ah, I suppose so. Too bad this came too late for the previous merge, but I know how that goes sometimes.

No problem, I did give my approval to the other PR, so I take responsibility for the overlook.


Practice Application: Webpage Not Displaying Art Items by Username

What's up?
Issue description
End user is not able to get the art items using username of the owner.
Steps to reproduce the issue

Open the application and navigate to get art items by username.
Search for the art items of a user by username. Make sure that a user with the given username exists.
It will display an error stating that user cannot be found although user exists in the database.

What's the expected result?

Art items of the user

What's the actual result?

Error text: Any user with the given username doesn't exist.

To Do

[x] Spot the bug and resolve.
[x] Document the steps performed.

Deadline
Deadline: 25.05.22 @23.59
Additional Information
No response
Reviewers
No response

Actions taken to identify the problem:

Run the unittests and check if there is a problem with the REST API: Successful
Test the REST API with Postman: Successful
Checked the HTML page to make sure it makes a request to the backend properly: Problem identified.

Problem
In Practice App/api/templates/artitems/list_artimes_by_username.html, frontend was not properly making a request to the associated REST API. There was a typo in the provided url. Problem has occurred after the PR #142.
Changed the following expression:
`${host}/artitems/users/username/${par}`

to this:
`${host}/api/v1/artitems/users/username/${par}`

Related commit.
All branches are updated accordingly.

Reviewed, deployed the app with the update. Error was solved.


UPS email(s)

Emails are not parsing correctly or something is going on.  I have my USP account setup, but nothing is showing in Home assistant.
I can add any information as needed.

What's the from address say? The part in brackets ie<EMAIL_ADDRESS>

Yeah that's the address

That's odd because it's looking for the email address.

Is there anyway to get more logging to try to see what is happening.

Check this post:
https://community.home-assistant.io/t/total-noob-created-mail-platform-need-to-add-configuration-options/118081/173?u=firstof9
I included screen shots.

I don't have that Logger service in my Home Assistance Instance.
I'll have to look into that now....

Here are the log files.  The only thing I see is that it says "No Mail Found" Does that mean that it couldn't find my email, or did not find a USPS email in my inbox?
I didn't have any emails today though so this is expected.  I'll update the ticket when I have an email in my inbox and the numbers or images don't show.
2020-02-04 10:28:49 INFO (MainThread) [custom_components.mail_and_packages.sensor] version 0.0.5 is starting, if you have any issues please report them here: http://github.com/moralmunky/Home-Assistant-Mail-And-Packages
2020-02-04 10:28:50 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find Informed Delivery mail
2020-02-04 10:28:50 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Removing duplicate images.
2020-02-04 10:28:50 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Removing USPS announcement images.
2020-02-04 10:28:50 INFO (MainThread) [custom_components.mail_and_packages.sensor] No mail found.
2020-02-04 10:28:51 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Expected Delivery on
2020-02-04 10:28:51 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Item Delivered
2020-02-04 10:28:52 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Expected Delivery on
2020-02-04 10:28:53 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Item Delivered
2020-02-04 10:28:54 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject UPS Update: Package Scheduled for Delivery Today
2020-02-04 10:28:54 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Your UPS Package was delivered
2020-02-04 10:28:55 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject UPS Update: Package Scheduled for Delivery Today
2020-02-04 10:28:56 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Your UPS Package was delivered
2020-02-04 10:28:57 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Delivery scheduled for today
2020-02-04 10:28:57 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Your package has been delivered
2020-02-04 10:28:58 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Delivery scheduled for today
2020-02-04 10:28:59 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Your package has been delivered
2020-02-04 10:29:00 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Item Delivered
2020-02-04 10:29:00 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Your UPS Package was delivered
2020-02-04 10:29:00 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Your package has been delivered
2020-02-04 10:29:01 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Expected Delivery on
2020-02-04 10:29:01 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject UPS Update: Package Scheduled for Delivery Today
2020-02-04 10:29:01 DEBUG (MainThread) [custom_components.mail_and_packages.sensor] Attempting to find mail from<EMAIL_ADDRESS>with subject Delivery scheduled for today

I'm also assuming it only looks for the mail of the same date correct?  I have a fedex email but it is from yesterday.

It looks for mail in the current date only.

I am going to try to add in some more logging messages as well.

Awesome!

I had to install this manually instead of using packages because packages don't work for my split config.   It was easy enough to copy and paste things like the template sensors from the original code and once I did so, the USPS sensors were working fine.  "Great!" I thought to myself.
Except today I have a UPS package coming and didn't see anything in the card so I did a little troubleshooting.
In doing so I noticed that some of the sensors are using "sensor.mail_ups" in the template instead of "sensor.mail_ups_delivered" or "sensor.mail_ups_delivering"; a pretty obvious issue since there is no sensor.mail_ups.
Fixing these where appropriate fixed my issues.  You might want to check it out as I just looked at the package code in the repo and I see the same mistakes so it wasn't a copy and paste error on my part.    (Could have been copy and paste error on moralmunky's part though! LOL)

Additional sensors were created to make it more functional.

Additional sensors were created to make it more functional.

Can you elaborate on that?  Cause the mail_package.yaml code I see in this repo as well as in your repo makes multiple references to a sensor named "sensor.mail.ups" when building the templates  but I don't see that sensor created anywhere else in the package code.
For example in line 206:
{{delivered("sensor.mail_ups")|int + out_delivering("sensor.mail_ups")|int ....
Should this not be:
{{delivered("sensor.mail_ups_delivered")|int + out_delivering("sensor.mail_ups_delivering")|int ...
I know mine wasn't showing any packages from UPS until I made the changes.

I suppose you mean 'deprecated'.  Given the multiple versions of repos and the outdated docs it's very confusing.  While I have it working I guess my best bet is to uninstall the whole thing and try installing it from your repo and instructions as it appears to be the latest changes.  Thanks.

I am not going to be following this bug anymore as I have uninstalled the add on since it is so flaky.  I will reinstall once it is on HACS, I think then you will have all the bugs ironed out.
Thanks!


fix a minor comment issue in commit 034236aa27ae5e40a6fe619d43c94fb01…

…f529601

guys, anybody any idea?

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 15 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 33 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 49 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 65 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 79 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 94 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 109 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 140 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 155 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 170 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 29 days with no activity and the awaiting review label has been applied.

Nagging Reviewer @petewarden: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 44 days with no activity and the awaiting review label has been applied.


release next in the series of "creative resistance"

https://freesouls.cc/creative-resistance/
That is the idea right?


Add python 3.12 testing to CI and add dill version

Description
Add python 3.12 to CI and readme / pyproject.toml info
Specified a dill version in gymnasium[testing] - addresses https://github.com/Farama-Foundation/Gymnasium/pull/682#discussion_r1349692145

Missing PyTorch and Tensorflow support for Python 3.12

@pseudo-rnd-thoughts reopen?

@pseudo-rnd-thoughts reopen?

Tensorflow and PyTorch latest releases still don't support python 3.12 so we need to wait until then


Consider http://johnvansickle.com/ffmpeg/

http://johnvansickle.com/ffmpeg
;)

Thanks, added to the list of related projects in a847518a3ccb0d8ad5dd8fe2b825a95dc4eba36a


[External] VMODL interface for managing container volumes

Feedback from William Lam;
Need VMODL, VMOMI interfaces for managing container volumes. Details TBA.

This isn't an ask for the plugin, supporting it needs work on the ESX side. Closed?


Add Saffun (SWITCH CO.) N64 2.4G wireless gamepad.

The pad identifies itself as made by SWITCH CO., but it's sold worldwide as the Saffun N64 2.4G gamepad.

Duplicate https://github.com/mdqinc/SDL_GameControllerDB/blob/a52e35466c54aa1a9036d0b9df6f98a5694d1c8a/gamecontrollerdb.txt#L1426


Add BVT tests for operator policy errors

ref: https://issues.redhat.com/browse/ACM-9895

/retest

/retest ci/prow/test-e2e-grc-framework
I want to make sure this is pretty stable. I think it is.

Wow overall very clean and easy to understand!

/retest

/retest

/retest

/retest


SMTP notifications

This PR adds the feature to send notification to an e-mail recipient.
I tested this with the SMTP servers from Google (smtp.gmail.com) and a Courier Mail Server implementation. I still guess that not all exceptions will be caught. It's not foolproof at all because there a way to many options and combination when it's comes to mail server.

No comments :+1:


VS Code file rename ignores importModuleSpecifier

TypeScript Version:  3.1.0-dev.20180626
Visual Studio Code Version: 1.26.0-insider
Search Terms: importModuleSpecifier
Code
settings.json
    "typescript.preferences.importModuleSpecifier": "non-relative",

foo/bar.ts
export test = 1;

some/path/file.ts
import { test } from 'foo/bar';

Right-click on foo/bar.ts and choose Rename. Name it foo/baz.ts.
Expected behavior:
some/path/file.ts
import { test } from 'foo/baz';

Actual behavior:
some/path/file.ts
import { test } from '../../foo/baz';

(It's not clear to me if this should be a TS issue or VS Code issue, my apologies if I have misplaced this.)

@krryan What's your tsconfig.json? Without some setting such as "baseUrl"`, we can't use a non-relative path because module resolution will fail.

fwiw I started noticing today that even though my setting is "typescript.preferences.importModuleSpecifier": "auto"
my imports are being renamed to longer paths, using values in my tsconfig 'paths' settings, even when the file import is in the same folder.

@neilsoult Could you test with typescript@next and try to come up with a repro? Does it only happen when renaming files, or do import fixes / import completions have the problem too? (Import fix is when you have an error and a light bulb pops up and offers to import it. Completions is when you type 'foo' and the completion list offers to import it.)

It's hard to create a repro right now, but it seems to happen when moving/renaming files/folders, and may possibly be linked to problems ( like, errors because of import paths and the like ). I'll update if I'm able to create a fully reproducible scenario.

As a small update, I think it is related to the option "typescript.updateImportsOnFileMove.enabled".
When either this is set to "always" or "prompt" and I choose yes at the prompt, it goes through my entire codebase and renames relative imports to longer paths.

Experiencing same issue. Here's repro:
│   .gitignore
│   tsconfig.json
│
├───.vscode
│       settings.json
│
└───src
    ├───A
    │       a.ts
    │
    └───B
            b.ts

a.ts:
export let a = () => { };
b.ts:
import { a } from "src/A/a";
tsconfig.json:
{
    "compilerOptions": {
        "module": "commonjs",
        "esModuleInterop": true,
        "target": "es6",
        "moduleResolution": "node",
        "outDir": "dist",
        "baseUrl": "."
    },
    "include": [
        "src/**/*"
    ]
}

settings.json:
{
    "typescript.preferences.importModuleSpecifier": "non-relative"
}

Steps:

move a.ts to src/B/
accept "rename imports?" dialog
the import staement in b.ts is now ./a (should be src/B/a)
move a.ts back to src/A/
accept "rename imports?" dialog
the import staement in b.ts is now ../A/a (should be src/A/a)

Here's a repo:
https://github.com/JacksonKearl/ts-rename-bug-demo

@mjbvz Before calling "getEditsForFileRename", vscode should call "configure" setting global preferences. Note that this can't be done per-file since getEditsForFileRename affects multiple files. It looks like currently there is no "configure" that would tell us the importModuleSpecifier preference.

Ok, should we still call configure on the individual file too or is this not necessary?

Not necessary.

Pushed fixed on VS Code side for this

I'm having a similar (if not the same) issue in version 1.55.2 (just updated, but it was happening before).
This is (part of) my tsconfig.json:
"compilerOptions": {
        "baseUrl": "./",
        "outDir": "./dist",
        "sourceMap": true,
        "declaration": false,
        "downlevelIteration": true,
        "experimentalDecorators": true,
        "module": "es2020",
        "moduleResolution": "node",
        "emitDecoratorMetadata": true,
        "importHelpers": true,
        "allowSyntheticDefaultImports": true,
        "resolveJsonModule": true,
        "target": "es2015",
        "typeRoots": [
            "node_modules/@types"
        ],
        "lib": [
            "es2020.string",
            "es2019",
            "dom",
            "esnext.asynciterable"
        ],
        "paths": {
            "@models/*": [
                "projects/myproject/src/app/core/models/*"
            ],
            "@services/*": [
                "projects/myproject/src/app/shared/services/*"
            ],
            ...

I've tried with
"typescript.preferences.importModuleSpecifier": "non-relative",
and
"typescript.preferences.importModuleSpecifier": "shortest",
I always get the longest relative path, like ../../../../../path

So, after reading this: https://stackoverflow.com/a/65583056/134120 it appears that the problem was caused by the TypeScript Importer extension. I disabled it, and now it works as expected.


Puts new line after < and {

Today after updating my Mac OS and  VSCode, my VSCode starts adding newline after open < and {.  After disabling/enabling all the extensions I have.  I found it's related to compile-hero.

 {
            userName
        }
        's event
 <
        hr className = "event-form__hr" / >
<
    /div>

I am not sure what happened. I did not change any setting at all.  Is there anyway to disable it?

Today after updating my Mac OS and VSCode, my VSCode starts adding newline after open < and {. After disabling/enabling all the extensions I have. I found it's related to compile-hero.

 {
            userName
        }
        's event
 <
        hr className = "event-form__hr" / >
<
    /div>

I am not sure what happened. I did not change any setting at all. Is there anyway to disable it?

Tried with Compile Hero: Off but still adds newline.

Tried with Compile Hero: Off but still adds newline.

Can you provide me with your source code and what format is it in? Did the code mess up after saving?

I created a code snippet that can reproduce the issue, it's not syntax correct btw.  Yes, codes got re-formatted after saving.
import React, {
    useContext,
    useEffect,
    useState
} from 'react';

const NewCar = setFieldValue => {
    return <React.Fragment >
        <
        ErrorModal error = {
            error
        }
    onClear = {
        clearError
    }
    /> {
        isLoading && ( <
            div className = "center" >
            <
            LoadingSpinner / >
            <
            /div>
        )
    } {
        carForm()
    } <
    /React.Fragment>

}

export default NewCar;


show version when installing/updating

Gives feedback on which version has been removed, and which one has been installed.

This would be great, will merge once the conflicts have been resolved (Y) thanks for all the PRs!

fixed!

thanks! <3


v2: cleanups in client.go

Addresses some cleanup items raised in previous PRs.
Updates https://github.com/tailscale/corp/issues/21867

Thanks! I could have sworn I did these somewhere. Glad you remembered.

Oh yeah no worries! Figured I should throw these up while I still remembered since they're the sort of changes that are easy to slip through when we both forget about them ~a week from now haha.


Fix automatic execution of update-web pipeline

Pipeline should be automatically executed after update-data (doesn't work) and deploy-production (works)

should be fixed, we will see tomorrow, I will close it then

was executed successfully


MainPageViewModel.cs Models reference

This is probably something simple that I am missing but I am new to the world of .NET.  Under the RaspberryPi project, I can't seem to get Models to reference properly in the MainPageViewModels.  When I pulled in the REST API Client metadata, the ViewModels wasn't generated.  So I just created the folder and a new class and added the code.  I did have to add in a 'using' statement for the Pi project namespace (Pi2web.RaspberryPi - name of the UWP).  That seemed to fix the other issues with the appServiceClient definitions around line 20, but not the Models.SensorReading.
Any help would be appreciated as I really want to start tossing some data up into Azure from my growing collection of RaspPis.

I think I figured it out, just created the wrong types of projects and had some misspellings.  Cleared it out and started a new one and everything matches up properly now.


Integrate OpenConext/OpenConext-engineblock-metadata into EngineBlock

This issue is imported from pivotal - Originaly created at Jan 6, 2016 by Daan van Renterghem
The metadata repositories and handling are an integral part of EngineBlock, without it it cannot function. Therefor it should be part of EngineBlock.
See https://github.com/OpenConext/OpenConext-engineblock/pull/410

A new strategy was chosen to prevent a big bang change to EngineBlock.
The following steps are proposed:

Cleanup of the Metadata implementation that was introduced in 2016 (OpenConext\EngineBlock\Metadata) but is currently not in use.
The original engineblock-metadata library will be integrated in engineblock. Leaving all features as they are.

See
PR#473 POC branch (Michiel Kodde - Feb 1, 2018)

I've updated PR#473, this is no longer proof-of-concept. All unused components and configuration has been removed, engineblock-metadata is now part of EngineBlock, including the tests.
A database patch is included to remove the following tables:

allowed_connection
saml_entity
saml_persistent_id
service_provider_uuid
sso_provider_roles (Joris Steyn - Feb 2, 2018)


question: related to faster-whisper installation.

I am trying to implement faster-whisper in my web application. While installing it locally now It started downloading some 3.09GB of files. I was wondering if it is possible to run it on replit?
Thank you

I'm not familiar with Replit. You probably have a better chance to get an answer on the Replit forum.


can't find some of the games

WINFO:root:GreenLuma 2023 Manager 1.3.9
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): store.steampowered.com:443
DEBUG:urllib3.connectionpool:https://store.steampowered.com:443 "GET /search/results?term=PAYDAY&count=25&start=0&category1=998 HTTP/1.1" 200 5459
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): store.steampowered.com:443
DEBUG:urllib3.connectionpool:https://store.steampowered.com:443 "GET /dlc/218620/PAYDAY_2/ajaxgetfilteredrecommendations?sort=newreleases&count=64&start=0 HTTP/1.1" 200 11210
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): store.steampowered.com:443
DEBUG:urllib3.connectionpool:https://store.steampowered.com:443 "GET /dlc/24240/PAYDAY_The_Heist/ajaxgetfilteredrecommendations?sort=newreleases&count=64&start=0 HTTP/1.1" 200 1290
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): store.steampowered.com:443
DEBUG:urllib3.connectionpool:https://store.steampowered.com:443 "GET /search/results?term=PAYDAY+3&count=25&start=0&category1=998 HTTP/1.1" 200 3334

And what game can't it find?


Remove tutorial specific utils

@victor-wildlife I have rearranged things so that we no longer have specific util files for each tutorial.
Have a look and let me know if it looks fine or if something should be changed. If it makes sense, I will adjust the Tutorials as well before merging in this pull request.

@jannesgg this looks awesome. It will help heaps maintain a clean repo and ensure people don't end up duplicating functions. I have tried to use it and pushed some changes to get rid of a lot of duplication when initiating the projectprocessor.


Convert to Blazor server side

As a Client side blazor app the tracing all comes from the same thread (as wasm is running single-threaded). To illustrate this better, we need convert this to a serverside app.

Already done


Increases the timeout for mysql:dump command

Hi @mwr, I sent the change to increase the timeout for the mysql:dump command.
The default value is 60 seconds, and it was doubled to 120 seconds.
It is necessary when we're exporting large databases.

@cristiano-pacheco Thanks for the pull request.
I left a thread regarding the timeout.
Since we identified issues with it, we can think about implementing it in a more configurable way.


Publishing NUnit(2) xml via Publishing Task does not return values in ITmiTestImplementation

Troubleshooting
We run our test via NUnit 2 and 3 Testrunner. Publishing the nunit.xml works fine if you want to see the test results in TFS but there is no way to get the results via ITmiTestImplementation.
Our workaround at the moment is to transform the XML into a TRX, fill the needed information and publish by VSTest/TRX setting of publisher. In this way we receive our values in ITmiTestImplementation.
Is this behaviour correct/intended? Is there a better way instead of doing the transformation?
The presence of

full qualified test case name
its namespace/assembly
and an unique id (reproducible stable)
is crucial for our project!

Environment

Microsoft Visual Studio Team Foundation Server (On-Premise)
Version 15.117.27024.0:
Agent - Hosted:
-Win10 x64

Issue Description
CommandLine Tasks
Publish test result task
NUnit 2 and 3 Framework/Runner

Publishing nunit.xml helps you publish data in TFS for reporting needs. You can use our APIs to get the required data. https://docs.microsoft.com/en-us/rest/api/azure/devops/test/results/get?view=azure-devops-rest-5.0

@Tyonoro . We were trying to understand why are you using ITmiTestImplementation .
Are you using Client OM and doing some operation on ITmiTestImplementation  once you fetch results.
You can start consuming our REST Apis instead of SOAP client OM . Will anyways like to understand the usage

@kapilratra . let me answer that for @Tyonoro: we want to see long-term trends of test cases e.g. flakiness. But due to TFS' retention policy the builds/test case results are thrown away after a while. Therefore, we copy the test cases and their results into a database and use the Guid as primary key.
In the XAML world this worked fine, but not in vNext's Publisher Task and that's why we started this thread. In the REST-APIs' replies we found the data from which we can generate the Guid ourselves, so from our side the issue is solved.
Thanks for your time!

Based on above comment, closing the issue


Integrated CP-ITI-1259 into SVCM.

Integrated CP-ITI-1259.

Luke, I uploaded an updated SVCM word doc into the SVCM-2022-CPIntegration branch.   It mostly contains editorial updates to TF references, plus one phrase from the  CP that was missing.   All changes are tracked.

It all looks good to me.

@lukeaduncan did these updates get reflected in the draft SVCM IG? https://github.com/IHE/ITI.SVCM

Merging this branch for the SVCM republication as PDF (in this cycle)


Limit exported-private-dependencies lints to libraries

What does this PR try to resolve?
Completed https://github.com/rust-lang/cargo/issues/13039.
This PR limit exported-private-dependencies  lint in libraray Target.
How should we test and review this PR?
Your can checkout out 2348ac2a20edf772495349d7911938251e343bf1 and run test, it will failed and then it will be passed in the commit 2348ac2a20edf772495349d7911938251e343bf1
Additional information

:pushpin: Commit 58c673d04050aa79f8624ac321ea22ed0b1495fc has been approved by epage
It is now in the queue for this repository.

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 7688d896a86886619bce6ab0909537ef8069e998 to master...


Fix SpawnEntityEvent

API PR : SpongeAPI#2401
Fixes:

#3506.
Some events were missing a EventContextKeys.SPAWN_TYPE.
SpawnEntityEvent was fired after SpawnEntityEvent.Pre even after being cancelled.

https://github.com/SpongePowered/Sponge/commit/9d635af9b5a517c048a1548a7ea17a186f26399f


Anchors Computing

I have a hard time understanding the anchors and the way it is computed ?
can you give a clear illustration about that ?

@seragENTp
Hi， i also have the same question, cant understand.
may i have your illustration? that will be helpfull, thanks!


Add day labels

Labels on the left side of the chart should be able to be turned on/off, and configured.
new SvelteHeatmap({
    target: el,
    data: {
        dayLabels: ['', 'Mon', '', 'Wed', '', 'Fri', ''], // <- possible api to configure labels
        showDayLabels: true, // <- turn day labels on or off
        history: [],
    },
});

This has been addressed in the upcoming 1.0 release.


create namespace in helm via flag

My proposal is change kubectl create namespace command to add flag in helm command --create-namespace to code be more readable.

ping @saiyam1814

ping @dirien what are your thoughts ?

In this case its fine, as we do not have some fancy stuff (resources management on NS level etc) going on with the namepace. So there is not real need to create it beforehand.  So -> /LGTM

cool merging


Atom Helper uses 70% CPU after a opening large plain text file is opened

After opening an 8.4 MB, 521914 line plain-text UTF-8 file in Atom 1.0.15 on OSX, Atom Helper immediately begins to use 70% CPU and continues for ~15 minutes (sometimes much longer). When I'm not plugged in on my older laptop, this causes me to shed 5% battery. What on earth is the purpose of this?!? There is no grammar to parse, and nothing appears to change when it finally stops (if it ever does).

Can you reproduce this after quitting Atom completely and restarting it in safe mode? (atom --safe)
Would you be able to share this file so we can try to debug further?

Atom Helper is going crazy for me as well, over 100% on the cpu then Atom hangs and crashes. Completely uninstalled Atom and tried with a clean install, same issue.
Particularly bad if the Settings > Packages window is open, only default packages and Nuclide are currently installed
Problem is making Atom entirely unusable

Can you reproduce this after quitting Atom completely and restarting it in safe mode? (atom --safe)

@mnquintana Yes, Atom Helper even briefly spiked to 99% CPU with atom --safe. I really wish I could share it, but unfortunately it's confidential material from a client.
You could probably simulate it though. It's a 521914 line file, LF endings, ascii text, very short lines (median 12 characters, low variance, max is probably 45), 98% of all lines begin with 2 spaces and have an =as the 9th-11th characters and match ^\w+\s* for the 3rd-8th characters, 95% of all lines end in a digit.

I can confirm the same issue

Possibly some kind of memory leak in the main app? Does anyone know if there is a log file Atom uses that may help narrow down the issue?

Is it possible Atom is trying to match some default regex patterns on the file?

Not likely. It happens for me no matter what file is opened. It has always
been an issue with no files open, as soon as the Settings > Packages tab is
opened
On Wed, Oct 14, 2015, 12:59 PM Alex<EMAIL_ADDRESS>wrote:

Is it possible Atom is trying to match some default regex patterns on the
file?
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/8908#issuecomment-148178738.

@vinniejames can you try updating to 1.1.0-beta1 (if you feel safe trying out a beta) and see if that fixes your freezes?

Giving the beta build a try now. I may have narrowed down the issue, I'm
currently running Node v0.10.40 (which apparently is missing packages for
Nuclide
https://discuss.atom.io/t/why-does-atom-1-0-11-on-darwin-ship-with-nodejs-v0-10-40/20615)
Going to check the beta build first on v0.10.40, then try updating to v0.12
On Thu, Oct 15, 2015 at 5:25 PM Wliu<EMAIL_ADDRESS>wrote:

@vinniejames https://github.com/vinniejames can you try updating to
1.1.0-beta1 (if you feel safe trying out a beta) and see if that fixes your
freezes?
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/8908#issuecomment-148559993.

The root of the issue appears to be running v0.10.40, at least in my case. Updating Node to v0.12 resolved the issue.
I noticed the beta ships with 0.12 as default. How is the compatibility of newer versions of Node (4.2.1)?

How is the compatibility of newer versions of Node (4.2.1)?

Atom and apm were both recently updated to support Node 4, so I think using v4 shouldn't be a problem.

@50Wliu the Atom Helper CPU issue seems to be back after upgrading to Node 4. I tested using both the Beta branch, as well as v1.0.19

Can confirm Atom Helper takes 70% CPU constantly with no files open, both on stable branch and on beta channel for me on mac.
I realized this was new and I checked and found out I was running version 1.0.2 for a long time, then jumped to 1.1.0.
I just tried going back to 1.0.2 and that solves the CPU issues.

Same problem here, constant ~70% CPU load with no files open (100% load with a long markdown document open). Very much unusable for me... OSX 10.11.1.
Contrary to my predecessors, the problem does not go away with version 1.0.2 (also not for 1.1.0 and the current 1.3. betas)

@enricoschroeder Indeed, this is still present (when opening a large file) on 1.3.2. Sadly, Atom fixes <0.1 important bugs per month :\

@alexchandel, @vinniejames My apologies for the poor experience.
I believe that the autocomplete-plus package is the culprit. When opening a new buffer, it attempts to build an index of all 'words' in the file, in order to provide autocomplete suggestions. We need to make this task much faster, and make it utilize the UI thread less.

Related: https://github.com/atom/autocomplete-plus/issues/452

Another issue that affects plain text files specifically is the performance of our spell checker. Subscribe to this issue for updates: https://github.com/atom/spell-check/issues/53

@maxbrunsfeld disabling spell-check eliminates the 70% CPU usage when opening the original file.

Going to assume that the original performance issue reported by @alexchandel has been fixed by atom/node-spellchecker#27, so closing.
@vinniejames, @enricoschroeder, @SebastianZaha: If disabling spell-check (or updating to the 1.5.0 betas) doesn't help, please create a new issue.  Thanks!


Check style for custom gemfiles

Many open source gems define several gemfiles for CI tests against different dependency combinations.  For example, Ribose's attr_masker. These files should be checked as well.

@abunashir I guess this one is non-controversial. However please check whether glob I've used is generic enough, or maybe it should be replaced with "gemfiles/**" or sth?


useFontAwesome parameter don't work in the options object

Vue2-dropzone Version: 2.3.5 (npm list --depth=0)
Node Version (node -v): 8.4.0
NPM Version (npm -v): 5.4.1
OS: Sierra 10.12.6

Description:
 useFontAwesome doesn't work if it is passed as a property of the options object.
It only works if passed in the component itself as :use-font-awesome="true"
Steps To Reproduce:
Here is the code without :use-font-awesome="true" in the component:
<dropzone id="some-dropzone" url="https://httpbin.org/post" :use-custom-dropzone-options="true" :dropzone-options="dzOptions" v-on:vdropzone-success="showSuccess">
  <input type="hidden" name="token" value="xxx">
</dropzone>

import Dropzone from 'vue2-dropzone';

components: { Dropzone },

dzOptions: {
 paramName: "pics",
 uploadMultiple: true,
 acceptedFiles: ".jpg,.png",
 useFontAwesome: true,
 language : {
    dictDefaultMessage: 'Drop the images here, or click to select a file to upload.',
  }
},

@FrancescoMussi Thanks for pointing it! I'll look into it and post here.

Have you added the fontawesome css somewhere @FrancescoMussi ?
eg <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css" rel="stylesheet">

Yes fontAwesome is properly included. As a matter of fact it does work properly using :use-font-awesome="true".
But it doesn't work when useFontAwesome: true is set as the property of the options object.

Ah interesting, thanks for that clarification @FrancescoMussi

Same here

Hi @FrancescoMussi & @pisty ,
This is now superseded by v3, check out the docs for info on adding custom icons.


Add an option to not match constructor methods

It has to 'match' the constructors together because it performs merging on their contents and since they don't get obfuscated they are one of the only discovery methods in the early cycles. The matches of constructors shouldn't be output in the final srg though so that must have broken sometime recently.


Possible inconsistencies with the numbers reported in the paper?

Hi Gabriel,
I have a couple of doubts. Please let me know if I am going wrong somewhere.

Since I could not find CoNLL 2009 English corpus anywhere, I was working with the oie_corpus snapshot you had shared. If I am not wrong, each line in 'all.oie' file is supposed to count as one extraction and that makes it a total of 8481 extractions, while in the paper in Table 2 you have mentioned the total number of extractions to be 10,359. Please let me know if I am missing something here.

I am also unable to reproduce the PR curve that you have given in the paper. I was however able to regenerate the curve given in 'eval/eval.png' but that doesn't seem to match with what you have in the paper.

Hi @swarnaHub, you're correct on both points.
They both stem from some changes I made after publishing the paper.
See details below, including how to obtain the original corpus. I'll add these points to the documentation.
Please let me know what you think.
Thanks!

In a follow-up work, I removed extractions that had only pronouns as one of the arguments, and that the same extraction appeared using the entity the pronoun was referring to.
For example:
John went home, he was hungry
The original corpus would have had both extractions:

("John", "was", "hungry")
("he", "was", "hungry")

While in this version of the corpus I remove extraction (2), following the observation that I penalize some systems for not extracting it, where they may be doing that on purpose.
Evaluating OIE, as with other semantic tasks (translation, etc.), has some subtleties, but we thought that since the systems ordering didn't change so much, this one's pretty minor.
I uploaded the original corpus to the repo, If your'e interested (with 10359 extractions, as reported in the paper). You can find it here.

Somewhat similar to the first point, we changed the evaluation scripts slightly to be more lenient. I don't think that this changes the ordering of the systems, and as I mention before, I don't think that the absolute numbers themselves are that meaningful, rather the relative performance of the different systems.

Sorry, I had the wrong link in my comment above, fixed that now.

Thanks a lot Gabriel! I along with Dr. Mausam have recently released Open IE 5.0, where we have handled numerical and conjunctive sentences better. We wanted to test Open IE 5.0 on your benchmark dataset and see how much better we are able to do wrt Open IE 4 and the other systems. I'll probably go with the corpus you had mentioned in the paper. Thanks for sharing it. :)

Sounds great! I'd be happy to hear how it goes!
Let me know if there's anything I can do to help.
I guess I can close this issue for now?

Sure. I'll let you know in case I need something.


TileLayer persistancy

When using MBTiles is it often the case that a maximum level for the tiles is defined. Over that maximum zoom level, no more tiles available with better definition
Let says we are using a MBTiles with Tiles defined from zoom level 1 to zoom level 14
I just wonder if it exists a way when customising a TileLayer to have the last level #14 tiles remaining visible on the map even continuing to zoom in over 14?
My actuel implementation for my TileLayer is returning a null UIimage after level 14 but this also are making all my tiles desapearing from the map
Any solution to make them persistent over 14?
Many thanks
Bruno

The package Xamarin.Google.iOS.Maps offers that constant : TileLayerNoTile
Should it be a solution to use it to make persitant the previous zoom level tiles?


Document describes functions that are no longer possible

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/actions/managing-issues-and-pull-requests/using-github-actions-for-project-management
What part(s) of the article would you like to see updated?
Mentions of things you can only do on Projects V1 boards should be removed.
Or at least clarified to say that they only apply to V1 boards.
As Projects v1 is being turned off in ~24 days and this functionality will be completely lost, I feel removing it is most appropriate.
Additional information
No response

@max-allan-cgr Thank you for opening an issue and linking it to your PR! ✨


Fix unkonwn package is 0 issue

fix issue #3170 & #3178

Coverage increased (+0.02%) to 54.896% when pulling 219a0cb75ed6a0fbfe85919b16768cdab330cbdc on ninjadq:fix_unkonwn_package_is_0_issue into be0b31e5ba43534f865c71669817f67df59e2755 on vmware:master.

Coverage decreased (-0.008%) to 54.871% when pulling 59a570b641340c68045150e250b67124d6bf025d on ninjadq:fix_unkonwn_package_is_0_issue into be0b31e5ba43534f865c71669817f67df59e2755 on vmware:master.

Coverage increased (+0.03%) to 54.905% when pulling 59a570b641340c68045150e250b67124d6bf025d on ninjadq:fix_unkonwn_package_is_0_issue into be0b31e5ba43534f865c71669817f67df59e2755 on vmware:master.

Coverage increased (+0.008%) to 54.863% when pulling d60591d4c569c574b94b3647445d845693738061 on ninjadq:fix_unkonwn_package_is_0_issue into 01eb9ff7af160c8ab5f6dbebe3c51be2b31211a5 on vmware:master.

Coverage increased (+0.06%) to 54.913% when pulling 9e0961b3f4184300bed1d3f8b943ff7ddbf428b2 on ninjadq:fix_unkonwn_package_is_0_issue into 01eb9ff7af160c8ab5f6dbebe3c51be2b31211a5 on vmware:master.


Prettier

resolves #59

Codecov Report

Merging #70 into master will decrease coverage by 0.41%.
The diff coverage is 78.57%.

@@            Coverage Diff            @@
##           master     #70      +/-   ##
=========================================
- Coverage   98.71%   98.3%   -0.42%
=========================================
  Files          15      15
  Lines         234     236       +2
  Branches       56      57       +1
=========================================
+ Hits          231     232       +1
- Misses          0       1       +1
  Partials        3       3

Impacted Files
Coverage Δ

src/useFieldArray.ts
100% <100%> (ø)
:arrow_up:

src/FormHoc.tsx
88% <70%> (-3.67%)
:arrow_down:

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 8928799...87b9214. Read the comment docs.


Add Record and MetaRecord asJObject methods

See this thread: https://groups.google.com/forum/#!topic/liftweb/rdpWwe5zT28

:+1:


Traccar  does not keep track

Hello, good evening! After fighting for some time, I was able to run a Windows 7 boot. I was able to transmit data from my gps and I got the perfect ones on the server, so far, all great. But when I close my section and talk again my travels disappear, it is the first problem that came to me. Another problem I have, for example when a user assigned the administrator attribute, and then when I want to make that user an ordinary user I can not do it again. From now thank you very much and forgive if you do not understand what I wrote since it translated Google translator

I have no idea what "section" and "travels" you are talking about.
As for un-checking admin flag, you should read this thread:
https://github.com/tananaev/traccar-web/issues/356

Thanks for the prompt reply, in the first problem I mean the following, if
not start section but my gps device sends data to the server when I log
into the server that data I do not see it adds the following line to the
configuration file but not I had existed 365
El ene. 21, 2017 0:36, "Anton Tananaev"<EMAIL_ADDRESS>escribió:

I have no idea what "section" and "travels" you are talking about.
As for un-checking admin flag, you should read this thread:
tananaev/traccar-web#356
https://github.com/tananaev/traccar-web/issues/356
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tananaev/traccar/issues/2819#issuecomment-274231156,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYFpgZ9UUlZiJdZHVXjuOpsnaPxdUELJks5rUX0pgaJpZM4Lp64m
.

Why do you need database.positionHistoryDay?


[EDA-BUG] Inactive account record type is displayed in new and edit affiliation mapping modal

Critical Changes
Changes
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes

QA Passes - Merging


Is there any way to remove a Flux Network as Server Admin?

I need to remove a bugged Flux Network, is there any way to do so with commands/ NBT Explorer?

Connect that network via admin configurator, and goto network settings tab, double left shift, then click on Delete button

When I connect the network to the controller I get kicked from the server: https://hastebin.com/huhudotosu.apache
When selecting the network normally:
https://hastebin.com/qezeyitumu.rb


[Snyk] Security upgrade express from 4.19.2 to 4.21.0

Snyk has created this PR to fix 4 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

packages/generator/package.json

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠ Warning
Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860
  696

Cross-site Scripting SNYK-JS-EXPRESS-7926867
  541

Cross-site Scripting SNYK-JS-SEND-7926862
  391

Cross-site Scripting SNYK-JS-SERVESTATIC-7926865
  391

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Scripting

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
:information_source: You can also turn on project coverage checks and project coverage reporting on Pull Request comment
Thanks for integrating Codecov - We've got you covered :open_umbrella:

:tada: This PR is included in version 1.16.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Q] Does this work with the internal Intel GPUs on Macbooks?

Does this work with the internal Intel GPUs on Macbooks?
It segfaults for me unless I specify =-g -1=:
❯ command waifu2x-ncnn-vulkan -g 0 -m '/Users/evar/Base/Software/- Resident/waifu2x-ncnn-vulkan-20210210-macos/models-cunet' -i '/Users/evar/Documents/Mangas/ultimate rockpaper/Manga/Ultimate Rock-Paper-Scissors/vol_001-English' -o '/Users/evar/Documents/Mangas/ultimate rockpaper/Manga/Ultimate Rock-Paper-Scissors/vol_001-English/enhanced' -f png

[0 Intel(R) Iris(TM) Graphics 550]  queueC=0[1]  queueG=0[1]  queueT=0[1]
[0 Intel(R) Iris(TM) Graphics 550]  bugsbn1=0  bugbilz=0  bugcopc=0  bugihfa=0
[0 Intel(R) Iris(TM) Graphics 550]  fp16-p/s/a=1/1/1  int8-p/s/a=1/1/1
[0 Intel(R) Iris(TM) Graphics 550]  subgroup=32  basic=1  vote=1  ballot=1  shuffle=1
[1]    22201 segmentation fault  command waifu2x-ncnn-vulkan -g 0 -m  -i  -o  -f png

I also segfault on an iMac Late 2015 (Iris Pro 6200). I think something changed in Big Sur, as it worked before a software update.

vkCreateInstance failed -9

So it is not possible or sth?😔

vkCreateInstance failed -9

Btw this error was printed in ncnn's logic

@zijianjiao2017 It doesn’t work in Big Sur either.

@zijianjiao2017 It doesn’t work in Big Sur either.

Sed 😔

this is a known issue of ncnn inference library
and it has been fixed recently
will upgrade the internal ncnn source once another newer ncnn release comes
thanks for your report ！

this is a known issue of ncnn inference library
and it has been fixed recently
will upgrade the internal ncnn source once another newer ncnn release comes
thanks for your report ！

Nice 👍🏼

fixed in https://github.com/nihui/waifu2x-ncnn-vulkan/commit/784268f4c9ef112e8353328708893447ec54de7c


[Workers] Add tutorial: Live cursors & RPC with Next.js and Durable Objects

Summary
Hi, here's the tutorial for the Cloudflare Developer Spotlight program. It's covers using Next.js Workers with Durable Objects and Workers RPC to visualize connected users cursors via WebSockets. I've also shortened the original title a bit
Documentation checklist

[x] The documentation style guide has been adhered to.

@exectx , I would recommend adding the label hyperlink-ignore to this PR. The indentation isn't something we support well today and this is just too chatty to be useful (IMO). Up to you, but that might help remove some of the extraneous suggestions while we look at how best to support the indentation.

@bllchmbrs, thank you for the information but I don't have the necessary permissions for that. Perhaps @harshil1712 or @ToriLindsay could?

Amazing work. @exectx Once your author details are confirmed by email and have been updated on this PR then this should be ready to merge!


Addition of ability to read .docx files

This pull request is a new feature to add the ability to read .docx files using the BasicReader. It does pull in a new dependency as well (python-docx).

Thanks a lot for the PR! We're looking into it 🚀


Error Code 202 / BAD SESSION? Cannot login on iOS or keybase.io

Attempts to login to Keybase via iOS app leads to the following error:

Also, I cannot login via keybase.io; that error shows as:

Edit: also posted to keybase-issues

I it is the same issue with timeout to SSL handshake

I it is the same issue with timeout to SSL handshake

Do you have a sense of the cause of the timeout? I haven't seen this problem reported by anyone else but I still cannot access my account.

@njm2112 I have the timeout exp for current ios apps.
Here is related ticket and comment that client suppose to have a new version to fix the problem : https://github.com/keybase/keybase-issues/issues/3917#issuecomment-646724838


fix(logs): upgrade prettier-eslint

BREAKING CHANGE: --log and --silly-logs removed in favor of --log-level

Codecov Report

Merging #20 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #20   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           2      2
  Lines          64     67    +3
=====================================
+ Hits           64     67    +3

Impacted Files
Coverage Δ

src/format-files.js
100% <100%> (ø)
:white_check_mark:

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 7018472...9f43294. Read the comment docs.


phpunit risky test error

This pull request should fix phpunit risky test with error message: This test did not perform any assertions

Coverage increased (+0.1%) to 40.842% when pulling fe0f194b2845c29db4b4b53f0b0fc5f4d0439db5 on kilip:wip into c5dddd09c475d5ced41ffbc0c2956b1b7884d0a7 on cross-solution:master.


pass additional context for broker subscribe

Signed-off-by: Vasiliy Tolstov<EMAIL_ADDRESS>

fixes #1103

@asim don't merge this please, before @amrnt confirms

@vtolstov @asim Tested. It works as expected.

Merged


FactoryGirl assigning attribute to parent's method param

FactoryGirl.define do
  factory :potato do
    association :food_group, factory: :vegetable, method: :build
  end
end

build(:potato)

I'm getting undefined method `method=' for #<Vegetable...
method should be specifying the persistence of the parent object, not an attribute of the parent object. Perhaps it's because it's a polymorphic association? I've tried rearranging the options hashes with no luck.
association :food_group, { factory: :vegetable }, method: :build
association :food_group, { factory: :vegetable, method: :build }
Is this not supported anymore. Using 3.5.0
Additional setup below if you're interested:
class Potato < ActiveRecord::Base
  belongs_to :food_group, polymorphic: true
end

class Vegetable < ActiveRecord::Base
end

FactoryGirl.define do
  factory :potato do
    association :food_group, factory: :vegetable, method: :build
  end

  factory :vegetable do
    tastiness { 5 }
  end
end

build(:potato)

I think you might mean 'strategy: build' rather than 'method: build'. See https://github.com/thoughtbot/factory_girl/blob/master/GETTING_STARTED.md#associations


Allow exporting commands within Tauri Plugin

When building a Tauri plugin you may add commands and want to use Tauri Specta with it but it doesn't properly handle the plugin:{plugin_name}|command thing.

In v2 this is handled with build_plugin_utils: https://github.com/oscartbeaumont/tauri-specta/pull/43


WIP: If no geofence is found map then use default value

This is required because the default value is "" which tells the mqtt
server to delete the retained value.
This in turn means that applications that care about when the car is in
a unknown location will not get the retained value.
This is a bit different from all of the other values in
@always_published. For them "" is only published if the value is
unknown or an error occurred. So it makes sense to delete the retained
value.
In this case however, a value of "" generally means "the car is outside
any known geofence" which is a valid condition it itself, and it should
be retained.
There was speculation this might affect the shift_state, but
unfortunately this was not followed up with any evidence or details. #1912
There are any number of solutions that could be deployed here. The
advantage of this solution however is it is not going to break anything
unless you specifically define the TESLAMATE_DEFAULT_GEOFENCE variable.
Fixes: #1336

Still in the process of testing this to make sure it works. I think I just noticed a problem already, will fix.
This perhaps isn't the perfect solution. But this solution unlike others I can think of avoids breaking the existing API.

As far as I can tell that test failure is unrelated to anything I did...

Tests have been successful so far. Set TESLAMATE_DEFAULT_GEOFENCE to "nowhere" and Tesla reported it was "nowhere" instead of "".

As far as I can tell that test failure is unrelated to anything I did.
LATER: I notice other PRs are failing on the same test. So probably a flaky test I think.

Yup, there are a bunch of flaky tests that really need to be fixed

Could you add a brief description of that env variable to website/docs/configuration/environment_variables.md?

Done.