v3.0.0 with Node v12/NPM 6.9.0 gives "TypeError: fsevents is not a constructor"

Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes, tried clean install use Node v12 and NPM 6.9.0
Which terms did you search for in User Guide?
Anything about fsevents errors.
Environment
System:
OS: macOS 10.14.4
CPU: x64 Intel(R) Core(TM) i7-4960HQ CPU @ 2.60GHz
Binaries:
Node: 12.0.0 - /usr/local/bin/node
Yarn: 1.15.2 - ~/.npm-global/bin/yarn
npm: 6.9.0 - ~/.npm-global/bin/npm
Browsers:
Chrome: 73.0.3683.103
Safari: 12.1
npmPackages:
react: ^16.8.6 => 16.8.6
react-dom: ^16.8.6 => 16.8.6
react-scripts: 3.0.0 => 3.0.0
npmGlobalPackages:
create-react-app: 2.1.8
Don't know why it says create-react-app: 2.1.8, if I do npm show create-react-app version it echos 3.0.0.
Steps to Reproduce
Install with NPM 6.9.0
Expected Behavior
npm start starts the server
Actual Behavior
fsevents throws:
/Users/.../node_modules/chokidar/lib/fsevents-handler.js:28
  return (new fsevents(path)).on('fsevent', callback).start();
          ^

TypeError: fsevents is not a constructor
    at createFSEventsInstance (/Users/.../Projects/fileflow/app/node_modules/chokidar/lib/fsevents-handler.js:28:11)
    at setFSEventsListener (/Users/.../Projects/fileflow/app/node_modules/chokidar/lib/fsevents-handler.js:82:16)
    at FSWatcher.FsEventsHandler._watchWithFsEvents (/Users/.../Projects/fileflow/app/node_modules/chokidar/lib/fsevents-handler.js:252:16)
    at FSWatcher.<anonymous> (/Users/.../Projects/fileflow/app/node_modules/chokidar/lib/fsevents-handler.js:386:25)
    at LOOP (fs.js:1622:14)
    at processTicksAndRejections (internal/process/task_queues.js:81:9)

Because even though chockidar depends on fsevents 1.2.8, it doesn't get installed, possibly due to chockidar declaring it as an optional dependency: https://github.com/paulmillr/chokidar/blob/master/package.json#L24

Instead fsevents v2 gets installed which has a different API which exports a plain object (new keyword breaks on it).
⚠ Works using yarn. (and older NPM versions as it worked on Node v11 I was using yesterday)
Reproducible Demo
Do create-create-app using NPM 6.9.0 and try to run it.

I had the same issue. How did you solve it?

Same issue...
TypeError: fsevents is not a constructor
node: v12.0.0
npm: 6.9.0
create-react-app: 3.0.0

I had the same issue. How did you solve it?

Updated 22:30
This worked for me:

I deleted my react app because I realized I did not have yarn installed.
So I installed yarn.
Then, again I did npx create-react-app my-app, and it worked. The issue disappeared.

Other things I did:

Installed node globally
Cleared the node caché

For now you can downgrade Node, or remove node_modules and package-lock.json and do yarn install instead

This issue is very common.
See #6657 (reported by me), #2558, #3588, #4308.
Unfortunately all these threads lead to dead-ends. I've reproduced this error on a fresh, brand new iMac and on my Windows PC. For some reason it's never drawn any attention.

It looks like Node.js v12 removed v8::Handle which<EMAIL_ADDRESS>uses. See https://electronjs.org/blog/nodejs-native-addons-and-electron-5.
You can reproduce:
nvm use 12
yarn init
yarn add<EMAIL_ADDRESS>
Output:
  SOLINK_MODULE(target) Release/.node
  CXX(target) Release/obj.target/fse/fsevents.o
../fsevents.cc:43:32: error: no template named 'Handle' in namespace 'v8'
    static void Initialize(v8::Handle<v8::Object> exports);

Fix in https://github.com/fsevents/fsevents/pull/271, waiting on https://github.com/nodejs/nan/issues/849

Giving up npm and using yarn helped me.
I removed node_modules package.lock cleared npm cache with --force.
and then yarn install and yarn run...and its working!

npm run eject then start again

FYI:
For me, removing node_module and yarn.lock then running yarn fixed the issue

I solved installing yarn and then sudo forever npm and node_modules. Try this https://timonweb.com/posts/install-npm-packages-without-sudo/ for permission issues

I had the same issue. How did you solve it?

Updated 22:30
This worked for me:

I deleted my react app because I realized I did not have yarn installed.
So I installed yarn.
Then, again I did npx create-react-app my-app, and it worked. The issue disappeared.

Other things I did:

Installed node globally
Cleared the node caché

THANKS MAN!

I had the same issue. How did you solve it?

Updated 22:30
This worked for me:

I deleted my react app because I realized I did not have yarn installed.
So I installed yarn.
Then, again I did npx create-react-app my-app, and it worked. The issue disappeared.

Other things I did:

Installed node globally
Cleared the node caché

Worked for me, thanks mate!

For now you can downgrade Node, or remove node_modules and package-lock.json and do yarn install instead. Author of chokidar package said it will be fixed in upcoming v3.

This worked for me so well that I would recommend to any one in my situation, this morning.
what happen to me: I've cloned react app() from github to local machine with:

macosx (10.12.6)
Node v10.15.3 and  NPM v6.9.0
and  then I tried to "npm intall" to get down all dependencies as usual, and then I've tried to run the  devServer by running the command: " npm start " to my surprice, npm quited with error above.
For me 'destroying' the whole react app was not an option, so I have just removed the node_modules folder and also deleted the package-lock.json,  as suggested by DominicTobias  and then installed yarn globally by using the MacPorts utility
After installing yarn, I've  cd to the react app project on the local machine, and then executed the command: "yarn run start" And voilà! everything starting running as expected.
many thanks to DominicTobias

"resolutions": {
    "fsevents": "
}

Resolved the issue temporarily by adding this to my package.json.
Until chokidar releases their next version, the api is fully compatible with latest version so it should work just fine 👍

@Shahor - Did as suggested but still not working :/

@Shahor did the job for me on OS X, thanks

all my problems i've got is from fsevents
why so terrible :(

rm -rf node_modules
rm -f yarn.lock
yarn

Solve the issue

Downgrading node version solves the issue.
Please note that I have uninstalled all versions of the Node on my machine (and yarn as well), and then, instead of installing Node manually, installed nvm. This allows you to switch between different versions of Node easily.
Once nvm is installed run nvm install node to install the specific version (I have installed 10.15.3)
To change Node version run nvm use <version>
Check you're set up correctly by running node -v

Giving up npm and using yarn helped me.
I removed node_modules package.lock cleared npm cache with --force.
and then yarn install and yarn run...and its working!

This worked for me.

very good way, thanks @ majda

Same issue using node v11.10.0 and npm v6.9.0, my issue was solved as well by deleting the yarn.lock and node_modules and running yarn again. I hope this gets fixed soon - it's very annoying to do a fresh install and have it break immediately when I try to launch the app

@DominicTobias What version of node works for you? I have tried several and yet no luck

@DominicTobias What version of node works for you? I have tried several and yet no luck

The LTS version works (10.6.0), I have 10.5.3

I was recently able to resolve this issue by going into the Node_module folder and finding fsevents folder.  I changed the name of the folder to fsevent_old.  I was then able to run React without an issue.

I was able to resolve the issue with npm i -S fsevents.
I did not have any luck with @Shahor 's fix, and I didn't try any solutions involving yarn as I don't use yarn.

So chokidar@2 seems broken as pointed out in this comment.
We should use chokidar@3.
From OP's stack trace we can't see which package uses chokidar because its run async from a callback.
Go to the earliest line we have in the stack trace, and place a console.trace() outside the callback. For me it was fsevents-handler.js:333. This let me see that it was watchpack that depended on chokidar@2.
When using pnpm in a monorepo...
In a pnpm monorepo we can search for usages like so: pnpm ls --depth=100 --filter my-package chokidar
Using pnpm and pnpmfile.js it can be patched like so:
if (pkg.name === 'watchpack') {
  pkg.dependencies['chokidar'] = '3.0.1'
}

Then trigger a reinstall like so:
pnpm up --depth=100 --filter my-package

I fix this issue using this command
npm install -g chokidar

I agree with @mattrafalko, the npm i fsevents solution worked for me. I also made sure to run npm i react-scripts since I was having an issue with npm start

i tried pretty much every thing mentioned in here and nothing worked. i use yarn, though. i would rather not involve npm (we use yarn only at work). did anyone solve this with yarn?

I had the same problem because I created new project using sudo what caused permission conflict.
$ sudo npx create-react-app my-app // Did not work
$ npx create-react-app my-app
$ cd my-app && npm start      // Work like a charm`
I hope this help someone to resolve this issue.

Installing yarn fixed it for me.

I was able to resolve the issue with npm i -S fsevents.
I did not have any luck with @Shahor 's fix, and I didn't try any solutions involving yarn as I don't use yarn.

This did it for me. Thanks!!!

I had the same issue. How did you solve it?

Updated 22:30
This worked for me:

I deleted my react app because I realized I did not have yarn installed.
So I installed yarn.
Then, again I did npx create-react-app my-app, and it worked. The issue disappeared.

Other things I did:

Installed node globally
Cleared the node caché

Worked for me, thanks mate!

Yes, Its work but unfortunately we have not find the actual error to resolve that permanently.

It may seem weird, but I was able to get it working after running:
$sudo npm install npm@latest -g

I also had the same issue though am using MacOS the issue is kind of bug. I solved this issue by repeatedly running the commands,

sudo npm cache clean --force
sudo npm uninstall
sudo npm install

One time it did not worked but when I repeatedly cleaned the cache and after uninstalling npm, reinstalled npm, the error went off. Am using Angular 8 and this issue is common

I had the same problem because I created new project using sudo what caused permission conflict.
$ sudo npx create-react-app my-app // Did not work
$ npx create-react-app my-app
$ cd my-app && npm start // Work like a charm`
I hope this help someone to resolve this issue.

Thank you this worked for me!

Hello Ronan,
if you are using 'npx' to create react app then you didn't need to add
sudo command at the beginning.
If you are using 'npm' then you need (if system want super user permission)
to add at the beginning.
I hope you got it.
Regards,
MANISH VERMA.
On Sat, 3 Aug 2019, 8:33 pm Ronan Mockett<EMAIL_ADDRESS>wrote:

I had the same problem because I created new project using sudo what
caused permission conflict.
$ sudo npx create-react-app my-app // Did not work
$ npx create-react-app my-app
$ cd my-app && npm start // Work like a charm`
I hope this help someone to resolve this issue.
Thank you this worked for me!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/6891?email_source=notifications&email_token=AHTB43X5YKCKLDFEGOH4JFLQCWM3LA5CNFSM4HIIC3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3PP7UQ#issuecomment-517930962,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHTB43SWARCISEUSMDECNYTQCWM3LANCNFSM4HIIC3JA
.

You need to install the yarn before creating your app
sudo npm i -g yarn
npx create-react-app my-app
cd my-app
npm start
It have worked for me. ;)

