text:
Coinbase Pay does not compile, missing babel loader

I'm trying to integrate with the coinbase pay sdk. I've created a button using their examples, however when trying to build I'm getting an issue Internal to their SDK
When trying to build my code I get an error internal to the `@coinbase/cbpay-js sdk
./node_modules/@coinbase/cbpay-js/dist/index.mjs 135:34
Module parse failed: Unexpected token (135:34)
File was processed with these loaders:
 * ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
 var isMobileSdkTarget = /* @__PURE__ */__name(win => {
   try {
>     return win.ReactNativeWebView?.postMessage !== void 0;
   } catch {
     return false;

This is my package.json:
{
  "name": "React App",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "@arkane-network/web3-arkane-provider": "^0.23.0",
    "@ethersproject/experimental": "^5.4.0",
    "@gelatonetwork/limit-orders-react": "^2.4.0",
    "@gnosis.pm/safe-apps-sdk": "^4.0.0",
    "@reduxjs/toolkit": "^1.3.5",
    "@transak/transak-sdk": "^1.0.28",
    "@types/jest": "^25.2.1",
    "@types/lodash.flatmap": "^4.5.6",
    "@types/multicodec": "^1.0.0",
    "@types/node": "^13.13.5",
    "@types/qs": "^6.9.2",
    "@types/react": "^17.0.0",
    "@types/react-dom": "^17.0.0",
    "@types/react-redux": "^7.1.8",
    "@types/react-router-dom": "^5.1.8",
    "@types/react-slick": "^0.23.7",
    "@types/react-virtualized-auto-sizer": "^1.0.1",
    "@types/react-window": "^1.8.5",
    "@types/styled-components": "^5.1.15",
    "@types/testing-library__cypress": "^5.0.5",
    "@typescript-eslint/eslint-plugin": "^5.3.1",
    "@typescript-eslint/parser": "^5.3.1",
    "@uniswap/governance": "^1.0.2",
    "@uniswap/liquidity-staker": "^1.0.2",
    "@uniswap/merkle-distributor": "1.0.1",
    "@uniswap/sdk": "npm:quickswap-sdk@3.0.8",
    "@uniswap/token-lists": "npm:quickswap-token-lists@1.0.1",
    "@uniswap/v2-core": "1.0.0",
    "@uniswap/v2-periphery": "^1.1.0-beta.0",
    "@web3-react/core": "6.0.9",
    "@web3-react/injected-connector": "6.0.7",
    "@web3-react/ledger-connector": "6.1.9",
    "@web3-react/portis-connector": "6.0.9",
    "@web3-react/walletconnect-connector": "6.2.4",
    "@web3-react/walletlink-connector": "6.2.3",
    "ajv": "^6.12.3",
    "apollo-cache-inmemory": "^1.6.6",
    "apollo-client": "^2.6.10",
    "apollo-link-http": "^1.5.17",
    "cids": "^1.1.9",
    "copy-to-clipboard": "^3.2.0",
    "cypress": "^7.7.0",
    "eslint": "^7.11.0",
    "eslint-config-prettier": "^6.11.0",
    "eslint-plugin-prettier": "^3.1.3",
    "eslint-plugin-react": "^7.19.0",
    "eslint-plugin-react-hooks": "^4.0.0",
    "ethers": "^5.0.7",
    "fortmatic": "^2.2.1",
    "graphql": "^15.5.1",
    "graphql-tag": "^2.12.5",
    "hamburger-react": "^2.4.1",
    "i18next": "^20.4.0",
    "i18next-browser-languagedetector": "^6.1.2",
    "ipfs-deploy": "^11.1.0",
    "lodash.flatmap": "^4.5.0",
    "multicodec": "^3.0.1",
    "multihashes": "^3.0.1",
    "polished": "^3.3.2",
    "prettier": "^1.17.0",
    "qs": "^6.9.4",
    "react": "^17.0.2",
    "react-app-rewired": "^2.1.8",
    "react-device-detect": "^1.6.2",
    "react-dom": "^17.0.2",
    "react-feather": "^2.0.8",
    "react-i18next": "^11.11.4",
    "react-redux": "^7.2.4",
    "react-router-dom": "^5.2.0",
    "react-scripts": "4.0.3",
    "react-virtualized-auto-sizer": "^1.0.6",
    "react-window": "^1.8.6",
    "redux-localstorage-simple": "^2.4.1",
    "serve": "^11.3.2",
    "source-map-explorer": "^2.5.2",
    "start-server-and-test": "^1.11.0",
    "typescript": "^4.1.2",
    "web3": "^1.7.0"
  },
  "resolutions": {
    "yargs-parser": "^13.1.2",
    "underscore": "^1.12.1",
    "lodash": "^4.17.21",
    "trim-newlines": "^3.0.1",
    "nth-check": "^2.0.1",
    "node-fetch": "^2.6.7",
    "follow-redirects": "^1.14.8",
    "axios": "^0.21.2",
    "immer": "^9.0.6",
    "ansi-html": "^0.0.8",
    "node-forge": "^1.3.0",
    "glob-parent": "^5.1.2",
    "browserslist": "^4.16.5",
    "ajv": "^6.12.3",
    "async": "^3.2.2",
    "ejs": "^3.1.7",
    "cross-fetch": "^3.1.5",
    "eventsource": "^2.0.2",
    "protobufjs": "^6.11.3",
    "shell-quote": "^1.7.3",
    "terser": "^4.8.1",
    "got": "^11.8.5",
    "jpeg-js": "^0.4.4"
  },
  "scripts": {
    "analyze": "source-map-explorer 'build/static/js/*.js'",
    "start": "react-app-rewired start",
    "build": "CI=false react-app-rewired --max_old_space_size=4096 build",
    "test": "react-app-rewired test --env=jsdom",
    "format": "prettier --write \"**/*.{ts,js,tsx,json,md}\"",
    "eject": "react-scripts eject",
    "integration-test": "start-server-and-test 'serve build -l 3000' http://localhost:3000 'cypress run'",
    "ipfs-deploy": "ipfs-deploy build"
  },
  "eslintConfig": {
    "extends": "react-app",
    "ignorePatterns": [
      "node_modules"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "license": "GPL-3.0-or-later",
  "dependencies": {
    "@coinbase/cbpay-js": "^1.6.0",
    "@material-ui/core": "^4.12.3",
    "@material-ui/icons": "^4.11.2",
    "@material-ui/lab": "^4.0.0-alpha.60",
    "apexcharts": "3.32.1",
    "i18next-http-backend": "^1.4.1",
    "market-sdk": "^2.2.0",
    "react-apexcharts": "1.3.9",
    "react-cool-inview": "^2.0.8",
    "react-ga": "^3.3.0",
    "react-query": "^3.34.19",
    "react-reflex": "^4.0.6",
    "react-slick": "^0.28.1",
    "react-virtuoso": "^2.8.4",
    "sass": "^1.51.0",
    "slick-carousel": "^1.8.1",
    "styled-components": "^5.3.3"
  }
}

config-overrides.js
module.exports = {
  // The function to use to create a webpack dev server configuration when running the development
  // server with 'npm run start' or 'yarn start'.
  // Example: set the dev server to use a specific certificate in https.
  devServer: function(configFunction) {
    // Return the replacement function for create-react-app to use to generate the Webpack
    // Development Server config. "configFunction" is the function that would normally have
    // been used to generate the Webpack Development server config - you can use it to create
    // a starting configuration to then modify instead of having to create a config from scratch.
    return function(proxy, allowedHost) {
      // Create the default config by calling configFunction with the proxy/allowedHost parameters
      const config = configFunction(proxy, allowedHost);

      config.headers = {
        'Access-Control-Allow-Origin': '*',
        'Access-Control-Allow-Methods': 'GET',
        'Access-Control-Allow-Headers':
          'X-Requested-With, content-type, Authorization',
      };

      // Return your customised Webpack Development Server config.
      return config;
    };
  },
  webpack: function(config, env) {
    config.optimization.splitChunks = {
      cacheGroups: {
          default: false,
      },
    };
    config.optimization.runtimeChunk = false;

    config.module.rules = [
      {
        test: /node_modules\/@coinbase\/cbpay-js/,
        use: {
          loader: 'babel-loader',
          // if you include your babel config here,
          // you don’t need the `babel.config.json` file
          options: { presets: ['@babel/preset-env'] }
        }
      },
      ...config.module.rules
    ]
    return config;
  }
};

I'm guessing I'm missing a dependecy for a babel loader or something, but I'm not sure how to figure out which one I need?

Coinb

Hmmm

I have the exact same issue in Vue3 with webpack (non vite).

I'm trying to integrate with the coinbase pay sdk. I've created a button using their examples, however when trying to build I'm getting an issue Internal to their SDK
When trying to build my code I get an error internal to the `@coinbase/cbpay-js sdk
./node_modules/@coinbase/cbpay-js/dist/index.mjs 135:34
Module parse failed: Unexpected token (135:34)
File was processed with these loaders:
 * ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
 var isMobileSdkTarget = /* @__PURE__ */__name(win => {
   try {
>     return win.ReactNativeWebView?.postMessage !== void 0;
   } catch {
     return false;

This is my package.json:
{
  "name": "React App",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "@arkane-network/web3-arkane-provider": "^0.23.0",
    "@ethersproject/experimental": "^5.4.0",
    "@gelatonetwork/limit-orders-react": "^2.4.0",
    "@gnosis.pm/safe-apps-sdk": "^4.0.0",
    "@reduxjs/toolkit": "^1.3.5",
    "@transak/transak-sdk": "^1.0.28",
    "@types/jest": "^25.2.1",
    "@types/lodash.flatmap": "^4.5.6",
    "@types/multicodec": "^1.0.0",
    "@types/node": "^13.13.5",
    "@types/qs": "^6.9.2",
    "@types/react": "^17.0.0",
    "@types/react-dom": "^17.0.0",
    "@types/react-redux": "^7.1.8",
    "@types/react-router-dom": "^5.1.8",
    "@types/react-slick": "^0.23.7",
    "@types/react-virtualized-auto-sizer": "^1.0.1",
    "@types/react-window": "^1.8.5",
    "@types/styled-components": "^5.1.15",
    "@types/testing-library__cypress": "^5.0.5",
    "@typescript-eslint/eslint-plugin": "^5.3.1",
    "@typescript-eslint/parser": "^5.3.1",
    "@uniswap/governance": "^1.0.2",
    "@uniswap/liquidity-staker": "^1.0.2",
    "@uniswap/merkle-distributor": "1.0.1",
    "@uniswap/sdk": "npm:quickswap-sdk@3.0.8",
    "@uniswap/token-lists": "npm:quickswap-token-lists@1.0.1",
    "@uniswap/v2-core": "1.0.0",
    "@uniswap/v2-periphery": "^1.1.0-beta.0",
    "@web3-react/core": "6.0.9",
    "@web3-react/injected-connector": "6.0.7",
    "@web3-react/ledger-connector": "6.1.9",
    "@web3-react/portis-connector": "6.0.9",
    "@web3-react/walletconnect-connector": "6.2.4",
    "@web3-react/walletlink-connector": "6.2.3",
    "ajv": "^6.12.3",
    "apollo-cache-inmemory": "^1.6.6",
    "apollo-client": "^2.6.10",
    "apollo-link-http": "^1.5.17",
    "cids": "^1.1.9",
    "copy-to-clipboard": "^3.2.0",
    "cypress": "^7.7.0",
    "eslint": "^7.11.0",
    "eslint-config-prettier": "^6.11.0",
    "eslint-plugin-prettier": "^3.1.3",
    "eslint-plugin-react": "^7.19.0",
    "eslint-plugin-react-hooks": "^4.0.0",
    "ethers": "^5.0.7",
    "fortmatic": "^2.2.1",
    "graphql": "^15.5.1",
    "graphql-tag": "^2.12.5",
    "hamburger-react": "^2.4.1",
    "i18next": "^20.4.0",
    "i18next-browser-languagedetector": "^6.1.2",
    "ipfs-deploy": "^11.1.0",
    "lodash.flatmap": "^4.5.0",
    "multicodec": "^3.0.1",
    "multihashes": "^3.0.1",
    "polished": "^3.3.2",
    "prettier": "^1.17.0",
    "qs": "^6.9.4",
    "react": "^17.0.2",
    "react-app-rewired": "^2.1.8",
    "react-device-detect": "^1.6.2",
    "react-dom": "^17.0.2",
    "react-feather": "^2.0.8",
    "react-i18next": "^11.11.4",
    "react-redux": "^7.2.4",
    "react-router-dom": "^5.2.0",
    "react-scripts": "4.0.3",
    "react-virtualized-auto-sizer": "^1.0.6",
    "react-window": "^1.8.6",
    "redux-localstorage-simple": "^2.4.1",
    "serve": "^11.3.2",
    "source-map-explorer": "^2.5.2",
    "start-server-and-test": "^1.11.0",
    "typescript": "^4.1.2",
    "web3": "^1.7.0"
  },
  "resolutions": {
    "yargs-parser": "^13.1.2",
    "underscore": "^1.12.1",
    "lodash": "^4.17.21",
    "trim-newlines": "^3.0.1",
    "nth-check": "^2.0.1",
    "node-fetch": "^2.6.7",
    "follow-redirects": "^1.14.8",
    "axios": "^0.21.2",
    "immer": "^9.0.6",
    "ansi-html": "^0.0.8",
    "node-forge": "^1.3.0",
    "glob-parent": "^5.1.2",
    "browserslist": "^4.16.5",
    "ajv": "^6.12.3",
    "async": "^3.2.2",
    "ejs": "^3.1.7",
    "cross-fetch": "^3.1.5",
    "eventsource": "^2.0.2",
    "protobufjs": "^6.11.3",
    "shell-quote": "^1.7.3",
    "terser": "^4.8.1",
    "got": "^11.8.5",
    "jpeg-js": "^0.4.4"
  },
  "scripts": {
    "analyze": "source-map-explorer 'build/static/js/*.js'",
    "start": "react-app-rewired start",
    "build": "CI=false react-app-rewired --max_old_space_size=4096 build",
    "test": "react-app-rewired test --env=jsdom",
    "format": "prettier --write \"**/*.{ts,js,tsx,json,md}\"",
    "eject": "react-scripts eject",
    "integration-test": "start-server-and-test 'serve build -l 3000' http://localhost:3000 'cypress run'",
    "ipfs-deploy": "ipfs-deploy build"
  },
  "eslintConfig": {
    "extends": "react-app",
    "ignorePatterns": [
      "node_modules"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  },
  "license": "GPL-3.0-or-later",
  "dependencies": {
    "@coinbase/cbpay-js": "^1.6.0",
    "@material-ui/core": "^4.12.3",
    "@material-ui/icons": "^4.11.2",
    "@material-ui/lab": "^4.0.0-alpha.60",
    "apexcharts": "3.32.1",
    "i18next-http-backend": "^1.4.1",
    "market-sdk": "^2.2.0",
    "react-apexcharts": "1.3.9",
    "react-cool-inview": "^2.0.8",
    "react-ga": "^3.3.0",
    "react-query": "^3.34.19",
    "react-reflex": "^4.0.6",
    "react-slick": "^0.28.1",
    "react-virtuoso": "^2.8.4",
    "sass": "^1.51.0",
    "slick-carousel": "^1.8.1",
    "styled-components": "^5.3.3"
  }
}

config-overrides.js
module.exports = {
  // The function to use to create a webpack dev server configuration when running the development
  // server with 'npm run start' or 'yarn start'.
  // Example: set the dev server to use a specific certificate in https.
  devServer: function(configFunction) {
    // Return the replacement function for create-react-app to use to generate the Webpack
    // Development Server config. "configFunction" is the function that would normally have
    // been used to generate the Webpack Development server config - you can use it to create
    // a starting configuration to then modify instead of having to create a config from scratch.
    return function(proxy, allowedHost) {
      // Create the default config by calling configFunction with the proxy/allowedHost parameters
      const config = configFunction(proxy, allowedHost);

      config.headers = {
        'Access-Control-Allow-Origin': '*',
        'Access-Control-Allow-Methods': 'GET',
        'Access-Control-Allow-Headers':
          'X-Requested-With, content-type, Authorization',
      };

      // Return your customised Webpack Development Server config.
      return config;
    };
  },
  webpack: function(config, env) {
    config.optimization.splitChunks = {
      cacheGroups: {
          default: false,
      },
    };
    config.optimization.runtimeChunk = false;

    config.module.rules = [
      {
        test: /node_modules\/@coinbase\/cbpay-js/,
        use: {
          loader: 'babel-loader',
          // if you include your babel config here,
          // you don’t need the `babel.config.json` file
          options: { presets: ['@babel/preset-env'] }
        }
      },
      ...config.module.rules
    ]
    return config;
  }
};

I'm guessing I'm missing a dependecy for a babel loader or something, but I'm not sure how to figure out which one I ne

Have you found a solution to this by chance?

I'm guessing I'm missing a dependecy for a babel loader or something, but I'm not sure how to figure out which one I ne

Have you found a solution to this by chance?

try
import ... from '@coinbase/cbpay-js/dist/index.js'

instead '@coinbase/cbpay-js
it will get .mjs by default, based on the exports in package.json
"exports": {
  ".": {
    "types": "./dist/index.d.ts",
    "import": "./dist/index.mjs",
    "require": "./dist/index.js",
    "default": "./dist/index.js"
  },
  ...
}

but somehow it occurred the same issue even I tried require
it works for me in vue-cli with vue2.6

No idk what the hell I'm doing lol I need to figure this all out
On Thursday, March 23, 2023 at 10:41:21 PM MDT, Nick Lin @.***> wrote:
I'm guessing I'm missing a dependecy for a babel loader or something, but I'm not sure how to figure out which one I ne
Have you found a solution to this by chance?
try
import ... from @.***/cbpay-js/dist/index.js'
instead @.***/cbpay-js
it will get .mjs by default, based on the exports in package.json
"exports": {
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.mjs",
"require": "./dist/index.js",
"default": "./dist/index.js"
},
...
}
but somehow it occurred the same issue even I tried require
it works for me in vue-cli with vue2.6
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

How do I get money from this
On Thursday, March 23, 2023 at 10:41:21 PM MDT, Nick Lin @.***> wrote:
I'm guessing I'm missing a dependecy for a babel loader or something, but I'm not sure how to figure out which one I ne
Have you found a solution to this by chance?
try
import ... from @.***/cbpay-js/dist/index.js'
instead @.***/cbpay-js
it will get .mjs by default, based on the exports in package.json
"exports": {
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.mjs",
"require": "./dist/index.js",
"default": "./dist/index.js"
},
...
}
but somehow it occurred the same issue even I tried require
it works for me in vue-cli with vue2.6
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

I really don't know what I'm doing so if you could help me out with the
madness that would be great 👍
Urica Matthews
On Fri, Mar 24, 2023, 12:41 AM Nick Lin @.***> wrote:

I'm guessing I'm missing a dependecy for a babel loader or something, but
I'm not sure how to figure out which one I ne
Have you found a solution to this by chance?
try
import ... from @.***/cbpay-js/dist/index.js'
instead @.***/cbpay-js
it will get .mjs by default, based on the exports in package.json
"exports": {
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.mjs",
"require": "./dist/index.js",
"default": "./dist/index.js"
},
...
}
but somehow it occurred the same issue even I tried require
it works for me in vue-cli with vue2.6
—
Reply to this email directly, view it on GitHub
https://github.com/coinbase/cbpay-js/issues/65#issuecomment-1482240217,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIPPNIEZXFLJU3KLAV6CXE3W5UQXBANCNFSM6AAAAAAR3WI6H4
.
You are receiving this because you commented.Message ID:
@.***>

