core-js problems with 2.5.0

Version
v2.5.0
Reproduction link
http://not-needed.com
Steps to reproduce
Do the fresh install of the Nuxt(via cli) with the following options:

Project name project
Project description Cool project
Use a custom server framework none
Choose features to install Axios
Use a custom UI framework element-ui
Use a custom test framework none
Choose rendering mode Universal
Author name Andrew Gorpenko
Choose a package manager npm

After running the npm run dev I am getting the error:
 ERROR  Failed to compile with 3 errors

These dependencies were not found:
* core-js/library/fn/object/assign in ./node_modules/babel-runtime/core-js/object/assign.js
* core-js/library/fn/symbol in ./node_modules/babel-runtime/core-js/symbol.js
* core-js/library/fn/symbol/iterator in ./node_modules/babel-runtime/core-js/symbol/iterator.js

What is expected ?
Clean install without errors
What is actually happening?
Fails to compile because of missing dependencies

This bug report is available on Nuxt community (#c8883)

We are having similar issues with upgrading from 2.4.5 to 2.5.0 when building the BootstrapVue docs:
SyntaxError: Unexpected token export
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:617:28)
    at Object.Module._extensions..js (module.js:664:10)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at r (/root/bootstrap-vue/node_modules/vue-server-renderer/build.dev.js:9295:16)
    at Object.<anonymous> (webpack:/external "@babel/runtime/helpers/esm/asyncToGenerator":1:0)
    at o (webpack/bootstrap:36:0)
    at Module.<anonymous> (.nuxt/middleware.js:1:19)
    at o (webpack/bootstrap:36:0)
    at Object.<anonymous> (node_modules/@nuxt/webpack/node_modules/core-js/internals/own-keys.js:4:43)
    at o (webpack/bootstrap:36:0)

And getting warning about core-js version not being specified:
WARNING: We noticed you're using the useBuiltIns option without declaring a core-js version.
Currently, we assume version 2.x when no version is passed. Since this default version will
likely change in future versions of Babel, we recommend explicitly setting the core-js
version you are using via the corejs option.

You should also be sure that the version you pass to the corejs option matches the version
specified in your package.json's dependencies section. If it doesn't, you need to run one
of the following commands:

  npm install --save core-js@2    npm install --save core-js@3
  yarn add core-js@2              yarn add core-js@3

@andrewgorpenko try:
~/plugins/element-ui.js
import Vue from 'vue'
import Element from 'element-ui**/lib**'
import locale from 'element-ui/lib/locale/lang/en'

export default () => {
  Vue.use(Element, { locale })
}

as temporary solution, while element-ui a plugin for nuxt not updated

This works fine with this temporary fix, thanks.

Thanks for reporting issues. All inconsistencies should be resolved with v2.5.1. Please upgrade and ping us if still, any problem exists regarding core-js.

Hey @pi0 Thanks for everything and the quick response.
Still getting a lot of core-js issues with v2.5.1 upgrade.

@digitalcrafted Do you have a babel.config.js or .babelrc file in your project? Otherwise is there any chance you can share the project with us or giving more details?
PS: Cleaning up yarn.lock/package-lock.js may help.

Thanks @pi0  => Cleaning up package-lock.js did it.

I am still getting the same errors... removed everything node_modules, .nuxt, yarn.lock, tried with npm instead of yarn and still am getting this error.
I already checked file by file from a clean npx create-nuxt-app install and all files are ok, including the package.json and .babelrc

@rodrigopedra Can you please manually add core-js@2 in your project?

Tried and still getting the same error, below are my package.json dependencies (with core-js added):
{
"dependencies": {
    "@nuxtjs/auth": "^4.5.3",
    "@nuxtjs/axios": "^5.3.6",
    "@nuxtjs/dotenv": "^1.3.0",
    "@nuxtjs/proxy": "^1.3.3",
    "@nuxtjs/pwa": "^2.6.0",
    "axios": "^0.18.0",
    "core-js": "2",
    "cross-env": "^5.2.0",
    "date-fns": "^1.30.1",
    "nuxt": "^2.4.0",
    "portal-vue": "^1.5.1",
    "vue-avatar": "^2.1.7",
    "vue-svg-loader": "^0.12.0"
  },
  "devDependencies": {
    "@nuxtjs/eslint-config": "^0.0.1",
    "@vue/test-utils": "^1.0.0-beta.27",
    "babel-core": "7.0.0-bridge.0",
    "babel-eslint": "^8.2.1",
    "babel-jest": "^23.6.0",
    "email-validator": "^2.0.4",
    "eslint": "^5.0.1",
    "eslint-config-prettier": "^3.1.0",
    "eslint-config-standard": ">=12.0.0",
    "eslint-loader": "^2.0.0",
    "eslint-plugin-import": ">=2.14.0",
    "eslint-plugin-jest": ">=21.24.1",
    "eslint-plugin-node": ">=7.0.1",
    "eslint-plugin-prettier": "2.6.2",
    "eslint-plugin-promise": ">=4.0.1",
    "eslint-plugin-standard": ">=4.0.0",
    "eslint-plugin-vue": "^5.2.0",
    "jest": "^23.6.0",
    "node-sass": "^4.11.0",
    "nodemon": "^1.18.9",
    "prettier": "1.14.3",
    "sass": "^1.17.0",
    "sass-loader": "^7.1.0",
    "vue-jest": "^3.0.2"
  }
}

@rodrigopedra I tried provided package.json locally and it was working fine. What error do you get? Is it related to a specific library? Sharing full error may help.

@pi0 I have the same issue with v2.5.1.
I exec npm run dev and print errors like below.
ERROR  Failed to compile with 452 errors                                                                                friendly-errors 19:47:28

These dependencies were not found:                                                                                friendly-errors 19:47:28
                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.concat in ./.nuxt/utils.js, ./.nuxt/auth/utilities.js and 14 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.fill in ./node_modules/vuetify/lib/components/VDatePicker/VDatePickerMonthTable.js, ./node_modules/vuetify/lib/components/VExpansionPanel/VExpansionPanel.js and 1 other            friendly-errors 19:47:28
* core-js/modules/es.array.filter in ./.nuxt/client.js, ./.nuxt/components/nuxt-link.client.js and 14 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.find in ./.nuxt/client.js, ./.nuxt/nuxt-i18n/plugin.main.js and 10 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.find-index in ./node_modules/vuetify/lib/components/VExpansionPanel/VExpansionPanel.js, ./node_modules/vuetify/lib/components/VItemGroup/VItemGroup.js and 4 others                 friendly-errors 19:47:28
* core-js/modules/es.array.flat in ./node_modules/vuetify/lib/components/VBtn/VBtn.js, ./node_modules/vuetify/lib/components/VCard/VCard.js and 2 others                                                       friendly-errors 19:47:28
* core-js/modules/es.array.from in ./node_modules/vuetify/lib/components/VCalendar/VCalendarWeekly.js, ./node_modules/vuetify/lib/components/VDataTable/mixins/head.js and 10 others                           friendly-errors 19:47:28
* core-js/modules/es.array.includes in ./.nuxt/client.js, ./.nuxt/auth/auth.js and 18 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.iterator in ./.nuxt/client.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.join in ./.nuxt/utils.js, ./.nuxt/auth/utilities.js and 10 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.map in ./.nuxt/client.js, ./.nuxt/auth/utilities.js and 24 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.slice in ./.nuxt/utils.js, ./.nuxt/auth/utilities.js and 10 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.array.splice in ./node_modules/vuetify/lib/components/VCombobox/VCombobox.js, ./node_modules/vuetify/lib/components/VExpansionPanel/VExpansionPanel.js and 5 others                       friendly-errors 19:47:28
* core-js/modules/es.array.unscopables.flat in ./node_modules/vuetify/lib/components/VBtn/VBtn.js, ./node_modules/vuetify/lib/components/VCard/VCard.js and 2 others                                           friendly-errors 19:47:28
* core-js/modules/es.function.name in ./.nuxt/client.js, ./.nuxt/auth/schemes/oauth2.js and 13 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.map in ./node_modules/vuetify/lib/components/VSelect/VSelect.js, ./node_modules/vuetify/lib/components/VTreeview/VTreeview.js                                                             friendly-errors 19:47:28
* core-js/modules/es.math.cbrt in ./node_modules/vuetify/lib/util/color/transformCIELAB.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.math.sign in ./node_modules/vuetify/lib/components/VDatePicker/VDatePickerDateTable.js, ./node_modules/vuetify/lib/components/VTimePicker/VTimePickerClock.js                             friendly-errors 19:47:28
* core-js/modules/es.number.constructor in ./node_modules/vuetify/lib/components/VAvatar/VAvatar.js, ./node_modules/vuetify/lib/components/VBottomNav/VBottomNav.js and 43 others                              friendly-errors 19:47:28
* core-js/modules/es.number.max-safe-integer in ./node_modules/vuetify/lib/components/VCalendar/VCalendarWeekly.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.number.to-fixed in ./node_modules/vuetify/lib/components/VSlider/VSlider.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.object.assign in ./.nuxt/client.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.object.freeze in ./node_modules/vuetify/lib/util/colors.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.object.is-extensible in ./node_modules/vuetify/lib/util/helpers.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.object.keys in ./.nuxt/utils.js, ./.nuxt/auth/utilities.js and 5 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.object.to-string in ./.nuxt/client.js, ./.nuxt/auth/auth.js and 25 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.object.values in ./.nuxt/auth/utilities.js, ./node_modules/vuetify/lib/components/VForm/VForm.js and 1 other                                                                              friendly-errors 19:47:28
* core-js/modules/es.promise in ./.nuxt/client.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.promise.finally in ./.nuxt/client.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.regexp.constructor in ./.nuxt/utils.js, ./.nuxt/nuxt-i18n/plugin.main.js and 1 other                                                                                friendly-errors 19:47:28
* core-js/modules/es.regexp.to-string in ./.nuxt/utils.js, ./.nuxt/nuxt-i18n/plugin.main.js and 14 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.set in ./node_modules/vuetify/lib/components/VTreeview/VTreeview.js, ./node_modules/vuetify/lib/mixins/data-iterable.js                                                                   friendly-errors 19:47:28
* core-js/modules/es.string.ends-with in ./node_modules/vuetify/lib/components/VCombobox/VCombobox.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.fixed in ./node_modules/vuetify/lib/components/VBottomNav/VBottomNav.js, ./node_modules/vuetify/lib/components/VBtn/VBtn.js and 5 others                                           friendly-errors 19:47:28
* core-js/modules/es.string.includes in ./.nuxt/client.js, ./.nuxt/auth/auth.js and 11 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.iterator in ./.nuxt/utils.js, ./.nuxt/auth/auth.js and 20 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.link in ./node_modules/vuetify/lib/components/VBtn/VBtn.js, ./node_modules/vuetify/lib/components/VTabs/VTab.js                                                                    friendly-errors 19:47:28
* core-js/modules/es.string.match in ./.nuxt/client.js, ./.nuxt/nuxt-i18n/middleware.js and 4 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.pad-start in ./node_modules/vuetify/lib/components/VDatePicker/VDatePickerDateTable.js                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.repeat in ./.nuxt/utils.js, ./node_modules/vuetify/lib/components/VDatePicker/util/pad.js and 1 other                                                                              friendly-errors 19:47:28
* core-js/modules/es.string.replace in ./.nuxt/utils.js, ./.nuxt/auth/auth.js and 8 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.search in ./.nuxt/utils.js, ./.nuxt/auth/schemes/oauth2.js and 2 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.small in ./node_modules/vuetify/lib/components/VBtn/VBtn.js, ./node_modules/vuetify/lib/components/VChip/VChip.js and 3 others                                                     friendly-errors 19:47:28
* core-js/modules/es.string.split in ./.nuxt/utils.js, ./.nuxt/auth/utilities.js and 10 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.starts-with in ./.nuxt/utils.js, ./node_modules/vuetify/lib/components/VGrid/grid.js and 3 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.string.trim in ./node_modules/vuetify/lib/components/VAutocomplete/VAutocomplete.js, ./node_modules/vuetify/lib/components/VAvatar/VAvatar.js and 13 others                               friendly-errors 19:47:28
* core-js/modules/es.symbol in ./.nuxt/axios.js, ./.nuxt/auth/auth.js and 13 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.symbol.description in ./.nuxt/axios.js, ./.nuxt/auth/auth.js and 13 others                                                                                friendly-errors 19:47:28
* core-js/modules/es.symbol.iterator in ./.nuxt/client.js, ./.nuxt/auth/auth.js and 12 others                                                                                friendly-errors 19:47:28
* core-js/modules/web.dom-collections.for-each in ./.nuxt/client.js, ./.nuxt/components/nuxt-child.js and 5 others                                                                                friendly-errors 19:47:28
* core-js/modules/web.dom-collections.iterator in ./.nuxt/axios.js, ./.nuxt/auth/auth.js and 12 others                                                                                friendly-errors 19:47:28
                                                                                friendly-errors 19:47:28
