prettier-plugin-tailwindcss doesn't work with vscode

prettier-plugin-tailwindcs: v0.2.1
Tailwind CSS: v3.2.4
Node.js: v18.12.1
Package Manager: pnpm v7.21.0
Operating System: Windows 11
Describe your issue
prettier-plugin-tailwindcss doesn't work with vscode and it's plugin Svelte for VS Code and Prettier - Code formatter;
it won't format the *.svelte files (but it formats the html files);
And with the svelte files, the "prettier" has taken effect, cause the prettier-plugin-organize-imports and prettier-plugin-css-order works fine，except prettier-plugin-tailwindcss...，so i think Is there anything that prevents tailwind formatting?...
here is my .prettierrc
{
    "plugins": ["prettier-plugin-svelte", "prettier-plugin-organize-imports", "prettier-plugin-css-order", "prettier-plugin-tailwindcss"],
    "pluginSearchDirs": false,
    "svelteSortOrder": "options-scripts-markup-styles",
    "svelteStrictMode": false,
    "svelteAllowShorthand": false,
    "svelteIndentScriptAndStyle": true,
    "organizeImportsSkipDestructiveCodeActions": true,
    "semi": true,
    "useTabs": false,
    "tabWidth": 4,
    "singleQuote": true,
    "trailingComma": "es5",
    "bracketSpacing": true,
    "bracketSameLine": true,
    "endOfLine": "lf",
    "quoteProps": "as-needed",
    "arrowParens": "always",
    "printWidth": 999999,
    "htmlWhitespaceSensitivity": "ignore",
    "singleAttributePerLine": false
}

I was JUST about to say this and you beat me to it by 12min LMAO. +1 on this issue.

Make that a +2
prettier-plugin-tailwindcs: v0.2.1
Tailwind CSS: v3.2.4
Node.js: v16.16.0
Package Manager: pnpm v7.13.5
Operating System: Big Sur v11.7.2
.prettierrc
{ 	"useTabs": false, 	"tailwindConfig": "./tailwind.config.cjs", 	"trailingComma": "es5", 	"semi": false, 	"singleQuote": true, 	"arrowParens": "avoid", 	"printWidth": 120, 	"plugins": [ 		"prettier-plugin-svelte", 		"prettier-plugin-tailwindcss" 	], 	"pluginSearchDirs": [ 		"." 	], 	"overrides": [ 		{ 			"files": "*.svelte", 			"options": { 				"parser": "svelte" 			} 		} 	] }

@floormodelcitizen
Based on your prettier configuration, if you add "prettier.documentSelectors": ["**/*.svelte"]  to the vscode settings.json, svelte will be formatted correctly; But prettier-plugin-organize-imports will fail;
This one is right, that one is wrong 😂

@floormodelcitizen
Based on your prettier configuration, if you add "prettier.documentSelectors": ["**/*.svelte"]  to the vscode settings.json, svelte will be formatted correctly; But prettier-plugin-organize-imports will fail;
This one is right, that one is wrong 😂

For me it doesn't work with astro. Any suggestions?
module.exports = {
  plugins: [
    require.resolve("prettier-plugin-astro"),
    require.resolve("prettier-plugin-tailwindcss")
  ],
  pluginSearchDirs: false,
  overrides: [
    {
      files: '*.astro',
      options: {
        parser: 'astro',
      },
    },
  ],
};

@floormodelcitizen
Couple of things:

Your prettier version is outdated (I went snooping around your desktop clock project :D). You need at least prettier 2.6. After updating it formatting in svelte files seems to work okay.
I noticed an issue where some used component imports get removed. This appears to be a problem with organize imports. The issue is present regardless of whether or not the tailwindcss plugin is enabled. Removing the organize imports plugin seems to fix the disappearing import.

So, as far as I can tell, your project seems to be working on my system at least. I'm testing on macOS Monterey but that shouldn't make a difference here.
@kuerme Could you provide a reproduction repo I can take a look at? I've got a windows machine as well I can test with.

Hi @thecrypticace,
You can find a demo repo here.

Also, if there is some code wrapped in an expression block, even after running prettier from command line won't sort the classnames:
An example would be:
{#await init()}

		<HeartIcon class="h-14 w-14 animate-ping fill-red-600" />

{:then}

		<slot />

{/await}

@ditoglez That looks like a separate bug to me. Would you please open a new issue?

@thecrypticace please find the issue here: https://github.com/tailwindlabs/prettier-plugin-tailwindcss/issues/117

@ditoglez I'm looking at your reproduction repo and it is indeed having problems formatting. But it's not using prettier at all in that project:

I can get it to format the code if I run Format Code (Forced). So as far as prettier itself is concerned it seems to work fine. Perhaps this is a problem with the Prettier VS Code extension? I'm not entirely sure what the cause is here. There's no output to indicate what the problem might potentially be either. I expect it is likely some incompatibility with pnpm and the vscode extension but not certain.

@thecrypticace sorry for the late reply. I also saw that the code can be formatted through Format Code (Forced) as a workaround, which I am using at the moment.  I tried switching between npm yarn and pnpm and the result is the same. Might be actually an issue with VSCode itself, I will try to take another look in my spare time.

I am facing the same problem when I have multiple plugins in my prettier config. Additionally, I am using a plugin for sorting imports in prettier, but it only enables the last plugin to work.

Might be related: https://github.com/prettier/prettier/issues/12807

@ditoglez I'm looking at your reproduction repo and it is indeed having problems formatting. But it's not using prettier at all in that project:

I can get it to format the code if I run Format Code (Forced). So as far as prettier itself is concerned it seems to work fine. Perhaps this is a problem with the Prettier VS Code extension? I'm not entirely sure what the cause is here. There's no output to indicate what the problem might potentially be either. I expect it is likely some incompatibility with pnpm and the vscode extension but not certain.

same here. It doesn't work with my vscode and pnpm. but npm works.

Am facing the same issue with Nextsjs project on windows.

Also seeing this on the latest prettier-plugin-tailwindcss version (0.2.2). Checking the Prettier logs, it looks like Prettier is not aware of the plugin when trying to autoload it:
["INFO" - 3:18:19 PM] Extension Name: esbenp.prettier-vscode.
["INFO" - 3:18:19 PM] Extension Version: 9.10.4.
["INFO" - 3:18:26 PM] Formatting file:///Users/matthewvolk/code/teller/src/pages/index.tsx
["INFO" - 3:18:26 PM] Using config file at '/Users/matthewvolk/code/teller/.prettierrc.json'
["INFO" - 3:18:26 PM] Using ignore file (if present) at /Users/matthewvolk/code/teller/.prettierignore
["INFO" - 3:18:26 PM] File Info:
{
  "ignored": false,
  "inferredParser": "typescript"
}
["INFO" - 3:18:26 PM] Detected local configuration (i.e. .prettierrc or .editorconfig), VS Code configuration will not be used
["INFO" - 3:18:26 PM] Prettier Options:
{
  "filepath": "/Users/matthewvolk/code/teller/src/pages/index.tsx",
  "parser": "typescript",
  "printWidth": 80,
  "singleQuote": true
}
["INFO" - 3:18:26 PM] Formatting completed in 230ms.

Unfortunately, even if I add "plugins": ["prettier-plugin-tailwindcss"] to .prettierrc.json, it tries looking for the plugin in node_modules (which does exist), but then there are no changes made to className strings inside the index.tsx file:
["INFO" - 3:19:17 PM] Formatting file:///Users/matthewvolk/code/teller/src/pages/index.tsx
["INFO" - 3:19:17 PM] Using config file at '/Users/matthewvolk/code/teller/.prettierrc.json'
["INFO" - 3:19:17 PM] Using ignore file (if present) at /Users/matthewvolk/code/teller/.prettierignore
["INFO" - 3:19:17 PM] File Info:
{
  "ignored": false,
  "inferredParser": "typescript"
}
["INFO" - 3:19:17 PM] Detected local configuration (i.e. .prettierrc or .editorconfig), VS Code configuration will not be used
["INFO" - 3:19:17 PM] Prettier Options:
{
  "filepath": "/Users/matthewvolk/code/teller/src/pages/index.tsx",
  "parser": "typescript",
  "printWidth": 80,
  "singleQuote": true,

  // New Log ⬇
  "plugins": [
    "/Users/matthewvolk/code/teller/node_modules/prettier-plugin-tailwindcss/dist/index.js"
  ]

}
["INFO" - 3:19:17 PM] Formatting completed in 30ms.

Before Save or npx prettier --write .:

After Save or npx prettier --write .:

Same issue with
Next.js 13.1.6
NodeJS 18.12.1
pnpm 7.26.2
VSCode
Windows

Same issue Format Code (Forced) works.
prettier-plugin-tailwindcs: v0.2.2
svelte-kit: 1.0.0
Tailwind CSS: v3.2.4
Node.js: v18.12.1
Package Manager: pnpm v7.26.2
Operating System: Windows 11
.vscode/settings.json
// For ESLint
    "eslint.validate": ["svelte", "javascript", "javascriptreact", "html", "json", "jsonc"],
    "editor.codeActionsOnSave": {
        "source.fixAll": false
    },
    "eslint.packageManager": "pnpm",
// For Prettier
    "editor.formatOnSave": true,
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "prettier.requireConfig": true,
// Svelte for VS Code
    "[svelte]": {
        "editor.defaultFormatter": "svelte.svelte-vscode"
    },

+1. vs code, sveltekit. not working :'-(

Same for me
prettier-plugin-tailwindcss: 0.2.2
prettier: 2.8.3
nodejs: 18.9.1
npm: 8.19.1
vite: 4.0.4
react: 18.2.0
VScode: 1.74.3
OS: Windows 11

I solved this problem after creating .prettierrc file and adding this:
{   "plugins": ["prettier-plugin-tailwindcss"],   "pluginSearchDirs": false }

Going back to my SvelteKit config (after setting it work for NextT3), I discovered that having both .prettierrc and prettier.config file caused the plug-in not to load, given if .prettierrc file contents are an empty json object like so:
{
}

Pretty surprising. I went back and forth at least 6 times, assuming I forgot to save a file or something, but consistently reproduced on my machine that having both files  keeps prettier for tailwinds from working (even though prettier otherwise working).

What's going on with the prettier plugin @reinink @adamwathan? The solutions mentioned above don't work.

I was able to get sveltekit with tailwind & their plugins working following this answer using pnpm.
Currently, the readme on tailwind-prettier-plugin recommends changing pluginSearchDirs and specifying the order of the plugins. I didn't do either of those and both tailwind-prettier-plugin & svelte-prettier-plugin are working.
My current .prettierrc
{
	"useTabs": true,
	"singleQuote": true,
	"trailingComma": "none",
	"printWidth": 100,
	"pluginSearchDirs": ["."],
	"overrides": [{ "files": "*.svelte", "options": { "parser": "svelte" } }]
}

The plugin works for me in Nextjs 13 but only when I run my format script. It doesn't actually format on save - the format on save functionality actually stops working entirely after declaring this plugin in my config. When I remove it, format on save is working again

Same issue here with NextJS 13.2.1

Hey folks! If you're having issues with the Prettier plugin, be sure to read the "Compatibility with other Prettier plugins" section of the readme: https://github.com/tailwindlabs/prettier-plugin-tailwindcss#compatibility-with-other-prettier-plugins
If you're using our Prettier plugin with another Prettier plugin that's incompatible with ours, it won't work out of the box and you'll need to follow the instructions there 👍

Hey @reinink, thanks for the reply. I am not using other prettier plugins. It's a barebones Nextjs 13 project with tailwind and prettier installed. Here is the prettier.config.js file:
module.exports = {
  singleQuote: true,
  semi: true,
  plugins: [require('prettier-plugin-tailwindcss')],
  pluginSearchDirs: ["."],
  tailwindConfig: './tailwind.config.js',
}

I've just discovered that when the file extension is .js the problem occurs and if it is .jsx the plugin works. I don't know if this is mentioned in the docs as a normal behavior but couldn't find anything.
In fact, here is a repo that reproduces the issue:
https://github.com/luizov/prettier-issue

I have just got this working. My setup uses:

SvelteKit
pnpm
VS Code

Firstly, a note on debugging. The Output tab in VS code spits out a load of info whenever prettier runs. This useful because it (A) shows when prettier runs, and (B) shows what config is being used. In my case, I was confused why tailwind classes weren't being sorted even though my document seemed to be formatted, turns out it was a different formatter doing the formatting. I did a bit of digging and found these two issues that set me right (1) (2)
TLDR;
1 - Rename .prettierrc to .prettierrc.cjs, then open .prettierrc.cjs and...
2 - Wrap the imports in a require and make sure tailwind is the last import.
3 - Set pluginSearchDirs to false
.prettierrc.cjs
module.exports = {
        ....
	plugins: [require('prettier-plugin-svelte'), require('prettier-plugin-tailwindcss')],
	pluginSearchDirs: false,
	overrides: [{ files: '*.svelte', options: { parser: 'svelte' } }]
        ....
};

It should now work.  Check the Output tab to double check that it's picking up the right config.
If Prettier still doesn't format the file, you may have to manually add a file association. Open settings in VS code, search for prettier document selectors, and add a new item: **/*.svelte

You can also see whether Prettier is recognizing your file in the bottom right hand corner of VS code, a double tick next to Prettier means you're all good.

Good luck!

This fixed the issue for me.
.prettierrc
{
  "pluginSearchDirs": ["."],
  "overrides": [{ "files": "*.svelte", "options": { "parser": "svelte" } }],
  "plugins": ["prettier-plugin-svelte", "prettier-plugin-tailwindcss"]
}

.vscode/settings.json
{
  "prettier.requireConfig": true,
  "prettier.documentSelectors": ["**/*.svelte"],
  "[svelte]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode",
  }
}