https://github.com/coinbase/cbpay-js/issues/65#issuecomment-1509473105

repo: coinbase/cbpay-js


text:
Minor typo

Remove duplicate word at line 197
type=routine
risk=low
impact=sev5

This readme is autogenerated. I would fix it in the code comment instead

Thank you, I've created the pull request in the code comment.

source: gharchive/pull-request

repo: coinbase/kryptology

license_type: permissive

license_source: github-api


text:
Colcon mixin documentation outlines potential for misuse (overlapping parameters)

This proposes a mixin documentation fix to describe the potential for misuse when
a. multiple mixins share parameters among each other, or
b. any one mixin shares parameters with the CLI.
It came out of the discussion in https://github.com/colcon/colcon-mixin/issues/20.

cc @dirk-thomas -- it looks like there were spelling mistakes flagged (which broke the Travis CI build). I don't think I have access to spelling/output.txt so cannot verify if this was my language or existing spelling mistakes.

Pinging @dirk-thomas

@robbel Friendly ping.

Since the author never responded to the feedback I will close this in favor of #80.

authors: dirk-thomas robbel


text:
it broke

The sync job broke, fyi @matthewcroughan in case you were relying on it.

looks like maybe they're force pushing. I'll probably try having a "patch" and resetting and then applying the patch instead of the current strategy of rebasing.