Yes yarn is a good method to create react app.
On Mon, 5 Aug 2019, 9:48 pm marcosaimola<EMAIL_ADDRESS>wrote:

You need to install the yarn before creating your app
sudo npm i -g yarn
npx create-react-app my-app
cd my-app
npm start
It have worked for me. ;)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/6891?email_source=notifications&email_token=AHTB43QHO734B3PK2CX6MZTQDBHFNA5CNFSM4HIIC3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3SKGFI#issuecomment-518300437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHTB43UFS7AFGJCXXVUCBH3QDBHFNANCNFSM4HIIC3JA
.

sudo n 10.16.0
npx create-react-app my-app
cd my-app
npm install
npm start
my fix above

If you want to use 'npx' then you must have npm 5.2+ version in your
system.
On Tue, 6 Aug 2019, 8:59 am Luke Markham<EMAIL_ADDRESS>wrote:

sudo n 10.16.0
npx create-react-app my-app
cd my-app
npm install
npm start
my fix above
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/6891?email_source=notifications&email_token=AHTB43S2B2QFODJJADGGRMTQDDVZLA5CNFSM4HIIC3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3TWXMA#issuecomment-518482864,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHTB43TMDTNDA3RMBL7AQJLQDDVZLANCNFSM4HIIC3JA
.

use npx create-react-app my-app --use-npm

This worked for me:
npm audit fix --force

I had this problem on macOS 10.13 too while using yarn, on a brand new create-react-app. I do not have a node version set in my package.json file:
{
  "name": "star-ratings-basic",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "react-scripts": "3.1.0"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

this happened to me while using NVM (node version manager) and had these versions of node & npm active respectively
$ npm -v
node 6.10.2
$ node -v
v12.8.0

deleting my yarn.lock file & deleting the node_modules folder and then running yarn worked immediately.
interestingly, I was able to get a diff on the regenerated yarn lock file compared to the old one. as seen by git diff ( note minus and plus symbols )
-"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>+"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>   version "7.5.5"
   resolved<EMAIL_ADDRESS>   integrity sha512-27d4lZoomVyo51VegxI20xZPuSHusqbQag/ztrBC7wegWoQ1nLREPVSKSW8byhTlzTKyNE4ifaTA6lCp7JjpFw==
   dependencies:
     "@babel/highlight" "^7.0.0"

-"<EMAIL_ADDRESS>-  version "7.0.0"
-  resolved<EMAIL_ADDRESS>-  integrity sha512-OfC2uemaknXr87bdLUkWog7nYuliM9Ij5HUcajsVcMCpQrcLmtxRbVFTIqmcSkSeYRBFBRxs2FiUqFJDLdiebA==
-  dependencies:
-    "@babel/highlight" "^7.0.0"
-
 "<EMAIL_ADDRESS>"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>   version "7.5.5"
   resolved<EMAIL_ADDRESS>@@ -36,17 +29,6 @@
     semver "^5.4.1"
     source-map "^0.5.0"

-"<EMAIL_ADDRESS>-  version "7.1.3"
-  resolved<EMAIL_ADDRESS>-  integrity sha512-ZoCZGcfIJFJuZBqxcY9OjC1KW2lWK64qrX1o4UYL3yshVhwKFYgzpWZ0vvtGMNJdTlvkw0W+HR1VnYN8q3QPFQ==
-  dependencies:
-    "@babel/types" "^7.1.3"
-    jsesc "^2.5.1"
:

First update your nodejs in your system. And then if they're any issue then
please demonstrate that to us.
On Sat, 10 Aug 2019, 11:44 pm Jason Fleetwood-Boldt, <
<EMAIL_ADDRESS>wrote:

I had this problem on macOS 10.13 too while using yarn, on a brand new
create-react-app. I do not have a node version set in my package.json
file:
{
"name": "star-ratings-basic",
"version": "0.1.0",
"private": true,
"dependencies": {
"react": "^16.9.0",
"react-dom": "^16.9.0",
"react-scripts": "3.1.0"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
this happened to me while using NVM (node version manager) and had these
versions of node & npm active respectively
$ npm -v
node 6.10.2
$ node -v
v12.8.0
deleting my yarn.lock file & deleting the node_modules folder and then
running yarn worked immediately.
interestingly, I was able to get a diff on the regenerated yarn lock file
compared to the old one. as seen by git diff ( note minus and plus symbols )
-"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>+"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>version "7.5.5"
resolved<EMAIL_ADDRESS>integrity sha512-27d4lZoomVyo51VegxI20xZPuSHusqbQag/ztrBC7wegWoQ1nLREPVSKSW8byhTlzTKyNE4ifaTA6lCp7JjpFw==
dependencies:
"@babel/highlight" "^7.0.0"
-"<EMAIL_ADDRESS>
version "7.0.0"
resolved<EMAIL_ADDRESS>integrity sha512-OfC2uemaknXr87bdLUkWog7nYuliM9Ij5HUcajsVcMCpQrcLmtxRbVFTIqmcSkSeYRBFBRxs2FiUqFJDLdiebA==
dependencies:
"@babel/highlight" "^7.0.0"

"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>"<EMAIL_ADDRESS>version "7.5.5"
resolved<EMAIL_ADDRESS>@@ -36,17 +29,6 @@
semver "^5.4.1"
source-map "^0.5.0"
-"<EMAIL_ADDRESS>
version "7.1.3"
resolved<EMAIL_ADDRESS>integrity sha512-ZoCZGcfIJFJuZBqxcY9OjC1KW2lWK64qrX1o4UYL3yshVhwKFYgzpWZ0vvtGMNJdTlvkw0W+HR1VnYN8q3QPFQ==
dependencies:
"@babel/types" "^7.1.3"
jsesc "^2.5.1"
:

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/6891?email_source=notifications&email_token=AHTB43T2IWUIS5AWJFDFYCLQD4AQFA5CNFSM4HIIC3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4ASOBA#issuecomment-520169220,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHTB43QG2QDKFLW4FD56OZ3QD4AQFANCNFSM4HIIC3JA
.

with

it appears to do this for me on every create-react-app I make

I also faced that situation in my system, so I researched alot about it
then I got that, first Clean your yarn then I Cleaned my apt using 'sudo
apt clean' then 'sudo apt update' for repair and updating packages then
'sudo apt upgrade' for require upgrades to my packages.
Then create a new react app.
It might be work in your system.
On Sun, 11 Aug 2019, 8:35 am Jason Fleetwood-Boldt, <
<EMAIL_ADDRESS>wrote:

it appears to do this for me on every create-react-app I make
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/6891?email_source=notifications&email_token=AHTB43WWDNHDWMYC4MMCFRDQD56Y3A5CNFSM4HIIC3JKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4AZBQY#issuecomment-520196291,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHTB43TKXK22WHSENSGKD4LQD56Y3ANCNFSM4HIIC3JA
.

I had the same problem because I created new project using sudo what caused permission conflict.
$ sudo npx create-react-app my-app // Did not work
$ npx create-react-app my-app
$ cd my-app && npm start // Work like a charm`
I hope this help someone to resolve this issue.

This worked for me too :) Cheers!

jason@JasonsMAir11RED:momeas_com $ sudo apt update
Unable to locate an executable at "/Library/Java/JavaVirtualMachines/jdk1.8.0_152.jdk/Contents/Home/bin/apt" (-1)

incidentally I am on mac OS 10.13.6 using Xcode 9.4.1 with gcc clang version clang-9<IP_ADDRESS>
I wonder if there's a way to blow away my yarn binary to clear the problem?

some people on the reactiflux Discord channel are recommending downgrading to Node 11 until the issue is mitigated.

Hi  I just removed yarn lock and then yarn install worked for me

This worked for me:
npm audit fix --force

thanks mate. this worked for me

You need to install the yarn before creating your app
sudo npm i -g yarn
npx create-react-app my-app
cd my-app
npm start
It have worked for me. ;)

This indeed works. I struggle making my first react app to work at first, but eventually installing yarn (and use it after that) make it work, it really do the trick ✨

I no longer get this issue, tested with Node 12.7 and 12.9 using either NPM or Yarn. Thinking of closing this soon as it seems to have been resolved.

rm -rf node_modules
rm -f yarn.lock
yarn

Solve the issue

This worked for me. I had Node version: 12.8.0 on a mac


Secure admin API section needs a warning about sending credentials over http/https

I'm making a new issue from this comment: https://github.com/Kong/getkong.org/pull/545#issuecomment-341775977 . Basically we should have a place in the docs indicating that some data (like keys) should ideally be sent via https. A good candidate for doing this is the "secure admin" section.

Added a note about sending important data over https.


ci(c): factor out build scripts

WIP: also need to port the Python, GLib, Ruby, and Go builds; then we can use these build scripts from the verification script


update color picker assets & documentation to reflect LEXI-1053 changes

I've updated the Color Picker documentation and images.
@victorvalle check this is aligned with the ticket description before publishing. Thanks!

Reviewed! This can be merged.
Thanks @hold-shift !


Added clock.md to display current time

I've adding a clock.md to 30-seconds-of-code. The purpose is to display the current time to users, hope it works!
If you have any questions, feel free to ask 😃

Alright. Thank you.


Can't deprecate enum values

We recently found ourselves wishing to rename an enum value, and planned to deprecate the old value while simultaneously introducing the new value.
enum Values {
  @Deprecated('Use Values.bar')
  foo,
  bar,
}

Unfortunately, it appears as though the Deprecated annotation isn't supported on enum values, and the above example yields the following error
Enum constants can't have annotations.

What's the reasoning or technical limitation preventing this? Could we see support for this?

I don't think there is a technical problem, it was just never added to the grammar.
We can definitely consider adding it.

Okay, thanks!

FYI: The required specification update is currently under construction.

The specification update has been accepted by the language team (as of 2f781e46b01e22541cd74ab82e57e72bdea3793e).

Blocked on #33082

It should not be blocked, #33082 had no remaining tasks so I just closed it.

Analyzer and other tools don't choke on having the annotation on an enum and the analyzer correctly hints at usage points.


fix general error handling

Many times when an onunhandledrejection event occurs (there is a listener registered at app startup in src/index.js) and the app crashes, it is not easy to debug because the error message, both in console logs and the user interface, is hidden in a pile of 'intl.formatMessage is not a function (...). This is because of a bug in the function that reports the error, handleGeneralError, which was calling showErrorDialog() without providing the intl object.
To fix this, we may just call showErrorDialog() with intl=null, as providing a valid object is not possible at the stage in which the onunhandledrejection event listener is registered.
Now, after that is fixed, the app crashes again because apparently that was the intended behaviour.   handleGeneralError calls Sentry.crash(), which throws, but the problem is that it keeps throwing forever, polluting once again the logs.
So unless there is a good reason for that, I propose we remove this behaviour. If this fix is accepted, then I also propose to apply it on shelley, as that may help for debugging unexpected errors.
Reproduction steps
Simply call handleGeneralError() somewhere:
const e = {title: 'title', message: 'message'}
handleGeneralError('Could not submit transaction', e)

@v-almonacid aha now I see what you meant. This is awesome because it will help a lot with debugging :-)


