<EMAIL_ADDRESS>not compatible with EXPO EAS builder

I tried to create a development build using EXPO EAS but it failed due to<EMAIL_ADDRESS>being incompatible with the Expo SDK (i have added the package to the plugins).
expo doctor output:
Running "expo doctor"

Running 10 checks on your project...

✔ Check Expo config for common issues

✔ Check package.json for common issues

✔ Check dependencies for packages that should not be installed directly

✔ Check for common project setup issues

✔ Check npm/ yarn versions

✔ Check Expo config (app.json/ app.config.js) schema

✔ Check that packages match versions required by installed Expo SDK

✔ Check for legacy global CLI installed locally

✔ Check that native modules do not use incompatible support packages

✖ Check that native modules use compatible support package versions for installed Expo SDK

Detailed check results:

[stderr]

Expected package<EMAIL_ADDRESS>
[stderr]

Found invalid:

[stderr]

<EMAIL_ADDRESS>
[stderr]

  (for more info, run: npm why @expo/config-plugins)

[stderr]

One or more checks failed, indicating possible issues with the project.

Advice: Upgrade dependencies that are using the invalid package versions.

Command "expo doctor" failed.
npx -y expo-doctor exited with non-zero code: 1

npm why @expo/config-plugins output:
<EMAIL_ADDRESS>node_modules/@expo/config-plugins
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>  node_modules/expo
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-location
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
    peer expo@"*" from<EMAIL_ADDRESS>    node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>  node_modules/@expo/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/expo
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-location
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>  node_modules/@expo/config
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/expo
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-location
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
      peer expo@"*" from<EMAIL_ADDRESS>      node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/expo-modules-autolinking
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-location
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
      peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/@expo/prebuild-config
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/@expo/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                  node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-location
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/@expo/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-location
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/@expo/metro-config
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/@expo/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-location
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/@expo/dev-server
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/@expo/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                  node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-location
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
            peer expo@"*" from<EMAIL_ADDRESS>            node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/@expo/prebuild-config
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/@expo/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/expo
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>                node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-location
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
          peer expo@"*" from<EMAIL_ADDRESS>          node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>  node_modules/@expo/prebuild-config
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/@expo/cli
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/expo
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-application
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-constants
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-dev-menu-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-menu
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-launcher
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>              node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-font
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-file-system
<EMAIL_ADDRESS>from<EMAIL_ADDRESS><EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-asset
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-keep-awake
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-location
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-secure-store
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-splash-screen
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-updates-interface
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-dev-client
<EMAIL_ADDRESS>from the root project
        peer expo@"*" from<EMAIL_ADDRESS>        node_modules/expo-task-manager
<EMAIL_ADDRESS>from the root project
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/expo-background-fetch
<EMAIL_ADDRESS>from the root project

<EMAIL_ADDRESS>node_modules/@maplibre/maplibre-react-native/node_modules/@expo/config-plugins
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>  node_modules/@maplibre/maplibre-react-native
<EMAIL_ADDRESS>from the root project

npm audit output:
xml2js  <0.5.0
Severity: moderate
xml2js is vulnerable to prototype pollution - https://github.com/advisories/GHSA-776f-qx25-q3cc
No fix available
node_modules/@maplibre/maplibre-react-native/node_modules/xml2js
  @expo/config-plugins  <=7.1.0
  Depends on vulnerable versions of xml2js
  node_modules/@maplibre/maplibre-react-native/node_modules/@expo/config-plugins
    @maplibre/maplibre-react-native  *
    Depends on vulnerable versions of @expo/config-plugins
    node_modules/@maplibre/maplibre-react-native

it looks like master has been updated, though there's been no release since the update ☹

It's now up-to-date with the current v10 pre-releases.


Taxed Award Scheme

Use this issue to discuss Taxed Award Scheme in the HMRC content style guide.

This is covered by the GOV.UK style guide at https://www.gov.uk/guidance/style-guide/a-to-z-of-gov-uk-style#c > Capitalisation > names of specific, named government schemes known to people outside government. So can probably be removed from the HMRC content style guide.

There are a number of entries for different schemes:

Accrued Income Scheme
Contracted-out Salary Related Scheme
Enterprise Investment Scheme
Non-resident Landlord Scheme
Rent-a-Room Scheme
Repayment of Teachers’ Loans scheme
Save As You Earn schemes (SAYE)

Should we remove all of them, given that this advice already exists, or retain those that have extra guidance about hyphenation, ie:

Accrued Income Scheme
Enterprise Investment Scheme

If we do this, will this decision be obvious to users, or will they be confused by not seeing individual entries for these?

If we covered all these in a single "Schemes" entry and put some context around that these have some specific rules (and that otherwise you follow the GOV.UK style) - would that help?

I will draft something. Thanks.

That is great. I would put a 'for example' at the end of the lead-in.

I considered this, but they're not, strictly speaking, "examples" (meaning: this is a small sample and there are others too). Rather, it is my understanding that these are intended as a more-or-less exhaustive list of all the schemes that are styled differently. Is that correct?

OK. Maybe...

Some HMRC schemes are styled in a specific way. These are:

I'm being a stickler cos these being examples creates ambiguity :)
I'll add "These are:"


[SR-1164] XCTestCase testRunClass should be of type XCTestRun.Type in Swift

Previous ID
SR-1164

Radar
rdar://25568830

Original Reporter
@modocache

Type
Improvement

Additional Detail from JIRA

Votes
0

Component/s
XCTest

Labels
Improvement, ClangImporter, SDKOverlay

Assignee
None

Priority
Medium

md5: 8adee259f35799e321fb96cfd32cf201

Issue Description:
See: https://github.com/apple/swift-corelibs-xctest/pull/86#discussion_r58315662
XCTest defines XCTestCase.testRunClass as an AnyClass?, and checks at runtime that this is a subclass of XCTestRun. It would be nicer if this was exported as XCTestRun.Type or XCTestRun.Type?.
Radar:

rdar://25568830

https://openradar.appspot.com/25568830

Sorry for the late reply.
This is technically correct, but it would introduce a source incompatibility with the XCTest framework that ships with Xcode, where the relevant API is implemented in Objective-C and uses Class (which is imported into Swift as AnyClass.) So if somebody implements this method in their own XCTestRun subclass, it would fail to compile with a type mismatch under one implementation or the other.


Syntax definition is confusing

COMMENT delimiter [[commentText]] delimiter [[text]] endofline
delimiter ::= [\x00-\xFF^\x08-\x0D^\x1A^\x20]
commentText ::= [\x00-\xFF]*
text ::= [\x00-\xFF^\x10]*
endofline ::= [\x10]

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