No worries, I was planning on forking this soon enough anyway. They're not maintaining it anymore. It's in need of flake-iifying anyway.

I got tired of the emails from github telling me it failed, and I had to write this same thing for wlroots-eglstreams so I fixed it here too.

source: gharchive/issue

authors: MatthewCroughan colemickens

repo: cole-mickens/wfvm


text:
Enums invalid_type issues have unexpected expected value

When adding translations to my global errorMap function, I ran into an issue with the enum type.
const s = z.enum(['Red', 'Green', 'Blue']);
console.log(s.safeParse(null));

This produces a ZodError with the following issue:
{
    "expected": "'Red' | 'Green' | 'Blue'",
    "received": "undefined",
    "code": "invalid_type",
    "path": [
        "color"
    ]
}

The problem here, is that the expected value ends up as a string representation of the array provided. I assume the point is to make it look like the Typescript representation, but that's not any of the expected values in the ZodInvalidTypeIssue.expected type. This makes it kind of impossible to add a general translation for enum errors in the generic global error map function.
It would be much better if expected was hardcoded "enum", and then the valid enum values instead came as a separate property. This would make it possible to translate all enum errors properly, and also give the ability to format the valid options however you want:
function zodErrorMap(...[issue, ctx]: Parameters<ZodErrorMap>): string {
  switch (issue.code) {
    case ZodIssueCode.invalid_type:
      switch (issue.expected) {
        case 'number':
          return 'must be a valid number';

        case 'integer':
          return 'cannot have decimals';

        case 'enum': // Currently not possible
          return `must be one of ${issue.valid.join(', ')}`

        case 'boolean':
          switch (issue.received) {
            case 'null':
            case 'undefined':
              return 'må fylles ut';
            default:
              return 'må være en boolsk verdi';
          }
      }
      break;

A workaround, if others run into this before it hopefully gets improved:
case ZodIssueCode.invalid_type:
  switch (issue.expected) {
    // ...
  }

  if (/^(?:'(\w+)'(?: \| )?)+$/.test(issue.expected)) {
    return 'må være valgt';
  }

  break;

repo: colinhacks/zod

license: MIT


text:
3.22.5 exists on npmjs but not on github

Hi. Thanks for all the great work on zod. I noticed that 3.22.5 exists on npm, but does not have a tag or release here on github.

Yeah there were no changes in that one...like literally no code changed. I pushed an empty commit by accident. 😅

authors: colinhacks eoftedal


text:
Upgrade MariaDB to v10.2

Hi, thank you for the excellent project.
I'm planning to start using galera and hope this image helps me. I'd like to start from the latest MariaDB. Does MariaDB 10.2 have some difficulties?

I don't know, perhaps give it a god and let us know! :)
I wouldn't be at all surprised if a few options have changed names, been deprecated, new features added, etc..

Actually it looks like it has been a while since Galera has released an update so I think as of now the latest 10.1 and 10.2 are using the same version of Galera so there may not be any issues.

Thanks. I'll try next week if I have time, ICBW. I knew Galera had own version now, I'm a very beginner. Please don't expect too much!

If anyone is interested, in the fork https://github.com/cpjolly/mariadb-galera-swarm I've created update.sh and Dockerfile.template, to generate version folders, similar to the structure in https://github.com/docker-library/mariadb.
@colinmollenhour - let me know if you'd like me to make a pull request.

Thanks guys I started maintaining a second Dockerfile for 10.1 and 10.2 will be in the main Dockerfile now. 10.1 is pegged at 10.1.31 for now until the bugs are fixed upstream so the patches can be removed. I believe 10.1 to be stable now. I still haven't tested 10.2 myself but it should work as well.

authors: colinmollenhour cpjolly kujiy

repo: colinmollenhour/mariadb-galera-swarm


text:
Running mongo with rails on a mac.

I added some basic language to README.md that tries to abstract how to start MongoDB with a Rails server on a Mac users.

Current coverage is 98.28% (diff: 100%)

Merging #738 into master will not change coverage

@@             master       #738   diff @@
==========================================
  Files            31         31
  Lines           642        642
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            631        631
  Misses           11         11
  Partials          0          0

Powered by Codecov. Last update 32a08a7...5fc391f

authors: codecov-io mvaden

license: mit

license_source: bigquery


text:
Install react router

For anyone who has not used React Router before, you might want to take a look at this video:
Learn React Router v6 In 45 Minutes

This is a great video, could you share it instead in the links and resources for groupwork issue though? This way all the info will be in one place.

Done (y)

Looking good! Thanks

authors: collectivenectar kgni

repo: collectivenectar/react-projects


text:
Provide an option to not escape unicode characters

This is a fix for #42
All needed functionality was already defined in the library but wasn't exposed in a PPrinter API.
I added escapeUnicode flag to a Walker. By default, I set it as false. This is an arguable decision because previously all unicode characters were automatically escaped. But I don't see any good reason, why by default we need to escape unicode characters. So I decided to change the default behavior.
Also, I added tests.

Superseded by https://github.com/com-lihaoyi/PPrint/pull/71

authors: LMnet lihaoyi

repo: com-lihaoyi/PPrint


text:
Instrument OS-Lib to block filesystem writes outside of designated Task.dest directories (2000USD Bounty)

From the maintainer Li Haoyi: I'm putting a 2000USD bounty on this issue, payable by bank transfer on a merged PR implementing this.

The goal of this bounty is to ensure that users on the "happy path" of accessing the filesystem via OS-Lib do not accidentally do the wrong thing by writing to places on disk they shouldn't. This isn't meant to be a 100% secure sandbox to protect against malicious code, but rather just guardrails for users to bump into when they accidentally do the wrong thing and help nudge them back in the right direction.
In particular, we want to block:

Code inside task writing to paths on disk outside of that task's designated Task.dest folder

Code outside of tasks writing to disk at all, i.e. during module initialization, which is meant to be pure

Code inside of tasks reading from disk outside of the .dest folders of upstream paths or Task.Source/Task.Sources/Task.Inputs

Some subtleties:

We only want to block unexpected writes to disk inside of WorkspaceRoot.

Outside of the WorkspaceRoot still needs to be writable, due to things like caches in /User or /home and temporary files/folders in /tmp.
This is a similar approach as tools like Bazel

We only want to block OS-Lib APIs for now.

People can always use java.io/java.nio/JNI/subprocesses/etc. to work around it, but at least in the common path there'll be something to nudge them when they do something wrong.
A fancier approach could use the JVM SecurityManager/bytecode-instrumenting-agent to block java-level file access as well, but for the purposes of this "guardrails" approach that is probably not necessary

Milestones

[ ] Instrument the various APIs in https://github.com/com-lihaoyi/os-lib to expose a scala.util.DynamicVariable allowing thread-local gating of reads and writes to specific paths, allowing us to throw errors if a read or write is disallowed (500USD)

[ ] Use the patched OS-Lib to limit writes from code running inside a task to locations within WorkspaceRoot but outside the task's Task.dest folder, with a flag to opt-out if desired (500USD)

[ ] Limit writes from code running during module-initialization/task-resolution to any location within WorkspaceRoot but outside the task's Task.dest folder, with a flag to opt-out if desired (500USD)

[ ] Limit reads from code running inside of tasks accessing locations outside of PathRefs received by that task's direct upstream dependencies. (500USD)

As adding such sandbox restrictions are breaking changes, they should be placed behind a flag in the upcoming Mill 0.12.x series and only turned on by default in 0.13.0

Are you sure you want to make os-lib that deeply dependent on a fairly specialized feature?  Might it be better to have an API-compatible alternative build so you could depend on os-lib-fenced instead of os-lib if you needed fenced filesystem operations?
Also, everything you mention is JVM-specific but os-lib has a native build as well.  Is fencing supposed to work with native?

@Ichoran it seems the most reasonable option. The alternative is we do bytecode instrumentation.
The implementation cost of stuffing this into OS-Lib seems relatively low: just a single DynamicVariable containing a trait Gating{ def allowRead(p: os.Path): Unit; def allowWrite(p: os.Path): Unit } that we can expand upon over time if necessary.
Nothing here seems JVM-specific or Mill-specific. Seems plausible that there would be other use cases for best-effort limiting of filesystem access as well. The JVM baked this stuff in 30 years ago, and although it is now taking it out, I think it's actually a pretty reasonable feature to have as long as expectation are set appropriately (e.g. best-effort guardrails, not a security-sensitive sandbox as the JVM was hoping for)

@lihaoyi - Well, the interface change is small, but it's going to touch a lot of code, and make every user of threads add an extra ThreadLocal variable to everything.  That's a big deal for Project Loom-style usage.  "Don't use os-lib and virtual threads together" isn't a great message.

Why is it a big deal for project loom usage?

The ThreadLocal variable has to be duplicated for every use of every thread since otherwise ThreadLocal is broken.  So it adds to the per-thread overhead.  The Oracle docs all caution against it.  I haven't actually run a microbenchmark myself, though.

@Ichoran does that mean println is banned in project loom?

println uses ThreadLocal?  Huh.  Did not know that.  Regardless, maybe I should actually do the microbenchmarking and then raise the concern if it's a non-negligible impact.

Yeah, I'm going to say performance is not a problem, until benchmarks demonstrate it is

Well, it's measurable, but I guess it's not really important.  It seems to be negligible on creation, just usage, and it's only if there's a creation issue that it's really something to avoid.  It's a little hard to do benchmarking of threads on a laptop CPU; even if I turn off as many CPU features as I can, it's still a bit inconsistent.  Using the benchmark I wrote here, I get the following:
Benchmark                 Mode  Cnt    Score    Error  Units
ThreadLocalLoom.base      avgt   40  641.756 ±  6.503  us/op
ThreadLocalLoom.local10   avgt   40  639.881 ±  9.644  us/op
ThreadLocalLoom.localmod  avgt   40  672.530 ± 17.414  us/op
ThreadLocalLoom.localuse  avgt   40  657.495 ±  9.196  us/op

and if you look through the individual counts, you see the ~640 to ~655 shift as a very common outcome.  So, maybe a 3% slowdown above the thread handling overhead.  (Most of the time is thread overhead--probably 90% or so.  I didn't measure carefully.)  Mod vs. Use depends on whether the thread changes the value or just consumes it from a withValue block.
The key point, though is the local10 one, where ten extra DynamicVariable instances are created but they're not used.  This has no performance penalty, and that's the one I was worried about.
So, I'm incorrect!  A lot of the advice, including from Oracle, also seems to be incorrect or at least too cautious.  One can use ThreadLocal with about the usual degree of slowdown for ThreadLocal, probably (on the order of 30 ns, because it's about 15 us in a test which uses it 500-odd times).
Sorry about the unwarranted concern!  Original plan sounds fine!

@lihaoyi

Instrument the various APIs in https://github.com/com-lihaoyi/os-lib to expose a scala.util.DynamicVariable allowing thread-local gating of reads and writes to specific paths, allowing us to throw errors if a read or write is disallowed (500USD)

Does this extend to get/set ops for permissions/stats?
Should file/folder create/remove ops require write access on the parent folder?

When creating intermediate parent folders, write access should be required on the closest existing parent?

When moving files/folders, both read/write access should be required on the source parent folder?

Does this extend to get/set ops for permissions/stats?

Only for set operations

Should file/folder create/remove ops require write access on the parent folder?
When creating intermediate parent folders, write access should be required on the closest existing parent?
When moving files/folders, both read/write access should be required on the source parent folder?

I think we can start with an API as follows
trait Checker{
  def onWrite(path: os.Path): Unit
  def onRead(path: os.Path): Unit
}

where onWrite and onRead are given the fully qualified path where any operation is taking place (not the parent folder). That way it is up to the implementor of Checker (or whatever we call it) how they want to model permissions, deal with nested permissions and so on. OS-Lib does not need to have an opinion on that, it just needs to provide the minimal hooks and the downstream implementor (e.g. Mill) can come up with whatever model is suitable

authors: Ichoran ajaychandran lihaoyi

repo: com-lihaoyi/mill


text:
Allow c2 to annotate

Still need to add the c2 up-sell in place of EON up-sell

Actually, need to make this work with EON too

repo: commaai/explorer


text:
GM: get VIN

You simply need to allow a different subset of addresses to send to in ELM mode (think 0x200 range?)

Hi Shane,
Can I pick this challenge and if possible, can you point me the initial file where to begin as I am new to this project?

I think this might have to do with getting VIN on GM:
https://docs.google.com/spreadsheets/d/1qEwOXSr3bWoc2VUhpuIam236OOZxPc2hxpLUsV0xkn0/edit#gid=2
Row 162 and 163

@leoforney Thank you so much. I will start working on this in December. Currently working on my writing thing. =)

@sshane What's wrong with using VIN1 and VIN2 signal?

Right now openpilot generates carParams once on startup, this requires a bit of a change to the architecture of openpilot. Doable, and we might want to do this since other cars also publish their VIN like this, but with the Bolt at least, we can just query the camera as the easiest way to get the VIN, right now.

Done in https://github.com/commaai/openpilot/pull/31224

authors: garrettpall leoforney sshane varshneydevansh

repo: commaai/openpilot


text:
Add 2020 Lexus RX Hybrid support

Added FPv2 of 2020 Lexus RX 450h Hybrid and test drove said car using toyota_nodsu_hybrid_pt_generated
Route:
b74758c690a49668|2020-05-20--15-58-57
Cabana and Explorer

There are two things missing to finish the port:

We want to make sure the old style fingerprint doesn't interfere with existing users. Therefore it needs to be added to this list: https://github.com/commaai/openpilot/blob/master/selfdrive/car/toyota/values.py#L264

Add your demo route to CI so it will be tested every time there is commit. Add an entry here like the non hybrid RX: https://github.com/commaai/openpilot/blob/master/selfdrive/test/test_car_models.py#L302. The important part here is the fingerprintSource.

Thanks @pd0wm -- I hope it's alright

All good! Thanks for doing the port!


text:
Payment method missing on thank you page reload

Description
Payment method is missing on thank you page when reloading.

:tada: This issue has been resolved in version 4.8.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

repo: commercelayer/mfe-checkout


text:
Ability to disable ensure resources

This fixes #72.
This is based off of the changes in #68.
Once that PR is merged, this one should follow. This is due to conflicts that would otherwise exist due to changes made in that PR

Thanks for merging the other two PRs! Now that they are merged, I have reset this one based on master so it only has the two new commits in there. As always, shout if there's anything you want any changes done!


text:
Retries after timeout errors immediately run into timeout after 0 ms

Retries after timeout errors immediately run into timeout after 0 ms
It looks like the SDK is reusing the AbortController from the initial request. But this is already timed out and will no longer work. Possible solution: Create a new AbortController for every request/retry
Here is a screenshot from our logs when the issue happens: The logging is done by wrapper around the fetch function. NETWORK_ERROR means there was no HTTP response status code

here the init of the client
const ctpClient = new ClientBuilder()
            .withProjectKey(config.projectKey)
            .withClientCredentialsFlow({
                host: `https://auth.${config.region}.gcp.commercetools.com`,
                httpClient: fetchWithDefaults,
                projectKey: config.projectKey,
                credentials: {
                    clientId: config.clientId,
                    clientSecret: config.clientSecret,
                },
            })
            .withHttpMiddleware({
                host: `https://api.${config.region}.gcp.commercetools.com`,
                httpClient: fetchWithDefaults,
                enableRetry: true,
                timeout: 5000,
                retryConfig: {
                    retryOnAbort: true,
                    maxRetries: 4,
                    retryDelay: 400,
                    retryCodes: [504, 503, 502, 500],
                },
            })
            .withConcurrentModificationMiddleware()
            .build()

Fixed with the latest version. Thank you


text:
coordinates present but not found

Several of my images are reported as having no coordinates (see screenshot, in comment), despite the presence of the {{Object location dec}} template.
Screenshot shows https://commons.wikimedia.org/wiki/File:Panorama_war_memorial_-2018-04-23-Andy_Mabbett-_01.jpg

Hi Andy, thanks for the feedback!
Could you please tell us what metadata the app should write, and what it wrote instead?
Did you perform this edit manually? Does the final metadata represent what the app should write?
Cheers!

Ah, I think I misunderstood.
The metadata is correct, but the problem is that the details activity's Coordinates field contains "None provided", right?

I'm not clear what you mean by "the details activity"; but the problem is that the image (which was not uploaded by the app) has coordinates and yet the app says "none provided".

Sorry, "details activity" is the screen that shows the details of an image, as seen in your screenshot.
The app gets the location like this:
Node coordinateTemplateNode = findTemplate(doc.getDocumentElement(), "location");

It seems that we should check for other templates such as  https://commons.wikimedia.org/wiki/Template:Object_location and possibly others.
Do you know where we can get a list of all possible location templates and their syntax?
Hopefully with Structured Commons we will be able to get coordinates in a single unified way :-)

