Browserslist error

Hello, i just used 'npx create-react-app project-name' and when im starting my project im getting this error:
/src/index.css (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./src/index.css)
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.
at Array.reduce ()
at Array.some ()
at Array.filter ()
Npm -v : 6.9.0
Node -v : v10.16.0

Same issue for the same versions of node and npm

Same issue with me

Same issue for
Npm -v : 6.9.0
Node -v : v11.2.0

yep - same issue. what we gonna do?

Same here.
Node 11.6.0
npm 6.9.0

may be we just downgrade version of browserlist to 4.6.1?
in 4.6.2 they are fixed android queries
() Fix last x version and similar queries for Android (by Tony Ross).

@epicbytes don't we need to eject CRA for that?

@epicbytes don't we need to eject CRA for that?

i dont know in this time, its just an idea)

same issue

Same issue
npm -v : 6.9.0
node -v : v10.15.1

Same issue

If you want to pin browserslist version, pin it to 4.6.0.
4.6.2 = 4.6.1 + Readme changes
4.6.1 is the faulty one and was release 20days ago

We're having the same issue here. Halp. 😞

same issue 🙋

If you want to pin browserslist version, pin it to 4.6.0.
4.6.2 = 4.6.1 + Readme changes
4.6.1 is the faulty one and was release 20days ago

Browserslist 4.6.0 still raises same error to me.

Same issue for :
npm ver. 6.9.0
node ver. 12.4.0

Same issue for :
npm ver. 6.9.0
node ver. 10.16.0

Same issue for :
npm ver. 6.9.0
node ver. 10.14.1

Same issue for :
npm ver. 6.9.0
node ver. 10.14.1

Same issue:
node v 11.6.0
npm  v 6.5.0

Same issue:
npm v6.9.0
node v12.4.0

Same issue:
./src/index.css (./node_modules/css-loader??ref--6-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./src/index.css)
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.
at Array.reduce ()
at Array.some ()
at Array.filter ()

Same issue
node v v10.13.0
npm v 6.4.1

Same issue
npm 6.9.0
node v10.15.3

Same here
npm 6.4.1
node 8.12.0

same here
./src/index.css (./node_modules/react-scripts/node_modules/css-loader/dist/cjs.js??ref--6-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./src/index.css)
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.
at Array.reduce ()
at Array.some ()
at Array.filter ()

https://github.com/browserslist/browserslist/issues/382#issuecomment-502991170

Same issue
npm 5.6.0
node 8.11.4

Same issue...

Same issue.
node -v: 8.11.4
yarn -v: 1.16.0

same issue
node -v: v10.15.0
npm -v: 6.4.1

same in Nuxtjs
create-nuxt-app

Same issue
Node: 11.7.0
npm: 6.5.0

Same issue on nuxt right now

same in Nuxtjs
create-nuxt-app

same issue right now

Same issue
Node: 10.16.0
npm: 6.9.0

Is the world falling apart? 😅

node v10.15.3
npm 6.9.0

same issue
node: v10.15.3
npm: 6.4.1

BTW what caused this? Can anyone has the clue?

Same issue
Node: V10.16.0
Npm:6.9.0

has someone hacked the package repo? :o

same issue:
node: 10.12.19
npm: 5.6.0

Same issue
node: 10.12.19
npm: 5.6.0
why?

When a hacker breaks all the development community in the world hahaha

Same issue
Node: 8.12.0
Npm: 6.4.1

same in Nuxtjs
create-nuxt-app
npm run dev
help

Same issue
Node: v10.15.0
npm: 6.4.1

Same issue
"./src/pages/Main.module.css (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-4-1!./node_modules/postcss-loader/src??postcss!./src/pages/Main.module.css)
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.
at Array.reduce ()
at Array.some ()
at Array.filter ()"
Node: 10.15.3
Npm: 6.4.1

hate to be "that guy", but commenting "Same issue" isn't really productive, and just pollutes the issue for whoever's looking at it. please reconsider

Same here!
node 10.14.1
npm 6.4.1

I'm here looking for solution not for comment same issue :(

I'm having same issue with
Node: v11.15.0
npm: v6.7.0

Same issue with
Node V10.9.0
Npm V6.9.0

Anyone found a workaround this issue ?

On Windows 10 x64:
`>node -v
v12.4.0

npm -v
6.9.0
`

same issue
BrowserslistError: Unknown browser query android all. Maybe  you are using old Browserslist or made typo in query.
at Array.reduce ()
at Array.some ()
at Array.filter ()
npm: 6.9.0
node: 10.16.0
issue arising during:    npm start (starting live server for creating react app)

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

Same issue
node 8.11.3
npm 6.2.0

Same issue on macOs 10.14.5
node: 8.9.4, npm 5.6.0

Same issue :/

Same issue
Mac OS 10.14.5
node 8.11.3
npm 6.2.0

pin "caniuse-lite": "1.0.30000974" in your package.json

Same Issue
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.
at Array.reduce ()
at Array.some ()
at Array.filter ()

the great thing here is the same issue :D :dancer:

same issueBrowserslistError: Unknown browser queryandroid all. Maybe you are using old Browserslist or made typo in query.     at Array.reduce (<anonymous>)     at Array.some (<anonymous>)     at Array.filter (<anonymous>)     at new Promise (<anonymous>)

removing all options from browserslist.production does the trick. A simple workaround until it is properly solved

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

Firefox seems to be the faulty one. It will still start when leaving chrome and safari there

On the left is the package.lock.json who was working before, on the right the new one.
There's only these differences.

Different issue now!
./src/index.css (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./src/index.css)
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.
at Array.reduce ()

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

@NaNdaWteK It worked for me.

same issue here. Deleted import './index.css' from index.js and started to work. But this is not a solution.

Similar to @carpacciao's diff, I have found that I also have this problem with this library:

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

This will work for now I believe

the solution will be to not use 30000975 caniuse-lite version and simply keep an older package-lock.json to restrict it to 973 or 974.

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

Firefox seems to be the faulty one. It will still start when leaving chrome and safari there

This works like a charm

Firefox seems to be the faulty one. It will still start when leaving chrome and safari there

Not sure if it's going to help anyone, but just wanted to note that after starting once successfully you seem to be able to actually put firefox back as well, and it will keep on starting successfully.

delete these lines in the package json file
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version",
"Android >= 4"
an its worked

the solution will be to not use 30000975 caniuse-lite version and simply keep an older package-lock.json to restrict it to 973 or 974.

pin "caniuse-lite": "1.0.30000974" in your package.json
they released a new version 2 hours ago:
https://www.npmjs.com/package/caniuse-lite

It works for me. Better solution for now.

temporary solution
package.json
 "browserslist": [],

pin "caniuse-lite": "1.0.30000974" in your package.json
they released a new version 2 hours ago:
https://www.npmjs.com/package/caniuse-lite

  "dependencies": {
    "react": "^16.8.6",

     ...

    "caniuse-lite": "1.0.30000974"
  },

temporary solution, but its work

pin "caniuse-lite": "1.0.30000974" in your package.json
they released a new version 2 hours ago:
https://www.npmjs.com/package/caniuse-lite

Installed, it but did not work for me.?
i am getting same error for android all when i run npm run dev

temporary solution
package.json
 "browserslist": [],

This works!

temporary solution
package.json
 "browserslist": [],

This works!!!

temporary solution
package.json
 "browserslist": [],

yeah, I tried and worked

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

@NaNdaWteK It worked for me.

Yes, worked also for me too!

temporary solution
package.json
 "browserslist": [],

npm ERR! JSON.parse Failed to parse json
does not work for me hmm

temporary solution
package.json
 "browserslist": [],

npm ERR! JSON.parse Failed to parse json
does not work for me hmm

Delete comma ;)

temporary solution
package.json
 "browserslist": [],

npm ERR! JSON.parse Failed to parse json
does not work for me hmm

yaaas, remove the comma at the end

Hi I just removed
"last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"

from browsersList development and it worked, Somebody know the source of this problem?

At the moment you can try this and wait for further fix
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
]
}

temporary solution
package.json
 "browserslist": [],

This works!

Thankyou. worked.

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

Same issue and the workarond fix works good. Thanks!

Hi I just removed
"last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"

from browsersList development and it worked, Somebody know the source of this problem?

Yep it's worked! Thanks!

Don't see an issue here https://github.com/browserslist/browserslist/commits/master
Must be something else 🤔

"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
]
}
Update to your package.json . it worked for me as well.

Sadly I can't get that working, I've removed everything from both the development and and production array but Im still getting the same error, pretty odd since it gets to work for nearly everyone.

"browserslist": []
This worked like a charm for me.

there is another thing strange here
it is opening with the same port more than 1 as :3000
so what???

the solution will be to not use 30000975 caniuse-lite version and simply keep an older package-lock.json to restrict it to 973 or 974.

For those of you using yarn, you need to modify the yarn.lock file to not include the 975 version. You can use a block like this:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  version "1.0.30000974"
  resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30000974.tgz#b7afe14ee004e97ce6dc73e3f878290a12928ad8"
  integrity sha512-xc3rkNS/Zc3CmpMKuczWEdY2sZgx09BkAxfvkxlAEBTqcMHeL8QnPqhKse+5sRTi3nrw2pJwToD2WvKn1Uhvww==

to pin it to 974 and also remove the block, referencing to 975.

from browsersList development and it worked, Somebody know the source of this problem?

Don't see an issue here https://github.com/browserslist/browserslist/commits/master
Must be something else 🤔

There isn't a solution, but if you want to continue developing, remove development browserlist items in package.json works for me
"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
    ]
  }