ID: a968a2ef-58ac-a2b7-daf9-2ace6630f6b6
Version Independent ID: 952845bf-711a-86cb-3a05-2512a357878d
Content: COMMENT (MASM)
Content Source: docs/assembler/masm/comment-masm.md
Product: visual-cpp
Technology: cpp-masm
GitHub Login: @corob-msft
Microsoft Alias: corob

Incorporated into Incomplete Syntax definition issue.


Code completion not working with roslyn

Hello, I would like to preface this with I am a total linux beginner, so please be patient and I'll do my best to get you all the information you ask for.
I believe I have successfully compiled the roslyn server, and after editing /autoload/OmniSharp.vim locally to echom 'server started' inside OmniSharp#StartServer(), I think the server is starting properly.  However, I cannot find it when using the 'top' command in my shell.
However, I receive no code completion, at all.  Upon hitting tab, I am greeted with
=SuperTab('n')
-- Omni completion (^O^N^P) Pattern not found

This is inside a brand new dotnet new project.
Currently running 7.4 vim-nox-py2 compiled with +python and -python3 on Ubuntu 16.04.  Below is the minimal vim config I am using in hopes of finding where my issue is.
"""VIM PLUG"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
if empty(glob('~/.vim/autoload/plug.vim'))
  silent !curl -fLo ~/.vim/autoload/plug.vim --create-dirs
        \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
  autocmd VimEnter * PlugInstall
endif

call plug#begin('~/.vim/plugged')

"Plug 'scrooloose/nerdtree'
"Plug 'vim-airline/vim-airline'
"Plug 'vim-airline/vim-airline-themes'
Plug 'scrooloose/syntastic'
"Plug 'nanotech/jellybeans.vim'
"Plug '907th/vim-auto-save'

Plug 'ctrlpvim/ctrlp.vim'
Plug 'OmniSharp/omnisharp-vim'
Plug 'tpope/vim-dispatch'
Plug 'ervandew/supertab'

call plug#end()

"""GENERAL""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
set nocompatible