To install them, you can run: npm install --save core-js/modules/es.array.concat core-js/modules/es.array.fill core-js/modules/es.array.filter core-js/modules/es.array.find core-js/modules/es.array.find-index core-js/modules/es.array.flat core-js/modules/es.array.from core-js/modules/es.array.includes core-js/modules/es.array.iterator core-js/modules/es.array.join core-js/modules/es.array.map core-js/modules/es.array.slice core-js/modules/es.array.splice core-js/modules/es.array.unscopables.flat core-js/modules/es.function.name core-js/modules/es.map core-js/modules/es.math.cbrt core-js/modules/es.math.sign core-js/modules/es.number.constructor core-js/modules/es.number.max-safe-integer core-js/modules/es.number.to-fixed core-js/modules/es.object.assign core-js/modules/es.object.freeze core-js/modules/es.object.is-extensible core-js/modules/es.object.keys core-js/modules/es.object.to-string core-js/modules/es.object.values core-js/modules/es.promise core-js/modules/es.promise.finally core-js/modules/es.regexp.constructor core-js/modules/es.regexp.to-string core-js/modules/es.set core-js/modules/es.string.ends-with core-js/modules/es.string.fixed core-js/modules/es.string.includes core-js/modules/es.string.iterator core-js/modules/es.string.link core-js/modules/es.string.match core-js/modules/es.string.pad-start core-js/modules/es.string.repeat core-js/modules/es.string.replace core-js/modules/es.string.search core-js/modules/es.string.small core-js/modules/es.string.split core-js/modules/es.string.starts-with core-js/modules/es.string.trim core-js/modules/es.symbol core-js/modules/es.symbol.description core-js/modules/es.symbol.iterator core-js/modules/web.dom-collections.for-each core-js/modules/web.dom-collections.iterator

Hi @pi0 thanks for the patience, here is the browser output:
SyntaxError
Unexpected token export

vm.js:80:10
createScript

vm.js:139:10
Object.runInThisContext

module.js:617:28
Module._compile

module.js:664:10
Module._extensions..js

module.js:566:32
Module.load

module.js:506:12
tryModuleLoad

module.js:498:3
Module._load

module.js:597:17
Module.require

internal/module.js:11:18
require

webpack:/external "@babel/runtime/helpers/esm/defineProperty":1:
Object.@babel/runtime/helpers/esm/defineProperty

webpack/bootstrap:25:
__webpack_require__

server.js:8327:99
Module../services/AuthService.js

webpack/bootstrap:25:
__webpack_require__

store/users.js:1:
Module../store/users.js

webpack/bootstrap:25:
__webpack_require__

The only userland file it is complaining about is a store. I checked this store in my code and it imports a class that defined a static property. Maybe some change disallowed this feature.
These are the changes I made in my code, in case someone faces the same issue:
Before
// /store/users.js
import AuthService from '@/services/AuthService';

// state, mutations, actions, ...

export const getters = {
    socialLoginUrl() {
        return AuthService.SOCIAL_LOGIN_URL;
    },
};

// /sevice/AuthService.js

export default class AuthService {
    static SOCIAL_LOGIN_URL = '/social/login'; // this is where the error occurs

    // other class methods
}

After
// /store/users.js
import AuthService, { SOCIAL_LOGIN_URL } from '@/services/AuthService';

// state, mutations, actions, ...

export const getters = {
    socialLoginUrl() {
        return SOCIAL_LOGIN_URL;
    },
};

// /sevice/AuthService.js
export const SOCIAL_LOGIN_URL = '/social/login'; // no more errors

export default class AuthService {
    // other class methods
}

@rodrigopedra I've seen similar "Unexpected token export" error in projects having babel.config.js file. Do you have one? And if yes, can you please remove if it to see it works?

The only babel file I have is the .babelrc generated by create-nuxt-app
Sorry if I wasn't clear before, but I got it working from changing the static class constant to a named const export.
See the before and after in my previous comment, after this change everything is working for me.

I fixed that with npm install --save-dev core-js@2

So now I'm stick with 2.5.0 if we "need" to stay with core-js3.0? This is kind of unsatisfying. Could we solve this somehow by a "flag" to use core js 3 via "opt in"?

@simllll 2.5.1 rollbacked core-js 2

I also reported a similar mistake.
Failed to compile with 6 errors                                                                                friendly-errors 17:51:56
These dependencies were not found:                                                                                friendly-errors 17:51:56
friendly-errors 17:51:56

core-js/library/fn/get-iterator in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                               friendly-errors 17:51:56
core-js/library/fn/is-iterable in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                                friendly-errors 17:51:56
core-js/library/fn/object/assign in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                             friendly-errors 17:51:56
core-js/library/fn/object/keys in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                                friendly-errors 17:51:56
core-js/library/fn/symbol in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                                friendly-errors 17:51:56
core-js/library/fn/symbol/iterator in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                         friendly-errors 17:51:56
friendly-errors 17:51:56
To install them, you can run: npm install --save core-js/library/fn/get-iterator core-js/library/fn/is-iterable core-js/library/fn/object/assign core-js/library/fn/object/keys core-js/library/fn/symbol core-js/library/fn/symbol/iterator

this is the package.json
"dependencies": {
    "axios": "^0.18.0",
    "element-ui": "^2.4.11",
    "js-cookie": "^2.2.0",
    "nuxt": "2.5.0",
    "nuxt-clipboard2": "^0.2.1",
    "nuxt-stripe-module-https": "^1.0.0",
    "rollup": "^0.67.4",
    "vant": "^1.4.2",
    "vue-i18n": "^8.3.1",
    "vue-lazyload": "^1.2.6",
    "vue-paypal-checkout": "^3.2.0",
    "vue-social-sharing": "^2.3.3",
    "vuex-persistedstate": "^2.5.4"
  },
  "devDependencies": {
    "@nuxtjs/axios": "^5.3.4",
    "@vue/test-utils": "^1.0.0-beta.29",
    "autoprefixer": "^9.3.1",
    "babel-core": "^6.26.3",
    "babel-eslint": "^10.0.1",
    "babel-jest": "^24.7.1",
    "babel-plugin-component": "^1.1.1",
    "babel-plugin-import": "^1.11.0",
    "babel-preset-env": "^1.7.0",
    "babel-preset-es2015": "^6.24.1",
    "cross-env": "^5.2.0",
    "eslint": "^4.19.1",
    "eslint-friendly-formatter": "^4.0.1",
    "eslint-loader": "^2.1.1",
    "eslint-plugin-vue": "^4.0.0",
    "identity-obj-proxy": "^3.0.0",
    "jest": "^24.7.1",
    "jest-transform-stub": "^2.0.0",
    "node-sass": "^4.10.0",
    "nuxt-sass-resources-loader": "^2.0.5",
    "postcss-pxtorem": "^4.0.1",
    "sass-loader": "^7.1.0",
    "vue-jest": "^3.0.4"
  }

I also reported a similar mistake.
Failed to compile with 6 errors friendly-errors 17:51:56
These dependencies were not found: friendly-errors 17:51:56
friendly-errors 17:51:56