The issue for me was that I didn't have the prettier-plugin-svelte plugin, installing and adding it to my config fixed the issue 🙂

Hi @kuerme, I'm not sure if it helps, but the fix suggested by @lab-do works just fine (except that you don't even need to specify the plugins in the array, you can remove it entirely), with the mention that a window reload is needed. The issue that I'm facing is that prettier-plugin-organize-imports doesn't work. In your original comment, you say that it's working fine, but I'm wondering how can that be since the plugin doesn't actually have support for it (issue here)? Am I missing something?

None of the solutions above worked in my project but I found a solution so I share it, maybe will help others too.
Situation: We had installed in our project both prettier-plugin-tailwindcss and @trivago/prettier-plugin-sort-imports for sorting import statements, however, only the later was working.  In .prettierrc we had only one of them listed: "plugins": ["prettier-plugin-tailwindcss"].
Solution: Adding the …-sort-imports plugin before (the order mattered!) prettier-plugin-tailwindcss  fixed the issue. So our current, working .prettierrc file looks like that:
{
  "plugins": ["@trivago/prettier-plugin-sort-imports", "prettier-plugin-tailwindcss"],
  "singleQuote": true,
  "importOrder": ["<THIRD_PARTY_MODULES>", "^@(.+)/(.+)$", "^\\..+"],
  "importOrderSeparation": true,
  "importOrderSortSpecifiers": true
}

Ok very weird, i got it to work now thanks to @philipdanielhayton.
My setup was sveltekit+tailwind using just the svelte & tailwind plugins for prettier.
What i changed was:

I made a .prettierrc.cjs out of .prettierrc like:

module.exports = {
  arrowParens: 'avoid',
  bracketSameLine: true,
  svelteIndentScriptAndStyle: true,
  singleAttributePerLine: true,
  tabWidth: 2,
  svelteSortOrder: 'scripts-options-markup-styles',
  semi: false,
  useTabs: true,
  singleQuote: true,
  trailingComma: 'none',
  printWidth: 100,
  plugins: [require('prettier-plugin-svelte'), require('prettier-plugin-tailwindcss')],
  pluginSearchDirs: false,
  overrides: [{ files: '*.svelte', options: { parser: 'svelte' } }]
}

Changed my .vscode/settings.json to:

{
  "editor.formatOnSave": true,
  "editor.tabSize": 2,
  "files.insertFinalNewline": true,
  // before, i just had the following as TS exclusive
  "editor.defaultFormatter": "esbenp.prettier-vscode",
}

Finally reload the window.

Hope this can help someone else.

Alright folks, here is the summary. I just spent a good couple of hours debugging this.
Thank you everyone who have commented so far. Specially ones that who mentioned renaming files to common js syntax, switching pnpm to npm etc.

Using .prettierrc - npm

{
	"useTabs": true,
	"singleQuote": true,
	"trailingComma": "none",
	"printWidth": 100,
	"plugins": ["prettier-plugin-svelte", "prettier-plugin-tailwindcss"],
	"pluginSearchDirs": false,
	"overrides": [{ "files": "*.svelte", "options": { "parser": "svelte" } }]
}

Works. I could keep Svelte for VS Code as my default formatter. Both Prettier & Svelte formatter did the same. I am not sure if there is any difference at all here. If anyone knows please let me know.

Using .prettierrc - pnpm

