App can't render SVGs after the latest VueCLI upgrade

Version
5.0.4
Reproduction link
github.com
Environment info
➜  broken-svgs git:(main) vue info

Environment Info:

  System:
    OS: macOS 12.2.1
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
  Binaries:
    Node: 17.8.0 - ~/.nvm/versions/node/v17.8.0/bin/node
    Yarn: 1.22.18 - /usr/local/bin/yarn
    npm: 8.5.5 - ~/.nvm/versions/node/v17.8.0/bin/npm
  Browsers:
    Chrome: 99.0.4844.84
    Edge: Not Found
    Firefox: 95.0
    Safari: 15.3
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.2
    @vue/babel-plugin-jsx:  1.1.1
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  5.0.4
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  5.0.4
    @vue/cli-plugin-babel: ~5.0.0 => 5.0.4
    @vue/cli-plugin-eslint: ~5.0.0 => 5.0.4
    @vue/cli-plugin-router:  5.0.4
    @vue/cli-plugin-vuex:  5.0.4
    @vue/cli-service: ~5.0.0 => 5.0.4
    @vue/cli-shared-utils:  5.0.4
    @vue/component-compiler-utils:  3.3.0
    @vue/web-component-wrapper:  1.3.0
    eslint-plugin-vue: ^8.0.3 => 8.5.0
    svg-to-vue:  0.7.0
    vue: ^2.6.14 => 2.6.14
    vue-eslint-parser:  8.3.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  17.0.0 (15.9.8)
    vue-style-loader:  4.1.3
    vue-svg-loader: ^0.16.0 => 0.16.0
    vue-template-compiler: ^2.6.14 => 2.6.14
    vue-template-es2015-compiler:  1.9.1
  npmGlobalPackages:
    @vue/cli: 5.0.4

Steps to reproduce

Create a Vue 2 project
Install vue-svg-loader, vue-template-compiler, file-loader
Update webpack config like https://github.com/orbitalwitness/broken-svgs/blob/main/vue.config.js
Start the app (npm-run-serve)
Import icon as a component (inline) import IconWord from './assets/icon-word.svg?inline'
Try to render it as an image src (external) <img src="./assets/icon-word.svg" />

What is expected?
Icons should be rendered.
What is actually happening?
None of the icons is rendered.

