Build failing with Error since we upgraded WpgraphQl, WpGatsby and Gatsby-wordpress-experimental

We are getting a weird error since we upgraded WpgraphQl, WpGatsby and Gatsby-woordpress-experimental.
Error :
Failed to validate error Error [ValidationError]: "config" is not allowed. "request" is not allowed. "response" is not allowed. "isAxiosError" is not allowed. "toJSON" is not allowed
    at Object.exports.process (D:\Gatsby\Obs-Git\OBSBeta\node_modules\@hapi\joi\lib\errors.js:202:19)
    at internals.Object._validateWithOptions (D:\Gatsby\Obs-Git\OBSBeta\node_modules\@hapi\joi\lib\types\any\index.js:763:31)
    at internals.Object.validate (D:\Gatsby\Obs-Git\OBSBeta\node_modules\@hapi\joi\lib\types\any\index.js:797:21)
    at constructError (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby\node_modules\gatsby-cli\lib\structured-errors\construct-error.js:52:32)
    at Reporter.error (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby\node_modules\gatsby-cli\lib\reporter\reporter.js:135:59)
    at Object.error (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby\src\utils\api-runner-node.js:190:16)
    at handleFetchErrors (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby-source-wordpress-experimental\src\utils\fetch-graphql.js:236:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at fetchGraphql (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby-source-wordpress-experimental\src\utils\fetch-graphql.js:539:5)
    at paginatedWpNodeFetch (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby-source-wordpress-experimental\src\steps\source-nodes\fetch-nodes\fetch-nodes-paginated.js:59:20)
    at fetchWPGQLContentNodes (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby-source-wordpress-experimental\src\steps\source-nodes\fetch-nodes\fetch-nodes.js:44:26)
    at D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby-source-wordpress-experimental\src\steps\source-nodes\fetch-nodes\fetch-nodes.js:149:30
    at D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby-source-wordpress-experimental\src\steps\source-nodes\fetch-nodes\fetch-nodes.js:139:9
    at async Promise.all (index 6)
    at runFnForEachNodeQuery (D:\Gatsby\Obs-Git\OBSBeta\node_modules\gatsby-source-wordpress-experimental\src\steps\source-nodes\fetch-nodes\fetch-nodes.js:127:5) {
  isJoi: true,
  name: 'ValidationError',
  details: [
    {
      message: '"config" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"request" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"response" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"isAxiosError" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"toJSON" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    }
  ],
  _object: {
    context: {},
    config: {
      url: 'https://backend.observalgerie.com/graphql',
      method: 'post',
      data: '{"query":" query NODE_LIST_QUERY($first:Int!,$after:String,){villesEtLieux(first:$first,after:$after,){nodes{ancestors(first:100){nodes{id}}wpChildren:children(first:100){nodes{id}}contentNodes(first:100){nodes{id __typename}}count databaseId description id link name wpParent:parent{node{id}}parentDatabaseId parentId posts(first:100){nodes{id}}seo{breadcrumbs{text url}canonical cornerstone focuskw metaDesc metaKeywords metaRobotsNofollow metaRobotsNoindex opengraphAuthor opengraphDescription opengraphImage{__typename id}opengraphModifiedTime opengraphPublishedTime opengraphPublisher opengraphSiteName opengraphTitle opengraphType opengraphUrl title twitterDescription twitterImage{__typename id}twitterTitle}slug taxonomy{node{id}}termGroupId termTaxonomyId uri __typename}pageInfo{hasNextPage endCursor}}}","variables":{"first":100,"url":"https://backend.observalgerie.com/graphql","after":null}}',
      headers: [Object],
      auth: [Object],
      transformRequest: [Array],
      transformResponse: [Array],
      timeout: 30000,
      adapter: [Function: httpAdapter],
      xsrfCookieName: 'XSRF-TOKEN',
      xsrfHeaderName: 'X-XSRF-TOKEN',
      maxContentLength: -1,
      validateStatus: [Function: validateStatus]
    },
    code: 'ECONNABORTED',
    request: Writable {
      _writableState: [WritableState],
      writable: true,
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      _options: [Object],
      _redirectCount: 0,
      _redirects: [],
      _requestBodyLength: 904,
      _requestBodyBuffers: [Array],
      _onNativeResponse: [Function],
      _currentRequest: [ClientRequest],
      _currentUrl<EMAIL_ADDRESS>      [Symbol(kCapture)]: false
    },
    response: undefined,
    isAxiosError: true,
    toJSON: [Function],
    pluginName: 'gatsby-source-wordpress-experimental',
    text: 'There was an error',
    level: 'ERROR',
    stack: [],
    docsUrl: 'https://gatsby.dev/issue-how-to'
  },
  annotate: [Function]
}

Package.json
{
  "name": "obs-beta",
  "private": true,
  "description": "An Obs Beta version with Gatsby & WordPress",
  "version": "0.1.0",
  "author": "Khaled Belkouche<EMAIL_ADDRESS>  "dependencies": {
    "@apollo/client": "^3.2.7",
    "@hot-loader/react-dom": "^17.0.0",
    "@material-ui/core": "^4.11.0",
    "@material-ui/icons": "^4.9.1",
    "@sideway/address": "^4.1.0",
    "babel-plugin-styled-components": "^1.11.1",
    "core-js": "^3.7.0",
    "gatsby": "^2.26.1",
    "gatsby-image": "^2.5.0",
    "gatsby-plugin-manifest": "^2.6.1",
    "gatsby-plugin-material-ui": "^2.1.10",
    "gatsby-plugin-offline": "^3.4.0",
    "gatsby-plugin-react-helmet": "^3.4.0",
    "gatsby-plugin-sharp": "^2.8.0",
    "gatsby-plugin-styled-components": "^3.4.0",
    "gatsby-source-filesystem": "^2.5.0",
    "gatsby-source-graphql": "^2.8.0",
    "gatsby-source-wordpress": "^3.5.0",
    "gatsby-source-wordpress-experimental": "^3.0.1",
    "gatsby-transformer-sharp": "^2.6.0",
    "graphql-tag": "^2.11.0",
    "html-react-parser": "^0.14.1",
    "isomorphic-fetch": "^3.0.0",
    "joi": "^17.3.0",
    "prop-types": "^15.7.2",
    "react": "^17.0.1",
    "react-helmet": "^6.1.0",
    "react-waypoint": "^9.0.3",
    "styled-components": "^5.2.1"
  },
  "devDependencies": {
    "prettier": "2.1.2"
  },
  "keywords": [
    "gatsby"
  ],
  "license": "0BSD",
  "scripts": {
    "build": "gatsby build",
    "develop": "gatsby develop",
    "format": "prettier --write \"**/*.{js,jsx,ts,tsx,json,md}\"",
    "start": "npm run develop",
    "serve": "gatsby serve",
    "clean": "gatsby clean",
    "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\" && exit 1"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/kabylebot/obsbeta"
  },
  "bugs": {
    "url": "https://github.com/kabylebot/obsbeta/issues"
  }
}

Config.js:
module.exports = {
  plugins: [
    `gatsby-plugin-react-helmet`,
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        name: `images`,
        path: `${__dirname}/src/images`,
      },
    },
    {
      resolve: `gatsby-plugin-material-ui`,
      options: {
        stylesProvider: {
          injectFirst: true,
        },
      },
    },
    `gatsby-plugin-styled-components`,
    `gatsby-transformer-sharp`,
    `gatsby-plugin-sharp`,
    {
      resolve: `gatsby-plugin-manifest`,
      options: {
        name: `OBS Algérie Version Beta`,
        short_name: `OBS`,
        start_url: `/`,
        background_color: `#00de85`,
        theme_color: `#33cc33`,
        display: `minimal-ui`,
        icon: `src/images/Logo-OBS.png`, // This path is relative to the root of the site.
      },
    },
    {
      resolve: `gatsby-source-wordpress-experimental`,
      options: {
        fieldName: "wpcontent",
        url:
          // allows a fallback url if WPGRAPHQL_URL is not set in the env, this may be a local or remote WP instance.
          process.env.WPGRAPHQL_URL ||
          `https://backend.observalgerie.com/graphql`,
        schema: {
          //Prefixes all WP Types with "Wp" so "Post and allPost" become "WpPost and allWpPost".
          typePrefix: `Wp`,
        },
        develop: {
          //caches media files outside of Gatsby's default cache an thus allows them to persist through a cache reset.
          hardCacheMediaFiles: false,
        },
        type: {
          Post: {
            limit:
              process.env.NODE_ENV === `development`
                ? // Lets just pull 50 posts in development to make it easy on ourselves (aka. faster).
                  100
                : // and we don't actually need more than 5000 in production for this particular site
                  10000,
          },
        },
        html: {
          useGatsbyImage: true,
          fallbackImageMaxWidth: 800,
          withWebp: true,
        },
      },
    },
  ],
}

In Wordpress Backend we are using : Wpgraphql, WpGatsby, Yoast SEO, Pods – Custom Content Types and Fields, Cloudinary