Update AuditDetails struct with new meta keys

Pull Request Test Coverage Report for Build 78

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

Totals

Change from base Build 75:
0.0%

Covered Lines:
1733

Relevant Lines:
1733

💛  - Coveralls


Networking failure: after proxying for a while, socks server starts failing to create new sessions

What steps will reproduce the problem?

A little unclear how to reproduce consistently at the moment. A little context to hint at the state of things: it happened while simultaneously proxying a YouTube video and visiting the New York times. Lots of sessions were active. We'd been proxying YouTube video for about 45 minutes to an hour already. @klazizpro also produced this error today.

What is the expected output?

The webpage loads.
What do you see instead?
Requesting a new page results in Chrome saying the webpage is not available (the tcp connection to it hits its timeout):

Additional information

Did a little interactive debugging... new tcp connections were being received, and new tcp connection objects were created. However, new SocksToRtc sessions were not being created for them. Here's an image:

(Note that Tcp connection N1257 was new, but no new socks-to-rtc session was created for it).

Next step: read the code again and imagine how this might happen.

I had similar problem and was able to get log from the host , sharing the Google doc link
https://docs.google.com/a/google.com/document/d/1r6LgIpU0mo4zLYdkgnEtvGiIs5-1pMc46ZKis2Bw4Ms/edit?usp=sharing

@klazizpro I don't think that is the same error. I think that is a log for: https://github.com/uProxy/uproxy/issues/892

Thanks for the detailed bug report! It's a little tricky to investigate without steps to reproduce but I think we can still narrow things down a bit...
Firstly, the issue seems to rest on the getter's (SocksToRtc) side. Next, if TCP sessions are still being created without a corresponding session then I think there's one of two possibilities:

something weird with tcp.ts's connectionsQueue, probably the underlying onConnection event from the TCP socket provider
something weird with SocksToRtc itself

Since we also saw some failures in the log related to chrome.runtime.lastError I have to suspect the first, even though I can't imagine off-hand how other SOCKS sessions could still be working reliably if the TCP socket provider somehow "failed".
@ryscheng and @willscott: Publishing a new release of freedom-for-chrome would help us eliminate the first possibility:
https://github.com/freedomjs/freedom-for-chrome/pull/69

I was just playing around with uProxy in the test lab and my proxy seemed to stop accepting new connections right around the time I got some chrome.runtime.lastError errors in my log -- another run, I saw the same errors but the server still seemed to be accepting connections.

So, freedom-for-chrome 0.4.13 is out (thanks @willscott!) and I just published version 5.2.2 of uproxy-networking.
Let's see if we can still break it...

Yeah, so I started to look at this issue and figured we have a general problem with large downloads:
https://github.com/uProxy/uproxy/issues/945

If you don't object too much, I'm going to close this in favour of the more general "large downloads" issue:
https://github.com/uProxy/uproxy/issues/945