Surprisingly pnpm didn't work. I no longer see the Prettier as a formatter. Svelte for VS Code does format, but tailwind plugin doesn't work (If you look at the prettier logs, it doesn't do anything). As others said Format Document (Forced) actually works.

Using .prettierrc.cjs - npm

module.exports = {
  useTabs: false,
  singleQuote: true,
  trailingComma: 'none',
  printWidth: 100,
  plugins: [require('prettier-plugin-svelte'), require('prettier-plugin-tailwindcss')],
  pluginSearchDirs: false,
  overrides: [{ files: '*.svelte', options: { parser: 'svelte' } }]
};

Works, same as above.

Using .prettierrc.cjs - pnpm
I don't see Prettier as a formatter. It was disabled in the corner like previously. But default formatter Svelte for VS Code picked up a tailwind plugin this time and actually worked.

Looks like something is wrong with pnpm x prettier setup. Also no need to mess with "prettier.documentSelectors": ["**/*.svelte"] .
TLDR; if you're using pnpm make sure you're using .prettierrc.cjs

Hey everyone! :wave:
It seems like there are a lot of different situations being presented in this issue, and I'm not entirely sure they all stem from the same underlying problem.
From what I can gather, most of the issues reported here seem to be related to pnpm. It's worth noting that there are known issues with Prettier itself when it comes to handling pnpm like https://github.com/prettier/prettier/pull/9167 and https://github.com/pnpm/pnpm/issues/4700.
I've got a few notes that should hopefully help anyone running into problems with pnpm:

We recommend you use a prettier.config.cjs or .prettierrc.cjs file instead of .prettierrc which will allow you to use require to load the plugin explicitly:

module.exports = {
  pluginSearchDirs: false,
  plugins: [require('prettier-plugin-svelte'), require('prettier-plugin-tailwindcss')],
  overrides: [{ files: '*.svelte', options: { parser: 'svelte' } }]

  // Other prettier options here
};

When using a JS prettier config be sure to set pluginSearchDirs: false and not pluginSearchDirs: ["."]. The internal plugin compatability we've implemented is order-dependent and doesn't necessarily work when the Tailwind CSS prettier plugin is not loaded last. This is a limitation of Prettier itself not directly supporting multiple plugins for the same language. Not setting this right could result, for instance, in Svelte files being formatted but classes not being sorted.

Before:
module.exports = {
  pluginSearchDirs: ["."], // <-- Don't do this
  overrides: [{ files: '*.svelte', options: { parser: 'svelte' } }]

  // Other prettier options here
};

After:
module.exports = {
  pluginSearchDirs: false, // <-- Do this instead
  plugins: [require('prettier-plugin-svelte'), require('prettier-plugin-tailwindcss')],
  overrides: [{ files: '*.svelte', options: { parser: 'svelte' } }]

  // Other prettier options here
};

Set "prettier.documentSelectors": ["**/*.svelte"] in your VSCode settings. It's not always required but some situations do need it to work properly. It's also recommended you add this anytime you also have overrides in your Prettier config.

{
  "prettier.documentSelectors": ["**/*.svelte"],
}

For Svelte specifically be sure that the formatter is set to svelte.svelte-vscode in your VSCode settings:

{
  "[svelte]": {
    "editor.defaultFormatter": "svelte.svelte-vscode"
  },
}

When using languages like svelte, pug, twig, or when using other prettier plugins like prettier-plugin-organize-attributes or prettier-plugin-organize-imports be sure to follow the instructions in our plugin compatibility guide. Just make sure to use require calls for the plugins you're using instead of specifying the plugin name as a string.

Thanks everyone for the solutions you provivded (and h/t to @shinebayar-g for the research regarding npm vs pnpm)!
At this point, I'm going to close this issue because I'm not convinced that it's directly related to this plugin but an issue with Prettier, pnpm, and plugins in general — tho I do believe this is still a good issue to keep around for people who are searching for solutions to similar problems.

@thecrypticace Thanks for clearing up how we should use prettier.documentSelectors & editor.defaultFormatter that helped a ton.

I didn't have any luck getting this working in VSCode with the Prettier extension, even after following all the steps and changing my prettierrc to a prettier.config.js and using require and all that.  I reverted to just having a prettierrc without the require and it's working fine with my husky -> lint-stage -> prettier --write precommit hook so I guess that's good enough for me.  Hopefully something changes in the future that gets the extension working for me

@rory-orennia Thank yo so much, it worked. I was trying to make it work for weeks. It also works with Svelte now.

I am using prettier-plugin-tailwindcss v0.3.0 with Next.js and tsx files and it wasn't working for me when using yarn to install node_modules and add packages. Once I switched back to npm, it started to work...
I don't use any extra config files for this like .prettierrc (and similar) mentioned here.

@kikky7 npm suck, use pnpm.

i am working on nextjs typescript tailwindcss project and i want to use preetier plugin tailwindcss to make my code more pretty can anyone help me out to find the solution, i am using npm

I fixed it by rolling back the vscode prettier plugin version to v9.2.0. Hope this helps.

If someone ends here, but is using Astro, not Svelte:
.prettierrc.cjs or prettier.config.cjs
module.exports = {
  plugins: [require("prettier-plugin-tailwindcss")],
  overrides: [{ files: "*.astro", options: { parser: "astro" } }],
  // rest of your custom stuff
}

Like the users of this issue, I have a solution that works for AdonisJS users who use the Edge template, not Svelte
tested & work with : .prettierrc.cjs or prettier.config.cjs or prettier.config.js
tested & work with : Prettier v3
my own prettier.config.js :
module.exports = {
  useTabs: false,
  tailwindConfig: "./tailwind.config.js", // ⚠ Set it so you're sure to call up the Tailwind config in the right place.
  trailingComma: 'es5',
  semi: false,
  singleQuote: true,
  quoteProps: 'consistent',
  bracketSpacing: true,
  arrowParens: 'always',
  printWidth: 100,
  plugins: [
    'prettier-plugin-organize-imports',
    'prettier-plugin-organize-attributes',
    'prettier-plugin-packagejson',
    'prettier-plugin-tailwindcss',  // ⚠ Order is very important place Tailwind prettier plugin at the end
  ],
  overrides: [ // ⚠ If you are using edge you need also set this to add support for edge
    {
      files: '*.edge',
      options: {
        parser: 'html',
      },
    },
  ],
};

Don't forget to download VSCode Prettier Extension and add this settings inside your VSCode settings.json :
{
        ...
        "editor.formatOnSave": true,
  	"[edge]": {
		"editor.defaultFormatter": "esbenp.prettier-vscode"
	},
	"prettier.useEditorConfig": false,
	"prettier.documentSelectors": ["**/*.edge"],
}

here you'll find a Medium that explains how to add support for an extension that doesn't exist in Prettier. (Astra, Edge, Handlebars ...)

I solved this problem after creating .prettierrc file and adding this: { "plugins": ["prettier-plugin-tailwindcss"], "pluginSearchDirs": false }

THANK YOU!
This worked. adding the prettier.config.js does not work as suggested in the Tailwind plugin readme.

@pratyushtewari can you provide a reproduction for this?

If someone ends here, but is using Astro, not Svelte:
.prettierrc.cjs or prettier.config.cjs
module.exports = {
  plugins: [require("prettier-plugin-tailwindcss")],
  overrides: [{ files: "*.astro", options: { parser: "astro" } }],
  // rest of your custom stuff
}

Not sure if my setup is different or this it out of date but I also had to install and update prettier-plugin-astro (the astro vscode extension ships with and uses prettier by default making the config finicky, it only supports prettier v3 around version 11 of the astro plugin). I had another package which install an older version of the astro plugin by default and so I had to run:
npm install -D prettier-plugin-astro prettier-plugin-tailwindcss

to get the updated, v3 compatible, plugins and then updated my .prettierrc with the list to be:
{
  "tabWidth": 2,
  "useTabs": false,
  "bracketSameLine": true,
  "plugins": [
    "prettier-plugin-astro",
    "prettier-plugin-tailwindcss"
  ]
}

@pratyushtewari can you provide a reproduction for this?

Hi @thecrypticace  - my project is here: https://github.com/pratyushtewari/bbos-components , the prettier.config.js did not work for me but adding .prettierrc worked with the same content inside the config.
I think prettier is only looking for the .prettierrc  file.

@pratyushtewari Your project is "type": "module" by default which means your prettier config itself must also be.
The following Prettier config works in that case:
export default {
  "plugins": ["prettier-plugin-tailwindcss"],
}

@thecrypticace  - Thanks! this worked.
I am not fluent in ESM much. to me export default and module.exports seems to be the same. I will look for more info on that.
Thanks!

This still isn't working for me.

This still isn't working for me.

Yeah i have given up and use Headwind (VSCode extension) instead for class sorting

I solved this problem after creating .prettierrc file and adding this: { "plugins": ["prettier-plugin-tailwindcss"], "pluginSearchDirs": false }

this works

I solve this problem by adding  *.{jsx,html} into  Prettier: Document Selectors

Alright folks, here is the summary. I just spent a good couple of hours debugging this.  Thank you everyone who have commented so far. Specially ones that who mentioned renaming files to common js syntax, switching pnpm to npm etc.

Using .prettierrc - npm

{
	"useTabs": true,
	"singleQuote": true,
	"trailingComma": "none",
	"printWidth": 100,
	"plugins": ["prettier-plugin-svelte", "prettier-plugin-tailwindcss"],
	"pluginSearchDirs": false,
	"overrides": [{ "files": "*.svelte", "options": { "parser": "svelte" } }]
}

Works. I could keep Svelte for VS Code as my default formatter. Both Prettier & Svelte formatter did the same. I am not sure if there is any difference at all here. If anyone knows please let me know.

Using .prettierrc - pnpm

Surprisingly pnpm didn't work. I no longer see the Prettier as a formatter. Svelte for VS Code does format, but tailwind plugin doesn't work (If you look at the prettier logs, it doesn't do anything). As others said Format Document (Forced) actually works.

Using .prettierrc.cjs - npm

module.exports = {
  useTabs: false,
  singleQuote: true,
  trailingComma: 'none',
  printWidth: 100,
  plugins: [require('prettier-plugin-svelte'), require('prettier-plugin-tailwindcss')],
  pluginSearchDirs: false,
  overrides: [{ files: '*.svelte', options: { parser: 'svelte' } }]
};

Works, same as above.

Using .prettierrc.cjs - pnpm
I don't see Prettier as a formatter. It was disabled in the corner like previously. But default formatter Svelte for VS Code picked up a tailwind plugin this time and actually worked.

Looks like something is wrong with pnpm x prettier setup. ~Also no need to mess with "prettier.documentSelectors": ["**/*.svelte"] .~
TLDR; if you're using pnpm make sure you're using .prettierrc.cjs
Yup found it prettier/prettier#9167 or pnpm/pnpm#4700

For folks using pnpm:
After adding prettier-plugin-tailwindcss to the last line of plugins (See doc) I can format the tailwind className string by command prettier --write . but VS Code doesn't format the file on save.
Then I change the config file name to .prettierrc.cjs, it works.
So my final config file is like:
module.exports = {
  plugins: [
    "prettier-plugin-packagejson",
    "@trivago/prettier-plugin-sort-imports",
    "prettier-plugin-prisma",
    "prettier-plugin-tailwindcss",
  ],
  pluginSearchDirs: false,
  importOrder: [
    "server-only",
    "^@([^/]+)(.*)/?(.*)$",
    "^@/(.*)/?(.*)$",
    "^[./]",
  ],
  // importOrderSeparation: true,
  importOrderSortSpecifiers: true,
  importOrderGroupNamespaceSpecifiers: true,
};

To others facing issues, restarting VS Code can help. Especially if you've changed a config and seen no impact.

This fixed the issue for me. .prettierrc
{
  "pluginSearchDirs": ["."],
  "overrides": [{ "files": "*.svelte", "options": { "parser": "svelte" } }],
  "plugins": ["prettier-plugin-svelte", "prettier-plugin-tailwindcss"]
}

.vscode/settings.json
{
  "prettier.requireConfig": true,
  "prettier.documentSelectors": ["**/*.svelte"],
  "[svelte]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode",
  }
}

100% works

Using require.resolve() instead of require() in .prettierrc.cjs worked for me.


Fix time format in filenames

Changed 15:07:47 to 15_07_47 in test_2016-01-27***.png files to fix fetch failed error on GitHub Desktop, since file names containing a colon : would be illegal on Windows.
Changed time formats in file names in utils.visualize.save_images for the same reason.

Any plans on merging this?

Thanks for the PR.


Suggestion: add -tags flag to support build tags

Hello,
At the moment there's no way to specify build tags when running golint. When running on specific files this is no problem (it will lint whatever file is specified), but that would be very useful when linting packages. Otherwise it silently ignores the files in the package that are not loaded due to a missing build tag.
I'd suggest adding a command-line flag called -tags, the same as for the go build flag, that would take a space-separated list of tags to define.
AFAICS, the only change required is in golint/golint.go, to set the specified build tags on a custom build.Context struct and use that context to import code (could even be set directly on build.Default as this is a command-line tool, doesn't impact anything else).
Let me know if that would be a welcome change, happy to provide a PR if that is the case.
Thanks,
Martin

I would really like to see this change. Without it, I'm not able to see any errors in my integration tests that are setup with // +build integration unless I actually try to run them. If we had -tags support for golint, I would be able to set the build tags and view the errors in real time in my editor.


Falco can't load BPF probe in GKE

Im using falcosecurity/falco:latest and the env

name: BPF_PROBE
value: ""
- name: FALCO_BPF_PROBE
value: "/root/.falco/falco-probe-bpf.o"

the pods crash with the errors:
Found kernel config at /proc/config.gz

Trying to download precompiled module from https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/falco-probe-latest-x86_64-4.19.102%2B-e0d915406c87215c571075f54ded2193.ko
curl: (22) The requested URL returned error: 404 Not Found
Download failed, consider compiling your own falco-probe and loading it or getting in touch with the Falco community
Mon Apr  6 16:27:03 2020: Falco initialized with configuration file /etc/falco/falco.yaml
Mon Apr  6 16:27:03 2020: Loading rules from file /etc/falco/falco_rules.yaml:
Mon Apr  6 16:27:04 2020: Loading rules from file /etc/falco/falco_rules.local.yaml:
Mon Apr  6 16:27:05 2020: Unable to load the driver. Exiting.
Mon Apr  6 16:27:05 2020: Runtime error: error opening device /dev/falco0. Make sure you have root credentials and that the falco-probe module is loaded.. Exiting.

@degilq: There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/area kernel-module

I'm on GKE and using the helm stable charts. I can't run falco 0.19, 0.20 or 0.21. Running 0.18 seems to work.
My error looks very similar.
* Setting up /usr/src links from host
* Mounting debugfs
Found kernel config at /proc/config.gz
* COS detected (build 12371.183.0), using cos kernel headers...
* Downloading https://storage.googleapis.com/cos-tools/12371.183.0/kernel-headers.tgz
* Extracting kernel sources
* Configuring kernel
* Trying to compile BPF probe falco-probe-bpf (falco-probe-bpf-latest-x86_64-4.19.104+-5ca6046631d128fd348208cbca9c777a.o)
make: *** /usr/src/falco-latest/bpf: No such file or directory.  Stop.
mv: cannot stat '/usr/src/falco-latest/bpf/probe.o': No such file or directory
* Trying to download precompiled BPF probe from https://s3.amazonaws.com/download.draios.com/stable/sysdig-probe-binaries/falco-probe-bpf-latest-x86_64-4.19.104%2B-5ca6046631d128fd348208cbca9c777a.o
curl: (22) The requested URL returned error: 404 Not Found
* Failure to find a BPF probe
Wed Apr  8 15:24:28 2020: Falco initialized with configuration file /etc/falco/falco.yaml
Wed Apr  8 15:24:28 2020: Loading rules from file /etc/falco/falco_rules.yaml:
Wed Apr  8 15:24:29 2020: Loading rules from file /etc/falco/falco_rules.local.yaml:
Wed Apr  8 15:24:30 2020: Unable to load the driver. Exiting.
Wed Apr  8 15:24:30 2020: Runtime error: can't open BPF probe '/root/.falco/falco-probe-bpf.o': Errno 2. Exiting.

Using an older version works.
helm install falco stable/falco --set ebpf.enabled=true --version 1.1.0
I also tried using the falco-daemonset-configmap-slim hoping that it would build the probe, but no such luck.

For me worked using master instead of 0.19/0.20/0.21.
I hope it helps

Yup, @degilq can you please try running it using the Falco master?

@leodido dunno about @degilq but can confirm swapping to the master that was just pushed to dockerhub solved this issue for me

So I'll call it a day and close this issue, thanks for reporting falcosecurity/falco:master is working!
In ~2 weeks we'll release a stable version (0.22.0) from the master, too.
@degilq feel free to file new issues if you have other problems. Thanks :)
/close

@leodido: Closing this issue.

In response to this:

So I'll call it a day and close this issue, thanks for reporting falcosecurity/falco:master is working!
In ~2 weeks we'll release a stable version (0.22.0) from the master, too.
@degilq feel free to file new issues if you have other problems. Thanks :)
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