core-js/library/fn/get-iterator in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                               friendly-errors 17:51:56
core-js/library/fn/is-iterable in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                                friendly-errors 17:51:56
core-js/library/fn/object/assign in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                             friendly-errors 17:51:56
core-js/library/fn/object/keys in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                                friendly-errors 17:51:56
core-js/library/fn/symbol in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                                friendly-errors 17:51:56
core-js/library/fn/symbol/iterator in ./node_modules/_babel-runtime<EMAIL_ADDRESS>                                                                         friendly-errors 17:51:56
friendly-errors 17:51:56
To install them, you can run: npm install --save core-js/library/fn/get-iterator core-js/library/fn/is-iterable core-js/library/fn/object/assign core-js/library/fn/object/keys core-js/library/fn/symbol core-js/library/fn/symbol/iterator

this is the package.json
"dependencies": {
    "axios": "^0.18.0",
    "element-ui": "^2.4.11",
    "js-cookie": "^2.2.0",
    "nuxt": "2.5.0",
    "nuxt-clipboard2": "^0.2.1",
    "nuxt-stripe-module-https": "^1.0.0",
    "rollup": "^0.67.4",
    "vant": "^1.4.2",
    "vue-i18n": "^8.3.1",
    "vue-lazyload": "^1.2.6",
    "vue-paypal-checkout": "^3.2.0",
    "vue-social-sharing": "^2.3.3",
    "vuex-persistedstate": "^2.5.4"
  },
  "devDependencies": {
    "@nuxtjs/axios": "^5.3.4",
    "@vue/test-utils": "^1.0.0-beta.29",
    "autoprefixer": "^9.3.1",
    "babel-core": "^6.26.3",
    "babel-eslint": "^10.0.1",
    "babel-jest": "^24.7.1",
    "babel-plugin-component": "^1.1.1",
    "babel-plugin-import": "^1.11.0",
    "babel-preset-env": "^1.7.0",
    "babel-preset-es2015": "^6.24.1",
    "cross-env": "^5.2.0",
    "eslint": "^4.19.1",
    "eslint-friendly-formatter": "^4.0.1",
    "eslint-loader": "^2.1.1",
    "eslint-plugin-vue": "^4.0.0",
    "identity-obj-proxy": "^3.0.0",
    "jest": "^24.7.1",
    "jest-transform-stub": "^2.0.0",
    "node-sass": "^4.10.0",
    "nuxt-sass-resources-loader": "^2.0.5",
    "postcss-pxtorem": "^4.0.1",
    "sass-loader": "^7.1.0",
    "vue-jest": "^3.0.4"
  }

remove .nuxt

For the benefit of people coming here from search engine, this error can trigger depending on what dependencies one has installed and can be fixed by explicitly installing core-js@2 dependency.

Here is the solution:
https://nuxtjs.org/guide/release-notes#core-js


Reverted commits should remove 2 commit mentions instead of one

The flow is normally:
Bunch of work
Commit
https://www.youtube.com/watch?v=1EBfxjSFAxQ
Revert
Bunch of work
Commit
When it finally goes in, it should be counted as 1 and now I think it's counted as 2.

I'm not sure if I understand this code but it looks like:
%x[#{git_command}].split("\n").each do |c|
  if c.index('Revert') == 0 then
    reverts.push(c.scan(/#([0-9]+)/))
  else
    commits.push(c)
  end
end

If it finds a reverted commit then it never counts that commit, so later it removes the reverted commit from the count.

Finally was able to install and run it.
This is how a revert process normally looks like
git log --pretty=oneline | grep 1425330
e5fe68e2a0eb427e3cab8ea6f6d5e7643b1aba98 Issue #1425330 by swentel, grendzy, davereid, wojtha, c960657: Fixed Apply Aggregator and OpenID fixes from DRUPAL-SA-CORE-2012-001.
28b68ad75dc627ec278397bf3a1fe36628ffb6c0 Revert "Issue #1425330 by swentel, grendzy, davereid, wojtha, c960657: Fixed Apply Aggregator and OpenID fixes from DRUPAL-SA-CORE-2012-001."
c3fa160dca988c221d7a34c327fd8c81a4df2483 Issue #1425330 by swentel, grendzy, davereid, wojtha, c960657: Fixed Apply Aggregator and OpenID fixes from DRUPAL-SA-CORE-2012-001.

So when a revert process happens in a normal way - or at least with an issue number -, the commit is counted twice because only the revert is being removed from the count and what is expected is that both the Revert and the original commit should be "discounted".
Another thing that is happening is that we're taking into account commits without issue number, and those are mostly coming from merges from VDC and DBTNG, and there's no need to evaluate those because they don't have "by" or anything (another discussion would be if the git author of that commit should be added to the count).
PR's coming soon :)


[FEATURE REQ] Need to format the result from ConversationAnalysisClient response

Library name
Azure AI services
Please describe the feature.
We are using Orchestrator workflow of Custom question answering service for connecting to multiple Question answering service.
We are fetching the predictions using ConversationAnalysisClient. The response contains all data but to access the values we need to use json.
Question answering is returning the data in KnowledgeBaseAnswer format which is easy to access.
Is there any possibility to develop a similar structure for fetching the response from Orchester for Question answering, Luis and Conversational analysis

@Aiswarya1794 Thanks for reaching out to us and reporting this issue. It seems like you are asking if there is a way to develop a similar structure for fetching the response from Orchestrator for Question answering, Luis, and Conversational analysis.
I'm not entirely sure what you mean by "similar structure". Could you please provide more information or clarify your question?

For AI.Language.QuestionAnswering, its returning the response as list of Question Answers
public virtual Task<Response> GetAnswersAsync(string question, QuestionAnsweringProject project, AnswersOptions options = null, CancellationToken cancellationToken = default) =>
GetAnswersAsync(project, (options ?? new()).WithQuestion(question), cancellationToken);
This answer result contains the list of KnowledgeBaseAnswer and this contains knowledge base answer in the below class staructure.
internal KnowledgeBaseAnswer(IReadOnlyList questions, string answer, double? confidence, int? qnaId, string source, IReadOnlyDictionary<string, string> metadata, KnowledgeBaseAnswerDialog dialog, AnswerSpan shortAnswer)
{
Questions = questions;
Answer = answer;
Confidence = confidence;
QnaId = qnaId;
Source = source;
Metadata = metadata;
Dialog = dialog;
ShortAnswer = shortAnswer;
}
But in case of Orchestrator workflow we are using conversationAnalysisClient for fecthing the data through 'AnalyzeConversationAsync' method and its just returing the method as Task<Response>

From a developer point of view , it will be good if this response can have a similar class structure for accessing the data easily , other wise every time we need to use json parser to parse the data and format for fetching the correct data

Adding Service team to look into this

Currently, the lack of models in Conversations is by design. The Azure SDK across all languages are working on a new way to generate idiomatic models from TypeSpec, and only when a service has authored their service in TypeSpec to mitigate breaking changes. The service team is working on a TypeSpec version of their service, so you can expect models sometime in the near future. Question Answering predates that effort.
To make it easier to work with JSON but have a C# feel, see our samples e.g., https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/cognitivelanguage/Azure.AI.Language.Conversations/samples/Sample2_AnalyzeConversation_OrchestrationPrediction.md#synchronous. You can use ToDynamicFromJson with C#'s dynamic keyword to access JSON properties idiomatically.


Create Mongo DB Storage Implementation

There is a working mongoDB Storage implementation in use on mikevdv.dev but it needs to cleaned up before general release. For a 0.1.0 release of the library, at least one real database implementation should exist.

Released as of now.
https://www.npmjs.com/package/webmention-handler-mongodb


Scholar

👷 Deploy Preview for crpp-ai-oncology processing.

Name
Link

🔨 Latest commit
74de4b38d28befd9d2139bc310d4dd860f991b34

🔍 Latest deploy log
https://app.netlify.com/sites/crpp-ai-oncology/deploys/647a0018721ac700080bbc29


Discovery document improvements

added documentationLink property
@Description for enum constants and fields

Codecov Report

Merging #93 into master will decrease coverage by 0.18%.
The diff coverage is 39.13%.

@@             Coverage Diff              @@
##             master      #93      +/-   ##
============================================
- Coverage     79.47%   79.29%   -0.19%
  Complexity     1621     1621
============================================
  Files           154      154
  Lines          5461     5481      +20
  Branches        703      709       +6
============================================
+ Hits           4340     4346       +6
- Misses          847      855       +8
- Partials        274      280       +6

Impacted Files
Coverage Δ
Complexity Δ

...com/google/api/server/spi/config/model/Schema.java
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

...e/api/server/spi/discovery/DiscoveryGenerator.java
84.76% <22.22%> (-2.87%)
51 <0> (ø)

.../api/server/spi/config/model/SchemaRepository.java
86.36% <50%> (-5.48%)
26 <0> (ø)

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 efe63f3...98145e9. Read the comment docs.

@tangiel @bradfriedman Guys, please have a look. Changes are pretty shallow.
Can you help me to figure out where to add tests to cover changes?

We've split the improvements brought by this PR and added some tests:

#121 for documentation links
#132 for description on resource fields
#133 for description on enum values

Maybe this one should be closed.


techstack

@jain-rishabh-21
I assume we have to develop the project from the start.
Could you please open issues for frontend if you have some designs so front end folks can start building it.
Also forthe blockchain part what tech stack would you prefer to be used.
I had developed a similar type of application, where I used thirdweb and web3.storage (for ipfs).
we can also use other libraries like web3.js or moralis.

Hey Anurag! Yes we need to start this project from the start!
Lets wait till we get the mentors in, and then we can decide! Thanks

Hi @jain-rishabh-21!! I saw this project's stack has AWS in it. I'm a Cloud Computing enthusiast and would love to get involved in the modules of project that are related to AWS. Please let me know how can I get to know more regarding this.
Thanks,
Anushka Saxena.


Show minutes instead of floating number when "total" is less than hour

I have combined three other pull requests here, because it depends on them, to build better looking result.
Previously when you have only one entry with some minutes, it will show 0.33h instead of showing nicer value like 20m. This adds such feature.

Thanks @ReekenX! I will go ahead and merge this and close the other two pull requests then.


Charm goes into error state with KeyError: 'is_ca'

When deploying Charmed 5g SD-Core bundle, the ssc charm goes into error state with the following being observed in the juju debug-log:
unit-self-signed-certificates-0: 12:53:21 ERROR unit.self-signed-certificates/0.juju-log Uncaught exception while in charm code:
Traceback (most recent call last):
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/./src/charm.py", line 313, in <module>
    main(SelfSignedCertificatesCharm)
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/venv/ops/main.py", line 436, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/venv/ops/main.py", line 144, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/venv/ops/framework.py", line 351, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/venv/ops/framework.py", line 853, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/venv/ops/framework.py", line 942, in _reemit
    custom_handler(event)
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/./src/charm.py", line 180, in _configure
    self._process_outstanding_certificate_requests()
  File "/var/lib/juju/agents/unit-self-signed-certificates-0/charm/./src/charm.py", line 198, in _process_outstanding_certificate_requests
    is_ca=request["is_ca"],
KeyError: 'is_ca'

Taken from the matrix convo with Mark:
self-signed-certificates           waiting      1  self-signed-certificates  beta            57  <IP_ADDRESS>  no       installing agent

So this is affecting revison 56 (beta)


[5.1] Allow arrays to be passed to array_pluck and data_get

This has the benefit of:

Allowing you to extract data from arrays whose keys have dots in them.
Considerably speeds up array_pluck, since it won't explode the $key and $value on every iteration.

Are you really using all this collection / array modification stuff or do you just look for things to do in there? :)

@taylorotwell I sure do. I use these features. A. Whole. Lot. I can confidently say that every single one of these changes were as a result of a personal need that I bumped into.
After Eloquent, the collections/helpers are my most used laravel features. I love them, and use them all over the place! The very fist thing I do in a non-laravel project is pull in the illuminate/support package.
P.S. some of these changes (including this one) are in preparation for a bigger feature I've been working on. Just didn't want to dump a single huge PR on you.

:skull:


angular cli dev dependency

Bug Report or Feature Request (mark with an x)
Error: The "@angular/compiler-cli" package was not properly installed.
    at Object.<anonymous> (C:\Users\vic_t\node_modules\@ngtools\webpack\src\index.js:14:11)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\vic_t\node_modules\@angular\cli\tasks\eject.js:10:19)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)