I suspect this is connected to Asset Modules in Webpack (https://webpack.js.org/guides/asset-modules/).
Currently, we have both inline and external SVGs in our project but it doesn't seem to work after the Vue CLI upgrade.

Try this solution.

@Irevall @dagadbm I still haven't managed to make it work.
My current config is this:
@vue/cli v5.0.4
npm v8.5.5
node v17.8.0
vue.config.js:
chainWebpack: (config) => {
        const svgRule = config.module.rule('svg');
        console.log(svgRule)
        console.log('\n\n\n\n\n')
        svgRule.uses.clear();
        svgRule.delete('type');
        svgRule.delete('generator');
        svgRule
            .use('vue-loader')
            .loader('vue-loader')
            .end()
            .use('vue-svg-loader')
            .loader('vue-svg-loader');
    },

Have you managed to solve something?
When I try to import an SVG and use it as a component, it doesn't work.

I've got the exact same problem, stuck on beta6 because of it 😅 I'm using html-loader since I never managed to get vue-svg-loader working in the past.

const { defineConfig } = require('@vue/cli-service');
module.exports` = defineConfig({
	transpileDependencies: true,
	chainWebpack: (config) => {
		// SVG loader
		const svgRule = config.module.rule('svg');
		svgRule.uses.clear();

		// https://github.com/vuejs/vue-cli/issues/6785
		svgRule.delete('type');
		svgRule.delete('generator');

		svgRule
			// load svgs as data-urls on scss using url('/path/to/svg?dataurl')
			.oneOf('dataurl')
			.resourceQuery(/dataurl/)
			.use('svg-url-loader')
			.loader('svg-url-loader')
			.end()
			.end()
			// load svgs as vue components when importing svg files
			.oneOf('vue-component')
			.test(/.*\.svg/)
			.use('vue-svg-loader')
			.loader('vue-svg-loader')
			.end()
			.end();
	},
});

I have something similar to this. I deleted an extra set of rules I had because of an external library at work.
Let me know if it worked

I converted it over to using vue-svg-loader on Vue CLI 5.0.0-beta.6, and everything works there (with just a "normal" setup from the README). Then when I upgrade Vue CLI any further and replace the SVG loading code in vue.config.js with what you suggested, it seems to error as though my SVGs are invalid 🤔
Compiled with problems:

ERROR in ./src/assets/icons/chevron-down.svg 1:0

Module parse failed: Unexpected token (1:0)
File was processed with these loaders:
 * ./node_modules/vue-svg-loader/index.js
You may need an additional loader to handle the result of these loaders.
> <template><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 448 512"><path d="M207.029 381.476L12.686 187.132c-9.373-9.373-9.373-24.569 0-33.941l22.667-22.667c9.357-9.357 24.522-9.375 33.901-.04L224 284.505l154.745-154.021c9.379-9.335 24.544-9.317 33.901.04l22.667 22.667c9.373 9.373 9.373 24.569 0 33.941L240.971 381.476c-9.373 9.372-24.569 9.372-33.942 0z"/></svg></template>

ERROR in ./src/assets/icons/heart-broken.svg 1:0

Module parse failed: Unexpected token (1:0)
File was processed with these loaders:
 * ./node_modules/vue-svg-loader/index.js
You may need an additional loader to handle the result of these loaders.
> <template><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M473.7 73.8l-2.4-2.5c-46-47-118-51.7-169.6-14.8L336 159.9l-96 64 48 128-144-144 96-64-28.6-86.5C159.7 19.6 87 24 40.7 71.4l-2.4 2.4C-10.4 123.6-12.5 202.9 31 256l212.1 218.6c7.1 7.3 18.6 7.3 25.7 0L481 255.9c43.5-53 41.4-132.3-7.3-182.1z"/></svg></template>

This is my full vue.config.js with the changes to try and get it working with newer versions of Vue CLI:
module.exports = {
  lintOnSave: false,
  chainWebpack: (config) => {
    const svgRule = config.module.rule('svg');
    svgRule.uses.clear();

    // https://github.com/vuejs/vue-cli/issues/6785
    svgRule.delete('type');
    svgRule.delete('generator');

    svgRule
      // load svgs as data-urls on scss using url('/path/to/svg?dataurl')
      .oneOf('dataurl')
      .resourceQuery(/dataurl/)
      .use('svg-url-loader')
      .loader('svg-url-loader')
      .end()
      .end()
      // load svgs as vue components when importing svg files
      .oneOf('vue-component')
      .test(/.*\.svg/)
      .use('vue-svg-loader')
      .loader('vue-svg-loader')
      .end()
      .end();
  },
  // For properly setting the base path in 'production' with GitLab Pages.
  publicPath: process.env.NODE_ENV === 'production' ? '/' + process.env.CI_PROJECT_NAME + '/' : '/'
}

Oh, if I change it to just this, it works fine:
    const svgRule = config.module.rule('svg');
    svgRule.uses.clear();

    // https://github.com/vuejs/vue-cli/issues/6785
    svgRule.delete('type');
    svgRule.delete('generator');

    svgRule
      .use('vue-loader')
      .loader('vue-loader')
      .end()
      .use('vue-svg-loader')
      .loader('vue-svg-loader');

That was simple enough...

Now my only problem is that the Jest tests print warnings about all of the SVG components not being registered:
  ● Console

    console.warn
      [Vue warn]: Failed to resolve component: chevron-down-icon
      If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.
        at <GameCard game= {
        id: 1,
        name: "Kirby's Epic Yarn",
        platforms: { nodes: [ [Object] ] },
        developers: { nodes: [ [Object] ] },
        isFavorited: true
      } ref="VTU_COMPONENT" >
        at <VTUROOT>

      at warn (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:40:17)
      at resolveAsset (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5973:13)
      at resolveComponent (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5922:12)
      at Proxy.render (src/components/GameCard.vue:143:40)
      at renderComponentRoot (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:889:44)
      at ReactiveEffect.componentUpdateFn [as fn] (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:4990:57)
      at ReactiveEffect.run (node_modules/@vue/reactivity/dist/reactivity.cjs.js:189:25)
      at setupRenderEffect (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5116:9)

I guess I can just call them custom components? But technically they're not. Unfortunately the Jest configuration that vue-svg-loader suggests doesn't work with the most recent versions of Vue/Vue CLI/Jest :/

This is the easiest one to fix:
https://github.com/visualfanatic/vue-svg-loader/issues/38&ved=2ahUKEwjPkcyZ9d_3AhWrR_EDHQtJB2oQFnoECA4QAQ&usg=AOvVaw2HdfuxTMdNzGTb5UtJKdX0
https://vue-svg-loader.js.org/faq.html#how-to-use-this-loader-with-typescript
On Sat, May 14, 2022, 20:43 Connor Shea @.***> wrote:

Now my only problem is that the Jest tests print warnings about all of the
SVG components not being registered:
● Console
console.warn

  [Vue warn]: Failed to resolve component: chevron-down-icon

  If this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement.

    at <GameCard game= {

    id: 1,

    name: "Kirby's Epic Yarn",

    platforms: { nodes: [ [Object] ] },

    developers: { nodes: [ [Object] ] },

    isFavorited: true

  } ref="VTU_COMPONENT" >

    at <VTUROOT>

  at warn ***@***.***/runtime-core/dist/runtime-core.cjs.js:40:17)

  at resolveAsset ***@***.***/runtime-core/dist/runtime-core.cjs.js:5973:13)

  at resolveComponent ***@***.***/runtime-core/dist/runtime-core.cjs.js:5922:12)

  at Proxy.render (src/components/GameCard.vue:143:40)

  at renderComponentRoot ***@***.***/runtime-core/dist/runtime-core.cjs.js:889:44)

  at ReactiveEffect.componentUpdateFn [as fn] ***@***.***/runtime-core/dist/runtime-core.cjs.js:4990:57)

  at ReactiveEffect.run ***@***.***/reactivity/dist/reactivity.cjs.js:189:25)

  at setupRenderEffect ***@***.***/runtime-core/dist/runtime-core.cjs.js:5116:9)

I guess I can just call them custom components? But technically they're
not. Unfortunately the Jest configuration that vue-svg-loader suggests
doesn't work with the most recent versions of Vue/Vue CLI/Jest :/
—
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-cli/issues/7084#issuecomment-1126801067,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD7WGR5KOBO4ZL5ZPNGX7MLVJ764ZANCNFSM5SBWLKSA
.
You are receiving this because you were mentioned.Message ID:
@.***>

For anyone facing the same issue as @connorshea with jest warnings, I figured out a fix that works here: https://github.com/visualfanatic/vue-svg-loader/issues/38#issuecomment-1135337194

Version
node: 'v20.11.0', npm: '10.2.4'
Environment info
"sass-loader": "^10.5.2",
"svg-url-loader": "^7.1.1",
"svgxuse": "^1.2.6",
"to-css": "^1.2.1",
"v-calendar": "^1.0.1",
"vue": "^2.5.17",
"vue-cookie": "^1.1.4",
"vue-router": "^3.2.0",
"vue-split-layout": "0.0.16",
"vue-svg-inline-loader": "^2.1.5",
"vue-svg-loader": "^0.16.0",
"vue-touch": "^2.0.0-beta.4",
"vuedraggable": "^2.24.3",
"vuex": "^3.0.1",
"vuex-i18n": "^1.13.1",
"vuex-router-sync": "^5.0.0",
"devDependencies": {
"@babel/core": "^7.8.7",
"@vue/cli-plugin-babel": "~4.2.3",
"@vue/cli-plugin-e2e-nightwatch": "~4.2.3",
"@vue/cli-plugin-eslint": "^4.2.3",
"@vue/cli-plugin-unit-jest": "~4.2.3",
"@vue/cli-service": "~4.2.3",
"@vue/test-utils": "^1.3.0",
"axios-mock-adapter": "^1.17.0",
"babel-eslint": "^10.1.0",
"babel-loader": "^8.3.0",
"babel-preset-vue": "^2.0.2",
"cache-loader": "^4.1.0",
"chromedriver": "^88.0.0",
"css-loader": "^3.4.2",
"dotenv": "^8.2.0",
"eslint": "^6.8.0",
"eslint-plugin-vue": "^6.2.1",
"faker": "^4.1.0",
"flush-promises": "^1.0.2",
"geckodriver": "^1.19.1",
"globby": "^11.0.1",
"gulp": "^4.0.2",
"gulp-hub": "^4.2.0",
"gulp-zip": "^5.0.1",
"jest-environment-jsdom-sixteen": "^1.0.3",
"jest-junit": "^8.0.0",
"jest-teamcity-reporter": "^0.9.0",
"jest-transform-stub": "^1.0.0",
"jest-when": "^2.7.0",
"nodemon": "^2.0.6",
"normalize-path": "^3.0.0",
"sonar-scanner": "^3.1.0",
"storybook-vue-router": "^1.0.7",
"vue-svg-sprite-loader": "^1.2.1",
"vue-template-compiler": "^2.5.17",
"vue-test-utils": "^1.0.0-beta.11",
"yargs": "^15.3.1"
}
vue.config.js
chainWebpack: (config) => {
const svgRule = config.module.rule('svg');
svgRule.uses.clear();
// https://github.com/vuejs/vue-cli/issues/6785
svgRule.delete('type');
svgRule.delete('generator');
svgRule
// load svgs as data-urls on scss using url('/path/to/svg?dataurl')
.oneOf('dataurl')
.resourceQuery(/dataurl/)
.use('vue-loader')
.loader('vue-loader')
.end()
.use('svg-url-loader')
.loader('svg-url-loader')
.end()
.end()
// load svgs as vue components when importing svg files
.oneOf('vue-component')
.test(/..svg/)
.use('vue-svg-loader')
.loader('vue-svg-loader')
.end()
.end();
},
Jest.config.js
transform: {
'^.+.vue$': 'vue-jest',
'.+.(css|styl|less|sass|scss|svg|png|jpg|ttf|woff|woff2)?(?:.)/$': 'jest-transform-stub',
'^.+.jsx?$': 'babel-jest',
'.+.svg?.+$': 'jest-transform-stub'
},
moduleNameMapper: {
'.+.svg?.+$': '/src/assets/icons/ui.svg',
'^@/(.)$': '/src/$1',
'^~/(.)$': '/test/unit/$1'
},
Error -
npm run serve
<EMAIL_ADDRESS>serve
**vue-cli-service serve
INFO Starting development server...
98% after emitting CopyPlugin
ERROR Failed to compile with 1 error 8:57:01 pm
error in ./src/assets/icons/icons.svg?arrow-left
Syntax Error: TypeError: iconInfo.hasOwnProperty is not a function
@ ./node_modules/cache-loader/dist/cjs.js??ref--12-0!./node_modules/babel-loader/lib!./node_modules/cache-loader/dist/cjs.js??ref--0-0!./node_modules/vue-loader/lib??vue-loader-options!./src/views/Work.vue?vue&type=script&lang=js 44:0-67 443:20-29
@ ./src/views/Work.vue?vue&type=script&lang=js
@ ./src/views/Work.vue
@ ./src/router/index.js
@ ./src/main.js
@ multi (webpack)-dev-server/client?sockjs-node (webpack)/hot/dev-server.js ./src/main.js**
Any help to resolve to this issue?

#7448
any help?

vue-svg-loader is just 20 lines of unmaintained code that doesn't do a whole lot, I think the best idea is to create your own SVG loader instead.

@kubajmarek added vue-svg-loader-2.. did not work...

@ganeshkumarpolipalli-accolite can you upload a reproduction anywhere? Something might be wrong with the icon or Work.vue.


[bug]: Installing openCL on old GPU that should support it

Suggestion Description
Hello, I have an AMD Radeon HD 7870 and it should support opencl
I'm on POPOS 22.04 and I managed to install these:
amdgpu-install_5.4.50401-1_all.deb  amdgpu-install_5.7.50702-1_all.deb    amdgpu-install_5.5.50503-1_all.deb
Install with 5.7 == impossible to work, it doesn't find some packages (spent 1h on google and no one has any solution)
For both below, I had to install in top of that mesa-opencl-icd
Install with 5.4 == i didn't notice errors but it doesn't work in the end
Install with 5.5 == several errors, and it doesn't work either
"clinfo" gives me 2 platforms but always 0 devices
I cannot find any solution, everybody just say to retry reinstalling with different options, it makes no sense
I installed with --use-case=opencl (or without this) and --opencl=legacy
Operating System
pop os 22.04
GPU
Radeon HD 7870
ROCm Component
No response

Hello, I have recently failed to install ROCm on my windaos10 system. Can you tell me how to install it?
Thank you very much.

@xiaobo1025 Please create your own issue for your own problem: here. 🙂

Hi, @BarbzYHOOL the AMD Radeon HD 7870 is a GCN1 device. The ROCm driver never supported this card and AMD has no plan to support it ever.
The AMD driver for this card is fglrx, more precisely “AMD Radeon Software Crimson Edition 15.12 Proprietary Linux” from the year 2015 and you need Ubuntu 14.04.2 or Ubuntu 12.04.4 (yeas, distributions from year 2014 or 2012). In other hand, AMD has no solution for you.
The legacy Orca driver which is newer than fglrx may list your device but I never seen it working with any GCN1 device I tried.
Your only options are the Mesa OpenCL drivers, the more complete one for AMD is rusticl.
Your only true hope with a GCN1 card like the AMD Radeon HD 7870 is to use rusticl. A tutorial is coming in the following comment. I made the following tutorial generic (not just for you), but I verified that your card is supported by this other driver.

Installing latest Mesa rusticl OpenCL driver for GCN/RDNA/CDNA AMD graphics card on Ubuntu Linux and derivatives
Here is a generic tutorial to install the latest Mesa rusticl driver for all GCN and RDNA cards on Ubuntu-derivated distros like Pop OS or Linux Mint (Ubuntu based).
To know if your graphics card is supported by the rusticl driver, search for your graphics card name on techpowerup website. If the page for your graphics card says the architecture of the graphics card is either GCN, RDNA or CDNA, this tutorial is for you. The TeraScale architectures are not supported yet by rusticl.
First you need to install the Mesa OpenCL drivers, I recommend you to also install the clinfo tool for the next instructions (to check if everything works).
Install the Oibaf PPA repository, this will provide you updated Mesa drivers and then rusticl:
sudo add-apt-repository 'ppa:oibaf/graphics-drivers'
sudo apt-get update
sudo apt-get dist-upgrade

Then you install the Mesa OpenCL drivers, the second command will disable the clover OpenCL driver which is now less good than rusticl, and keep rusticl enabled:
sudo apt-get install 'mesa-opencl-icd' 'clinfo'
sudo dpkg-divert --divert '/etc/OpenCL/vendors/mesa.icd.disabled' --rename '/etc/OpenCL/vendors/mesa.icd'

Then before you run your application, set some environment variable, let's try with clinfo first:
export RUSTICL_ENABLE='radeonsi'
clinfo --list

The environment variable makes sure you enable rusticl for AMD Radeon cards. The rusticl driver is still experimental and then not installed by default.
If that works for you, to make this variables permanent, edit a profile file:
sudo nano '/etc/profile.d/rusticl.sh'

Then paste this content:
export RUSTICL_ENABLE='radeonsi'

And save the file. Close your session and reopen.
Now, simply doing this should work:
clinfo --list

This should print you something like this (with other card name):
Platform #0: rusticl
 `-- Device #0: AMD Radeon PRO W7600 (gfx1102, LLVM 15.0.7, DRM 3.56, 6.5.0-14-generic)

To completely revert to your previous state and uninstall everything we did, you would do:
sudo rm '/etc/profile.d/rusticl.sh'
sudo dpkg-divert --rename --remove '/etc/OpenCL/vendors/mesa.icd'
sudo apt-get autoremove --purge 'mesa-opencl-icd' 'clinfo'
sudo ppa-purge 'ppa:oibaf/graphics-drivers'

And you would have to close and re-open your session.
I'm not an AMD employee, but this may save you a lot of time. I'm not paid to give you this help but I was passing by while dealing with some other ROCm issues and thought I could help you. I maintain some information about what driver supports what GPU here: https://gitlab.com/illwieckz/i-love-compute/ If I saved your life you may find ways to thank me. 😉

Hi, @BarbzYHOOL the AMD Radeon HD 7870 is a GCN1 device. The ROCm driver never supported this card and AMD has no plan to support it ever.
The AMD driver for this card is fglrx, more precisely “AMD Radeon Software Crimson Edition 15.12 Proprietary Linux” from the year 2015 and you need Ubuntu 14.04.2 or Ubuntu 12.04.4 (yeas, distributions from year 2014 or 2012). In other hand, AMD has no solution for you.
The legacy Orca legacy driver which is newer than fglrx may list your device but I never seen it working with any GCN1 device I tried. The less-legacy Orca legacy driver (the one you get with the --opencl=legacy option) will even not list your GPU.
Your only options are the Mesa OpenCL drivers, the most complete one for AMD GCN1 devices is rusticl.
Your only true hope with a GCN1 card like the AMD Radeon HD 7870 is to use rusticl. A tutorial is coming in the following comment. I made the following tutorial generic (not just for you), but I verified that your card is supported by this other driver.

what about trying one of the AMD driver "Linux" and try to compile it for my own distribution? it seems like they have given this option on AMD driver page
And thank you very much for the tutorial, I'm gonna do this in the upcoming days. First I'll remove everything else I added.
Btw why keep the "clover" thing? why not remove it all?

@illwieckz
I had installed all of these before opening the issue, what should I uninstall and keep?
  54    install amdgpu-install_5.4.50401-1_all.deb                                           2023-12-12 02:24:38 CET           3    me (1000)
  55    install opencl-headers ocl-icd-libopencl1 clinfo                                     2023-12-12 03:06:54 CET           4    me (1000)
  56    install mesa-opencl-icd                                                              2023-12-13 00:55:57 CET          13    me (1000)
  57    install discord-0.0.38.deb                                                           2023-12-13 01:14:16 CET           5    me (1000)
  58    install vainfo                                                                       2023-12-16 00:58:30 CET           1    me (1000)
  59    install mesa-va-drivers                                                              2023-12-16 23:05:28 CET           1    me (1000)
  60    history undo 56                                                                      2023-12-17 23:43:04 CET          10    me (1000)
  61    install amdgpu-install_5.7.50702-1_all.deb                                           2023-12-18 00:01:25 CET           2    me (1000)
  62    install amdgpu-install_5.5.50503-1_all.deb                                           2023-12-18 00:26:14 CET           2    me (1000)
  63    install mesa-opencl-icd                                                              2023-12-18 00:48:47 CET          10    me (1000)

As root:
apt-mark auto opencl-headers ocl-icd-libopencl1
amdgpu-uninstall
apt-get autoremove --purge amdgpu-install
rm /etc/modprobe.d/blacklist-radeon.conf /etc/modprobe.d/blacklist-amdgpu.conf
update-initramfs -k all -u

Some commands may be useless (the update-initramfs one), or report some errors (the rm one), depending what you have installed or not, but doing them will not do harm if not needed.
Before rebooting, make sure that this command reports nothing:
grep -ER 'blacklist radeon$|blacklist amdgpu$' /etc/modprobe.d/

If it report some file, delete the said file and re-run update-initramfs -k all -u before rebooting.

the modprobe files were kinda empty but i removed them
also those commands did not remove some of the stuff amdgpu installed like amdgpu-core amdgpu-dkms-firmware amdgpu-pro-core autoconf automake autotools-dev grub-common grub-efi-amd64 grub-efi-amd64-bin   grub-efi-amd64-signed grub2-common libdrm-amdgpu-amdgpu1 libdrm-amdgpu-common libdrm2-amdgpu m4 mokutil ocl-icd-libopencl1-amdgpu-pro os-prober shim-signed
the update-initramfs command returned:
update-initramfs: Generating /boot/initrd.img-6.4.6-76060406-generic
cryptsetup: WARNING: Resume target cryptswap uses a key file
W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vega10_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi12_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/psp_13_0_6_sos.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/aldebaran_cap.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_0_toc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sdma_4_4_2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/gc_11_0_3_mes.bin for module amdgpu

and many more, and I'm on an older kernel so I feel like i'm gonna get screwed when rebooting

For the remaining packages, well, if you're sure all of them were installed by amdgpu-install, then remove them all.
If you're note sure, removing amdgpu-core amdgpu-dkms-firmware amdgpu-pro-core ocl-icd-libopencl1-amdgpu-pro libdrm-amdgpu-amdgpu1 libdrm-amdgpu-common libdrm2-amdgpu is safe (and they should be removed).
You can totally ignore the W: possible missing firmware messages, they are abouts GPUs you don't have. Those messages mean your kernel is more recent than your firmwares, and the missing firmwares are those of newer GPU you don't have.

ok it all worked, for those extra packages, I had noted them down, but since I reinstalled another amdgpu-install once, I suppose I have other useless packages installed, but I may find them back in apt log
Everything works atm, in fact when I installed the previous drivers, it gave me some errors. Now I'm gonna do what you said to install the right drivers and tell you the result, thanks

Ok @illwieckz  it printed one device:
Platform #0: Clover
 `-- Device #0: PITCAIRN (radeonsi, , LLVM 15.0.7, DRM 2.50, 6.2.6-76060206-generic)

Now running a miner using OpenCl, I get this:
OpenCL driver detected.
Number of OpenCL supported GPUs: 0

Another:
[2023-12-31 01:14:25] Found 1 OpenCL platforms, but none is AMD, NVIDIA OR INTEL

I guess I'm doomed

Ok @illwieckz it printed one device:
Platform #0: Clover
 `-- Device #0: PITCAIRN (radeonsi, , LLVM 15.0.7, DRM 2.50, 6.2.6-76060206-generic)

This is progressing!
Your GPU is properly detected, but it is detected by the clover driver, not the rusticl one.
In my tutorial there was some instructions to disable Clover, but don't worry, keep it for now.
Does the /etc/OpenCL/vendors/rusticl.icd file exist?
You can check for its existence this way:
file '/etc/OpenCL/vendors/rusticl.icd'

Now running a miner using OpenCl, I get this:
OpenCL driver detected.
Number of OpenCL supported GPUs: 0

Since Clover is incomplete, tt's possible that the device is ignored because it misses some important required things. Though usually Clover is enough for non-graphics applications…
We still need to make rusticl work in case of rusticl is good with this one.

Another:
[2023-12-31 01:14:25] Found 1 OpenCL platforms, but none is AMD, NVIDIA OR INTEL

For this one, you're probably screwed, as the developper seems to have written a white list of drivers and doesn't care about other drivers. The purpose of OpenCL is to have a single code and to run it on any OpenCL driver. You may check if the software has an option to continue anyway, otherwise it may require patching of the software. The software is explicitly looking for a specific AMD driver or a set of specific AMD drivers (like fglrx, Orca, PAL or ROCm), and doesn't check for OpenCL compatibility, what it should do. This is very bad practice and it's the miner developer's fault. I would report that issue to the miner developer.

I didn't run the command to disable Clover because I thought the command would rename in the other sense, I didn't realize it was to disable Clover lol. I had to adapt some commands to my fish shell etc... that's why I diverged a bit.
I also ran "upgrade" and not "dist-upgrade" because I didn't want to update my kernel, I guess it didn't matter it still did -__-'
Now I ran the disabling command.
/etc/OpenCL/vendors/rusticl.icd: cannot open `/etc/OpenCL/vendors/rusticl.icd' (No such file or directory)

No file, so "clinfo --list" gives nothing now

I didn't run the command to disable Clover because I thought the command would rename in the other sense, I didn't realize it was to disable Clover lol. I had to adapt some commands to my fish shell etc... that's why I diverged a bit.
I also ran "upgrade" and not "dist-upgrade" because I didn't want to update my kernel, I guess it didn't matter it still did -__-'
Now I ran the disabling command.
/etc/OpenCL/vendors/rusticl.icd: cannot open `/etc/OpenCL/vendors/rusticl.icd' (No such file or directory)

No file, so "clinfo --list" gives nothing now

@illwieckz Since I disabled clover, i cannot read any video, no OpenGl lol

@illwieckz hey sorry to call you again, but I'm waiting for a last reply (just in case there is a solution) before I roll back all the changes of the last entire month, if you have any other idea to solve this or time to reply else just tell me and i'll roll back

Hmm, @BarbzYHOOL for some reasons I only got a notice for the closing, not for the mentions. 🤔
So I'm sorry to answer this late.
Disabling Clover cannot remove OpenGL at all, make sure libglx-mesa0 is installed, and make sure a kernel module is loaded. What is the output of lsmod | grep -E 'radeon|amdgpu'?
Make sure you have removed all files doing blacklist radeon or blacklist amdgpu in /etc/modprobe.d and updated initramfs as indicated here: https://github.com/ROCm/ROCm/issues/2743#issuecomment-1870768714

libglx-mesa0 23.3.0-1pop0~1702935939~22.04~67e417a [Pop!_OS Release/jammy main]
├── is installed and upgradable to 23.3.2-1pop0~1704238321~22.04~36f1d0e
└── free implementation of the OpenGL API -- GLX vendor library
lsmod | grep -E 'radeon|amdgpu'                                                                                2.3s|02:19:51
amdgpu              14774272  0
iommu_v2               24576  1 amdgpu
drm_buddy              20480  1 amdgpu
gpu_sched              57344  1 amdgpu
radeon               2101248  34
video                  69632  2 amdgpu,radeon
i2c_algo_bit           16384  2 amdgpu,radeon
drm_suballoc_helper    16384  2 amdgpu,radeon
drm_ttm_helper         12288  2 amdgpu,radeon
ttm                   106496  3 amdgpu,radeon,drm_ttm_helper
drm_display_helper    217088  2 amdgpu,radeon
drm_kms_helper        258048  3 drm_display_helper,amdgpu,radeon
drm                   708608  22 gpu_sched,drm_kms_helper,drm_suballoc_helper,drm_display_helper,drm_buddy,amdgpu,radeon,drm_ttm_helper,ttm

rm /etc/modprobe.d/blacklist-radeon.conf /etc/modprobe.d/blacklist-amdgpu.conf                                                     0.2s|02:22:51
rm: cannot remove '/etc/modprobe.d/blacklist-radeon.conf': No such file or directory
rm: cannot remove '/etc/modprobe.d/blacklist-amdgpu.conf': No such file or directory

╰─# set RUSTICL_ENABLE 'radeonsi'
╰─# clinfo --list                                                                                02:22:27
---------------------

Nothing

@illwieckz
libglx-mesa0 23.3.0-1pop0~1702935939~22.04~67e417a [Pop!_OS Release/jammy main]
├── is installed and upgradable to 23.3.2-1pop0~1704238321~22.04~36f1d0e
└── free implementation of the OpenGL API -- GLX vendor library

lsmod | grep -E 'radeon|amdgpu'                                                                                2.3s|02:19:51
amdgpu              14774272  0
iommu_v2               24576  1 amdgpu
drm_buddy              20480  1 amdgpu
gpu_sched              57344  1 amdgpu
radeon               2101248  34
video                  69632  2 amdgpu,radeon
i2c_algo_bit           16384  2 amdgpu,radeon
drm_suballoc_helper    16384  2 amdgpu,radeon
drm_ttm_helper         12288  2 amdgpu,radeon
ttm                   106496  3 amdgpu,radeon,drm_ttm_helper
drm_display_helper    217088  2 amdgpu,radeon
drm_kms_helper        258048  3 drm_display_helper,amdgpu,radeon
drm                   708608  22 gpu_sched,drm_kms_helper,drm_suballoc_helper,drm_display_helper,drm_buddy,amdgpu,radeon,drm_ttm_helper,ttm

rm /etc/modprobe.d/blacklist-radeon.conf /etc/modprobe.d/blacklist-amdgpu.conf                                                     0.2s|02:22:51
rm: cannot remove '/etc/modprobe.d/blacklist-radeon.conf': No such file or directory
rm: cannot remove '/etc/modprobe.d/blacklist-amdgpu.conf': No such file or directory

╰─# set RUSTICL_ENABLE 'radeonsi'
╰─# clinfo --list                                                                                02:22:27
---------------------

Nothing

I waited too long and now my automatic backups have been deleted so I cannot rollback and I still can try to make this work if you know what to do @illwieckz

I uninstalled everything and I still have log errors everyday after boot

@illwieckz

Installing latest Mesa rusticl OpenCL driver for GCN/RDNA/CDNA AMD graphics card on Ubuntu Linux and derivatives

sudo apt-get install 'mesa-opencl-icd' 'clinfo'
sudo dpkg-divert --divert '/etc/OpenCL/vendors/mesa.icd.disabled' --rename '/etc/OpenCL/vendors/mesa.icd'

export RUSTICL_ENABLE='radeonsi'
clinfo --list

the ubuntu rusticl tutorial posted above worked for me. I have an AMD Radeon RX 580 GPU and Ubuntu 24.04.1 (noble). Rusticl was included in noble's 'mesa-opencl-icd' package, and all I needed to do was install it and set the environment variable RUSTICL_ENABLE='radeonsi'.
I realize this post may come too late to solve the original issue but I wanted to record how I got OpenCL working on AMD GPU for future readers

Thanks @jon-gao-yang for the feedback! 👍
Indeed with Noble no PPA should be needed (though a PPA may provide a more up-to-date features), I may update the tutorial in regard to that. 🙂

Hi @BarbzYHOOL, sorry for the delay. Are you still experiencing those log errors?

Converting this to a discussion, as some great advice has been given here on getting old hardware to work. As stated earlier in this thread, we don't officially support this hardware (or Pop OS for that matter), but future users with similar configurations may find this guidance useful.


Type definitions for option.xmlDocument

There is no Typescript's type definition for xmlDocument, which is a valid option when we use JsBarcode with nodejs and the svg output.
Also, it's not listed on the Options wiki:
https://github.com/lindell/JsBarcode/wiki/Options
Tested with  jsbarcode 3.11.0

I am having the same issue. Is there a fix coming soon? or any work around?


Are posts supported?

The examples at the minute are all Http GETS.
Does Diffy currently support posts?
I've tried sending a few in but it doesn't seem to be acknowledged by Diffy as I can't see the post being forwarded on to the service nor any results entered?
I've tried adding the Canonical-Resource header as well but with no luck so far
curl  --header "Canonical-Resource: Html"  -H "Content-Type: application/json" -X POST -d '{"foo":"bar"}' http://localhost:8880
Is my request at the minute or a scaled down version.

POST, PUT, DELETE are ignored by default for safety. You can enable them by explicitly adding the following flag to your diffy deploy command:
-allowHttpSideEffects=true

Thanks!
That got it


Cannot display the correct localization

Hi, I have a problem using this localization framework.
Here is the step I have done

install localize using cocoapods
import Localize in AppDelegate.swift and put below code inside "application" function
let localize = Localize.shared
localize.update(provider: .json)
localize.update(fileName: "lang")
localize.update(defaultLanguage: "en")
print(localize.language())
print(localize.availableLanguages())
then, I created "lang-en.json" and put it inside my working folder
I add print("hello.world".localize()) somewhere in the viewController
I tried to run the program
the result which is shown in the console is
en
[]
hello.world

Am I missing something? or they cannot find my "lang-en.json" file?
Thank you

@christchan sorry I'm back to the project, do you have yet this issue?


Add Router check into network plugin for labchecker

Add new Router check into network plugin for labchecker.

LGTM


Time Penalty

Time Penalty
User Story
AS A coding boot camp student
I WANT to take a timed quiz on JavaScript fundamentals that stores high scores
SO THAT I can gauge my progress compared to my peer
Acceptance Criteria
GIVEN I am taking a code quiz
WHEN I answer a question incorrectly
THEN time is subtracted from the clock

Completed, commented in JS Code


Topic H1 sometimes cuts off on mobile

Linked to #120
Linked to #193

Is this still an issue? Needs to be reviewed please 🙏🏼 @anikbrazeau @ClementineHahn

@daine @ClementineHahn  The cutting off seems to be solved. However the size of headings based on levels of hierarchy is not right. The H1 is smaller than H2/3/etc.

Should we reframe this issue or create a new one?

I will close this and create a new GitHub issue one with the new challenge: #290


Latest camera firmware

Appgotapo is not able to log in to the camera since the camera firmware was updated to the latest firmware in Dec 2023. Are you able to supply a fix for this?

problem on 1.3.11 ?

Yes.
On Thu, 14 Dec 2023 at 05:57, YuYu @.***> wrote:

problem on 1.3.11 ?
—
Reply to this email directly, view it on GitHub
https://github.com/KusoKaihatsuSha/appgotapo/issues/3#issuecomment-1855190512,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7HKILM4TUTYLK55UTVMK33YJKIM5AVCNFSM6AAAAABAS4ZNJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVGE4TANJRGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

On new firmware old insecure type of auth is disabled. On appgotapo v1.0.5 added digit auth.

Now works. Thank you so much.


chore: bump SHA in Combinatorics/Composition

<EMAIL_ADDRESS>
Nothing to do but bump the SHA.

Thanks!
bors r+


fingerprint

Is your feature request related to a problem? Please describe.

Describe the solution you'd like:

Describe alternatives you've considered:

Additional context:

Am not able to run my code in Vs code

Closing as incomplete. Please feel free to add more information if you have any and we can re-open the issue.


Don't commit storage tries

One slowdown came up when introducing verkle storage tries: the Commit function was being called over and over again on the same trie. There was a workaround introduced in go-verkle, but ultimately Commit should simply not work on storage tries.

hey can i take up this issue please?


Transparent_Form_using_CSS.md

Description 📜Transparent_Form_using_CSS.md
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #8505

Type of change 📝Transparent_Form_using_CSS.md

[X] Doc#umentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[X] Frontend Dev #HTML/CSS/JS

Checklist ✅

[X] I follow Contributing Guidelines & Code of conduct of this project.
[X] I have performed a self-review of my own code or work.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] My changes generates no new warnings.
[X] I'm GWOC'21 contributor