Coordinates templates are in https://commons.wikimedia.org/wiki/Category:Geocoding_templates
Note that some image pages have more then one set of coordinates - for example, for a distant object, the location of the object, and of the camera.

Can anyone recall whether this was resolved?
Chris.

authors: chrisdebian nicolas-raoul pigsonthewing

repo: commons-app/apps-android-commons


text:
Contributions Screen- Nearest Feature

What is the user problem or growth opportunity you want to see solved?
When using the app, at the top of the Contributions tab/page, I can see the nearest location to me, that is recognised as being if interest. In many cases, a photograph of the location has already been submitted.
How do you know that this problem exists today? Why is this important?
So that it is easier to identify the next item needing a photo, would it be possible to only show 'near' places that actually need a photo?
Who will benefit from it?
This will enable photos to be taken and uploaded, with less effort, so should increase contributions.
Anything else you would like to add?
Forgive me if this was an options in the settings, that I missed. The 'Display Nearby Notification' is turned on, but seems to show all locations, not just those needing photos.
Cheers,
chris_debian
2E0FRU

I'm using version 3.1.1~1c9267ca0, on a Pixel 4a.

@nicolas-raoul, this seems to be a duplicate of #5448 which is already solved by #5468. Could we close this as completed?

Oops I am the one who created a duplicate.
Thanks for noticing!