I faced the same issue, I can confirm that master works, but only the full version, the minimal one doesn't.


Cannot exclude files during terraform module publish

Describe the bug
Using following command to publish a terraform module and want to exclude .git and .github directories. Published module zip file contains the excluded directories.
jf terraform publish --namespace consensys --provider azurerm --tag 'v0.0.8' --exclusions "\*.git\*"
Tried different options --exclusions '.git;.github' and none seems to be working.
I can see DEBUG logs indicate it ignored .git directory but it is still included.
09:30:50 [Debug] Sending HTTP GET request to: https://consensys.jfrog.io/artifactory/api/system/version
09:30:50 [Debug] The path '/Users/***/github/***/***/.DS_Store' is excluded
09:30:50 [Debug] The path '/Users/***/github/***/***/.git' is excluded

Following instruction in https://docs.jfrog-applications.jfrog.io/jfrog-applications/jfrog-cli/cli-for-jfrog-artifactory/package-managers-integration#terraform-publish example 2
Current behavior
Cannot exclude files using --exclusions when publishing terraform module
Reproduction steps

Create a simple terraform module in a git repository and run following command to exclude the .git folder jf terraform publish --namespace consensys --provider azurerm --tag 'v0.0.8' --exclusions "\*.git\*"
Check the zip file content in Artifactory portal and .git folder is included in the zip file

Expected behavior
Any file, directory added in --exclusions argument must be excluded from the zip file uploaded to Artifactory
JFrog CLI version
jf version 2.56.0
Operating system type and version
OSX
JFrog Artifactory version
Cloud
JFrog Xray version
No response

Having the same issue.  Trying to eclude .git, .github, .terraform.  The only thing that works is using , which, in our use case, excludes things we intend to keep in a couple of cases

Same issue here - my intended workaround is to use rsync to copy the directory to somewhere else but excluding the files I don't want, and then using jf to upload the temporary directory which has already been sanitised. But this is a frustrating bug, especially since the documentation states explicitly that this is possible in the last paragraph.


fix: in search results, change header based on content

Summary of Changes
When searching, ResourceListItem uses per-resource content classes to sub in the content columns. Thus the header columns need to vary based on the content as well.
Solve that by having the parent of ResourceListHeader pass in the types of the current content, and have ResourceListHeader swap out labels based on ResourceType
It's a bit smelly to me to have a fan-out based on ResourceType here. Perhaps ideally Resource would have a columnLabel method, and DashboardResource would override that to show the correct label (same for other subclasses of Resources). however AFAICT DashboardResource is just an interface, not an object, so I don't know that that's possible. Definitely looking for a better way to do this, this certainly works and isn't horrific, but it is a bit fragile. I've defaulted to just show BADGES (as before) so that if a new resource type is added, a label will be shown by default. If there are multiple different resource types passed in, we'll just display a blank column header.
Tests
I don't know how to test this behavior, but would be happy to add test if pointed to a somewhat-similar example.
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes, including screenshots of any UI changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public python functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes all tests documented in the developer guide

If LGTY'all, could someone merge? thanks!


Add support for sampler settings

Added basic Temperature and Top_P sampler settings to be passed to the LLM  (important for some models, Yi models are basically unusable with default 1.0)
Made MAX_COMPLETION_TOKENS a dotenv variable
Updated .env-example to reflect these changes.
Updated readme.md to reflect these changes

Great suggestions, thanks!


M04-LAB07 Controlling Deployments using Classic Release Gates - problem when deploying eshoponweb new code

Contact Details
No response
What happened?
Exercise 3: Configure the release pipeline
Task 1: Set Up Release Tasks
Step: Switch to the Azure portal interface, navigate to the resource group az400m04l09-RG, in the list of resources, click the DevTest web app, on the web app blade, click Browse, and verify that the web page (E-commerce website) loads successfully in a new web browser tab.
Description of issue:
the code of the e-SohopOnWeb application has been updated and when we deploy in a web app there is always the following error, does anyone have this same problem, below is a screenshot, this blocks the rest of the lab and the other labs too since it is always the same code to deploy
thanks
Below is a screenshot.
Lab
Control Deployments using Release Gates
Relevant screenshots

Do you want to help us? 👏

[ ] Create a Pull Request by following this project's Contribution Guide

@LuizMacedo since the last merge, deployment is no longer done correctly in Azure webapps, this is also valid for lab 16 thanks

Thanks @jajjaf I'm checking it and I'll fix as soon as possible. Apparently not something with AZ-400 labs but the eShopOnWeb update.

Thanks @jajjaf. I'm on it and I'll fix as soon as possible.

It's fixed. Issue was the old bicep folder path in the .yml files from the .ado folder.

@LuizMacedo
Thank you, even with the modified Bicep path there is an application problem, when it is pushed to a web app it still displays the same error message.
THANKS

Interesting. Let me reopen the issue so I can dig deeper. Thanks.

@LuizMacedo it may be a configuration problem or migration to version 8 of dotnet, and it's the same thing for a few other Labs. Thanks

@LuizMacedo @yashints Thank you for your quick interaction
I tested with the new version of the code that you recently merged,  the eshoponweb application once deployed in the web still displays the same error message the rest of the labs are blocked

@LuizMacedo yes, absolutely I redeployed with the new still the same error

@LuizMacedo @yashints  yes absolutely I redeployed with the latest version still the same error

Hello I test the lab 16 today and I can confirm that I have the same issue mentioned by @jajjaf

Thanks @jajjaf @sofiing1985 I'll try to check it today. The last update from @yashints should have resolved the issue. I'll check what else is missing.

Currently, I cannot reproduce the error when I have the latest Eshop and the latest instruction set.
Make sure you are seeing Exercise 3 Task 1 Step 14
"Open the Application and Configuration Settings pane and enter -UseOnlyInMemoryDatabase true -ASPNETCORE_ENVIRONMENT Development in the App settings box."

@jajjaf @sofiing1985 please, let us know if it works following @rob-foulkrod suggestion. Thanks!


Searchable combo box dark text while editing

Hey, think I found one last issue hehe. We have a lot of searchable Combo Boxes and the text when you are inputting is really dark. Pics here:
https://imgur.com/a/T0ygwmA
https://imgur.com/a/Z2fX4xg
Using standard combo boxes with following enabled ...

… and the ComboBox.ItemsSource is bound to a List.