@2024-SANDHYA
I have rectified all grammatical errors . Can u please review and merge.


auto.sh not found

when i try to use any of the options it tells me the sh file of that option doesnt exist help me please!

$ cd core
$ bash update

$ cd core
$ bash update

when i try to use any of the options it tells me the sh file of that option doesn't exist help me please!

It have a simple solutions you need to excute the file manually in the main folder
there are two files

auto.sh
2)manual.sh

open that folder in terminal
run "bash auto.sh"

it may help you.


Sleep longer if request speed is over github limitation

Since github has a 5000 API request times per hour per token limitation, we have to add a limit for migrating from those bigger repository.

Codecov Report

Merging #9335 into master will increase coverage by 0.01%.
The diff coverage is 51.66%.

@@            Coverage Diff             @@
##           master    #9335      +/-   ##
==========================================
+ Coverage   41.26%   41.28%   +0.01%
==========================================
  Files         561      561
  Lines       73433    73500      +67
==========================================
+ Hits        30301    30343      +42
- Misses      39339    39359      +20
- Partials     3793     3798       +5

Impacted Files
Coverage Δ

modules/migrations/migrate.go
24.21% <100%> (-0.79%)
:arrow_down:

modules/migrations/git.go
61.29% <100%> (+5.73%)
:arrow_up:

modules/migrations/base/downloader.go
29.65% <40.47%> (+4.41%)
:arrow_up:

modules/migrations/github.go
79.19% <66.66%> (-0.34%)
:arrow_down:

modules/migrations/gitea.go
8.84% <0%> (-0.64%)
:arrow_down:

modules/indexer/issues/indexer.go
63.79% <0%> (-0.12%)
:arrow_down:

models/repo.go
47.92% <0%> (-0.05%)
:arrow_down:

modules/notification/indexer/indexer.go
50.72% <0%> (+0.72%)
:arrow_up:

models/repo_list.go
74.07% <0%> (+0.92%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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

@guillep2k done.

So because the sleeps are actually of arbitrary length I think these probably need to use the NewTimer(...).C formulation with timer.Stopin the ctx.Done() section. Otherwise if you cancel the ctx you leak the timer.
(This is mainly because I think we should be able to cancel these downloads at least from the process manager - if not by the user themselves)

I'll test it later :)

@zeripath done. The previous version will not leak the timer. It will be released when the time is expired(Or when program is exit).
But of course, your idea is better that will spend less memory when running.

@adelowo done.

make L-G-T-M work


fixes code coverage

Codecov Report

Merging #8 (a2ea91a) into master (d46d172) will increase coverage by 24.62%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master       #8       +/-   ##
===========================================
+ Coverage        0   24.62%   +24.62%
===========================================
  Files           0        7        +7
  Lines           0      402      +402
===========================================
+ Hits            0       99       +99
- Misses          0      293      +293
- Partials        0       10       +10

Impacted Files
Coverage Δ

database/config.go
63.15% <0.00%> (ø)

core/slice.go
100.00% <0.00%> (ø)

database/mysql.go
0.00% <0.00%> (ø)

database/escape.go
100.00% <0.00%> (ø)

generator/faker.go
53.42% <0.00%> (ø)

database/option.go
75.00% <0.00%> (ø)

core/config.go
25.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Use git tags for versioning

Instead of hard-coding the version, just get it from the last git tag. Streamlines automated deployment a bit.
see setuptools-scm.

closed with #63


Problems in make_models.py

Version
"react-native-pytorch-core": "0.1.2",

Problem Area
react-native-pytorch-core (core package)
Steps to Reproduce
npx torchlive-cli init MyFirstProject
Expected Results
Create a project without an error
Code example, screenshot, or link to repository
I get this error when I create new project.

› Error project "SmartCalc" is created but we ran into the following issues at generatin…

Downloading: "https://download.pytorch.org/models/resnet18-f37072fd.pth" to /Users/nec…
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.p…
h.request(req.get_method(), req.selector, req.data, headers,
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py",…
self._send_request(method, url, body, headers, encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py",…
self.endheaders(body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py",…
self._send_output(message_body, encode_chunked=encode_chunked)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py",…
self.send(msg)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py",…
self.connect()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/http/client.py",…
self.sock = self._context.wrap_socket(self.sock,
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/ssl.py", line 50…
return self.sslsocket_class._create(
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/ssl.py", line 10…
self.do_handshake()
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/ssl.py", line 13…
self._sslobj.do_handshake()
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify fail…
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/Users/necmettinsargin/Documents/GitHub/SmartCalc/models/make_models.py", line 1…
main()
File "/Users/necmettinsargin/Documents/GitHub/SmartCalc/models/make_models.py", line 1…
export_image_classification_models()
File "/Users/necmettinsargin/Documents/GitHub/SmartCalc/models/make_models.py", line 3…
"resnet18": torchvision.models.resnet18(pretrained=True),
File "/Users/necmettinsargin/Documents/GitHub/SmartCalc/models/venv/lib/python3.9/site…
return _resnet('resnet18', BasicBlock, [2, 2, 2, 2], pretrained, progress,
File "/Users/necmettinsargin/Documents/GitHub/SmartCalc/models/venv/lib/python3.9/site…
state_dict = load_state_dict_from_url(model_urls[arch],
File "/Users/necmettinsargin/Documents/GitHub/SmartCalc/models/venv/lib/python3.9/site…
download_url_to_file(url, cached_file, hash_prefix, progress=progress)
File "/Users/necmettinsargin/Documents/GitHub/SmartCalc/models/venv/lib/python3.9/site…
u = urlopen(req)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.p…
return opener.open(url, data, timeout)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.p…
response = self._open(req, data)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.p…
result = self._call_chain(self.handle_open, protocol, protocol +
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.p…
result = func(*args)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.p…
return self.do_open(http.client.HTTPSConnection, req,
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/urllib/request.p…
raise URLError(err)
urllib.error.URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate ver…

please rerun
    • "python make_models.py" in the SmartCalc/models/ directory, and
    • "pod install" in the SmartCalc/ios/ directory
if the issue persists, please report at https://github.com/pytorch/live/issues.

And When I run python make_models.py it says

File "make_models.py", line 17
print(f"torch version {torch.version}")
^
SyntaxError: invalid syntax

Hi @Sargnec ,
The error is due because you didn't install the certificates for Python after installing it locally (its post-installation). You can read more about it in the next link: urllib and "SSL: CERTIFICATE_VERIFY_FAILED" Error.
I recommend you to install Python 3.9.5.
See that, after installing Python, the installer asks you to Install the necessary certificates:

⚠ Make sure the command python3 references to this installation of Python 3.9.5. That's because, for the moment, the python3 command is used to make the models. As a temporal solution, you can add the line alias python3=<python folder> substituting <python folder> by the path of your local installation of Python like /usr/local/bin/python3. You can see this by opening the Python Launcher and copying the path after Interpreter.
As soon as I have time to work on it, I'll create a Python Installer on #9 to avoid having this kind of issue.
Thanks for reporting it! 😊

I did try both 3.9.5 and 3.9.4 and when I click on Install certificate it gives this

python3.9: posix_spawn: /Library/Frameworks/Python.framework/Versions/3.9/Resources/Python.app/Contents/MacOS/Python: Undefined error: 0

Btw I'm on macos m1

What's the output of the terminal when you write which python ?
At first it seems that your Python installation is broken (the default Python 2.7 installation that comes with your Mac).
You can try install Python using Homebrew: brew install python.
Then, make sure /usr/local/bin is added to PATH. You can add it manually with the command export PATH=$PATH:/usr/local/bin.
After that, try installing the certificates.
And don't worry, it is not an Apple Silicon problem. I'm also using an M1 MacBook.
Hope it works this time @Sargnec ! 😁

Do I remove existing python and link<EMAIL_ADDRESS>@aaronespasa
And thank you for your help

@Sargnec  Do not remove the existing python. Link<EMAIL_ADDRESS>with the command brew link --overwrite --dry-run<EMAIL_ADDRESS>to avoid having the symlink error (--dry-run will let you know which files will be removed). You can find more about this issue in StackOverflow: How to symlink python in Homebrew?.
Then, try to install the certificates.
After doing that, keep in mind that Python 3.9.9 will generate some conflict at the time of making the models because it can't find the last version of torchvision. So you will have to downgrade Python to the version 3.9.5 and be sure that the command python3 -V outputs the version 3.9.5 of Python. You can follow the steps that I indicated on the first comment to create this alias temporally.

Hi @Sargnec
Thanks for using Pytorch Live!  As @aaronespasa mentioned, this seems to be python version issue and his suggestion seems mostly right! And after you configure the python version correctly on you machine, here are the steps you may want to rerun within your project to re-create the ptl files:
https://github.com/pytorch/live/blob/main/react-native-template-pytorch-live/script.js#L20-L24
Please let us know how does that work for you! Thanks!

Thank you @aaronespasa @liuyinglao. At first try nothing changed it was giving me same errors

python3.9: posix_spawn: /Library/Frameworks/Python.framework/Versions/3.9/Resources/Python.app/Contents/MacOS/Python: Undefined error: 0

but today I tried again and I was able to install certificates and right now ImageClassificationTutorial app is working for me.


Support using Cryptographic providers

Hi y'all
Describe the problem you'd like to have solved
In my project, I'm required to use an HSM (Hardware Security Module) for computing digital signatures. This particular HSM provides a Java API which includes a java.security.Provider class. This class is tasked with making the HSM specific calls for computing signatures with a given java.security.PrivateKey reference.
The same could be said if we want to use BouncyCastleProvider, another common crypto provider in the Java and .NET crypto communities.
Specifying the signature provider is standard Java, as can be observed in the Signature.getInstance(String algorithm, String provider).
Unfortunately, there's no way in auth0 to pass a provider instance or it's name to the CryptoHelper.
Describe the ideal solution
Since auth0 is already relying on java.security.Signature class to compute signatures, for me, the ideal solution would be to add a provider parameter to the JWTCreator.Builder#sign(Algorithm algorithm) method to match the java.security.Signature.getInstance(String algorithm, String/Provider provider) method in the Java API.
Alternatives and current work-arounds
I'm unsure if setting the HSM provider as the provider in position 0 of the providers list would suffice. Other than this, I'm forking auth0 and modifying the code.
Additional information, if any
I'm using auth0 3.16.0.
I'm also available to implement this and create a pull request with the code. I'm doing it right now..
Regards
Antonio Pedro Santos

Hello again,
I have the code ready but have no permissions to push a new branch ;). I was able to keep the API untouched, as the tests remain unchanged and still compile.
Hope to hear back from you. In the meantime, I'm using my fork from release-4.0.0.
Regards
Antonio Pedro Santo
provider_support_patch.zip
s

Yeah, in the previous comment I attached the patch but forgot to say so..
Regards
APS

Hi @aps-dnxt, apologies for the delay. Thanks for the request and offer to make a PR. We'll take a look at this and see if this is something that makes sense to add.

Hi @jimmyjames
In our case it did given that we are using both BouncyCastle's Provider and a Luna HSM (which has it's own provider).
Maybe it's an edge case but it would also provide more flexibility to the lib. Win-win, right?
Regards,
APS

I had a similar situation come up where I was using this JWT library in a java application running on a CentOS 7 image with FIPS enabled and it was refusing to allow any of the algorithms supported by this library to be used. It would be nice to allow alternative  providers like BouncyCastle for those cases. It would be great if Argon2 could be added. Spring's Security Crypto module uses bouncy castle under the hood to implement it. https://docs.spring.io/spring-security/site/docs/6.0.x/api/org/springframework/security/crypto/argon2/Argon2PasswordEncoder.html

@aps-dnxt 👋 If we can add this through standard Java typings, it may be a win-win. Could you provide some details about the new public APIs proposed (signatures) and if any additional dependencies would be required (doesn't sound like it, but just to be sure). Or if you already have the changes made, we could just review in a PR (are you still unable to make a PR?). If not we can look at the patch you provided (though we do want contributions so should figure out why that's an issue). Thanks again!

Hi @jimmyjames! Just opened a PR. Yes, I used all standard Java typings. Hope it's up to the project's quality.
I also thank you and the rest of the team for all the work you threw at this so that I can use it in my project :).
Regards.

It would be nice to have a facility of mentioning the SecurityProvider, say BouncyCastleProvider, while creating a JWTCreator & JWTVerifier.


Bind Address in use error at upgrade of Machine Controller from KubOne 1.2.3 -> KubeOne 1.3.0-alpha

What happened:
Upgrading of a GCE KubeOne cluster from version 1.2.3 to use KubeOne 1.3.0-alpha.0 broke the machine controller validation webhook deployment. The webhook pod don't start, due to:
k logs -f machine-controller-webhook-84bb7f5467-ggnj8 -c machine-controller-webhook
W0730 14:33:24.039052       1 client_config.go:608] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0730 14:33:24.133720       1 plugin.go:95] looking for plugin "machine-controller-userdata-amzn2"
I0730 14:33:24.133837       1 plugin.go:123] checking "/usr/local/bin/machine-controller-userdata-amzn2"
I0730 14:33:24.137414       1 plugin.go:136] found '/usr/local/bin/machine-controller-userdata-amzn2'
I0730 14:33:24.137484       1 plugin.go:95] looking for plugin "machine-controller-userdata-centos"
I0730 14:33:24.137527       1 plugin.go:123] checking "/usr/local/bin/machine-controller-userdata-centos"
I0730 14:33:24.137606       1 plugin.go:136] found '/usr/local/bin/machine-controller-userdata-centos'
I0730 14:33:24.137613       1 plugin.go:95] looking for plugin "machine-controller-userdata-flatcar"
I0730 14:33:24.137665       1 plugin.go:123] checking "/usr/local/bin/machine-controller-userdata-flatcar"
I0730 14:33:24.137687       1 plugin.go:136] found '/usr/local/bin/machine-controller-userdata-flatcar'
I0730 14:33:24.137700       1 plugin.go:95] looking for plugin "machine-controller-userdata-rhel"
I0730 14:33:24.137745       1 plugin.go:123] checking "/usr/local/bin/machine-controller-userdata-rhel"
I0730 14:33:24.137838       1 plugin.go:136] found '/usr/local/bin/machine-controller-userdata-rhel'
I0730 14:33:24.137849       1 plugin.go:95] looking for plugin "machine-controller-userdata-sles"
I0730 14:33:24.137900       1 plugin.go:123] checking "/usr/local/bin/machine-controller-userdata-sles"
I0730 14:33:24.137926       1 plugin.go:136] found '/usr/local/bin/machine-controller-userdata-sles'
I0730 14:33:24.137935       1 plugin.go:95] looking for plugin "machine-controller-userdata-ubuntu"
I0730 14:33:24.137951       1 plugin.go:123] checking "/usr/local/bin/machine-controller-userdata-ubuntu"
I0730 14:33:24.138012       1 plugin.go:136] found '/usr/local/bin/machine-controller-userdata-ubuntu'
F0730 14:33:24.141985       1 main.go:86] Failed to start server: listen tcp <IP_ADDRESS>:9876: bind: address already in use