"""OMNISHARP-VIM""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
" OmniSharp won't work without this setting
filetype plugin on

"This is the default value, setting it isn't actually necessary
let g:OmniSharp_host = "http://localhost:2000"

"Set the type lookup function to use the preview window instead of the status line
"let g:OmniSharp_typeLookupInPreview = 1

let g:OmniSharp_server_type = 'roslyn'

"Timeout in seconds to wait for a response from the server
let g:OmniSharp_timeout = 1

"Showmatch significantly slows down omnicomplete
"when the first match contains parentheses.
set noshowmatch

"Super tab settings - uncomment the next 4 lines
let g:SuperTabDefaultCompletionType = 'context'
let g:SuperTabContextDefaultCompletionType = "<c-x><c-o>"
let g:SuperTabDefaultCompletionTypeDiscovery = ["&omnifunc:<c-x><c-o>","&completefunc:<c-x><c-n>"]
let g:SuperTabClosePreviewOnPopupClose = 1

"don't autoselect first item in omnicomplete, show if only one item (for preview)
"remove preview if you don't want to see any documentation whatsoever.
set completeopt=longest,menuone,preview
" Fetch full documentation during omnicomplete requests.
" There is a performance penalty with this (especially on Mono)
" By default, only Type/Method signatures are fetched. Full documentation can still be fetched when
" you need it with the :OmniSharpDocumentation command.
" let g:omnicomplete_fetch_documentation=1

"Move the preview window (code documentation) to the bottom of the screen, so it doesn't move the code!
"You might also want to look at the echodoc plugin
set splitbelow

" Get Code Issues and syntax errors
" let g:syntastic_cs_checkers = ['syntax', 'semantic', 'issues']
" If you are using the omnisharp-roslyn backend, use the following
let g:syntastic_cs_checkers = ['code_checker']
augroup omnisharp_commands
  autocmd!

  "Set autocomplete function to OmniSharp (if not using YouCompleteMe completion plugin)
  autocmd FileType cs setlocal omnifunc=OmniSharp#Complete

  " Synchronous build (blocks Vim)
  "autocmd FileType cs nnoremap <F5> :wa!<cr>:OmniSharpBuild<cr>
  " Builds can also run asynchronously with vim-dispatch installed
  autocmd FileType cs nnoremap <leader>b :wa!<cr>:OmniSharpBuildAsync<cr>
  " automatic syntax check on events (TextChanged requires Vim 7.4)
  autocmd BufEnter,TextChanged,InsertLeave *.cs SyntasticCheck

  " Automatically add new cs files to the nearest project on save
  autocmd BufWritePost *.cs call OmniSharp#AddToProject()

  "show type information automatically when the cursor stops moving
  autocmd CursorHold *.cs call OmniSharp#TypeLookupWithoutDocumentation()

  "The following commands are contextual, based on the current cursor position.

  autocmd FileType cs nnoremap gd :OmniSharpGotoDefinition<cr>
  autocmd FileType cs nnoremap <leader>fi :OmniSharpFindImplementations<cr>
  autocmd FileType cs nnoremap <leader>ft :OmniSharpFindType<cr>
  autocmd FileType cs nnoremap <leader>fs :OmniSharpFindSymbol<cr>
  autocmd FileType cs nnoremap <leader>fu :OmniSharpFindUsages<cr>
  "finds members in the current buffer
  autocmd FileType cs nnoremap <leader>fm :OmniSharpFindMembers<cr>
  " cursor can be anywhere on the line containing an issue
  autocmd FileType cs nnoremap <leader>x  :OmniSharpFixIssue<cr>
  autocmd FileType cs nnoremap <leader>fx :OmniSharpFixUsings<cr>
  autocmd FileType cs nnoremap <leader>tt :OmniSharpTypeLookup<cr>
  autocmd FileType cs nnoremap <leader>dc :OmniSharpDocumentation<cr>
  "navigate up by method/property/field
  autocmd FileType cs nnoremap <C-K> :OmniSharpNavigateUp<cr>
  "navigate down by method/property/field
  autocmd FileType cs nnoremap <C-J> :OmniSharpNavigateDown<cr>

augroup END

" this setting controls how long to wait (in ms) before fetching type / symbol information.
set updatetime=500
" Remove 'Press Enter to continue' message when type information is longer than one line.
set cmdheight=2

" Contextual code actions (requires CtrlP or unite.vim)
nnoremap <leader><space> :OmniSharpGetCodeActions<cr>
" Run code actions with text selected in visual mode to extract method
vnoremap <leader><space> :call OmniSharp#GetCodeActions('visual')<cr>

" rename with dialog
nnoremap <leader>nm :OmniSharpRename<cr>
nnoremap <F2> :OmniSharpRename<cr>
" rename without dialog - with cursor on the symbol to rename... ':Rename newname'
command! -nargs=1 Rename :call OmniSharp#RenameTo("<args>")

" Force OmniSharp to reload the solution. Useful when switching branches etc.
nnoremap <leader>rl :OmniSharpReloadSolution<cr>
nnoremap <leader>cf :OmniSharpCodeFormat<cr>
" Load the current .cs file to the nearest project
nnoremap <leader>tp :OmniSharpAddToProject<cr>

" (Experimental - uses vim-dispatch or vimproc plugin) - Start the omnisharp server for the current solution
nnoremap <leader>ss :OmniSharpStartServer<cr>
nnoremap <leader>sp :OmniSharpStopServer<cr>

" Add syntax highlighting for types and interfaces
nnoremap <leader>th :OmniSharpHighlightTypes<cr>
"Don't ask to save when changing buffers (i.e. when jumping to a type definition)
set hidden

" Enable snippet completion, requires completeopt-=preview
" let g:OmniSharp_want_snippet=1

I'm having the same issue. Did you find a solution since then?

First of all try to invoke omni-completion without going through a 3rd party plugin. So, <c-x><c-o> (that is, ctrl-x, followed by ctrl-o)
If that doesn't work, try starting the server manually from the command line. It should work exactly the same if you do this, but you will see extra output in the console. There is code in omnisharp-vim to not automatically launch the server if it detects that one is already running.
Read the instructions here. You should be able to start the server with Omnisharp -s /path/to/solutionfile.sln. At least you could 18 months ago when I last tried this. Beyond that, I'm not going to be able to help, I'm afraid... I haven't used vim or omnisharp in ages!

So far I have had no luck and have not found any solution.
With everything disabled except omnisharp-vim, I still receive
Omni completion (^O^N^P) Pattern not found
when using <c-x><c-o>

I tried again a clean installation on my Windows machine, and it works properly both with omnisharp-server and with omnisharp-roslyn.
I'll try again today on Linux and investigate more.

I wonder how much of this is related to issue 276.  Although using the publish folder instead of the scripts folder appeared to fix their issue and not mine.

I can start the server manually from here .vim/bundle/omnisharp-vim/omnisharp-roslyn/artifacts/publish/OmniSharp/default/netcoreapp1.1 and it works fine, but I am unable to start it from vim. I tried to set the g:OmniSharp_server_path variable, but without any success.

I found two issues:

The OmniSharp not detects csproj projects. In the find_solution_files function of the autoload/OmniSharp.vim the code is detects sln files only. After I added the *.csproj detection is same way, the vim at least tired to start anything in the OmniSharp#StartServer function
Unfortunately, the roslyn OmniSharp server seems to stop if we pass the csproj file to it with the -s
parameter. Currently I solved the issue with commenting out this thing in the OmniSharp#StartServerSolution, but it is just a workaround.

But after this two changes and the setting of the Omnisharp_server_path in the .vimrc I at least was able to run omnisharp from vim with roslyn.


Segfaults

Haven't touched this in quite a while,
but building/running now segfaults the program. (Running on Arch Linux).
Steps to Reproduce

Run program; open an image.
Draw image.
Generate random points.
Segfaults when clicking "Compute Voronoi Diagram" or so.

Segfault happens in polypixel.cpp, findSomeColor3iv(), when accessing loadedImageData.

Was relying on OpenCV's mat to not be cleared, apparently.


fix issue where menu overlaps content.

There are more improvements that could be made, for example it'd be nice to be able to collapse the menu all together, but at least the fixes the current issue I'm having which is, if my file names are long, the menu covers up the content and I am not able to scroll so my content is completely hidden.

Could you provide please some "before and after" screenshots? so I can test it more properly.
thx

Before
You can see the menu is obstructing the page content.

After
Now the menu allows scrolling, but has max-width so it isn't overlapping the content.

There are certainly some more improvements that could be made, but I don't have much time to spend on it now, and this fixes the issue for me.

@smussell Looks good! Mind bumping that to 400px though? I think this is a good fix until we start extracting common paths from each file path.

Sure, I made the change to bump the size to 400, thanks.

thanks @smussell. please squash and we'll merge it.

@a8m @smussell Just doing some quick cross-browser tests (older IEs) and will merge if all looks good :)

go for it @danielstjules :)

Found some quirks that are def unrelated to this PR - so looks good!


SelectPanel anchors should have aria-haspopup="dialog"

Summary

Currently the anchors of SelectPanel have aria-haspopup="true" which is incorrect.
Since the value was set to aria-haspopup="true" by default in AnchoredOverlay.tsx.
To overwrite that we need to add aria-haspopup="listbox" in SelectPanel.stories.tsx renderAnchor to fix the issue.

Closes #3629
Screenshots

Before Fix
After Fix

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[ ] Changes are SSR compatible
[x] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

Thanks so much for taking the time to open this PR! Just wanted to share this as a heads up, we're sync'ing up with the accessibility team here at GitHub to double-check the intended behavior for the upstream issue. We should be meeting on Friday this week and we'll figure out next steps from there. Hope this makes sense! Let me know if you have any questions.

Hey @joshblack ,
Thank you so much for taking your time and taking a look at the PR. This gives me motivation to contribute more to primer/react. Also I have seen your comment yesterday on the issue where you mentioned there will be discussion first regarding this which also made me think Did I understand completely why aria-haspopup equal to listbox and not true? I have worked on few accessibility issues myself in the past and then I started reading about it and I learned what aria-haspopup attribute is actually used for. Thanks again for taking your time and giving me the heads up will keep on contributing to primer/react.
Thanks!

hey @joshblack ✋ ,
It's been two months since this issue was raised so wanted to check with you once with the latest update.
Is this component now a legacy component since there is SelectPanel2 and that's why we are not working on fixing the a11y issue or do you think the solution that I came up with is not the best solution for this issue?
Thanks!

Hey @electron97! So sorry about the delay, re-checking this and I think the changes look great 👍
For SelectPanel, there has been new work on the V2 version but I think this change totally makes sense as-is. Thanks so much for making this PR!


[stdlib] convert _withUnprotectedUnsafeMutablePointer() to typed throws

Part of the ongoing conversion of standard library rethrows functions, after SE-0413.
This converts the top-level, no-stack-protection function _withUnprotectedUnsafeMutablePointer().

@swift-ci please test

What sort of tests are we developing for these?

I expect the existing tests to still be valid. My previous idea for any further testing turned into tedious argument-checking tests, which were done as part of the typed throws implementation. Perhaps simply writing a use of the updated function in a typed-throw context and making sure that it compiles correctly would be testing enough?

@swift-ci please test macOS platform


How to change the text of buttons in dialog

Hi there,
I want to change the text of the buttons in the dialog but can't find an easy way to do that. Do I really need to create two ButtonFlat Objects for that or is there an easier way to achieve what I want to do?

Hi,
if you want change the text of the buttons, the dialog have getButtonAccept() and getButtonCancel(); functions that return a ButtonFloat and with this buttonfloat you can setText to set your text

Thanks. I will give it a try

This is what I get when I call the getButtonAccept() and getButtonCancel() and want to set the text with .setText()
java.lang.NullPointerException: Attempt to invoke virtual method 'void com.gc.materialdesign.views.ButtonFlat.setText(java.lang.String)' on a null object reference

I try change the text of the buttons ,but  getButtonAccept() and getButtonCancel() are null!

So two developers facing the same issue! This should issue should be opened again and most important fixed!

Thanks!

I have the same problem. Both of the getters return null.

get the return after showing it

显示了窗口再通过geter来获取button

I get the same error even if I use this code:
   ` dialog.show();
    // Access to accept button
    ButtonFlat acceptButton = dialog.getButtonAccept();
    acceptButton.setText(activity.getResources().getString(R.string.abort_dialog_ok));
    // Access to cancel button
    ButtonFlat cancelButton = dialog.getButtonCancel();
    cancelButton.setText(activity.getResources().getString(R.string.abort_dialog_cancel));`

This code return null on cancellButton:
dialog.show();
// Access to accept button
ButtonFlat acceptButton = dialog.getButtonAccept();
acceptButton.setText(activity.getResources().getString(R.string.abort_dialog_ok));
// Access to cancel button
ButtonFlat cancelButton = dialog.getButtonCancel();
cancelButton.setText(activity.getResources().getString(R.string.abort_dialog_cancel));`

I was facing the same issue.
I found that you should call Dialog.addCancelButton(String) before calling Dialog.show();
Best.

dialog.addCancelButton("cancel");


Highlight still appers different colors

Issue Type: Bug
Today I updated my VSCODE and, again, In my editor appered two highlight background color.
In the old days I had this problem before, and it was fixed changing some configs!
in /usr/share/applications/code.desktop
I had to put --disable-gpu nit the code.desktop file
Follow:
https://github.com/microsoft/vscode/issues/84690#issuecomment-554008427
In this release, I had to do again
I'd like to know the why this is happening
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:54:40.719Z)
OS version: Linux x64 4.15.0-70-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 2573)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
7.67GB (1.08GB free)

Process Argv
--no-sandbox --unity-launch

Screen Reader
no

VM
0%

Extensions (29)

Extension
Author (truncated)
Version

better-comments
aar
2.0.5

dart-code
Dar
3.6.0

flutter
Dar
3.6.0

vscode-eslint
dba
1.9.1

gitlens
eam
10.2.0

vscode-great-icons
emm
2.1.47

prettier-vscode
esb
3.11.0

mithril-emmet
Fal
0.7.3

php-debug
fel
1.13.0

php-intellisense
fel
2.3.13

php-pack
fel
1.0.2

mongo-runner
Joe
0.5.8

vscode-phpfmt
kok
1.0.30

dotenv
mik
1.0.1

vscode-elixir
mjm
1.1.0

vscode-docker
ms-
0.9.0

python
ms-
2019.11.50794

vscode-typescript-tslint-plugin
ms-
1.2.3

sqltools
mtx
0.21.3

color-highlight
nau
2.3.0

material-icon-theme
PKi
3.9.2

phpdoc-comment-vscode-plugin
rex
1.1.0

RocketseatReactJS
roc
2.2.0

RocketseatReactNative
roc
2.2.0

vscode-sql-beautify
sen
0.0.4

markdown-preview-enhanced
shd
0.5.0

vscode-counter
uct
1.3.1

vscode-icons
vsc
9.6.0

bootstrap-3-snippets
wcw
0.1.0

(1 theme extensions excluded)

The HW accelerated rendering support comes from chromium, and especially on certain linux distributions it doesn't work well often, might be due to graphic cards etc,
Please don't edit the .desktop file, it will be updated and your changes will be lost. Also vscode will never disable HW acceleration support by default.
However, you can do this in a less harmful way on your end by
If that helps, you can permanently configure this option via:
* Command Palette search for "Configure Runtime Arguments"
* Set `disable-hardware-acceleration: true`
* Restart


adding reminders model and tests.

Creating remainders application
creating Remainder model and validation
Creating remainders tests
Created costume test migration

fix #30

@kobihk @brochwerger @nemerna
Please Pay Attention to the comment in the tests.py file.
As a result of trying to minimize duplicate code, we imported fixtures and other methods that can help in the tests.
Because Flase8 doesn't "understand" that fixtures are a function that can be added to a function as part of her arguments,
it gives a warning like F401 that says the imported function is not used.
So we found a way to ignore the Flake8 wrong warning by inserting the comment "# noqa: ",
if we remove those comments our code will run and pass the tests but will not pass Flake8 tests.

@danninon please update the line in PR description
creating Remainder model and validation
to
Creating Remainder model and validation

@danninon please update the line in PR description creating Remainder model and validation to Creating Remainder model and validation

@kobihk done!

@danninon please ask for CR from your team members


BF: Fix sample aggregation

This began as work to add stat, which as a dumb initial implementation was just a list of all the values we get. (to be replaced by a counter). However, the sample aggregation returned strange results-- the averages reported the correct number of samples, but stat was only showing a list of length 1.
So this PR refactors the complexity of sample aggregation be abstracted by a Report function update_from_sample. This will be much more testable.
DONE test update_from_sample~
DONE: since aggregate (was max) is now updating the averages, we can drop Report.averages, since that information is duplicated by report.max_values.averages, which should be renamed to report.full_execution_stats (I don't like that name) or similar.
At the end of the run:
ipdb> report.averages
Averages(rss=1802240.0, vsz=226902016.0, pmem=0.0, pcpu=0.0, num_samples=18)
ipdb> report.max_values.averages
Averages(rss=1802240.0, vsz=226902016.0, pmem=0.0, pcpu=0.0, num_samples=18)
ipdb>

I've removed the stat update, to add separately in another PR

Sanity Check
On typhon with singularity (with and without containers run), prior to this PR we got divergent results that clearly showed that duct sample aggregation was not working as expected.
I've rerun those experiments, and now the 2 ways of using singularity with duct are returning very similar outputs.
Singularity run direct
 "execution_summary": {
   "exit_code": 0,
   "command": "singularity run --contain --bind /home/asmacdo/devel/sandbox/mriqc-sanity/sourcedata:/data:ro --bind /home/asmacdo/devel/sandbox/mriqc-sanity/dfix-sr-1:/out --bind /home/asmacdo/devel/sandbox/mriqc-sanity/dfix-sr-1/workdir:/workdir code/containers/images/bids/bids-mriqc--0.16.0.sing /data /out participant --participant-label 02 -w /workdir --no-sub",
   "logs_prefix": "dfix-sr-1/duct_",
   "wall_clock_time":<PHONE_NUMBER>6381226,
   "peak_rss":<PHONE_NUMBER>,
   "average_rss":<PHONE_NUMBER>.13043,
   "peak_vsz":<PHONE_NUMBER>0,
   "average_vsz":<PHONE_NUMBER>5.826088,
   "peak_pmem": 0,
   "average_pmem": 0,
   "peak_pcpu": 3438.4,
   "average_pcpu":<PHONE_NUMBER>3478267,
   "num_samples": 368,
   "num_reports": 8
 },

Containers Run
  "execution_summary": {
    "exit_code": 0,
    "command": "./code/containers/scripts/singularity_cmd run code/containers/images/bids/bids-mriqc--0.16.0.sing sourcedata dfix-cr-1 participant --participant-label 02 -w dfix-cr-1/workdir --no-sub",
    "logs_prefix": "dfix-cr-1/duct_",
    "wall_clock_time":<PHONE_NUMBER>163208,
    "peak_rss":<PHONE_NUMBER>,
    "average_rss":<PHONE_NUMBER>.772606,
    "peak_vsz":<PHONE_NUMBER>6,
    "average_vsz":<PHONE_NUMBER>2.120544,
    "peak_pmem": 0,
    "average_pmem": 0,
    "peak_pcpu": 3035.2,
    "average_pcpu":<PHONE_NUMBER>972601,
    "num_samples": 365,
    "num_reports": 8
  },

somewhat unrelated I guess: "peak_pcpu": 3438.4, looks odd, even for typhon with 32 cores. Having a plot would have been useful to grasp situation on that

Singularity Direct

Containers Run

While running top, I'm not

The case I can think of that could artificially inflate the peak would be if the processes were trading resources back and forth, but the aggregation was totaling the peaks of both. So I added a test for that case, which passes.
IIUC (still could be wrong) this means that the 3438% spike was actually recorded by a single call to ps and the individual processes actually somehow added up to more than numcores*100.
FWIW the record of the spike:
{
  "timestamp": "2024-09-19T14:24:03.175972-04:00",
  "num_samples": 58,
  "processes": {
    "4159232": {
      "pcpu": 100.0,
      "pmem": 0.0,
      "rss": 218427392,
      "vsz": 705040384,
      "timestamp": "2024-09-19T14:24:03.175328-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159233": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 119971840,
      "vsz": 365043712,
      "timestamp": "2024-09-19T14:24:03.175350-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159234": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 119971840,
      "vsz": 365051904,
      "timestamp": "2024-09-19T14:24:03.175372-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159235": {
      "pcpu": 109.0,
      "pmem": 0.0,
      "rss": 119734272,
      "vsz": 365043712,
      "timestamp": "2024-09-19T14:24:03.175394-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159236": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 260890624,
      "vsz": 745840640,
      "timestamp": "2024-09-19T14:24:03.175414-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159237": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 119451648,
      "vsz": 365043712,
      "timestamp": "2024-09-19T14:24:03.175436-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159238": {
      "pcpu": 109.0,
      "pmem": 0.0,
      "rss": 119971840,
      "vsz": 365043712,
      "timestamp": "2024-09-19T14:24:03.175459-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159239": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 119767040,
      "vsz": 365043712,
      "timestamp": "2024-09-19T14:24:03.175481-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159240": {
      "pcpu": 115.0,
      "pmem": 0.0,
      "rss": 119902208,
      "vsz": 365035520,
      "timestamp": "2024-09-19T14:24:03.175502-04:00",
      "etime": "00:49",
      "cmd": "S    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159241": {
      "pcpu": 105.0,
      "pmem": 0.0,
      "rss": 305442816,
      "vsz": 791502848,
      "timestamp": "2024-09-19T14:24:03.175525-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159242": {
      "pcpu": 110.0,
      "pmem": 0.0,
      "rss": 119947264,
      "vsz": 365031424,
      "timestamp": "2024-09-19T14:24:03.175549-04:00",
      "etime": "00:49",
      "cmd": "S    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159243": {
      "pcpu": 110.0,
      "pmem": 0.0,
      "rss": 217567232,
      "vsz": 702205952,
      "timestamp": "2024-09-19T14:24:03.175571-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159244": {
      "pcpu": 110.0,
      "pmem": 0.0,
      "rss": 119894016,
      "vsz": 365031424,
      "timestamp": "2024-09-19T14:24:03.175592-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159245": {
      "pcpu": 105.0,
      "pmem": 0.0,
      "rss": 119902208,
      "vsz": 365035520,
      "timestamp": "2024-09-19T14:24:03.175613-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159246": {
      "pcpu": 115.0,
      "pmem": 0.0,
      "rss": 119853056,
      "vsz": 365035520,
      "timestamp": "2024-09-19T14:24:03.175634-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159247": {
      "pcpu": 110.0,
      "pmem": 0.0,
      "rss": 119955456,
      "vsz": 365031424,
      "timestamp": "2024-09-19T14:24:03.175655-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159248": {
      "pcpu": 115.0,
      "pmem": 0.0,
      "rss": 119803904,
      "vsz": 365031424,
      "timestamp": "2024-09-19T14:24:03.175675-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159249": {
      "pcpu": 110.0,
      "pmem": 0.0,
      "rss": 119943168,
      "vsz": 365031424,
      "timestamp": "2024-09-19T14:24:03.175696-04:00",
      "etime": "00:49",
      "cmd": "S    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159250": {
      "pcpu": 110.0,
      "pmem": 0.0,
      "rss": 119955456,
      "vsz": 365035520,
      "timestamp": "2024-09-19T14:24:03.175717-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159251": {
      "pcpu": 105.0,
      "pmem": 0.0,
      "rss": 119787520,
      "vsz": 365031424,
      "timestamp": "2024-09-19T14:24:03.175737-04:00",
      "etime": "00:49",
      "cmd": "S    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159757": {
      "pcpu": 2.3,
      "pmem": 0.0,
      "rss": 10940416,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175886-04:00",
      "etime": "00:41",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(8)"
    },
    "4159756": {
      "pcpu": 3.5,
      "pmem": 0.0,
      "rss": 10854400,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175865-04:00",
      "etime": "00:41",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(8)"
    },
    "4158843": {
      "pcpu": 4.2,
      "pmem": 0.0,
      "rss": 14962688,
      "vsz": 31133696,
      "timestamp": "2024-09-19T14:24:03.175047-04:00",
      "etime": "00:57",
      "cmd": "S    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159768": {
      "pcpu": 0.0,
      "pmem": 0.0,
      "rss": 716800,
      "vsz": 4620288,
      "timestamp": "2024-09-19T14:23:33.076612-04:00",
      "etime": "00:10",
      "cmd": "S    /bin/sh -c 3dvolreg -Fourier -twopass -1Dfile slice.1D -1Dmatrix_save slice.aff12.1D -prefix slice_volreg.nii.gz -zpad 4 -maxdisp1D slice_md.1D /workdir/mriqc_wf/funcMRIQC/fMRI_HMC/_in_file_..data..sub-02..func..sub-02_task-rhymejudgment_bold.nii.gz/gen_ref/slice.nii.gz"
    },
    "4159769": {
      "pcpu": 103.0,
      "pmem": 0.0,
      "rss": 18223104,
      "vsz": 59785216,
      "timestamp": "2024-09-19T14:23:33.076633-04:00",
      "etime": "00:10",
      "cmd": "R    3dvolreg -Fourier -twopass -1Dfile slice.1D -1Dmatrix_save slice.aff12.1D -prefix slice_volreg.nii.gz -zpad 4 -maxdisp1D slice_md.1D /workdir/mriqc_wf/funcMRIQC/fMRI_HMC/_in_file_..data..sub-02..func..sub-02_task-rhymejudgment_bold.nii.gz/gen_ref/slice.nii.gz"
    },
    "4159642": {
      "pcpu": 5.7,
      "pmem": 0.0,
      "rss": 11001856,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175780-04:00",
      "etime": "00:45",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(8)"
    },
    "4159771": {
      "pcpu": 4.4,
      "pmem": 0.0,
      "rss": 10956800,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175909-04:00",
      "etime": "00:39",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(8)"
    },
    "4159226": {
      "pcpu": 109.0,
      "pmem": 0.0,
      "rss": 119955456,
      "vsz": 365039616,
      "timestamp": "2024-09-19T14:24:03.175198-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159228": {
      "pcpu": 100.0,
      "pmem": 0.0,
      "rss": 282193920,
      "vsz": 703242240,
      "timestamp": "2024-09-19T14:24:03.175242-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159610": {
      "pcpu": 2.6,
      "pmem": 0.0,
      "rss": 11001856,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175758-04:00",
      "etime": "00:45",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(8)"
    },
    "4159738": {
      "pcpu": 3.8,
      "pmem": 0.0,
      "rss": 11001856,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175801-04:00",
      "etime": "00:43",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(8)"
    },
    "4159230": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 228229120,
      "vsz": 712790016,
      "timestamp": "2024-09-19T14:24:03.175286-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159932": {
      "pcpu": 6.2,
      "pmem": 0.0,
      "rss": 10895360,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175929-04:00",
      "etime": "00:27",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(8)"
    },
    "4159934": {
      "pcpu": 0.0,
      "pmem": 0.0,
      "rss": 761856,
      "vsz": 4620288,
      "timestamp": "2024-09-19T14:24:03.175950-04:00",
      "etime": "00:26",
      "cmd": "S    /bin/sh -c 3dvolreg -Fourier -twopass -1Dfile sub-02_task-rhymejudgment_bold_valid.1D -1Dmatrix_save sub-02_task-rhymejudgment_bold_valid.aff12.1D -prefix sub-02_task-rhymejudgment_bold_valid_volreg.nii.gz -base /workdir/mriqc_wf/funcMRIQC/fMRI_HMC/_in_file_..data..sub-02..func..sub-02_task-rhymejudgment_bold.nii.gz/gen_ref/ref_bold.nii.gz -zpad 4 -maxdisp1D sub-02_task-rhymejudgment_bold_valid_md.1D /workdir/mriqc_wf/funcMRIQC/fMRI_HMC/_in_file_..data..sub-02..func..sub-02_task-rhymejudgment_bold.nii.gz/motion_correct/sub-02_task-rhymejudgment_bold_valid.nii.gz"
    },
    "4159935": {
      "pcpu": 101.0,
      "pmem": 0.0,
      "rss": 56315904,
      "vsz": 97992704,
      "timestamp": "2024-09-19T14:24:03.175972-04:00",
      "etime": "00:26",
      "cmd": "R    3dvolreg -Fourier -twopass -1Dfile sub-02_task-rhymejudgment_bold_valid.1D -1Dmatrix_save sub-02_task-rhymejudgment_bold_valid.aff12.1D -prefix sub-02_task-rhymejudgment_bold_valid_volreg.nii.gz -base /workdir/mriqc_wf/funcMRIQC/fMRI_HMC/_in_file_..data..sub-02..func..sub-02_task-rhymejudgment_bold.nii.gz/gen_ref/ref_bold.nii.gz -zpad 4 -maxdisp1D sub-02_task-rhymejudgment_bold_valid_md.1D /workdir/mriqc_wf/funcMRIQC/fMRI_HMC/_in_file_..data..sub-02..func..sub-02_task-rhymejudgment_bold.nii.gz/motion_correct/sub-02_task-rhymejudgment_bold_valid.nii.gz"
    },
    "4159754": {
      "pcpu": 102.0,
      "pmem": 0.0,
      "rss": 76070912,
      "vsz": 95371264,
      "timestamp": "2024-09-19T14:24:03.175844-04:00",
      "etime": "00:42",
      "cmd": "R    N4BiasFieldCorrection -d 3 --input-image /workdir/mriqc_wf/anatMRIQC/_in_file_..data..sub-02..anat..sub-02_T1w.nii.gz/conform/sub-02_T1w_conformed.nii.gz --output [ sub-02_T1w_conformed_corrected.nii.gz, sub-02_T1w_conformed_bias.nii.gz ] -r"
    },
    "4158281": {
      "pcpu": 2.8,
      "pmem": 0.0,
      "rss": 19939328,
      "vsz":<PHONE_NUMBER>,
      "timestamp": "2024-09-19T14:24:03.174912-04:00",
      "etime": "01:00",
      "cmd": "Ssl  Singularity runtime parent"
    },
    "4158932": {
      "pcpu": 83.7,
      "pmem": 0.0,
      "rss": 227446784,
      "vsz": 788496384,
      "timestamp": "2024-09-19T14:23:12.163871-04:00",
      "etime": "00:05",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4158306": {
      "pcpu": 87.7,
      "pmem": 0.0,
      "rss": 230993920,
      "vsz": 865636352,
      "timestamp": "2024-09-19T14:24:03.174991-04:00",
      "etime": "01:00",
      "cmd": "R    /usr/local/miniconda/bin/python /usr/local/miniconda/bin/mriqc /data /out participant --participant-label 02 -w /workdir --no-sub"
    },
    "4159074": {
      "pcpu": 10.7,
      "pmem": 0.0,
      "rss": 11018240,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:23:12.163878-04:00",
      "etime": "00:02",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(9)"
    },
    "4159084": {
      "pcpu": 4.9,
      "pmem": 0.0,
      "rss": 10915840,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:23:13.197145-04:00",
      "etime": "00:01",
      "cmd": "S    /usr/local/miniconda/bin/python -s -Wignore -c from multiprocessing.semaphore_tracker import main;main(11)"
    },
    "4159220": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 119717888,
      "vsz": 365023232,
      "timestamp": "2024-09-19T14:24:03.175070-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159221": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 216580096,
      "vsz": 628342784,
      "timestamp": "2024-09-19T14:24:03.175091-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159222": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 119906304,
      "vsz": 365027328,
      "timestamp": "2024-09-19T14:24:03.175114-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159223": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 213327872,
      "vsz": 622346240,
      "timestamp": "2024-09-19T14:24:03.175134-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159224": {
      "pcpu": 109.0,
      "pmem": 0.0,
      "rss": 119795712,
      "vsz": 364994560,
      "timestamp": "2024-09-19T14:24:03.175155-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159225": {
      "pcpu": 100.0,
      "pmem": 0.0,
      "rss": 119623680,
      "vsz": 365035520,
      "timestamp": "2024-09-19T14:24:03.175175-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4158842": {
      "pcpu": 4.2,
      "pmem": 0.0,
      "rss": 10948608,
      "vsz": 26898432,
      "timestamp": "2024-09-19T14:24:03.175023-04:00",
      "etime": "00:57",
      "cmd": "S    /usr/local/miniconda/bin/python -s -c from multiprocessing.semaphore_tracker import main;main(7)"
    },
    "4159227": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 229507072,
      "vsz": 720797696,
      "timestamp": "2024-09-19T14:24:03.175221-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4158844": {
      "pcpu": 63.6,
      "pmem": 0.0,
      "rss": 232763392,
      "vsz": 912482304,
      "timestamp": "2024-09-19T14:23:13.197122-04:00",
      "etime": "00:07",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159229": {
      "pcpu": 104.0,
      "pmem": 0.0,
      "rss": 119898112,
      "vsz": 365031424,
      "timestamp": "2024-09-19T14:24:03.175264-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    },
    "4159753": {
      "pcpu": 0.0,
      "pmem": 0.0,
      "rss": 774144,
      "vsz": 4620288,
      "timestamp": "2024-09-19T14:24:03.175823-04:00",
      "etime": "00:42",
      "cmd": "S    /bin/sh -c N4BiasFieldCorrection -d 3 --input-image /workdir/mriqc_wf/anatMRIQC/_in_file_..data..sub-02..anat..sub-02_T1w.nii.gz/conform/sub-02_T1w_conformed.nii.gz --output [ sub-02_T1w_conformed_corrected.nii.gz, sub-02_T1w_conformed_bias.nii.gz ] -r"
    },
    "4159231": {
      "pcpu": 100.0,
      "pmem": 0.0,
      "rss": 306819072,
      "vsz": 797450240,
      "timestamp": "2024-09-19T14:24:03.175307-04:00",
      "etime": "00:49",
      "cmd": "R    /usr/local/miniconda/bin/python -s -c from multiprocessing.forkserver import main; main(7, 9, ['__main__'], **{'sys_path': ['/usr/local/miniconda/bin', '/usr/local/miniconda/lib/python37.zip', '/usr/local/miniconda/lib/python3.7', '/usr/local/miniconda/lib/python3.7/lib-dynload', '/usr/local/miniconda/lib/python3.7/site-packages']})"
    }
  },
  "totals": {
    "pmem": 0.0,
    "pcpu": 3438.4,
    "rss":<PHONE_NUMBER>,
    "vsz":<PHONE_NUMBER>6
  },
  "averages": {
    "rss":<PHONE_NUMBER>.448277,
    "vsz":<PHONE_NUMBER>9.51724,
    "pmem": 0.0,
    "pcpu":<PHONE_NUMBER>482758,
    "num_samples": 58
  }
}

and indeed, if I go through and add the peaks of each pid as listed above, we get an even higher number

In [25]: for pid, stats in data['processes'].items():
    ...:     for k, v in stats.items():
    ...:         if k == 'pcpu':
    ...:             tot += v
    ...:

In [26]:

In [26]: tot
Out[26]: 4000.2999999999993

Please wrap long dumps into <details> next time. So was that on Typhon? If so, let's consider ok and proceed

Yes on typhon


Black & White ("Greyscale") NTSC games on a PAL console

Hi friends, thanks all for your great work!
I'm using neutrino via xebplus-neutrino-loader-plugin and stream games from my windows PC.
This all works great (and very fast), but when I launch NTSC games on my PAL console, they are black and white only. When I launch the same games via OPL / smb, I can see colors normally.
Difficult to judge for me of this is a neutrino issue or not.
Do you happen to have any guidance on how I might be able to resolve this? :)

So for those who are coming after me, my fix was super easy: "YFix NTSC to PAL patcher" for my NTSC iso. No I can play happily on my PAL PS2 via XEB / Neutrino / UDPBD. 🙂

I need a little more clarification. My current assumptions:

You are using a PAL ps2, with PAL TV
You used a composite cable (not RGB or component)
On OPL you enabled GSM and changed the CRTC output from NTSC to PAL

Are these correct?

Hi @rickgaiser and thanks. Yes, all three are correct! :) I'm picking up an RGB cable today, so hopefully that will be an even better solution then patching the iso. Either way, thanks a lot for your hard work on these awesome tools! :)

Just wanted to report back here again that switching to an RGB cable did indeed also fix my issue with (non-patched) NTSC games. :)


KAFKA-17205: Allow topic config validation in controller level in KRaft mode

Allow topic config validation in controller level in KRaft mode by passing existing configuration for validation. Adding tests.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@kamalcph @clolov @satishd  , call for review. Thanks.

Test failures appear to be unrelated!


Add command to stop the bot

Please add !shutdown command, so maybe if the owner has many outdated listings, cannot update them and isnt home to turn off the bot

or when u dont have time to update all the listings

so u will shut it down if u not home thru command and than do it at home

Thank you for making an issue! I'll add this in a few minutes 😄

Clicked the wrong button

lol i tried to add it for like 2 hrs lol gotta learn

It is literally one function that needs to be called, I'll finish what I am working on and add it 😃

I know but im learning node.js by seeing other projects and copying it and experimenting with it lol

Added with version 1.10.9


Error when using ./bin/place-order

~/mango/mango-explorer/bin# ./place-order --market SOL/USDC --quantity 0.01 --price 90.00 --side BUY --order-type LIMIT --account-address 2WkWHY1u7LyXuYZSjA2SEqNiZDyhr8VMrNQ8rfVtBxfk
2022-01-29 03:31:43 ⓘ SpotMarketOp Placing SOL/USDC order « Order BUY for 0.01000000 at 90.00000000 [ID: 0 / 0] LIMIT».
Traceback (most recent call last):
  File "/root/mango/mango-explorer/bin/./place-order", line 41, in <module>
    placed = market_operations.place_order(order)
  File "/root/mango/mango-explorer/mango/spotmarketoperations.py", line 177, in place_order
    place: CombinableInstructions = self.market_instruction_builder.build_place_order_instructions(
  File "/root/mango/mango-explorer/mango/spotmarketoperations.py", line 89, in build_place_order_instructions
    return build_spot_place_order_instructions(self.context, self.wallet, self.group, self.account,
  File "/root/mango/mango-explorer/mango/instructions.py", line 664, in build_spot_place_order_instructions
    open_orders_address = create_open_orders.signers[0].public_key
IndexError: list index out of range

It appears that the array of signers is empty.

Apologies. I've fixed this in commit 5a36608b3de5a34e72223d0b61dbb936d380a743 and it'll be packaged in the next release.
The cause of this was a move to using PDAs for spot openorders - I updated the code everywhere but I missed this one spot. Sorry.

Thanks, looks like it's fixed in 3.3.3


ci: Check if RBAC rules are in sync

Signed-off-by: Krzesimir Nowak<EMAIL_ADDRESS>Fixes #250.

The failure will go away when #317 is merged.

Updated and rebased on top of current master, so the test should pass now.


character wont load

Describe your bug here.
i insert the sprite shet and xml, i go in the character editor, do the offsets and when i try using it it crashes the game, and then the character wont load
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
nope

do you set the png and xml file in mods\images\characters


Work with latest pr-bumper

This project uses semver, please check the scope of this pr:

[x] #none# - documentation fixes and/or test additions
[ ] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

:+1:


New version: LibDLF v0.2.0

Registering package: LibDLF
Repository: https://github.com/emsig/libdlf
Created by: @github-actions[bot]
Version: v0.2.0
Commit: 7cd5eb817234e7bdca5bf86f935878c82c1b3dbf
Reviewed by: @github-actions[bot]
Reference: https://github.com/emsig/libdlf/commit/7cd5eb817234e7bdca5bf86f935878c82c1b3dbf#commitcomment-55366622

We've switched our (unusually organized) package so that it now deploys the julia package to branch package-julia.

@kerrykey is it ok to jump from v0.0.12 to v0.2.0 (so missing the entire 0.1.x series)?  We can manually merge this, but we want to double check this was done on purpose (most of the time it isn't, that's why we don't automerge)

@giordano yeah, this is all good for jumping to v0.2.0. We didn't register the earlier versions since they were mostly testing releases while we sorted out how to get the GHA's working to correctly deploy to python and Julia packages.

And thanks for checking!


more eclusions due to collections.abc moves

jenkins run the full tests please

:grey_exclamation: Build Aborted

There is a new build on-going so the previous on-going builds have been aborted.

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: Pull request #1078 opened

Reason: Aborted from #2

Start Time: 2021-03-23T09:43:35.047+0000

Duration: 15 min 4 sec

Commit: 9f93e53fc368b3cb2b176c717a181a40e90c6db5

Test stats :test_tube:

Test
Results

Failed
0

Passed
9580

Skipped
7208

Total
16788

Trends :test_tube:

Steps errors
Expand to view the steps failures

Show only the first 10 steps failures

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-elasticsearch-2

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-gevent-newest

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-mysql_connector-newest

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-pymysql-newest

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-mysqlclient-newest

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-graphene-2

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-httpx-newest

Restore files previously stashed

Took 0 min 0 sec . View more details on here
Description: coverage-pypy-3-httplib2-newest

Archive the artifacts

Took 0 min 0 sec . View more details on here
Description: [2021-03-23T09:58:35.822Z] Archiving artifacts
Python-pypy-3-flask-0.12 tests failed : org.jenkinsc

Error signal

Took 0 min 0 sec . View more details on here
Description: Python-pypy-3-flask-0.12 tests failed : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException

Log output
Expand to view the last 100 lines of log output

[2021-03-23T09:57:55.724Z] ERROR: No such saved stash ‘coverage-pypy-3-celery-3-django-2.0’
[2021-03-23T09:57:56.422Z] ERROR: No such saved stash ‘coverage-pypy-3-pymongo-newest’
[2021-03-23T09:57:57.116Z] ERROR: No such saved stash ‘coverage-pypy-3-elasticsearch-2’
[2021-03-23T09:57:57.801Z] ERROR: No such saved stash ‘coverage-pypy-3-gevent-newest’
[2021-03-23T09:57:57.947Z] ERROR: No such saved stash ‘coverage-pypy-3-mysql_connector-newest’
[2021-03-23T09:57:58.088Z] ERROR: No such saved stash ‘coverage-pypy-3-pymysql-newest’
[2021-03-23T09:57:58.231Z] ERROR: No such saved stash ‘coverage-pypy-3-mysqlclient-newest’
[2021-03-23T09:57:58.510Z] ERROR: No such saved stash ‘coverage-pypy-3-graphene-2’
[2021-03-23T09:57:58.655Z] ERROR: No such saved stash ‘coverage-pypy-3-httpx-newest’
[2021-03-23T09:57:58.800Z] ERROR: No such saved stash ‘coverage-pypy-3-httplib2-newest’
[2021-03-23T09:58:00.102Z] + python3 -m coverage combine
[2021-03-23T09:58:32.235Z] + python3 -m coverage xml
[2021-03-23T09:58:34.824Z] [Cobertura] Skipping Cobertura coverage report as build was not SUCCESS or better ...
[2021-03-23T09:58:34.824Z]
[2021-03-23T09:58:35.259Z] + curl -sLO https://code.jquery.com/jquery-3.3.1.slim.min.js
[2021-03-23T09:58:35.569Z] + curl -sLO<EMAIL_ADDRESS>[2021-03-23T09:58:35.822Z] Archiving artifacts
[2021-03-23T09:58:36.007Z] Stage "Building packages" skipped due to earlier failure(s)
[2021-03-23T09:58:36.116Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2021-03-23T09:58:36.220Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2021-03-23T09:58:36.457Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2021-03-23T09:58:36.507Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2021-03-23T09:58:36.619Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2021-03-23T09:58:36.733Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2021-03-23T09:58:37.449Z] Running on Jenkins in /var/lib/jenkins/workspace/hon_apm-agent-python-mbp_PR-1078
[2021-03-23T09:58:37.755Z] [INFO] getVaultSecret: Getting secrets
[2021-03-23T09:58:37.951Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2021-03-23T09:58:38.963Z] + chmod 755 generate-build-data.sh
[2021-03-23T09:58:38.964Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-1078/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-1078/runs/1 ABORTED 903638
[2021-03-23T09:58:39.514Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-1078/runs/1/steps/?limit=10000 -o steps-info.json
[2021-03-23T09:58:42.743Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-1078/runs/1/tests/?status=FAILED -o tests-errors.json