Wait hmmm this sounded familiar. Looks like you closed out an issue for the same thing earlier. Did it get undone somehow? =(
https://github.com/AngryCarrot789/CoolDarkThemeThingy/issues/2

Also just to make sure I re-downloaded the zipped source again just now. Pretty sure I have the latest.

I think I already fixed this before. if it broke again, I'll try and fix it
(might have left out a few lines of code) in a few hours or so (out atm)
On Tue, 10 Mar 2020, 03:03 Shmoopy02<EMAIL_ADDRESS>wrote:

Also just to make sure I re-downloaded the zipped source again just now.
Pretty sure I have the latest.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AngryCarrot789/CoolDarkThemeThingy/issues/4?email_source=notifications&email_token=AHWHPZE5U2QNDODQAXZYLETRGW3ZJA5CNFSM4LEVXFK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEOJ2BNA#issuecomment-596877492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWHPZEKF5JAXHKSFCY7ESTRGW3ZJANCNFSM4LEVXFKQ
.

long delay soz, but i think i fixed it
somehow the code from when i set the Foreground in the editable style had just vanished... strange.
but it seems to work now.

Looks good!


Cross the terabyte threshold

We already have users in the wild storing and processing terabyte sized workloads, we'd like to have automated tests for this and learn about which workloads work at this scale and which still have issues.

We've also seen individual jobs emit 1TB of net new data. (Another data point for testing considerations).

stale


Is there functionality to de-commission all resources?

Just wondering, with all of these resources being provisioned, is there some script to de-provision all of these?

Woops. Didn't read the README...
To remove all of the resources that were deployed on the deploy script run the
following command:

```bash
npm run destroy

Note: Unless you changed the related configuration values, running this script
will delete everything deployed by this template including your minecraft server
data.
Alternatively, you can delete the minecraft-server-stack first, then the
minecraft-domain-stack from the AWS Console.


Button group signal "pressed" not triggered

Godot version
v3.5.stable.official [991bb6ac7]
System information
Windows 11, GLES3
Issue description
Button group signal "pressed" cannot be triggered when any button in the group is pressed.
Steps to reproduce
Add some buttons to a button group, connect the "pressed" signal, click any button in the group.
Minimal reproduction project
Uploading ButtonGroupSignal.zip…

What's wrong with Github? I can't upload the test project even when I'm on another computer.

I'd guess your buttons are not toggleable? Seems like ButtonGroup works only for toggleable buttons:
https://github.com/godotengine/godot/blob/35cfaafda8073f700c9d2fe42a43d3d81eaaea67/doc/classes/ButtonGroup.xml#L6-L9
I guess this signal should be called something like toggled_on in the first place to avoid confusion... or just toggled and be also emitted for the button being toggled off. But this can't be changed in 3.x, it would break compatibility. However maybe ButtonGroup could be changed/improved in 4.0? :thinking:

@kleonc You're right. Making all member buttons togglable does work. Is there any reason for all member buttons to be togglable? I don't see an obvious reason for this limitation.

Is there any reason for all member buttons to be togglable?

I can be only guessing, seems like it was simply made specifically for radio buttons (only one button in a group can be pressed at once).

I don't see an obvious reason for this limitation.

Same, it's rather a design choice. I think potential changes are a subject for a proposal though. ButtonGroup seems to work as intended (whether we like it or not).

This is already documented.

Group of [Button]. All direct and indirect children buttons become radios. Only one allows being pressed.[member [BaseButton.toggle_mode] should be [code]true[/code].


[Debug] Improve keyword highlighting and escaping of query strings.

Description
~This PR adds a few more composite query keywords to the highlight list for the debug toolbar.~
~I also decided to sort the keywords alphabetically, as it was a pain checking which ones are missing. (This is debatable of course.)~

Deconstruct composite keywords.
Sort kewords alphabetically.
Modify regex pattern to ignore kewords within escaped string values ('').
[WIP] Add HTML escaping.

Depends on #5196.
Checklist:

[x] Securely signed commits
[x] Conforms to style guide

Before:

After:

The escaping way looks good to me.

The esc() or htmlspecialchars() way?


ProjectFile has a None option

This was a little funny:
ProjectFile keywords to customize:
[press: d=done, a=all, n=none]
   [X] version
 > [X] None

With both selected, the None option seemed to win.   Seems like this None option should be removed.

It's an implementation detail of TerminalMenus, you can't create a menu with just one entry. 🙁

Ah, that's unfortunate.  Perhaps this should be an upstream issue?  Seems like a 1-element menu should make sense and be easy to support.
cf. https://github.com/JuliaLang/julia/pull/35915#issuecomment-638316817

Yeah, I agree. Tbh we're probably better off using the non-stdlib version because the stdlib will never backport these kinds of changes to 1.0.

FYI, single option menu for REPL.TerminalMenus just got merged (likely available with Julia 1.6+): JuliaLang/julia#36369

I think some people have said that 1.6 has potential to be the next LTS, so when that comes we can make the change 🙂


Fix typos in README/help message

Note that the install instructions for working with STIX 1.1.1 content
didn't work without the quotes - the shell interpreted  '<' as input
redirection.

I'll fix the style issues.  Thanks for finding the typo.


ks prototype use accepts qualified components with slash separator only

ks prototype use currently requires qualified component names (including their module) to use / separators. Using . is rejected with an error that does not indicate the cause or how to resolve.
Rejected:
$ ks prototype use namespace apps.ksonnet.namespace --name ksonnet
ERROR 2:58-59 Expected token IDENTIFIER but got (";", ";")

Accepted
$ ks prototype use namespace apps/ksonnet/namespace --name ksonnet
INFO Writing component at '.../components/apps/ksonnet/namespace.jsonnet'

Goals

We should perform validation on qualified components and produce a more contextual error if an invalid component name is provided by the user.
If the rest of ksonnet is using dot separators, we should align ks prototype with that convention

A single dot separator is accepted in the current implementation, but not a deeper module hierarchy.

@shomron Should this go into 0.12?


changed css

Looks like you have change a lot more than css, 127 files... including python. Did you accidentally push all files in a directory? 😊


Installation following virtualenvwrapper instructions fails

Performed the following:
Updated to current virtualenv        16.0.0
Updated to current virutalenvwrapper 4.8.2
mkvirtualenv wagtailbakerydemo
Changed to my dev directory ~/wagtail
cd bakerydemo/
git clone https://github.com/wagtail/bakerydemo.git
pip install -r requirements.txt
Installing requirements failed with the following exception:
Collecting Django<2.1,>=2.0 (from -r requirements/base.txt (line 1))
Could not find a version that satisfies the requirement Django<2.1,>=2.0 (from -r requirements/base.txt (line 1)) (from versions: 1.1.3, 1.1.4, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.3.7, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 1.4.14, 1.4.15, 1.4.16, 1.4.17, 1.4.18, 1.4.19, 1.4.20, 1.4.21, 1.4.22, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.5.7, 1.5.8, 1.5.9, 1.5.10, 1.5.11, 1.5.12, 1.6, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5, 1.6.6, 1.6.7, 1.6.8, 1.6.9, 1.6.10, 1.6.11, 1.7, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, 1.7.9, 1.7.10, 1.7.11, 1.8a1, 1.8b1, 1.8b2, 1.8rc1, 1.8, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 1.8.7, 1.8.8, 1.8.9, 1.8.10, 1.8.11, 1.8.12, 1.8.13, 1.8.14, 1.8.15, 1.8.16, 1.8.17, 1.8.18, 1.8.19, 1.9a1, 1.9b1, 1.9rc1, 1.9rc2, 1.9, 1.9.1, 1.9.2, 1.9.3, 1.9.4, 1.9.5, 1.9.6, 1.9.7, 1.9.8, 1.9.9, 1.9.10, 1.9.11, 1.9.12, 1.9.13, 1.10a1, 1.10b1, 1.10rc1, 1.10, 1.10.1, 1.10.2, 1.10.3, 1.10.4, 1.10.5, 1.10.6, 1.10.7, 1.10.8, 1.11a1, 1.11b1, 1.11rc1, 1.11, 1.11.1, 1.11.2, 1.11.3, 1.11.4, 1.11.5, 1.11.6, 1.11.7, 1.11.8, 1.11.9, 1.11.10, 1.11.11, 1.11.12, 1.11.13, 1.11.14, 1.11.15)
No matching distribution found for Django<2.1,>=2.0 (from -r requirements/base.txt (line 1))

Discovered Django 2.x is not supported using Python 2.x.
Did the following:
pip3 install -r requirements.txt
And this worked to install a number of the required packages before it failed on psycopg2 which I will research and, if necessary, open a separate issue.
As for the documentation for performing the virtualenv installation, I think this should be updated/clarified.

Thanks for the report @tsgood77! I've now updated the virtualenv setup instructions (in #221) to address these issues, and the Python 3.7 compatibility issues have been dealt with in #222 (although we now skip awscli anyway by using requirements/base.txt rather than production.txt - it's only required for Heroku deployments). Python 3.7 isn't listed in the 'dependencies' section because we won't officially support it until Wagtail 2.4, but it should still work.


Add OAI image builder

Add OAI image builder which I used. The Helm chart for OAI will follow on the sdran-helm-charts repo.

The image size is too big; I will optimize it.


Update billing.md

Little tweaks to billing page

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Flutter Doctor: Connected device (the doctor check crashed)... Exception: Unable to run "adb" ...

Steps to reproduce

I connect the device via USB to the computer.

I run the command flutter doctor -v

The command gives an error: "Connected device (the doctor check crashed)... Exception: Unable to run "adb" ..."

Actual results
When the device is connected via USB, the command flutter doctor -v produces the following error:
[☠] Connected device (the doctor check crashed)
    X Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
    X Exception: Unable to run "adb", check your Android SDK installation and ANDROID_SDK_ROOT environment variable: D:\ProgramData\Android\Sdk\platform-tools\adb.exe

This error began to appear after updating flutter from version 3.13.6 to version 3.16.9.
But after rolling back to flutter version 3.13.6, this problem did not disappear.
In addition, the device was no longer recognized in Android Studio, although everything worked fine before the flutter update.
Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output

[√] Flutter (Channel stable, 3.13.6, on Microsoft Windows [Version 6.1.7601], locale ru-RU)
    • Flutter version 3.13.6 on channel stable at D:\ProgramData\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ead455963c (4 months ago), 2023-09-26 18:28:17 -0700
    • Engine revision a794cf2681
    • Dart version 3.1.3
    • DevTools version 2.25.0

[X] Windows Version (Unable to determine Windows version (command `ver` returned Microsoft Windows [Version 6.1.7601]))

[√] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at D:\ProgramData\Android\Sdk
    • Platform android-33, build-tools 33.0.1
    • ANDROID_HOME = D:/ProgramData/Android/Sdk
    • Java binary at: D:\ProgramData\Android\Android Studio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop Windows apps (Visual Studio Community 2019 16.11.9)
    • Visual Studio at D:\ProgramData\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.11.32106.194
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2022.1)
    • Android Studio at D:\ProgramData\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = D:\ProgramData\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)

[☠] Connected device (the doctor check crashed)
    X Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
    X Exception: Unable to run "adb", check your Android SDK installation and ANDROID_SDK_ROOT environment variable: D:\ProgramData\Android\Sdk\platform-tools\adb.exe
    • #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
      #1      AndroidDevices.pollingGetDevices (package:flutter_tools/src/android/android_device_discovery.dart:75:7)
      <asynchronous suspension>
      #2      PollingDeviceDiscovery._populateDevices (package:flutter_tools/src/device.dart:563:36)
      <asynchronous suspension>
      #3      Future.wait.<anonymous closure> (dart:async/future.dart:525:21)
      <asynchronous suspension>
      #4      DeviceManager.refreshAllDevices (package:flutter_tools/src/device.dart:231:40)
      <asynchronous suspension>
      #5      DeviceValidator.validate (package:flutter_tools/src/doctor.dart:690:34)
      <asynchronous suspension>
      #6      Future.any.onValue (dart:async/future.dart:615:5)
      <asynchronous suspension>

[√] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

@Rudentsov
Do you have any anti-virus that might be blocking adb ?

@Rudentsov Do you have any anti-virus that might be blocking adb ?

Hello. No, there are no antivirus programs on the device. There are also no antivirus programs on the computer, except for the native firewall. In the native Windows firewall, adb is allowed.
The only thing is that the computer is now connected to another Wi-Fi router (“Keenetic Start”), previously it was connected to the “DrayTek VigorFly 200”. But the router does not have any antivirus software or blocking software.

I noticed this:
When the device is not connected to USB, the result of the command adb devices is as follows:
C:\Users\User>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached

And when the device is connected to USB, the result of executing the command adb devices is as follows - an error occurs and adb.exe starts and ends immediately:
C:\Users\User>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
error: protocol fault (couldn't read status): Connection reset by peer

I tried to use the Android Studio utility "Menu / Tools / Troubleshoot Device Connections". The result of scanning devices is as follows (device found - Lenovo TAB4 10):

USB debugging is allowed:

But restarting the adb server results in the error "Unable to locate ADB.":

I tried the following commands:
C:\Users\User>set ADB_TRACE=all

C:\Users\User>adb devices
02-07 16:19:42.018  7660  1924 D adb     : adb_trace.cpp:187 Android Debug Bridge version 1.0.41
02-07 16:19:42.018  7660  1924 D adb     : adb_trace.cpp:187 Version 34.0.5-10900879
02-07 16:19:42.018  7660  1924 D adb     : adb_trace.cpp:187 Installed as D:\ProgramData\Android\Sdk\platform-tools\adb.exe
02-07 16:19:42.018  7660  1924 D adb     : adb_trace.cpp:187 Running on Windows 6.1.7601
02-07 16:19:42.018  7660  1924 D adb     : adb_trace.cpp:187
02-07 16:19:42.018  7660  1924 D adb     : adb_client.cpp:160 _adb_connect: host:version
02-07 16:19:43.030  7660  1924 D adb     : sysdeps_win32.cpp:1032 could not connect to tcp:5037: cannot connect to <IP_ADDRESS>:5037: ╨Я╨╛╨┤╨║╨╗╤О╤З╨╡╨╜╨╕╨╡ ╨╜╨╡ ╤
Г╤Б╤В╨░╨╜╨╛╨▓╨╗╨╡╨╜╨╛, ╤В.╨║. ╨║╨╛╨╜╨╡╤З╨╜╤Л╨╣ ╨║╨╛╨╝╨┐╤М╤О╤В╨╡╤А ╨╛╤В╨▓╨╡╤А╨│ ╨╖╨░╨┐╤А╨╛╤Б ╨╜╨░ ╨┐╨╛╨┤╨║╨╗╤О╤З╨╡╨╜╨╕╨╡. (10061)
02-07 16:19:43.030  7660  1924 D adb     : sysdeps_win32.cpp:602 _socket_set_errno: mapping Windows error code 10061 to errno 22
* daemon not running; starting now at tcp:5037
02-07 16:19:43.060  7044  6496 D adb     : adb_trace.cpp:187 Android Debug Bridge version 1.0.41
02-07 16:19:43.060  7044  6496 D adb     : adb_trace.cpp:187 Version 34.0.5-10900879
02-07 16:19:43.060  7044  6496 D adb     : adb_trace.cpp:187 Installed as D:\ProgramData\Android\Sdk\platform-tools\adb.exe
02-07 16:19:43.060  7044  6496 D adb     : adb_trace.cpp:187 Running on Windows 6.1.7601
02-07 16:19:43.060  7044  6496 D adb     : adb_trace.cpp:187
* daemon started successfully
02-07 16:20:04.561  7660  1924 D adb     : sysdeps_win32.cpp:151 _fh_from_int: invalid fd -2 passed to adb_close
List of devices attached
02-07 16:20:04.561  7660  1924 D adb     : adb_client.cpp:400 adb_query: host:devices
02-07 16:20:04.561  7660  1924 D adb     : adb_client.cpp:358 adb_connect: service: host:devices
02-07 16:20:04.561  7660  1924 D adb     : adb_client.cpp:160 _adb_connect: host:devices
02-07 16:20:04.561  7660  1924 D adb     : sysdeps_win32.cpp:1040 port 5037 type tcp => fd 2048
02-07 16:20:04.561  7660  1924 D adb     : adb_io.cpp:107 writex: fd=2048 len=16<PHONE_NUMBER>6f73743a64657669636573 000chost:devices
02-07 16:20:04.561  7660  1924 D adb     : adb_io.cpp:81 readx: fd=2048 wanted=4
02-07 16:20:04.571  7660  1924 D adb     : sysdeps_win32.cpp:689 recv fd 2048 failed: ╨г╨┤╨░╨╗╨╡╨╜╨╜╤Л╨╣ ╤Е╨╛╤Б╤В ╨┐╤А╨╕╨╜╤Г╨┤╨╕╤В╨╡╨╗╤М╨╜╨╛ ╤А╨░╨╖╨╛╤А╨▓╨░╨╗ ╤Б
╤Г╤Й╨╡╤Б╤В╨▓╤Г╤О╤Й╨╡╨╡ ╨┐╨╛╨┤╨║╨╗╤О╤З╨╡╨╜╨╕╨╡. (10054)
02-07 16:20:04.571  7660  1924 D adb     : adb_io.cpp:88 readx: fd=2048 error 108: Connection reset by peer
02-07 16:20:04.571  7660  1924 D adb     : sysdeps_win32.cpp:537 adb_close: 2048(lo-client:5037)
02-07 16:20:04.571  7660  1924 D adb     : adb_client.cpp:372 _adb_connect error: protocol fault (couldn't read status): Connection reset by peer
02-07 16:20:04.571  7660  1924 D adb     : adb_client.cpp:376 adb_connect: return fd -1
error: protocol fault (couldn't read status): Connection reset by peer

After searching for various options, the cause of the error was found.
Android SDK Platform-Tools version 34.0.5 is incompatible with my configuration Android Studio (Electric Eel | 2022.1.1 Patch 1) or SDK Developer Tools.
After the rollback on the Android SDK Platform-Tools version 34.0.4, the error disappeared - the device connected to the USB is recognized in Android Studio and Flutter.
The problem is solved.


CAMEL-20560 - Camel-AWS-Bedrock: Support Anthropic models

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

/component-test aws


Enable setting transport_protocols

@mbautin

@tas50 Can you take a look at this the CLA is signed?

Removed version number bump.

@tas50 when you get a chance can you review this PR? thanks

I'm off today, but I was going to fire up Test Kitchen on monday

@tas50 Looks like Travis CI ran Test Kitchen for this PR, this should be ready for review again.

How does this look now?

Looks good to me, FWIW.

@tas50 This should be ready for review when you get a chance, thanks


Marked ConfigurationItemFactory.CreateInstance obsolete #5191: No documented alterative approach.

In 5.2 some of the configuration methods were made obsolete, without providing a documented alternative approach.
I have code that does the following:
    private static void LoadConfiguration(JsonNode jsonNode, LogFactory logFactory)
    {
        // it is, let's get the common config folder.
        if (!jsonNode.GetNodeValue("CommonConfigFolder", out string commonConfigFolder))
            return;

        // does the folder exist?
        if (!Directory.Exists(commonConfigFolder))
            throw new DirectoryNotFoundException(
                $"The specified common config folder {commonConfigFolder} was not found.");

        // let's update the places NLog looks for it's configuration file.
        var currentFilePaths = logFactory.GetCandidateConfigFilePaths().ToList();

        // add the common config file location.
        currentFilePaths.Add(Path.Combine(commonConfigFolder, "nlog.config"));

        // reset the config paths.
        logFactory.ResetCandidateConfigFilePath();
        logFactory.SetCandidateConfigFilePaths(currentFilePaths);
    }

The GetCandidateConfigFilePaths(), ResetCandidateConfigFilePath(), and SetCandiadateConfigFilePaths() are now marked as obsolute.
I was using these methods to add an additional location for NLog to search for the nlog.config file.  Since I'm building a library that will be used to bootstrap the development of .NET 7 services that can run on multiple OS platforms, I am leaving the location of the NLog.Config file up to the implementor. I just need to add an additional location to be searched.
While I can use the new LogFactory.Setup().LoadConfigurationFromFile() method and pass the a new location, it will then expect to load the file from that location.
For example, a group of services that are designed as a processing pipeline might have a common configuration folder as they share a significant group of settings, while a standalone service will have the configuration information in the application's folder.
Having a common configuration folder, doesn't prevent the implementor from placing the NLog.Config file in the application's folder.  If I need to change logging on one specific instance, I can just drop an updated NLog.Config in the application folder, while all the other services in the group would use the common NLog.Config file.
How can I add a new location to be searched, while still allowing the default locations to be searched?
Thank you.
-marc

Was thinking one could LogManger.Setup().LoadConfigurationFromFile() and chain them together:
LogManger.Setup()
         .LoadConfigurationFromFile()
         .LoadConfigurationFromFile(Path.Combine(commonConfigFolder, "nlog.config")); // extra fallback

LoadConfigurationFromFile has the parameter optional that is true by default, and configuration is already loaded then it will skip config-loading.

Thank you. I will give that a try.

Closing as resolved, due to inactivity.


how to use this in my VR scene based on WebXR

Hi @oxters168.
This is an amazing project. Can I use this in my VR scene based on aframe?

Thank you! My hand physics solution is built on Unity and it looks like A-Frame is not something that is used with Unity. So out of the box it does not seem like it would work. Feel free to port it over if you'd like though.


Added more inequality predicates

Signed-off-by: Michael Lodder<EMAIL_ADDRESS>

Any idea when this would be merged and when could we use it in Indy SDK?

Talk to the maintainers. I’m hoping not too long.

I will ask on the Slack channel! Thanks! :smile:

They are internal. Indy-SDK would not see any of this.
@mikelodder7 @brentzundel Unfortunately it's not true. This PR contains breaking changes. And new master is incompatible with current stable.

@mikelodder7
IndySDK use ProofBuilder like
Prover::new_proof_builder();
...
.add_sub_proof_request
...
.finalize() -> Proof

then IndySDK serialize Proof as part of output JSON string for application. This string is used by Proover to present the proof for Verifier
pub struct Proof {
    proofs: Vec<SubProof>,
    aggregated_proof: AggregatedProof,
}
...
pub struct SubProof {
    primary_proof: PrimaryProof,
    non_revoc_proof: Option<NonRevocProof>
}
...
pub struct PrimaryProof {
    eq_proof: PrimaryEqualProof,
    ~ge_proofs: Vec<PrimaryPredicateGEProof>~ now changed to
    ne_proofs: Vec<PrimaryPredicateInequalityProof>
}

The easiest way may be to just "duplicate" ge_proofs field and add 3 new like gt_proofs, le_proofs and lt_proofs.
AFAIR design discussion there is an option to create new anoncreds type. Now it's "CL" but we can implement the new one. I don't like this option, as current changes is just extending existing implementation to fit math model.
we can try to introduce versioning here. E.g. append ver field and assume omitted as ver.0

@mikelodder7 please share your options too
@vimmerru have I forgotten smth from our discussions about versioning in IndyCrypto?

I vote for option 3,1,2 in that order. The problem occurs when deserializing in that in consumes the stream so you can only convert once. So what have you done before to handle this?


Use QueryComplexityCalculator from graphql-java

Switch to using QueryComplexityCalculator from graphql-java in DgsGraphQLMetricsInstrumentation. Additionally, eliminate some unnecessary usage of Optional.

I opened a new PR #1797 since the commit author was getting messed up on this one.


Is the order of the files in the *. config.d directory incorrect?

The following description is in usage:
https://github.com/Kotlin/kotlin-frontend-plugin/blob/22ef064c1c2fcf1a7859a451d0d82e57bbbd3825/README.md#L127-L128
I created files and tried it as follows:
webpack.config.d
    10-config-20.js
    20-config-10.js

In the generated webpack.config.js, it is written as follows:
// from file .../webpack.config.d/20-config-10.js
{
   "name": "20-config-10"
}
// from file .../webpack.config.d/10-config-20.js
{
   "name": "10-config-20"
}

Is the order incorrect? The order is not decided by prefix.
I am sorry if it is a misunderstanding. If the order is incorrect, I think that if we correct the following code it will be fixed.
https://github.com/Kotlin/kotlin-frontend-plugin/blob/22ef064c1c2fcf1a7859a451d0d82e57bbbd3825/kotlin-frontend/src/main/kotlin/org/jetbrains/kotlin/gradle/frontend/npm/GeneratePackagesJsonTask.kt#L115
https://github.com/Kotlin/kotlin-frontend-plugin/blob/22ef064c1c2fcf1a7859a451d0d82e57bbbd3825/kotlin-frontend/src/main/kotlin/org/jetbrains/kotlin/gradle/frontend/webpack/GenerateWebPackConfigTask.kt#L117

Fixed in 0.0.22, thanks!


Drag n Drop within a tree with keyboard support

I am thinking of using JSTree for a project I am currently working on. I have just been reading upon it and looking at samples for past couple of days and I see that this will work great for most functionalities required. Just a few questions since I have not seen any samples illustrating if such a thing can be done.
I need to be able to drag a node and drop it on another node but I need to control how the dropped node behaves:

when the node is dragged and dropped without any key being pressed I want the dropped node to be the last child of the target node.
when the node is dragged and dropped while the ctrl key is pressed I want the dropped node to be the previous sibling of the target node.
when the node is dragged and dropped while the shift key is pressed I want the dropped node to be the next sibling of the target node.

Can you give me some ideas about how I can do such a thing?

You can use the core.check_callback function and while monitoring for pressed keys prevent all other kinds of drops. When a node is dragged this function will be triggered 3 times - checking if the node can be dropped inside, before or after the target node - depending on your requirements return ```true' only for the valid drop. Keep in mind the function will be triggered in other cases too, so check if this is a move_node or copy_node operation.
Here are the docs:
https://www.jstree.com/api/#/?q=check&f=$.jstree.defaults.core.check_callback
You might want to set dnd.copy to false as well:
https://www.jstree.com/api/#/?q=dnd&f=$.jstree.defaults.dnd.copy


[RUST] Store manifest metadata out of protobuf

Giving that we could allow to store arbitrary size of metadata key-value stores in manifest protobuf. We should consider to move it out of the Manifest protobuf body.  So that for most of the query/scans, we don't need to pay the latency of reading large k/v pairs.

@eddyxu does this include dictionaries?

Dictionary is already out.
On Mon, Feb 13, 2023 at 9:43 PM Chang She @.***> wrote:

@eddyxu https://github.com/eddyxu does this include dictionaries?
—
Reply to this email directly, view it on GitHub
https://github.com/eto-ai/lance/issues/332#issuecomment-1429153103, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAEFSJFV755TXYXHZI4OLLWXMLQDANCNFSM6AAAAAASJ2VM2A
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Lei Xu
Eto Labs https://eto.ai | Calendly https://calendly.com/leixu/30min


Rename VhostUserSlave for clarity

Naming with slaves is getting confusing, try and rename.

Hmm, my one concern with this change is that VhostUserSlaveReqHandler now seems a bit out of place, since the "Slave" has been renamed to MasterReqHandler.
It might just be best to leave things as is, and to lean on the documentation to clarify what each trait implements.
Thoughts?

There's always confusion about vhost-user terms, master/slave vs client/server. When naming the interfaces, I follow the terms in vhost-user spec. How about still stick to terms used by the vhost-user spec?


Zend/Http/Request::renderRequestLine() does not take query parameters into account

This issue has been moved from the zendframework repository as part of the bug migration program as outlined here - http://framework.zend.com/blog/2016-04-11-issue-closures.html

Original Issue: https://api.github.com/repos/zendframework/zendframework/issues/7472
User: @afeder
Created On: 2015-04-30T16:03:58Z
Updated At: 2015-11-06T21:33:03Z
Body
The renderRequestLine() function of Zend/Http/Request counterintuitively does not include query parameters set via setQuery() in the request line it returns. Is this intentional or is it something for which a patch would likely be accepted?

Comment
User: @adamlundrigan
Created On: 2015-05-01T13:47:35Z
Updated At: 2015-05-01T13:47:35Z
Body
IMO, this is a bug.  Zend\Http\Request::renderRequestLine delegates the building of the URI to Zend\Uri\Uri::toString (unless Zend\Http\Request::$uri is a string, of course), but Zend\Http\Request::setQuery does not pass data through to the Uri object so the two fall out of sync.

This repository has been closed and moved to laminas/laminas-http; a new issue has been opened at https://github.com/laminas/laminas-http/issues/14.


fix: Resolve GKEPod pickup process for geos_fp dataset

Description
Dataset:
geos_fp
Pipelines:
copy_files_rolling_basis
Checklist

[x] (Required) This pull request is appropriately labeled
[x] Please merge this pull request after it's approved

Data Onboarding

[x] I'm editing a dataset
[x] The Google Cloud Datasets team is aware of the proposed dataset
[x] I put all my code inside  datasets/geos_fp and nothing outside of that directory

Code cleanup or refactoring

[x] I'm refactoring or cleaning up some code

@nlarge-google @adlersantos Kindly review this PR

Thanks for fixing this @vijay-google!


Add benchmarks with PyPy

Pure-python libraries might run faster on PyPy, and it worth it to include it for comparison

Done

Done


navbar-brand width is set to 155px vs 200px

Hi,
Following up on https://github.com/coreui/coreui-free-vue-admin-template/issues/154
When setting SidebarToggler to 'd-none', other items in header move to the left -- see attached. 'Dashboard' is no longer aligned with sidebar.
navbar-brand width is set to 155px vs 200px, to be same as the sidebar. Can't find how to overwrite this. If using !important, it breaks the mobile view.
We believe navbar-brand should be same as the sidebar (200px) and items inside it (img) centered.
Also, would be great if by default there would be no SidebarToggler in desktop-view. We already have the minify toggler in sidebar. There's no need to add more togglers just because it's possible.
Thanks

Hi! sidebar toggler on desktop view is a default feature of the CoreUI template. By default we don't have toggler inside the sidebar, so the header toggler is necessary. You can just delete it and wrap brand and mobile toggler in div with min-width.
In DefaultContainer.vue:
<AppHeader fixed>

    <SidebarToggler class="d-lg-none" display="md" mobile />

Hi, thanks for your help!
That solution doesn't work properly on mobile: sidebar toogle will take 200px instead of the small space it needs.
It would be great to have this fixed in coreui, somehow.
There's a toggler inside sidebar on desktop, which leaves only the icons. If you could measure the usage or ask users about the desktop toggler, I'm sure it's not that used. It could be left in code commented out.
The patters is visible on all sites navigation: on desktop they just show the menu, on mobile most have a menu toggler. NO site has a menu toggler on desktop, because it's not needed.

Thank you for your suggestions, we will consider it.
Did you wrap Toggler AND link with the brand in the div with min-width? It should work on mobile.

Thank you for your suggestions, we will consider it.
I just checked for possible solutions and code below works fine both on desktop and mobile, both with commented or not commented toggler in 2.1.5 version.

Thank you for your suggestions, we will consider it.
Now I think I see your problem. You are not talking about mobile view problem, but rather a problem with minimizing on desktop view. You can fix it this way:
<SidebarToggler class="d-md-down-none invisible"/>

We will also rethink the positioning, so it could be easier customed by users :)