Same issue and the workarond fix works good. Thanks!

Worked for me, thanks

temporary solution
package.json
 "browserslist": [],

This works!

Thankyou. worked.

This worked perfectly! Thank you so much

"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
]
}
Update to your package.json . it worked for me as well.

worked for me

Same Issue here
Windows 10 Version 1809 (Build 17763.557)
node v11.10.0
npm 6.7.0

Following Solution worked 🚀

Add caniuse-lite to your package.json
npm i

"dependencies": {
    "react": "^16.8.6",
    ...
    "caniuse-lite": "1.0.30000974"
  }

maybe resolutions better for the temp quick fix
 "resolutions": {
    "caniuse-lite": "1.0.30000974"
  }

"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
]
}
Update to your package.json . it worked for me as well.

Work for me, Thanks!

maybe resolutions better for the temp quick fix
 "resolutions": {
    "caniuse-lite": "1.0.30000974"
  }

works in yarn 😘

For those of you who can't seem to have much luck with the solutions provided try aborting npm run and executing it again.

temporary solution
package.json
"browserslist": [],

Rolling back to<EMAIL_ADDRESS>works perfectly.
I though yarn add<EMAIL_ADDRESS>--exact  will force the version. But doesn't.
So I did what @phuhl said. Edit yarn.lock for the line for caniuse-lite that reference 975, and manually update the version, resolved and integrity lines. Respecting the first line. Then yarn install and it started working again.
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  version "1.0.30000974"
  resolved "https://registry.yarnpkg.com/caniuse-lite/-/caniuse-lite-1.0.30000974.tgz#b7afe14ee004e97ce6dc73e3f878290a12928ad8"
  integrity sha512-xc3rkNS/Zc3CmpMKuczWEdY2sZgx09BkAxfvkxlAEBTqcMHeL8QnPqhKse+5sRTi3nrw2pJwToD2WvKn1Uhvww==```

maybe resolutions better for the temp quick fix
 "resolutions": {
    "caniuse-lite": "1.0.30000974"
  }

Work for me, Thanks!

I am also facing the same issue,
./src/index.css (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-3-1!./node_modules/postcss-loader/src??postcss!./src/index.css)
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.

Looks like this is the problem. There has been a commit in caniuse-lite 3 hours ago: https://github.com/ben-eb/caniuse-lite/commits/master
Issue: https://github.com/ben-eb/caniuse-lite/issues/27

here https://pasteboard.co/IjXHz77.png is the package.json file just update yours to this you will be all set to go temporarily after this do npm start.

check here
https://github.com/browserslist/browserslist/issues/382

Setting up a typescript project with
create-react-app --typescript project

does not produce this error 🤔

maybe resolutions better for the temp quick fix
 "resolutions": {
    "caniuse-lite": "1.0.30000974"
  }

Work for me, Thanks!

maybe resolutions better for the temp quick fix
 "resolutions": {
    "caniuse-lite": "1.0.30000974"
  }

Worked like charm

We made a dirty fix in Browserslist 4.6.3 to fix the problem: https://twitter.com/Browserslist/status/1140911400304467968

The problem is solved in new react apps at this moment

The problem is fixed :)

problem solve after install browserslist
 npm i<EMAIL_ADDRESS>

hello, after the fix my react project run but while compiling I got this:

hello, after the fix my react project run but while compiling I got this:

You will see this warning until we will not have the real fix in postcss-preset-env

@ai Thank you so much for the quick "dirty" fix. Really appreciate it

@ai please tell us when the problem is solve
Thanks

@Creator-360 subscribe to https://twitter.com/Browserslist for recent updates

temporary fix, change
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
to
"browserslist": {
"production": [
],

Do not change browserslist: []. It will remove all prefixes and polyfills.
Just update Browserslist.

Do not change browserslist: []. It will remove all prefixes and polyfills.
Just update Browserslist.

Just update Browserslist.

How i can update Browserlist inside create-react-app? i have just installed latest Browserslist in devDependencies, but it doesn't help me.

same issue:
on yarn v1.16.0
clear the browserlist is the temporary solution.
"browserslist": {     "production": [     ],     "development": [     ]   } }

same issue:
node -v : v10.15.3
yarn -v : 1.16.0

"browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }

This solution worked for me

How i can update Browserlist inside create-react-app?

yarn upgrade or npm update

it seems like caniuse-lite has unpublished the bad version. rm -rf node_modules and reinstall deps

it seems like caniuse-lite has unpublished the bad version. rm -rf node_modules and reinstall deps

nope

I think the issue is now fixed:
npm cache clean --force
rm -rf node_modules
rm package-lock.json && npm install

or
yarn cache clean
rm -rf node_modules
rm yarn.lock && yarn

would do.

I think the issue is now fixed:
npm cache clean --force
rm -rf node_modules
rm package-lock.json && npm install

or
yarn cache clean
rm -rf node_modules
rm yarn.lock && yarn

would do.

no it's not, here: https://www.npmjs.com/package/caniuse-lite, version 1.0.30000975 is still active (which is also causing the problem)

I did
npm cache clean --force
rm -rf node_modules
rm package-lock.json && npm install

and yet the problem remains :(

march08 is right, caniuse-lite 1.0.30000975 was removed on https://github.com/ben-eb/caniuse-lite/releases but it is still available on npm.  So we are still waiting for downstream patches to happen.

I tried...

npm cache clean --force
rm -rf package-lock.json
npm install<EMAIL_ADDRESS>
and the error is gone.....!!!!

@ai this is affecting our production release cycles since builds break and can't complete with Netlify. Would it be possible to revert introduced breaking changes and try to find a fix in isolation?
I may be wrong, but suggested fixes are non-deterministic and don't work for everyones environment.

@timurmamedov nobody did a breaking change. We had an error in postcss-preset-env browsers generation. By accident this error didn't showed before. New Can I Use update just contained new data. Unfortunately with this new data that old issues generated wrong browsers list (with never existed android all). The browsers list is still broken because of this issue. We should fix this issue somewhere in postcss-preset-env.
 We just ignore broken android all browser. But it means that Autoprefixer will miss correct prefixes for Android. To mark that browsers list is still incorrect we print warning.

I see, thanks for clarification Andrey. I'll see if we can have a look as well

how do fix this issue?

@liSong5713 Temporary solution:
npm i<EMAIL_ADDRESS>npm i<EMAIL_ADDRESS>

temporary solution:
// package.json

  "resolutions": {
    "browserslist": "4.6.2",
    "caniuse-lite": "1.0.30000974"
  },

This looks like a repeat of what the angular team ran into some time ago. Came to report left with a solution. Thank you! @ycjcl868

It looks like caniuse or caniuse-lite may have published a potentially breaking change that rolled into postcss-preset-env, which then rolled into browserslist and threw this error or warning.
How it worked: More or less, caniuse stats are provided as an object of features, like { "css-all": {}, "css-any-link": {} }. Within each feature, stats are provided as an object of browsers, like { "android": {}, "edge": {} }. Within each browser, stats are provided as an object of versions or version ranges, like { 4.1": "n", "4.2-4.3": "n" }.
For example, one tree of features might look like { "css-all": { "android": { "4.1": "n", "4.2-4.3": "n" } } }.
What changed: Within the android browser object of versions, stats now provide a simplified "all" value.
This means one tree of features might look like { "css-all": { "android": { "all": "n" } } }.
That is how the android all query ends up getting generated, which browserslist does not support.

How i can update Browserlist inside create-react-app?

yarn upgrade or npm update

Didn't help with update.

How i can update Browserlist inside create-react-app?

yarn upgrade or npm update

Didn't help with update.

Try it stuff:
// package.json

"devDependencies": {
    "browserslist": "4.6.2"
  },
"resolutions": {
    "browserslist": "4.6.2",
    "caniuse-lite": "1.0.30000974"
  },

There is some help.

How i can update Browserlist inside create-react-app?

yarn upgrade or npm update

Didn't help with update.

Try it stuff:
// package.json

"devDependencies": {
    "browserslist": "4.6.2"
  },
"resolutions": {
    "browserslist": "4.6.2",
    "caniuse-lite": "1.0.30000974"
  },

There is some help.

@umyar, that didn't help. Adding that actuall fails my build with the following message:

./src/App.css
BrowserslistError: Unknown browser query android all. Maybe you are using old Browserslist or made typo in query.
at Array.reduce ()
at Array.some ()
at Array.filter ()
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: react-scripts build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!      /Users/tomasjansson/.npm/_logs/2019-06-20T12_55_59_151Z-debug.log

This guy has the fix https://github.com/browserslist/browserslist/issues/382#issuecomment-503182000. Just tried and it works.

  This broke my 2.1.8 build.   Can't get those 8 hours back....
I 100% understand that the blame here is distributed, but I still am considering ejecting and/or migrating away from react-scripts entirely.   I can't help but wonder which one of the dependencies will break next.  There are over 50 direct dependencies in package.json when i eject a fresh project, and node_modules has around 1000 folders in it.  Is this REALLY the way to use react?
Also the only thing that worked for me was settings browserslist:[] in package.json as @anhquande has mentioned.

temporary solution:
// package.json

  "resolutions": {
    "browserslist": "4.6.2",
    "caniuse-lite": "1.0.30000974"
  },

maybe you can use umijs, it is not affected.

don't work

temporary solution:
// package.json

  "resolutions": {
    "browserslist": "4.6.2",
    "caniuse-lite": "1.0.30000974"
  },

maybe you can use umijs, it is not affected.

don't work

remove browserslist item, only set caniuse-lite, it works for me.

@zechau  you can use yarn install, it's ok. resolutions

@ycjcl868 gotcha.

Any level of testing should have caught this, that is the contract cost of using dependancies. I hate to ask or look since I know what I'm getting isn't what I'll actually use when I care about the content I'm making, but do you need help developing better tests? This project is a nice relief for dealing with rolling changes in this bloated ecosystem. I'm confident if it needs to happen the community will come together to make sure this doesn't happen again. It could have been any subdep changes that didn't crash getting into your npm release.

@ai @jonathantneal builds seem to be succeeding now, since the latest update to caniuse-lite from 5 hours ago. Thank you.

@timurmamedov, yes, the all version appears to be removed in<EMAIL_ADDRESS>which has been merged into<EMAIL_ADDRESS>I used this rudimentary test to compare v1.0.30000975 and v1.0.30000976:
// present in 1.0.30000975, removed in 1.0.30000976
caniuse.feature(caniuse.features['prefers-color-scheme']).stats.android.all

Looking at the most recent commits to caniuse-lite, it appears this change was most likely made within caniuse-db, and not patched in caniuse-lite. This is great news for all projects affected by the all change to caniuse-db, including PostCSS Preset Env. 🎉
@etisdew, if I managed caniuse, which merely exports a collection of function-less JSON files, I might not be prepared to test for every way other projects have chosen to use my files. If you think more tests are needed, you must produce a sufficient JSON schema and submit the PR to caniuse-db — I believe that is the contract cost of complaining about open source. 😉

@ai @jonathantneal builds seem to be succeeding now, since the latest update to caniuse-lite from 5 hours ago. Thank you.

I just tried it on my projects and it seems the issue is resolved.

@jonathantneal I only feel empathy for the situation in which another repository is able to affect its downstream users. From a learning perspective what is the best way of managing and remediating dependancys and the possibility of dependency divergence? Rollback and lock until stable? Find/build alternatives?
My major concern is malicious injection through strategic compromise and the dangers of rolling dependencies. I know that in any sizable form they would be obvious and found in review but on the state of the culture, the idea of manually disabling an execution context from human input grows harder and harder in the context of an automated pipeline not using strict version semantics and open source suffering from non-viable donation models to give the time and attention where it deserves to be. Keep fighting the good fight, but I would be interested to learn more about how to handle these issues, isolating ones own project from them without going full hermit.

@etisdew we already discussing solution in postcss-preset-env repo. This repo is a wrong place for issue and discussing.

@ai and all the other devs in create-react-app.  THANK YOUUUU.
This also highlights the absurdity that we deal w/ in the first place.  The dependency-heavy-environment that we navigate is a result of the browser devs lack of standards and coherency.
As endusers its super easy to place blame, on say, CRA, or browserslists, or postcss-preset-env.  The reality is that NONE of these would have to exist if the browser wasn't a giant flaming turd to develop on.

Now, what can we do to help avoid this?

Question is definitely off topic... I am not even talking about this browserslists fiasco.
As a user of CRA, what kind of confidence can I have in this going forward that this wont just randomly break?

I apologize for OT and discussion, I have to second the comment thanking you and all developers in the pipeline we have to manage everyday.  Open source is a beautiful thing aswell. Issue seems to be largely closed yes?

Yeap, this issue can be closed here.
We in separated issue are finding solution to prevent problems on similar case in the future.

As a user of CRA, what kind of confidence can I have in this going forward that this wont just randomly break?

That's what the package lock file prevents.
Closing this issue for now as it appears to be resolved. Will leave pinned for a couple days in case anyone is still running into this issue.

That's what the package lock file prevents.

This broke a stable project on CRA 2.1.8.  With said lock file, I was getting a warning saying to update caniuse-lite and browserslist.  I did not update or change any deps; I woke up to builds failing.
I'd be happy to provide yarn.lock if useful.

@derek-adair please file a new issue with commands your build ran and errors you saw.  Also results to "yarn why caniuse-lite"


Introduce HasBinaryBlockInfo and make it overridable in SerialiseHFC

Fixes #2239.
Instead of having a RunNode method to get the BinaryBlockInfo of a
block (offset and size of the header within the block), create a separate type
class HasBinaryBlockInfo for it. This is another step in the clean-up process
of RunNode that started in the weeks before the HFC was merged.
This means we can provide a generic implementation of HasBinaryBlockInfo for
HardForkBlock that takes the HFC wrapper into account. This wrapper adds a
listlen 2 and a tag indicating the era to the start of each block, so we need to
shift the offset of the header by 2 bytes.
More importantly, we now allow overriding the getBinaryBlockInfo method in
SerialiseHFC, just like we allow overriding the disk en/decoder for blocks.
This allows us to do the right thing for the Byron era: no era wrapper for
Byron, but start using era wrappers for the eras after it.
This also fixes a bug: cardano-node running in pure Shelley mode uses
ShelleyHFC, i.e., a ShelleyBlock wrapped in the HFC. Since the generic
RunNode instance for HardForkBlock '[blk] forwards everything to the
instance for blk, we were using the BinaryBlockInfo implementation for
Shelley, which didn't account for the era wrapper in the header offset. Since
we were using the era wrapper to serialise ShelleyHFC blocks on disk, this
meant we were extracting the header from the on-disk blocks incorrectly,
resulting in deserialisation failures when reading headers from disk.
This refactoring allows us to fix it properly: now the defaults for
SerialiseHFC do the right thing for ShelleyHFC, and for ByronHFC we
forward to ByronBlock, just like for all the other methods. This means
ShelleyHFC starts out with an era wrapper around blocks from the first era (to
allow for easier transitions to later eras, which is the right thing to do from
the start), but ByronHFC's block format is binary compatible with
ByronBlock.

bors merge


add yarn in readme.md

Added yarn as an install method in readme file.

what do you think @eltonmesquita

Although it doesn't hurt to add yarn, I don't think it's necessary at all as npm and yarn are interchangeable. But I'm open to it. What do you think @WarenGonzaga ?

@eltonmesquita base on this https://scotch.io/@brian_kimo/npm-vs-yarn I think we should add options to our users to select which they want to use between NPN or YARN.

Alright. Merging it.


Add auto-installation script

An attempt on an installation script that creates the config directory, adds in the example config file, places the binaries in their correct folders (/bin), and adds in a script launching mouseless with the --config flag.

Thanks for the contribution, I would like to merge it with some adjustments:

consider the case when multiple devices are found, optimally insert all to the config file, but it would also be ok to simply take the first one (e.g. with head -n1) so that at least the config file is syntactically correct
use /usr/local/bin which is intended for manually installed binaries
use /tmp/mouseless instead of the home directory for temporary files

Do you want to have a look? Otherwise I could also merge it and then make the adjustments.

Is this what you had in mind?

So I've accidentally written a genious code. I plugged a keyboard into my laptop, and the keyboard variable detected the plugged in keyboard. Once un-plugged, the variable is back to the laptop keyboard.

We could set mouseless-execute to automatically detect the connected keyboards, and upon each launch it would detect whether an external one is plugged in, or if you are only using the laptop's one, and it would change it in the config file.... now how to implement that.

So I've come up with this idea. It's not ideal at all as it involves the user pasting commands into the terminal, but for some reason sed refuses to edit the config file if it's done directly like this sed -i 's#$oldkeyboard#$newkeyboard#g' config.yaml, but when you echo this output, the variables get replaced with the names of the keybaords, and once pasted into the terminal, it works as intented. I'm probably missing something important with sed.
#!/bin/bash

newkeyboard=$(ls /dev/input/by-id/*kbd* || ls /dev/input/by-path/*kbd* | head -n1)
oldkeyboard=$(cat /home/$USER/.config/mouseless/config.yaml | grep "/dev/input" | sed 's/- //')
echo "Copy this output and paste it into your terminal."
echo "====================================================="
echo "cd /home/$USER/.config/mouseless && sed -i 's#$oldkeyboard#$newkeyboard#g' config.yaml && sudo mouseless --config ~/.config/mouseless/config.yaml"
echo "====================================================="

Made it work, even tho I'm not pround of this at all. But hey, it does exactly what I wanted.
#!/bin/bash

newkeyboard=$(ls /dev/input/by-id/*kbd* || ls /dev/input/by-path/*kbd* | head -n1)
oldkeyboard=$(cat /home/$USER/.config/mouseless/config.yaml | grep "/dev/input" | sed 's/- //')

touch /home/$USER/.config/mouseless/hugeworkaround.sh
echo "#!/bin/bash
cd /home/$USER/.config/mouseless && sed -i 's#$oldkeyboard#$newkeyboard#g' config.yaml && sudo mouseless --config ~/.config/mouseless/config.yaml" > /home/$USER/.config/mouseless/hugeworkaround.sh
chmod +x /home/$USER/.config/mouseless/hugeworkaround.sh
cd /home/$USER/.config/mouseless
sh hugeworkaround.sh

One can also specify multiple devices in the config file, and mouseless reads all that are currently available. If there is more logic needed I would like to put it in mouseless itself and not an external script, unless for special cases maybe. Some improvements I have been thinking about:

if it cannot read any of the devces in the confg file, it could detect all available keyboards and ask the user which to use
if the config file does not exist, create one and ask which device to use
an option to read all keyboards it can detect

Interesting, didn't know mouseless accepts multiple keyboard names in the config. I will take a look when I get back home.

It looks good now, there are just some minor things I would change, but I merge it now and go over it again later.
Thanks again for your contribution!


NSwagStudio - generated OpenApi c# client does not fill form data correctly for arrays

According to the way the Swagger UI sends array data in a multiform, and also according to this issue https://github.com/swagger-api/swagger-ui/issues/4741, arrays should not be sent as a single value.
If I use the NSwag Studio to generate an OpenApi c# client, in the code the array is actually sent as a single value (string, in my case)
public async System.Threading.Tasks.Task<Result> PostSomethingAsync(IEnumerable<string> myArray= null, System.Threading.CancellationToken cancellationToken = default(System.Threading.CancellationToken))
    {
 var boundary_ = System.Guid.NewGuid().ToString();
          var content_ = new System.Net.Http.MultipartFormDataContent(boundary_);
          content_.Headers.Remove("Content-Type");
          content_.Headers.TryAddWithoutValidation("Content-Type", "multipart/form-data; boundary=" + boundary_);
...
 if (myArray== null)
            throw new System.ArgumentNullException("myArray");
          else
          {
            content_.Add(new System.Net.Http.StringContent(ConvertToString(myArray, System.Globalization.CultureInfo.InvariantCulture)), "myArray");
          }
...
}

private string ConvertToString(object value, System.Globalization.CultureInfo cultureInfo)
    {
...
      else if (value.GetType().IsArray)
      {
        var array = System.Linq.Enumerable.OfType<object>((System.Array) value);
        return string.Join(",", System.Linq.Enumerable.Select(array, o => ConvertToString(o, cultureInfo)));
      }
...
  }

Which is wrong, when sending the data to the backend the array gets deserialized as an array containing one single item, whereas I would expect a list of items.
What do you think about that? Is there a way to workaround this issue?
Thanks

Any hints? Am I doing something wrong in the documentation of the API?


udpates with Vue Flow tree in extension panel, based on static data

Updates dev branch with a fully-featured Vue Flow tree in App.vue, based on static data from initial-elements.js.
Updates package.json with dependencies for running Vue Flow.

Awesome work Abe!


Settings structure not optimal for VoiceOver

From @PeterSaathoff-Harshfield
Settings editor: tab around after the commonly used comes, "settings list focus helper, group," which seems to outline most of the window and contains no other elements.
Next is "settings, table." This appears to contain the bulk of the settings. Interacting with this area does nothing. VoiceOver knows about no elements within. Interestingly, using tab at this point will cause VoiceOver to move focus to controls within this area, but only editable controls and links. None of the static text is accessible.
Below the main settings area is another "settings list focus helper" that appears to do nothing.
At the bottom of the window is a bar that VoiceOver reports as, "content info." The elements in this bar are navigated to by VoiceOver in the opposite order than they appear

The static text should be read when you focus the setting control. I'll have to investigate

At the bottom of the window is a bar that VoiceOver reports as, "content info." The elements in this bar are navigated to by VoiceOver in the opposite order than they appear

I'm not sure what you're referring to

I made a short video demonstrating this "right-to-left" order. https://youtu.be/SPHmXH4OY6E

Ok, that is called the status bar, it is not related to the settings editor.

Afaik we do not allow focus to go to the status bar.
Aslo assigning to @bpasero

We intentionally do not allow to focus into the status bar so that we reduce the number of tab stops in the UI and not frustrate the user that needs to use Tab to navigate. I do not think we should chang this unless people that use Tab key for navigation ask for this.

I was not indicating that there was anything happening with tabbing through the status bar.
What I am referring to is that, using standard VoiceOver navigation commands (control + option + left/right arrow), the elements in the status bar are in the opposite order than they appear visually.

@PeterSaathoff-Harshfield ah yes good point, this is due to the use of float: right down there which I might want to revisit 👍

@bpasero We are now using flex down there
@PeterSaathoff-Harshfield the status bar behavior should be better

@isidorn ah yeah, forgot to come back here. the order of items is still reverse though, even when using flex. I need to do that so that elements wrap in an order that is good for us (e.g. the notification icon should drop last).
If someone has an idea for this question I can change that:
I have a div with display: flex and multiple elements within. When I shrink it’s size, I want the first item to hide (=wrap) but not the last. By default, flex starts to wrap the last element which makes sense. I know I can do it via flex-direction: row-reverse but that makes it complicated because elements in the DOM have to be in reverse order.

Let's add help-wanted so maybe some nice soul comes and answers your question.

Should we move this to a new issue though? I find the summary has nothing to do with status bar.

Yeah, created https://github.com/microsoft/vscode/issues/76010

@roblourens I see there are quite some issues settings UX not accessibilie. Maybe we compile all the data in one issue and try to close duplicates?


"received only 1 responses from 2 CL=QUORUM" query error having RF=3 and only 1 down node

What version of Scylla or Cassandra are you using?
4.6.3 , 2022.1.rc8
What version of Gocql are you using?
1.6.0
What version of Go are you using?
1.17.4
What did you do?
Created 5-node Scylla cluster and ran scylla-bench tool that uses this gocql driver. Commands are following:
stress_cmd:
- scylla-bench -workload=sequential -mode=write -replication-factor=3 -partition-count=25 -clustering-row-count=10000 -partition-offset=401 -clustering-row-size=uniform:10..1024 -concurrency=10 -connection-count=10 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 10
- scylla-bench -workload=sequential -mode=write -replication-factor=3 -partition-count=25 -clustering-row-count=100 -partition-offset=426 -clustering-row-size=uniform:2048..5120 -concurrency=10 -connection-count=10 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 10
- scylla-bench -workload=sequential -mode=write -replication-factor=3 -partition-count=25 -clustering-row-count=10 -partition-offset=451 -clustering-row-size=uniform:5120..8192 -concurrency=10 -connection-count=10 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 10
- scylla-bench -workload=sequential -mode=write -replication-factor=3 -partition-count=25 -clustering-row-count=1 -partition-offset=476 -clustering-row-size=uniform:8192..10240 -concurrency=10 -connection-count=10 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 10
- scylla-bench -workload=sequential -mode=read  -replication-factor=3 -partition-count=25 -clustering-row-count=5555 -clustering-row-size=uniform:1024..2048 -concurrency=100 -connection-count=100 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 0 -duration=170m -validate-data
- scylla-bench -workload=sequential -mode=read  -replication-factor=3 -partition-count=25 -clustering-row-count=5555 -partition-offset=26 -clustering-row-size=uniform:1024..2048 -concurrency=100 -connection-count=100 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 0 -duration=170m -validate-data
- scylla-bench -workload=sequential -mode=read  -replication-factor=3 -partition-count=25 -clustering-row-count=5555 -partition-offset=51 -clustering-row-size=uniform:1024..2048 -concurrency=100 -connection-count=100 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 0 -duration=170m -validate-data
- scylla-bench -workload=sequential -mode=read  -replication-factor=3 -partition-count=25 -clustering-row-count=5555 -partition-offset=76 -clustering-row-size=uniform:1024..2048 -concurrency=100 -connection-count=100 -consistency-level=quorum -rows-per-request=10 -timeout=30s -retry-number=30 -retry-interval=80ms,1s -iterations 0 -duration=170m -validate-data

As it can be seen. We use RF=3 and CL=quorum.
Then, as part of a test run we do various disruptions to Scylla cluster. ANd when we run terminate and replace node disruption/nemesis we get following error with pretty high probability:
Operation timed out for scylla_bench.test - received only 1 responses from 2 CL=QUORUM.

Host selection policy which we use is token-aware with fallback to round-robin. But, host-pool with automatic detection of down nodes behaves the same way.
Note that this problem is not rare it gets caught a lot of times. It is hard to not catch it making a Scylla node go down.
What did you expect to see?
No errors because there must be 2 alive Scylla nodes holding replicas and only 1 down (expected).
What did you see instead?
The mentioned error which assumes that one of the Scylla nodes that holds one of replicas is not contacted to.
Logs
CI job: https://jenkins.scylladb.com/view/staging/job/scylla-staging/job/valerii/job/longevity-large-partition-asymmetric-cluster-3h/13/console
db-cluster - https://cloudius-jenkins-test.s3.amazonaws.com/700cb0a5-d24d-43a1-b191-4cf8e954cffe/20220628_125019/db-cluster-700cb0a5.tar.gz
monitor-set - https://cloudius-jenkins-test.s3.amazonaws.com/700cb0a5-d24d-43a1-b191-4cf8e954cffe/20220628_125019/monitor-set-700cb0a5.tar.gz
loader-set - https://cloudius-jenkins-test.s3.amazonaws.com/700cb0a5-d24d-43a1-b191-4cf8e954cffe/20220628_125019/loader-set-700cb0a5.tar.gz
sct-runner - https://cloudius-jenkins-test.s3.amazonaws.com/700cb0a5-d24d-43a1-b191-4cf8e954cffe/20220628_125019/sct-runner-700cb0a5.tar.gz

If you are having connectivity related issues please share the following additional information
Describe your Cassandra cluster
please provide the following information

output of nodetool status
output of SELECT peer, rpc_address FROM system.peers
rebuild your application with the gocql_debug tag and post the output

Hello! This is an error from the Scylla server and not an error at gocql side. The Scylla server coordinator node could only get response from 1 replica. Is it possible that you overloaded the cluster by bringing one of the nodes down?

Hello! This is an error from the Scylla server and not an error at gocql side. The Scylla server coordinator node could only get response from 1 replica. Is it possible that you overloaded the cluster by bringing one of the nodes down?

No. The load was about 25%.
Proof:

we need to see if retries did work, and took into action, is there a way to enable debug to see that ?
if all the timeout are in coordinator end and fail even when retried, so yes sound like a scylla end issue. (and we should move it there)

You can supply a QueryObserver and BatchObserver to count the number of query attempts. The occurrences with Attempt > 0 are retries.

I implemented simple observe query logger and, looks like, it is useless for this case.
Here is how it looks like:
2022/07/15 18:08:15 [CQL] query: '''SELECT pk, ck, v FROM scylla_bench.test WHERE pk = ? AND ck >= ?  LIMIT 10 ''' is attempted 13 time
...
2022/07/15 18:08:15 [CQL] query: '''SELECT pk, ck, v FROM scylla_bench.test WHERE pk = ? AND ck >= ?  LIMIT 10 ''' is attempted 2879 time
2022/07/15 18:08:15 [CQL] query: '''SELECT pk, ck, v FROM scylla_bench.test WHERE pk = ? AND ck >= ?  LIMIT 10 ''' is attempted 2881 time

Here we can see that attempts just grow with the load alongside having completely healthy cluster.
So, it is not number retries made after failed attempts.

How does the code executing the queries look like? It seems that the code might be calling Query.Exec multiple times with the same *Query value?
gocql currently has a note in the documentation that queries shouldn't be reused across multiple executions. This is one of the reasons why I added that note there. Historically it was not documented what the usage of Query should look like though, so it's possible that scylla-bench reuses the query.

How does the code executing the queries look like? It seems that the code might be calling Query.Exec multiple times with the same *Query value?
gocql currently has a note in the documentation that queries shouldn't be reused across multiple executions. This is one of the reasons why I added that note there. Historically it was not documented what the usage of Query should look like though, so it's possible that scylla-bench reuses the query.

The code just reads and logs, no calls at all.
And yes, I also think that scylla-bench uses same query all the time.

@martin-sucha
For some reason, github doesn't allow me to add you as a reviewer to the fix of this bug here: https://github.com/scylladb/gocql/pull/104

The problem was in the incorrect usage of the queries.
Closing because fix must be in the scylla-bench project.


feat: add loot notifier option to skip player loot

Add a setting for loot notifier to ignore player loot events

Does it make sense to just say PvP loot?


provide props such as prefix, suffix

This function solves the problem (这个功能解决的问题)
user experience
Expected API (期望的 API)
Other than slot, provide props such as prefix, suffix, etc

Please list related components.

For now, naiveui supports a lot of slots, but there are a lot of places you can use props to replace them
I think too many slots will make the code too bloated, whether to provide props or directives to make it easier to use

code too bloated, whether to provide

In my pointer of view, if something is more of just inserting some DOM in, a slot is enough. prefix and suffix are some of them.
If we provide a prop, it means it may contain some logic in it (or it need types).
I'm not a fan of everything should be in template.


added IST to CET Calculator

Fixes Issue🛠
Closes #1312
Description👨💻
Implemented IST to CET time zone converter functionality.
Type of Change📄

[ ] Bug fix (non-breaking change which fixes a bug)
[x] New feature (non-breaking change which adds functionality)
[ ] Style (non-breaking change which improves website style or formatting)
[ ] Documentation (non-breaking change which updates or adds documentation)
[ ] Responsiveness (non-breaking change which improves UI/UX on different screen sizes)

Checklist✅

[x] I am an Open Source contributor
[x] I have performed a self-review of my code
[x] My code follows the style guidelines of this project
[x ] I have commented on my code, particularly in hard-to-understand areas

Screenshots/GIF📷

@Rakesh9100  i have added cal please review this PR and accept it

@GAGGZ1 Please fix the issue.

There is missing >

Also, add your calculator in alphabetical order.

We already have Time Zone Calculator which does this conversion as well @GAGGZ1


[TERRA-383] add comment to getAllTestTagsToRun, cleanup

Add comment to getAllTestTagsToRun (in / out)
Cleanup of compiler and IDE warnings
No functional change

Failure unrelated to current change - https://scans.gradle.com/s/ccunqtwfwcota/tests/:runTestsWithTag/unit.GcsObjectReferenced?top-execution=1


Outdated

This page is significantly out of date and should be updated.

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

ID: 06eed28a-51cd-9282-0364-680c7fa98bd8
Version Independent ID: ce2aace1-9078-6ad1-39f1-fc90a7c72312
Content: How to administer Azure Cache for Redis
Content Source: articles/azure-cache-for-redis/cache-administration.md
Service: cache
GitHub Login: @yegu-ms
Microsoft Alias: yegu

@DarinMacRae We are looking into this and will get back to you.

@DarinMacRae Thank you for the feedback.
Yes, the features are out of preview and the screenshots can be updated.
Please comment and let us know if you would like to see any other content added/updated.
This issue is being assigned to the content author to evaluate and update as appropriate.

@yegu-ms Please help in getting this document updated.

@DarinMacRae Thanks for your feedback! We've updated the contents and screenshots.

#please-close


Include flogger-system-backend in library pom as a runtime dep

If we make flogger-system-backend a runtime dependency in google-cloud-pubsublite/pom.xml, do we still need to specify it for samples? The goal is to clean up dependencies in the samples pom.xml if possible: https://github.com/googleapis/java-pubsublite/blob/30a276bc600662066839c9e8027856673fc2f1d9/samples/snippets/pom.xml#L44-L64
Cc: @BenWhitehead

The thing is, I don't think flogger-system-backend is a runtime dep. SOME system backend is, but it could just as easily be a remote logger instead of a stdout one

Part of the issue as the pom.xml stand right now is that it is not possible for a user to run the pubsub lite client without picking a flogger backend due to the following exception being thrown.
java.lang.ExceptionInInitializerError
  at com.google.common.flogger.backend.Platform.getCallerFinder(Platform.java:160)
  at com.google.common.flogger.GoogleLogger.forEnclosingClass(GoogleLogger.java:48)
  at com.google.cloud.pubsublite.internal.wire.RetryingConnectionImpl.<clinit>(RetryingConnectionImpl.java:48)
  at com.google.cloud.pubsublite.internal.wire.PublisherImpl.<init>(PublisherImpl.java:109)
  at com.google.cloud.pubsublite.internal.wire.PublisherImpl.<init>(PublisherImpl.java:129)
  at com.google.cloud.pubsublite.internal.wire.PublisherBuilder$Builder.build(PublisherBuilder.java:129)
  at com.google.cloud.pubsublite.internal.wire.SinglePartitionPublisherBuilder$Builder.build(SinglePartitionPublisherBuilder.java:73)
  at com.google.cloud.pubsublite.internal.wire.RoutingPublisherBuilder$Builder.build(RoutingPublisherBuilder.java:76)
  at com.google.cloud.pubsublite.cloudpubsub.PublisherSettings.instantiate(PublisherSettings.java:100)
  at com.google.cloud.pubsublite.cloudpubsub.Publisher.create(Publisher.java:26)
  at com.google.cloud.testing.PubSubLiteTesting.publishMessages(PubSubLite.java:113)
  ...

It is correct that a user could choose to pick a different backend for their environment, but right now we're pushing an incomplete library definition. With maven, gradle etc it's possible for a user to exclude a library and swap to a different backend if they prefer it.
For those users which are using std/err logging (which is the vast majority) I think it makes sense to provide a default backend which works out of the box.
The above exception can be seen by trying to run the "Publishing Messages" code sample here  with the following pom.xml
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.google.cloud.testing</groupId>
  <artifactId>pubsub-lite-testing</artifactId>
  <version>0.1.0-SNAPSHOT</version>

  <properties>
    <maven.compiler.target>1.8</maven.compiler.target>
    <maven.compiler.source>1.8</maven.compiler.source>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
  </properties>

  <dependencies>
    <dependency>
      <groupId>com.google.cloud</groupId>
      <artifactId>google-cloud-pubsublite</artifactId>
      <version>0.2.0</version>
    </dependency>
  </dependencies>
</project>


Fix arrows in primitive type promotion diagram

Made the arrows to make sense and match the description below.
(Seeing the diagram, I was baffled by the idea of promoting an Int32 to a Float32.)

Docs are a WIP at the moment until the language is more or less finalized. But thanks for your changes :)


[KOGITO-4957] - Handling HTTP CloudEvents requests without Content-Type

Many thanks for submitting your Pull Request :heart:!
In this PR, we reevaluate the "Consumes" header of the CloudEvent HTTP Listener endpoint. Now, we do accept everything and try to parse the data field as JSON internally. This is needed because a client might send an HTTP request without specifying a Content-Type. In this case, the CE SDK will treat it as a BINARY format, so the data will be serialized to base64 data by Jackson.
To avoid this, in situations like this, we try to parse the data to JSON before pushing the message to internal channels. Then, if it's not a JSON message, we fail beautifully.
See: https://issues.redhat.com/browse/KOGITO-4957
Please make sure that your PR meets the following requirements:

[x] You have read the contributors guide
[x] Your code is properly formatted according to this configuration
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[x] Pull Request contains link to the JIRA issue
[x] Pull Request contains link to any dependent or related Pull Request
[x] Pull Request contains description of the issue
[x] Pull Request does not include fixes for issues other than the main ticket

How to retest this PR or trigger a specific build:

Pull Request
Please add comment: Jenkins retest this

Quarkus LTS checks
Please add comment: Jenkins run LTS

Native checks
Please add comment: Jenkins run native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

The Linux check is successful.

OH MY GOD, IT'S GREEN!
Please don't make me do any modifications to this PR. :laughing:

Hey,
Tested with the reproducer and works fine :)
cheers


Syntax error in Log custom telemetry in JavaScript functions

[Enter feedback here]
https://docs.microsoft.com/en-us/azure/azure-functions/functions-monitoring?tabs=cmd#log-custom-telemetry-in-javascript-functions
client.trackException has a missing }

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

ID: 13672b67-22ea-3dda-8b6b-3332c24e6030
Version Independent ID: fdc60aeb-9971-1d9f-a6ba-b3ad818cf0d5
Content: Monitor Azure Functions
Content Source: articles/azure-functions/functions-monitoring.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@aliabbasmanager Thank you for your feedback! We will review and update as appropriate.

@aliabbasmanager Thanks for reporting this item! I have updated the doc and it will be published soon. We appreciate the feedback!


[FEATURE] Support for common pydantic types

It will be great to add support for common pydantic types, namely EmailStr and HttpUrl. Possible?
The obvious use case is to pass and emails and HTTP URLs strings as command line parameters and being validated automagically - similar to what FastAPI does.

P.S. @tiangolo many thanks for creating another gem!

I have immediate usecases for pydantic.FilePath, pydantic.DirectoryPath, and the pydantic.con- types (conint, confloat, ...)

Hello,
I encountered this issue while trying to use email, IP addresses and urls as parameters.
I did some experiments so I'm sharing thoughts:

Currently Typer doesn't depend on pydantic, and supporting pydantic native types would add an extra dependency that not everyone may want
Besides Pydantic, users may want to use other kinds of data types that may just be subclasses of str, int or whatever plain data type.
Pydantic types are not consistent in the way you may do conversion to them. For instance, EmailStr.validate takes a simple value argument, and will return a regular str, while AnyHttpUrl will require FieldInfo and BaseConfig arguments on top.

My experiment was therefore not opinionated on supporting pydantic but rather supporting "any kind of str or int subclass".
I changed get_click_type's
if annotated == str:
    return click.STRING

to a later
elif issubclass(annotated, str):
    return click.STRING

It is important to defer it as one of the latest cases, because it is not uncommon to have subclasses of Enum to be also subclasses of int or str see StrEnum coming in 3.11, which we want to still fall into click.CHOICE.
With this change in mind, we've got half of the original request: we can annotate our code with the actual expected data. What's missing is the automagical conversion to the expected type when the callback gets executed.
To me, it's not a big deal to wrap it with @pydantic.validate_arguments decorator to get it done, and it avoids an unnecessary dependency.
All that being said, I would like to thank you @tiangolo for the great and inspirational work you do with your libraries ❤ , and I'd really be eager to contribute if you accept my proposal of simplified implementation of this ticket.

Hi I am trying to pass a URL as a parameter, hence check it is valid so this feature would be great. Any update on it? Thanks!

Hello,
I've made a recent attempt to progress on the topic in order to propose a pull request.
Unfortunately, I've discovered that some pydantic types, such as EmailStr or HttpUrl, which were previously subclasses of str are no longer so in pydantic 2.
However, I've therefore dug a little bit further and realised that you may specify click_type in the parameter_info
Consider the following snippet:
app = Typer()

EmailArg = Annotated[EmailStr, Argument(click_type=click.STRING)]

@app.command("something_with_email")
@validate_arguments
def something(user_email: EmailArg):
    print(user_email)

if __name__=='__main__':
    app()

It's enough IMO to do the job, and if you want to go even further, it's possible to even plug a callback function to the argument to catch a pydantic error and return a typer Exception
def validate_email(ctx: Context, value: str):
    if ctx.resilient_parsing: # handling autocompletion
        return
    try:
        return EmailStr._validate(value, None) # this one is a bit hacky but just for the sake of demo
    except ValueError as exc:
        raise BadParameter(str(exc)) from exc

EmailArg = Annotated[EmailStr, Argument(click_type=click.STRING, callback=validate_email)]

@app.command("something_with_email")
def something(user_email: EmailArg):
    print(user_email)

however there are hacky parts here and there in code above, which I'd be delighted to not have to put in my production code, but I think we'd need a strong statement from @tiangolo or core team of this repository whether we want to go or not into adding pydantic as strong dependency for typer.

Update on this ticket, I've found some free time to work a bit on a tryout for pydantic types integration while still keeping it an optional dependency.
I'll write some more tests, and polish a bit the code before I submit something.

Note for people coming here from Google who really want pydantic support: There are extensions/alternatives to typer that enable pydantic types for Python CLIs. Here's a quick overview from most to least similar to typer:
pydantic-typer

Note: I created pydantic-typer for personal use.
A thin wrapper around typer that addresses this issue as well as the issue described in Typer issue #111.
Fully compatible with typer; just replace typer.run with pydantic_typer.run. Tested against the entire typer test suite.

feud
Feud is essentially a wrapper around Click that takes classes and functions with type hints and intelligently 'compiles' them into a ready-to-use Click generated CLI.
The author compares it to typer here:

Typer is a more complete library for building CLIs overall, but currently lacks support for more complex types, such as those offered by Pydantic.

cyclopts
From the author:

Cyclopts is what you thought Typer was. Cyclopts includes information from docstrings, supports more complex types (even Unions and Literals!), and includes proper validation support.

There is a detailed comparison between typer and cyclopts. Two main differences are:

cyclopts uses the Annotation syntax exclusively, allowing most cyclopts functions to be callable from regular Python code as well. In contrast, typer also allows defining Options and Arguments using proxy default values for function parameters.
cyclopts doesn’t use click but implements its own parser.


@apply directive doesn't work with Postcss imports

Environment

Operating System: Linux
Node Version:     v16.14.2
Nuxt Version:     3.0.0-rc.12
Nitro Version:    0.6.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      modules, postcss, css
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://stackblitz.com/edit/github-ih6nny
Describe the bug
Styles are not applied to class written in the .pcss file imported by another .pcss file.

The workaround is to place all pcss files into nuxt.config.ts CSS array, which looks quite ugly


Extends default partitions for overcloud nodes

It uses a custom overcloud-node-growvols playbook to extend the partitions.
This PR resolves https://github.com/redhat-performance/jetpack/issues/483

LGTM

LGTM

@kemmy22 can you rebase this PR?

@masco Resolved Merge Conflicts.


[3.0] Sprite3D and ImmediateGeometry doesn't show any geometry

Operating system or device - Godot version:
OS: Windows 10
Version: last build from master
Issue description:
Sprite3D and ImmediateGeometry render doesn't work
Steps to reproduce:

Create new project
Add Sprite3D to scene
Add texture to sprite

Example project
Test3d.zip

I've also had this issue with Sprite3D and AnimatedSprite3D in Ubuntu Linux


"sub X by NULL" is (sadly) acceptable

There's a terrible hack that's not in the FEA specification, but is used by a number of fonts. It's possible to use multiple substitution to delete a glyph; this is supported by the spec, in fonttools and makeotf.
Because you can do sub X by NULL you can also do sub a X' by NULL; but currently fea-rs pulls a face at this:
error: Expected glyph class features.fea at 4004:22
     |
4004 | sub @All.Medis r0' by NULL;

okay I think this is just an oversight in the parsing of contextual lookups, we do support the sub X by NULL syntax in non-contextual... contexts. Will take a look. :)

I guess this means we should also support,
sub @someclass a';

to be an implied by NULL?

I don't think we need an implied one, no - the syntax for deleting is sub <single glyph> by NULL, nothing else. But we need both x by NULL; and <context> x' <context> by NULL;

I was just thinking of how in various places the spec says, "Omitting the by clause is equivalent to adding by NULL".

oh also: this repo has moved into fontc, I'll see about moving this issue over there.


Pass cookies to EventSource request

Currently EventSource request is initialized with no document cookies passed, which in most cases (lost session) disables fine reproduction of real website behavior.
According to eventsource documentation they can be easily passed.

Pushed update that fixes that, issue is now a Pull Request


Remove NEXUS_SHOULD_GENERATE_ARTIFACTS

We will revert #243 because we have decided to officially make nexus a lower level tool optimized for higher order tooling first and foremost.
We should do this in two steps:

Deprecate #243 in 0.12.x
Outright remove it in 0.13.x

Users can use a higher order tool (at Prisma we're kicking off work on a prototype soon), build/use plugins, or just inline logic like as follows:
makeSchema({
  shouldGenerateArtifacts: process.env.NEXUS_SHOULD_GENERATE_ARTIFACTS === 'true' || process.env.NODE_ENV !== 'production',
  // ...
})

I do not plan on removing this in two steps, it was only ever available via a beta release (only relatively recently), and it has already been removed in #242 and is documented in the changelog on that branch as such.
There are now console warnings if the outputs is missing and better documentation. Going to close this, as the work for removing this has already been done, as well as porting the relevant logic to https://github.com/prisma-labs/nexus-prisma/pull/521 if you plan for more of a graceful degradation strategy there.


Move to GitHub actions

This PR adds github actions based on https://github.com/ueberauth/ueberauth_example/pull/55#pullrequestreview-317990768
Now, to enable the actions I think that needs a collaborator to turn it on, on the Actions tab.

Amazing! Thank you very much


Can you please attach a license file to this code.

I would like to use this code to control some stepper motors. Currently without a license file I don't know what are the terms of use.
For my project code, I will be adding a MIT licence before making it public.

done


Toggle Noclip debug hotkey

Ctrl+N to toggle noclip in the world or battles

Please make different PRs for different things. Anyway, the reason why we don't use the tension function is because it caps the tension to 100%, while the debug key was for 200% (to test Snowgrave).


Improve test project settings, contributing docs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>3:
0.0%

Covered Lines:
1448

Relevant Lines:
1448

💛  - Coveralls


JSON.parse is called on response

Added parsing response and errors via JSON.parse in _request method. Now it is easier to handle responses from bot methods.

Checks are not passed because the environment variables are not set, e.g. Error: Bot token not provided. Tests successfully pass on my machine.

Closing PR to reopen from another branch


add GitHub Actions workflow for DCO check

Change log description
Adds a new GitHub Actions workflow to run in parallel to the build/test/coverage workflow.
Purpose of the change
To enforce Developer Certificate of Origin signoffs.
What the code does
Adds a step that checks git commits for Signed-off-by.
How to verify it
This PR should run the check.

These changes have been incorporated into PR #4.


LeftNav Restyle

@diogoperillo I changed the base branch to master as the graphql branch got merged, let's not use this one for integration anymore.

Sounds good. I fixed the build.


background-*.jpg is not working

If no pictures the mask background-*.jpg or *, the task results in an error.
the task must be turned off manually until it is needed and should include when the pictures appear.
Error:
Message:
    Available images do not match the following config:
  - `background-*.jpg`
  - `background-*.jpg`
  - `background-*.jpg`
Details:
    domainEmitter: [object Object]
    domain: [object Object]
    domainThrown: false

Please add the correct handling of such situations without completing the task fail.
Thank you! :)

close please.
a solution was found in the configs: errorOnUnusedConfig

Hi @slavikse thanks 😉


fix: add ac - quantum updates on enactment

Fix/quantum updates on enactment ac

closing as covered in:

https://github.com/vegaprotocol/specs/pull/2056


Is v3 officially released?

Description:
I got a PR from Renovate bot bumping the setup-java action to v3.
Task version:
v3:
     - uses: actions/setup-java@v3
        with:
          java-version: 17
          distribution: adopt
          cache: gradle

Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Repro steps:
https://github.com/artamonovkirill/ninshubur/pull/189
Expected behavior:
CI step succeeds
Actual behavior:
CI steps fails due to out-of-range error:
Run actions/setup-java@v3
  with:
    java-version: 17
    distribution: adopt
    cache: gradle
    java-package: jdk
    architecture: x64
    check-latest: false
    server-id: github
    server-username: GITHUB_ACTOR
    server-password: GITHUB_TOKEN
    overwrite-settings: true
    job-status: success
Trying to resolve the latest version from remote
Resolved latest version as 17.0.[2](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:2)+8
Trying to download...
Downloading Java 17.0.2+8 (Adopt-Hotspot) from https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.2%2B8/OpenJDK17U-jdk_x64_linux_hotspot_17.0.2_8.tar.gz ...
Extracting Java archive...
/usr/bin/tar xz --warning=no-unknown-keyword -C /home/runner/work/_temp/db9051e8-02a1-4d70-a166-91e[3](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:3)325db[4](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:4)[5](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:5)0 -f /home/runner/work/_temp/03d793fc-d48f-4a35-ba8c-beb8[6](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:6)95bfd11
Java 1[7](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:7).0.2+[8](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:8) was downloaded
Setting Java 17.0.2+8 as the default

Java configuration:
  Distribution: adopt
  Version: 17.0.2+8
  Path: /opt/hostedtoolcache/Java_Adopt_jdk/17.0.2-8/x64

Creating settings.xml with server-id: github
Writing to /home/runner/.m2/settings.xml
Received 58720256 of 2[9](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:9)35425672 (2.0%), 56.0 MBs/sec
Received 167772160 of<PHONE_NUMBER> (5.7%), 80.0 MBs/sec
Received 327155712 of<PHONE_NUMBER> (11.1%), [10](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:10)3.7 MBs/sec
Received 528482304 of<PHONE_NUMBER> (18.0%), 125.7 MBs/sec
Received 717225984 of<PHONE_NUMBER> (24.4%), 136.5 MBs/sec
Received 910163968 of<PHONE_NUMBER> (31.0%), 144.4 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (37.4%), 149.4 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (43.7%), 152.7 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (48.7%), 151.3 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (54.4%), 152.2 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (59.9%), 152.2 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (64.6%), 150.5 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (69.7%), 150.0 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (74.0%), 147.8 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (78.2%), 145.7 MBs/sec
Received 2420[11](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:11)3408 of<PHONE_NUMBER> (82.4%), [14](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:14)4.1 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (86.7%), 142.7 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (91.4%), 142.1 MBs/sec
Received 2831[15](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:15)5[20](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:20)0 of<PHONE_NUMBER> (96.4%), 141.9 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (100.0%), 140.6 MBs/sec
Error: The value of "length" is out of range. It must be >= 0 && <= [21](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:21)47483647. Received 29354[25](https://github.com/artamonovkirill/ninshubur/runs/5359803125?check_suite_focus=true#step:6:25)672

I, too, am experiencing a similar issue. example execution link
Snippet of task output:
Run actions/setup-java@f69f00b5e53[2](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:2)4696b07f6b1c92f0470a6df00780
  with:
    distribution: zulu
    java-version: 11
    cache: gradle
    java-package: jdk
    architecture: x64
    check-latest: false
    server-id: github
    server-username: GITHUB_ACTOR
    server-password: GITHUB_TOKEN
    overwrite-settings: true
    job-status: success
Trying to resolve the latest version from remote
Resolved latest version as 11.0.14+9
Trying to download...
Downloading Java 11.0.14+9 (Zulu) from https://cdn.azul.com/zulu/bin/zulu11.54.2[3](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:3)-ca-jdk11.0.1[4](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:4)-linux_x64.tar.gz ...
Extracting Java archive...
/usr/bin/tar xz --warning=no-unknown-keyword -C /home/runner/work/_temp/[5](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:5)bec91df-a7[6](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:6)8-4c41-bff2-f09233f6ee10 -f /home/runner/work/_temp/f3[7](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:7)004f6-715f-409d-9[8](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:8)82-8b4661[9](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:9)1bd8b
Java 11.0.14+9 was downloaded
Setting Java 11.0.14+9 as the default

Java configuration:
  Distribution: zulu
  Version: 11.0.14+9
  Path: /opt/hostedtoolcache/Java_Zulu_jdk/11.0.14-9/x64

Creating settings.xml with server-id: github
Writing to /home/runner/.m2/settings.xml
Received 0 of<PHONE_NUMBER> (0.0%), 0.0 MBs/sec
Received 83886080 of<PHONE_NUMBER> (3.1%), 40.0 MBs/sec
Received 209715200 of<PHONE_NUMBER> (7.7%), 66.6 MBs/sec
Received 322961408 of<PHONE_NUMBER> (11.8%), 76.9 MBs/sec
Received 452984832 of<PHONE_NUMBER> (16.6%), 86.3 MBs/sec
Received 562036736 of<PHONE_NUMBER> (20.6%), 89.3 MBs/sec
Received 662700032 of<PHONE_NUMBER> (24.2%), 90.2 MBs/sec
Received 784334848 of<PHONE_NUMBER> (28.7%), 93.4 MBs/sec
Received 89758[10](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:10)56 of 2734770[11](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:11)3 (32.8%), 95.1 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (36.8%), 96.0 MBs/sec
Received 1[12](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:12)4073472 of 27347701[13](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:13) (41.1%), 97.4 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (44.9%), 97.6 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (48.9%), 98.1 MBs/sec
Received [14](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:14)47034880 of<PHONE_NUMBER> (52.9%), 98.5 MBs/sec
Received [15](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:15)60281088 of<PHONE_NUMBER> (57.1%), 99.1 MBs/sec
Received [16](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:16)73527296 of<PHONE_NUMBER> (61.2%), 99.7 MBs/sec
Received [17](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:17)82579200 of<PHONE_NUMBER> (65.2%), 99.9 MBs/sec
Received [18](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:18)79048[19](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:19)2 of<PHONE_NUMBER> (68.7%), 99.5 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (72.4%), 99.3 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (76.8%), 100.1 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (81.0%), 100.5 MBs/sec
Received 233[20](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:20)33024 of<PHONE_NUMBER> (85.3%), 101.0 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (89.3%), 101.1 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (92.9%), 100.9 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (96.6%), 100.7 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (99.2%), 99.4 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (100.0%), 99.2 MBs/sec
Error: The value of "length" is out of range. It must be >= 0 && <= [21](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:21)47483647. Received [27](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:27)[34](https://github.com/ChrisCarini/environment-variable-settings-summary-intellij-plugin/runs/5630609896?check_suite_focus=true#step:3:34)770113

I'm seeing a similar problem, except it gives me a warning instead of an error. So subsequent steps can still complete, but are very slow since apparently there is no cache.

Hello everyone. We prepared a fix and updated the major tag with these changes. Could you please confirm that everything works as expected ?

The setup step succeeds now!
Run actions/setup-java@v3
Trying to resolve the latest version from remote
Resolved latest version as 17.0.2+8
Trying to download...
Downloading Java 17.0.2+8 (Adopt-Hotspot) from https://github.com/adoptium/temurin17-binaries/releases/download/jdk-17.0.2%2B8/OpenJDK17U-jdk_x64_linux_hotspot_17.0.2_8.tar.gz ...
Extracting Java archive...
/usr/bin/tar xz --warning=no-unknown-keyword -C /home/runner/work/_temp/757b372f-37bf-4f27-93d4-5928ea1d7cf8 -f /home/runner/work/_temp/dfe4c63f-fc30-4755-b2f6-30aa06690bf8
Java 17.0.2+8 was downloaded
Setting Java 17.0.2+8 as the default

Java configuration:
  Distribution: adopt
  Version: 17.0.2+8
  Path: /opt/hostedtoolcache/Java_Adopt_jdk/17.0.2-8/x64

Creating settings.xml with server-id: github
Writing to /home/runner/.m2/settings.xml
Received 234881024 of<PHONE_NUMBER> (8.0%), 221.3 MBs/sec
Received 528482304 of<PHONE_NUMBER> (18.0%), 249.4 MBs/sec
Received 792723456 of<PHONE_NUMBER> (27.0%), 247.6 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (36.0%), 248.7 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (45.9%), 254.0 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (55.6%), 256.5 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (64.6%), 255.8 MBs/sec
Received 2[14](https://github.com/artamonovkirill/ninshubur/runs/5793264375?check_suite_focus=true#step:6:14)7483647 of<PHONE_NUMBER> (73.2%), 135.0 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (78.4%), 135.8 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (83.0%), 135.4 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (87.4%), 134.7 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (92.4%), 135.0 MBs/sec
Received 28479324[15](https://github.com/artamonovkirill/ninshubur/runs/5793264375?check_suite_focus=true#step:6:15) of<PHONE_NUMBER> (97.0%), 134.7 MBs/sec
Received<PHONE_NUMBER> of<PHONE_NUMBER> (100.0%), 119.3 MBs/sec
Cache Size: ~2799 MB<PHONE_NUMBER> B)
/usr/bin/tar --use-compress-program zstd -d -xf /home/runner/work/_temp/c7552e25-fb8b-46f7-866a-b5002cf1cb3d/cache.tzst -P -C /home/runner/work/ninshubur/ninshubur
Cache restored successfully
Cache restored from key: setup-java-Linux-gradle-6ced1418278f67deda07f1d033aa9a4486e3c[16](https://github.com/artamonovkirill/ninshubur/runs/5793264375?check_suite_focus=true#step:6:16)573ab59694[37](https://github.com/artamonovkirill/ninshubur/runs/5793264375?check_suite_focus=true#step:6:37)f0ff61e0f79e4


cant play midi

Description
any instrument ive tried including musician pda says i dont have fluidsynth
i do have it and it works fine on upstream, maybe missing an upstream fix pr merge?
Reproduction

get musician pda in ruin
cant play it

Additional context
using pipewire 0.3.71 on linux 6.1.29

Thank you for your report. We'll look if there has been a recent change to fluidsynth support that would fix your issue.

Could you let me know what version of fluidsynth you have installed? Alternatively, let me know if engine version v<IP_ADDRESS> fixes the issue for you?

ok i figured out why
something upstream changed so that it no longer checks for fluidsynth in /bin/loader so you dont need to make a symlink
ms needs this change merged or you can just ln -s


CLI test failure

I'm trying to run the tests locally (mimicking steps in the Travis-Ci configuration file), but I get this error:
$ docker exec -it sge_master /bin/bash -c "cd /dask-drmaa; py.test dask_drmaa/cli -vs --tb=native"
========================================================== test session starts ==========================================================
platform linux -- Python 3.6.0, pytest-3.0.7, py-1.4.33, pluggy-0.4.0 -- /opt/anaconda/bin/python
cachedir: .cache
rootdir: /dask-drmaa, inifile:
collected 1 items

dask_drmaa/cli/tests/test_dask_drmaa.py::test_dask_drmaa distributed.utils - ERROR - Timed out trying to connect to 'tcp://<IP_ADDRESS>:8786' after 5 s: ConnectionRefusedError: [Errno 111] Connection refused
Traceback (most recent call last):
  File "/opt/anaconda/lib/python3.6/site-packages/distributed/comm/core.py", line 169, in connect
    quiet_exceptions=EnvironmentError)
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
    value = future.result()
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
    raise_exc_info(self._exc_info)
  File "<string>", line 4, in raise_exc_info
tornado.gen.TimeoutError: Timeout

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/opt/anaconda/lib/python3.6/site-packages/distributed/utils.py", line 212, in f
    result[0] = yield make_coro()
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
    value = future.result()
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
    raise_exc_info(self._exc_info)
  File "<string>", line 4, in raise_exc_info
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1063, in run
    yielded = self.gen.throw(*exc_info)
  File "/opt/anaconda/lib/python3.6/site-packages/distributed/client.py", line 518, in _start
    yield self._ensure_connected(timeout=timeout)
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
    value = future.result()
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
    raise_exc_info(self._exc_info)
  File "<string>", line 4, in raise_exc_info
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1063, in run
    yielded = self.gen.throw(*exc_info)
  File "/opt/anaconda/lib/python3.6/site-packages/distributed/client.py", line 550, in _ensure_connected
    connection_args=self.connection_args)
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
    value = future.result()
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
    raise_exc_info(self._exc_info)
  File "<string>", line 4, in raise_exc_info
  File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1063, in run
    yielded = self.gen.throw(*exc_info)
  File "/opt/anaconda/lib/python3.6/site-packages/distributed/comm/core.py", line 178, in connect
    _raise(error)
  File "/opt/anaconda/lib/python3.6/site-packages/distributed/comm/core.py", line 161, in _raise
    raise IOError(msg)
OSError: Timed out trying to connect to 'tcp://<IP_ADDRESS>:8786' after 5 s: ConnectionRefusedError: [Errno 111] Connection refused

Print from stderr
=================
b'distributed.scheduler - INFO -   Scheduler at:    tcp://<IP_ADDRESS>:32890\n'b'distributed.scheduler - INFO -       bokeh at:              <IP_ADDRESS>:8787\n'b'distributed.scheduler - INFO - Scheduler closing...\n'b'distributed.scheduler - INFO - Scheduler closing all comms\n'

Print from stdout
=================
FAILED

Judging by the stderr, it seems expected that connecting to tcp://<IP_ADDRESS>:8786 fails if the scheduler is actually listening on tcp://<IP_ADDRESS>:32890 (i.e. on a different IP and port)...

The scheduler is created on the local machine (with LocalCluster) so the IP
difference shouldn't matter.  I can't explain the port difference.
On Thu, May 18, 2017 at 2:57 AM, Antoine Pitrou<EMAIL_ADDRESS>wrote:

I'm trying to run the tests locally (mimicking steps in the Travis-Ci
configuration file), but I get this error:
$ docker exec -it sge_master /bin/bash -c "cd /dask-drmaa; py.test dask_drmaa/cli -vs --tb=native"
========================================================== test session starts ==========================================================
platform linux -- Python 3.6.0, pytest-3.0.7, py-1.4.33, pluggy-0.4.0 -- /opt/anaconda/bin/python
cachedir: .cache
rootdir: /dask-drmaa, inifile:
collected 1 items
dask_drmaa/cli/tests/test_dask_drmaa.py::test_dask_drmaa distributed.utils - ERROR - Timed out trying to connect to 'tcp://<IP_ADDRESS>:8786' after 5 s: ConnectionRefusedError: [Errno 111] Connection refused
Traceback (most recent call last):
File "/opt/anaconda/lib/python3.6/site-packages/distributed/comm/core.py", line 169, in connect
quiet_exceptions=EnvironmentError)
File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
value = future.result()
File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
raise_exc_info(self._exc_info)
File "", line 4, in raise_exc_info
tornado.gen.TimeoutError: Timeout
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/anaconda/lib/python3.6/site-packages/distributed/utils.py", line 212, in f
result[0] = yield make_coro()
File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
value = future.result()
File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
raise_exc_info(self._exc_info)
File "", line 4, in raise_exc_info
File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1063, in run
yielded = self.gen.throw(*exc_info)
File "/opt/anaconda/lib/python3.6/site-packages/distributed/client.py", line 518, in _start
yield self._ensure_connected(timeout=timeout)
File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
value = future.result()
File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
raise_exc_info(self._exc_info)
File "", line 4, in raise_exc_info
File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1063, in run
yielded = self.gen.throw(*exc_info)
File "/opt/anaconda/lib/python3.6/site-packages/distributed/client.py", line 550, in _ensure_connected
connection_args=self.connection_args)
File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1055, in run
value = future.result()
File "/opt/anaconda/lib/python3.6/site-packages/tornado/concurrent.py", line 238, in result
raise_exc_info(self._exc_info)
File "", line 4, in raise_exc_info
File "/opt/anaconda/lib/python3.6/site-packages/tornado/gen.py", line 1063, in run
yielded = self.gen.throw(*exc_info)
File "/opt/anaconda/lib/python3.6/site-packages/distributed/comm/core.py", line 178, in connect
_raise(error)
File "/opt/anaconda/lib/python3.6/site-packages/distributed/comm/core.py", line 161, in _raise
raise IOError(msg)
OSError: Timed out trying to connect to 'tcp://<IP_ADDRESS>:8786' after 5 s: ConnectionRefusedError: [Errno 111] Connection refused
Print from stderr
b'distributed.scheduler - INFO -   Scheduler at:    tcp://<IP_ADDRESS>:32890\n'b'distributed.scheduler - INFO -       bokeh at:              <IP_ADDRESS>:8787\n'b'distributed.scheduler - INFO - Scheduler closing...\n'b'distributed.scheduler - INFO - Scheduler closing all comms\n'
Print from stdout
FAILED
Judging by the stderr, it seems expected that connecting to tcp://
<IP_ADDRESS>:8786 fails if the scheduler is actually listening on tcp://
<IP_ADDRESS>:32890 (i.e. on a different IP and port)...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-drmaa/issues/26, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszJSixb7m8w5U110ginOaZgIiuxyUks5r7BYXgaJpZM4Ne_eg
.

Now it also fails on Travis-CI:
https://travis-ci.org/dask/dask-drmaa/builds/235681387#L1830
I think the reason is that I changed LocalCluster to listen on a random port by default, rather than port 8786. I was assuming that LocalClusters are always used with Client(cluster), not for connecting independently...

I included a fix in https://github.com/dask/dask-drmaa/pull/29.