- [ ] bug report -> please search issues before submitting
- [ ] feature request

Versions.
@angular/cli: 1.2.1
node: 6.11.1
os: win32 x64

Repro steps.
ng new my-app
cd my-app
ng serve

The log given by the failure.

$ ng serve
The "@angular/compiler-cli" package was not properly installed.
Error: The "@angular/compiler-cli" package was not properly installed.
at Object. (C:\Users\vic_t\node_modules@ngtools\webpack\src\index.js:14:11)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (C:\Users\vic_t\node_modules@angular\cli\tasks\eject.js:10:19)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
Desired functionality.

Mention any other details that might be useful.

if i do " npm install -g --save-dev @angular/cli@latest"
it serves. but without doing this angular won't serve the project

Having the same issue.

In my setup I have a seperate project for all my devDeps
Until today I was able to seperate all @angular devDeps into this project except angular/cli
If you have the same setup as me, add @angular/compiler-cli back to your project and don't seperate it into a subproject - my app is running again.
I hope this is not getting a standard (forcing people to put all devDeps into their project)
In our environment we got n-apps, all running in a big solution - to keep track of all devDeps per app is a maintenance nightmare...

I have the same issue with those versions:
Versions.
@angular/cli: 1.2.1
npm: 5.0.3
node: 8.1.2
os: Linux 16.04

@angular/compiler-cli is required for Angular CLI to properly work, and you should add it to your dependencies or devDependencies. I'm sorry but this isn't optional.


Unable to work in 'uncurried' mode with rescript v11-beta.2

The following code (as an example) throws gives an error when using this with uncurried: true setting (the default).
@spice
type user = string
@spice
type specDatabases = Js.Dict.t<user>

Setting "uncurried": false in the bsconfig seems to fix the issue - but this isn't the default.

#49
You can test the next version<EMAIL_ADDRESS>

<EMAIL_ADDRESS>

It works fine to me. Can you check your bsconfig.json configuration?
"ppx-flags": [
    [
      "../ppx",
      "-uncurried"
    ]
  ],


Suggestion: More realistic example function

Hi,
after talking about the repo yesterday, I wanted to check it out at night.
Unfortunately being no c++ coder and having no duckdb API/SPI docs available (add link in readme and code?)
it took me about an hour to turn static function with no parameters into something that takes a parameter and is executed for each row of input.
Trying to use the existing extensions as inspiration was only minimally helpful because their internal structure (even the simple excel-format function) was vastly different from the boilerplate function, using the BinaryExecutor for each vectorized chunk of input. And figuring out how to access the content and create and return a string_t was also a lot of searching in the extensions examples. I found it with String::EmptyString(result, size) and them memcpy.
My suggestions would be (here is the PR)

turn it into a kind of "Hello World" function that takes a single string argument
return a friendly message using the argument, e.g. "Hello "+name+"!"
the name boilerplate has negative connotations and is not welcoming
I would make it something friendly and fun, e.g. quack(name) -> "Quack "+name+" 🐥"

Thanks for the changes! i'll reboot the CI as soon the guys over at ubuntu have things working again


Add token to documentation ui

Hello, i installed the package and i don't known where to store the token getting from the login url when i try to fetch data from another url that require authentification token

README


Private artifactory server credentials get passed on to upstream unauthenticated chart repository