Thank you!


Map Docker labels to appc annotations.

Given a Dockerfile:
FROM scratch
LABEL foo=bar
ADD emptyfile /

touch emptyfile
docker build -t grep/test .
docker save -o docker/test.docker grep/test
Exported docker manifest:
[
  {
    "Config": "02d28b56668b4dcd4f354b2799f65246378aa23e4f5e62db4d6eb7d8737beee9.json",
    "RepoTags": [
      "grep/test:latest"
    ],
    "Layers": [
      "0e664782202308a03920d0fe133f34e6d348e0cd2cf315c24d71a1c5d8b48f6f/layer.tar"
    ]
  }
]

cat 02d28b56668b4dcd4f354b2799f65246378aa23e4f5e62db4d6eb7d8737beee9.json | jq .config
{
  "Hostname": "9cfcce2510b1",
  "Domainname": "",
  "User": "",
  "AttachStdin": false,
  "AttachStdout": false,
  "AttachStderr": false,
  "Tty": false,
  "OpenStdin": false,
  "StdinOnce": false,
  "Env": [
    "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
  ],
  "Cmd": null,
  "Image": "sha256:dc7cef81fee136961f5302ddd013a29aaf0a3f04e0dfc2208ed8a53d34bacb8b",
  "Volumes": null,
  "WorkingDir": "",
  "Entrypoint": null,
  "OnBuild": null,
  "Labels": {
    "foo": "bar"
  }
}