What is the expected behavior:
Machine Controller comes up and get correct migrated by kubeone
How to reproduce the issue:
(not sure if every cluster breaks) but upgrade a existing 1.2.3 with new kubeone binary by kubeone apply
Anything else we need to know?
run-2 env
Information about the environment:
KubeOne version (kubeone version):
$ kubeone version
{
  "kubeone": {
    "major": "1",
    "minor": "3",
    "gitVersion": "v1.3.0-alpha.0",
    "gitCommit": "4d2a705612750eb8d74a6c59de3df92118b45b6c",
    "gitTreeState": "",
    "buildDate": "2021-07-30T16:23:16+02:00",
    "goVersion": "go1.16.5",
    "compiler": "gc",
    "platform": "linux/amd64"
  },
  "machine_controller": {
    "major": "1",
    "minor": "33",
    "gitVersion": "v1.33.0",
    "gitCommit": "",
    "gitTreeState": "",
    "buildDate": "",
    "goVersion": "",
    "compiler": "",
    "platform": "linux/amd64"
  }
}```
Operating system: `Ubuntu`
Provider you're deploying cluster on: `gce`
Operating system you're deploying on: `Ubuntu`

@toschneck which kubernetes versions has need used?


Canot create wallets by rai_node service

Install rai_node on centos 7
Service rai_node run success but can't create wallet
[vudangnt@rai-node ~]$ sudo service rai_node status
Redirecting to /bin/systemctl status rai_node.service
● rai_node.service - RaiBlocks node service
Loaded: loaded (/etc/systemd/system/rai_node.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2017-12-25 06:27:45 UTC; 7s ago
Main PID: 1162 (rai_node)
CGroup: /system.slice/rai_node.service
└─1162 /home/vudangnt/rai_node --daemon
Dec 25 06:27:45 rai-node systemd[1]: Started RaiBlocks node service.
Dec 25 06:27:45 rai-node systemd[1]: Starting RaiBlocks node service...
[vudangnt@rai-node ~]$ curl -g -d '{ "action": "wallet_create" }' <IP_ADDRESS>:7076
curl: (7) Failed connect to <IP_ADDRESS>:7076; Connection refused
Config file:
"rpc_enable": "true",
"rpc": {
"address": "::ffff:<IP_ADDRESS>",
"port": "7076",
"enable_control": "true",
"frontier_request_limit": "16384",
"chain_request_limit": "16384"
},

I'm having similar issues connecting via rpc. @vudangnt have you figured it out yet?

Check sudo netstat -ltnp look for the addresses and ports that the node is listening on.
Config file shows "::ffff:<IP_ADDRESS>" and not <IP_ADDRESS>.

Just use normal user in config service, do not use root


Docs headings and ToC

Move from h4s and misc to h5s so headings from example snippets don't show in our table of contents. This change is possible after the ToC config settings. Closes #24489.

Assuming you tested this 👍


Support Redshift UNLOADs

I'm sure this will need a once over. I don't have a handle on all of the internals yet. Questions I have

Is a Directory(S3) the right resource type for an s3 prefix (an s3 uri that ends in a forward slash)?
What should be tested?
Is it customary to leave out explicit keyword arguments in things like redshift_to_s3_bucket? This rubs me the wrong way.
Is append the right and only dispatcher I need?

Will need to rebase on #450.
Closes #447.

@jseabold apologies for the extreme lag in looking in this.  Thanks for the PR.
Assuming this is still relevant to you, could you rebase / merge in master?  There's been some work around updating the sqlachemy-redshift imports that I want to make sure are consistent with this PR.

Rebased on master. I think it would be nice if we can find a way to get this in. I've written and am using my own redshift connector for dask but perhaps code sharing is better here.
Some of the fundamental questions asked above are still outstanding.

Is this going to be merged into master? I need this in blaze.

I don't think anything is still blocking this. I am going to merge. If there is a problem we can revert.


Split out ProfileBinding webhook

What type of PR is this?
/kind bug
/kind flake
What this PR does / why we need it:
The ProfileBinding CRD isn't required for the minimum functionality of
the operator, and it requires installing cert-manager additional
dependency which may not be desireable to all users. Furthermore,
cert-manager is causing intermittent problems in the e2e tests that need
to be worked out. This change splits the webhook into its own command
and its own deployment, and skips deploying and testing it in the e2e
tests. The webhook e2e test can still be run manually by setting the
environment variable E2E_RUN_EXPERIMENTAL=Y.
Which issue(s) this PR fixes:

Relates to #220
Does this PR have test?

N/A
Special notes for your reviewer:
Does this PR introduce a user-facing change?
NONE

Do you think it would make sense to make the webhook deployment configurable in a follow-up?

Had to think about it for a bit but yes I think it would be good to follow this pattern. I filed https://github.com/kubernetes-sigs/security-profiles-operator/issues/270 to track that.


handoff always say failed to determine if node X is active

I have a 7-nodes cluster, after upgraded to the 10.3, I always got some errors in the log, say:
[handoff] 2016/03/15 14:45:02 failed to determine if node 9 is active: node not found
[handoff] 2016/03/15 14:45:02 failed to determine if node 13 is active: node not found
[handoff] 2016/03/15 14:45:02 failed to determine if node 11 is active: node not found
the show servers command shows only 7 boxes, so why it try to find 9,11 and 13? How can I fix this (by change some configs or run some tools)?

@lcrenix Did you remove any nodes via a drop server command?  That message is reported when a server is dropped and there are still hinted handoff queued messages on other nodes.  Hinted handoff queues are not currently deleted so those message will continue to be logged.
On the server logging those errors. you can delete the numeric sub-directory under your hinted handoff dir (default "hh") corresponding to the node ID.

@jwilder yes, I removed some nodes by using drop meta server and drop data server,  I'll try to manually delete these folders from the hh folder, thank you!

Closing this is as this is a known issue an won't be fixed in 0.11 or later.  Hinted handoff code no longer exists in master.


CI:impl for escapes detect as github action

resolve #161
Signed-off-by: Sam Yuan<EMAIL_ADDRESS>

https://github.com/sustainable-computing-io/kepler/actions/runs/3143019794/jobs/5107286079#step:4:398 @rootfs FYI

for vulnerability check https://github.com/sustainable-computing-io/kepler/actions/runs/3143172203/jobs/5107602033 as it is experimental tool, I didn't force it to pass for now.

@sustainable-computing-io/kepler-testing

This is impressive!

Looks very good!
Are you planning to fix some of the issues? :)
/lgtm

https://github.com/sustainable-computing-io/kepler/actions/runs/3143019794/jobs/5107286079#step:4:398 @rootfs from this job we can know where do we have escapes.

this is really a tall list, any plan to fix them all or there are severity levels we can use to prioritize?


Added chinese simplification for noon and pm

fixes #232

Current coverage is 94.37% (diff: 100%)

Merging #236 into master will not change coverage

@@             master       #236   diff @@
==========================================
  Files            32         32
  Lines          2736       2736
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           2582       2582
  Misses          154        154
  Partials          0          0

Powered by Codecov. Last update 73ba31c...8172ad2


Make better use of the GHA cache

Description
This PR aims to improve the cache effects of the GHA jobs. I've noticed that the GHA jobs spend considerable time building dependencies, and I have a proposed fix for that.
First, some observations using cardano-ledger#4488 as an example. This PR changes only a GitHub workflow file, but we can observe:

Build jobs like build (8.10.7, ubuntu-latest) spend 21m 41s building dependencies
Test jobs like byron-spec-chain-8.10.7-ubuntu-latest also spend a considerable amount of time on building dependencies, even though the previous build job has already built it.
Moreover, a test job like byron-spec-ledger-8.10.7-ubuntu-latest is also building those same dependencies as the previous one, so the reduced cache effect is compounded by having separate test jobs.

What I'd expect here is that these jobs would be able to restore a cache holding all the already built dependencies, assuming that an appropriate cache was created by a job that was run previously
The solution is to make the cache keys more expressive. Currently, a new cache is only created when the CABAL_CACHE_VERSION environment variable is changed, or if a cabal.project* file is changed. This does not account for dependencies changing (or other parts of the cabal files changing). As such, if a dependency is changed, then the built dependencies of the new build plan are not stored in a new cache (keys are never overwritten). Subsequent jobs will therefore also restore an old cache, and also build the new dependencies
As an aside, I've used the newer restore/save actions, which allow the cache of dependencies to be saved earlier than normal: right after building the dependencies, instead of at the end of the job.
Note:

New caches add dependencies to old caches, so the size of new caches grows over time. There is a limit on how many bytes of cache can be used by a repo, and so there might be a high degree of evicted caches if the individual caches become too large. The CABAL_CACHE_VERSION environment can be changed manually to reset all the caches, or one could reset the caches automatically once in a set time period like we do in consensus
With the proposed solution, any change to a cabal file would result in a new cache. I personally don't think it's a problem, but if you want to have fewer new caches, you could make the cache depend only on the dependency list like we do in consensus
I think at some point cardano-ledger also cached the dist-newstyle folder. You could reconsider also caching that (if it isn't too large that it takes up significant cache space) to reduce build times. The build job for ghc-8.10.7 in particular seems to be costly

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[x] New tests are added if needed and existing tests are updated
[x] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[x] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

@amesgen mentioned that https://github.com/andreabedini/cabal-cache-native might eventually be a nice alternative to the current caching actions, once released

Please have a go (or I can open a PR). The action should be complete, it only needs some stress testing.

Please have a go (or I can open a PR). The action should be complete, it only needs some stress testing.

I'll probably try it out in https://github.com/IntersectMBO/lsm-tree, which has shorter build times, and then I could port that over to this PR

By all means, guys. If you can reduce our CI build times in any way you can we will forever be indebted to you :wink:

There seems to have been an unrelated test failure: https://github.com/IntersectMBO/cardano-ledger/actions/runs/9905527544/job/27367972778?pr=4489#step:12:578

Comparing a run of GHA on this PR (https://github.com/IntersectMBO/cardano-ledger/actions/runs/9908237728/usage) and on
#4488 (https://github.com/IntersectMBO/cardano-ledger/actions/runs/9880346192/usage) shows that total running time is down from 1d 18h 56m 29s to 17h 40m 41s

@lehins what do you think about adding this to the workflow?
concurrency:
  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
  cancel-in-progress: true

It would cancel ongoing GHA runs when a new commit is pushed to the branch before the run is finished

what do you think about adding this to the workflow?

@jorisdral We already do that:
https://github.com/IntersectMBO/cardano-ledger/blob/3c1b5765cc219e85988bafa8d5e546e45ae9c1a1/.github/workflows/haskell.yml#L25-L33

what do you think about adding this to the workflow?

@jorisdral We already do that:
https://github.com/IntersectMBO/cardano-ledger/blob/3c1b5765cc219e85988bafa8d5e546e45ae9c1a1/.github/workflows/haskell.yml#L25-L33

Oops! Missed that -- I only looked at the top of the file


feat(AlgebraicGeometry): universally closed morphisms are topologically proper

from the valuative criterion project
Co-authored-by: Christian Merten

Thanks!
bors merge


Add warning about file_server directive.

I ran into an issue when using the file_server directive where the cgi would only return 404 errors, not being able to find the path. The proposed change to the README gives a warning about the case and an example on how to work around it using the handle directive.  This was a caddy v2 change because in v1 this workaround was not required.

I think this documentation change is incorrect.
The problem I think (FYI @aksdb) is that there's a bug with the middleware handling. See here:
https://github.com/aksdb/caddy-cgi/blob/86eddda826aa4d908dc8f20e9ad428a2481ad544/cgi.go#L176
This passes through to the subsequent middleware, so that means if a file_server directive runs after cgi, then it will always write a 404.
The cgi directive should be terminal, in other words it should not call next and it should just return nil instead (but you could add a pass_thru option like the file_server directive has if you want to make it call the next middleware).

I think this documentation change is incorrect.
The problem I think (FYI @aksdb) is that there's a bug with the middleware handling. See here:
https://github.com/aksdb/caddy-cgi/blob/86eddda826aa4d908dc8f20e9ad428a2481ad544/cgi.go#L176
This passes through to the subsequent middleware, so that means if a file_server directive runs after cgi, then it will always write a 404.
The cgi directive should be terminal, in other words it should not call next and it should just return nil instead (but you could add a pass_thru option like the file_server directive has if you want to make it call the next middleware).

Simply returning nil here fixed my problems with the handle_errors directive.

Another small thing, the readme mentions using order cgi last. I don't think that's the best order to use in this case.
I'd suggest maybe order cgi before respond. See https://caddyserver.com/docs/caddyfile/directives#directive-order, this would put it above other response-writing handlers.
From what I've seen from a few users who asked questions on the forums & discord about the plugin, they tend to want to pass requests to cgi "sometimes" and serve static files for any other request.
Having cgi last means any other handler directive would need a matcher instead so that it doesn't eat requests before it reaches cgi, and it's often not as easy to craft a matcher that would fit depending on the needs.

Both problems should be fixed in 2.2.1. I don't delegate to the subsequent handlers anymore and I adjusted the README recommendation regarding the order of the module.

Thank you! I think this PR can be closed.

Since a better solution has been found, I concur. This PR is not needed anymore. Thanks for raising awareness and starting the solution-finding-process :smile:


Allow Project Admins to configure refresh token expiry

Different apps will have different requirements around how long a refresh token should last. We should allow project admins to configure the expiry time for their refresh tokens.
**Open question: ** Should this be a project-level setting, or a setting on the ClientApplication?

Patient auth and provider auth often have different requirements both from the regs (d1 vs g10) and on the practice policy side - so ClientApplication seems pragmatic for that reason.

@codyebberson mentioned that it could also make sense for this to live on the AccessPolicy

Closed as completed via #4525


update the version of DC/OS to 1.11.10

High-level description
https://jira.mesosphere.com/browse/DCOS-48228 - Update the next release of 1.11 DC/OS version to 1.11.10
How to review

Go to https://dcos.io/releases/ and make sure the version mentioned in this change is the next version of DC/OS for 1.11 release

@mesosphere-mergebot label ready for review

@mesosphere-mergebot merge-it

@mesosphere-mergebot bump-ee


Chapter 11, p. 341 & 342

Page 341
The formula for net input misses bias.
Page 342

I think this should be x^(in)`.