authors: ShashwatKedia chrisdebian nicolas-raoul


text:
Replace Mapbox with OSMDroid in Explore Activity

This issue is in continuation to https://github.com/commons-app/apps-android-commons/issues/5414 where @sivaraam suggested to replace Mapbox to OSMDroid in every place of the app. Since we have already replaced mapbox to osmdroid in Upload Activity (https://github.com/commons-app/apps-android-commons/pull/5443) and Nearby Activity (https://github.com/commons-app/apps-android-commons/pull/5403). Only map in Explore Activity is left to be replaced, which I expect to be achieved in upcoming pull requests by me.

Great! If I understand correctly, there will be no trace of MapBox (no Mapbox-related imports in Java/Kotlin/Gradle) after this? :-)

There will be small amount of code still left such as LatLng is used from mapbox package but we can remove it which will not take much time then we can completely remove Mapbox-related imports in Java/Kotlin/Gradle.

Hello @nicolas-raoul, I have successfully 🙌 replaced MapBox with OSMDroid and tested it on production server. I will share the pull request as soon as possible.
https://github.com/commons-app/apps-android-commons/assets/114223204/6dca5d00-bf1b-44f4-90e6-31625d0a72d1

Wonderful! 🙂


text:
Categories with pipe suffix

Categories with pipe suffix
Fixes {GitHub issue number #1826 and title Categories with pipe suffix}
Description (required)
Certain Categories in MediaDetailsFragment used to show up suffixed with pipe. Because of which , when such categories were clicked, the associated images did not show up, because server could not find any images associated because of the pipe suffix.
Fixes {GitHub issue number #1826 and title Categories with pipe suffix}
Changes made :
-Certain category names used to show suffixed with strings prefixed with pipe '|'. Removed everything after the pipe. As per the discussion on the thread, its safe to remove everything after the pipe, including the pipe
{Describe the changes made and why they were made.}
As a fix, I have looped the category names list and and for each category name if it contains a pipe '|'. It removes everything from the string proceeding the pipe including the pipe. As a result of which, the categories would be shown without the pipe and the clicks on them would show appropriate images.
Tests performed (required)
Tested on {27 & name of Pixel 2}, with {build variant, ProdDebug}.
Screenshots showing what changed (optional)

Codecov Report

Merging #1873 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1873      +/-   ##
=========================================
- Coverage    3.61%   3.61%   -0.01%
=========================================
  Files         188     188
  Lines        9839    9842       +3
  Branches      873     874       +1
=========================================
  Hits          356     356
- Misses       9457    9460       +3
  Partials       26      26

Impacted Files
Coverage Δ

...fr/free/nrw/commons/media/MediaDetailFragment.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Thanks for PR @ashishkumar468 , can you please include issue title to PR title too? It would be a lot easier for tester while checking all PRs from list:)

@neslihanturan I have made the required changes, if you could review :)

@neslihanturan Bump?

Ready, works for me. Thanks @ashishkumar468 !

authors: ashishkumar468 codecov-io domdomegg neslihanturan


text:
Proto/uncompeted fund journey

Ayyy lmao!

No need for merging.


text:
Approved List of Contributors From My Organization in Project EasyCLA page

Summary
Any user associated with a company will be taken to this page after they switch to member console, select project from left navigation and EasyCLA from top navigation.
Here is the link to wireframe for the project page for EasyCLA.

Step 4 in PRD
https://confluence.linuxfoundation.org/display/PROD/Project+Dashboard+for+EasyCLA
Approved List of Contributors From My Organization will show the CLAs signed by user's company. The table displays following columns:
Approved List is the emaild or GitHub userid or GitHub Organization or Domain name that is in approved list.
Coverage Type explains the type of approved list in column 1.
Added on i.e. date it was added to approved list.
Manage allows you to edit the approved list or delete it. There is no confirmation dialog box for editing or deleting a contributor. Only users who have CLA Manager permission for this project should be shown this manage option
The information for this table will be provided by EasyCLA API
NOTE :
If the user's company has not got any signed CLAs that fall under this foundation then this table display is empty.
There is no pagination on this table, all the values will be displayed at once
Acceptance Criteria

[ ] Design Changes Required ?--> Not Applicable (N/A)
[ ] Unit Testing Complete

[ ] Unit Testing complete for backend API
[ ] Unit Testing complete for UI

[x] Functional Testing Complete

[ ] Functional Testing complete for backend API
[ ] Functional Testing complete for UI

[ ] Integration Testing Complete

[ ] Integration Testing complete for backend API and UI
[ ] Integration Testing complete end to end dev deployment

[ ] Documentation Updated
[ ] Any Open Sev. 1 bug(s)

@nirupamav I have created a few functional tests for this one. We can easily expend this set of tests to be more comprehensive.  Please review: https://github.com/communitybridge/easycla/blob/master/cla-backend-go/cmd/functional_tests/signatures/signatures.go#L199  Let's discuss more on Monday.

@pranab-bajpai @dealako
Could you please clarify below queries

As per the PRD, Name and Added On are listed. But in our response we are not getting name and added on. As per my understanding, the contributor might not be in our user system to fetch from user service. If my understanding is wrong LFX team fetch the data from user service
As per PRD, CLA Manager and Non-CLA Manager can view data but only CLA Manager can edit the data.
I tested it with different roles and observed that except for cla-manager and lf-operations roles, 401 is returned for other roles
As per PRD, CLA-Manager who has access to the project of the organization can manage the list. As of now the API returns 401 if the scope is project|Organization and returns data with 200 when role scope is Organization. Does this mean that if the user is CLA Manager for the Organization, he can manage all projects of the organization

For #1 defined above, for now, we won't load the user's name if they are in the email field. We would have to search around for the user's name - not stored in the signature, most-likely not in the EasyCLA user's table, and probably not in the Platform User service. Most of these users will be GH users with no relationship with CommunityBridge other than pass/fail of the EasyCLA gating.

For #2 - will review the permissions. For now, it's locked down to the CLA Manager and admins.

As Endpoint needs modification reopening the ticket

@prasannamahajan what is the latest update on this one? If it is work in progress then please provide the ETA.

API : https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/api-docs#operation/getProjectCompanySignatures
Moving ticket in "Ready for review" state

Performed testing for happy path and happy path is working as expected. However I have query regarding CLA group and if @pranab-bajpai clarifies that CLA group is required then endpoint may require changes else if @pranab-bajpai confirms that current behavior is as expected then no change is required for the endpoint.
Testing is Inprogress for other scenarios
At Project Level CLA Managers of only the project are fetched
Test Data used
Role cla-manager
Scope
Cloud Native Computing Foundation|Bakbone
Endpoint
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/signatures/project/a092M00001IV45HQAT/company/0014100000Te1DWAAZ
Response
{
"resultCount": 2,
"signatures": [
{
"companyName": "Bakbone",
"created": "2020-06-01T10:11:39.485378+0000",
"domainApprovalList": [
"proximabiz.com"
],
"emailApprovalList": [
"nirupamav+mentee12341@proximabiz.com"
],
"githubOrgApprovalList": [
"niruorg"
],
"githubUsernameApprovalList": [
"nirupamav"
],
"modified": "2020-06-01T10:11:39.485385+0000",
"projectID": "3d354e3d-1561-49bf-a66c-ffa31392a018",
"signatureACL": [
{
"dateCreated": "2020-05-18T09:25:29Z",
"dateModified": "2020-06-01T07:27:43Z",
"emails": null,
"lfEmail": "nirupamav+clamanager10@proximabiz.com",
"lfUsername": "nirupamavclamanager10",
"userID": "83b550d0-98e9-11ea-b69b-fa63295d7f2d",
"username": "nirupamav clamanager10",
"version": "v1"
}
],
"signatureApproved": true,
"signatureCreated": "2020-06-01T10:11:39.485378+0000",
"signatureID": "07f3dc1b-56b2-46a7-bc14-62d5b344e0b3",
"signatureMajorVersion": "2",
"signatureMinorVersion": "0",
"signatureModified": "2020-06-01T10:11:39.485385+0000",
"signatureReferenceID": "0014100000Te1DWAAZ",
"signatureReferenceName": "Bakbone",
"signatureReferenceNameLower": "bakbone",
"signatureReferenceType": "company",
"signatureSigned": true,
"signatureType": "ccla",
"version": "2.0"
},
{
"companyName": "Bakbone",
"created": "2020-06-01T10:11:39.485378+0000",
"domainApprovalList": null,
"emailApprovalList": null,
"githubOrgApprovalList": null,
"githubUsernameApprovalList": null,
"modified": "2020-06-01T10:11:39.485385+0000",
"projectID": "2e3f95be-962e-4eb0-90d6-48cce5a0218f",
"signatureACL": [
{
"dateCreated": "2020-05-18T09:25:29Z",
"dateModified": "2020-06-01T07:27:43Z",
"emails": null,
"lfEmail": "nirupamav+clamanager10@proximabiz.com",
"lfUsername": "nirupamavclamanager10",
"userID": "83b550d0-98e9-11ea-b69b-fa63295d7f2d",
"username": "nirupamav clamanager10",
"version": "v1"
}
],
"signatureApproved": true,
"signatureCreated": "2020-06-01T10:11:39.485378+0000",
"signatureID": "732730d0-ddb5-43f6-bfb6-8fbdcab63772",
"signatureMajorVersion": "2",
"signatureMinorVersion": "0",
"signatureModified": "2020-06-01T10:11:39.485385+0000",
"signatureReferenceID": "0014100000Te1DWAAZ",
"signatureReferenceName": "Bakbone",
"signatureReferenceNameLower": "bakbone",
"signatureReferenceType": "company",
"signatureSigned": true,
"signatureType": "ccla",
"version": "2.0"
}
],
"totalCount": 0
}