I'm getting the same error intermittently.
Failed to validate error Error [ValidationError]: "config" is not allowed. "request" is not allowed. "response" is not allowed. "isAxiosError" is not allowed. "toJSON" is not allowed
    at Object.exports.process (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/@hapi/joi/lib/errors.js:202:19)
    at internals.Object._validateWithOptions (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/@hapi/joi/lib/types/any/index.js:763:31)
    at internals.Object.validate (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/@hapi/joi/lib/types/any/index.js:797:21)
    at constructError (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-cli/lib/structured-errors/construct-error.js:52:32)
    at Reporter.error (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-cli/lib/reporter/reporter.js:135:59)
    at Object.error (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby/src/utils/api-runner-node.js:190:16)
    at handleFetchErrors (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-source-wordpress-experimental/src/utils/fetch-graphql.js:236:14)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at fetchGraphql (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-source-wordpress-experimental/src/utils/fetch-graphql.js:539:5)
    at paginatedWpNodeFetch (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js:59:20)
    at fetchWPGQLContentNodes (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:44:26)
    at /mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:149:30
    at /mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:139:9
    at async Promise.all (index 6)
    at runFnForEachNodeQuery (/mnt/c/Users/Alex/code/moonmeister/moonmeister.net/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:127:5) {
  isJoi: true,
  details: [
    {
      message: '"config" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"request" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"response" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"isAxiosError" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"toJSON" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    }
  ],
  _object: {
    context: {},
    config: {
      url: 'https://cms.moonmeister.net/graphql',
      method: 'post',
      data: '{"query":" query NODE_LIST_QUERY($first:Int!,$after:String,){menus(first:$first,after:$after,){nodes{count databaseId id locations menuItems(first:100){nodes{id}}name slug __typename}pageInfo{hasNextPage endCursor}}}","variables":{"first":100,"url":"https://cms.moonmeister.net/graphql","after":null}}',
      headers: [Object],
      transformRequest: [Array],
      transformResponse: [Array],
      timeout: 30000,
      adapter: [Function: httpAdapter],
      xsrfCookieName: 'XSRF-TOKEN',
      xsrfHeaderName: 'X-XSRF-TOKEN',
      maxContentLength: -1,
      validateStatus: [Function: validateStatus]
    },
    code: 'ECONNABORTED',
    request: Writable {
      _writableState: [WritableState],
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      _options: [Object],
      _redirectCount: 0,
      _redirects: [],
      _requestBodyLength: 301,
      _requestBodyBuffers: [Array],
      _onNativeResponse: [Function (anonymous)],
      _currentRequest: [ClientRequest],
      _currentUrl: 'https://cms.moonmeister.net/graphql',
      [Symbol(kCapture)]: false
    },
    response: undefined,
    isAxiosError: true,
    toJSON: [Function (anonymous)],
    pluginName: 'gatsby-source-wordpress-experimental',
    text: 'There was an error',
    level: 'ERROR',
    stack: [],
    docsUrl: 'https://gatsby.dev/issue-how-to'
  },
  annotate: [Function (anonymous)]
}```

This is really odd 🤔 we recently added support for the pluginOptionsSchema node API that was recently added to Gatsby but that shouldn't be affecting axios.. Are either of you able to share a reproduction /graphql url and repo so I can reproduce and debug? I haven't run into this myself, weirdly.
Thanks!

Tyler I believe you can still login to my WordPress site : https://cms.moonmeister.net/wp-admin
Code is on my github.com/moonmeister/moonmeister.net

Ah, of course. Thanks Alex!

Can you run gatsby info? I wonder if this is somehow related to being on a version of gatsby that doesn't have the pluginOptionsSchema API. That'd be weird but it'd be good to rule it out.

No matter how many times I run a build of your site I don't get that error 😱 gatsby info is definitely needed here so I can make sure my setup is as close to yours as possible.

  System:
    OS: Linux 4.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 14.15.0 - ~/.nvm/versions/node/v14.15.0/bin/node
    Yarn: 1.22.10 - /mnt/c/Users/Alex/AppData/Roaming/npm/yarn
    npm: 6.14.8 - ~/.nvm/versions/node/v14.15.0/bin/npm
  npmPackages:
    gatsby: ^2.26.1 => 2.26.1
    gatsby-image: ^2.5.0 => 2.5.0
    gatsby-plugin-feed: ^2.7.0 => 2.7.0
    gatsby-plugin-goatcounter: ^0.4.0 => 0.4.0
    gatsby-plugin-linaria: ^2.2.0 => 2.2.0
    gatsby-plugin-manifest: ^2.6.1 => 2.6.0-next.0
    gatsby-plugin-netlify: ^2.5.0 => 2.5.0
    gatsby-plugin-offline: ^3.4.0 => 3.4.0
    gatsby-plugin-postcss: ^3.1.0 => 3.1.0
    gatsby-plugin-preact: ^4.1.0 => 4.1.0
    gatsby-plugin-react-helmet: ^3.4.0 => 3.4.0
    gatsby-plugin-readingtime: ^1.0.1 => 1.0.1
    gatsby-plugin-robots-txt: ^1.5.3 => 1.5.3
    gatsby-plugin-sharp: ^2.8.0 => 2.8.0
    gatsby-plugin-sitemap: ^2.6.0 => 2.6.0
    gatsby-plugin-webpack-bundle-analyzer: ^1.0.5 => 1.0.5
    gatsby-plugin-webpack-size: ^1.0.0 => 1.0.0
    gatsby-source-filesystem: ^2.5.0 => 2.5.0
    gatsby-source-wordpress-experimental: ^3.0.1 => 3.0.1
    gatsby-transformer-sharp: ^2.6.0 => 2.6.0

Thanks Alex! And I was able to reproduce with your /graphql url @KabyleBOT . Investigating now

I've only gotten this error twice and run build a dozen or more times FYI. but also notice code: ECONNABORTED I think this is some kind of tcp issue causes the error then Joi tries to validate it somehow...

I think it's because I'm passing an error object into reporter.error() which it seems now has Joi validation and doesn't allow that anymore 🤔 I'm trying to just pass the error message there instead now which I assume will fix it.

Yep, this is due to timeouts. A more detailed error is printed out on the next line but because Joi was throwing a validation error for reporter.error() it never got to that point.

Makes sense, I'm on a slow connection.

This is fixed in<EMAIL_ADDRESS>Thanks so much for reporting this and for helping me reproduce it!

Thank you very much. I will try that. And let you know :)

Its Working 👍 Thanks

Hi @TylerBarnes,
I still have an issue in version 3.0.3 that I think is related to this.
Failed to validate error Error [ValidationError]: "name" is not allowed
    at Object.exports.process (/Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/@hapi/joi/lib/errors.js:202:19)
    at internals.Object._validateWithOptions (/Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/@hapi/joi/lib/types/any/index.js:763:31)
    at internals.Object.validate (/Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/@hapi/joi/lib/types/any/index.js:797:21)
    at constructError (/Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/gatsby-cli/lib/structured-errors/construct-error.js:52:32)
    at Reporter.error (/Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/gatsby-cli/lib/reporter/reporter.js:135:59)
    at Reporter.panic (/Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/gatsby-cli/lib/reporter/reporter.js:75:34)
    at Object.panic (/Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/gatsby/src/utils/api-runner-node.js:201:16)
    at /Users/Kreppar/Content Pilot/Clients/fbp/frontend/node_modules/gatsby-plugin-sharp/index.js:162:14
    at processTicksAndRejections (node:internal/process/task_queues:93:5) {
  isJoi: true,
  details: [
    {
      message: '"name" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    }
  ],
  _object: {
    context: {},
    name: 'WorkerError',
    pluginName: 'gatsby-source-wordpress-experimental',
    text: 'There was an error',
    level: 'ERROR',
    stack: [],
    docsUrl: 'https://gatsby.dev/issue-how-to'
  },
  annotate: [Function (anonymous)]
}

gatsby info:
 Binaries:
    Node: 15.2.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.0.10 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 87.0.4280.66
    Edge: 86.0.622.69
    Safari: 14.0.1
  npmPackages:
    gatsby: ^2.26.1 => 2.26.1
    gatsby-awesome-pagination: ^0.3.6 => 0.3.6
    gatsby-image: ^2.4.21 => 2.6.0
    gatsby-plugin-antd: ^2.2.0 => 2.2.0
    gatsby-plugin-gdpr-cookies: ^1.0.10 => 1.0.10
    gatsby-plugin-hotjar: ^1.1.1 => 1.1.1
    gatsby-plugin-layout: ^1.3.13 => 1.5.0
    gatsby-plugin-less: ^4.0.6 => 4.2.0
    gatsby-plugin-manifest: ^2.4.35 => 2.7.0
    gatsby-plugin-netlify: ^2.5.0 => 2.6.0
    gatsby-plugin-nprogress: ^2.3.13 => 2.5.0
    gatsby-plugin-purgecss: ^5.0.0 => 5.0.0
    gatsby-plugin-remove-serviceworker: ^1.0.0 => 1.0.0
    gatsby-plugin-robots-txt: ^1.5.3 => 1.5.3
    gatsby-plugin-root-import: ^2.0.5 => 2.0.5
    gatsby-plugin-sass: ^2.3.17 => 2.6.0
    gatsby-plugin-sharp: ^2.6.42 => 2.9.0
    gatsby-plugin-sitemap: ^2.4.17 => 2.7.0
    gatsby-plugin-typography: ^2.5.13 => 2.7.0
    gatsby-plugin-web-font-loader: ^1.0.4 => 1.0.4
    gatsby-source-filesystem: ^2.3.35 => 2.6.0
    gatsby-source-wordpress-experimental: ^3.1.3 => 3.1.3
    gatsby-theme-wordpress-gutenberg: ^0.1.0 => 0.1.0
    gatsby-transformer-sharp: ^2.7.0 => 2.7.0
  npmGlobalPackages:
    gatsby-cli: 2.12.112

Hi @TylerBarnes, I am getting the same Joi error in version 5.0.1.  Let me know if you need any details.
success open and validate gatsby-configs - 0.017s
success load plugins - 0.619s
success onPreInit - 0.028s
success initialize cache - 0.010s
success copy gatsby files - 0.021s
success onPreBootstrap - 0.011s
success  gatsby-source-wordpress  ensuring plugin requirements are met - 3.186s

info  gatsby-source-wordpress

	This is either your first build or the cache was cleared.
	Please wait while your WordPress data is synced to your Gatsby cache.

	Maybe now's a good time to get up and stretch? :D

success  gatsby-source-wordpress  ingest WPGraphQL schema - 11.933s
success createSchemaCustomization - 15.148s
success  gatsby-source-wordpress  PostFormat - 1.627s - fetched 3
success  gatsby-source-wordpress  UserRole - 1.654s - fetched 0
success  gatsby-source-wordpress  Menu - 1.665s - fetched 1
success  gatsby-source-wordpress  Taxonomy - 2.241s - fetched 3
success  gatsby-source-wordpress  MenuItem - 2.486s - fetched 10
success  gatsby-source-wordpress  fetch root fields - 3.185s
success  gatsby-source-wordpress  ContentType - 3.257s - fetched 3
Failed to validate error Error [ValidationError]: "config" is not allowed. "request" is not allowed. "response" is not allowed. "isAxiosError" is not allowed. "toJSON" is not allowed
    at Object.exports.process (/home/akshay/pocWP/node_modules/@hapi/joi/lib/errors.js:202:19)
    at internals.Object._validateWithOptions (/home/akshay/pocWP/node_modules/@hapi/joi/lib/types/any/index.js:763:31)
    at internals.Object.validate (/home/akshay/pocWP/node_modules/@hapi/joi/lib/types/any/index.js:797:21)
    at constructError (/home/akshay/pocWP/node_modules/gatsby/node_modules/gatsby-cli/lib/structured-errors/construct-error.js:52:32)
    at Reporter.error (/home/akshay/pocWP/node_modules/gatsby/node_modules/gatsby-cli/lib/reporter/reporter.js:135:59)
    at Object.error (/home/akshay/pocWP/node_modules/gatsby/src/utils/api-runner-node.js:190:16)
    at handleFetchErrors (/home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/utils/fetch-graphql.js:259:14)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at fetchGraphql (/home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/utils/fetch-graphql.js:582:5)
    at paginatedWpNodeFetch (/home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes-paginated.js:59:20)
    at fetchWPGQLContentNodes (/home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:44:26)
    at /home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:149:30
    at /home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:139:9
    at async Promise.all (index 12)
    at runFnForEachNodeQuery (/home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:127:5)
    at fetchWPGQLContentNodesByContentType (/home/akshay/pocWP/node_modules/gatsby-source-wordpress-experimental/src/steps/source-nodes/fetch-nodes/fetch-nodes.js:148:3) {
  isJoi: true,
  details: [
    {
      message: '"config" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"request" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"response" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"isAxiosError" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    },
    {
      message: '"toJSON" is not allowed',
      path: [Array],
      type: 'object.allowUnknown',
      context: [Object]
    }
  ],
  _object: {
    context: {},
    config: {
      url: 'https://hindi.karnival.tech/graphql',
      method: 'post',
      data: '{"query":" query NODE_LIST_QUERY($first:Int!,$after:String,){users(first:$first,after:$after,){nodes{avatar{default extraAttr forceDefault foundAvatar height rating scheme size url width}capKey capabilities comments(first:100){nodes{id}}databaseId description email extraCapabilities firstName id lastName locale name nicename nickname pages(first:100){nodes{id}}posts(first:100){nodes{id}}registeredDate roles(first:100){nodes{id}}slug uri url username __typename}pageInfo{hasNextPage endCursor}}}","variables":{"first":100,"url":"https://hindi.karnival.tech/graphql","after":null}}',
      headers: [Object],
      transformRequest: [Array],
      transformResponse: [Array],
      timeout: 30000,
      adapter: [Function: httpAdapter],
      xsrfCookieName: 'XSRF-TOKEN',
      xsrfHeaderName: 'X-XSRF-TOKEN',
      maxContentLength: -1,
      validateStatus: [Function: validateStatus]
    },
    request: ClientRequest {
      _events: [Object: null prototype],
      _eventsCount: 6,
      _maxListeners: undefined,
      outputData: [],
      outputSize: 0,
      writable: true,
      _last: true,
      chunkedEncoding: false,
      shouldKeepAlive: false,
      useChunkedEncodingByDefault: true,
      sendDate: false,
      _removedConnection: false,
      _removedContLen: false,
      _removedTE: false,
      _contentLength: null,
      _hasBody: true,
      _trailer: '',
      finished: true,
      _headerSent: true,
      socket: [TLSSocket],
      connection: [TLSSocket],
      _header: 'POST /graphql HTTP/1.1\r\n' +
        'Accept: application/json, text/plain, */*\r\n' +
        'Content-Type: application/json;charset=utf-8\r\n' +
        'User-Agent: axios/0.19.2\r\n' +
        'Content-Length: 583\r\n' +
        'Host: hindi.karnival.tech\r\n' +
        'Connection: close\r\n' +
        '\r\n',
      _onPendingData: [Function: noopPendingOutput],
      agent: [Agent],
      socketPath: undefined,
      method: 'POST',
      insecureHTTPParser: undefined,
      path: '/graphql',
      _ended: true,
      res: [IncomingMessage],
      aborted: false,
      timeoutCb: [Function: emitRequestTimeout],
      upgradeOrConnect: false,
      parser: null,
      maxHeadersCount: null,
      reusedSocket: false,
      _redirectable: [Writable],
      [Symbol(kCapture)]: false,
      [Symbol(kNeedDrain)]: false,
      [Symbol(corked)]: 0,
      [Symbol(kOutHeaders)]: [Object: null prototype]
    },
    response: {
      status: 500,
      statusText: 'Internal Server Error',
      headers: [Object],
      config: [Object],
      request: [ClientRequest],
      data: [Object]
    },
    isAxiosError: true,
    toJSON: [Function],
    pluginName: 'gatsby-source-wordpress-experimental',
    text: 'There was an error',
    level: 'ERROR',
    stack: [],
    docsUrl: 'https://gatsby.dev/issue-how-to'
  },
  annotate: [Function]
}
not finished source and transform nodes - 3.838s
not finished  gatsby-source-wordpress  fetching nodes - 3.800s - 20 total
not finished  gatsby-source-wordpress  Category - 3.800s
not finished  gatsby-source-wordpress  Comment - 3.799s
not finished  gatsby-source-wordpress  Page - 3.797s
not finished  gatsby-source-wordpress  Post - 3.797s
not finished  gatsby-source-wordpress  Tag - 3.797s
not finished  gatsby-source-wordpress  User - 3.797s

Gatsby info details:
System:
    OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 12.18.0 - ~/.nvm/versions/node/v12.18.0/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.7 - ~/.nvm/versions/node/v12.18.0/bin/npm
  Languages:
    Python: 2.7.18 - /usr/bin/python
  Browsers:
    Chrome: 87.0.4280.88
    Firefox: 83.0
  npmPackages:
    gatsby: ^2.26.1 => 2.26.1
    gatsby-image: ^2.5.0 => 2.5.0
    gatsby-plugin-manifest: ^2.6.1 => 2.6.1
    gatsby-plugin-offline: ^3.4.0 => 3.4.0
    gatsby-plugin-react-helmet: ^3.4.0 => 3.4.0
    gatsby-plugin-sharp: ^2.8.0 => 2.8.0
    gatsby-source-filesystem: ^2.5.0 => 2.5.0
    gatsby-source-wordpress-experimental: ^5.0.1 => 5.0.1
    gatsby-transformer-sharp: ^2.6.0 => 2.6.0
  npmGlobalPackages:
    gatsby-cli: 2.15.1
    gatsby: 2.27.3


Greetings from CONTROLLINO!

Hi Jan,
great job! 🥇
Please note that CONTROLLINO web pages are https://controllino.biz/
May I ask you to update your readme accordingly, please?
Thanks,
Best regards,
Lukas from CONTROLLINO team

Hi,
thanks for the heads-up. I've updated the link.
Note: I'll be changing this project soon so that it can connect with the
home-assistant gateway (https://home-assistant.io/) for better
compatibility and interoperability with other systems.
Cheers,
Jan.
------ Original Message ------
From: "Controllino"<EMAIL_ADDRESS>To: "ATT-JBO/controllino_lights_control"
<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Sent: 7/03/2017 15:07:15
Subject: [ATT-JBO/controllino_lights_control] Greetings from
CONTROLLINO! (#1)

Hi Jan,
great job! 🥇
Please note that CONTROLLINO web pages are https://controllino.biz/
May I ask you to update your readme accordingly, please?
Thanks,
Best regards,
Lukas from CONTROLLINO team
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ATT-JBO/controllino_lights_control/issues/1, or
mute the thread
https://github.com/notifications/unsubscribe-auth/AHP_tdjMk9HDD2LJ4Gl8n1Kacn2br7duks5rjWSTgaJpZM4MVhcA.


Old version of kubectl 1.15, latest stable is 1.19.1

Summary
The Dockerfile for argo is pulling in 1.15 of kubectl. Given the comment in the Dockerfile, I expected this to be 1.19.1 or at least 1.18.8.
The Kubernetes project maintains release branches for the most recent three minor releases (1.19, 1.18, 1.17).
Kubernetes 1.19 and newer receive approximately 1 year of patch support.
Kubernetes 1.18 and older received approximately 9 months of patch support.
kubectl is supported within one minor version (older or newer) of kube-apiserver.
Example: kube-apiserver is at 1.18, then kubectl is supported at 1.19, 1.18, and 1.17
Given the above, argo should likely remain on one minor less (1.18) than the current stable (1.19). This allows support for all three active releases of k8s.
Diagnostics
I reviewed the master branch and latest release branch of argo.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

It would be good to upgrade this dependency. Would you like to submit a PR with the fix?


Move format_message() from Integreat CMS into chatanswers app

The Integreat CMS API app contains a format_message() function. This was necessary in the beginning because we did not have the title present in the Chat back end. Now we do. We should therefore be able to move the functionality into

Done with #108


Fix TypeError: Vue is not a constructor

This pull-request fixes TypeError: Vue is not a constructor.
Issue
Rison Playground is not working.

In JavaScript console, Uncaught TypeError: Vue is not a constructor.
Mustache tags like {{ rison_string }} are displayed without replacement. #2
Buttons don't work.

Cause

Rison Playground expects Vue2 but CDN returns Vue3.

Change

Specify Vue version in CDN URL.

Alternative Change: Use Vue3
https://github.com/othree/rison.dev/compare/master...deton:rison.dev:vue3?expand=1

Thank you!


How to do server side validation of values?

Hi,
thanks for providing this library and keeping it updated even after 8 years!
One question I have is about data security and avoiding tampering. If a bad actor really wants to mess with my site, they can modify the schema on client side and submit invalid data.
How would I validate the data again the schema on the server side in NodeJS? Can this be done with deps/opt/jsv.js or would I use another library like ajv or dormant jsv?
Thanks,
bluepuma

Hi @bluepuma77
You can use any library you like but ajv seems more up to date so I would rather go along with that

ajv seems not to be 100% compatible with the JSON format :-/
"schema is invalid: data/properties/name/required should be array"
Is there a way to run jsonform on the server side with the JSON schema and data?

ajv seems not to be 100% compatible with the JSON format :-/
"schema is invalid: data/properties/name/required should be array"
Is there a way to run jsonform on the server side with the JSON schema and data?

Arf. I haven't tested server-side, but I guess there are going to be several problems because it's expecting to be in a browser and have access to window.

Arf. I haven't tested server-side, but I guess there are going to be several problems because it's expecting to be in a browser and have access to window.

In 2014 Fabian looked at validation in JSON Form. I looked into the code again, the whole validation part is done by JSONFormValidator from file jsv.js. I tested it and the validation part can be used easily on the server-side in NodeJS:
const jsv = require('../../static/js/jsv'); # adapt your local path
let validator = jsv.JSONFormValidator.createEnvironment("json-schema-draft-03");

let values = JSON.parse(req.body.json);
let schema = { properties: full_jsonform_definition.schema };
let v = validator.validate(values, schema);
console.log(v.errors)

Example result:
[
  {
    uri: 'urn:uuid:ed8924e5-df71-4b9e-9240-e972d528c023#/zip',
    schemaUri: 'urn:uuid:782a6bc6-29b4-49b5-a2fa-7ed6261f61c3#/properties/zip',
    attribute: 'type',
    message: 'Instance is not a required type',
    details: [ 'integer' ]
  },
  {
    uri: 'urn:uuid:ed8924e5-df71-4b9e-9240-e972d528c023#/zip',
    schemaUri: 'urn:uuid:782a6bc6-29b4-49b5-a2fa-7ed6261f61c3#/properties/zip',
    attribute: 'maxLength',
    message: 'String is greater then the required maximum length',
    details: 5
  }
]

An interesting next step would be to transform the submitted values from String into the right type (e.g. integer, date).


[data-import] Importing large text

When importing large text fields, only about 215 chars are imported. How do I import all the text from Excel into my Rich Text field?
Best regards,
Thomas...

I don't reproduce this behaviour with textarea or richtext , the test i've made contains 750 characters.

Can you provide more info such as the text (it may contains some special characters)  and screenshots ?

Hi
Thank you for the quick answer. You where right. The text included "<<" which the import didn't like. This is fully inderstandable for a RichText / HTML field :-)
Thank you again, really appreciate this!
Thomas...


Exclude files that are from scratch

I've aliased Sublime Text as my editor for terminal stuff, so when I create a commit, it's opened in Sublime Text for me to write the commit message. This works great, except CodeFormatter throws an error when it opens, "File is From Scratch".
Is there any way to disable that error/notification in these sort of circumstances?

Hi @tconroy, Can you list steps to reproduce your issue ?

Creating an alias Sublime Text as my editor for terminal stuff, so when you create a commit.

After re-prodcing your issue, I might be able to resolve it faster.
Thanks,
Priyank

Removing these lines from the source code and trying to format a scratch file doesn't seems to cause any problems.
Any info on this @akalongman ?

Hi @priyankt68,
sorry for taking awhile to get back to you. Here are steps to reproduce:

set Sublime as your primary editor for Git via the following guide: https://help.github.com/articles/associating-text-editors-with-git/#using-sublime-text-as-your-editor

$ git config --global core.editor "subl -n -w"

modify an existing git repository and commit your changes:

git add .
git commit

( this should open sublime for you to write the commit message. )

hit save (I'm on mac so cmd + s). The error from these lines of the plugin will be thrown.

The save / commit are successful, however the error is really annoying and ruins my workflow ( I have a dedicated virtual desktop for my terminal and the error message causes the active desktop to fling back to my editor ).
 I am facing the same message and it is annoying.

hi @Kreativschnittstelle -- sorry, no progress from me. I have long since switched from Sublime to other editors. Hope you can figure out a fix!


ID 2820: Add syntax highlights

Add here your WMS ID
2820
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[x] All filenames are lower case (including folders, images, files, etc.)
[x] Filenames are descriptive
[x] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[x] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[x] Image references in markdown contain an alternate text

@aberinnj I have updated all OCI console screenshots. Thank you for your review!


Fixed id being passed to patternfly_tab_xxx methods.

patternfly_tab_xxx methods expect id and sb[:active_tab] to be the same to display tab as an active tab. In this case there is only a single tab on the screen so have to make sure both values match.
Issue #3309
@mkanoor @dclarizio please review/test.

@mkanoor please retest, fixed another reported issue in class schema sequence change form that was caused by jquery to patternfly tabs conversion work.

@h-kataria
tested the PR for the Class Edit Screen and ordering the fields. Looks good


add indexes to timestamped models

ref: django-extensions/django-extensions#1425
Added indexes in the Meta of the TimeStampedModel.
Usage:
class Cheese(TimeStampedModel):
    name = models.CharField(max_length=50, null=True, blank=True)

or
class Sale(TimeStampedModel):
    quantity = models.IntegerField()

    class Meta(TimeStampedModel.Meta):
        db_table = "sale"

or
class Sale(TimeStampedModel):
    quantity = models.IntegerField()

    class Meta(TimeStampedModel.Meta):
        db_table = "sale"
         indexes = TimeStampedModel.Meta.indexes + [models.Index(fields=["quantity"])]

Could you please update docs/model_extensions.rst and put the usage example in the description as an example under *TimeStampedModel*.

Coverage increased (+0.2%) to 71.329% when pulling dc2d1ee5714302c5dc55422560ef679f76e091e7 on anudeepsamaiya:add-indexes-for-timestamped-activator-models into 0f0ca99c8d5f3e34399b2f6a6f920167376d7fb9 on django-extensions:master.

Could you please update docs/model_extensions.rst and put the usage example in the description as an example under *TimeStampedModel*.

I have added the docs. Thanks.

Why not do a little differently... Add an IndexedTimeStampedModel (name is just a strawman) which is something like:
class IndexedTimeStampedModel(TimeStampedModel):
    class Meta(TimeStampedModel.Meta):
        indexes = [
            models.Index(fields=["-modified"])
            models.Index(fields=["-created"]),
        ]

I was thinking of implementing this way, but then most people will have to modify their code if they want to use indexes. On the other hand if we go TimeStampedModel any new user will have indexes right from start and others will have database migrations. The latter one will surely introduce inconveniences but in favor of performance improvements.
Although, I am not in favor of going with latter options, we can totally avoid it if we by adding the document for IndexedTimeStampModel and properly explaining its pros and cons. I also think we can also have indexed versions for other models.

(or models.Index(fields=["-modified", "-created"]) we have to decide on one multi column index or two separate ones. Do all supported django database offer multi column indexes ?)

Yes MySQL, MariaDB, Postgres, Oracle, SQLServer all popular dbs support multi column indexes.

This way we do not suddenly change the behavior of TimeStampedModel and create a schema migration after an upgrade of django-extensions for everybody.

Cool lets do it that way and add index'd versions with some documentation.
This would also be a very nice example of how easy it can be to customize these things :-)

FWIW as a django-extensions user I think adding the index to my existing models, vs. having to make complex migrations to migrate my TimeStampedModel columns to IndexedTimeStampedModel columns, is the right way to go...per what @anudeepsamaiya said here:

On the other hand if we go with adding indexes to TimeStampedModel, then any new user will have indexes right from start and others will have database migrations.

This would be much easier for me than having to switch my existing TimeStampedModel's to IndexedTimeStampedModels.
@trbs I would think that for almost all use cases, having an index on created and modified fields that are used so often in sorting would be expected by default. See for instance this SO question/answers.
For large projects this would (I believe) significantly speed up queries, and for small projects this would make a negligible difference from the current implementation.

Unless you have TimeStampedModel on very large tables where you don't need the index and it will slow down the database, bloat the size (because of the additional indexes) and potentially mess a little with caching since you now evicting potentially hot pages :-)
Anyways so many potential cases and we really don't know what people are using it for.
I can be convinced to set the indexes by default, specially since I think having a complex migration path for people (I assume the majority) that do want to have the indexes by default.
So what I suggest to do is if there is consensus to make the indexes the default. Then we do so via:

The class Meta indexes property
Update the PR to fix the style of those as indicated in my comments/reviews
Write more and better documentation of the change and how people that do NOT want the index should adjust their code (aka override Meta.indexes) to avoid getting them
Write a short details explanation of the change for in the changes file with a link to documentation
We bumb the major version number of Django-Extensions with the release of this change

(Please note that I will be traveling a lot this month, so appologies in advance for reviews and merging PR's to be a bit slow)

@trbs thanks for your thoughtful response! One thing to add.
I think the reason people would assume the indexes are in place is because TimeStampedModel [sorts on the modified and created fields by default]. I believe means that for most users the index will be of benefit any time they query a large number of models unless they've explicitly removed this Meta ordering on their TimeStampedModel.
Your suggestion for managing the change makes perfect sense. @anudeepsamaiya let me know if you want any help on implementing the changes? I have some time end of next week but not before then.


Unify code for spectral line fits

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

While working on #49, I see a great deal of code that could be unified by making the following objects share a superclass and reorganizing:

VoigtFitter
NVoigtFitter
GaussianFitter
LorentzianFitter
MultiLorentzianComplexFitter

Also remove SimultaneousMultiLorentzianComplexFitter, which was meant to handle, for example, a Cr K-beta line and a Mn K-alpha line at once. But it doesn't work, right @oneilg ?

Original comment by Galen O'Neil (Bitbucket: oneilg, GitHub: oneilg).

Correct I never got it to work.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Fixed in 61f36305bd7.
I have tested VoigtFitter, GaussianFitter, and both MnKAlphaFitter and MnKBetaFitter. (See test_fits.py). This seems to work with much more unified code than fitters had before. Hooray!


Add a basic .editorconfig file

Description
Based on Augur's .editorconfig (https://github.com/AugurProject/augur/blob/dev/.editorconfig).
This will pretty much eliminate any issues with extra whitespace creeping in at EOL, resulting in 'dirty' commits. Though it might also mean that commits are noisier for a while, as the extra whitespace will be removed anytime a file is opened and saved again.
Many editors will inherit settings from this file, but VSCode requires an [extension](VSCode requires an extension to support it.) to support it. Learn more: https://editorconfig.org/.

Keeping as draft so I can consider the implications of

it might also mean that commits are noisier for a while, as the extra whitespace will be removed anytime a file is opened and saved again.

it might also mean that commits are noisier for a while, as the extra whitespace will be removed anytime a file is opened and saved again.

I think this is fine. Not a huge deal. Could circumvent this by going through each file and fixing extra whitespace in a single PR if we want.

@maurelian is this ready for review?

Yes, I think we should do this.


Disable format of plain text in HTML

Hello,
I work with OctoberCMS, and the html files are as following:

Those lines above the == need to be under eachother if you want it to work. But if I format (even without any extensions!) this happens:

Unfortunately this causes the code to break.
Is it possible to prevent this plain text from getting formatted inside html files?

This looks like invalid HTML. Any chance you can add comments around it?
Otherwise select only the lines you want format and invoke format.
To solve that correctly you probably would need a specific language support for OctoberCMS file that never touch the lines before '====='

@BenjaVR, I also sometimes use October CMS, so I can make the extension for support this syntax.

@mrmlnc That would be great!

@BenjaVR,
Well, I started work on the octobercms extension. Now I finished work on syntax highlighting. You can follow the progress in the vscode-october repository. Unfortunately, I now have a little time, so will work on this extension in their spare time.


fix: use same logic for all list_nexuses listings

We currently don't list nexuses when their state is Init. This is probably not good as we're hiding things from the control-plane and we should come up with a better strategy for handling this.
However, atm we're not consistent depending on the type of list nexuses so until we have a better fix we should make what we have consistent.
Signed-off-by: Tiago Castro<EMAIL_ADDRESS>

bors merge


SHEX::reset() is incompatible with ctor

I haven't used it, but looking at SHEX::reset(), it sets _length    = 0;
This is different behaviour to the ctor.
I suggest adding uint8_t length = 16 to the function's signature, to more closely mimic how ctor works
Whilst you're there, maybe add #define SHEX_DEFAULT_LENGTH 16 and use that as the default.

Thanks for the issue, might rake a few days.
Although this one seems straightforward.

Started with a 0.2.2 version to fix this.

fix should also be default param for setBytesPerLine(const uint8_t length = SHEX_DEFAULT_LENGTH)
added #define SHEX_MAX_LENGTH                 32 too  to remove magic number from code.


Should we use relative path instead of absolute path in notes?

Spark official docs use relative path instead of absolute path, such as submitting-applications. I think it's better to use relative path in documentation since not every user have the specific path and will not make users feel confused.
Currently, documentations in Mobius mainly use absolute paths, such as windows-instructions and running-mobius-app. What's more, the absolute paths have different folder names, such as c:\dependency\ and C:\MobiusDependencies\, which would also make users easily feel confused.

This's really will puzzle especially the freshman using Mobius.
I'd prefer use a notion path such as {Mobius}\build\dependency\ or {yourself-downloaded-jars-dir}\, etc.

Personally  I don't think it is needed. I think absolute paths make more sense and I assume those who read the doc can figure out that the path references are just for showing how to carry out somethings in Mobius.

Closing this issue for now. Reopen if needed.


Recent migration to Git makes ServiceGenerator un-buildable?

I think the project has references to files that are now under Deps (e.g. GTMSessionFetcher.{m,h}, etc.)

Should be fixed with that pull.


Add browserlist support

Hi!
I have updated the autoprefixer and added tests to test support for new features in PR #353

Hi, this is not useful (since semver handle this update automatically (we use a ^ with get minor and patch) and does not help us with browserlist here.

@rajdee
Thanks for making the dependency update and adding tests.
Updating "^6.0.2" to "^6.7.6" doesn't do anything because the ^ syntax in semver gets the latest version of the same major.
Not to mention, the CHANGELOG for autoprefixer says "Browserslist 2" was added in 7.0.
Would you update the autoprefixer entry in package.json to "^7.0.0" and reopen the PR?

Autoprefixer will be updated to 7.x in cssnext 3.x

Possibly resolved by #445

postcss-cssnext has been deprecated in favor or postcss-preset-env. Read more at https://moox.io/blog/deprecating-cssnext/


doc: Unindent additional Return lines to work around napolean bug

In a google-style docstring, this is problematic:
Returns:
    str: Some really long description that requires more
        than one line

Since the additional text (i.e., "than one line") is indented,
napolean gets confused and incorrectly formats the description. The
fix is to align subsequent lines with the first:
Returns:
    str: Some really long description that requires more
    than one line.

Along the way I also added missing return types as needed.

Current coverage is 98.52% (diff: 100%)

Merging #892 into master will decrease coverage by 1.47%

@@           master       #892   diff @@
========================================
  Files          30         30
  Lines        1897       1897
  Methods         0          0
  Messages        0          0
  Branches      314        302    -12
========================================
- Hits         1897       1869    -28
- Misses          0         22    +22
- Partials        0          6     +6

Powered by Codecov. Last update a14a4b1...68869f0

LGTM :+1:


Inquiries on multi-modal data loader

Hi, thank you for your amazing work. I'm wondering whether there is an instruction for loading both the image face frames as well as the speech segments.

Hi, as of current, this repo only covers the audio part.


Support Install on Hardened Cluster - Logging

Support Install on Hardened Cluster - logging

Closing in favor of 28620.


FullScreen not possible

Hi! I can't get the player to full screen. Any ideas? The example app is working, but once copied your exampel code 1:1 into my application it just not going into orientation:landscaperight. Any ideas?

I could not figure out what caused it, but I solved it following:
override func viewDidLoad() {
super.viewDidLoad()
//rotate complete view, so we get a landscape orientation
self.view.transform = CGAffineTransform(rotationAngle: CGFloat(Double.pi / 2 * 1))
......
}


docs: deny missing docs

Fixes #1140

[ ] iroh (@flub)
[x] iroh-io (@rklaehn)
[ ] iroh-net

[x] #1165
[ ] derp mod

[x] iroh-bytes (@rklaehn)
[ ] iroh-metrics (@Arqu)

If like to take the net crate if that's ok

iroh-metrics docs are covered now in https://github.com/n0-computer/iroh/pull/1173


Upgrade from 1.0 to 1.1 fails

When attempting to upgrade a repository created by:
$ sqitch --version
sqitch (App::Sqitch) 0.9991

using a newer version:
$ sqitch --version
sqitch (App::Sqitch) 0.9992

the following error is generated:
* From 1.0 to 1.1
psql:/usr/local/lib/perl5/App/Sqitch/Engine/Upgrade/pg-1.1.sql:3: ERROR:  constraint "changes_script_hash_key" of relation "changes" does not exist

                             Table "sqitch.changes"
     Column      |           Type           |             Modifiers
-----------------+--------------------------+------------------------------------
 change_id       | text                     | not null
 script_hash     | text                     |
 change          | text                     | not null
 project         | text                     | not null
 note            | text                     | not null default ''::text
 committed_at    | timestamp with time zone | not null default clock_timestamp()
 committer_name  | text                     | not null
 committer_email | text                     | not null
 planned_at      | timestamp with time zone | not null
 planner_name    | text                     | not null
 planner_email   | text                     | not null
Indexes:
    "changes_pkey" PRIMARY KEY, btree (change_id)
    "changes_project_script_hash_key" UNIQUE CONSTRAINT, btree (project, script_hash)
 Foreign-key constraints:
    "changes_project_fkey" FOREIGN KEY (project) REFERENCES sqitch.projects(project) ON UPDATE CASCADE
Referenced by:
    TABLE "sqitch.dependencies" CONSTRAINT "dependencies_change_id_fkey" FOREIGN KEY (change_id) REFERENCES sqitch.changes(change_id) ON UPDATE CASCADE ON DELETE CASCADE
    TABLE "sqitch.dependencies" CONSTRAINT "dependencies_dependency_id_fkey" FOREIGN KEY (dependency_id) REFERENCES sqitch.changes(change_id) ON UPDATE CASCADE
    TABLE "sqitch.tags" CONSTRAINT "tags_change_id_fkey" FOREIGN KEY (change_id)  REFERENCES sqitch.changes(change_id) ON UPDATE CASCADE`

Did you originally build v0.991 from a Git clone instead of a release? It looks like that patch has already been applied to your code. You can fix it by running these commands:
ALTER TABLE sqitch.changes DROP CONSTRAINT changes_project_script_hash_key;
ALTER TABLE sqitch.changes ADD UNIQUE (script_hash);

Then run the the upgrade again.

For posterity: this also happens when two deploy sql files are identical in content (this is unusual in practice, as sqitch add inserts comments which are unique to each file).

@pdl Ah-ha. That issue was the reason for the 1.1 upgrade. Prior to that, the script hash had to be unique. 1.1 lets it be the project name and script hash.


Show exact timestamp of commits at the dashboard

A user may want to see exact timestamp instead of a month ago, etc.

/cc @jongyeol

Hovering over the '... ago' should reveal the exact timestamp, no?

Oops, didn't notice it. Thank you for letting me know.


Change API version for cloud metadata endpoint

This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines

[x] The PR has modified HISTORY.rst with an appropriate description of the change (see Modifying change log).

Command Guidelines

[n/a] Each command and parameter has a meaningful description.
[n/a] Each new command has a test.

(see Authoring Command Modules)

FYI @lmazuel @bganapa

Codecov Report

Merging #4056 into master will decrease coverage by 0.01%.
The diff coverage is 11.11%.

@@            Coverage Diff             @@
##           master    #4056      +/-   ##
==========================================
- Coverage   70.63%   70.62%   -0.02%
==========================================
  Files         428      428
  Lines       27891    27895       +4
  Branches     4273     4273
==========================================
  Hits        19700    19700
  Misses       6919     6919
- Partials     1272     1276       +4

Impacted Files
Coverage Δ

...li-cloud/azure/cli/command_modules/cloud/custom.py
13.79% <11.11%> (-0.67%)
:arrow_down:

src/azure-cli-core/azure/cli/core/util.py
70.66% <0%> (ø)
:arrow_up:

...dback/azure/cli/command_modules/feedback/custom.py
31.25% <0%> (ø)
:arrow_up:

...nent/azure/cli/command_modules/component/custom.py
16.23% <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 757d00e...af3c924. Read the comment docs.


feat(codegen): minify case "foo" -> case"foo"

#8085  👈 (View in Graphite)
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

0-merge - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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


L2 vlans marked with a tag are not imported

Issue Summary
When tagging some SVIs and l2vlans with a tag in the tenant file:
          svis:
            255:
              name: V255-T-UTIL-IDMZ-APP_UTIL_OPER
              enabled: true
              tags: [ VH_UTIL_IDMZ ]

      l2vlans:
        55:
          name: V55-T-UTIL-IDMZ-Back-FW-to-VPN
          tags: VH_UTIL_IDMZ

With the same tag, vlan 255 gets imported, but not vlan 55.
After removing the filter tags, both get imported in the configuration. Could you please check?
Which component(s) of AVD impacted
eos_cli_config_gen
How do you run AVD ?
Ansible CLI (with virtual-env or native python)
Steps to reproduce
Tag l2vlans and filter based on the tags.

Relevant log output
No response
Contributing Guide

[X] I agree to follow this project's Code of Conduct

I think the tags is a list.
l2vlans:
55:
name: V55-T-UTIL-IDMZ-Back-FW-to-VPN
tags: [VH_UTIL_IDMZ]
reference: https://avd.sh/en/releases-v3.x.x/docs/how-to/first-project.html#l2-services

absolutely my script missed to output that in the l2 case. thanks for the second pair of eyes!


Create a list of Koans for other languages

Pick several programming languages and see if they have Koans.  Answer the following questions:

[ ] What are the first 5 categories?
[ ] How do you "execute" the Koans?

Write the answers in the reasonml-koans wiki.

There's a nice list here.


Feature Request: Run all scripts in a directory

It would be great if you could run all the scripts in a specified directory without needing to change the config to specify each one in turn. This would make the addition of new scripts a trivial exercise and prevent the centralised prometheus config from getting out of hand in large sites.
Thanks

It makes sense, but I coded it the way I did out of an abundance of caution.  By requiring each script to be hand-coded, you're less likely to have someone sneak a file into a directory and trick you into executing it with potentially elevated privileges.
Someone else wrote a very similar exporter before me, but I only discovered it subsequently because they chose a very odd name.  Unfortunately I forget the name, but if I rediscover it I'll post it here, because I think they were more liberal in a way that would address this issue.


Move KeyError checks to state methods

Fixes #72

As we see here, I get a lot of KeyErrors from that line. I also get IndexErrors still from handle_mode
 process_channel_modes
    del state.connected_users[user.nick.lower()]
KeyError: 'nick'
    if args[1][0] not in ["+", "-"]:
IndexError: string index out of range
Exception in thread Thread-1297:
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 973, in _bootstrap_inner
    self.run()
  File<EMAIL_ADDRESS>line 910, in run
    self._target(*self._args, **self._kwargs)
  File "/Users/Writing/pthn/mantatail/mantatail.py", line 199, in recv_loop
    call_handler_function(state, user, args)
  File "/Users/Writing/pthn/mantatail/commands.py", line 133, in handle_mode
    process_channel_modes(state, user, args)
  File "/Users/Writing/pthn/mantatail/commands.py", line 361, in process_channel_modes
    if args[1][0] not in ["+", "-"]:
IndexError: string index out of range
Exception in thread Thread-1307:
Traceback (most recent call last):
  File<EMAIL_ADDRESS>line 973, in _bootstrap_inner
    self.run()
  File<EMAIL_ADDRESS>line 910, in run
^CTraceback (most recent call last):
  File<EMAIL_ADDRESS>line 197, in _run_module_as_main
    self._target(*self._args, **self._kwargs)
  File "/Users/Writing/pthn/mantatail/mantatail.py", line 199, in recv_loop
    return _run_code(code, main_globals, None,
  File<EMAIL_ADDRESS>line 87, in _run_code
    call_handler_function(state, user, args)
  File "/Users/Writing/pthn/mantatail/commands.py", line 184, in handle_nick
    exec(code, run_globals)
  File "/Users/Writing/pthn/mantatail/mantatail.py", line 412, in <module>
    del state.connected_users[user.nick.lower()]
KeyError: 'pong'

@Akuli I added a print in handle_nick() that shows what is received when it errors. It doesn't make a lot of sense to me though.

As you can see, it errors with KeyError: 'privmsg'. However, the last command sent to handle_nick() contained only MODE, not PRIVMSG.
Any thoughts on this?

After staring at this for a while, I realized that the print is before setting the nick of the user. So the old nick of the user is PRIVMSG, and we are trying to changing its nick to MODE.
At this point, I would make a text file that contains the commands the fuzzer sent, so that you can send the same exact commands again easily. If you have the commands saved in a file commands.txt, you can redirect it as input to netcat like this:
nc localhost 6667 < commands.txt

This tells the shell to copy/paste the contents of commands.txt into netcat. Also, send me the exact commands, so that I don't have to type them manually from your screenshot and guess what was before the visible part :)

@Akuli I tried to do as you said. However, when running the file via netcat, there are no errors at all. It just says ":QUIT :Quit: (Remote host closed the connection)". I tried to remove all instances of QUIT, but it changes nothing.
Here is the whole set of commands run by the fuzzer:
https://dpaste.com/GTXFPHXC6


Package management

Hey! Just stumbled upon this repo from shopify_theme. I know this project is very fresh, and is still being developed. I was surprised to see you have everything in downloadable releases. I'd love it if you guys used a package manager. I really don't care what package manager you guys choose, just so that I can download this dependency and embed it into my build process.

Installation of themekit on Linux and OSX is now basically jokes. And when #94 gets merged updating to newer versions will be a single command.
Install for first time:
curl https://raw.githubusercontent.com/Shopify/themekit/installers/install | python
Update Application (once v0.3.0 goes out)
theme update


Integration Test - Release - 2019/02/22 08:52:56

Auto create for integration test. AnotherAuthorUpdatedArticleFlow

#backlog

The feedback you logged for Integration Test - Release - 2019/02/22 08:52:56 has been in our backlog for 90 days. While we try to respond individually to as many feedback items as possible, we are not able to respond to all of them. Since this item has been in the backlog for 90 days, we’re closing it.
For more information about the process by which we handle documentation feedback, see "How we respond to Azure technical documentation feedback" in our public contributor guide.


Use decimals to calculate amount in the currency network

The clientlib should use the decimals of the currency network to calculate the amount of value. Additionally the raw information should still be accessible.
This means in every get method where balances or creditlines limits are stated, there should be
{
   value: 1.23,
   raw: 123,
   decimals: 2,
}

returned, where value = raw / (10^decimals)
for methods that take value it is the other way arround.
it should take value and an optional parameter decimals, and calulate based on that the raw value internally either by the given decimal if present, or by the know decimals.

The decimals can come from the server for now, but the right way would be that the clientlib has a list of known currency networks, same of what the rest endpoint returns, where it takes the decimals from.


Fail to generate MSVS project for VS2017

Operating system or device - Godot version:
Windows 10 Pro
Godot 3
python2.7
scons 2.5.0
Issue description:

trying to build the Godot source with scons -j10 p=windows vsproj=yes
received an error that says,
"AttributeError: 'SConsEnvironment' object has no attribute 'MSVSProject':
File "C:\Z_Development\Godot_Source\SConstruct", line 443:
msvproj = env.MSVSProject(target=['#godot' + env['MSVSPROJECTSUFFIX']],"

In the Scons' User guide, it says that this builder should be included by default.
Steps to reproduce:
Using Developer command prompt for VS2017
successfully build the binary with scons p=windows
then build with scons -j10 p=windows vsproj=yes
receive an error.
**I also received errors related to VsDevCmd.bat. But I don't think it relates to my problem.

Link to minimal example project:

SCons wasn't updated to support VS 2017. You can notice that by the first warnings by SCons. There's nothing we can do in Godot to alleviate that AFAIK.

You can go into the VS2017 Installer, modify your installation to include VC++ 2015.3 v140 toolset. Then still use the Dev Console for VS2017.  My system never completes the initial build when I use the -j tag so maybe try without that too.

My system never completes the initial build when I use the -j tag so maybe try without that too.

This is and old and hard to fix issue (#5042), not related to the toolset. You just need to restart the build when it fails a few times until all generated files are built.

@vnen @Tyler-Yocolano
Thanks for the explanations. Btw like I mentioned I did manage to compile a functioning executable with the latest vc compiler tho. XD magic. As vnen said ,you do have to run the build multiple times. That -j seems to be for parallel compilation. Anyway, I guess I have to get another ide for the lovely godotgodot

You can use VS 2017 to compile, because SCons will use whatever compiler is set up in the prompt. The issue with SCons not supporting VS 2017 is those warnings and the fact that you can't generate a project.

Got it


Update integration logos

Not sure what the bit about missing Instagram/Twitter/etc. logos was because they render fine in my dev environment, but this fixes #11590.

Looks reasonable to me; @rishig can you review?
@synicalsyntax the issue with Instagram and friends was ad blockers blocking images with a filename of e..g twitter.png or maybe the appearance of the Twitter logo.  So we will need to rename those files to something else to get around it (or change the images?  I'm not sure).  I think probably @rishig may need to help test whether it's the file or the path that's the issue.

Thanks @synicalsyntax! Many nice improvements; I merged all but 4 of these.
For irc, matrix, and xkcd, I think it makes sense to have them a little bigger; maybe closer to 80-90px width? Wasn't sure the best way to do that. Possibly it'll make sense to have two different classes, one for squarish logos and one for rectangular logos.
For stripe; I'm a bit conflicted, since the old logo was so much better as a bot avatar. Zapier also seems to have not updated (even though they did e.g. update Slack, which changed much later). The old one is still fairly in line with their brand, so I think just better just to keep the old one.
For resolving the Adblock issue, my guess is the issue is with the filename. Could you try changing the filename?
If you use adblock, the setting that removes them is "Block social media icons tracking".

Merged, thanks @synicalsyntax!


fix(connectors): MGDCTRS-1416: removed tid Undeclared query param referenced in ConnectorsHandler.Create

Description

A clean up of unused and undefined url parameter named tid.
Verification Steps

OCM_ENV=integration make test/integration/connector

Checklist (Definition of Done)

[x] All acceptance criteria specified in JIRA have been completed
[x] Unit and integration tests added that prove the fix is effective or the feature works (tested against emulated and non-emulated OCM environment)
[x] Documentation added for the feature
[x] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer
[x] All PR comments are resolved either by addressing them or creating follow up tasks
[x] Required metrics/dashboards/alerts have been added (or PR created).
[x] Required Standard Operating Procedure (SOP) is added.
[x] JIRA has been created for changes required on the client side

The other option is to add it to the open API. Isn't there a use case for listing all connectors of a particular type?

The other option is to add it to the open API. Isn't there a use case for listing all connectors of a particular type?
If I recall correctly connectors can be already listed by searching per connector type id

Yeah, it's exposed as a search field connector_type_id. :+1:


reloading on routes will get error

I use $serve -s build -p 80 to deploy my react app with react-router.
When I reload the  page on index route (/) and login page (/login), it works fine.
However, my website gets error as I refresh on other routes, for example /book/123456.
Because no matter what the request is, the browser always gets HTML file.
Thus, both of the content in main.css and main.js are HTML, and the browser error.

Did I lost any configurations?

serve only responds with index.html if it doesn't find a file - so I'm happy to accept a PR that makes it find our files. 😊


feat: aztec-cli "unbox" command

WIP, not working or ready for full review.
shows my high level thoughts on implementation approach based on https://github.com/AztecProtocol/aztec-packages/issues/1056
feedback thus far:
(1) instead of looking up the install directory from npm i -g... for the aztec-cli package, let's download the noir-contracts from github directly (done)
(2) setup a new subpackage starter-kit for the barebones webserver + frontend (done, but it's basically the default next.js project.  tried to merge its settings with our other subpackage package.json)
questions on my side:
does this require a local sandbox running as well? (yes)
why aren't the formik forms working on the frontend?
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

i have been testing the starter-kit subpackage by coping the private_token_contract.json ABI in noir-contracts/artifacts into starter-kit/noir-contracts, not 100% sure about the package management here

TODO: look at https://github.com/noir-lang/noir-starter/tree/main/next-hardhat

Some thoughts:
When users run the command:
aztec-cli unbox private_token [optional_name_of_the_output_dir]
They will find the following files:
private_token
|— README.md
|— package.json
|— any.config.cjs
|— src
       |— app
              |— index.tsx
              |— globals.css
              |— Contract.tsx
              |— DeployForm.tsx
              |— FnForm.tsx
       |- scripts
              |— index.tx
              |— deploy_contract.tx
              |— call_contract_function.tx
       |— contracts
              |— private_token_contract
                     |— main.nr
                     |— Cargo.toml
       |— artifacts
              |— private_token_contract.json
              |— private_token.ts
       |— test

package.json
It should provide scripts to compile noir contracts, run tests, and start the website.
"scripts": {
    "compile": "aztec-compile compile --outdir ./src/artifacts --typescript ./src/artifacts",
    "test": "jest",
    "start": "next start"
}

App
The app speaks to the AztecRPCServer (which should already be running). We don't need a web server for the frontend.
Contract.tsx
We can import the already generated abi and render a form for each contract function:
import PrivateTokenJson from '../artifacts/private_token_contract.json' assert { type: 'json' };

<DeployForm abi={constructorAbi} onDeployed={contractAddress => setState('contractAddress', contractAddress)} />
{!!state.contractAddress && (
  PrivateTokenJson.functions.filter().map(fnAbi => <FnForm contractAddress={state.contractAddress} abi={fnAbi}></FnForm>)
)}

DeployForm.tsx
We should create a file in scripts to demonstrate how to do something.
import { deployContract } from '../scripts/deploy_contract.js';

onSubmit: deployContract(contractAbi, inputs)

FnForm.tsx
import { callContractFunction } from '../scripts/call_contract_function.js';

onSubmit: (inputs) => callContractFunction(contractAddress, fnAbi, inputs)

scripts/call_contract_function.ts
function callContractFunction(contractAddress, fnAbi, inputs) {
       if (fnAbi.functionType === 'unconstrained') {
              viewTx();
       } else {
              sendTx();
       }
}

Nice to have
Account.tsx
Fetch accounts from RPCServer and display them here. Users can pick which one to use, or create a new account.
All open to discussions :)

i did a bad squash, gonna leave this here in case i need something but opened fresh PR at https://github.com/AztecProtocol/aztec-packages/pull/1825


Cannot Find Option to Save/Restore settings

Description of the feature, modification, idea or suggestion
Self-explanatory: the application has a LOT of settings options. There should be simple way in the app to both back them up and also restore them.
Proposed implementation details (optional)
No response

Is copy of settings.xml and usernotesdb.xml from %appdata%\SystemInformer ( or in case of portable installation SystemInformer.exe.settings.xml and usernotesdb.xml from installed folder) aren't simple enough for you?

Just copy the configuration file. Is as portable as it gets.
Or you are looking for a File / Save as option alike to save the config somewhere else?
Everything is contained within a single xml. Seems really convenient


Mobile support (iOS and Android)

Let's make a check list of know issues here, we'll solve them one by one:

[x] Fix the auto updater downloading weird stuff on mobile platforms
[x] Make the mobile screens actually use SafeArea to prevent collisions
[x] Fix the login and register page to support mobile on small screens
[x] Fix the password reset page on small screens
[ ] Make a better message context menu specifically for mobile
[x] Remove all inappropriate or unsupported settings from the mobile settings page
[ ] Remove all Spaces related pages from the mobile app

When this check list is complete, I guess we can try testing the first version of the app on Android. Just as an .apk for now and no auto updates for Android unfortunately. After it is done I'll start applying to Google for putting it into the Play Store and then eventually into the App Store. Once both apps in these stores work properly, we'll start rolling out more features to mobile. That's the plan for now at least.

This is now finally one step closer because of the internal changes made in v0.2.0. After this release, mobile will get some more love and we'll hopefully have the first version of the mobile app by v0.3.0.

Android support is now on track for the end of November. You can read more at https://liphium.com/docs/general/roadmap/#goals-for-november.

While the app deployment to the Play Store is something I'm not aiming for this November, I feel like I can make a better app throughout December by also adding more features to finally make Liphium a chat app you wanna use. Liphium should have message search and other basic stuff, message editing will not be on that list, but search is one of the most important parts. Browsing messages while offline adds to this as well.

This issue just needed closing because it is way too broad. In the future, issues like this may exist in case new platforms appear, but for now, I'll just keep this in the project board over at https://github.com/orgs/Liphium/projects/2/views/1.


Add pages with the complete list of properties or the styles in documentation

I'm wondering why there isn't a page in the documentation with all the styles declared and every classes in a single page.
It's really easy to find the right class for beginners this way.
Are you planning to integrate something like this maybe?

Previous versions had a page like that but I don't know that it added much value beyond just looking at the CSS<EMAIL_ADDRESS>

I think you got the point, maybe just add this link in the first menu then, because it's what I was looking for and I didn't find.
Anyway thanks for your libraries, you are brilliant!


Install dependencies for phpstan analysis

Changed

Install dev dependencies when running phpstan analysis

Makes use of https://github.com/OskarStark/phpstan-ga/releases/tag/<IP_ADDRESS>
Relates to: https://github.com/OskarStark/phpstan-ga/pull/22

This was fixed in 10f74ba


[DataLoader2] Forward fix of 'limit' delegation

Stack from ghstack:

#915
#998
#1011
-> #1019

@nivekt has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.


Flow control deadlock when using SetReadDeadline / CancelRead

Example:
https://gist.github.com/ltucker/c03d3d917b17cd31bcf4c5ab73638657
Typical Output:
https://gist.github.com/ltucker/1d2d8c28f2976077cddace06da666080
I've been running into what appears to be a flow control related deadlock on a session if I attempt to set read deadlines on streams and cancel reads.
The scenario demonstrated is set up so that 50% of streams in a session time out and then attempt to "cancel". Eventually, all writers see the session level send window as exhausted and no reader can (or will) adjust it (even new ones after the fact).  All subsequent streams in the session then time out with no bytes received.
My theory is that some bytes on timed-out or read-cancelled streams are not accounted for / don't cause window adjustments -- perhaps in-flight bytes are accounted for on the write side, but not on the read side.  It is not possible from the perspective of a library-user to "drain" a read-cancelled stream afaict.
I'm not certain whether it is an issue with the implementation (like those bytes should be dropped, but still cause window adjustments), or whether this is more of a "don't-do-that" issue with the protocol.  Glad to provide more detail if it is helpful.

Deadlines are a purely local operation that Go's net.Conn interface provides to make Read and Write calls return after the expiration of a deadline. Nothing is sent on the wire when you set a deadline.
This means that data received will sit in its buffer waiting to be read, consuming flow control credit. There's things you can do: Set the deadline to the future, or to time.Time{}, then you'll be able to read the data. Alternatively, you can call CancelRead on the stream, if you're no longer interested in reading the data.

Can you try using an IETF QUIC version?
In IETF QUIC, CancelRead sends a STOP_SENDING frame:
https://github.com/lucas-clemente/quic-go/blob/93c7eb94ce4109373c0d3366b39daef66723136e/receive_stream.go#L197-L202
When receiving a STOP_SENDING frame, the peer will cancel writing
https://github.com/lucas-clemente/quic-go/blob/93c7eb94ce4109373c0d3366b39daef66723136e/send_stream.go#L291
and send a RST_STREAM frame, containing a final flow control offset for that stream
https://github.com/lucas-clemente/quic-go/blob/93c7eb94ce4109373c0d3366b39daef66723136e/send_stream.go#L253-L257
In gQUIC, things are more complicated, since the stream state machine was not designed to be general purpose, but for the HTTP/QUIC use case. After calling CancelRead, the RST_STREAM is only sent when you call Close. Receiving the RST_STREAM should make the peer respond with a RST_STREAM, which would then contain the final offset.

@marten-seemann Ah I see.  Sure, will do -- is the IETF version roughly as stable as the older gQUIC stuff at this point?

@marten-seemann Ah I see. will do.  Is the IETF version roughly as stable as the older gQUIC stuff at this point?

We're not maintaining any stable versions of IETF QUIC in the master branch, that's why protocol.VersionTLS is not an exported variable (although nothing can stop you from just copying the value for testing purposes... Just keep in mind that there's no compatibility guarantee between commits, i.e. things might break between commits if you build master with this version).
If you want a stable IETF QUIC version, you can vendor a release tag, e.g. https://github.com/lucas-clemente/quic-go/releases/tag/v0.10.0, which explicitly exposes a version number for IETF QUIC.

@marten-seemann got it, thanks!

@marten-seemann yup, works as expected in IETF quic.  I'll close this on the assumption that I'm just abusing GQUIC. :)


Ready timeout fix

Description
According to the documentation, the .kitchen.yml file contains the :ready_timeout parameter under machine_options directly - not bootstrap_options. Because bootstrap_options is passed to the ip_to_bootstrap function, :ready_timeout is not visible.
      # TODO: please create a better solution for the below
      # bootstrap_options shouldn't contain the :ready_timeout value - machine_options does
      # however, I don't want to break previous work or change all the calls made to this function
      # setting a default, as for most people bootstrap_options[:ready_timeout] will be nil
      # another possible workaround is to add a second entry under bootstrap_options in .kitchen.yml

Issues Resolved
The commit https://github.com/chef-partners/chef-provisioning-vsphere/commit/0040fb83809f7ed2d0723c1dc4020f984e8c450a essentially broke mine (and I'm guessing others who are following the doc's standard for the .kitchen.yml file). Added an OR comparison to essentially assign the value of 90 in case bootoptions[:ready_timeout] resolves to nil so as to no longer break.
Check List

[x] All tests pass.
[x] All style checks pass.
[x] Functionality includes testing.
[x] Functionality has been documented in the README if applicable

Sorry for the confusion with the multiple commits. Kept getting "class has too many lines" errors in Travis CI. I condensed the change into one line.

Can you squash this down to one commit, it looks good to ship.

Closing this pull request. Will submit another.


Model caching with new download manager?

While away from home I noticed that models that are cached aren't loading when there is no internet connection.
Is there a setting I should toggle perhaps?

Solved by awesome new 'allowOffline' setting.
https://github.com/ngxson/wllama/pull/90


App won't install since version 19.0 or crashes in my device

Accrescent does absolutely nothing when trying to install the app. Installing manually from releases will return a simple "app not installed" dialog. Installing any version prior to 19.0 will install and open succesfully, but it crashes after trying to create or open ANY file or folder. Maybe my device is too old for this, but if you wanna check this, my device is a Xiaomi Redmi 9C with Android version: 10 QP1A.190711.020.

@El-Desconocido your device is using a 32-bit OS. BeauTyXT doesn't support 32-bit OS'. 32-bit OS' are worse for security than 64-bit OS'.
Before 0.19.0, BeauTyXT didn't explicitly say it didn't support 32-bit, but it didn't include 32-bit native libraries which is why it installs but crashes when trying to open or create a file or folder.
I highly recommend using GrapheneOS on a recommended device (https://grapheneos.org/faq#recommended-devices). GrapheneOS also has support for MTE (along with many other privacy/security improvements listed at https://grapheneos.org/features), which BeauTyXT opts-in to for better protection from exploit attempts.


#44 - fix gradle dependencies scope

[ ] All tests passed. If this feature is not already covered by the tests, I added new
tests.

Fixes #44

I have read the CLA Document and I hereby sign the CLA


Update Registrar.php to populate email field

Adding email field during signup to enable email verification from Parse.

I'm not sure this is the best way to do this. I think what we need is a better way to make the field names you're passing in to the registrar be configurable, to properly handle all the valid ways you can use them in Parse. Thoughts?

Yeah I agree, I did this as a 'bare minimum' change based on the fact you're calling out email as mandatory in the Registrar validator which I thought implied you'd be using the email as the username so it seemed logical to do this change. Thinking about it though, it needs a change to give a bit more flexibility.
Perhaps in the meantime a documentation update clarifying extending the Registrar and User classes would help?

Can we merge this as a temporary solution until we come up with something more general?

Sure why not.


PyTest does not output Code Coverage report

This could be done be either having an option to enable or by letting the user pass custom commands for pytest.

Fixed in #9


Do not use latest package

While re-running the playbook we do not want to check for new packages.
We shouldn't perform upgrades, we leave this to the operators.
Signed-off-by: leseb<EMAIL_ADDRESS>

This change breaks the rolling_update.yml Playbook. Intentional?

@mwheckmann you're right, my mistake going to revert this.

@mwheckmann I'm currently on PTO, would you mind doing a PR for this? Otherwise this will have to wait next week...

Hi there, I was actually on PTO too :). Thanks for fixing this.

@mwheckmann np :)


Fix return value and type signature of shell_completion.add_completion_class function

Decorators should return a possibly modfiied version of the original type. Hence, add_completion_class should return cls rather than merely None. This conforms to Python conventions, and allows type checking to work properly.
Checklist:

[ ] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[ ] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[ ] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

Pre-commit check failures seem to concern pre-existing issues.

Hi @davidism. Is this okay for you?

Hey @alexreg , thanks for the PR.
While this PR is pretty straight-forward, you didn't include any tests to verify it.
Can you add some tests to check that everything works smoothly?

@saroad2 Sure. I added a couple of tests for the return value.

Hey @alexreg , thank you for reposing my review. I'm glad I was able to introduce you to new concepts.
I've added some small tweaks to your PR, mainly a small refactoring for the fixture, elaboration on the steps of the tests you wrote, and add one more test about using add_completion_class with the name parameter.
Happily merging the PR and hope to see your contributions again in the future!

@saroad2 Looks good, re the tests. I'm not sure why I treated the dict like a value type in the fixture, but glad you fixed that too... Cheers.


getters and setters

How can I set getters and setters in sequelize-typescript ?
http://docs.sequelizejs.com/manual/tutorial/models-definition.html#getters-setters

sorry, that seems to be clear in doc
i did not search enough


Install source instructions don't include Go dependencies

This is my first time using go, so let me know if I'm just being stupid, but I get a dependencies error when trying to compile the source following instructions in the readme:
laptop:alfred-bullet cybrosis$ make workflow
mkdir -p ./build
go build -o ./build/alfred-bullet
alfred-bullet.go:12:2: cannot find package "github.com/mitsuse/pushbullet-go" in any of:
	/usr/local/go/src/github.com/mitsuse/pushbullet-go (from $GOROOT)
	/Users/cybrosis/work/src/github.com/mitsuse/pushbullet-go (from $GOPATH)
alfred-bullet.go:13:2: cannot find package "github.com/mitsuse/pushbullet-go/requests" in any of:
	/usr/local/go/src/github.com/mitsuse/pushbullet-go/requests (from $GOROOT)
	/Users/cybrosis/work/src/github.com/mitsuse/pushbullet-go/requests (from $GOPATH)
alfred-bullet.go:14:2: cannot find package "github.com/mitsuse/pushbullet-go/responses" in any of:
	/usr/local/go/src/github.com/mitsuse/pushbullet-go/responses (from $GOROOT)
	/Users/cybrosis/work/src/github.com/mitsuse/pushbullet-go/responses (from $GOPATH)
alfred-bullet.go:15:2: cannot find package "github.com/pascalw/go-alfred" in any of:
	/usr/local/go/src/github.com/pascalw/go-alfred (from $GOROOT)
	/Users/cybrosis/work/src/github.com/pascalw/go-alfred (from $GOPATH)
make: *** [build] Error 1

I had to clone these projects to get it to compile.  Commands executed from $GOPATH/src/github.com
git clone https://github.com/mitsuse/pushbullet-go.git mitsuse/pushbullet-go
git clone https://github.com/pascalw/go-alfred.git pascalw/go-alfred
Now it compiles:
laptop:alfred-bullet cybrosis$ make workflow
mkdir -p ./build
go build -o ./build/alfred-bullet
mkdir -p ./tmp
rm -rf ./tmp/workflow
cp -Rp ./workflow ./tmp/workflow
cp -fp ./build/alfred-bullet ./tmp/workflow/alfred-bullet
perl -ne 's/README_INSERTION/`cat README.md`/e;print' ./workflow/info.plist > ./tmp/workflow/info.plist
cd ./tmp/workflow && zip -r AlfredBullet.alfredworkflow *
  adding: alfred-bullet (deflated 70%)
  adding: icon.png (deflated 36%)
  adding: info.plist (deflated 71%)
mv ./tmp/workflow/AlfredBullet.alfredworkflow ./build/AlfredBullet.alfredworkflow

Fixed in 8a5c50e6e532ae8a1e5abc0d922252c06a06c6ae, thanks


add registration status endpoint

This change adds the /registrations/status endpoint in the users resource.
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[X] I acknowledge that all my contributions will be made under the project's license.

Thanks for your patience @miguelgrinberg - if you rebase against master the tests have been fixed!

@robinske All green now. Thanks!

Updated the docs, creating the release now! https://www.twilio.com/docs/authy/api/users?code-sample=code-get-no-pii-user-registration-status-5&code-language=Python&code-sdk-version=default


Remove flake-utils

This project isn’t doing anything fancy or useful with flake-utils. It can be replaced with lib.genAttrs which would remove polluting all downstream users’ flake.lock with a dependency that now requires auditing.

That should be done with commit d480050658c3721a87f8cd011df49a686f93363f.


Can't join chat on Android 6 (Nexus 6)

I have found issue when I try to run this demo on Android 6. "Join" button make no effect. On my Samsung Note 2 (Android 4.4.2) chat works like a charm.
Here is log:

/com.github.nkzawa.socketio.androidchat W/System: ClassLoader referenced unknown path: /data/app/com.github.nkzawa.socketio.androidchat-2/lib/arm

/com.github.nkzawa.socketio.androidchat D/OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true

/com.github.nkzawa.socketio.androidchat I/Adreno: **QUALCOMM build                   : 52af4d2, I8366cd0437
Build Date                       : 10/20/15
OpenGL ES Shader Compiler Version: XE<IP_ADDRESS>
Local Branch                     : M14
Remote Branch                    :
Remote Branch                    :
Reconstruct Branch               : **

/com.github.nkzawa.socketio.androidchat I/OpenGLRenderer: Initialized EGL, version 1.4

Update io.socket version didn't help
compile ('io.socket:socket.io-client:0.7.0') {         exclude group: 'org.json', module: 'json'     }

I have found issue in activity-fragment interrelation. If someone needs - ask me and I'll prepare fix. Seems this repo is not supported any more so fix on demand.

@ervinmartirosyan This repo is still active, thanks for your report!

@ervinmartirosyan Can you explain your fix for this?

As far as I can remember the issue is in LoginActivity:setResult and receiving result in MainFragment:onActivityResult Unfortunately I can't to tell you more details now (need debug). I'm sure that login functionality can be replaced to dialog and everything would works fine (as hotfix). I'm going to prepare pull request with fix till Sunday 17.04.16.

@ervinmartirosyan hi could youe send message to specific user by this library?

@tux-world sorry, there wasn't this case in my requirements so I didn't met your issue with message to specific user

there is no problem on my android 6 phone using this example


Feature/player frame combat

Moved attack icon and adjusted player frame glow to reflect Dragonflight

Hey,
good fix for the StatusTexture, looks way better! But i found multiple issues:

Module.ChangePlayerframe() is not the right place for the status hook, because the function gets called often (e.g. every target change), so it will get hooked multiple times.
I guess you looked at the blizzard code (judging from the code structure and variable names^^), but i would say it would be easier to just hook into PlayerFrame_UpdateStatus().
Also vehicles could break the the status (the original code has if ( UnitHasVehiclePlayerFrameUI("player") ) then ...)
Module.inCombat and  Module.onHateList not really used; only inside the hook, but the other function uses PlayerFrame.inCombat and PlayerFrame.onHateList

My own code is not really great most of the time (evolved from hacking together things to really understanding the blizzard code), but i try to stay as near as possible to the original code.  I'm working on improving the code qualitiy, and removing unnecessary code.
I merged my latest changes, and started working on fixing the issues i wrote about, will commit after more tests.

I think i found a good way to keep the code clean.
Feel free to check my changes and send a new PR if necessary.


Fix TabBar tab indicator stretch effect

fixes [Material3] TabBar indicator stretch effect behaving weirdly with long tabs
This PR fixes the tab indicator stretch effect, it currently stretches from both sides.  After the fix, tab indicator stretches depending on next size of the indicator and direction of the scroll.
The fix is based on Android Components implementation of the elastic/stretch effect.
https://github.com/material-components/material-components-android/blob/20f92dfb513916d0df6c38bfd630dfc41aff484e/lib/java/com/google/android/material/tabs/ElasticTabIndicatorInterpolator.java#L46-L78
Code sample

expand to view the code sample
import 'package:flutter/gestures.dart';
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: ScrollConfiguration(
        behavior: ScrollConfiguration.of(context)
            .copyWith(dragDevices: <PointerDeviceKind>{
          PointerDeviceKind.touch,
          PointerDeviceKind.mouse,
        }),
        child: DefaultTabController(
          length: 8,
          child: Scaffold(
            appBar: AppBar(
              bottom: const TabBar(
                isScrollable: true,
                tabAlignment: TabAlignment.start,
                tabs: <Widget>[
                  Tab(text: 'Home'),
                  Tab(text: 'Search'),
                  Tab(text: 'Add'),
                  Tab(text: 'Favorite'),
                  Tab(text: 'The longest text...'),
                  Tab(text: 'Short'),
                  Tab(text: 'Longer text...'),
                  Tab(text: 'Profile'),
                ],
              ),
            ),
            body: const TabBarView(
              children: <Widget>[
                Center(child: Text('Page')),
                Center(child: Text('Page')),
                Center(child: Text('Page')),
                Center(child: Text('Page')),
                Center(child: Text('Page')),
                Center(child: Text('Page')),
                Center(child: Text('Page')),
                Center(child: Text('Page')),
              ],
            ),
          ),
        ),
      ),
    );
  }
}

Before
https://github.com/flutter/flutter/assets/48603081/0e7c9323-fe05-4f5f-8a72-51b76e7fe86b
After
https://github.com/flutter/flutter/assets/48603081/6389d14a-ff0a-4a1c-8751-502f2de94437
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@Piinks
Great observation, the issue might be that i used to trackpad to test in the videos. I'll put some real device comparison and see if it really glitches.

@Piinks Great observation, the issue might be that i used to trackpad to test in the videos. I'll put some real device comparison and see if it really glitches.

I tested this closely on desktop and mobile. This happens when you tap the before the tab indicator indications is completed and swipe tab animation is interrupted. This also happens without this PR too, it's not a bug from this PR.

In the next PR. adding a way customize this stretch/elastic tab indicator animation so user can choose to use linear tab indicator animation as part of another issue. https://github.com/flutter/flutter/issues/150508
https://github.com/flutter/flutter/assets/48603081/de147c28-d9ab-4c45-89a1-927cec443d5f


Don't display "deleted" SHARDS

If a shard's "owning" shard group has been marked as deleted, the shard is, or soon will be, deleted. So don't list shards that are effectively deleted.
The constant for minimum retention policy was also duplicated in the code, and this was a mistake. This PR also fixes that, setting the constant in one place.
Fixes issue 4709.

@corylanou @benbjohnson

+1


doesn't work on vscode last version

doesn't work i test  on vscode Version: 1.84.2  last version
comment single line  // not have color

Fix with https://github.com/edwinhuish/better-comments-next/commit/8a9a80b7df355c401a36c257f3fc11a936a8cb91