How to deal with $(document).ready(function().... things with updating modules/ajax

Hi,
My issue is javascript functions which run on document ready.
(for example masonry).
How do i implement a   $(ajax).ready(function().... in microweber?
Or more precisely,
$(when microweber and the browser finished updating the module).ready(function()..

hi, the $(document).ready function works when the module loads or its realoded
in your module's index.php you can put
<script>
$( document ).ready(function() {
  alert('hi')
});
</script>

and it will work


has_flag in setup.py doesn't seem to work

It looks like that any flags you want to check using the has_flag method in setup.py will return True and then the flag will be added to the compiling.

That is not my experience. Here is an excerpt from the output of pip3 install -U --user -v -e . after adding this line:
diff --git a/setup.py b/setup.py
index a9c0ea9..c8286c1 100644
--- a/setup.py
+++ b/setup.py
@@ -74,6 +74,7 @@ class BuildExt(build_ext):

     def build_extensions(self):
         ct = self.compiler.compiler_type
+        print(has_flag(self.compiler, "-bogus"))
         opts = self.c_opts.get(ct, [])
         if ct == 'unix':
             opts.append('-DVERSION_INFO="%s"' %

running build_ext
    x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.4m -c /tmp/tmpkt6wc5ws.cpp -o tmp/tmpkt6wc5ws.o -bogus
    x86_64-linux-gnu-gcc: error: unrecognized command line option ‘-bogus’
    False

Can you provide an example?

I spoke it too absolutely. It always returns True for -l stuff. Try -lbogus for example.

In that case, the flag is -l, which exists for most (all?) compilers. It is expected to return True.


macOS: cannot open new file or new window when in different space

VSCode Version:  1.29.1
OS Version: 10.13.3 (17D102)

Here, the "Spaces" I refer to are part of macOS's built-in "Mission Control".
Steps to Reproduce:

Open vscode (only) in one Space
Attempt "File>Open New file" or "File>Open New Window" in a different Space

Does this issue occur when all extensions are disabled?: Yes

/duplicate https://github.com/Microsoft/vscode/issues/63959


Child record mutations should navigate back to parent upon completion

Is your feature request related to a problem? Please describe.
When adding or editing records from a page another record is embedded in, you have to press back twice (once to get to the edit form and another to get back to the initial page) in order to arrive at the initial page you were coming from. This is a UX nightmare for edit heavy applications.
Describe the solution you'd like
Edit and insert operations should remember where they were initiated from and renavigate to the initiating page upon completion.
Additional context
See video for example (image doing this 100's of times per day)
https://user-images.githubusercontent.com/19151369/193868890-aa04ad99-dd44-48fd-84bd-f432ffea81ef.mp4
Add any other context or screenshots about the feature request here.

Is there anyway I can contribute to this to help it make an earlier release?

Apologies for the late response, if you wish to provide a good strategy for the back button in general I would be all ears.
Its a complex issue since you cannot rely on browser history at all times, so some logic has to be designed.

We're using vue-router which supports manipulating and traversing history
https://router.vuejs.org/guide/essentials/navigation.html#traverse-history
I agree it could evolve to be complex, but I think to start we could make rules for common ui-nav paths and mark certain routes as 'non-navigateable'
For example:
press edit on a record -> push current route into 'last navigateable path' and navigate to edit route
press save -> don't push anything into 'last navigateable path' since edit route is 'non-navigateable'
press back -> go to the 'last navigateable path' which in this case would be the view page of the last record
I'm sure we'd need to come up with something more thourough, but what are your thoughts on that?

Great start, it goes in the same direction as what we are planning, certain new features such as page blocks and records in modals do make it a bit more complex.


Prepare DragAndDrop for commonization

Fix followups after #1493
Sync internals with https://r.android.com/3197432 (unlock merging iOS implementation)
Restore PlatformDragAndDropManager and add related APIs
Use hasEligibleDropTarget for dynamic drop target indication

https://github.com/user-attachments/assets/8b7a65af-97d2-4033-8d88-33445256f8cb
Testing
Test sample from #1493
This should be tested by QA
Release Notes
Features - Desktop

Add dynamic Drag&Drop target indication (🚫 icon under cursor if currently there is no valid drop target under it)

@elijah-semyonov, could you please do the main review? I will look at the commonMain changes and the API for ComposeScene


Correct comment explaining trustedOnly

In register:
https://github.com/farcasterxyz/contracts/blob/80dde9b16ba09774d7500e24cded5fd88a71863e/src/IdRegistry.sol#L200
and, in trustedRegister:
https://github.com/farcasterxyz/contracts/blob/80dde9b16ba09774d7500e24cded5fd88a71863e/src/IdRegistry.sol#L223
=> trustedOnly = 0 to call register.
trustedOnly = 1 to call trustedRegister.
The comment over the the definition of trustedOnly conveyed the opposite.
https://github.com/farcasterxyz/contracts/blob/80dde9b16ba09774d7500e24cded5fd88a71863e/src/IdRegistry.sol#L141
Cheers,
Yash Karthik

sure, no problem.


Signum with grad compression

Description
Added a new grad compression scheme.
It keeps track of the momentum on every worker and sends the sign vector of the momentum.
This is a somewhat hacky version of doing distributed version of the Signum optimizer: https://github.com/apache/incubator-mxnet/pull/9220
Checklist
Essentials

[x] Passed code style checking (make lint)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Microsoft made its 1-bit SGD to open. I think someone can borrow some idea from that.

It's fairly easy to change the compression to use 1bit. You need to change the bitmasks in the struct quantize_signum and dequantize_signum, and also change the start and end indices to cover 32 values in one call.
You could use masks like 0x80, 0x40, 0x20, 0x10, 0x08, 0x04, 0x02, 0x01 for the values which are greater than 0. As an optimization don't encode negative values, and remove the second if statement in quantize. Let them be 0. During dequantization change them to -1.
Yes you'll not lose accuracy if the server forwards the differences to worker. But the way mxnet kvstore currently works is that it pushes the full model to the workers. As against this, if we tried to send differences then we would need to send (num_workers * compressed_size) data as updates to each worker. This is because we can't merge the updates from different workers without decompressing, merging and then compressing them back. Also if we do this, then if num_workers becomes higher than the compression factor, then gradient compression would give no speedup.

@rahul003
Hi, I have implemented a similar 1bit gradient compression algorithm with your advice. However, when I train resnet110 on CIFAR-10 dataset to compare my implementation to 2bit compression and no compression algorithms, I found that the speedup of gradient quantization for ResNet training seems not significantly. The training command and logs are shown as follows, and I deployed training tasks across four nodes (each node is equipped four K80 GPUs), in which one parameter server and three workers. Is there any incorrect setup in my training process?
ps: I use the example code in dictionaryexample/image-classification
mxnet version: 1.4.0
cuda: 8.0
training command:
python ../../tools/launch.py --launcher ssh -H hosts -s 1 -n 3 python train_cifar10.py --gc-type 2bit --gc-threshold 1 --kv-store dist_sync --num-epochs 200 --batch-size 128 --lr-step-epochs 100,150 --wd 0.0001 --lr 0.1 --lr-factor 0.1 --network resnet --gpus 0,1,2,3

100th epoch:

No Quantization
2bit Quantization
1bit Quantization

time cost (second)
19.27
19.777
18.545

validation accuracy
0.89122
0.887921
0.885871

150th epoch:

No Quantization
2bit Quantization
1bit Quantization

time cost (second)
18.73
22.357
20.339

validation accuracy
0.92758
0.929688
0.929109

200th epoch:

No Quantization
2bit Quantization
1bit Quantization

time cost (second)
19.048
18.846
19.649

validation accuracy
0.929988
0.935397
0.937500


Add Vault K8S to showcase

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[X] You have updated the .github/CODEOWNERS file according to your changes.
[X] You have registered new documents to /sidebars.js if any.

Dear @ainhoa-a,
In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.
If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.
— The DFINITY Foundation


[feature] Can we use one headless service for one job?

We have ps/worker/chief for one TFJob. And now we create one headless service for one replica. I think we can use one headless service for easy-to-use.
After that, we could use {tfjob_name}-{replica_type}-{index}.{service_name}.svc.cluster.local in the code.
WDYT @johnugeorge @richardsliu

/area engprod
/priority p2

/reopen
We should take this to improve cluster performance.

I realized this need by Aldo's comment.
cc: @kubeflow/wg-training-leads

/lifecycle frozen

@tenzen-y brought this up in brainstorming around jobset/kubeflow.
We have implemented a few ways to customize network names.

type Network struct {
	// EnableDNSHostnames allows pods to be reached via their hostnames.
	// Pods will be reachable using the fully qualified pod hostname:
	// <jobSet.name>-<spec.replicatedJob.name>-<job-index>-<pod-index>.<subdomain>
	// +optional
	EnableDNSHostnames *bool `json:"enableDNSHostnames,omitempty"`

	// Subdomain is an explicit choice for a network subdomain name
	// When set, any replicated job in the set is added to this network.
	// Defaults to <jobSet.name> if not set.
	// +optional
	Subdomain string `json:"subdomain,omitempty"`
}

Was what we used to control service creation for the jobset.

The suffix will differ from .svc.cluster.local according to the cluster settings. Maybe we could use a CLI parameter to config it.


Support diagnostics additional locations

2 broken tests:

The_correct_project_capablities_is_emitted - missing FolderPublish
TwoProjectsWithSolutionAndCustomConfigurations - only contains Lib.csproj, App.csproj is not added to the workspace.


Big feature : Sharing your config with the outside world without sharing API keys.

Description
To achieve sharing a config public over the internet.
The current problem is that the whole config (including secrets) is passed in the body of a request whenever a request is done.
I would need to just send the name of the config in the request URL (via body or path GET /api/modules/torrents?config=my%20config%20is%20better  ==> Get the config using fs to read the config file directly, find the Torrent-able services (The services that are either of Qbit/Deluge/Transmission)
Then I can use the API key from these services without it ever being exposed to the frontend.
Issues : The whole config is passed on page fetch and gives you the API keys it uses. They are not filtered out of the config.
Maybe we could filter them out if a config is ReadOnly: true or something similar.
These modifications need to be made in the index.tsx file and the [slug].tsx file, which gets a config based on the URL.
Another idea would be to make it so a password in not required to access ReadOnly configs using the url homarr/myConfigName .
==> Need to make sure that the user can't add, modify, edit, view or remove a service. (ReadOnly)
==> Need to make sure that the API keys are not passed to the user and that they are only used by the API
But why ?
I don't understand why people would like to share Homarr and are scared of exposing their API keys. Unless they find an exploit that would allow them to run anything on Homarr's backend and make a malicious request to their Sonarr instances (Like add a really bad show like Family guy for example)
I don't see why this would be a concert. Just expose Homarr and don't share Soanrr / Radarr in that case ?
Or maybe you want to share Homarr and still have Radarr/Sonarr accessible with their password/login (So you want to hide API keys because it would then be easy to make a malicious request to your services)
Please tell me if you have any more ideas on how to implement this public sharing feature because I am still a little bit lost on how to safely implement it.
Priority
Low (Nice-to-have)
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues

Can we close this?


Change balance variables places

Solving the issue #6
Avoid code-logic-confusion with starting_balance_of_account and balance_of_lottery variables by changing the places of them.

was just in the middle of writing this up, good catch!


Replace nbshell with shell_plus

Environment

Nautobot version: 1.2.x

Proposed Functionality
Since Nautobot 1.2 introduces django_extensions I would like to see nbshell replaced with shell_plus.

Use Case
Shell_plus auto-imports models like nbshell, but also supports importing models for plugins. There are other neat features such as iPython support.

Database Changes
None

External Dependencies
None.
TODO

Remove nbshell management command
Update docs to inform to use shell instead of nbshell
Remove nbshell invoke command
Add shell management command (in Core) which would start shell_plus, overloading Django's built-in shell command
Add shell invoke command

This can be accomplished by replacing the contents of nautobot/extras/management/commands/nbshell.py with:
from django_extensions.management.commands.shell_plus import Command

Implemented for 2.0 via #3181.


Using Update command with table-per-hierarchy class does not set the discriminator

If I use the Update command to change the type of an entry in a table-per-hierarchy class, i.e. change the class from Book to BookWithPromotion then the discriminator column is not updated.
I did try setting the discriminator in code, but that didn't work either - I assume that setting the discriminator via code isn't allowed anyway, so that is most likely superfluous.
Steps to reproduce
The following Unit Test fails both tests at the end.
[Fact]
public void UpdateBookToPromotionNoTracking()
{
    //SETUP
    const string connection =
         "Data Source=(localdb)\\mssqllocaldb;Database=TestThp;Integrated Security=True;";
    var optionsBuilder =  new DbContextOptionsBuilder <MyDbContext>();

    var options = optionsBuilder.UseSqlServer(connection).Options;

    int bookId;
    using (var context = new MyDbContext(options))
    {
        context.Database.EnsureCreated();

        var book = new Book {Title = "Book", Price = 2};
        context.Books.Add(book);
        context.SaveChanges();
        bookId = book.BookId;
    }

    using (var context = new MyDbContext(options))
    {
        //ATTEMPT
        var bookNoTracking = context.Books.AsNoTracking().Single(x => x.BookId == bookId);

        var bookProm = new BookPromotion
        {
            BookId = bookNoTracking.BookId,
            Title = bookNoTracking.Title,
            OldPrice = bookNoTracking.Price,
            //promotion stuff
            Price = 1,
            PromotionText = "This promotion"
        };
        context.Books.Update(bookProm);
        context.SaveChanges();
    }
    using (var context = new MyDbContext(options))
    {
        //VERIFY
        context.Books.Single(x => x.BookId == bookId).GetType().ShouldEqual(typeof(BookPromotion));
        context.Books.Single(x => x.BookId == bookId).HasPromotion.ShouldBeTrue();
    }
}

The classes are:
    public class Book
    {
        public int BookId { get; set; }
        public bool HasPromotion { get; set; }
        public string Title { get; set; }
        public decimal Price { get; set; }
    }

    public class BookPromotion : Book
    {
        public decimal OldPrice { get; set; }
        public string PromotionText { get; set; }
    }

The DbContext is:
public class MyDbContext : DbContext
{
    public DbSet<Book> Books { get; set; }

    public MyDbContext(
        DbContextOptions<MyDbContext> options)
        : base(options) { }

    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<Book>()
            .HasDiscriminator<bool>("HasPromotion")
            .HasValue<Book>(false)
            .HasValue<BookPromotion>(true);
    }
}

Further technical details
EF Core version: 1.1.0
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2015, Update 3.

Note for triage: The reason for this is that shadow properties are marked as having an unknown value when an entity is attached to the context. This stops accidental over writing with null of, for example, FK properties--see #4920. In this case it means that the discriminator property is the shadow property, and the value it should have is known because it comes from the CLR type. So we could special case discriminators, although off the top of my head I'm not sure where the special casing would go given that discriminators are a relational concept.
Also note that this is an attempt to do back-door type mutation, which is why the code is jumping through all the hoops of creating a no-tracking query, etc. So we could just say that this is not supported.

Hi @ajcvickers,
OK, I can see it could be a lot of work to get Update to work with discriminators. If that is the decision I will put that in my write up.

We discussed this in triage and decided that we won't add explicit support for mutating the type in this way. If the discriminator does need to be set in an update (only needed to mutate the type) then the discriminator value can be set explicitly.

HI @ajcvickers,
Fine, but re your last comment:

If the discriminator does need to be set in an update (only needed to mutate the type) then the discriminator value can be set explicitly.

I did try that and setting the discriminator directly did not work (I mentioned that in my initial post - see second paragraph in italics).

@JonPSmith It works for me if I set the property to allow writes:
modelBuilder.Entity<Book>()
    .Property("Discriminator").Metadata.IsReadOnlyAfterSave = false;

And then set the value before saving:
context.Entry(bookProm).Property("Discriminator").CurrentValue = nameof(BookPromotion)

What error are you seeing?

Hi @ajcvickers,
Well, another learning experience. I hadn't got into the .MetaData part of setting up properties - thanks for pointing that out! I need to pull that into my examples.
Yes, when I added the ...Metadata.IsReadOnlyAfterSave = false; to my Fluent API my unit test (with HasPromotion = true, added) worked. Previously, because it was read only, setting it didn't work.
I have updated my original post so that if anyone else has this problem then they can see the answer


DOC: Add to citations.bib for QIIME2

I don't think there's a citation etiquette, but I think leaving just the EMPress citation makes sense.

The following artifacts were built for this PR: empire-biplot.qzv, empire.qzv, empress-tree.qzv, just-fm.qzv, plain.qzv

Thanks @ElDeveloper! (and @emperor-helper :penguin: ;)


Feature : allow for a maximum number of tabs

Expected behavior
As a developer I often open multiple Stack Overflow tabs.
What would be awesome is to set a limit on the number of tabs of the same domain open. If the limit is reached, we automatically replace the older tab.
Actual behavior
I can only limit to one tab.
What do you think ? 😊

Be wise. :)
Best


Manually implement Debug for combinators/wrappers containing closures

#[derive(Debug)] isn't particularly useful for combinators or wrappers that take closures as it requires all fields to be Debug even though closures don't implement it and the Debug impl on function pointers isn't particularly meaningful anyway, as it just prints the value of the pointer.
I recommend instead manually implementing Debug for these, debug-printing the other fields such as nested futures/streams while printing something like [closure] (bikeshedding welcome) for the closure fields of these combinators/wrappers.
This is confusing users in the wild, like this person trying to .unwrap() the result of a Select2<Map<_, [closure]>, _>.
I'm willing to implement this myself if it meets everyone's approval.

This sounds like a great idea to me!


Start failed when using pipx install wsgidav cheroot

Describe the bug
Start failed when using pipx install wsgidav cheroot
To Reproduce
Steps to reproduce the behavior:

brew install pipx
pipx install wsgidav cheroot
wsgidav --host=<IP_ADDRESS> --port=8080 --root=$(pwd) --auth=anonymous
See error

Expected behavior
no error when starting
Screenshots, Log-Files, Stacktrace
Running without configuration file.
10:39:03.822 - WARNING : App wsgidav.mw.cors.Cors(None).is_disabled() returned True: skipping.
10:39:03.828 - INFO    : WsgiDAV/4.3.0 Python/3.12.1 macOS-14.3-arm64-arm-64bit
10:39:03.828 - INFO    : Lock manager:      LockManager(LockStorageDict)
10:39:03.828 - INFO    : Property manager:  None
10:39:03.828 - INFO    : Domain controller: SimpleDomainController()
10:39:03.828 - INFO    : Registered DAV providers by route:
10:39:03.828 - INFO    :   - '/:dir_browser': FilesystemProvider for path '/Users/edy/Library/Application Support/pipx/venvs/wsgidav/lib/python3.12/site-packages/wsgidav/dir_browser/htdocs' (Read-Only) (anonymous)
10:39:03.828 - INFO    :   - '/': FilesystemProvider for path '/Users/edy' (Read-Write) (anonymous)
10:39:03.828 - WARNING : Basic authentication is enabled: It is highly recommended to enable SSL.
10:39:03.828 - WARNING : Share '/' will allow anonymous write access.
10:39:03.828 - WARNING : Share '/:dir_browser' will allow anonymous write access.
10:39:03.828 - WARNING : Could not import lxml: using xml instead (up to 10% slower). Consider `pip install lxml`(see https://pypi.python.org/pypi/lxml).
10:39:03.829 - ERROR   : Could not import Cheroot (https://cheroot.cherrypy.dev/).
Traceback (most recent call last):
  File "/Users/edy/Library/Application Support/pipx/venvs/wsgidav/lib/python3.12/site-packages/wsgidav/server/server_cli.py", line 433, in _run_cheroot
    from cheroot import server, wsgi
ModuleNotFoundError: No module named 'cheroot'
10:39:03.829 - ERROR   : Try `pip install cheroot`.

If applicable, add screenshots to help explain your problem.
If applicable, add a log file (consider --verbose).
Environment:
WsgiDAV/4.3.0 Python/3.12.1(64 bit) macOS-14.3-arm64-arm-64bit
Python from: /Users/edy/Library/Application Support/pipx/venvs/wsgidav/bin/python

Which WSGI server was used (cheroot, ext-wsgiutils, gevent, gunicorn, paste, uvicorn, wsgiref, ...)?
Which WebDAV client was used (MS File Explorer, MS Office, macOS Finder, WinSCP, Windows, file mapping, ...)?
Additional context
Add any other context about the problem here.

As the error message says:

10:39:03.829 - ERROR   : Try pip install cheroot.

You must install a server separately. See also the --server option

As the error message says:

10:39:03.829 - ERROR   : Try pip install cheroot.

You must install a server separately. See also the --server option

Thanks for reply ！
I figured out the difference between pipx and pip.
pipx install wsgidav --pip-args cheroot works fine !


kadane_algo

Description
Describe more about the issue.
Kadane's algorithm is an iterative dynamic programming algorithm in which we search for a maximum sum contiguous subarray within a one-dimensional numeric array.
such good algo!
Programming language

[ ] C
[ ] C++
[ ] Java
[x] Python

Are you contributing under any open-source program?

Can you assign this issue to me. I love to work on it


when use MONGO_URI, error: Another user is already authenticated

I use a cloud mongodb server,  version is 3.0.7. But its authMechanism is 'MONGODB-CR', not default 'SCRAM-SHA-1'. So when I used 'MONGODB-CR', occured error 'Another user is already authenticated'. My MONGO_URI:
'mongodb://demo:123456@<IP_ADDRESS>:27017/demo?authMechanism=MONGODB-CR'
I read source code, and found the reason,
# flask_pymongo/__init__.py 252-253
if any(auth):
    db.authenticate(username, password)

authenticate not assign mechanism agument, so 'DEFAULT‘ and occured my error.

Can you try to apply the following changes?
In URI parsing, add this line:
app.config[key('AUTH_MECHANISM')] = parsed['options'].get('authMechanism', 'DEFAULT')

In URI-less config, add this line:
app.config.setdefault(key('AUTH_MECHANISM'), 'DEFAULT')

Then when calling authenticate:
mechanism = app.config[key('AUTH_MECHANISM')]
db.authenticate(username, password, mechanism=mechanism)

This untested patch could help. If it does not work as is, it may be a hint.
pymongo v3.0 adds a ClientOptions class that handles that (and auth source) correctly. Dropping pymongo < 3.0 support would allow flask-pymongo to benefit from it.

@lafrech I used the same solution for this, and thank you for the reply.

@syfun I know this is a very old bug and it sounds like you've gotten a workaround for this at this point. But I'm trying to revive this project, and I've just recently merged #88, which I think should fix your issue as well. I'll be releasing 0.5.0 soon. When I do, would you be able to test and confirm here whether that works for you?

@dcrosta Ok for that. This bug is realy old enough. I alreay fixed, but almost forgot that. Sorry for not further communication. I will seriously test after you releasing 0.5.0.

@dcrosta in 0.5.0, I get this error. not sure if it's related to this issue above:
File "/home/someuser/.local/lib/python3.5/site-packages/flask_pymongo/init.py", line 97, in init
self.init_app(app, config_prefix)
File "/home/someuser/.local/lib/python3.5/site-packages/flask_pymongo/init.py", line 278, in init_app
auth_mechanism = app.config[key('AUTH_MECHANISM')]
KeyError: 'MONGO_AUTH_MECHANISM'
I went back to 0.4.1 and it works.

@chattr1n @dcrosta I also encounter this error. I found the reason in the code.
When user not define MONGO_URI, AUTH_MECHANISM had no default value.

I believe that will be fixed by #93, which I'll be releasing shortly as 0.5.1.

0.5.1 is now in PyPI -- please upgrade and let me know if that fixes it. If not, we can dig in deeper here.

@lafrech That's OK for 0.5.1.

Great, thanks for following up!


Serve the autoyast content even when a SCC/SMT connection error happens

The service unavailable http error code (503) will only be returned now
until the first page of the setup is completed (so we have the dashboard
address to serve the autoyast profile).
When one of the following exceptions happens:

Missing registration code
Missing credentials for SCC/SMT
Any HTTP error while connecting to SCC/SMT

We will still serve the autoyast content with a comment explaining why
the system cannot be registered. The returned http error code will be
success (200), but the XML will contain a comment stating why the system
cannot be registered.
Fixes: bsc#1049948

Backport for 1.0/update here: https://github.com/kubic-project/velum/pull/271

Instead of a comment on the XML I'm trying something fancier with ask-list on the autoyast profile. Putting it back to WIP.

Updated PR. This message is shown when using autoyast when the system is not being registered. The message depends on the error:

I thought this way is a nicer way to provide feedback than a comment in the XML file, however this doesn't allow an unattended installation (if anything goes south with the registration, which might be good actually).
Please provide your feedback to know if this is a feasible solution or we should be silent during the whole installation process when using autoyast without mattering the error we are facing.

I think this looks pretty great. I can't really test it (I haven't built an ISO yet myself!) but I think it looks good.
Maybe AJ should sign off on it too, since it's user-facing?

@robdaemon Just as a side note, I launched the devenv and used an existing ISO (in this case I didn't build the ISO myself), so if you raise a VM with qemu you can still point it with netsetup=dhcp autoyast=http://your-ip-address/autoyast as we are only testing that it fetches the error from the XML served from your devenv in this case :)

Adding @flavio because it's user facing, who we should ask too as @robdaemon says? @ajaeger, @eotchi?

This will also very probably need adapting the QA suite tests.

Yes, and this warning is completly wrong and needs to be removed immediately again. Not that this breaks autoinstallation (even a timeout of 30 seconds is not Ok), for 99% of the installations you don't need a registration code, because customers normally use SMT or SUSE Manager.

Yes, and this warning is completly wrong and needs to be removed immediately again. Not that this breaks autoinstallation (even a timeout of 30 seconds is not Ok), for 99% of the installations you don't need a registration code, because customers normally use SMT or SUSE Manager.

This message will only pop up if:

There was a problem connecting to SCC or SMT when the autoyast profile is going to be served (so the worker won't be registered).
No regcode was provided during the admin installation (so there's no way to register new workers against SCC), and no SMT is being used.
Credentials for SCC/SMT are missing (API), this should not happen under normal circumstances.

If this message is being shown with SMT it's a bug, it shouldn't happen.

How does velum know what my installation source is? That's impossible to know for velum, since this is an installer option and not visible to velum.

How does velum know what my installation source is? That's impossible to know for velum, since this is an installer option and not visible to velum.

It certainly can, done here: https://github.com/kubic-project/velum/blob/7625b36d2a34f9b100d6800c4fad9cbc57e0e8ea/lib/velum/suse_connect.rb#L58-L60
All our docker containers have the secrets patch, which includes:
linux-jbau:~ # docker exec -it 9a6 bash
bash-4.3# cat /var/run/secrets/SUSEConnect
---
insecure: false
url: https://scc.suse.com

If url is https://scc.suse.com then it's SCC, otherwise it's SMT.

What you are seeing there is how the admin node was installed, not what the installation source for the cluster nodes will be.
QA, Rob and me run into this, so this are already three ways of installation where velum is wrong with the guess.
I use the DVD for the admin node and PXE boot with autoyast via SMT. I'm not interested in running around with a DVD for installation, but I'm also not interested in writing an autoyast profile only for the admin node. Everything is configured in the PXE/tftpboot config files on my install server. Velum has no access to this and is not able to find out what the installation source for the cluster nodes is and what is needed.

I spoke with @ereslibre, we are going to revert this PR.


[bazel] Use CRT for toolchain configuration

Use Compiler Repository Toolkit to
configure the RISC-V toolchain instead of bazel-embedded.

Bazel-embedded seems to be somewhat unmaintained.
Bazel-embedded wasn't well structured for the addition of the riscv compiler.  We never successfully upstreamed our fork.
CRT was written by the OpenTitan team.
CRT has a somewhat easier structure for supporting additional target architectures.
CRT is also being used by the provisioning project to cross compile for Win32/64 targets.

I also checked the CRT repo to make sure that we have the recent changes from our bazel-embedded fork: It looks like CRT does not enable -Werror -Wall -Wpedantic.

I'm not sure why github search doesn't work but it looks like we just need to enabled -Werror here since -Wall -Wpedantic are already enabled.

Didn't merge because @cfrantz requested a review from @cindychip and wanted to give @cindychip the chance to take a look before this is merged.

I also checked the CRT repo to make sure that we have the recent changes from our bazel-embedded fork: It looks like CRT does not enable -Werror -Wall -Wpedantic.

I'm not sure why github search doesn't work but it looks like we just need to enable -Werror here since -Wall -Wpedantic are already enabled.

I've updated the configuration in the CRT repo such that the riscv compiler is invoked with identical options to the current bazel-embedded configuration (modulo repository path differences).

The request for @cindychip was automatically added when I updated some of the toolchain labels in the //hw/... scripts.  @cindychip , the changes are simple replacements.
@timothytrippel will merge this PR after it passes CI and he performs the needed updates to the internal EDA runtime images.

Looks like we need to remove this line in order to get the image building.

@ bazel_embedded is still in .bazelrc

@ bazel_embedded is still in .bazelrc

#14646 should fix.


Added File organizer

Type of change

[x] Added new project
[ ] Bug fix
[ ] New features
[ ] Enhanced documentation

Changes proposed in this pull request

Project name : File Organizer

Short description :

Given a directory path  via command line argument, it checks the files, sorting and moving them to appropiate subdirectories under the same directory.
Ex:
Moved 'IMG_9055.JPG' to 'Pictures' folder.
Moved 'IMG_9098.JPG' to 'Pictures' folder.
Moved 'AGC9.0.37_V1.0.apk' to 'Executables' folder.
Checklist

[x] The code is Python 3 compatible
[x] I have added relevant comments in my file to make code understandable
[x] I have added my project in a folder which includes all the necessary files

Please have a look at this PR, thank you.

Hey @JohnRTitor
Thanks for your contribution 🚀


[update] update functions should only update fields

Right now the update function updates the entire document supplied the mutation data.
I think that the update should only update the fields sendt in the mutation.

How I now it updates only that fields which was passed via mutation. If you pass fieldname with null, it must save null to DB. If field not present in mutation it should keep it in DB unchanged.
@rlogachyov can you confirm this?

I have this function on Users scema:
UserSchema.pre('save', function (next) {
  if (this.password || this.isNew){
    this.password = bcryptjs.hashSync(this.password, 10)
  }
  next()
})

https://github.com/nodkz/graphql-compose-mongoose/blob/master/src/resolvers/updateById.js#L109-L116
Will get full document, update fields that is changed and save complete document back to database with all fields. This triggers crypt of a password that is not sendt in mutation.
I find http://mongoosejs.com/docs/api.html#document_Document-update to be more in the right place as it just sends a update to model containing just the fields to update.
😉

I can confirm when updating attributes on a subdocument i.e.,
{
_id: 'someId',
profile: {
...
}
}
the update wipes out fields that are not passed along with the query.

@smooJitter
From MongoDB docs:

To update an embedded document or an array as a whole, specify the replacement value for the field. To update particular fields in an embedded document or in an array, use dot notation to specify the field.

I think, that it also will be true for using with mongoose. And it will work with graphql-compose-mongoose if we wrap updateById resolver where make record fields flat via dot-notation keys.
So partial updating of embedded docs is quite tricky. Maybe it will be nice to write additional standard resolver for graphql-compose-mongoose and call it like updatePartialById.

So we ran into this issue as well. Before writing a resolver, we found a work around just using updateMany(filter: {_id: ID}, record: { field: value}}). It works in most cases when you don't need the record back (since updateMany only returns numAffected).

I know this issue is quite old now, but this was something that I wanted to achieve in a universal manner, and I found a way that seems to work nicely.
I created this before-save hook which can be applied to all my updateById. This goes in a file called "mergeFields.js"
function isObject(item) {
  return item && typeof item === "object" && !Array.isArray(item);
}

export function merge(target, source) {
  // sanity check - probably overkill
  if (!isObject(source)) {
    return source !== null ? source : undefined;
  }
  const output = target;
  const entries = Object.entries(source);
  for (let i = 0; i < entries.length; i += 1) {
    const [key, value] = entries[i];
    if (isObject(source[key])) {
      if (target[key] === undefined) {
        // add new embedded documents
        output[key] = value;
      } else {
        // recursively merge existing embedded documents
        output[key] = merge(target[key], value);
      }
    } else {
      // remove existing fields with a `null` input
      output[key] = value !== null ? value : undefined;
    }
  }
  return output;
}

export default function mergeFields(resolvers) {
  Object.keys(resolvers).forEach((k) => {
    resolvers[k] = resolvers[k].wrapResolve(
      (next: any) => async (rp) => {
        rp.beforeRecordMutate = async (doc, rp) => {
          const entries = Object.entries(rp.args.record);
          for (let i = 0; i < entries.length; i += 1) {
            const [key, value] = entries[i];
            if (isObject(value)) {
              // merge new embedded documents into existing ones
              rp.args.record[key] = merge(doc[key], rp.args.record[key]);
            } else if (value === null) {
              // remove existing fields with a `null` input
              rp.args.record[key] = undefined;
            }
          }
          return doc;
        };
        return next(rp);
      }
    );
  });
  return resolvers;
}

Then when I add my resolvers:
import mergeFields from "./mergeFields";

export const NestedExampleMutation = {
  ...mergeFields({ updateNestedExample: NestedExampleTC.getResolver("updateById") }),
  addNestedExample: NestedExampleTC.getResolver("createOne"),
};

If this approach actually works as well as it seems to in my testing, it might be nice to have it available as an option in UpdateByIdResolverOpts.


Upgrade to fabric8 and jube 2.0.30.

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/260/
Test PASSed.


I can't understand one sentence in this document.

[Enter feedback here]

What does it mean by saying "IoT Hub requires two thumprints when registering and IoT Edge device. " ?
Is there anything wrong or I misunderstood this sentence.

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

ID: e275ce10-660d-4f06-9b9d-abb31940c564
Version Independent ID: de3b6527-e1fb-93d3-fdb9-3bb5f6958aa7
Content: Understand how IoT Edge uses certificates for security
Content Source: articles/iot-edge/iot-edge-certs.md
Service: iot-edge
GitHub Login: @jlian
Microsoft Alias: jlian

@zh0903 thank you for reporting this issue. I am sure it is a Typo. The statement should be "IoT Hub requires two thumprints when registering an IoT Edge device." We will take the appropriate action.

@PatAltimore Please look into this feedback and update the doc as appropriate.

Hi @zh0903,
Thanks for pointing out the issue. It's a mistake. It should say IoT Hub requires two thumprints when registering an IoT Edge device. We'll improve the clarity of the tip.
Thanks,
Pat

Hi @zh0903,
We updated the note to fix the typo an clarify the use of thumbprints. Thanks for the feedback. I'm going to close the issue.
Thanks,
Pat
#please-close


feat(ci): add test stage

This issue is quite complicated to be addressed now
Need further investigation
Verify
Templates Testing Tooling
Diffengine


Disable performance testing in CI

It turns out that regular changes to the compiler can cause fluctuations to these test cases that are sufficient to make them trip over so we can’t run them in CI. The test should still be valuable to bisect a performance regression after we find it or to verify that a change doesn’t cause a performance regression.

@swift-ci Please test


(High) Incomplete string escaping or encoding

Repo:
https://github.com/US-EPA-CAMD/easey-mdm-api/security/code-scanning

https://github.com/US-EPA-CAMD/easey-mdm-api/security/code-scanning?query=is%3Aclosed+branch%3Adevelop Marked as done here. Closing this ticket. Monitor for another alert.


Select list: Allow options not on the list

It may be a bit counterintuitive, but it would also be handy to allow pre-population of fields with a set of known values, but also allow items not in that list.
Currently if you use a set of options, values in the spreadsheet that don't match are blanked out, and new values cannot be entered. Which makes sense if you want to ensure values from the list, but in a couple of places we want to provide a list of known values but allow new ones to be added.

Indeed that would be a cool addition. Unfortunately I do not have the capacity to implement it right now. Feel free to open a pr.


Draft breaks when pressing enter on atomic block

Do you want to request a feature or report a bug?
BUG
What is the current behavior?
When the Image is not 100% wide in the editor and you focus cursor after it and press enter you get.

invariant.js:44 Uncaught Invariant Violation: Unknown DraftEntity key.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.
In Media example remove the width styles like showed below.
https://github.com/facebook/draft-js/compare/master...leniartek:patch-1
Than place the cursor after image and press enter.

What is the expected behavior?
Enter to create a empty new line after image.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
all draft versions
all browsers

The example is a bit misleading. It probably shouldn't try to use img directly as the atomic block, but should instead use a wrapper div and apply the width to that. Then the img can be an arbitrary width, but the div width should remain 100%.
Beyond that, it's currently a limitation that the cursor can't really be adjacent to an atomic block in this way. It would be great to have a really solid solution for this, but in the meantime the example should be changed.

Any recommendation how handle this?

Any updates on this or any example how to handle this?

Hi, is anyone working on it? i am new to open source, how do i get started?


Is there a API for create a topic?

I search the doc, can't find a function to create a topic.

No. Kafka does not let you do this directly via API.

Topics are created using the Kafka CLI, which orchestrates it using Zookeeper. My Ruby library implements this, but AFAIK there is no go library that does at the moment.


Automatically unsourced gvm when I exit my terminal.

I am really annoyed by this.
When I completed the installation, both gvm and go runs fine. But the problem occurs every time I close my terminal. My environment and/or terminal (and/or whatever since I cannot figure out what's wrong with this) is automatically unsourced - Idk if this is even possible.
I suppose it hasn't been sourced correctly. But, I'm not sure because I get to enjoy gvm and go prior to closing my terminal.
This is really weird.
EDIT
This will happen when I install rvm and gvm respectively.
Quick Fix
So I echo-ed $GOPATH and $PATH to my .bash_profile.

You set the default environment?
gvm use go1.4 --default


Types/proposals

closes #203

@rachelhox this might take some time to test and fix since morpheus rpc has cors issue. solving it with kwun


Add Sink.none operator

Motivation:
When took a look at the current PR in Kotlin Flow, I think we should have this operator too.
Sink#none operator will just works as the Java's Stream#none.
refs: https://github.com/Kotlin/kotlinx.coroutines/issues/4212
  def none[T](p: T => Boolean): Sink[T, Future[Boolean]] =
    Flow[T].foldWhile(true)(util.ConstantFun.scalaIdentityFunction)(_ && !p(_))
      .toMat(Sink.head)(Keep.right)
      .named("noneSink")

cool~


Allow for logging to Studio when not inside a repo

Partially addresses #638
This allows for posting to Studio if the following environment variables are set:

DVC_STUDIO_TOKEN
DVC_STUDIO_REPO_URL
DVC_EXP_BASELINE_REV
DVC_EXP_NAME

TODO:

[ ] Make DVC_EXP_BASELINE_REV and/or DVC_EXP_NAME optional
[ ] Example
[ ] Docs

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.09% :tada:

Comparison is base (1a73881) 88.18% compared to head (8653732) 88.28%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #646      +/-   ##
==========================================
+ Coverage   88.18%   88.28%   +0.09%
==========================================
  Files          43       43
  Lines        3090     3099       +9
  Branches      270      268       -2
==========================================
+ Hits         2725     2736      +11
  Misses        324      324
+ Partials       41       39       -2

Files Changed
Coverage Δ

src/dvclive/live.py
94.64% <100.00%> (+0.12%)
:arrow_up:

tests/test_dvc.py
100.00% <100.00%> (ø)

tests/test_studio.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

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

Need to look into windows tests not passing. Somehow dvclive expects to pass posix paths even on windows, but not sure where that conversion happens.

Need to look into windows tests not passing. Somehow dvclive expects to pass posix paths even on windows, but not sure where that conversion happens.

The cause was because the conversion only happens within a repo, which brought up that we need to decide where paths should be relative to if there is no repo root. I went with cwd for now.

Need to look into windows tests not passing. Somehow dvclive expects to pass posix paths even on windows, but not sure where that conversion happens.

The cause was because the conversion only happens within a repo, which brought up that we need to decide where paths should be relative to if there is no repo root. I went with cwd for now.

I see. Probably no need to do with cwd (not even sure if it might be potentially problematic)
The posix and relpath operations should be decoupled but I mixed them in a single function (they were actually 2 separate bugfixes one for windows other for monorepo in Studio).
I assume that in norepo scenario we don't really need relpath operation because the default values are already as expected but we do need posix

Make DVC_EXP_BASELINE_REV and/or DVC_EXP_NAME optional

This depends on:

https://github.com/iterative/dvc/pull/9806 (for exp name)
https://github.com/iterative/dvc-studio-client/pull/72 (for baseline rev)
Studio work to allow for requests with a missing baseline rev (these would have to be permanently "detached" unless we later find some way to connect them back to a baseline)

I see. Probably no need to do with cwd (not even sure if it might be potentially problematic)

Updated to remove that.

Example

See https://colab.research.google.com/drive/17X5OyyUi73PXGyZl_87Pl4yUoNS5lMWn?usp=sharing

@dberenbaum do you have a sense on what is the mid-term plan for this? If we are not attached to Git - what is the benefit of using the DVC ecosystem? (sorry, I know it's a non-trivial question, definitely not a blocker of this PR or effort). Data management? something else?
Is there a way to clone the repo in those system under the hood / seamlessly for end-users?
Do we want to cover scenarios like when people don't use Git at all - they don't have a repo at all even? (we pretty much then become two products - Git based and separately MlFlow/W&B, right?

Do we want to cover scenarios like when people don't use Git at all - they don't have a repo at all even? (we pretty much then become two products - Git based and separately MlFlow/W&B, right?

It's not in my plans at this point. This is mainly to cover scenarios where you have a project in a repo but want to run an experiment in an environment where it's painful/impossible to have a full copy of the Git repo. In my experience, it's not uncommon to have a notebook that gets checked into Git but that runs independently in databricks, colab, etc. It's also helpful for the SageMaker scenario where you can kick off a job on a remote machine, but that machine only has access to a single .py file, so this way you can at least see metrics populated in Studio.

Okay, I see. What is the plan of connecting it back? Those experiments will stay "studio"-only, is it correct?
And why can't we try to do a git clone? any specific obstacles for that?

TODO: follow up on why this PR isn't passing on Windows.

@mnrozhkov To try this out, install this branch on all the ray workers (pip install git+https://github.com/iterative/dvclive.git@no-git) and ensure they have the DVC_STUDIO_TOKEN and DVC_STUDIO_REPO_URL env vars.

@mattseddon i think you should be aware by this change as well (baseline is optional)

@mattseddon i think you should be aware by this change as well (baseline is optional)

In the end, baseline is still required to be sent to dvc-studio-client in this PR and defaults to "0" * 40. It seems this is an accepted value for a null ref (see https://stackoverflow.com/questions/18977462/git-sha1-0000000000000000000000000000000000000000-all-zeroes-is-this-normal).


Very slow on Xcode 7

There's a ~0.5 second delay when typing in Xcode 7

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/22395608-very-slow-on-xcode-7?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F252770&utm_medium=issues&utm_source=github).

FWIW I'm not seeing any speed issues on my 2014 Retina Macbook Pro, OS X 10.10.3.

I am also not seeing a delay in typing.
15" Late 2013 rMBP, 10.11, Xcode 7

I feel that Xcode 7 has been very slow and sluggish on this version.
I even have a 2015 Macbook Pro 13" i7 16GB ram so I know that is not what we should be worrying about. Many people have been experiencing this slowness as seen by a simple google search.

No delay here either, 2013' MBP, 10.11.1, Xcode 7.1

I have the same issue on my MacBook Pro (13-inch, Mid 2010), 10.10.5 and Xcode 7.1.1

Scrolling for me is very laggy on XCode 7.1.1, lag disappears when disabling XVim.

Yea i am also having same problem.And moreover launching even take more time.

so slow using swift language in Xcode7


Error running CheckpointSaver.close(). Skipping CheckpointSaver.post_close()

batch=336/5000]:
Train time/batch: 335
Train time/sample: 85760
Train time/batch_in_epoch: 335
Train time/sample_in_epoch: 85760
Train time/token: 351272960
Train time/token_in_epoch: 351272960
Train metrics/train/academic_en_weight: 0.0733
Train metrics/train/book_en_weight: 0.2521
Train metrics/train/code_weight: 0.0122
Train metrics/train/qa_en_weight: 0.0900
Train metrics/train/webtext_en_weight: 0.4453
Train metrics/train/wiki_en_weight: 0.1271
Train memory/current_allocated_mem: 17.7600
Train memory/current_active_mem: 17.7600
Train memory/current_inactive_mem: 3.8283
Train memory/current_reserved_mem: 74.4430
Train memory/peak_allocated_mem: 60.7340
Train memory/peak_active_mem: 61.1380
Train memory/peak_inactive_mem: 27.1850
Train memory/peak_reserved_mem: 74.4430
Train memory/alloc_retries: 0
Train trainer/device_train_microbatch_size: 16
Train loss/train/total: 1.8199
Train loss/train/ce_loss: 1.8199
Train metrics/train/LanguageCrossEntropy: 1.8199
Train metrics/train/Perplexity: 6.1711
Train metrics/train/academic_en_LanguageCrossEntropy: 1.3244
Train metrics/train/academic_en_count: 9893
Train metrics/train/book_en_LanguageCrossEntropy: 1.8898
Train metrics/train/book_en_count: 20179
Train metrics/train/code_LanguageCrossEntropy: 0.8853
Train metrics/train/code_count: 4807
Train metrics/train/qa_en_LanguageCrossEntropy: 1.4436
Train metrics/train/qa_en_count: 10816
Train metrics/train/webtext_en_LanguageCrossEntropy: 2.0363
Train metrics/train/webtext_en_count: 27327
Train metrics/train/wiki_en_LanguageCrossEntropy: 1.5175
Train metrics/train/wiki_en_count: 12994
Train throughput/batches_per_sec: 0.0204
Train throughput/samples_per_sec: 5.2330
Train throughput/device/batches_per_sec: 0.0026
Train throughput/device/samples_per_sec: 0.6541
Train throughput/tokens_per_sec: 21434.4781
Train throughput/device/tokens_per_sec: 2679.3098
Train throughput/flops_per_sec:<PHONE_NUMBER>366202.0000
Train throughput/device/flops_per_sec:<PHONE_NUMBER>20775.2500
Train time/train: 4.5453
Train time/val: 0.1311
Train time/total: 4.6764
Train lr-DecoupledAdamW/group0: 0.0001
Error running CheckpointSaver.close(). Skipping CheckpointSaver.post_close().
Traceback (most recent call last):
File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 527, in _close
callback.close(state, logger)
File "/home/pai/lib/python3.9/site-packages/composer/callbacks/checkpoint_saver.py", line 310, in close
self._save_checkpoint(
File "/home/pai/lib/python3.9/site-packages/composer/callbacks/checkpoint_saver.py", line 332, in _save_checkpoint
saved_path = checkpoint.save_checkpoint(
File "/home/pai/lib/python3.9/site-packages/composer/utils/checkpoint.py", line 761, in save_checkpoint
'state': state.state_dict(),
File "/home/pai/lib/python3.9/site-packages/composer/core/state.py", line 891, in state_dict
serialized_value = self.get_model_state_dict()
File "/home/pai/lib/python3.9/site-packages/composer/core/state.py", line 868, in get_model_state_dict
model_state_dict = self.model.state_dict()
File "/home/pai/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1818, in state_dict
module.state_dict(destination=destination, prefix=prefix + name + '.', keep_vars=keep_vars)
File "/home/pai/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1815, in state_dict
self._save_to_state_dict(destination, prefix, keep_vars)
File "/home/pai/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1722, in _save_to_state_dict
hook(self, prefix, keep_vars)
File "/home/pai/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
return func(*args, **kwargs)
File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 669, in _pre_state_dict_hook
_pre_state_dict_hook_fn[fsdp_state._state_dict_type](
File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 271, in _full_pre_state_dict_hook
_common_unshard_pre_state_dict_hook(
File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 143, in _common_unshard_pre_state_dict_hook
_enter_unshard_params_ctx(
File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 109, in _enter_unshard_params_ctx
fsdp_state._unshard_params_ctx[module].enter()
File "/home/pai/lib/python3.9/contextlib.py", line 119, in enter
return next(self.gen)
File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_unshard_param_utils.py", line 186, in _unshard_fsdp_state_params
assert (
AssertionError: Expects the handle training to be IDLE but got HandleTrainingState.BACKWARD_PRE
Stack (most recent call last):
File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 483, in del
self.close()
File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 512, in close
self._close(self.state, self.logger)
File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 529, in _close
Has anyone encountered this issue before? Why do I always get an error when I train with eight cards on a single machine for over 300 batchs, even though I definitely have enough training data?

batch=336/5000]: Train time/batch: 335 Train time/sample: 85760 Train time/batch_in_epoch: 335 Train time/sample_in_epoch: 85760 Train time/token: 351272960 Train time/token_in_epoch: 351272960 Train metrics/train/academic_en_weight: 0.0733 Train metrics/train/book_en_weight: 0.2521 Train metrics/train/code_weight: 0.0122 Train metrics/train/qa_en_weight: 0.0900 Train metrics/train/webtext_en_weight: 0.4453 Train metrics/train/wiki_en_weight: 0.1271 Train memory/current_allocated_mem: 17.7600 Train memory/current_active_mem: 17.7600 Train memory/current_inactive_mem: 3.8283 Train memory/current_reserved_mem: 74.4430 Train memory/peak_allocated_mem: 60.7340 Train memory/peak_active_mem: 61.1380 Train memory/peak_inactive_mem: 27.1850 Train memory/peak_reserved_mem: 74.4430 Train memory/alloc_retries: 0 Train trainer/device_train_microbatch_size: 16 Train loss/train/total: 1.8199 Train loss/train/ce_loss: 1.8199 Train metrics/train/LanguageCrossEntropy: 1.8199 Train metrics/train/Perplexity: 6.1711 Train metrics/train/academic_en_LanguageCrossEntropy: 1.3244 Train metrics/train/academic_en_count: 9893 Train metrics/train/book_en_LanguageCrossEntropy: 1.8898 Train metrics/train/book_en_count: 20179 Train metrics/train/code_LanguageCrossEntropy: 0.8853 Train metrics/train/code_count: 4807 Train metrics/train/qa_en_LanguageCrossEntropy: 1.4436 Train metrics/train/qa_en_count: 10816 Train metrics/train/webtext_en_LanguageCrossEntropy: 2.0363 Train metrics/train/webtext_en_count: 27327 Train metrics/train/wiki_en_LanguageCrossEntropy: 1.5175 Train metrics/train/wiki_en_count: 12994 Train throughput/batches_per_sec: 0.0204 Train throughput/samples_per_sec: 5.2330 Train throughput/device/batches_per_sec: 0.0026 Train throughput/device/samples_per_sec: 0.6541 Train throughput/tokens_per_sec: 21434.4781 Train throughput/device/tokens_per_sec: 2679.3098 Train throughput/flops_per_sec:<PHONE_NUMBER>366202.0000 Train throughput/device/flops_per_sec:<PHONE_NUMBER>20775.2500 Train time/train: 4.5453 Train time/val: 0.1311 Train time/total: 4.6764 Train lr-DecoupledAdamW/group0: 0.0001 Error running CheckpointSaver.close(). Skipping CheckpointSaver.post_close(). Traceback (most recent call last): File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 527, in _close callback.close(state, logger) File "/home/pai/lib/python3.9/site-packages/composer/callbacks/checkpoint_saver.py", line 310, in close self._save_checkpoint( File "/home/pai/lib/python3.9/site-packages/composer/callbacks/checkpoint_saver.py", line 332, in _save_checkpoint saved_path = checkpoint.save_checkpoint( File "/home/pai/lib/python3.9/site-packages/composer/utils/checkpoint.py", line 761, in save_checkpoint 'state': state.state_dict(), File "/home/pai/lib/python3.9/site-packages/composer/core/state.py", line 891, in state_dict serialized_value = self.get_model_state_dict() File "/home/pai/lib/python3.9/site-packages/composer/core/state.py", line 868, in get_model_state_dict model_state_dict = self.model.state_dict() File "/home/pai/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1818, in state_dict module.state_dict(destination=destination, prefix=prefix + name + '.', keep_vars=keep_vars) File "/home/pai/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1815, in state_dict self._save_to_state_dict(destination, prefix, keep_vars) File "/home/pai/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1722, in _save_to_state_dict hook(self, prefix, keep_vars) File "/home/pai/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context return func(*args, **kwargs) File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 669, in _pre_state_dict_hook _pre_state_dict_hook_fn[fsdp_state._state_dict_type]( File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 271, in _full_pre_state_dict_hook _common_unshard_pre_state_dict_hook( File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 143, in _common_unshard_pre_state_dict_hook _enter_unshard_params_ctx( File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_state_dict_utils.py", line 109, in _enter_unshard_params_ctx fsdp_state._unshard_params_ctx[module].enter() File "/home/pai/lib/python3.9/contextlib.py", line 119, in enter return next(self.gen) File "/home/pai/lib/python3.9/site-packages/torch/distributed/fsdp/_unshard_param_utils.py", line 186, in _unshard_fsdp_state_params assert ( AssertionError: Expects the handle training to be IDLE but got HandleTrainingState.BACKWARD_PRE Stack (most recent call last): File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 483, in del self.close() File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 512, in close self._close(self.state, self.logger) File "/home/pai/lib/python3.9/site-packages/composer/core/engine.py", line 529, in _close
Has anyone encountered this issue before? Why do I always get an error when I train with eight cards on a single machine for over 300 batchs, even though I definitely have enough training data?

@rzr002 Seems that you solved the issue, mind sharing what it was?


Dark Mode issues

PR: https://github.com/NationalSecurityAgency/skills-service/pull/2842

:+1:


[firebase_ml_vision] Support the v2 Android embedder plugins API

@amirh
The issue at https://github.com/flutter/flutter/issues/41875 has been closed and moved here. Future collaboration on this issue will be done here.

Hi @amirh
could you please provide your flutter doctor -v
and your flutter run --verbose.
Also, to better address the issue, would be helpful
if you could post a self contained app on github
or the steps to reproduce it.
Thank you

This is now supported.


vor bind error

i have this when i trying to launch
vor on the last version

i have found that was an app working in font of my pc than i she was closed


sftp doesnt upload correctly

When i upload a file with sftp it uploads to the home folder using the remote_path without any / or 's
in the config i have remote_path set to
"remote_path": "/var/www/",
in /home/heihachi its lists as
heihachi@code-breaker:~$ ls
development
downloads
exclude.txt
project-fire -> /var/www/
varwww
\var\www\config.dist.php
I was looking around in the source code and cant find any place where it would replace it

Hi guys,
Sorry for the long period of inactivity.
We are currently working on a new version : better code, more stable, and bug fixes.
This bug will be fixed at the next release.
Thank you for using our work ! :)

Hi guys,
A new version (1.0.0) was published tonight.
Feel free to reopen if the problem is still there.
Enjoy ! :D


generating sdk for ipam/vnv using 2024-01-01-preview

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


Error in running oncoplot and empty first columns

Hello,
Sorry, I am being stopped when running oncoplot
> oncoplot(maf = laml, top = 1, fontSize = 12)
Error in oncoplot(maf = laml, top = 1, fontSize = 12) :
  Cannot create oncoplot for single gene. Minimum two genes required !

Also I noticed I don't have any gene name
> head(var.annovar.maf[1:2,1:7])
   Hugo_Symbol Entrez_Gene_Id  Center NCBI_Build Chromosome
1:        <NA>             NA CSI-NUS       hg19         15
2:        <NA>             NA CSI-NUS       hg19          7
   Start_Position End_Position
1:       67547301     67547301
2:       48443570     48443570
>

Any help please to know what I am doing wrong?
Thank you so much

Hello!
How did you generate your maf files ?

Hi
I firstly used annovar to convert vcf so I used annovar output for your software
Thank you for replying me

Is it possible to share your maf file ?
Also it should be noted that maftools won't work with single sample.

Sorry what I have tried here was sample .vcf in vcf2maf software to get used to this tool but on my own .vcf I have stopped in producing maf files
I know this is unrelated to you but could you please help me to get maf file for your software?
I have called somatic SNV by Strelka; Long time I am trying vcf2maf to convert my .vcf files to maf required for any visualization tool like maftools but I am failing. I heard I can use annovar to get something compatible with maftools but annovar rejects .vcf from Strelka.
I am typing
-bash-4.1$ module load samtools/1.3.2
-bash-4.1$ module load ensembl-vep/95
-bash-4.1$ perl vcf2maf.pl --input-vcf /temp/hgig/fi1d18/strelka-2.9.2.centos6_x86_64/bin/demo_somatic_036_2post/results/variants/double_filtered_somatic_036_2post.snvs.vcf --output-maf tests/test.vep.maf --filter-vcf /home/fi1d18/ExAC_nonTCGA.r0.3.1.sites.vep.vcf.gz --ref-fasta /temp/hgig/fi1d18/hs37d5.fa --vep-path /local/software/ensembl-vep/95/vep --vep-data /home/local/software/ensembl-vep/95/cache/
But program returns empty maf
I have attached one of my .vcf files here
https://www.dropbox.com/s/4lc23an3rdcrios/filtered_1pre_021_somatic.snvs.vcf?dl=0
Could you please help me to convert my .vcf files to maf?
Thank you for any help


fix: always use posix paths

Since path.normalize creates Windows-preferred path separators on Windows, lint-staged fails on some Windows environments. This PR changes resolveGitDir to return a path via path.resolve instead, which seems a better choice.
See https://github.com/okonet/lint-staged/issues/669 for the bug report.

I've been looking at #669 this morning, and I don't think this will solve the problem for those in msys/cygwin environments. Any of the path functions will format the path based on the OS that node detects it's in, but really what I think we want is that we determine which path library to use (path.posix' or 'path.win32) based on the type of path git expects, and then use that in place of path throughout the library. In this case though only git can tell us what that path type is, and I haven't worked out how to reliably get that information.

Thanks for the response, @emily-curry. Let us look into this more then, before merging this. It would be nice to have a definitive fix, possible in the way you suggested (treating all paths consistently vased on posix/win32 env).

@emily-curry do you think you could manually test this change in your Windows environment? Since lint-staged doesn’t have a build process, you could simply edit the source from path.normalize to path.resolve.

@iiroj path.resolve('/c/Users/emily.curry/Code/use') (which is incorrectly using path.win32.resolve('/c/Users/emily.curry/Code/use')) evaluates to C:\\c\Users\emily.curry\Code\use.
We could use git rev-parse --absolute-git-dir to get the absolute path, and if it starts with a slash, use path.posix, else path.win32, and then somehow provide that path object to the rest of the library. The problem is testing it, a lot of the tests use things like process.cwd() which evaluates to a windows style path.

I wonder if using a library like normalize-path would help here.

It looks promising!
In the meantime, I've worked around this by using the git binary included with the git for windows bundle, instead of that installed via pacman.

I created a new PR here https://github.com/okonet/lint-staged/pull/678


Not an issue

Hey @hwalsuklee,
Thanks for sharing your code which helps me a lot. I have a question about the linear function in ops.py
I would be appreciated if you can explain what you are doing in the this function.
def linear(input_, output_size, scope=None, stddev=0.02, bias_start=0.0, with_w=False):
    shape = input_.get_shape().as_list()

    with tf.variable_scope(scope or "Linear"):
        matrix = tf.get_variable("Matrix", [shape[1], output_size], tf.float32,
                 tf.random_normal_initializer(stddev=stddev))
        bias = tf.get_variable("bias", [output_size],
        initializer=tf.constant_initializer(bias_start))
        if with_w:
            return tf.matmul(input_, matrix) + bias, matrix, bias
        else:
            return tf.matmul(input_, matrix) + bias

Also, It would be great if you add some comments when you are implementing; to be much easier for others to understand.
Thanks.

Hi.
As it is mentioned on the top in ops.py, this is borrowed from  https://github.com/carpedm20/DCGAN-tensorflow
It is just an implementation of fully connected layer.
Input×weight+bias
Hwalsuk Lee

Thanks, you can close this issue.


Module Resolution Issue In 0.33.X

The 0.33.X update seems to have changed how Volar supplies paths to TypeScript to check in some manner.
I have a monorepo project that uses yarn, TypeScript, Vue, and Pug. Prior to 0.33.0, this is how my App.vue would load:

After the 0.33.0, I began getting JSX issues:

I thought it might be a Pug related issue, but when I swapped to HTML:

The issue is resolved when I run npm install within the sr6tk-client folder, which tells me something has changed so that Volar doesn't handle a monorepo setup with Yarn as well anymore. Any suggestions on what I'm doing wrong?

I think this might be an issue with my monorepo setup. I didn't have it configured correctly via yarn as I was missing the package declarations in the package.json file. Once I did and the packages were listed correctly in yarn workspaces info, running yarn began to add a node_modules\.bin folder which references some executables. That might be the difference. I'm going to close for now, assuming I'm the one at fault, and someone else can reopen if there's something new.


code update problem

Hi, I am very interested in the work you do. When will the code be updated?

Hi, thank you for your interest!
I plan to update this month (latest next month). If you have any specific questions, feel free to drop me an email

Hi,i am very interested in your work，when will the code will be updated？

Hi,i am very interested in your work，when will the code will be updated？

Hi,i am very interested in your work，when will the code will be updated？