Prasanna informed on lfx-dev slack channel that this api is ready for  consumption by lfx team.

Tested and have below queries and issues

When invalid projectsfId is provided 404 should be returned, but 200 is returned with below response
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/signatures/project/a092M00001IV4PgQLA/company/0014100000Te1DWAAZ

When invalid companysfId is provided 404 should be returned, but 403 is returned with below response
https://api-gw.dev.platform.linuxfoundation.org/cla-service/v4/signatures/project/a092M00001IV45HQAT/company/a092M00001IV4PgQAL

When projectsfid/companysfid is not provided 400 should be returned, but 403 is returned
In the response, null is returned for emails in signatureACL object even though there is a secondary email for the user

As per the  the response model, git hub details should be displayed in the signatureACL object.  But we do not store the github details of the user in cla_dev_users so should those details be in the response model
As per the  the response model, admin and userExternalID details should be displayed in the signatureACL object.  For the CLA Manager admin value exists in cla_dev_users table but is not returned in response. Should sfid for the CLA Manager be returned for userExternalID?
In UI added on is displayed for the approved list and the list is sorted by Added on Date. But API does not return added on date for each approved list

@pranab-bajpai
I have completed testing. Could you please review test plan and let me know if I missed to test any scenarios
Failed test cases are due to tickets #1173, #1036
I test case is blocked due to query related to the sort order of the data which I have posted in PRD. Based on the clarification if required will log a separate ticket for sort order.
Test Plan https://confluence.linuxfoundation.org/display/PROD/getProjectCompanySignatures

Working on fix for this, see: https://github.com/communitybridge/easycla/pull/1182
For invalid company SFID - you probably don't have permissions or it, so the permissions check is caught first
When projectsfid/companysfid is not provided 400 should be returned, but 403 is returned -> permissions are checked and caught first, so 403 is correct.  This is the desired behavior.
This is what we have in the DB. We can raise a separate ticket to keep SF and EasyCLA user emails in sync.

Added logic to show all validation errors - not just the first.

Addressed issues - subsequent tickets can be opened if error message need updates. Core functionality works.

authors: dealako nirupamav pranab-bajpai prasannamahajan vinod-kadam

repo: communitybridge/easycla


text:
Use Administration Prefix List

Updates security group config to utilise a Managed Prefix List to define administrative access, rather that pulling data from vault. This will allow for safer and easier future updates to administrative access.
heritage-shared-infrastructure
Removed vault data lookup and replaced with prefix list data lookup
Removed admin_cidrs local
Removed now-deprecated object attribute from vars
Restructured RDS security groups for use with the prefix list
Added new security group specific to service access to prevent unwanted inheritance of the prefix list
sessions
Migrated from static SG lookups to dynamic list-based method
Added local to construct the necessary SG data
Added SG pattern lists to vars
Added prefix list lookup
Added dedicated SG for service ingress
Amended existing SG to use prefix list

Closing PR - a different approach is being discussed


text:
Address list of the non 3rd party existing build warnings

Updates within package.json server constrains only

CI: No security warnings found

CI: No security warnings found

repo: companieshouse/psc-verification-web


text:
Confusing options

If I give a tag name, what is the branch name used for (and vice-versa)?
Either one uniquely identifies a release.
Please clarify in the README.

Oh, yeah… I don't know how to fix the README for the semantics you've got, but branch is not a branch name and tag is not a tag name.  For 5.9 the branch would be release/5.9 and the tag would be swift-5.9-RELEASE but what I actually have to pass is something like
        branch: swift-5.9-release
        tag: 5.9-RELEASE

Perhaps the option names are poor, naming is difficult!  I'm open to renaming the options in a backwards compatible manner.  The names themselves are references to the URL:
https://download.swift.org/development/windows10/swift-DEVELOPMENT-SNAPSHOT-2023-08-12-a/swift-DEVELOPMENT-SNAPSHOT-2023-08-12-a-windows10.exe
which appears to be:
https://download.swift.org/[branch]/[host]/swift-[tag]/swift-[tag]-[host][suffix]

In the ideal scenario, we would be able to use just the release version and or snapshot (for a release train or stable train) as a single parameter and derive everything from that.

BTW, the tag terminology is also on the download page as well.

We should really discuss how to fix this.  I just came back here and find myself opting for https://github.com/SwiftyLab/setup-swift/ because I can't figure out what these instructions mean.  Presumably your Windows support is better, but at least for simple use cases I totally understand how to use the other one.

i have also found this extremely frustrating although the problem is hardly limited to this particular project. identifying toolchains is hard.

Clearly doesn't have to be this hard. The swiftylab component makes it trivial. Anyone could implement the same API.

Continuing from https://github.com/swift-actions/setup-swift/issues/634#issuecomment-1980787840
@compnerd wrote:

I know that you are frustrated by those options, but they are what apple uses. I'm happy to rename them, but we need the two parameters (or at least a way to derive the two). compnerd/gha-setup-swift does work on other platforms as well, and is much easier to evolve when working with the Windows platform. I don't mind co-maintaining an action if it is designed to take the needs for evolving the Windows support in mind.

Well, the names are confusing, but even if you do that there needs to be

a clear explanation of what the names mean, and
most especially, for the vast majority out there who only want to use released versions of Swift, how to go from an official version number to these settings.

Ideally, though (and you really need to do this if you want uptake of usage) there would be one option you could set that would take an official number, and, if set, would be used to derive the other settings.

could this be as simple in the instructions as saying,

for an official release version X, use
        with:
          branch: swift-${{ X }}-release
          tag: ${{ X }}-RELEASE

?

Yeah, I'm totally happy to have the documentation say that.

authors: compnerd dabrahams tayloraswift

repo: compnerd/gha-setup-swift


text:
create a release tag

can we get a release tag, like v0.1.0?

Hmm, let me bump test with 5.7 and main, and if both of those continue to work with main, I'm happy to tag a v0.1.0.

I knew that I was expecting something to be broken ... https://github.com/compnerd/swift-win32/runs/7546429823?check_suite_focus=true
This shouldn't be too terrible to fix.  There was some shuffling recently where vcruntime.{modulemap,apinotes} was renamed.  We should support both the new name and the old name.

Tagged v0.0.1.


text:
Add more preg wrapper methods

I appreciate that you are already working on this, but since I was already testing various API ideas it seemed quicker to knock up a POC to show how this library could provide safe wrappers for the full range of preg_* function usage (plus its own API), rather than discussing it all. So no worries if you don't want this.

Union types in the preg_* functions are supported (even though Composer may not use them itself)
The $subject param from PcreException::fromFunction has been removed because it was not used
ReplaceResult::result is now a string|string[]
Regex::isMatch has been introduced as syntax sugar for Regex::match(...)->matched

Tests are needed for:

Preg::filter
Preg::grep
Preg::replaceCallbackArray
Preg::split

There is an inconsistency between the preg_ functions that emit warnings (in that Preg::filter is the only one to suppress them) because I don't know what is best to do.

Thanks for illustrating the string|string[] issue. That's a very good point, and I get it now.

I still disagree about supporting array inputs though

I presume you mean array $subjects? So we can:

Remove them completely (from the Preg class)
Allow them in the Preg class but remove them from the Regex class.
Allow them and add a ReplaceArrayResult class (naming?)

And your choice is?

I'd remove them from both classes I think, to keep things simple for now, and add a dedicated method to both classes with dedicated result class later if we really need this?

oh great namer of things

🙄
Message seems fine to me :p
Thanks for the updates, let me review the latest state again.

OK looks good to me, just the couple weird changes in test files which I don't understand, and perhaps adding grep/filter/etc. to the Regex class would be nice, if you have time, otherwise I can do some other time.

Thanks for the updates. Do you still want to add anything? Otherwise I'd merge this already. We're getting closer to something stable IMO.

If you can hang on. I'm just adding missing tests now and I need to fix preg_filter which I hadn't realized returns null when the pattern doesn't match a string:
<?php
preg_filter('/d/', 'e', 'abcd') // abce
preg_filter('/d/', 'e', 'abc')  // null

I'm thinking of allowing Preg::filter to accept arrays, because then it is a bit like preg_grep with a filter, but not adding it to the Regex class. What do you think?

But then you still have to return string[]|string? I'd say if anything I'd allow it only with array because if you're doing it on a single string there's really not a lot of benefit over if(match) {replace}.. Overall this function seems kinda weird to me I don't quite get the use case. I think it mostly is misused by people instead of preg_grep, if I can trust the comments on https://www.php.net/preg_filter
So maybe we just drop filter altogether? How about that? :p

Yes I agree. Reading through the source to see how it worked, it turned out there wasn't even a test for it until last year!

I think I'm done now. Please review, thanks.