Thanks, good catch! Will add a note to the errata to add the missing bias unit. The second one, in pg 342 was already fixed some time ago in a preprint I think:


Better single line recovery

Sometimes a parse error causes the block function to consume all of the remaining tokens. This PR fixes that issue by discarding the line, which should drastically improve parse error recovery.
Fixes #157

Heya!  Looks like this reports a few more errors than expected.  Consider this test file:
sub main()
    aa = { foo: "bar",  baz: "qux" +}
    derp()
end sub

sub derp()
    print "hi!"
end sub

With your changes, three errors are reported:
$ brs error.brs
error.brs(2,36-37): Found unexpected token '}'
error.brs(2,21-22): Expected newline or ':' after expression statement
error.brs(2,35-36): Expected newline or ':' after expression statement

But in current-master, only the first is reported:
$ brs error.brs
error.brs(2,36-37): Found unexpected token '}'

That seems like a pretty big regression - anything we can do to reduce the extraneous errors?

In typescript, one invalid character can cause a bunch of bogus error messages too. I created a test typescript file and added the percent sign to the end of the name property of an object. While that's technically the only issue, it DOES cause a ripple effect of other parse errors.

With respect to this PR, I wouldn't consider it a regression. Nothing stops working, and we still get the error we used to get. We just end up with a few extra errors as well. The current master branch, in many cases, scraps either the rest of the block or sometimes the rest of the file. I feel like this PR moves us in the right direction, and these extra errors are worth that forward progress.
For example, using the master branch code, typing a not-fully-formed function name causes a similar set of errors to the ones you mention above, but in this case, line 2 is VALID but gets marked as invalid.

