Error while building application

Hello,
I have an error while building the application (npm):
This error in particular seems to repeat itself:
ERROR in ./resources/js/components/app.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
   at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
   at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
@ ./resources/js/app.js 8:0-48 51:15-27
@ multi ./resources/js/app.js

Here is the rest of the logs:
Hash: 92ff731e4713ae3323ec
Version: webpack 4.42.1
Time: 23006ms
Built at: 04/06/2020 5:07:31 PM
 33 assets
Entrypoint bundle = bundle.css bundle.487fefac8d60c8eb1225.js

ERROR in ./resources/js/components/app.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/app.js 8:0-48 51:15-27
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/home.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 13:13-39
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/auth/login.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 19:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/components/error.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/component.js 1:0-50 3:16-28 5:35-47
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/intro/farm.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 28:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/create.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 55:13-47
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/intro/reservoir.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 37:13-50
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/intro/area.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 46:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/reservoir.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 73:13-50
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/area.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 91:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/reservoirs.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 64:13-51
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/areas.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 82:13-46
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/crop.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 109:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/tasks/task.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 127:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/inventories/materials.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 136:13-56
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/crops.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 100:13-46
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/crop-notes.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 118:13-51
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/settings/account.vue
Module Error (from ./node_modules/vue-loader/lib/index.js):

Vue packages version mismatch:

-<EMAIL_ADDRESS>(/tania-core/node_modules/vue/dist/vue.runtime.common.js)
-<EMAIL_ADDRESS>(/tania-core/node_modules/vue-template-compiler/package.json)

This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

 @ ./resources/js/router.js 145:13-51
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/components/app.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/app.js 8:0-48 51:15-27
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/home.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 13:13-39
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/auth/login.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 19:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/components/error.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/component.js 1:0-50 3:16-28 5:35-47
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/intro/farm.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 28:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/create.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 55:13-47
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/intro/reservoir.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 37:13-50
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/intro/area.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 46:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/reservoir.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 73:13-50
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/area.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 91:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/reservoirs.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 64:13-51
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/areas.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 82:13-46
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/crop.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 109:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/tasks/task.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 127:13-45
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/inventories/materials.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 136:13-56
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/crops.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 100:13-46
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/farms/crop-notes.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 118:13-51
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js

ERROR in ./resources/js/pages/settings/account.vue
Module build failed (from ./node_modules/vue-loader/lib/index.js):
TypeError: Cannot read property 'parseComponent' of undefined
    at parse (/tania-core/node_modules/vue-loader/node_modules/@vue/component-compiler-utils/dist/parse.js:14:23)
    at Object.module.exports (/tania-core/node_modules/vue-loader/lib/index.js:67:22)
 @ ./resources/js/router.js 145:13-51
 @ ./resources/js/app.js
 @ multi ./resources/js/app.js
Child html-webpack-plugin for "index.html":
     1 asset
    Entrypoint undefined = index.html
Child mini-css-extract-plugin node_modules/css-loader/dist/cjs.js!node_modules/sass-loader/dist/cjs.js!resources/sass/app.scss:
    Entrypoint mini-css-extract-plugin = *
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! @ production: `cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --mode production --progress --hide-modules`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the @ production script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 2
npm ERR!
npm ERR! Failed at the @ prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-04-06T17_07_33_173Z-debug.log

Same here

Fixed:
Miss match between vue-template-compiler and vue
npm install<EMAIL_ADDRESS>--save-dev
npm install<EMAIL_ADDRESS>--save-dev
npm run dev
you can also build with npm install 2.6.10 if needed

This problem was caused by using npm and the fact that package-lock.json is missing from the repo. In which case npm will install newest packages versions matching ranges defined in package.json instead of versions verified to work and locked in package-lock.json.
There is however yarn.lock file in the repo, and when using yarn instead of npm build works fine.
Since in the readme instructions are using npm but in the repo there's yarn.lock, there should be probably a decision made on which one (npm or yarn) is recomended and then the readme and/or lock files should be updated accordingly.

@wotnak thank you. We'll use NPM then. To reduce the step to build the project. Apparently, not everybody knows how to install Yarn and NPM is the default dependency manager for Node.


Unexpected CLI argument DX

The use of a single dash (-) for multi-character flags (instead of --) is unusual! Additionally, dry run looks like it's being treated as a flag but looks a bit strange because it is inverted (defaulting to true, and false when provided). More detail below!
- / --
Generally, conventions around CLI programs are that single hyphens denote flags, or short versions of arguments.
For flags, you can provide one or more each with a -. Multiple flags can be combined after a single dash, so the following two commands are identical:
myprogram -abc
myprogram -a -b -c

Many programs also provide long versions of flags, which can be easier to understand. Here's an example of expanding the a, b and c flags for this hypothetical program.
myprogram --all --backtrack --crazy-mode

This also applies to arguments. A familiar example is that the AWS CLI accepts a profile parameter, which can be provided in short form (-p or long form --profile). This argument expects a value to be provided afterwards, both of the following are equivalent:
aws sts get-caller-identity -p myprofile
aws sts get-caller-identity --profile myprofile

In bucket-blocker, the help text uses a single dash for multi-character flags/arguments. For example, the exclusions flag is documented as the following:
bucket-blocker -exclusions string

But to me, this looks equivalent to passing multiple single character flags, the last of which takes an argument (which is itself a bit weird)!
bucket-blocker -e -x -c -l -u -s -i -o -n -s string

More canonical would be to use -- for the full name of this flag, and provide a short form behind a single hyphen to save typing, if desired.
bucket-blocker --exclusions string
bucket-blocker -x string

Flags defaulting to false
Generally, the presence of a flag enables that flag. This means they implictly default to "false" when absent, so if you want a flag to be an opt-out then it's typically inverted in its naming and meaning.
For example, if you want to have a dry run feature then you can add a --dry-run flag that enables a version of the program that does not perform side effects. However, if you want to have the program run in dry-run mode by default, then the flag will need to disable dry-run mode. AWS use --no-dry-run for this but another approach is to think about what it means for your program to run in real mode and name the flag the positive way for this, --commit for example!
Bucket blocker does this now, and I think this is why its help text is a bit confusing. It seems to imply that dry-run takes a parameter (since it defaults to true), but also looks like a flag that toggles something based on its presence or absence. Without reading the source code, I'd guess that including the -dry-run flag would in fact disable dry-run mode, and have it run in production mode.

Re: single dash vs double dash, the Go standard library doesn't differentiate between single and double dash. They are treated as equivalent: https://pkg.go.dev/flag#hdr-Command_line_flag_syntax
I know this because I had to look it up when the first PR in this repo was opened, as I also found it very confusing, and against the principle of least astonishment. I was expecting it to be the way you described.
Afaik when CLIs tend to get more complex, people tend to use third party libraries, and they just seem to proliferate which doesn't make the choice very easy. Of course, If I had to pick, I'd go with Meta's recommendation ;)
Re: flags defaulting to false, I agree. If a boolean flag is absent, it should be treated as false.


IoTCoreDefaultApp - Screen saver needs to hide cursor

Hi @rachitb777, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Rachit Bajpai). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


Can you add a license to this project? Like Apache 2.0 or MIT?

It's good practice to have license in an open-source project.

+1 Without an appropriate license, the documentation can't be displayed on https://pkg.go.dev/github.com/volcengine/volc-sdk-golang.


Support model binding to tuples

Tuples seem like a nice way to define an input model for an action method.

Might be nice to then also have a simple way to map the input model to your application model. See #5883.

Yes please!! This could be a much nicer way to protect against mass-assignment without the need to create concrete types for input models or use the (awful) Bind/NeverBind features.
So, something like this:
[HttpPost]
public IActionResult Create((string FirstName, string LastName, DateTime BirthDate) inputCustomer)
{
    var customer = new Customer();
    ObjectMapper.Map(inputCustomer, customer);
    // Save it, blah blah
    return View();
}

You can't put attributes on the fields of a tuple. With that limitation do you still want this?

Closing because there are no plans to implement this.


fix: static job check path

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0e2f172) 35.20% compared to head (8991fa1) 35.20%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #807   +/-   ##
=======================================
  Coverage   35.20%   35.20%
=======================================
  Files          37       37
  Lines        4550     4550
=======================================
  Hits         1602     1602
  Misses       2795     2795
  Partials      153      153

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


make Page implementations idempotent

Coverage remained the same at 81.834% when pulling ad21ae0aeff1cf96495d0744dca60ed5602da93a on ostumpf:ost-idempotent-page into 0c3827fafa1a90cf6cef6e036bb82397a1d7a5bb on martiner:master.

Coverage remained the same at 82.672% when pulling 59d2c1eb518d8ab9b5dd1484a8aa84880c608177 on ostumpf:ost-idempotent-page into e477a2cd4a6804fc6bcc93b987be9fbc898064ea on martiner:2.0.0-RC.

Coverage remained the same at 82.672% when pulling 5073d431f3d14fe5ddfa0ab0fb3e207096aba003 on ostumpf:ost-idempotent-page into e477a2cd4a6804fc6bcc93b987be9fbc898064ea on martiner:2.0.0-RC.