Sorry, just had to sort the tests out - they were so hard to read because they were all lumped together and it was easy to make (and not spot) mistakes.
I've only included pcre engine error (backtrack limit exhausted) tests for preg_match. Is it necessary to include them for the other functions?

I've only included pcre engine error (backtrack limit exhausted) tests for preg_match. Is it necessary to include them for the other functions?

Nah that's fine by me.
Thanks for all the test updates, looks good to me 👍🏻

authors: Seldaek johnstevenson

repo: composer/pcre


text:
Use PSR-1 for PHPUnit TestCase

Simple version of composer/spdx-licenses#11.
Use PSR-1 while extending PHPUnit TestCase class. This will help us when to migrate to PHPUnit 6, that no longer support snake case namespaces.

Codecov Report

Merging #12 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #12   +/-   ##
=========================================
  Coverage     98.66%   98.66%
  Complexity       45       45
=========================================
  Files             2        2
  Lines           150      150
=========================================
  Hits            148      148
  Misses            2        2

Continue to review full report at Codecov.

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

Thanks

authors: alcohol codecov-io gabriel-caruso

repo: composer/spdx-licenses


text:
fix: ensure the manifest name is the dependency prefix for local depe…

…ndencies when at top level
I'm submitting a

[x] bug fix
[ ] feature
[ ] documentation addition

What is the current behaviour?
Fixes #388
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
Version (comtrya --version):
Operating system:

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

Comparison is base (f4fd2c1) 28.26% compared to head (e6579c2) 28.26%.

Files
Patch %
Lines

app/src/commands/apply.rs
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #389   +/-   ##
=======================================
  Coverage   28.26%   28.26%
=======================================
  Files          85       85
  Lines        2289     2289
=======================================
  Hits          647      647
  Misses       1642     1642

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

authors: codecov-commenter rawkode

repo: comtrya/comtrya


text:
InteractiveBox > PressableBox

Use case
A more intuitive name describing the expected capacities of the widget (on hover, pressed, long press etc) while also giving room for further development of the widget
Proposal
Suggestion to rename PressableBox to InteractiveBox

Thank you for your contribution!
We were discussing it because it was mentioned on another Issue that requested adding one more callback on PressableBox, the onHover. I agree that to continue with the name PressableBox is a bit weird.
@leoafarias what's your opinion?

Yes, this aligns well with our internal discussions, @jonathanfristedt. We might also create a different name for the Pressable, which is just a provider of the states and does not have the Box styling.

We now support the WidgetStateController and Interactable which handles these cases described
https://www.fluttermix.com/docs/tutorials/controlling-widget-state

authors: jonathanfristedt leoafarias tilucasoli

repo: conceptadev/mix


text:
Simplify DestroyFailedContainers query

remove the expensive, unnecessary JOIN statements
See: concourse/concourse#2036

authors: topherbullock vito

repo: concourse/atc


text:
Bug - broken pagination on sitemap->page search when logged in as non-admin user

When logged in as an admin, the pagination on sitemap->page search works correctly:

As opposed to being logged in as a non-admin user, this is what happens:

Is this bug anything to do with this issue (https://github.com/concrete5/concrete5/issues/5742) which was apparently fixed?

@aembler any thoughts on this issue? I'm running on v8.3.0.1a1.


text:
Multilingual - Copy to Locale Tree errors - Integrity constraint violations

In Multilingual (version 8.4.1), I'm trying to Copy Locale Tree to a new locale, and I get dozens, perhaps hundreds, of errors that seem to be about duplicate foreign keys. Example:
An exception occurred while executing 'insert into MultilingualPageRelations (mpRelationID, cID, mpLocale, mpLanguage) values (?, ?, ?, ?)' with params ["75", "358", "en_US", "en"]: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '75-358' for key 'PRIMARY'
In researching the problem I noticed that it's the aliased pages that it chokes on. I was able to get through all the errors by going in the DB and deleting the entry in question each time.
When it was finally finished (it took hours), I noticed that a lot of the aliased pages had numerous (as in dozens) of duplicates, many with the number 2 appended many times (i.e. 2 2 2 2 2 2 2 2 ) to the page name. (see screenshot)

Clarification after further investigation - it's not strictly aliases that cause the problem, it's just duplicates. So in the above example I actually had some aliases whose originals had later been removed, so they were no longer duplicates, and they didn't cause errors.

Found myself in the same situation... 8.5.2 didn't help either.


text:
Calendar Even attribute breaks for guests

Create an Express form and add a Calendar Event attribute to it to be able to select an event.
Add it to a page and use it as Admin, it works.
Use it as a guest it breaks because ccmi18n is undefined. event-selector.js uses ccmi18n.loadingText.
If I load the core/localization script myself, that error disappears and another one appears complaining that b.fn.dialog.open is not a function
If I require both assets 'core/calendar/event-selector' and 'core/calendar/admin' all JS errors go away but I then get a PHP 500 error: "core/localization" is not a valid asset group handle
This is all happening in 8.4.4, 8.5.0 and 8.5.1

Just to be sure I gave guests permissions to view both "View Calendar" and "Event List" dashboard pages
I also gave guests permission to view that specific calendar in Edit Interface.
Nothing worked

Just to be sure I gave guests permissions to view both "View Calendar" and "Event List" dashboard pages
I also gave guests permission to view that specific calendar in Edit Interface.
Nothing worked


text:
dashboard file manager tweaks

This resolves issue #4129, see comments in there

Since this change wraps a bunch of code in an if statement, the diff is a bit hard to read, try looking at it with whitespace changes hidden: https://github.com/concrete5/concrete5/pull/4374/files?w=1

grunt release && git commit?

:+1: thanks @mlocati

This doesn't actually seem to trigger the menu when I'm using the simulator (and doing a long press)

authors: KorvinSzanto aembler mlocati


text:
Move slideout method of imageeditor to the right place

the slideout method was added to /concrete/js/build/core/image-editor/image-editor.js, which is generated automatically from the chunks in the /concrete/js/build/core/image-editor/build folder.
So, it's overwritten when we run the build process.
Let's move it to the correct file.
PS: there's no need to rebuild the assets manually, since the repository is now automatically updated.

This is wrong

The correct fix is #7173


text:
Remove pin on krb5, lmdbxx, cyrus-sasl and fmt

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

This extracts some of the changes proposed in https://github.com/conda-forge/arcticdb-feedstock/pull/60.

@conda-forge-admin, please rerender

The builds there are being tested by https://github.com/man-group/ArcticDB/pull/888.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Rerendering after manually remerging rc into this branch:
@conda-forge-admin, please rerender

repo: conda-forge/arcticdb-feedstock


text:
Adding update inspection

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12339590371. Examine the logs at this URL for more detail.

@conda-forge-admin, please rerender

repo: conda-forge/beets-feedstock


text:
Upgrade to 3.24.6

Checklist

[X] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

repo: conda-forge/blpapi-feedstock


text:
OSx: building with clang 11 and 12

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, rerender

Sadly I'm not the best to debug this...

To move forward until this is resolved I build my feedstock using clang12 to get around the signing problem. However, this seems to give unwanted conflicts for libcxx in building feedstocks that depend on the one that I merged.
Therefore it would be great if there would be a more global solution. I don't know how to proceed from here, but maybe @isuruf can give some pointers in the right direction ?

Looks like new cctools doesn't codesign at all.

That explains why I don't experience the bug. Is there a reason why it is removed?

I will just document my experience here :

With cctools 12 there is no signing-bug, but binaries compiled with this version give a signing error on the client.
For example the shared-object from
conda install python-goosefem -c conda-forge

(see feedstock) gives
codesign -v GooseFEM.cpython-39-darwin.so
GooseFEM.cpython-39-darwin.so: invalid signature (code or signature have been modified)
In architecture: arm64

(whereas it loads fine when importing during building the feedstock, as is the case when it is compiled locally).
This would confirm that the binary might simply not be signed at all.

All feedstocks that are based on setup.py calling CMake (and using pybind11) such as prescribed in this example fail with a singing error on conda build.
This is for example the case with
https://github.com/conda-forge/iminuit-feedstock/pull/58
that was already successfully build on OSX ARM before. Beyond this package there are many more affected, e.g.
https://github.com/conda-forge/goosefem-feedstock/pull/33
where, to debug I do pass CMAKE_ARGS to CMake (which is I think not the case for https://github.com/conda-forge/iminuit-feedstock/pull/58). cc: https://github.com/pybind/cmake_example/issues/52 @henrii

authors: conda-forge-linter isuruf tdegeus


text:
Patch libnetcdf pin

Ping @isuruf

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks @isuruf!

authors: conda-forge-linter ocefpaf


text:
Add new maintainer

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Adds @Tobias-Dwyer as a maintainer.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

authors: conda-forge-linter vyasr

repo: conda-forge/coxeter-feedstock


text:
add maintainer

@conda-forge-admin Can I be added as recipe maintainer? Current maintainers appear to be inactive.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter wietsedv

repo: conda-forge/datasets-feedstock


text:
Add Windows build

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [64, 65]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter ndevenish

repo: conda-forge/dials-feedstock


text:
Rerender

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

@conda-forge-admin, please rerender

Trying to let the bot rerender the feedstock. If this doesn't work, we would need to rerender manually.

repo: conda-forge/dictdiffer-feedstock


text:
Remove setuptools

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Fixes #43 to remove the new version of setuptools after building the package, to avoid packaging this setuptools into the package.
See https://github.com/conda-forge/artifact-validation/issues/897#issuecomment-1206485235

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@mattip let me see if I can add a fresh build of setuptools 57.4.0 instead. Hold on...

windows 3.7 cpython is failing to build the git-downloaded version of setuptools, claiming
ModuleNotFoundError: No module named '_distutils_hack'

I believe this is good to go now. Let's give it a try. Thanks @mattip!

Thanks, sorry for the additional work.

authors: conda-forge-linter mattip ocefpaf

repo: conda-forge/docutils-feedstock


text:
Don't include PyQt in requirements

It is only an optional dependency and we don't want to include it for e.g. glue-core or glue-jupyter

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

repo: conda-forge/echo-feedstock


text:
update to v1.2.2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

repo: conda-forge/eodms-api-client-feedstock


text:
Update frc

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: ExpectozJJ conda-forge-linter


text:
added testing of downstream packages annexremote and datalad

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

(continued from #98)
@yarikoptic when you have time, can you look at the causes of datalad test failures here?  there seem to be different failures with the standard and the standalone git-annex builds.

woohoo -- fetched 167MB log.  Largely due to the run of
python -c 'from annexremote import Master, SpecialRemote, RemoteError'

better be probably 2>&1 | tee -n 1000 or smth like that for that one.  I guess to be addressed at the annexremote feedstock level?
datalad failed only 1 test and very interestingly and I filed https://github.com/datalad/datalad/issues/4921  with more details:
2020-09-14T06:57:15.2915093Z ======================================================================
2020-09-14T06:57:15.2915566Z FAIL: datalad.tests.test_witless_runner.test_runner_parametrized_protocol
2020-09-14T06:57:15.2916282Z ----------------------------------------------------------------------
2020-09-14T06:57:15.2916765Z Traceback (most recent call last):
2020-09-14T06:57:15.2918077Z   File "/home/conda/feedstock_root/build_artifacts/git-annex_1600056447586/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.8/site-packages/nose/case.py", line 197, in runTest
2020-09-14T06:57:15.2919171Z     self.test(*self.arg)
2020-09-14T06:57:15.2920772Z   File "/home/conda/feedstock_root/build_artifacts/git-annex_1600056447586/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/lib/python3.8/site-packages/datalad/tests/test_witless_runner.py", line 149, in test_runner_parametrized_protocol
2020-09-14T06:57:15.2922014Z     eq_(res['stdout'], '5')
2020-09-14T06:57:15.2922684Z AssertionError: '55' != '5'

there is no easy way to provision skipping of a single test here, right?
PS I checked only a single build/run

"there is no easy way to provision skipping of a single test here, right?" -- to skip it here but still have it in datalad-feedstock, no; but if this failure is not important, maybe silence it in datalad-feedstock?

@yarikoptic the standard build got fixed.  the standalone one still has some (different?) errors.

I think all three failing tests are something we haven't seen before failing, filed https://github.com/datalad/datalad/issues/4933 and https://github.com/datalad/datalad/issues/4932 , we will try to look into them soonish than laterish

@yarikoptic I'm going to enable downstream testing of datalad just for the standard git-annex build for now.  Let me know when these other failures get fixed.   If you think these failures might reflect real issues, maybe for now change the git-annex dependency in datalad-feedstock to =*=alldep* to force installation of the standard version?  (Also, that dependency doesn't specify a minimal git-annex version -- maybe it should?)

I have not looked into the nature of those failures -- will try in a few days to make a decision either version restriction is indeed due or a quick bug fix is possible.  Limiting downstream testing for now sounds like a good plan, thank you @notestaff !

authors: conda-forge-linter notestaff yarikoptic

repo: conda-forge/git-annex-feedstock


text:
Release 2.11

Enhancements and new features:

* New export plugin: standard and configurable Restfull exporter (issue #1129)
* Add a JSON export module (issue #1130)
* [WIP] Refactoring of the WebUI

Bugs corrected:

* Installing GPU plugin crashes entire Glances (issue #1102)
* Potential memory leak in Windows WebUI (issue #1056)
* glances_network `OSError: [Errno 19] No such device` (issue #1106)
* GPU plugin. <class 'TypeError'>: ... not JSON serializable"> (issue #1112)
* PermissionError on macOS (issue #1120)
* Cant move up or down in glances --browser (issue #1113)
* Unable to give aliases to or hide network interfaces and disks (issue #1126)
* `UnicodeDecodeError` on mountpoints with non-breaking spaces (issue #1128)

Installation:

* Create a Snap of Glances (issue #1101)

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter jakirkham

repo: conda-forge/glances-feedstock


text:
kartothek v3.14.0

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

authors: conda-forge-linter fhoehle

repo: conda-forge/kartothek-feedstock


text:
@conda-forge-admin,please add bot automerge

Comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added bot automerge in conda-forge/kopf-feedstock#4.

authors: conda-forge-linter jacobtomlinson

repo: conda-forge/kopf-feedstock


text:
maxima doesn't need bdw-gc

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter isuruf

repo: conda-forge/maxima-feedstock


text:
[MERGE INTO RELEASE PR] revert astunparse pin

Checklist

[X] Used a personal fork of the feedstock to propose changes
[NA] Bumped the build number (if the version is unchanged)
[NA] Reset the build number to 0 (if the version changed)
[NA] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[NA] Ensured the license file is being packaged.

DO NOT MERGE THIS INTO MASTER
Merge this PR into the release PR whenever a release is done with https://github.com/mdtraj/mdtraj/pull/1635 (or repeat the change and close this PR).
This pin is not needed anymore if a release is made with https://github.com/mdtraj/mdtraj/pull/1635 in.
This is just a PR so that this is not forgotten.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Merge this PR into the release PR whenever a release is done with mdtraj/mdtraj#1635

:+1:

This PR was forgotten when #33 got merged, so this now needs to go into master (with an updated build number)

authors: conda-forge-linter rmcgibbo sroet

repo: conda-forge/mdtraj-feedstock


text:
MNT: rerender

Hi! This is the friendly automated conda-forge-webservice.
I've rerendered the recipe as instructed in #1.
Here's a checklist to do before merging.

[ ] Bump the build number if needed.

Fixes #1

@conda-forge-admin, please rerun ci

authors: conda-forge-linter timkpaine

repo: conda-forge/methodtools-feedstock


text:
@conda-forge-admin, please update circle

Not sure if this is this problem or not, but it might be?

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I updated the circle-ci deploy key and followed the project.

authors: conda-forge-linter dougalsutherland

repo: conda-forge/onnx-feedstock


text:
pin matplotlib-base <3.9

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

this needs a re-render and a build number bump, I will do it :mechanical_arm:

authors: IAlibay mikemhenry

repo: conda-forge/openfe-feedstock


text:
Build 1.0 beta

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

For the moment I switched back to a noarch build and removed NNPOps as a dependency, since that looks like the quickest path to getting the beta out.  We need to find a better solution within the next couple of weeks, so we can handle it properly in the release candidate.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

It's not getting the dependencies:
Mamba failed to solve:
 - pip
 - openmm 8.0.0beta
 - python >=3.6
 - numpy
 - openmm-torch 1.0beta

with channels:

The reported errors are:
- Encountered problems while solving:
-   - nothing provides requested openmm 8.0.0beta
-   - nothing provides requested openmm-torch 1.0beta

I tried specifying the channels both as
channel_sources:
- conda-forge/label/openmm_rc,conda-forge/label/openmm-torch_rc,conda-forge

and as
channel_sources:
- conda-forge/label/openmm_rc
- conda-forge/label/openmm-torch_rc
- conda-forge

but neither one works.  What am I doing wrong?

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The requirements/ sections should be defined in the following order: build, host, run; instead saw: host, build, run.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter peastman

repo: conda-forge/openmm-ml-feedstock


text:
2.6.0.6

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

repo: conda-forge/pandoctools-feedstock


text:
switch to grayskull update

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


text:
Update 0.4.2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Reset the build number to 0 (if the version changed)
[x Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

@conda-forge-admin please rerender

repo: conda-forge/pyinterpolate-feedstock


text:
Requesting an update to Python 3.6

This is the most commonly used conda for grabbing PyKalman.  Just a quick request for a rebuild including 3.6 as I'm not sufficiently knowledgeable to do it myself.

The noarch package is now available. Going to close this out as resolved.

thanks

authors: jakirkham rhaskett

repo: conda-forge/pykalman-feedstock


text:
R3.5

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: cbrueffer conda-forge-linter

repo: conda-forge/r-brobdingnag-feedstock


text:
Update to version 0.2-0, update recipe

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter dbast

repo: conda-forge/r-nlp-feedstock


text:
Enable more platforms, add missing license

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

repo: conda-forge/r-timechange-feedstock


text:
WIP: Add pmdarima to sktime-all-extras

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi @freddyaboulton 👋
The helpful folks over on conda-forge gitter pointed out the fact that I have been using pin_compatible incorrectly.
The usage of {{ pin_compatible('numpy') }} should remain the same - it's the host pinning which is incorrect here. In the host section the pin should be 1.19.* instead of >=1.19

https://conda-forge.org/docs/maintainer/knowledge_base.html#building-against-numpy

@dhirschfeld Thanks for following up with the folks on the gitter channel. I implemented your suggestion!

@dhirschfeld Uh-oh, looks like the build is failing again! sktime is being built with 1.21.1 again. Look at the CI log

Thanks for following up with the folks on the gitter channel

Not a problem - I thought something wasn't quite right. I think it's the >= in the host which short-circuits the pin_compatible handling so just 1.19.* should work... IIUC.

Uh-oh, looks like the build is failing again! I think sktime is being built with 1.21.1 again?

I'm trying without >= now as you suggested. I misread that.

@dhirschfeld Thanks again for the feedback! The builds are all green now. Weird that the run constraint for numpy cannot have >= ! Glad we were able to figure it out.

repo: conda-forge/sktime-feedstock