docker2aci test.docker
tar xvf grep-test-latest.aci
cat manifest | jq .annotations
[
  {
    "name": "created",
    "value": "2016-10-06T20:34:17Z"
  },
  {
    "name": "appc.io/docker/repository",
    "value": "grep/test"
  },
  {
    "name": "appc.io/docker/imageid",
    "value": "0e664782202308a03920d0fe133f34e6d348e0cd2cf315c24d71a1c5d8b48f6f"
  },
  {
    "name": "foo",
    "value": "bar"
  }
]

I don't understand the nature of this semaphoreci build failure.

Semaphore was a flake it seems.
This looks okay to me but we probably need to deal with conflicts (e.g. what if a user has set labels that conflict with the ones docker2aci generates?)
@lucab thoughts?

I also have the same concern. I think one possible way out of this is:

define the list of our reserved prefixes. At the moment, these seem to be: created, docker-comment, author, authors, appc.io/docker/.
set out an additional schema-label prefix for ourself (io.appc.docker2aci?)
translate all conflicting and dot-free labels to annotations under our prefix (io.appc.docker2aci.labels?)
translate all non-conflicting and schema-label scoped entry to annotations, copied over 1:1
bonus: gradually start emitting our own generated annotations under our schema-label prefix

Am I missing some corner case?

I've a doubt, so I'm paging @squeed here. I know we have different kinds of annotations and labels now in appc/spec, which one should be used here?

GH seems to have eaten my comment - reposting:
I forgot to come back to this after the recent appc changes. I think we can potentially just put the docker labels directly into the new userLabels field - the only problem I see is if the CRI/dockershim expects something different (i.e. it mutates Docker labels instead of passing them through), but I doubt it?

I forgot to come back to this after the recent appc changes. I think we can
potentially just put the docker labels directly into the new userLabels
field - the only problem I see is if the CRI/dockershim expects something
different, but I doubt it?
On 27 October 2016 at 11:19, Luca Bruno<EMAIL_ADDRESS>wrote:

I've a doubt, so I'm paging @squeed https://github.com/squeed here. I
know we have different kinds of annotations and labels now in appc/spec,
which one should be used here?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/appc/docker2aci/pull/209#issuecomment-256590616, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACewNwTat1HZS_3B_8pzup9ogKcOUaxUks5q4GyugaJpZM4Kbjo5
.

@jonboulle the answer to your question is, as they say, clear as mud: kubernetes/kubernetes#3764

so that issue is sort of confusing because it discusses container labels as well as image labels? I think the LABEL directive in Dockerfiles doesn't lead to labels on running containers. Also it looks like k8s adds only runtime labels--since image labels are immutable.
Can we consider only image labels for the time being? If this userLabels field is strictly for user-provided metadata, it seems like a simple 1to1 mapping appropriate.