However, with this branch, we are now able to recover from that by discarding the der line

I know we have more work to do when handling parse errors inside of array and associative array literals, but I think this PR is still a step forward.
Thoughts?

Thanks for the writeup!  It seems Ruby does something similar: https://repl.it/repls/VariableSilentGravity
You're right - this is definitely an improvement over the status quo!


Crouton error download kali

Please paste the output of the following command here: sudo edit-chroot -all

Please describe your issue:
When Crouton is retrieving packages to install kali-rolling it mentions cannot check release signature and then says links are not available anymore.
If known, describe the steps to reproduce the issue:
Run sudo crouton -n kali -r kali-rolling -t core,xiwi,xfce,extension

check this out you may need to fork and adjust the kali repo location
https://pkg.kali.org/pkg/debootstrap
crouton uses debootstrap to install distros the current crouton distro is not current for debootstrap this is maintenance activity

Thank you Tom

#4799


Introduce an equate judgment

The only way we have to relate types is via subtyping. This plays poorly with invariant type constructors because we must apply subtyping both ways. This is especially bad if invariant constructors are nested, which is common with mutable references.
For example, consider a type S<T> invariant on T. If we want to prove the judgment
&mut S<i32{v: v > 0}> <: &mut S<i32{v: 0 < v}>

We will generate the following derivation
       v>0 => 0<v              0<v => v>0                 0<v => v>0                 v>0 => v<0
------------------------  ------------------------   -----------------------   ------------------------
i32{v:v>0} <: i32{v:0<v}  i32{v:0<v} <: i32{v:v>0}   i32{v:0<v} <: i32{v:v>0}  i32{$v:>0} <: i32{v:v<0}
--------------------------------------------------   --------------------------------------------------
        S<i32{v:v>0}> <: S<i32{v:0<v}>                         S<i32{0<v}> <: S<i32{v>0}>
        ---------------------------------------------------------------------------------
                          &mut S<i32{v:v>0}> <: &mut S<i32{v:0<v}>

Maybe we could have an equate judgment and switch to that when we have invariant subtyping. This way, I think we could define most of the judgment structurally and "push down" the double implication. I'm thinking we can get a derivation like this
         v>0 => v<0  v<0 => v>0
        ------------------------
        i32{v:v>0} ≡ i32{v:v<0}
     ------------------------------
     S<i32{v:v>0}> ≡ S<i32{v:v<0}>
----------------------------------------
&mut S<i32{v:v>0}> <: &mut S<i32{v:0<v}>

In this simple example, it sounds like it should work because both types are structurally equal (up to the differences in the predicate), but in general, this is more complicated because existentials can appear  out-of-order and there are types that are not structurally equal but should be (judgmentally) equivalent (they would be if we apply subtyping both ways). For example, the following should hold
∃a. (i32[a], ∃b. {i32[b] | a > b}) ≡ ∃a,b. ({i32[a] | b < a}, i32[b])

Also, more than out of order, types can differ in the number of existential and still be equivalent, e.g.,
i32[0] ≡ ∃v. {i32[v] | v == 0}

So I think in general we need to fall back to subtyping both ways in some cases, but what could help is to canonicalize types by pulling out constraints and existential to increase the chances of types being structurally equal. For example, we can canonicalize
∃a. (i32[a], ∃b. {i32[b] | a > b}) ≡ ∃a,b. ({i32[a] | b < a}, i32[b])

to
∃a,b. { (i32[a], i32[b]) | a > b } ≡ ∃a,b. { (i32[a], i32[b]) | b < a }

so the types are structurally equal up to the difference in the predicate.


fix RpcClient.cs code

delete weird semicolon
channel must be closed before closing connection (order is important)

code from rabbitmq-tutorials > RPCClient.cs

if RpcClient is not disposed, Task from InvokeAsync will not completed.

@naramdash channels do not have to be explicitly closed. When a connection is closed, so will be all channels on it.

I will apply this change manually.

https://github.com/rabbitmq/rabbitmq-website/commit/fbfd29818bd2d44de0ca344e470b62c0f627f299


[BUG-python/deployment] Confusion about dataset_argilla.exists() / .delete() / .create()

Describe the bug
When I create a dataset with the following code:
dataset_argilla_name = "code-llm"
workspace_name = "admin"
reuse_existing_dataset = False  # for easier iterative testing

annotators = ["annotator-1", "annotator-2", "annotator-3"]

# Create the interface structure via an Argilla FeedbackDataset
settings = rg.Settings(
    # The overall annotation guidelines, which human annotators can refer back to inside of the interface
    guidelines=annotator_guidelines,
    # The fields on the left side of the interface
    fields=[
        rg.TextField(name="instruction", title="Instruction:", use_markdown=True, required=True),
        rg.TextField(name="generation_1", title="Response model 1:", use_markdown=True, required=True),
        rg.TextField(name="generation_2", title="Response model 2:", use_markdown=True, required=True),
    ],
    # The different questions on the right side of the interface
    # These are the questions we ask annotators about the fields on the left of the interface
    # The available question types are documented here: https://docs.argilla.io/en/latest/getting_started/cheatsheet.html#configure-datasets
    questions=[
        rg.RatingQuestion(
            name="score_response_1",
            title="Your score for the response of model 1:",
            description=rating_tooltip,  #"1 = very bad\n2 = bad\n3 = mediocre\n4 = good\n5 = very good",
            values=[0, 1, 2, 3, 4, 5, 6, 7],
            required=True,
        ),
        rg.RatingQuestion(
            name="score_response_2",
            title="Your score for the response of model 2:",
            description=rating_tooltip,  #"1 = very bad\n2 = bad\n3 = mediocre\n4 = good\n5 = very good",
            values=[0, 1, 2, 3, 4, 5, 6, 7],
            required=True,
        ),
        rg.LabelQuestion(
            name="which_response_corrected",
            title="If both responses score below 4, select a response to correct:",
            description="Select the response you will correct in the text field below.",
            labels = ["Response 1", "Response 2", "Combination of both", "Neither"],
            required=False,
        ),
        rg.TextQuestion(
            name="correction",
            title="Paste the selected response below and correct it manually:",
            description="Your corrected response must fulfill all criteria from the annotation guidelines.",
            use_markdown=True,
            required=False
        ),
        rg.TextQuestion(
            name="comments",
            title="Annotator Comments",
            description="Add any additional comments here. E.g.: edge cases, issues with the interface etc.",
            use_markdown=True,
            required=False
        ),
    ],
    metadata = [
        rg.TermsMetadataProperty(
            name="annotator-groups",
            title="Annotator groups",
            options=annotators,
        ),
        rg.TermsMetadataProperty(
            name="source-dataset",
            title="Original dataset source",
        ),
    ],
    allow_extra_metadata = False
)