Make ContourSequence optional

The get_contour_sequence_by_roi_number function now checks if roi_contour has the ContourSequence attribute. If it does, we return the sequence, i.e. roi_contour.ContourSequence. Otherwise, we return an empty sequence, i.e. Sequence().

Closes #67

This pull request appears to have been closed instead of merged. Is it a mistake?


runtime: exit hook invoked panic in cmd/go.TestScript/cover_build_pkg_select

#!watchflakes
post <- `fatal error: internal error: exit hook invoked panic`

(Appears in logs matching #56197, but seen in other cover-related tests as well.)
(CC @thanm)

Closing this out, hasn't happened in more than 9 months (we can always reopen if needed).


Training checkpoints (of large models) are unreadble due to metadata

What happened?
Training checkpoints for large models (num_channels equal or greater than 912) become unreadable by pytorch and hence can't be used to resume or fork runs.
Note - for now this issue can be overcome by:

patching an existing checkpoint: zip -d model.ckpt archive/anemoi-metadata/ai-models.json
commenting out the line that writes the metadata to the training config: https://github.com/ecmwf/anemoi-training/blob/91d8c6e9a8ac275ded43f781aac031ccca36499d/src/anemoi/training/diagnostics/callbacks/init.py#L888C1-L889C1

These are temporary solutions, since if we also reach a point where our inference checkpoints are that large then we would also need a fix to be able to run inference
What are the steps to reproduce the bug?

Update the config to use a model with num_channels equal or greater than 912.
Run anemoi-training train --config-name filename
Once finished, try to resume or fork the above run with run_id: previous_run_id or fork_run_id: previous_run_id
Code crashes when loading the checkpoint with following error: RuntimeError: PytorchStreamReader failed reading zip archive: invalid header or archive is corrupted

Version
0.1.0
Platform (OS and architecture)
ATOS
Relevant log output
Error executing job with overrides: []
Traceback (most recent call last):
  File "/etc/ecmwf/nfs/dh2_home_a/ecm1715/anemoi-training/src/anemoi/training/train/train.py", line 355, in main
    AnemoiTrainer(config).train()
  File "/etc/ecmwf/nfs/dh2_home_a/ecm1715/anemoi-training/src/anemoi/training/train/train.py", line 341, in train
    trainer.fit(
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 543, in fit
    call._call_and_handle_interrupt(
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/trainer/call.py", line 43, in _call_and_handle_interrupt
    return trainer.strategy.launcher.launch(trainer_fn, *args, trainer=trainer, **kwargs)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/strategies/launchers/subprocess_script.py", line 105, in launch
    return function(*args, **kwargs)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 579, in _fit_impl
    self._run(model, ckpt_path=ckpt_path)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/trainer/trainer.py", line 955, in _run
    self._checkpoint_connector._restore_modules_and_callbacks(ckpt_path)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/trainer/connectors/checkpoint_connector.py", line 397, in _restore_modules_and_callbacks
    self.resume_start(checkpoint_path)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/trainer/connectors/checkpoint_connector.py", line 79, in resume_start
    loaded_checkpoint = self.trainer.strategy.load_checkpoint(checkpoint_path)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/pytorch_lightning/strategies/strategy.py", line 368, in load_checkpoint
    return self.checkpoint_io.load_checkpoint(checkpoint_path)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/lightning_fabric/plugins/io/torch_io.py", line 83, in load_checkpoint
    return pl_load(path, map_location=map_location)
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/lightning_fabric/utilities/cloud_io.py", line 56, in _load
    return torch.load(f, map_location=map_location)  # type: ignore[arg-type]
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/torch/serialization.py", line 1004, in load
    with _open_zipfile_reader(opened_file) as opened_zipfile:
  File "/perm/ecm1715/conda/envs/aifs-dev/lib/python3.10/site-packages/torch/serialization.py", line 456, in __init__
    super().__init__(torch._C.PyTorchFileReader(name_or_buffer))
RuntimeError: PytorchStreamReader failed reading zip archive: invalid header or archive is corrupted

Accompanying data
No response
Organisation
No response

I dug a little into this, I think it is related to torch using its own ZIP implementation PyTorchFileWriter.
A ZIP file contains a metadata "Central Directory", which is a collection of headers that describe the files included in the ZIP, and the offset of where they are stored in the byte stream. These headers (one for each file in the zip) are located at the end of the file, with the offset to the start stored at the very end. So that a ZIP client can show you the contents of a file without unzipping the whole thing.
An example header (the first one) looks like this, taken from an original PTL training checkpoint larger than 2GB (2.6GB):
A5A780B8 CENTRAL HEADER #1     02014B50
A5A780BC Created Zip Spec      00 '0.0'
A5A780BD Created OS            00 'MS-DOS'
A5A780BE Extract Zip Spec      00 '0.0'
A5A780BF Extract OS            00 'MS-DOS'
A5A780C0 General Purpose Flag  0808
         [Bit  3]              1 'Streamed'
         [Bit 11]              1 'Language Encoding'
A5A780C2 Compression Method    0000 'Stored'
A5A780C4 Last Mod Time         00000000 'Fri Nov 30 00:00:00 1979'
A5A780C8 CRC                   56EFB34A
A5A780CC Compressed Length     0003CFBF
A5A780D0 Uncompressed Length   0003CFBF
A5A780D4 Filename Length       0010
A5A780D6 Extra Length          0000
A5A780D8 Comment Length        0000
A5A780DA Disk Start            0000
A5A780DC Int File Attributes   0000
         [Bit 0]               0 'Binary Data'
A5A780DE Ext File Attributes   00000000
A5A780E2 Local Header Offset   00000000
A5A780E6 Filename              'archive/data.pkl'

In the corrupted checkpoint (the one where we added our metadata to), this first header is exactly the same. So far so good.
So, the central directory is just a long list of these headers, one for each file, in the order of which they were added to the zip. Note that the header tells you the size of the file (Compressed Length and Uncompressed Length).
Going through the headers, at some point the cumulative size of all files will become greater than 2GB. This is where the original and the corrupted is different.
Original:
A5A82E4C CENTRAL HEADER #2CF   02014B50
A5A82E50 Created Zip Spec      00 '0.0'
A5A82E51 Created OS            00 'MS-DOS'
A5A82E52 Extract Zip Spec      00 '0.0'
A5A82E53 Extract OS            00 'MS-DOS'
A5A82E54 General Purpose Flag  0808
         [Bit  3]              1 'Streamed'
         [Bit 11]              1 'Language Encoding'
A5A82E56 Compression Method    0000 'Stored'
A5A82E58 Last Mod Time         00000000 'Fri Nov 30 00:00:00 1979'
A5A82E5C CRC                   9EE748F7
A5A82E60 Compressed Length     00001000
A5A82E64 Uncompressed Length   00001000
A5A82E68 Filename Length       0010
A5A82E6A Extra Length          0000
A5A82E6C Comment Length        0000
A5A82E6E Disk Start            0000
A5A82E70 Int File Attributes   0000
         [Bit 0]               0 'Binary Data'
A5A82E72 Ext File Attributes   00000000
A5A82E76 Local Header Offset   812ABB94
A5A82E7A Filename              'archive/data/743'

Corrupted:
A5A90992 CENTRAL HEADER #2CF   02014B50
A5A90996 Created Zip Spec      2D '4.5'
A5A90997 Created OS            00 'MS-DOS'
A5A90998 Extract Zip Spec      2D '4.5'
A5A90999 Extract OS            00 'MS-DOS'
A5A9099A General Purpose Flag  0808
         [Bit  3]              1 'Streamed'
         [Bit 11]              1 'Language Encoding'
A5A9099C Compression Method    0000 'Stored'
A5A9099E Last Mod Time         00000000 'Fri Nov 30 00:00:00 1979'
A5A909A2 CRC                   F99F2265
A5A909A6 Compressed Length     00000004
A5A909AA Uncompressed Length   00000004
A5A909AE Filename Length       0010
A5A909B0 Extra Length          000C
A5A909B2 Comment Length        0000
A5A909B4 Disk Start            0000
A5A909B6 Int File Attributes   0000
         [Bit 0]               0 'Binary Data'
A5A909B8 Ext File Attributes   00000000
A5A909BC Local Header Offset   FFFFFFFF
A5A909C0 Filename              'archive/data/743'
A5A909D0 Extra ID #0001        0001 'ZIP64'.   <-----
A5A909D2   Length              0008.  <-----
A5A909D4   Offset to Central<PHONE_NUMBER>AABF50 <-----
         Dir <-----

Note the addition of an extra ZIP64 fields at the end, marked with the arrow. So the python ZipFile implementation is rewriting the headers of the PyTorch data in the central directory. I believe this is what causes the corruption. For whatever reason, the PyTorch ZIP implementation does not add or expect these fields in the central directory.
The PyTorch ZIP implementation does seem to follow the ZIP64 spec, because it has ZIP64 headers at the end of the central directory, it just does not also add that extra field to each individual header:
A5A87114 ZIP64 END CENTRAL DIR 06064B50
         RECORD
A5A87118 Size of record<PHONE_NUMBER>00002C
A5A87120 Created Zip Spec      1E '3.0'
A5A87121 Created OS            03 'Unix'
A5A87122 Extract Zip Spec      2D '4.5'
A5A87123 Extract OS            00 'MS-DOS'
A5A87124 Number of this disk   00000000
A5A87128 Central Dir Disk no   00000000
A5A8712C Entries in this disk<PHONE_NUMBER>0003E2
A5A87134 Total Entries<PHONE_NUMBER>0003E2
A5A8713C Size of Central Dir<PHONE_NUMBER>00F05C
A5A87144 Offset to Central dir 00000000A5A780B8

A5A8714C ZIP64 END CENTRAL DIR 07064B50
         LOCATOR
A5A87150 Central Dir Disk no   00000000
A5A87154 Offset to Central dir 00000000A5A87114
A5A8715C Total no of Disks     00000001

Are there any updates on this? I am also experiencing the same issue.

Are there any updates on this? I am also experiencing the same issue.

As a temporal solution you can 'patch' you training checkpoint to remove the metadata by doing: zip -d model.ckpt archive/anemoi-metadata/ai-models.json
after running that command you should be able to fork/resume your run since the checkpoint (model.ckpt) become readable by pytorch

Hi, I had this issue trying to run inference on a 9km model (the checkpoint is 3.3GB). With @gmertes help, the following steps resolved the issue. These commands make a copy of the json file, delete it inside the zip and then replace it with the copied version.
unzip -l inference-last.ckpt | grep json #prints the local path of the json within the checkpoint, in this case 'inference-last/anemoi-metadata/ai-models.json'
unzip -j inference-last.ckpt inference-last/anemoi-metadata/ai-models.json #extracts just ai-models.json from the zip and puts it in current directory
zip -d inference-last.ckpt inference-last/anemoi-metadata/ai-models.json #deletes the json file inside the zip
zip inference-last.ckpt inference-last/anemoi-metadata/ai-models.json #adds the copy outside back into the zip

recommenting bc of a bug with the old steps
Hi, I had this issue trying to run inference on a 9km model (the checkpoint is 3.3GB). With @gmertes help, the following steps resolved the issue. This is a script you can run which will fix your checkpoints. You just pass the checkpoint you want fixed as an input.
#!/bin/bash
set -xe
checkpoint=$1
file_name="ai-models.json"
file_zip_path=`unzip -l $checkpoint | grep $file_name | awk '{print $NF}'`
echo $file_zip_path
unzip -j $checkpoint $file_zip_path #copy the json out of the zip
zip -d $checkpoint $file_zip_path #delete the json inside the zip
zip $checkpoint "$file_zip_path" $file_name  #put the copy into the zip in the right place
rm $file_name #clean up by deleting the copy outside the zip

Can we deactivate saving of metadata for these checkpoints by default? Otherwise training of somewhat larger model becomes quite difficult.

Patching this in #166 for transfer learning.

@icedoom888 can you link to where this is patched in #166 please?

@icedoom888 can you link to where this is patched in #166 please?

@mchantry I had to remove the patch from #166.
Patching the checkpoint directly within the code caused issues in multi-gpu setting.
Now the checkpoint is expected to be patched beforehead using the aforementioned:
cp model.ckpt model_patched.ckpt
zip -d model_patched.ckpt archive/anemoi-metadata/ai-models.json

Fixed, by removing unused metadata file in #190


Point to correct Submariner URL in docs

Signed-Off-By: Janki Chhatbar<EMAIL_ADDRESS>(cherry picked from commit 8c27c712ff0b92f4f1d345f6cd0cfc157a89bfd6)
https://github.com/open-cluster-management/backlog/issues/16741

/assign @leena-jawale @KevinFCormier @Jaanki

/assign @chuckbrant

/cc @jamestalton


Name is No Longer Optional Attribute for 'Icon' component in Typescript

I have gone through these following points

[X]   Check latest documentation: https://docs.nativebase.io/
[X]   Check for existing open/closed issues for a possible duplicate before creating a new issue: https://github.com/GeekyAnts/NativeBase/issues
[X]   Use the latest NativeBase release: https://github.com/GeekyAnts/NativeBase/releases
[X]   Check examples from NativeBase KitchenSink https://github.com/GeekyAnts/NativeBase-KitchenSink
[]   For discussion purpose make use of NativeBase Slack: http://slack.nativebase.io/
[]   For queries related to theme, check Theme Variables from Docs and live NativeBase Theme Editor http://nativebase.io/customizer/

Issue Description
This fix (https://github.com/GeekyAnts/NativeBase/issues/960) has been removed in current version of index.d.ts for native base 2.12.1. Name is no longer optional. According to documentation Icon can be used without name but with android and ios properties.
Following is copy of documentation example of Icon:
import React, { Component } from 'react'; import { Container, Header, Content, Icon } from 'native-base'; export default class IconExample extends Component {   render() {     return (       <Container>         <Header />         <Content>           <Icon name='home' />           <Icon ios='ios-menu' android="md-menu" style={{fontSize: 20, color: 'red'}}/>           <Icon type="FontAwesome" name="home" />         </Content>       </Container>     );   } }
lines 642-653 of index.t.ts
interface Icon extends Testable { name: string; type?: "AntDesign" | "Entypo" | "EvilIcons" | "Feather" | "FontAwesome" | "FontAwesome5" | "Foundation" | "Ionicons" | "MaterialCommunityIcons" | "MaterialIcons" | "Octicons" | "SimpleLineIcons" | "Zocial"; // TODO position attribute of ReactNative.FlexStyle hasn't another position values without "absolute" and "relative" style?: any; onPress?: (e?: any) => any; active?: boolean; ios?: string; android?: string; color?: string; fontSize?: number; }
Example usage that triggers 'Property 'name' is missing in type...' error in Typescript:  <Icon active ios='ios-send' android='md-send />
node, npm, react-native, react and native-base version, expo version if used, xcode version
irrelevant
Expected behaviour
Typescript does not complain about only using ios and android properties of Icon.
Actual behaviour
Typescript complains that attribute name is missing
Steps to reproduce
-use Typescript and Icon with only ios and android attributes without name defined
Is the bug present in both iOS and Android or in any one of them?
Irrelevant
Any other additional info which would help us debug the issue quicker.

Has this been reviewed?

Hi @wardjk87 , Found no issue with Icon in Typescript with NativeBase v2.13.14 . Closing for now. Let us know if the issue still persists.


Request to do further research on this topic

Dear @luhaonan20,
I was going through base paper and code ,But some aspects of the codes I was not able to understand .Could you please provide the background knowledge for the model,
thanks in advance
Anmol

Dear @luhaonan20,
I was going through base paper and code ,But some aspects of the codes I was not able to understand .Could you please provide the background knowledge for the model,
thanks in advance
Anmol

Hi,
The idea is from the intuition of math and physics, use the group theory to model the different relation types in KGs. We will upload the new version of our paper recently and will let you know the progress later. :)
Cheers,
Haonan


NS-Cache: Do not use a time based filter for removing object_mds when performing eviction in cache buckets.

Part of issue: https://github.com/noobaa/noobaa-core/issues/6137
When object md has no constituent parts, we need to remove the object md from the database.
The current removal of the object mds is dependent on a bucket getting some chunks evicted. If there is no eviction, there can be object_mds in the database even though there is no activity on the objects.
The ideal fix will be to move the object_mds in a separate worker so it is not dependent on eviction.
This will be handled as part of complete fix for issue 6137
Explain the changes

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

@guptsanj Please rebase


Possible bug: backslash handling in clone

#134 adds support for a simple clone function that clones a git repository and also fetches the repository's gittuf refs. The clone function infers the name of a local directory when one isn't provided, much like the default git clone command. It's possible that the current implementation of this directory name inferencing mishandles backslashes in the repository URL.

This can likely be closed with the switch to the git binary.


Verify "Largest Series Product" exercise implementation

There was some confusion in this exercise due to the ambiguous use of the term consecutive in the README. This could be taken to mean contiguous, as in consecutive by position, or as in consecutive numerically. The the README has been fixed (https://github.com/exercism/x-common/pull/200).
Please verify that the exercise is implemented in this track correctly (that it finds series of contiguous numbers, not series of numbers that follow each other consecutively).
If it helps, the canonical inputs/outputs for the exercise can be found here:
https://github.com/exercism/x-common/blob/master/largest-series-product.json
If everything is fine, go ahead and just close this issue. If there's something to be done, then please describe the steps needed in order to close the issue.

None of the tests included in this track violates rules stated in the README.
But, there are interesting cases in the canonical inputs/outputs that could be added:
[
// ...
    {
        "description": "can get the largest product of a big number (Project Euler)",
        "digits": "7316717653133062491922511967442657474235534919493496983520312774506326239578318016984801869478851843858615607891129494954595017379583319528532088055111254069874715852386305071569329096329522744304355766896648950445244523161731856403098711121722383113622298934233803081353362766142828064444866452387493035890729629049156044077239071381051585930796086670172427121883998797908792274921901699720888093776657273330010533678812202354218097512545405947522435258490771167055601360483958644670632441572215539753697817977846174064955149290862569321978468622482839722413756570560574902614079729686524145351004748216637048440319989000889524345065854122758866688116427171479924442928230863465674813919123162824586178664583591245665294765456828489128831426076900422421902267105562632111110937054421750694165896040807198403850962455444362981230987879927244284909188845801561660979191338754992005240636899125607176060588611646710940507754100225698315520005593572972571636269561882670428252483600823257530420752963450",
        "span": 13,
        "expected":<PHONE_NUMBER>0
    },
    {
        "description": "reports zero if all spans include zero",
        "digits": "99099",
        "span": 3,
        "expected": 0
    },
    {
        "description": "rejects invalid character in digits",
        "digits": "1234a5",
        "span": 2,
        "expected": -1
    },
    {
        "description": "rejects negative span",
        "digits": "12345",
        "span": -1,
        "expected": -1
    }
]

And, one case that explains the weird (I found it weird the first time I read the specs) spec that returns 1 (the spec already exists, but not the explanation):
{
    "#": [
      "There may be some confusion about whether this should be 1 or error.",
      "The reasoning for it being 1 is this:",
      "There is one 0-character string contained in the empty string.",
      "That's the empty string itself.",
      "The empty product is 1 (the identity for multiplication).",
      "Therefore LSP('', 0) is 1.",
      "It's NOT the case that LSP('', 0) takes max of an empty list.",
      "So there is no error.",
      "Compare against LSP('123', 4):",
      "There are zero 4-character strings in '123'.",
      "So LSP('123', 4) really DOES take the max of an empty list.",
      "So LSP('123', 4) errors and LSP('', 0) does NOT."
    ],
    "description": "reports 1 for empty string and empty product (0 span)",
    "digits": "",
    "span": 0,
    "expected": 1
}

@rchavarria that last one is weird.  I thought it was in this track, but I must be remembering the java track.

@rchavarria are you proposing that we implement the 'interesting cases' you mentioned above?  Let me know,  is be happy to?

@matthewmorgan Yep, that cases are in the canonical inputs/outputs, but not on the track, so it would be nice to have them. Feel free to add them if you want.

OK I just tried to push this change, guessing GitHub is still having some issues.  Will try again soon.


im not able to set up this bot

i need help

Issue is 9 months old and totally irrelevant, might wanna close it?


developer workflow updates + CLI tool doc

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Creating a challenging backend to show the transpiler stochasticity

The documentation about the transpiler shows that the process is stochastic in https://docs.quantum.ibm.com/api/qiskit/transpiler#routing-stage:

In order to highlight this, we run a GHZ circuit 100 times, using a “bad” (disconnected) initial_layout:

This distribution is quite wide, signaling the difficulty the swap mapper is having in computing the best mapping.

Which is not very wide. That's because GenericFakeBackend replaced a FakeBackend in #11376. The GenericFakeBackend has an all-to-all connectivity by default.
This PR produces the following image:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.003%) to 89.341%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
2
92.37%

Totals

Change from base Build<PHONE_NUMBER>:
0.003%

Covered Lines:
60257

Relevant Lines:
67446

💛  - Coveralls


Laravel 8 support

Will you provide support for Laravel 8?
I'm currently unable to upgrade, since this library requires Laravel 6 or 7.

@thomeijken  Looks like version 6 has 8 support - https://github.com/TerrePorter/StringBladeCompiler/blob/6.0.3/composer.json


panic at rust_verify/src/rust_to_vir_base.rs

Hi all,
I am currently trying to use Verus to compile and check Linux Rust kernel modules. I encountered a panic while running Verus on the rnull driver (drivers/block/rnull.rs) from metaspace:rnull-6.7
When building this file, make eventually runs the following command (I only removed a few -Z and -D options):
$ export RUSTC_BOOTSTRAP=1
$ RUST_MODFILE=drivers/block/rnull rustc --edition=2021 @./include/generated/rustc_cfg \
    -Drust_2018_idioms -Zallow-features=new_uninit,offset_of,allocator_api,impl_trait_in_assoc_type \
    -Zcrate-attr='feature(new_uninit,offset_of,allocator_api,impl_trait_in_assoc_type)' --extern alloc \
    --extern kernel --crate-type rlib -L ./rust/ --crate-name rnull --out-dir drivers/block/ \
    --emit=dep-info=drivers/block/.rnull.o.d --emit=obj=drivers/block/rnull.o drivers/block/rnull.rs

I only kept the -Z flags which are absolutely necessary for the file to compile (they enable some nightly features).
Without even adding a verus! block, I tried to verify this file using the following command (I just replaced rustc by verus in the command above):
$ RUST_MODFILE=drivers/block/rnull.rs <path-to-verus> @./include/generated/rustc_cfg \
    -Zallow-features=new_uninit,offset_of,allocator_api,impl_trait_in_assoc_type \
    -Zcrate-attr='feature(new_uninit,offset_of,allocator_api,impl_trait_in_assoc_type)' \
    --extern alloc --extern kernel --crate-type rlib -L ./rust/ --crate-name rnull --out-dir drivers/block \
    --emit=dep-info=drivers/block/.rnull.o.d --emit=obj=drivers/block/rnull.o drivers/block/rnull.rs

and got the following errors
error[E0725]: the feature `stmt_expr_attributes` is not in the list of allowed features
 --> <crate attribute>:1:9
  |
1 | feature(stmt_expr_attributes)
  |         ^^^^^^^^^^^^^^^^^^^^

error[E0725]: the feature `box_patterns` is not in the list of allowed features
 --> <crate attribute>:1:9
  |
1 | feature(box_patterns)
  |         ^^^^^^^^^^^^

[...]

I then tried to remove the -Z flags that enable some nightly features.
$ RUST_MODFILE=drivers/block/rnull.rs <path-to-verus> @./include/generated/rustc_cfg --extern alloc \
    --extern kernel --crate-type rlib -L ./rust/ --crate-name rnull --out-dir drivers/block \
    --emit=dep-info=drivers/block/.rnull.o.d --emit=obj=drivers/block/rnull.o drivers/block/rnull.rs

and got the following error
error[E0658]: use of unstable library feature 'offset_of'
   --> drivers/block/rnull.rs:210:1
    |
210 | / kernel::impl_has_timer! {
211 | |     impl HasTimer<Self> for Pdu { self.timer }
212 | | }
    | |_^
    |
    = note: see issue #106655 <https://github.com/rust-lang/rust/issues/106655> for more information
    = help: add `#![feature(offset_of)]` to the crate attributes to enable
    = note: this error originates in the macro `kernel::impl_has_timer` (in Nightly builds, run with -Z macro-backtrace for more info)

I then followed the suggestions from the error message, adding attributes at the top of my file until Verus stopped suggesting me to do so
#![feature(offset_of)]
#![feature(allocator_api)]
#![feature(impl_trait_in_assoc_type)]

After rerunning Verus, I ended up getting a panic:
thread 'rustc' panicked at rust_verify/src/rust_to_vir_base.rs:154:28:
unhandled name DefId(0:158 ~ rnull[311a]::add_disk::{closure#0}::__InitOk)
stack backtrace:
   0:     0x7f55e5db66f6 - std::backtrace_rs::backtrace::libunwind::trace::hbee8a7973eeb6c93
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/../../backtrace/src/backtrace/libunwind.rs:104:5
   1:     0x7f55e5db66f6 - std::backtrace_rs::backtrace::trace_unsynchronized::hc8ac75eea3aa6899
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x7f55e5db66f6 - std::sys_common::backtrace::_print_fmt::hc7f3e3b5298b1083
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:68:5
   3:     0x7f55e5db66f6 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::hbb235daedd7c6190
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:44:22
   4:     0x7f55e5e08f40 - core::fmt::rt::Argument::fmt::h76c38a80d925a410
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/fmt/rt.rs:142:9
   5:     0x7f55e5e08f40 - core::fmt::write::h3ed6aeaa977c8e45
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/fmt/mod.rs:1120:17
   6:     0x7f55e5daa53f - std::io::Write::write_fmt::h78b18af5775fedb5
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/io/mod.rs:1810:15
   7:     0x7f55e5db64d4 - std::sys_common::backtrace::_print::h5d645a07e0fcfdbb
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:47:5
   8:     0x7f55e5db64d4 - std::sys_common::backtrace::print::h85035a511aafe7a8
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:34:9
   9:     0x7f55e5db9267 - std::panicking::default_hook::{{closure}}::hcce8cea212785a25
  10:     0x7f55e5db8fc9 - std::panicking::default_hook::hf5fcb0f213fe709a
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:292:9
  11:     0x7f55e5db9828 - std::panicking::rust_panic_with_hook::h095fccf1dc9379ee
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:779:13
  12:     0x7f55e5db9702 - std::panicking::begin_panic_handler::{{closure}}::h032ba12139b353db
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:657:13
  13:     0x7f55e5db6bf6 - std::sys_common::backtrace::__rust_end_short_backtrace::h9259bc2ff8fd0f76
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys_common/backtrace.rs:171:18
  14:     0x7f55e5db9460 - rust_begin_unwind
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/panicking.rs:645:5
  15:     0x7f55e5e05645 - core::panicking::panic_fmt::h784f20a50eaab275
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/core/src/panicking.rs:72:14
  16:     0x562f53e9f8f7 - rust_verify::rust_to_vir_base::def_id_to_vir_path::h3caef56d9d863069
  17:     0x562f53da276b - rust_verify::rust_to_vir::check_item::h46516ae08cb5cc00
  18:     0x562f53da90b9 - rust_verify::rust_to_vir::crate_to_vir::hf7e107487f543039
  19:     0x562f53e2554c - rust_verify::verifier::Verifier::construct_vir_crate::hc9c6a87369536c95
  20:     0x562f53df3bf0 - rustc_middle::ty::context::GlobalCtxt::enter::h5ab9270d552770ea
  21:     0x562f53e28df5 - <rust_verify::verifier::VerifierCallbacksEraseMacro as rustc_driver_impl::Callbacks>::after_expansion::h486666fd3d17e265
  22:     0x7f55e4afe63a - rustc_interface[bf5cafa581ab7832]::interface::run_compiler::<core[f975038e3cc9791c]::result::Result<(), rustc_span[7a149c27976a99e7]::ErrorGuaranteed>, rustc_driver_impl[66ed8fdbde15dc6c]::run_compiler::{closure#0}>::{closure#0}
  23:     0x7f55e4c2c7db - std[79729d9c385e1623]::sys_common::backtrace::__rust_begin_short_backtrace::<rustc_interface[bf5cafa581ab7832]::util::run_in_thread_with_globals<rustc_interface[bf5cafa581ab7832]::interface::run_compiler<core[f975038e3cc9791c]::result::Result<(), rustc_span[7a149c27976a99e7]::ErrorGuaranteed>, rustc_driver_impl[66ed8fdbde15dc6c]::run_compiler::{closure#0}>::{closure#0}, core[f975038e3cc9791c]::result::Result<(), rustc_span[7a149c27976a99e7]::ErrorGuaranteed>>::{closure#0}::{closure#0}, core[f975038e3cc9791c]::result::Result<(), rustc_span[7a149c27976a99e7]::ErrorGuaranteed>>
  24:     0x7f55e4c2c639 - <<std[79729d9c385e1623]::thread::Builder>::spawn_unchecked_<rustc_interface[bf5cafa581ab7832]::util::run_in_thread_with_globals<rustc_interface[bf5cafa581ab7832]::interface::run_compiler<core[f975038e3cc9791c]::result::Result<(), rustc_span[7a149c27976a99e7]::ErrorGuaranteed>, rustc_driver_impl[66ed8fdbde15dc6c]::run_compiler::{closure#0}>::{closure#0}, core[f975038e3cc9791c]::result::Result<(), rustc_span[7a149c27976a99e7]::ErrorGuaranteed>>::{closure#0}::{closure#0}, core[f975038e3cc9791c]::result::Result<(), rustc_span[7a149c27976a99e7]::ErrorGuaranteed>>::{closure#1} as core[f975038e3cc9791c]::ops::function::FnOnce<()>>::call_once::{shim:vtable#0}
  25:     0x7f55e5dc38e5 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h12de4fc57affb195
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/alloc/src/boxed.rs:2015:9
  26:     0x7f55e5dc38e5 - <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once::h3c619f45059d5cf1
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/alloc/src/boxed.rs:2015:9
  27:     0x7f55e5dc38e5 - std::sys::unix::thread::Thread::new::thread_start::hbac657605e4b7389
                               at /rustc/07dca489ac2d933c78d3c5158e3f43beefeb02ce/library/std/src/sys/unix/thread.rs:108:17
  28:     0x7f55dfeac897 - start_thread
  29:     0x7f55dff33a5c - __clone3
  30:                0x0 - <unknown>

I don't really understand what could cause such an issue. Maybe the above mentioned nightly features are not supported by verus ? It also seems odd to me that enabling the nightly features with the -Z flags or using #![] attributes at the top of my file give different results.
If you have any idea about what might be causing my problem or where I could look to find out more, I would be glad to know!

The key line is this one: unhandled name DefId(0:158 ~ rnull[311a]::add_disk::{closure#0}::__InitOk)
It looks like __InitOk (which appears to be declared from a macro expansion inside add_disk) is a nested item. Verus doesn't support nested items. Normally, it ought to be OK anyway because you haven't asked Verus to verify add_disk, so I think this must be a Verus bug.

Thank you very much! I'll try to get around the problem for now. If you need to reproduce the bug, feel free to ask. I'll be glad to provide detailed reproducible instructions!

 I ask because I fixed a related bug just a couple of weeks ago, so I wonder if the issue is that you have an older Verus.

I am using the commit bd46b8dcaf5e5a72ca0fefb965b61e4ddbdb5030 (branch main, Apr 7, 2024)

I just managed to get around my problem by adding the line
            DefPathData::Closure => {}

in the function def_path_to_vir_path from rust_verify/src/rust_to_vir_base.rs
fn def_path_to_vir_path<'tcx>(tcx: TyCtxt<'tcx>, def_path: DefPath) -> Option<Path> {
    let multi_crate = MULTI_CRATE.with(|m| m.load(std::sync::atomic::Ordering::Relaxed));
    let krate = if def_path.krate == LOCAL_CRATE && !multi_crate {
        None
    } else {
        Some(Arc::new(tcx.crate_name(def_path.krate).to_string()))
    };
    let mut segments: Vec<vir::ast::Ident> = Vec::new();
    for d in def_path.data.iter() {
        use rustc_hir::definitions::DefPathData;
        match &d.data {
            DefPathData::ValueNs(symbol) | DefPathData::TypeNs(symbol) => {
                segments.push(Arc::new(symbol.to_string()));
            }
            DefPathData::Ctor => {
                segments.push(Arc::new(vir::def::RUST_DEF_CTOR.to_string()));
            }
            DefPathData::Impl => {
                segments.push(vir::def::impl_ident(d.disambiguator));
            }
            DefPathData::ForeignMod => {
                // this segment can be ignored
            }
            DefPathData::Closure => {}
            _ => return None,
        }
    }
    Some(Arc::new(PathX { krate, segments: Arc::new(segments) }))
}

I realized that when running Verus without a verus block on my file, d.data is a DefPathData::Closure at some point, which causes Verus to panic without the line I added.
I don't know if its a viable solution to my bug. I'd be glad to provide additional information. Thanks for your help!

Thanks for finding the root of this problem.  I think I now understand what's going on based on the information you've provided.  I believe we should not be calling def_path_to_vir_path at all for external items that might cause def_path_to_vir_path to panic.  Can you try out pull request https://github.com/verus-lang/verus/pull/1074 to see if it solves the issue?

I tried out your PR and it indeed solves the issue! Thank you so much!


Does it or will it support Vicuna-13b-v1.1 finetuning?

Thanks for creating such an amazing project.
Vicuna-13b-v1.1 seems to achieve impressive performance in tasks in multiple languages. I believe it would be a good idea to conduct further fine-tuning based on it. So, will this project support Vicuna-13b-v1.1 finetuning later?

Hi,
Thank you very much for your interest in our work.
We will support vicuna-13b-v1.1 very soon.


SetupDiag Link does not work

Setupdiag link throws a 404 Page not found error.

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

ID: b3d6356b-87ff-8c3a-56ef-1270a823d3ab
Version Independent ID: 4d6ae878-66cf-0e10-bdf3-bdd6054cbc9d
Content: What's new in Windows 10, version 1809
Content Source: windows/whats-new/whats-new-windows-10-version-1809.md
Product: w10
GitHub Login: @greg-lindsay
Microsoft Alias: trudyha

Created PR https://github.com/MicrosoftDocs/windows-itpro-docs/pull/3135

@officedocsbot close


Add glossary for 'task'

A task!
Might actually be good to link off to https://docs.gradle.org/current/userguide/more_about_tasks.html but wasn't sure how to put it in

I committed through the browser so couldn't squash sorry, but I think when you hit merge there is an option to squash? :-)


Add channel calendar limitation to private-channels.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/9959

@MikePlumleyMSFT
PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


feat: Fix timeout and read functions

Set read and write timeouts for the stream
Set keep alive for the stream
Retry reading up to 3 times in case of a 'WouldBlock' error
Update the read function to return the number of bytes read

finish #6


[clkmgr] Security enhancements

As part of reviews, it was determined that clkmgr needs to some basic security enhancements

clock frequency measurement to ensure clocks are not drifting away from their intended targets.

if the clock frequency measurement fails, a alert must be triggered.
This will be done only for the fixed frequencies as the jittery clock will anyways change on average.

@dsandrs
let me know what you guys think of this item.  This was a result from the security reviews and I want to make sure we give it some thought.

I will let Matute assess (and update the clkmgr testplan) these enhancements. For the chip level, the alert will get  tested as a part of the common alert test. LMK if there is any other impact at the chip level, otherwise this seem contained within the IP.


Return validation details

Return a list of all invalid inputs to postUser

Review not necessary but will leave PR here for you guys to take a look until tomorrow. Will merge then.


Program returned error: SBF program panicked

Hello, can you help me with my problem? Thank you very much
https://solscan.io/tx/qCZYK1ACG6RwLjE9jZZaeDZzuzfnz5SZTgqv34peQevfWo8DMvc3gC7CfqnbkiM7MLxYeXwrATqpL5icvH8TygH

Hi, can you share your input? It's hard to say just from the tx.

const privateKey = ""; // Replace with your actual private key
const mintAddress = "BjjvKX5k7gQoGRmvQAA5WMr7EkQ2cirGTSGxAznDpump"; //Replace with actual token mint address
const txMode = TransactionMode.Execution; //Set to simulate to test, Execution to perform
const solIn = 0.03; // Example value, adjust as needed
const slippageDecimal = 0.25; // Example value, adjust as needed
const tokenBalance = 10000; // Example value, adjust as needed
const priorityFeeInSol = 0.001; // Example value for tip to get faster inclusion, adjust as needed
await pumpFunBuy(
this.transactionMode,
this.payerPrivateKey,
this.mintAddress,
solIn,
priorityFeeInSol,
slippageDecimal
);
This one?

Could there be something wrong with my json rpc? quicknode

Work out


Need a ruby-debug 0.11.0 release

Recently we got a fix out in ruby-debug-base 0.11.0 for JRuby, but because ruby-debug has not had a release it's not possible to resolve both in a Gemfile.
See https://github.com/jruby/jruby/issues/6018#issuecomment-584660437

+1 ...

What would be necessary in order for this release to happen? Is there any work you need done that an outsider could do?

@ViugiNick are you able to release this as well?  Looks like just releasing base does not line up numberwise.

I believe this can be closed with the latest ruby-debug release by @ViugiNick: https://github.com/jruby/jruby/issues/6018#issuecomment-600452838

Specifying version '0.11.0' in my gemfile causes a failure to install:
Bundler could not find compatible versions for gem "ruby-debug-base":
  In Gemfile:
    ruby-debug (= 0.11.0) was resolved to 0.11.0, which depends on
      ruby-debug-base (~> <IP_ADDRESS>)

Could not find gem 'ruby-debug-base (~> <IP_ADDRESS>)', which is required by gem
'ruby-debug (= 0.11.0)', in any of the sources.

Does  ruby-debug-base (~> <IP_ADDRESS>) even make any sense? Am I doing something wrong?

looks like it's asking for <IP_ADDRESS> because of this line in the gemspec:
https://github.com/ruby-debug/ruby-debug/blob/ecc865ac9373cb9ec4975b2433fffd79915d9e93/ruby-debug.gemspec#L34
Wondering why this ever worked, given that this line has been unchanged for several years.

It seems that the dependency on ruby-debug-base is very narrow, requiring an exact match, which in turn means that all gems must be released in lock-step.
We need to get a ruby-debug-base release of 0.11.0 and in the future we need a way to guarantee that these gems are all being released at the same time.
Alternatively, if ruby-debug can go with a softer dependency and still work that might mean we don't have to force a release of ruby-debug-base for every ruby-debug release.
I would really like to get this resolve... we get periodic reports about debugging not working and we can't do much about it when the gems are not getting released.
@ViugiNick Are you still the point of contact on this? How can we help maintain this gem, including getting releases out as needed?

It seems that the dependency on ruby-debug-base is very narrow, requiring an exact match, which in turn means that all gems must be released in lock-step.
We need to get a ruby-debug-base release of 0.11.0 and in the future we need a way to guarantee that these gems are all being released at the same time.
Alternatively, if ruby-debug can go with a softer dependency and still work that might mean we don't have to force a release of ruby-debug-base for every ruby-debug release.
I would really like to get this resolve... we get periodic reports about debugging not working and we can't do much about it when the gems are not getting released.
@ViugiNick Are you still the point of contact on this? How can we help maintain this gem, including getting releases out as needed?

So I was doing some fighting against this today on jruby-<IP_ADDRESS> and ran into differing behavior based on bundler version.
On bundler version 2.1.2, I can happily install ruby-debug 0.11.0. But once it's installed and the Gemfile.lock updated, trying to do bundler install yields this error:
Bundler could not find compatible versions for gem "ruby-debug-base":
  In snapshot (Gemfile.lock):
    ruby-debug-base (= 0.11.0)

  In Gemfile:
    ruby-debug java was resolved to 0.11.0, which depends on
      ruby-debug-base (~> <IP_ADDRESS>)

and in order to make updates to other gems in the Gemfile, I have to run bundle update ruby-debug ruby-debug-base (which is pretty annoying).
On bundler version 2.2.4 (which is included with jruby-<IP_ADDRESS> for example), I couldn't install ruby-debug 0.11.0 or 0.10.6 at all. Instead it installs 0.10.4. Looking at rubygems, I can't see any reason for this to happen, my only guess was that bundler was being stricter about installing ruby-debug-base version 0.11.0 as fulfilling the gemspec requirement for ~> <IP_ADDRESS> but nothing actually jumps out at me among the published versions. I scanned the gemspecs for the two versions too, but nothing jumped out at me there either.

So I was doing some fighting against this today on jruby-<IP_ADDRESS> and ran into differing behavior based on bundler version.
On bundler version 2.1.2, I can happily install ruby-debug 0.11.0. But once it's installed and the Gemfile.lock updated, trying to do bundler install yields this error:
Bundler could not find compatible versions for gem "ruby-debug-base":
  In snapshot (Gemfile.lock):
    ruby-debug-base (= 0.11.0)

  In Gemfile:
    ruby-debug java was resolved to 0.11.0, which depends on
      ruby-debug-base (~> <IP_ADDRESS>)

and in order to make updates to other gems in the Gemfile, I have to run bundle update ruby-debug ruby-debug-base (which is pretty annoying).
On bundler version 2.2.4 (which is included with jruby-<IP_ADDRESS> for example), I couldn't install ruby-debug 0.11.0 or 0.10.6 at all. Instead it installs 0.10.4. Looking at rubygems, I can't see any reason for this to happen, my only guess was that bundler was being stricter about installing ruby-debug-base version 0.11.0 as fulfilling the gemspec requirement for ~> <IP_ADDRESS> but nothing actually jumps out at me among the published versions. I scanned the gemspecs for the two versions too, but nothing jumped out at me there either.


devenv shell not working with paths with spaces

Describe the bug
devenv init and devenv shell don't play nice with paths with spaces
To reproduce
mkdir -p '/tmp/proof of concept'
cd '/tmp/proof of concept'
git init
devenv init

last command output is:
[zarel@tantra:/tmp/proof of concept]$ devenv init
Creating .envrc
Creating devenv.nix
Creating devenv.yaml
Appending defaults to .gitignore
Done.
direnv is installed. Running direnv allow.
direnv: loading /tmp/proof of concept/.envrc
direnv: loading https://raw.githubusercontent.com/cachix/devenv/d1f7b48e35e6dee421cfd0f51481d17f77586997/direnvrc (sha256-YBzqskFZxmNb3kYVoKD9ZixoPXJh1C9ZvTLGFRkauZ0=)
direnv: using devenv
direnv: .envrc changed, reloading
Building shell ...
error:
       error: 'file:///tmp/proof of concept' is not a valid URL
direnv: loading the environment failed
direnv: error exit status 1

Version
devenv: 0.6.3

I'm just about to publish a rewrite of CLI in Python, which should fix this.

Could you try https://github.com/cachix/devenv/pull/745 by installing python-rewrite branch?

The python rewrite right now is not working with this case but that's okay it's just a small nuisance for me:
[zarel@tantra:/tmp/proof of concept]$ devenv init
Creating devenv.nix
Creating devenv.yaml
Creating .envrc
Appending defaults to .gitignore
Done.
direnv is installed. Running $ direnv allow .
direnv: loading /tmp/proof of concept/.envrc
direnv: loading https://raw.githubusercontent.com/cachix/devenv/d1f7b48e35e6dee421cfd0f51481d17f77586997/direnvrc (sha256-YBzqskFZxmNb3kYVoKD9ZixoPXJh1C9ZvTLGFRkauZ0=)
direnv: using devenv
direnv: .envrc changed, reloading
Traceback (most recent call last):
  File "/nix/store/8fpiimbs1c22vdpv21bi1lzaqwnin7zs-python3.10-devenv-1.0/bin/.devenv-wrapped", line 9, in <module>
    sys.exit(cli())
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/nix/store/8fpiimbs1c22vdpv21bi1lzaqwnin7zs-python3.10-devenv-1.0/lib/python3.10/site-packages/devenv/cli.py", line 418, in print_dev_env
    env = shell()
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/nix/store/vzfvszdsa9mdz4rpy03n6c7qh37g91dc-python3.10-click-8.1.6/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/nix/store/8fpiimbs1c22vdpv21bi1lzaqwnin7zs-python3.10-devenv-1.0/lib/python3.10/site-packages/devenv/cli.py", line 201, in shell
    run_assemble()
  File "/nix/store/8fpiimbs1c22vdpv21bi1lzaqwnin7zs-python3.10-devenv-1.0/lib/python3.10/site-packages/devenv/cli.py", line 132, in run_assemble
    system = click.get_current_context().obj['system']
TypeError: 'NoneType' object is not subscriptable
direnv: loading the environment failed
direnv: error exit status 1

@zarelit thanks for reporting that, I've fixed it in the latest branch, can you try again?

Hi @domenkozar thank you again for your support, unfortunately I have to report this outcome:
[zarel@tantra:/tmp/proof of concept]$ devenv init
Creating devenv.nix
Creating devenv.yaml
Creating .envrc
Appending defaults to .gitignore
Done.
direnv is installed. Running $ direnv allow .
direnv: loading /tmp/proof of concept/.envrc
direnv: loading https://raw.githubusercontent.com/cachix/devenv/d1f7b48e35e6dee421cfd0f51481d17f77586997/direnvrc (sha256-YBzqskFZxmNb3kYVoKD9ZixoPXJh1C9ZvTLGFRkauZ0=)
direnv: using devenv
direnv: .envrc changed, reloading
error:
       error: unexpected argument 'concept/.devenv/gc/shell'
Try '/nix/store/y7jg84kb2kr0rln9a33jdlk6vkzkh9ii-nix-2.12.0pre20230216_7c91803/bin/nix --help' for more information.
Error: Following command exited with code 1:

  /nix/store/y7jg84kb2kr0rln9a33jdlk6vkzkh9ii-nix-2.12.0pre20230216_7c91803/bin/nix --show-trace --extra-experimental-features "nix-command flakes" --option warn-dirty false --system x86_64-linux print-dev-env --impure --profile /tmp/proof of concept/.devenv/gc/shell
direnv: loading the environment failed
direnv: error exit status 1

and devenv info
[zarel@tantra:/tmp/proof of concept]$ devenv info
error:
       error: 'file:///tmp/proof of concept' is not a valid URL
Error: Following command exited with code 1:

  /nix/store/y7jg84kb2kr0rln9a33jdlk6vkzkh9ii-nix-2.12.0pre20230216_7c91803/bin/nix --show-trace --extra-experimental-features "nix-command flakes" --option warn-dirty false --system x86_64-linux flake metadata

To reproduce:
/nix/store/hxrvmv3vvcw2g9z8kfxmnyd17s1dgxf3-python3.11-devenv-1.0/bin/devenv print-dev-env
path '/home/domen/dev/foo bar/bar/.devenv/gc/shell' does not contain a '.devenv.flake.nix', searching up
error:
       error: getting status of '/home/domen/dev/foo bar/bar/.devenv/gc/shell': No such file or directory
Error: Following command exited with code 1:

  /nix/store/y7jg84kb2kr0rln9a33jdlk6vkzkh9ii-nix-2.12.0pre20230216_7c91803/bin/nix --show-trace --extra-experimental-features "nix-command flakes" --option warn-dirty false --system x86_64-linux print-dev-env --impure --profile /home/domen/dev/foo bar/.devenv/gc/shell

This should be fixed in the latest branch. Thanks!

I can also confirm it's working since 1.0.0 :-) thank you @domenkozar and the rest of the devenv team

Actually before <IP_ADDRESS> it was not able to "devenv init" but actually using it keeps giving errors. Keeping this issue closed in favor of #1107


Root Password Change?

good day
first of all thank you for your great tutorial :)
i am trying to change the password on my root account but unfortunately it is not saved.
i log in with sudo su root and try to change it with passwd. i get the message: password updated successfully. but the old password is still saved?
thanks for the help and have a nice day :)
greetings waffi

@waffi121 , you have opened an issue which is ment for issue reporting, not support. Do a quick search at the internet and you will find support for this. Please close this issue ASAP.
Two hints:
Set a password for root:
sudo passwd root
Test root password:
su -
Second, disable root account, or at least make sure it cannot be used to login with ssh. You'll find many great guides with practices etc. Good luck with the learning process! :)


Create new release for current state of master

Hi there, I was just wondering if you could cut a new tag for the 6 commits since the last release. I was hoping to avoid forking the repo or pointing composer directly at the master branch. Thanks!

Release v1.1.0 has been tagged.
https://github.com/steverhoades/oauth2-openid-connect-server/releases/tag/v1.1.0


Proxy setting on Android blocks access to Listener

Steps to reproduce:

Enable a proxy setting in the network tab of the Android Wifi panel -> http://cl.ly/070J1u133W16/a7xeltexxLMY47Xjamesnocentini02152016224058.png

Then the "Unable to connect to the proxy server" page is displayed for http://localhost:5984 -> http://cl.ly/0x0D031X3r0m/a7xeltexxLMY47Xjamesnocentini02152016222339.png

The workaround is to add localhost in the "Bypass proxy for" section in the proxy settings.
Is there a way that the Listener could automatically enable this? Maybe something similar to how couchbase-lite-ios does it by using an internal URL only accessible within the app.

@jamiltz,
As WebView (browser), which is used from PhoneGap, can not reach to localhost:5984, it is not Listener issue.
User might be able to set Proxy setting by them self with following  samples.

http://stackoverflow.com/questions/12486441/how-can-i-set-proxysettings-and-proxyproperties-on-android-wi-fi-connection-usin
http://grepcode.com/file/repo1.maven.org/maven2/org.robolectric/android-all/5.0.0_r2-robolectric-0/android/net/ProxyInfo.java
http://grepcode.com/file/repo1.maven.org/maven2/org.robolectric/android-all/5.0.0_r2-robolectric-0/android/net/ProxyInfo.java

@jamiltz, Can we close this ticket? Please let us know.

Yes sure. Thanks for the links!


How to refresh Xpand Dashbboard

Hi all,
Can someone advise me how to refresh dashboard ? I tried to click on Refresh button and all data becomes blank on dashboard

try a screenshot please so we can follow u easier and most probably the log would be helpful in this case.

Hi,
I am using this xml below, 1st open is loading  all data which we expected. However, click on refresh button on the top makes dashboard data blank. I am leaving xpand setting as default as very new to it. Hope this clears

eCourierPickup

[DeletedDate] Is Null And [CreatedDate] > #2018-06-03#

`

eCourierPickup

[DeletedDate] Is Null And [CreatedDate] > #2018-06-03#

`

try this

`

eCourierPickup

[DeletedDate] Is Null And [CreatedDate] > #2018-06-03#

[]
`

Sorry I could not post xml
I am using this xml below, 1st open is loading all data which we expected. However, click on refresh button on the top makes dashboard data blank. I am leaving xpand setting as default as very new to it. Hope this clears. I hope with any data changed, dashboard would be changed accordingly when click on refresh

it should be enough give me some time please as I am loaded at the moment and see my previous post on how to post your xml
<?xml version="1.0" encoding="utf-8"?>
<Application >

</Application>

Thank you very much for your prompt help. XML as below
<?xml version="1.0" encoding="utf-8"?>
<Dashboard CurrencyCulture="en-US">
  <Title Text="Dashboard" />
  <DataSources>
    <ObjectDataSource ComponentName="eCourierPickup">
      <Name>eCourierPickup</Name>
      <DataSource Type="TestObject.eCourierPickup, Module, Version=1.0.6823.15619, Culture=neutral, PublicKeyToken=null" />
      <Filter>[DeletedDate] Is Null And [CreatedDate] > #2018-06-03#</Filter>
    </ObjectDataSource>
  </DataSources>
  <Items>
    <Pivot ComponentName="pivotDashboardItem1" Name="Pivot 1" DataSource="eCourierPickup">
      <DataItems>
        <Measure DataMember="Id" DefaultId="DataItem1" />
        <Dimension DataMember="Caption" DefaultId="DataItem0" />
      </DataItems>
      <Columns>
        <Column DefaultId="DataItem0" />
      </Columns>
      <Values>
        <Value DefaultId="DataItem1" />
      </Values>
    </Pivot>
  </Items>
  <LayoutTree>
    <LayoutGroup>
      <LayoutItem DashboardItem="pivotDashboardItem1" />
    </LayoutGroup>
  </LayoutTree>
</Dashboard>

your xml has nothing strange but I do not understand how to repro it. Which refresh you hit DataboardDefintion_DetailView?
can you provide your sample solution ?

`Internal error. Please contact the application vendor or your system administrator and provide the following information.
DevExpress.Data.Filtering.CriteriaCompilerException: Error 'Can't find property 'DeletedDate'' at '[DeletedDate]' compiling criteria '[DeletedDate] Is Null And AddDays([CreatedDate], 5) > Now()' ---> DevExpress.Data.Filtering.Exceptions.InvalidPropertyPathException: Can't find property 'DeletedDate'
at DevExpress.Data.Filtering.Helpers.CriteriaCompilerContextDescriptorDefaultBase.MakePropertyAccessCoreChecked(Expression baseExpression, String property)
at DevExpress.Data.Filtering.Helpers.CriteriaCompilerContextDescriptorDefaultBase.MakePropertyAccess(Expression baseExpression, String propertyPath)
at DevExpress.Data.Filtering.Helpers.CriteriaCompilerCore.Process(CriteriaOperator criteria)
--- End of inner exception stack trace ---
at DevExpress.Data.Filtering.Helpers.CriteriaCompilerCore.Compile(CriteriaCompilerDescriptor descriptor, CriteriaCompilerAuxSettings settings, CriteriaOperator op)
at DevExpress.DataProcessing.DataReaderExEnumerableWrapper.CreateFilterPredicate(CriteriaOperator filterCriteria)
at DevExpress.DataProcessing.DataReaderExEnumerableWrapper..ctor(String[] dataMembers, IEnumerable source, PropertyDescriptorCollection properties, CustomFunctionCollection customFunctions, CriteriaOperator filterCriteria, Int32 numberOfRows)
at DevExpress.DashboardCommon.DashboardObjectDataSource.ExecuteReader(Action1 action, CriteriaOperator filterCriteria, Int32 numberOfRows, String[] schema)    at DevExpress.DashboardCommon.DashboardObjectDataSource.GetStorageInternal(CancellationToken token)    at DevExpress.DashboardCommon.DashboardObjectDataSource.DevExpress.DashboardCommon.Native.IDashboardDataSourceInternal.GetStorage(String dataMember)    at DevExpress.DashboardCommon.DataProcessing.DataSourceModel.Create(IDashboardDataSource ds, String dataMember)    at DevExpress.DashboardCommon.DataProcessing.DataSourceModel.Create(IDashboardDataSource ds, String dataMember, IDataFlowStorage storage)    at DevExpress.DashboardCommon.Native.DataSourceModelsProvider.GetDataSourceModel(String dataSourceName, String dataMember, IDataFlowStorage storage)    at DevExpress.DashboardCommon.Native.DashboardColoringValuesProvider.GetColoringValuesCore(IDataSourceMetadata dataSourceMetadata, String dataMember, IEnumerable1 definitions, IEnumerable1 filterDimensions, CriteriaOperator filter, IList1 dashboardItems, IEnumerable1 items, IActualParametersProvider parameters)    at DevExpress.DashboardCommon.Native.DashboardColoringValuesProvider.DevExpress.DashboardCommon.Native.IColoringValuesProvider.GetColoringValues(ColorRepositoryKey repositoryKey)    at DevExpress.DashboardCommon.Native.ColorSchemeGenerator.BuildTable(ColorRepositoryKey repositoryKey, MeasureDefinition[][] measures)    at DevExpress.DashboardCommon.Native.ColorSchemeGenerator.GenerateColoring()    at DevExpress.DashboardCommon.Native.ColorSchemeGenerator.GenerateColoringCache(IColoringValuesProvider provider, ColorRepository repository, Int32 paletteColorsCount)    at DevExpress.DashboardCommon.Server.DashboardSession.EnsureDashboardColoringCache()    at DevExpress.DashboardCommon.Service.DashboardServiceOperation1.Execute(DashboardServiceResult result)
If I am putting the filter under data source then the error message above showing up, although the last version of xpand works well. The issue only happens when I upgraded to xpand 18.1.5. I am struggling with Refresh button and tried to fix that.  If no filter putting into data source then click on Refresh no error but data on dashboard becomes blank. The below screenshot is where we click on Refresh.

`

Can you try this path. It includes #157 in which the related to your case easytest works fine.
https://github.com/eXpandFramework/eXpand/tree/18.1/Demos/Modules/SystemTester/SystemTester.Module/FunctionalTests/SequenceGenerator

you do not need to modify anything from MSSQLConnectionProvider and its descendants

Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.


Added example for fine tuning BERT on Text Extraction task (SQuAD)

Uses pretrained bert-base-uncased from HuggingFace and their tokenizers.
Gets an exact match score of 79.4 after 2 epoch on TPU. (Paper shows 80.8, most likely due to a bunch of extra post-processing steps that I saw in the original implementation while converting the predicted token indexes back to the answer text)
We will have to limit the data before training begins because this will take hours on CPU.

Thanks for the comments. Making the required changes.

I'll be running the make command on my laptop. So, I'll change
use_tpu = False

and add some lines like
# Remove these lines to train on the entire data
x_train  = [_[:10,:] for _ in x_train]
y_train  = [_[:10,:] for _ in y_train]
model.fit(x_train, y_train, ...)

Or is there a better way?

How long does it take to run the example on a V100?

1 epoch took 1 hour 12 min on Colab GPU (K80 I think?).
Anyhow, I copied everything over to Colab, and ran python autogen.py add_example ... with TPU runtime. Generated files have been added.
I set epochs=1 for this.


Lower bound and upper bound in find_optimum_budget function can produce unintuitive result

Due to the slight differences between how _generate_starting_values and _get_lower_and_upper_bounds differ in calculating the budget allocated to each channel, when setting percentages lower bound or upper bound, it is hard for user to know what is the reference point.
For example in my case, a channel has 41% spend in starting_values with a 0 pct upper bound (we cannot scale this channel any further) can still produce a 52% allocation in the final solution due to the _get_lower_and_upper_bounds function referencing mean values for media data.
Is it better to pass in absolute values for lower and upper bound in this case? Or it is better for these two functions to use consistent calculation methodologies?

_generate_starting_values and _get_lower_and_upper_bounds differ in calculation by design. The optimisation itself works on "media unit" but the constraint within it needs to use the budget to make sure the constraint of "using all the budget" is met along the way. That is why the bounds are based on an average of historic media unit and the starting values include the budget in that calculation (also note that starting values dont really need to include budget and we only do that so we can provide the user an average value they can compare against after the optimisation, starting values could be random technically).
I think the current behaviour that you are finding is due to #82 (which should be fixed this week). The best thing is to ignore the third output on optimize_media. find_optimal_budgets and calculate yourself some average budget you want to compare against.
Since the prices and bounds are both per channel calculating the bounds in monetary value and then converting back to media unit, or calculating them in media unit directly should yield the same result.
Let me know if Im somehow miss-understanding the issue you are finding.


Added Server-Side Swift newsletter

Project URL
https://www.serverswift.tech
Description
This PR adds a new newsletter (Server-Side Swift Newsletter) to the newsletters list.
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 7 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

Thanks for contributing, @explicitcall!


Release 2023-07-06 (add pg_embedding extension only)

pg_embedding extension release

Covered by the https://neon.tech/docs/release-notes/2023-07-12-storage-and-compute release.


Xcode 12.1 replaced silently with Xcode 12.1.1 RC?

At some point today it seems that /Applications/Xcode_12.1.app/ was updated from Xcode 12.1 to Xcode 12.1.1 (which as of right now is still a release candidate).
This is on the macOS-10.15 image

Hello @asnaith , usually, we install the latest Xcode for every major.minor pair.
For example, when Xcode 12.0.1 is released, we replace 12.0.0 by 12.0.1 (except cases when it is beta release)
Changing of patch version (third number) doesn't bring breaking changes because of semantic versioning and RC means that most likely this version will be officially published as stable.
Do you have any use-cases that are broken after this change?

12.1.1 is not even released and it is breaking because it does not have ios14.1 simulators but only ios14.2 simulators
you need to test a bit before you deploy such things:
Run export DEVELOPER_DIR=/Applications/Xcode_12.1.app/Contents/Developer && xcodebuild test -scheme App -workspace ios/App/App.xcworkspace -destination 'platform=iOS Simulator,name=iPhone 12,OS=14.1' | xcpretty && exit

xcodebuild: error: Unable to find a destination matching the provided destination specifier:
		{ platform:iOS Simulator, OS:14.1, name:iPhone 12 }

We are rolling back image. You can track progress in #1984


Documentation update: Fixed minor grammatical and spelling errors

What this PR does / why we need it:
This PR cleans up some grammatical and spelling errors found within the README and documentation for Litmus. These include fixing capitalization, adding commas where appropriate, and fixing slight typos.

@silvia-odwyer , can you please fix the failed DCO check/i.e., sign your commits ?

Hi @silvia-odwyer , firstly, thanks for your interest in contributing to Litmus and secondly, for your patience in trying to merge other changes/attempt sign-off. If it is not asking for too much, can you please close this PR and raise a new one w/ your changes alone ? (The DCO continues to bother and the travis CI fails - which I believe is fixed in later PRs).  Thanks again!


Added the stinson filter

I have added the stinson filter. I have tested it using the test files you provide (well folder), and it works like a charm!

Hey, can you edit just stinson.scss, cssgram.scss, and the json data file? A great example is #210


[TopoFR] result on MFR

I found your model on MFR: http://iccv21-mfr.com/#/leaderboard/academic
Is that correct? Which dataset did you use for training?
Have you tried training with WF42M, and if so, what were your results?

Hi @TranThanh96 ~
In fact, the model we published on MFR was trained using the WebFace42M dataset. For a detailed analysis of the results, please refer to our paper. It is worth mentioning that to ensure our TopoFR model achieves outstanding generalization performance on MFR, we applied insights and tricks we gathered from our experiences in previous competitions during its training.

@DanJun6737 Can you share some tips? and when will you update source code training with partial fc ?