Output of helm version:
version.BuildInfo{Version:"v3.6.0", GitCommit:"7f2df6467771a75f5646b7f12afb408590ed1755", GitTreeState:"dirty", GoVersion:"go1.16.4"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:16:14Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"19+", GitVersion:"v1.19.8-eks-96780e", GitCommit:"96780e1b30acbf0a52c38b6030d7853e575bcdf3", GitTreeState:"clean", BuildDate:"2021-03-10T21:32:29Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):  EKS

We have a setup where we are trying to use a virtual artifactory helm repository to proxy to various third-party chart repositories. Our artifactory system is private, and requires credentials. What we have found is that it appears helm always passes along the credentials to every HTTP request in the install command. This leads to an error with at least one repository based in S3 where AWS responds with a 400: Bad Request response. We do not see this issue if we install directly from originating chart repository.
Does it make sense to assume the credentials passed to get the manifest of charts should be continued to be used if the URL is different? The specific lines of code helm is erroring at are https://github.com/helm/helm/blob/main/pkg/getter/httpgetter.go#L59-L61

This is a very good point. One that I was just thinking about last week while thinking about some of the concerns #9762 raises. Thank you for writing this up.
I think there is a general security concern for helm to assume that the credentials used to authenticate with the chart repository API can also be used to fetch the chart itself using the download URL from the index.

Does it make sense to assume the credentials passed to get the manifest of charts should be continued to be used if the URL is different?

In many cases yes. Many organizations may choose to have both the chart repository API and the charts themselves backed by the same authentication endpoints. For example if both are saved in an Azure account and you want them to share the same service principal as they are part of the same "app" or "platform" you're building.
However the case you mention (a chart index pointing at external endpoints, like a public mirror) could be a privacy issue for many users.
An open question here: if both the chart repository and the download URL are saved at different locations but they share the same credentials, how can one pass those credentials onto the secondary fetch? If we solve this problem, then we can start to discuss how to pull apart the repository API from the download URL.
That all being said, the experimental OCI feature is expected to replace the chart repository API moving forward, so it might not be worth spending too much time trying to solve this problem if it's going to be deprecated once that goes GA.

I see, makes sense. My concern is the ability of vendors like Artifactory updating their software to support OCI quickly, or seamlessly. Also, looking into OCI, it doesn't seem to address a proxy/cache situation? At least, not in the way tools like Artifactory, Nexus, and others often implement aggregating remote and local (as in created in that repository system itself) repositories mostly as pass-throughs.
Could a patch that adds a flag to skip that logic block be an acceptable short-term patch? Where by default it does the current behavior?

Also, looking into OCI, it doesn't seem to address a proxy/cache situation? At least, not in the way tools like Artifactory, Nexus, and others often implement aggregating remote and local (as in created in that repository system itself) repositories mostly as pass-throughs.

It's described in the documentation.

fixed in Helm 3.6.1. See https://github.com/helm/helm/security/advisories/GHSA-56hp-xqp3-w2jf.
Thanks for raising this issue.


[Event Request] Table 36 - OnBeforeGetShippingTime

Please add a new integration event OnBeforeGetShippingTime in Table 36.
    procedure GetShippingTime(CalledByFieldNo: Integer)
    var
        ShippingAgentServices: Record "Shipping Agent Services";
+       IsHandled: Boolean;
    begin
+       IsHandled := false;
+       OnBeforeGetShippingTime(Rec, CalledByFieldNo, IsHandled);
+       if IsHandled then
+           exit;
        [...]

New integration event
[IntegrationEvent(false, false)]
local procedure OnBeforeGetShippingTime(var Rec: Record "Sales Header"; CalledByFieldNo: Integer; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


I can't run the test from Readme

On all configurations, the test failed.
Tested on:

win10 x64
and lua:

Lua 5.1.5
LuaJIT 2.1.1695653777
Lua 5.3.6 / due to the increased stack size, the number in the test was not 40000, but 900000

local memoize = require('memoize')

local function tri(x)
  if x == 0 then return 0 end
  return x+tri(x-1)
end

-- print(tri(40000)) -- here we get a stackoverflow, as expected

local memoized_tri = mem(tri)

for i=0, 40000 do
	if i % 1000 == 0 then print(i) end
	memoized_tri(i) -- here we also get a stackoverflow, but it was expected that there wouldn’t be one
end

print(memoized_tri(40000)) -- we'll never get here

I forgot to mention that I tested all the commits in the repository

Memoizing recursive functions is a tad fiddly, because essentially,
once you've memoized a recursive function, you need the function to
call the memoized version instead of the original during the recursion
step.  The README does get this wrong.  Here's how that (probably)
should look.  Apologies in advance if the formatting is terrible.
I'm blind and using the gh CLI on Linux, and I can't attach files to comments.
The raw file can also be found at https://paste.xogium.me/WB.lua.
I made the max value passed to tri insanely large, because I don't
think I can predict what the max stack size will be.
Here on Linux with musl and Lua 5.3.6, it seems to be 499990.
local memoize = require 'memoize'

local tri
tri = function(x)
  if x == 0 then return 0 end
  return x+tri(x-1)
end

local success, errmsg = pcall(
  function()
    print(tri(9999999)) -- stack overflow: too much recursion
    end)

if success then error('Unexpected success')
end
print(errmsg)

tri = memoize(tri) -- now tri "remembers" previous results

print('Seeding cache, this will take a while:')
for i=0, 9999999 do tri(i) end -- seed cache
print('Cache seeded.')

print(tri(9999999)) --<PHONE_NUMBER>0000, instantaneous result


parts database

Fixes #415
If there's a better way to do this, let me know. I thought this was an easy way to ensure the database is generated during the fasm2bels install.

I forgot the runners don't quite work the same way as the lab computers.


Remove unnecessary changing of shortcut name in editor node.

The same effect which was desired here can just be done with set_item_text(...), which is what this PR does. It removes the need to constantly update the shortcut name when the scene menu is opened.
https://user-images.githubusercontent.com/41730826/211192086-b7460eff-9802-4b5e-8cad-b63c5357f02e.mp4

Thanks!


Accept 'selected' as value for source.selected

This fixes #39.

@gauda thanks. Your code failed linting, but I fixed it. If the build passes, we'll merge it.


Using C modules with webpack

I'm submitting a ...  (check one with "x")
[ ] bug report => check the README and search github for a similar issue or PR before submitting
[x] support request => check the README and search github for a similar issue or PR before submitting
[ ] feature request

Current behavior
Everything work great! Untill I try to use any module written on C, I get error, while npm run build:universal-dev:
Error: ./node_modules/node-pre-gyp/lib/node-pre-gyp.js
Module not found: Error: Can't resolve '../package' in '/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/lib'
resolve '../package' in '/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/lib'
  using description file: /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.json (relative path: ./lib)
  after using description file: /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.json (relative path: ./lib)
    using description file: /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.json (relative path: ./package)
      no extension
        /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package doesn't exist
      .ts
        /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.ts doesn't exist
      .js
        /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.js doesn't exist
      as directory
        /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package doesn't exist
[/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package]
[/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.ts]
[/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.js]
[/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package]
 @ ./node_modules/node-pre-gyp/lib/node-pre-gyp.js 62:16-37
 @ ./node_modules/bcrypt/bcrypt.js
 @ ./src/server/api/modules/users/models/users.model.ts
 @ ./src/server/api/modules/users/models/index.ts
 @ ./src/server/api/modules/users/index.ts
 @ ./src/server/api/modules/index.ts
 @ ./src/server/api/index.ts
 @ ./src/server/server.ts

Error: ./node_modules/node-pre-gyp/lib/info.js
Module not found: Error: Can't resolve 'aws-sdk' in '/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/lib'
resolve 'aws-sdk' in '/mnt/c/projects/an-derjava/node_modules/node-pre-gyp/lib'
  Parsed request is a module
  using description file: /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.json (relative path: ./lib)
  after using description file: /mnt/c/projects/an-derjava/node_modules/node-pre-gyp/package.json (relative path: ./lib)
    resolve as module
      looking for modules in /mnt/c/projects/an-derjava/node_modules
        using description file: /mnt/c/projects/an-derjava/package.json (relative path: ./node_modules)
        after using description file: /mnt/c/projects/an-derjava/package.json (relative path: ./node_modules)
          using description file: /mnt/c/projects/an-derjava/package.json (relative path: ./node_modules/aws-sdk)
            no extension
              /mnt/c/projects/an-derjava/node_modules/aws-sdk doesn't exist
            .ts
              /mnt/c/projects/an-derjava/node_modules/aws-sdk.ts doesn't exist
            .js
              /mnt/c/projects/an-derjava/node_modules/aws-sdk.js doesn't exist
            as directory
              /mnt/c/projects/an-derjava/node_modules/aws-sdk doesn't exist
      looking for modules in /mnt/c/projects/an-derjava
        using description file: /mnt/c/projects/an-derjava/package.json (relative path: .)
        after using description file: /mnt/c/projects/an-derjava/package.json (relative path: .)
          using description file: /mnt/c/projects/an-derjava/package.json (relative path: ./aws-sdk)
            no extension
              /mnt/c/projects/an-derjava/aws-sdk doesn't exist
            .ts
              /mnt/c/projects/an-derjava/aws-sdk.ts doesn't exist
            .js
              /mnt/c/projects/an-derjava/aws-sdk.js doesn't exist
            as directory
              /mnt/c/projects/an-derjava/aws-sdk doesn't exist
      looking for modules in /mnt/c/projects/an-derjava
        using description file: /mnt/c/projects/an-derjava/package.json (relative path: .)
        after using description file: /mnt/c/projects/an-derjava/package.json (relative path: .)
          using description file: /mnt/c/projects/an-derjava/package.json (relative path: ./aws-sdk)
            no extension
              /mnt/c/projects/an-derjava/aws-sdk doesn't exist
            .ts
              /mnt/c/projects/an-derjava/aws-sdk.ts doesn't exist
            .js
              /mnt/c/projects/an-derjava/aws-sdk.js doesn't exist
            as directory
              /mnt/c/projects/an-derjava/aws-sdk doesn't exist
[/mnt/c/projects/an-derjava/node_modules/aws-sdk]
[/mnt/c/projects/an-derjava/node_modules/aws-sdk.ts]
[/mnt/c/projects/an-derjava/node_modules/aws-sdk.js]
[/mnt/c/projects/an-derjava/node_modules/aws-sdk]
[/mnt/c/projects/an-derjava/aws-sdk]
[/mnt/c/projects/an-derjava/aws-sdk.ts]
[/mnt/c/projects/an-derjava/aws-sdk.js]
[/mnt/c/projects/an-derjava/aws-sdk]
[/mnt/c/projects/an-derjava/aws-sdk]
[/mnt/c/projects/an-derjava/aws-sdk.ts]
[/mnt/c/projects/an-derjava/aws-sdk.js]
[/mnt/c/projects/an-derjava/aws-sdk]
 @ ./node_modules/node-pre-gyp/lib/info.js 14:14-32
 @ ./node_modules/node-pre-gyp/lib ^\.\/.*$
 @ ./node_modules/node-pre-gyp/lib/node-pre-gyp.js
 @ ./node_modules/bcrypt/bcrypt.js
 @ ./src/server/api/modules/users/models/users.model.ts
 @ ./src/server/api/modules/users/models/index.ts
 @ ./src/server/api/modules/users/index.ts
 @ ./src/server/api/modules/index.ts
 @ ./src/server/api/index.ts
 @ ./src/server/server.ts

As far as I understand, it's necessary add that module as external to webpack.config, but I'm newer work with webpack and don't understand how to do this.
Minimal reproduction of the problem with instructions
Use 'sqlite3', 'pg', 'tedius', 'mysql2', 'mongoose'
What is the motivation / use case for changing the behavior?
Using DB store
Please tell us about your environment:
node v8.2.1
windows 10, debian, ubuntu on windows 10
latest ng-seed/universal

Angular version: 4.3.2

Browser: [all]

Language: [TypeScript]

I found some solution for my problem. Maybe it's be useful for someone.
declare let __non_webpack_require__: any; // prevent TypeScript reference error

let mongoose = __non_webpack_require__('mongoose'); // requires mongoose, but not include it in boundle

import * as Mongoose from 'mongoose' // import mongoose types from @types/mongoose

The same can be used for any other modules.
PS: Perhaps the solution is not the best, but I have not found another.


Fixes minor typo

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @DaemonErrors for your contribution and congratulations on your first PR merge to this repo! 🎉


feat: Remove the "pfe-" prefix from the history feature in pfe-tabs

Fixes #802
Testing Instructions

Navigate to http://localhost:8000/elements/pfe-tabs/demo/?my-tabs=tab2 and verify that "Tab 2" is open in the "Tab History" section of the page
Next,  navigate to http://localhost:8000/elements/pfe-tabs/demo/?pfe-my-tabs=tab3 and verify that "Tab 3" is open in the "Tab History" section of the page

Note the "pfe-" prefix in the URL. This has been deprecated but we're going to support it.

It is expected that clicking on a different tab in the tab set will add another query string parameter to the URL.
This has been tested on:

Chrome
Firefox
Safari
Edge 80
IE 11 (this feature isn't supported on IE11 but it does not break tabs)

Note that this PR will need to be approved before I get the changes for #793 working.


Revert to Go 1.4.2

This is not passing 'go vet' under 1.4.2.

@sparrc -- can you please pull down this branch and see if you can fix these errors under Go 1.4.2?
$ go tool vet ./
client/example_test.go:15: ExampleNewClient refers to unknown identifier: NewClient
client/example_test.go:35: ExampleClient_Ping refers to unknown identifier: Client
client/example_test.go:52: ExampleClient_Query refers to unknown identifier: Client
client/example_test.go:71: ExampleClient_Write refers to unknown identifier: Client
client/v2/example_test.go:15: ExampleClient refers to unknown identifier: Client
client/v2/example_test.go:28: ExampleClient_uDP refers to unknown identifier: Client
client/v2/example_test.go:60: ExampleClient_write refers to unknown identifier: Client
client/v2/example_test.go:92: ExampleBatchPoints refers to unknown identifier: BatchPoints
client/v2/example_test.go:114: ExampleBatchPoints_setters refers to unknown identifier: BatchPoints
client/v2/example_test.go:135: ExamplePoint refers to unknown identifier: Point
client/v2/example_test.go:149: ExamplePoint_withoutTime refers to unknown identifier: Point
client/v2/example_test.go:163: ExampleClient_write1000 refers to unknown identifier: Client
client/v2/example_test.go:214: ExampleClient_query refers to unknown identifier: Client
client/v2/example_test.go:233: ExampleClient_createDatabase refers to unknown identifier: Client

cc @rossmcdonald

Fixes https://github.com/influxdb/influxdb/issues/4754

It appears that the Go vet failures are local to my machine. @sparrc is double-checking.
@sparrc -- if everything is OK for you, can you review and +1?

+1, worked for me on linux on 1.4.2


NumFOCUS Outline Information

Let me know if you need anything else.

Thanks. Looking forward to the interview.


Internal connections

Some components have pins internaly connected, like the GND pin. I wish to make internal connected pins configurable. At the moment when I configure that two pins of the same component are connected, the algorythm will make an separatire jumper wire.

Good point. That would definitely be useful, but it's unfortunately not implemented. I'm rewriting this application in Rust and have added a ticket for it over there. https://github.com/rogerdahl/striprouter/issues/1
In the meantime, I think you'll have to give the two GND pins different names, like GND1 and GND2, and specify directly which ones you want to use for the connections.


Fix the HTML, there were too many rejected valid HTML, like bold (critical for interviews), and figure captions.
Remove the URL redirection

Thank you for the improvements !


[facebook-login] - Add facebook signin with FBClientId, FBClientSecret, ...

...callbackURL and facebook signin config variables. Closes #745

@slifszyc When I logout, it takes me to login page (shouldn't be accesible).


Add OKX Wallet adapter

Add OKX Wallet adapter, Link to OKX Wallet extension.

Thanks for your contribution. We are no longer accepting PRs of adapters for this type of wallet. You can read about this policy here, but more importantly, please check out this guide for wallets to implement the Wallet Standard.
However, most of what you've written for this adapter is portable to the Wallet Standard interface, and implementing this interface will grant your wallet distribution on dapps across Solana. After reading the guide and looking at the reference implementations, if you have questions on how to do this, please open an issue here:
https://github.com/solana-labs/wallet-standard


pp.asfields() on a cube with a single longitude point results in incorrect lbnpt

I've encountered another unexpected behaviour in the pp_save_rules.  I'm not sure if this one is  intentional so I thought I'd confirm before preparing a fix.
Saving a cube with a single longitude point, e.g. zonal mean data, as a pp file results in lbnpt (number of longitude points) being incorrectly set to 0 rather than 1 (Note this example isn't on the save function directly, but is on the function that save calls to set up the fields prior to writing to disc):
import iris
from iris.coords import DimCoord
import numpy as np

def create_cube(longitude_points):
    cube = iris.cube.Cube(np.zeros((longitude_points, 2)))
    xcoord = DimCoord(np.arange(longitude_points),
                      standard_name='longitude',
                      units='degrees')
    ycoord = DimCoord(points=np.arange(2))
    cube.add_dim_coord(xcoord, 0)
    cube.add_dim_coord(ycoord, 1)
    return cube

cube1 = create_cube(1)
fields1 = list(iris.fileformats.pp.as_fields(cube1))
fields1[0].lbnpt
#[Out]# 0
# Incorrect result: should be 1

cube2 = create_cube(2)
fields2 = list(iris.fileformats.pp.as_fields(cube2))
fields2[0].lbnpt
#[Out]# 2
# Correct result

Digging into this, it looks like the culprit is in the pp_save_rules requiring longitude to be a vector coordinate here.  Is there a reason to constrain to a vector coordinate?

There's a similar issue for BDX too: it's not set for zonal mean data, but it should be set to 360.0 (for a fixed resolution lat/lon grid).

ping

It doesn't look like intended behaviour, but looking at the code I'm wondering how easy it will be to fix and maintain current behaviour: currently Iris saves vector coordinates of length 1 as scalars in pp files. So, for example, a cube of shape (1, 10, 20) can be saved in pp format (though it will load as a cube of shape (10, 20)). The function scalar_coord, used in the pp rules, will detect 1D vector coordinates of length 1, whereas vector_coord won't. Attempting to treat them as either scalars or vectors may lead to difficulties.

Thanks, that's interesting info.  I don't know that area of the code well enough to have a good grasp of how easy it will be to fix, but I think the fastest way to find out will be to take a stab at it and see where the difficulties lie.  I'm going to assume that preserving current behaviour for the (1, 10, 20) shape cube is required.
Just a heads up that it's unlikely that a PR will be in the next couple of weeks, I don't have a great deal of time to devote to this just now.


reverseCountdown doesn't stop at zero

FlipClock.reverseCountdown doesn't stop at zero mark, and also don't run alert function when countdown is done
DateTime now = DateTime.now();
DateTime debugTime = DateTime(
        now.year, now.month, now.day, now.hour, now.minute, now.second + 10);

FlipClock.reverseCountdown(
            duration: _duration,
            digitColor: Colors.white,
            backgroundColor: Colors.black,
            digitSize: 35.0,

            flipDirection: FlipDirection.down,
            borderRadius: const BorderRadius.all(Radius.circular(3.0)),
            onDone: alert(),
          ),

alert() {
    print('Done');
  }

How to fix this?

@hnvn no updates?

I will have a look at it, hope that it can be resolved this weekend


Attempt at fixing compile problem

Attempt to fix problem:
https://groups.google.com/forum/#!msg/votca/LGjDJLwuFgI/EnM4zFvJBQAJ

It looks like the pull request is building with master instead of stable...

gitlab still building against master...

The branch name needs to be for/stable/..., but don't worry I just push the commit on another branch, so that should trigger the build without the need for a new PR.

oh right, I forgot. My bad.


Add augmentation module

Primary changes:

TF aliases for mappers
RandomAugmentationPolicy (DataPoint -> DataPoint) which takes in TFs and applies them at random (for a seq length of k) to a DataPoint
TFApplier (List[SimpleNamespace] -> List[SimpleNamespace]) and PandasTFApplier (pd.DF -> pd.DF) that takes in a policy, a number of transformed data points per original, and keep_original as a flag

Example usage:
import pandas as pd
from snorkel.augmentation.apply import PandasTFApplier
from snorkel.augmentation.policy import RandomAugmentationPolicy
from snorkel.augmentation.tf import transformation_function
from snorkel.types import FieldMap

df = pd.DataFrame(dict(num=[1, 2, 3]))

@transformation_function
def square(num: int) -> FieldMap:
    return dict(num=num ** 2)

@transformation_function
def double(num: int) -> FieldMap:
    return dict(num=2 * num)

policy = RandomAugmentationPolicy([square, double], sequence_length=4)

applier = PandasTFApplier(policy, k=2, keep_original=True)
df_augmented = applier.apply(df)

Other changes:

Add __init__.py files to test dir so that they don't have to be imported in the global namespace by pytest
Fixes a bug for Mapper in NAMESPACE mode where the underlying SimpleNamespace.__dict__ was getting modified in-place
Allow people to pass in positional args to pytest when calling tox, e.g. tox -e py36 -- -k test_tf_applier_pandas

Test plan
Unit tests for TFAppliers and RandomAugmentationPolicy

Offline:

Updating signature to

@lambda_mapper
def my_function(x: DataPoint) -> DataPoint:
   ...

in follow up PR

Subclassing Mapper so that TFs can yield multiple transformations

@henryre thoughts on making the TFApplier return a generator, or at least having this option?  This is more in keeping with how data aug usually applied

Or: add a kwarg that determines whether the TF applier returns a dataset or a generator, e.g. materialize=true|false

@ajratner agreed, adding in a followup

@henryre Happy to finish up this PR including requested change if you want

Add matplotlib into requirements or this synthetic.py does not run


support honor ephemeral-storage for scan jobs

I missed configs like trivy.resources.requests.ephemeral-storage or trivy.resources.limits.ephemeral-storage to adjust ephemeral-storage for scan jobs.
it would be nice, if scan jobs would honor ephemeral-storage
e.g.
    resources:
      limits:
        cpu: 500m
        ephemeral-storage: 300Mi
        memory: 2048M
      requests:
        cpu: 100m
        ephemeral-storage: 300Mi
        memory: 512M

I have tried this by my self, but my go skills and test env is to bad :/
https://github.com/1337andre/trivy-operator/commit/6369908ed71a18abe8c41a93e64fc6c013249603

@1337andre this could be nice addition , you can pick it up if you have time.


Record Updates Allow Arbitrary Expressions, Update Pollen Tests

The short change list:

Update pollen examples to match new pollen syntax rules (such as putting everything in a function definition; more details below) and fix a logical bug in flip.pollen.
In record updates, allow arbitrary expressions for the reference record (e.i., { e with f1:e1, f2:e2, ... } )
Add automated testing via runt
Rename the test folders to tests, for the sake of consistency with the calyx directory (I don't have a preference between one or the other, I just want to be consistent so that I don't have to think about which one I need depending on which directory I'm in)
Rename the pollen extension to .pollen from .pol. .pol is much shorter, but apparently is already a file extension for "group policy settings." I'd be curious if anyone has feeling about .pol versus .pollen.

The longer explanation:
The majority of updates to the pollen examples consisted of

Making sure that everything (at the high level) is a function,
Removing "local" functions, aka nested functions,
Replacing outset with parset,
Writing tuple types as (t1*t2) rather than (t1, t2).
Replacing x += y with x = x + y (we do not yet support this syntactic sugar)
Replaced references to in_g.paths, in_g.steps, and in_g.segments with simply paths, steps, and segments, though perhaps we would only want one special variable as opposed to 5 (including handles and edges).

Additionally, I fixed a logical bug in flip.pollen related to our parset semantics - previously, it had been attempting to update a step's rank by iterating through rev(path.steps) and then emitting the step with it's orientation reversed without updating its index. However, as per our relational semantics, the order in which we emit steps does not matter, and we must instead specify its new index on path when we emit it, like so:
{ step with idx: max_step_idx - step.idx }.
What this pull request does not do is completely reconcile our pollen tests with the parser's semantics - paths.pollen refers to the steps in the path via path.steps[i], but the parser does not currently support array access. See #140

Excellent; all sounds great!

3. Add automated testing via runt

I see the new directory of tests, which seems great, but I don't set see a configuration file for Runt (or Turnt). Did this perhaps just not get checked in?

5. Rename the pollen extension to .pollen from .pol. .pol is much shorter, but apparently is already a file extension for "group policy settings." I'd be curious if anyone has feeling about .pol versus .pollen.

Sounds right to me! Less ambiguity => more better.

I see the new directory of tests, which seems great, but I don't set see a configuration file for Runt (or Turnt). Did this perhaps just not get checked in?

Ah, it looks like runt.toml was already merged into the main branch as part of #136 . I'll go ahead and update this PR to reflect that


[wallet] upgrade transaction data to filter by adding a tag (instead of using is_market)

For transaction_data upgrade, refer
https://github.com/BitShares/bitshares/blob/8bd3f8cf332ff72c0a51f8e51619ab3e2975fa82/libraries/wallet/wallet.cpp#L471

delete struct transaction_data after all wallet get upgraded.


ci: publish to new offering and use a catalog manifest file

Description
Modify catalog publishing for this offering to now publish to a different offering (new) in the catalog.
Also including a catalog manifest file, ibm_catalog.json, to specify the current flavor name.
Check the relevant boxes:

[ ] Bug fix (nonbreaking change that fixes an issue)
[ ] New feature (nonbreaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[x ] CI related update (pipeline, etc.)

Checklist

[ ] If relevant, a test for the change has been added or updated as part of this PR.
[ ] If relevant, documentation for the change has been added or updated as part of this PR.

Merge

Merge using "Squash and merge".
Make sure to use a relevant conventional commit message that is based on the PR contents. The commit message determines whether a new version of the modules needs to be released, and if so, which semver number to use).

Looks like unit tests are failing.  Some are mentioning quotas.   Is there is a nuke that cleans up?

@kbiegert Unit tests have passed so going to merge. Was any action taken to get them to pass? Do you recall what quotas we were hitting?

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

GitHub release
v1.2.0

Your semantic-release bot :package::rocket:


Post a message successfully even if bsky fails to get thumbnail of link card

When the og:image URL returns a status code other than 200, as in the case of https://www.mof.go.jp/index.htm, bsky is unable to post the message.
$ bsky post https://www.mof.go.jp/index.htm
failed to create post: XRPC ERROR 400: InvalidMimeType: Referenced Mimetype does not match stored blob. Expected: */*, Got: text/plain; charset=utf-8

In such instances, bsky should bypass to embed the og:image and proceed to post the message successfully.

Thank you


Ensure we release tunneld + tunnel binaries

We have tested this at https://github.com/cloudnative-coop/wgtunnel/releases/tag/v0.1.13
Will be good to have binaries built for other platforms.

I don't want to complicate the release process too much. We don't use the tunnel binaries in Coder and only provide the code as an example client. Providing tunnels for each OS and arch combo in releases is potentially more useful but it should be done with actual make targets instead of running make build repeatedly.


Mu estimation options, saving and loading

This expands flamedisx's options for estimating the total expected events ('mu'). It mostly prepares the ground for implementing new mu estimation methods in the near future, rather than adding new methods.
Specifying different mu estimation methods
See issue #71. A new mu_estimators argument to Likelihood.__init__ controls how mu estimators are built:

fd.CrossInterpolation (the default) will use the current algorithm.
fd.SimulateEachCall does a completely new simulation each call. This does not actually work -- it makes the likelihood non-differentiable. But it could be useful for debugging, or for future developement (I think Pueh is looking into this)
You can pass an already-built dictionary of mu interpolators, e.g. loaded from disk (see next section);
If you have multiple sources in the likelihood, and want to use different mu estimation methods for each, pass a dictionary mapping source names to the options above.

The actual code for mu estimation now lives in a new file (mu_estimation.py) which contains classes for the different methods. Currently it's a short list, but we can start adding to this. Sources no longer have a mu_function method; they are only responsible for estimate_mu at one parameter combination.
This PR also generalizes the third element in parameter specifications. Currently this is a number of anchors:
ll = fd.LogLikelihood(
    sources=dict(er=fd.ERSource),
    elife=(300e3, 500e3, 2),)

This remains supported for backwards compatibility. However, an anchor count is not meaningful for all mu estimation methods. Instead, you can omit the third element (fd.CrossInterpolation will use 2 anchors by default):
ll = fd.LogLikelihood(
    sources=dict(er=fd.ERSource),
    elife=(300e3, 500e3),)

or pass a dictionary, in which you can put other options as well:
ll = fd.LogLikelihood(
    sources=dict(er=fd.ERSource),
    elife=(300e3, 500e3, dict(n_anchors=2),)

Saving and loading mu estimators
See issue #52. Now that we're going to spend more computation time on the mu estimation, we don't want to redo that work every time we start a notebook.
You can set the new mu_estimators argument to a previously built mu_estimators dictionary. For example,
ll = fd.LogLikelihood(....)

# Saving to disk
fn = 'bla.pkl'
with pickle.open(fn, mode='wb') as f:
    pickle.dump(f, ll.mu_estimators)

# Loading from disk
with pickle.open(fn, mode='rb') as f:
    mu_estimators = pickle.load(f)
ll = fd.LogLikelihood(...., mu_estimators=mu_estimators)

Maybe we want to build something more opinionated (a la blueice) on top of this later, or maybe simpler is better for now.

Thanks so much for this @JelleAalbers - this will be very useful for testing the different options. I have a slightly manic couple of weeks ahead with other projects but when I get back to thinking about this I'll dump some of my code (currently in standalone Jupyter notebooks) into here

This looks great! I also have some code to put here but it is based on Rob's work on the mu Taylor expansion. The idea is to have multiple Taylor expansions around different points in the parameter space and weight the functions according to the distance where the evaluation happens. When Rob puts in the Taylor expansion I could gladly put in my method as well.

Allright, finally added units tests; now this is ready for review. If nobody gets to this in a while, I may add GridInterpolation -- but I would prefer to make that a separate PR, this is already a big one.
I added a fix to how flamedisx handles empty data (datasets with no events), which was useful for writing the mu estimator tests. Previously feeding in empty data would crash the source (during populate_tensor_cache) and cause trouble in the likelihood (the mu and constraint term get added on batch #0, but skipped if there are no batches).

Thank you for doing this, I read through it a while ago but have had a more thorough look this morning.
I think having an argument in the Likelihood function is the best way of doing this and I like that the functions get their own file.
I personally would like the grid interpolation method included in this PR or to quickly follow this PR (or another method than the cross interpolation). This would give us a good solution for uncorrelated and correlated parameters. Currently, we don't have a good option for correlated parameters. This would allow us to perform fits on the same data using both methods and maybe would inform us on the extent that this mu issue is impacting us.
In terms of how this has all been implemented, I have no comments. It all looks neat to me.

Thanks for your comments everyone! Let's merge this and start collecting new interpolation methods soon.


Leaked Credentials

Hello Yuta-san,
I am a part of the Zscaler security team. We were alerted that you had checked in credentials for the ZIA portal in this repo at sample/sample_adminuser.json.
While I couldn't find any account in zscaler.net cloud associated with this account, I urge you to consider whether this information needs to be public.

Hi, Naresh
Thanks for contacting me. Sorry for credentials of my json file.
The file you mentioned has below username.

<EMAIL_ADDRESS>
But this is a not real ZIA account.
I added this info to explain how to use this file as sample.
Although I think this is not confidential info, I'll change this domain from zscaler.net to like sample.com.


Spaces Page

Description
Added Spaces page. It displays all spaces available.
Additional Context
Type of Spaces

Default Spaces: Personal & Work
New Spaces can be added by the user.  Max Spaces should be 4 (including default spaces).

Related Issues

#25

Changes

Create & Read functionality implemented for Spaces
Converted Route's attributes to object and populated Routes using the map.
Default Spaces: Personal only.

TODO (To be address in new issues)

[ ] Confusion between Spaces and Space. Describe it clearly on Epic Space
[ ] Improvise Naming Convention for Types.


Create blur functions

The point is to build our auxiliary functions in order to get a better understanding of how we're going to execute the projet.

We need to create the following functions for an MVP:

Finds a face, return the array where the face is located
Given an array, apply a blur, be it a Gaussian blur, avg pixel, max pixel
Add back the matrix on the original image


Added the extra-index-urls change to az extension add and update commands

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

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

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

(see Authoring Command Modules)

View a preview at https://prompt.ws/r/Azure/azure-cli/5443
This is an experimental preview for @microsoft users.


Cancel button sometimes won't work

I think this probably has to do with times when it's not even reached the worker yet. We need to support cancellation at any level of the process. Suspicious this is related to #136 and reproducible in that context.

Now that #136 is fixed, let's see if this keeps happening. Maybe should close.


Add pip check

Address https://github.com/conda-forge/tqdm-feedstock/issues/84

Checklist

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

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

noarch: python recipes are recommended to have a lower bound on the python version. This recommendation will become a requirement in the future.
License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

While adding pip check is also included in #85, this PR does not fix #84, due to the underlying issue of missing setuptools_scm...


StaticInjectorError when loading via systemJS import-map

I want to share common dependencies in a micro-frontend project using single-spa/single-spa-angular. When trying to share @esm-bundle/angular__core, the console shows the following error:

MWE: https://github.com/SebastianOltmanns/singlespa-angular-core-share-dep
My minimal working example has three projects:

root, the root-config, where the systemJS import-map is loaded and the micro-frontend services are loaded
p1, basic angular example project, where @angular/core is externalized
p2, basic angular example project, where @angular/core is included

When running all three projects, visiting p1 gives the error shown above, but visiting p2 works. The literal only difference in p1 and p2 is in externalizing the @angular/core library, and instead using @esm-bundle/angular__core. This is why I open this issue here, because I think it has to do with this project.
Thanks for any help or investigations!

Hello, is there an update to this issue? I'm having the same problem with Angular 11.

Sadly, no.
On Thu, Jan 27, 2022, 3:25 PM Steven Kolamkuzhiyil @.***>
wrote:

Hello, is there an update to this issue? I'm having the same problem with
Angular 11.
—
Reply to this email directly, view it on GitHub
https://github.com/esm-bundle/angular__core/issues/241#issuecomment-1023264460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEM7Y5OVZOAIR7H244XFBQDUYFIW3ANCNFSM5JEVHQDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>


[BUG] THE PROGRAM IS UNABLE TO VERIFY ITSELF

Describe the bug
the code opens a chrome window in which the website chatgpt4 shows a cloudfare captcha, as i solve the captcha there comes a another one.
To Reproduce
Steps to reproduce the behavior:

Go to localhost
Type the content
The code opens a new chrome tab
See error

Expected behavior
The chatgpt site is supposed to open when i solve the captcha
Screenshots

Desktop (please complete the following information):

OS: Windows
Browser Chrome
Python Version 3.9

??


Feat add signoz as vendor

Please sign the CLA

yes, I will. waiting on a few changes. will make this ready for review and merge.

Closing this as stale; please re-submit when you're ready.


[maint] Rename Repo and Change All 'Embassy' References

Following a rebrand, embassyOS is now StartOS and Embassies are now Start9 Servers

Changed references to StartOS
Backend on github for sdk not found in link

Changed references to StartOS
Backend on github for sdk not found in README link

Not sure exactly what you are looking for here - have you checked our other package repos for what you need?


Adding documentation for building and running HDF5 on a Broad VM.

Closes #129

Coverage decreased (-0.04%) to 91.722% when pulling 8df303aa817f771a15e25869226ca336d0c7a94a on issue-129-Broad_VM_README into db19cd31d194b404a2e3c61f2ad1b52800ab4543 on master.

Coveralls is full of it... please ignore.

looks good to merge.  i noticed that "prorected" should be "protected" in the last line of the readme, maybe fix that while you're at it?

I made that last change and rebased.


Support --json mode

I've just stumbled upon this package and have to say: it seems super cool!
My company has an internal auditor that runs the appropriate auditors against our repos, and this looks like it could be a complete drop-in that would gain us some very useful features (whitelisting in particular).
However currently audit-ci outputs a few lines of text before & after the JSON audit results - it would be useful if there was a --json flag that would have only the audit results JSON be outputted.
An extension on this could be to then add a auditCi property that contained information from audit-ci, such as what was whitelisted.
I'm happy to work on a PR for this, and have a few ideas on how to go about it - my initial attempt will likely be to just replace all log calls with a logger function call that is a noop if the flag is present.

I was wondering if someone was going to request "JSON-only" mode! Would this JSON-only mode be your desired behaviour or would the returning of the "report" object be more useful? If in JSON-only mode, you could pipe the result to a consumer and that may be sufficient.
To add a datapoint to the discussion, https://github.com/npm/npm-audit-report is an interesting project specifically for npm. I haven't reviewed much of it yet, but there may be lessons to be learned from that project.
Another thing to consider is that Yarn's audit isn't a single JSON object while NPM's audit is a single JSON object. It doesn't support whitelisting, but does manage the audit result in a single object that can be consumed. We use the JSON-stream dependency to manage consuming the JSON from the audits since we have had CIs fail due to too many security advisories.
Currently, the information regarding the information from the audit and whitelisting is contained within Model.js. I don't mind if that's refactored or if it's exported to be consumed.

For further flexibility, I would consider revising the flag from --json to something like --output {none/full/json} (default full). This is slightly different than the --report-type since report-type refers to the output within either a full or json.
I am unsure if this would be a confusing semantic for adopters. Also, since Yarn uses JSON-lines format rather than JSON, that might result in a "gotcha", but this behaviour can be documented.

Those are some good questions & considerations.
Currently our auditor shells out to npm & yarn for auditing, so it handles both the json structures; the primary win here is supporting a whitelist.
However overall in theory npm 7 will make this less of a problem since it supports both package-lock.json & yarn.lock, so it should be able to audit both, giving the same output. (but that would just save you from having to implement whitelisting in yarn).
I think --output is a good idea, and I could see use for the none value. The name might need some regigging, but the outputted JSON is pretty big, and always outputted so that value could be used to shut audit-ci up: "only tell me what failed if things fail".
I'll have a think over this as I play with audit-ci during the course of the week :)
I might have a crack at implementing the whitelisting into yarn first, as we use Ruby/Rails a lot which picked yarn as their default package manager.

Also note this request has significant overlap with this feature request: https://github.com/IBM/audit-ci/issues/118
Would be nice for a solution to address both issues, but not a requirement 🙂

Hi, any update on the above feature request?
I think providing a way to output the report as a pure JSON object would be helpful in parsing the data. Checked retireJS. It also supports flags like --outputFormat and --outputPath(to directly redirect output to a file, we can skip this if not desired). Maybe we can introduce something like this.
Regards
Lohitaksh

I have not performed any work on this feature at this time. However, I do think it is a valuable addition. I don't have immediate plans to write this feature myself (may in the future), but I would certainly review PR requests.

Hi, what are your thoughts on SARIF output format?

@keshavkaul the more the merrier! I think having an --outputFormat|--output-format flag is very useful and SARIF is a great standard. I have no immediate plans to write that functionality at this time (JSON is an easier place to start anyways).


Update COG path

Fixes #14234
The TCI file seems unavailable via the /2020/ path but is available via the /36/Q/WD/2020/7/ path.
https://deploy-preview-14236--ol-site.netlify.app/en/latest/examples/cog.html
(The corresponding B04 and B08 files used in other examples continue to be available via the shorter path).

Thanks, @mike-000


[hibernate-search] No transactional EntityManager available error

No transactional EntityManager available error when running example from
https://github.com/eugenp/tutorials/blob/master/persistence-modules/spring-hibernate-5/src/main/java/com/baeldung/hibernatesearch/ProductSearchDao.java

Hi, which version of JDK are you using?
If it is 11 or higher, then the problem might be in missing JAXB API. In order to fix it, please add the following dependencies to your spring-hibernate-5 POM:
        <dependency>             <groupId>javax.xml.bind</groupId>             <artifactId>jaxb-api</artifactId>             <version>2.3.1</version>         </dependency>         <dependency>             <groupId>org.glassfish.jaxb</groupId>             <artifactId>jaxb-runtime</artifactId>             <version>2.3.1</version>             <scope>runtime</scope>         </dependency>
This should fix the problem

I'm using JDK <IP_ADDRESS>

Hi @Med-All,
Sorry to hear you're having issues with this.
Can you please clarify how to recreate the problem? Does it occur during the tests or only when the 'live' application is started?
Can you also say how do you deploy the app and provide the full log?
Thanks!

Hi @Med-All, just a quick ping. Would you be able to provide the additional information?

@kwoyke I had the problem with the live application. Not sure because I have done it as SpringBoot2 but solved it by adding @Transactional annotation to the index builder code and search repository.


TypeConverter other than for primitives are not supported yet

@igarashitm commented on Mon Oct 30 2017
https://github.com/atlasmap/atlasmap-runtime/blob/ce498616965254723428641ab5c03ed80cff4d40/atlas-core/src/main/java/io/atlasmap/core/DefaultAtlasConversionService.java#L279-L306
Yes it's definitely TODO. Even DateConverter is not available.

@igarashitm is this issue only focused on adding DateConverter support?

@rohanmars nope, this is to implement exactly this TODO
https://github.com/atlasmap/atlasmap-runtime/blob/ce498616965254723428641ab5c03ed80cff4d40/atlas-core/src/main/java/io/atlasmap/core/DefaultAtlasConversionService.java#L304-L305
DateConverter is just an example (well, right now it's the only one though...). All the OOTB converters other than primitives should be invoked from here.

@igarashitm I have implemented an approach that uses the annotation (AtlastConversionInfo) values to determine which conversion method to actually use in the conversion service. Is this an okay approach with you? It will simplify the solution I believe and help on #114
Basically, when the conversion service loads the converter classes it now builds a map of converter methods using reflection, keyed by source/target field types. Then when the converterType method is called it looks up which method it should invoke from the map and uses the saved Method reference to invoke using refection. That way new conversion methods can be added simply by adding methods to the AtlasConverter class and annotating them accordingly. No update to the converter service would then be required.
I might need to slightly change the key object include the class names also (if they are specified on the annotation) to support multiple use cases that map to the COMPLEX fileldType but having different concrete impl classes. This is currently the case for the existing DateConverter, however, I think that this class needs to be improved anyway so that might not be required for that specific converter but probably should be supported anyway.
I was thinking also to remove the AtlasPrimativeConverter interface, I think that is unnecessary now. Do you have any thoughts as to why we should keep it if I change to use the reflection based approach?

@mattrpav what you think about my proposed changes?
Upon deeper analysis the targetType class information is not readily available and/or not necessarily passed in the right places. There is a convertType method which contains the target class name (I assume) but this not currently implemented (and there are no places that call it).
The issue is when a field is marked as a COMPLEX type it would be advantageous to record the actual associated class with the converter method. That way multiple converters could exist for the COMPLEX use case to/from a different type.
Maybe it's better to leave full support of a COMPLEX type to another issue. It would mean that the current DateConveter would only support conversions between existing field types (except COMPLEX).

+1 I’m in favor of this approach. It sounds similar to how Camel works for comparison. Also, the FieldActions have a similar approach.
I think we need to be clear what ‘Complex’ means. From inspection POV, it means a holder of other fields. For conversion, I think supporting  a matter of “does a converter exist for my exact class name” vs trying to accept

@rohanmars that approach sounds right to me, but want to look at the prototype to have deeper understand.
w/r/t COMPLEX, I think we currently stick to not use COMPLEX as a final field type. For UI COMPLEX field is a container of fields, not a mappable field. UI never creates a mapping using COMPLEX field type. So having COMPLEX as a field type of converter/fieldaction is a bug (i.e. DateConverter has bugs).
Changing this policy causes huge impact through UI, and I don't think we have enough feedback gathered to decide if we should do that or not. I think this was the conclusion in our discussion @mattrpav ?


Get playlist name on Youtube

Checklist

[x] I'm reporting a site feature request
[x] I've verified that I'm running youtube-dl version 2020.03.24
[x] I've searched the bugtracker for similar site feature requests including closed ones

Description

I was searching to be able to get the name of a youtube playlist.
I could get it by several lines of codes that I could share here (using grep and sed) but it would be nice to have a option for this. A bit similar to youtube-dl -e urlplaylist.

Output as JSON & parse JSON. No grep or sed nonsense is required.


fix upgrading pip to v10

Installing with --user option will leave the old pip.exe script in the $PATH, but then running the latter fails because pip 10 has moved its 'main' function to internal modules, and the old pip.exe launcher fails to import it.
The fix is to force overwriting the old pip.exe by installing globally without the --user option.
pypa/pip#5240 (comment)
Also see https://github.com/google/brotli/pull/663

Thanks!