dataset_argilla = rg.Dataset(
    name=dataset_argilla_name,
    workspace=workspace_name,
    settings=settings,
    client=client,
)

And then I run dataset_argilla.exists() it returns None indicating that the dataset does not exist yet.
However, when I then run dataset_argilla.create() again I get an error indicating that it does exist: ConflictError: Argilla SDK error: ConflictError: Conflict with the server. Resource or entity already exists. Details: {"detail":"Dataset with name code-llmalready exists for workspace with idf6667c96-49cf-497e-821e-830b98e6e821"}
But running dataset_argilla.delete() returns UnprocessableEntityError: Argilla SDK error: UnprocessableEntityError: Unprocessable entity. The server cannot process the request. Details: {"detail":{"code":"argilla.api.errors::ValidationError","params":{"errors":[{"loc":["path","dataset_id"],"msg":"value is not a valid uuid","type":"type_error.uuid"}]}}}
expected behaviour
Does the dataset exist, or does it not exist?
dataset_argilla.exists() should probably return something indicating that the dataset exists (or .delete() / .create() should return something indicating that the dataset does not exist)
Or do I misunderstand something?
Environment:
!pip install argilla==2.0.0rc1
with Argilla running in a HF space.

@sdiazlor 's code here solved the issue for me. I hadn't understood that after running
dataset_argilla = rg.Dataset(
    name=dataset_argilla_name,
    workspace=workspace_name,
    settings=settings,
    client=client,
)

I then still need to run
retrieved_dataset = client.datasets(name=dataset_argilla_name, workspace=workspace_name)
before I can run .exists() on retrieved_dataset
I was trying to call dataset_argilla.exists()
My wrong code:
dataset_argilla = rg.Dataset(
    name=dataset_argilla_name,
    workspace=workspace_name,
    settings=settings,
    client=client,
)
if dataset_argilla.exists():
    dataset_deleted = dataset_argilla.delete()
dataset_argilla.create()

Correct code:
dataset_argilla = rg.Dataset(
    name=dataset_argilla_name,
    workspace=workspace_name,
    settings=settings,
    client=client,
)

retrieved_dataset = client.datasets(name=dataset_argilla_name, workspace=workspace_name)
if retrieved_dataset.exists():
    dataset_deleted = retrieved_dataset.delete()
dataset_argilla.create()

@frascuchon @burtenshaw let me know if you think it makes sense to keep the issue open and refactor this in case the first code snippet mentioned by @MoritzLaurer seems more intuitive for users.
Or close this issue if it's going to stay as it is now.


Add zoom value in the URL (or in style properties)

I want to cluster a layer icons until a zoom level. It's difficult to guess at which level I'm currently.
Could be helpful to see the zoom level on the URL, or to show it in a window (like the style options of the layer).

Maybe from the user point of view we should display equivalent scales instead of zoom level (which is only a technical detail) ?
Parameters in the URL are used to setup the view on refresh and zoom level will be redundant with the bouding box we use now. Indeed, defining the extent of the map to be visualized implicitly defines the adequate zoom level. However, we might add it anyway just as an additional information.


[2.2.7] Logs path is absolute?

I'm using the latest versione of Parse-Server and I keep getting this error:
Error: EACCES: permission denied, open '/logs/parse-server.info.2016-04-20'
    at Error (native)

It seems that the logs path is absolute and not relative to the project, and the logs are created in the absolute path /logs/. My Parse instance is running through foreverjs, maybe this helps?

It is. use __dirname in your config to construct an absolute path to a folder in your Parse Server project.

Not fixed, I set the logsFolder parameter to the absolute path of my Parse instance but Parse still creates the /logs directory in the root of the file system.

Where do you deploy? What's the path to you logs folder? What's the behaviour locally?

I'm using Parse with expressjs on a virtual machine running the latest Ubuntu LTS. The logs path is passed through the constructor of ParseServer. The configuration is attached, personal data is blacked out. As I said before the logsFolder is ignored and new logs are created at /logs (file system root).

I'll have a look

Can you reopen this issue then?

Maybe the logs folder is created by foreverjs.
I start my server by:
forever start index.js -l /home/abc-user/logs/abc.log

Nope, here is the error with my instance running as www-data
`fs.js:794
return binding.mkdir(pathModule._makeLong(path),
^
Error: EACCES: permission denied, mkdir '/logs'
at Error (native)
at Object.fs.mkdirSync (fs.js:794:18)
at configureLogger (/var/www/xxxx/node_modules/parse-server/lib/logger.js:71:18)
at Object. (/var/www/xxxx/node_modules/parse-server/lib/logger.js:80:1)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
error: Forever detected script exited with code: 1`


Trigger a channel publish event from server side outside of worker.js

I would like to trigger a channel publish event outside of worker.js
e.g: scServer.exchange.publish('tenant.LDN1', {message: 'hello tenant LDN1'});
I have a .net backend sending data to (via signalR) to my middletier (node running socketCluster). Once I get this new data at the middletier, I am parsing it and I would like to send it to the front-end. I am not sure how to do that, as I don't know how to get an instance of scServer outside of worker.js

somewhat similar https://github.com/SocketCluster/socketcluster/issues/371
@HoplaGeiss tldr you can connect to your existing sc app using https://github.com/SocketCluster/client-drivers or even via external queues.

Thanks!


MessagePack support

Does anyone need MessagePack support?
I can implement it in https://github.com/3Hren/msgpack-rust as an option.
It's not an issue actually, but it may generate issues if I start to working with it :)

That would be wonderful! If you haven't starting working on it yet, I think I have a partially implemented version I started and didn't finish months ago.

I am working on that. It seems to work pretty well except for enums which are very complicated as each variant can have a different type. How should I publish the code?
Should I make a separate crate or should I create a pull request?
BTW: I also have some macros which allow to serialize structs to tuples and maps without using a compiler plugin.

Actually I've already have rustc_serialize support: https://github.com/3Hren/msgpack-rust/blob/master/src/decode.rs#L1754.
Migrating from it to serde doesn't seems like a big problem.
The real challenge - is to how implement zero-copy deserialization into a non-owning structs, which contains &str or &[T] for example. Does serde allows to do that somehow?
PR is ok if only serde plans to be the main serialization/deserialization library (and rustc_serialize is going to be dead, right?).

My main problem with rmp, mpack and msgpack was that neither of them allowed me to serialize [u8] to msgpack bin. Instead all rustc-serialize based serializers serialize [u8] as a list of single u8 which is very inefficient as half of those bytes require two bytes to serialize.

Wrong: https://github.com/3Hren/msgpack-rust/blob/master/src/encode.rs#L634

Yes, you are right. However I did not figure out any way to use that with rustc-serialize.

With rustc_serialize - you're right, it's impossible. Does serde allows to encode &[u8] directly?

Not exactly but there is a wrapper type Bytes which serializes to bin. I don't think such a wrapper type would be possible with rustc_serialize as it does not expose any way to serialize binary data through its API.

@3Hren and @dswd: I've also hacked up msgpack support in https://github.com/3Hren/msgpack-rust/pull/26.

This has landed in rmp!

I don't see how this improves on the &[u8] issue. As far as I can see rmp still does not support it. There is no way to serialize something to binary data and you get a type mismatch error if you try to deserialize it.

Does this helps: https://github.com/3Hren/msgpack-rust/commit/380a68be68c7468c4f53e240fe149a557ee31357

And this should help with serialization: https://github.com/3Hren/msgpack-rust/commit/6c1f7c18fc036e746c787441450f209aec86cba0


I would add dropdown in a search dropdown but this will trigger an error  inside dropdown is not displayed

https://jsfiddle.net/IIN727/vrr94krd/1/?utm_source=website&utm_medium=embed&utm_campaign=vrr94krd

Dropdowns with overflow like search dropdown do not support sub menus.


Bump Spring boot dependency to latest version

Merged. Thank you for the contribution!
Planning to do the 4.6 release tomorrow (on Jan 1st).


Allow wildcards in files association

It would be great to add * support for files association like:
  "symbols.files.associations": {
    "*.module.ts": "ts",
  }

as right now you have to match the exact name for it to work (app.module.ts), which can get tedious.
FYI @wladimirgrf

Nice, it's a good feature, I can take a look at how to implement it.

Started looking into this and this is not supported by the VS Code extension API https://github.com/Microsoft/vscode/issues/12493

Maybe there is a way to do it, material-icon-theme has that feature.
About the https://github.com/miguelsolorio/vscode-symbols/pull/92, did you test it? It work fine for you?

They have the same issue https://github.com/PKief/vscode-material-icon-theme/issues/330 and yes the current file association works, you have to match the name exactly.

Yes, we can make the simplest version, it already solves most cases.
I asked about the last PR, because I'm testing the official extension and I need to reload the window every time I change the settings.json (to update the icons).

Ah, I thought that was the expected behavior? At least when I tested it with the material icons it also worked the same way (icon only changes after reload)

hmm I see, I wasn't 100% sure how it would look after publishing.
This is the first extension project for VsCode that I work on.
The idea was to behave exactly like material-icons, as soon as the settings.json is updated so is the icon.
I will try to do this. If everything goes well I'll open another PR.

*.module.ts is just a non-standard fileExtensions key to be fair!

Fixed via https://github.com/miguelsolorio/vscode-symbols/pull/101


[stable/odoo]: fix password retrieval instructions

Fixes https://github.com/kubernetes/charts/issues/815
Instructions match the redmine and some other charts: https://github.com/kubernetes/charts/blob/master/stable/redmine/templates/NOTES.txt#L26

👍

@k8s-bot ok to test


Is is possible to apply the model.json on multiple data lakes vs just one?

Is it possible to apply one model.json for multiple Data Lakes vs just one?

@isamllr Thanks for reporting this issue. We're looking into it and will update here when we have a resolution.

Hi isamllr,
Could you please provide more deals about the scenario you are working on? Information about model.json - https://docs.microsoft.com/en-us/common-data-model/model-json

@isamllr We are closing this issue because we haven't gotten a response from you. Please reopen the issue as needed.