Superseded by https://github.com/appc/docker2aci/pull/223, closing.


Research how to Allow User to select Stars to rate Resource

Overview
Allow User to select Stars to rate Resource
Technical Notes

resourcereview_rating = (
    (1,1),
    (2,2),
    (3,3),
    (4,4),
    (5,5)
)
resourcereview_stars = models.IntegerField(choices=resourcereview_rating)
def __str__(self):
    return self.resource.title


--crop function android12

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: [e.g. Debian, Windows, macOS...] windows10
scrcpy version: [e.g. 1.12.1] 2.1.1
installation method: [e.g. manual build, apt, snap, brew, Windows release...] windows release
device model: galaxy s10
Android version: [e.g. 10] 12

Describe the bug
I am mirroring by dividing the screen of the mobile phone into upper and lower parts through the --crop function, and then running the upper and lower windows separately.
However, in Android 12, there is a phenomenon that the two do not run at the same time.
If i run one window and then run a second window, the first window does not work.

This picture is Android 13, and it is a picture that shows the function I want to do.
However, just like this picture, using the --crop function does not work on Android 12.


Fix ISSUE-344

Regarding https://github.com/steemit/steem-js/issues/344
Hello, the previous method has round error and failed at input<PHONE_NUMBER>4120
    console.log(reputation(95832978796820));
    console.log(reputation(10004392664120));
    console.log(reputation(30999525306309));
    console.log(reputation(-37765258368568));

should output
69
61
65
-16

anybody reviews? thanks.


Default lights of the apply service

The apply service is meant to apply the adaptive lighting parameters to a specific set of light(s). This set of lights need to be passed to the service, even though each Adaptive Lighting switch already has this list configured on itself. While having the flexibility to apply to some, it also might be useful to apply to all lights that the switch manages.
This patch makes the lights paramater optional and defaults it to the lights configured on the corresponding configuration entry of the switch being called.

Thanks a lot!
Great contribution 😄


🚧 API: UnderlyingByteSource

Context
Specification: Name
Specification interface: Interface name
Additional documentation:

mdn docs
deno docs
Cloudflare workers docs
Boa documentation

Expected TypeScript interface

looks like https://streams.spec.whatwg.org/#underlying-source-api is equivalent to https://deno.land/api@v1.36.4?s=UnderlyingByteSource and not to https://deno.land/api@v1.36.4?s=UnderlyingSource
Not sure #160  and this one have to be done. @johnyob
keep it empty waiting your answer

This component is specific to deno impl and should not be implemented. Archived


Check node spec for unschedulable as well

Should address #453
Tested on minikube w/ v1.12.1
Let me know if I did something weird, first dive into this codebase. :)
Thanks!

/approve
please help to address the above comments, and then I'll add lgtm label to get it merged.

My bad, I know better. :) Fixed/Re-tested!
Thanks!

/lgtm


cmd/compile/internal/gc: prealloc map space

why it can be imported to gerrit?

why it can be imported to gerrit?


chore: add default solomachine client id for testing

Description
Add DefaultSolomachineClientID constant to testing package
closes: #2843
Commit Message / Changelog Entry
chore: replace 06-solomachine-0 with DefaultSolomachineClientID constant

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md).
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[x] Added relevant godoc comments.
[x] Provide a commit message to be used for the changelog entry in the PR description for review.
[x] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

I think it can be merged once #3328 is also merged since the fork e2e tests are failing

The pr seems ready for review now


Packgae Request: netbox

Project description
IP address management (IPAM) and data center infrastructure management (DCIM) tool.
Metadata

homepage URL: -
source URL: https://github.com/netbox-community/netbox
license: Apache-2.0
platforms: Linux

So far, I have packaged netbox and its remaining dependencies in https://github.com/NixOS/nixpkgs/compare/master...hax404:netbox_init?expand=1, but was not able to build the netbox module. Feel free to use this code base.

I created a PR at #162624. But it still some issues, where I could need help with more experienced nixos-contributers.

That's an enormous amount of work you put in there, thank you! I'm currently not in a position to review this though. I'm sorry. Perhaps another member will be able to. Thank you again :beers:

I failed to mention this at the time, but I packaged up all dependencies at the time in https://github.com/NixOS/nixpkgs/pull/143112 and then failed to find the time to continue with the actual application. Thanks for picking this up, will be around for the review.


Allow arbitrary input for ListSelect

Hi all,
I have a normal TextField in a form, and I'd like to use DAL to provide list of possible selection, but also allow user to type in an input if no match found. Basically, I'd like to present the autocomplete result as a suggestion to the user, not as a finite option for selection.
I am currently using the Select2ListView and building the list of suggestions, but during user input the widget does not accept any value outside of the autocomplete list. I think the current DAL assumes that you MUST choose from one of the selection.
Is there a way to render the suggestion, but when no match found, accept whatever input the user types in? A pointer to the right direction would help!
edit: to clarify, I am not after the behavior of creation of new choices as in: https://django-autocomplete-light.readthedocs.io/en/master/tutorial.html#creation-of-new-choices-in-the-autocomplete-form - I would simply like to be able to accept whatever the user type in into the TextField, thus making AutoComplete to provide a list of suggestion, not a finite option to select from.
Regards,
Zen

Hi @zsugiart, brilliant solution to this.
Would be good to get this added to the docs.
As a sidenote the DAL library uses Select2 under the hood but is not an exhaustive wrapper around it. Select2 is under active development and syntax and options keep changing all the time. If you want to further customise the behavior you can just interface directly with Select2 as you've done.

OK, so I got my own fix for this. So here's what I ended up doing:
To allow for 'arbitrary input' we need to use the 'tags' option of select2. Had a look and found that select2.js parsed Boolean, so I needed to use "true" instead of True on the widget code to make it work.
in the form:
# email is just a plain TextField
widgets = {
            'email':autocomplete.Select2(url='api>autocomplete.memberEmail', attrs={
                "data-tags":"true", "data-html":True,
            })
        }

For the autocomplete view, it's just the good ol' Select2QuerySetView - because that's what I wanted. I want it to search and return a QuerySet. This bit is working as expected.
class AutoComplete_MemberEmail(autocomplete.Select2QuerySetView):
    def get_queryset(self):
        return Member.Q_searchEmailNameUname(self.q)
    def get_selected_result_label(self, item):
        return item.user.email
    def get_result_label(self, item):
        return "%s <br />[@%s] %s" % (item.user.email, item.user.username, item.displayName )

So now in the UI form, when I type in a text in the email field, it searches AutoComplete_MemberEmail for members with matching username, name, or email. But when I don't see a suggestion that fits, I can type in another e-mail directly. the tags option creates a new option on the fly, and the new e-mail is set as the selected value.
Problem is, when I DO select an existing value, the get_result_label() output is set as the option value, instead of the get_selected_result_label() output. After some digging, I found the code in the select2.js that does it, and it only triggers when data-tags is present
...
processResults: function (data, page) {
                    if (element.attr('data-tags')) {
                        $.each(data.results, function(index, value) {
                            value.id = value.text; <-- this bit here
                        });
                    }
                    return data;
                },

So I had to override it with my custom js code which basically copy paste the same stuff, but set that line into
'''value.id = value.selected_text'''
I checked on the backend, if I did not define get_selected_result_label(), it automatically sets selected_text as the value of get_result_label(). So I think value.id = value.selected_text is better, because it make use of get_selected_result_label() output as intended.
So ... I'd consider this issue as solved ! not an issue with the DAL itself, but the select2.js when data-tags is set to true ignores get_selected_result_label()

It saved my day. Thanks for your help

Another possiblity is to simply use autocomplete.TagSelect2 witch is designed for this.
By defaut it accept multiple selection, but you can just say:
autocomplete.TagSelect2.allow_multiple_selected = False, or make your subclass.


All day events show up the next day

All day events in a iCal calendar cause 2 remind lines:
BEGIN:VEVENT
CREATED:20240924T181113Z
DTEND;TZID=floating;VALUE=DATE:20241014T000000
DTSTAMP:20241014T174502Z
DTSTART;TZID=floating:20241013T000000
LAST-MODIFIED:20240924T181113Z
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY: Delivery
TRANSP:TRANSPARENT
<EMAIL_ADDRESS>END:VEVENT

Results in:
REM Oct 13 2024 +3 MSG %a %"Delivery%"%
REM Oct 14 2024 +0 MSG %a %"Delivery%"%

This has finally annoyed me enough that I want to fix it.

Added a check while working on multi-day events to see if event starts and ends at 00:00:00, and ignored those days. This will appear in 0.8


NginxProxyManager ignoring ssl-ciphers.conf with custom SSL certificate's

Checklist
Have you pulled and found the error with jlesage/nginx-proxy-manager:latest docker image?
    Yes
Are you sure you're not using someone else's docker image?
    Yes
Have you searched for similar issues (both open and closed)?
    Yes

Describe the bug
When using a custom SSL certificate (in my case a Comodo/Sectigo Positive wildcard) and I do a SSL crypto check (cryptcheck.fr or ssl labs) for some reason all ciphers (including old unsecure ones) are enabled so ignoring the ones defined in the "ssl-ciphers.conf".
So to test I used the same host but this time I created a Let's Encrypt certificate instead of using my custom one, redid the crypto checks and now only the secure ciphers are showed (as defined in ssl-ciphers.cond).
Also tested this with another custom certificate same result...
@jlesage
Can you have al look at this plz?
Btw expect a donation for your great work.
Thx

@jlesage
Did some more research and found out why this is happening:
If you create a proxy, there a config file created inside /data/nginx/proxy_host (x.conf)
To test I created the same proxy but first with the custom SSL and second time with Let's Encrypt.
When I compared the two configs I noticed that in the config file for the Let's Encrypt host, the config line "include conf.d/include/ssl-ciphers.conf;" is added, if you look to the same proxy host with custom certificate that config line is not added.
Then to test I added the line manual to the proxy host with custom ssl and then the correct ciphers are used.
So as a workaround I just add "include conf.d/include/ssl-ciphers.conf; in the advanced tab section of the proxy hosts.
Btw: I posted this bug also on the Github off jc21 since the same problem exists here also


python3Packages: patch updates

Description of changes
Reference https://hydra.nixos.org/eval/1784131
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

fix build for chiapos: https://github.com/NixOS/nixpkgs/pull/199417/files#diff-30e6c1dab67b0202ec035585ff202ccf40b0ca516ecdb3dc1cdc0151dc5be833
(I will look at chiavdf asaic)

#199889

fixes tabulate and awsebcli https://github.com/NixOS/nixpkgs/pull/199470

Looks like this PR gained some merge conflicts - would it be helpful if I tried to rebase or would you prefer to keep the lead here yourself?

two more ood packages #201869

Unfortunately I did not have the time to finish this. Still, some commits can probably be cherry-picked.