feat: cleanup cert/key info in tls config for ensuring service account will be used

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind bug
/kind documentation
/kind enhancement
/kind good-first-issue
/kind feature
/kind question
/kind design
/sig ai
/sig iot
/sig network
/sig storage

/kind feature
What this PR does / why we need it:
cleanup cert/key info in tls config of yurt-manager for ensuring serviceaccount will be used.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Does this PR introduce a user-facing change?

other Note

/LGTM

Why we need this? If we provide --kubeconfig option to  yurt-manager, this code makes yurt-manager fails to access the server.

Why we need this? If we provide --kubeconfig option to yurt-manager, this code makes yurt-manager fails to access the server.

@fungaren each controller will use unique service account to access kube-apiserver in order to manage rbac settings for each controller.
The case of --kubeconfig option can not work, I think this pull request maybe fixed this problem.
https://github.com/openyurtio/openyurt/pull/2193


Allow customizing the suffix function in multiprocess mode (instead of os.getpid())

One frequent issue with using prometheus_client in multiprocess mode is that you can end up with a lot of files which can severely impact the collecting performance ending with scraping timeouts in the worth cases.
This comes from the fact that to prevent concurrent usage, prometheus_client uses os.getpid() to name its metrics file and ensure that each process only touches its own files: it's a perfectly good and simple design.
However for long running processes spawning new processes every few minutes you can end up with several thousands files after a few months.
But in some cases, you have access to other methods to ensure that each process is uniquely identified (and ensure that each process only touches uniquely identified metrics files).
Would it be possible to allow customizing (& document as public API) the function generating metrics file suffix ?
(Of course, this would still be an use-at-your-own-risk escape hatch).
I'm speaking of:
https://github.com/prometheus/client_python/blob/e58301600c47d5c93985b83490bc57903af2918e/prometheus_client/values.py#L31
For instance, using uWSGI, we might want to use uwsgi.worker_id():
from prometheus_client import values
import uwsgi

values.ValueClass = values.MultiProcessValue(uwsgi.worker_id)

Or when each worker has its own task and you can ensure that only one worker at a time is dealing with this task (thanks to a postgres advisory lock in my case).
def prometheus_pid_func():
    return os.getenv("PROMETHEUS_WORKER_TASK_ID", str(os.getpid()))

from prometheus_client import values
values.ValueClass = values.MultiProcessValue(prometheus_pid_func)

The problem is that that isn't safe if the process then later forks, it took a while to get the current logic right and I'm not sure how correctly it'll work with anything that's not actually a pid.

The problem is that that isn't safe if the process then later forks, it took a while to get the current logic right and I'm not sure how correctly it'll work with anything that's not actually a pid.

Yes, hence the "use-at-your-own-risk escape hatch".
This would be clearly documented as a "I know what I'm doing" hook but I think that in most cases the user has a fairly good understanding whether its code will spawn a subprocess or not (typically web server workers don't).

I don't think this is something that should go in the readme, we already have issues with users failing to follow the docs that are there and this would be handing them a chainsaw to juggle. I am open to code changes that'd make this easier to do for those who know what they're up to though.

I believe this can be closed now.

I believe this can be closed now.


Explicitly show how to cast getBody() result to string.

Lot of tutorials still show example of:-
$body = $response->getBody(true);

to get a string as a result. This confuse me a lot until I found that it no longer apply in recent version.

I don't think this is needed. A comment about a previous version just adds to the confusion I think, and documentation shows that it can be cast to a string which is thoroughly documented on php.net. I'd merge a PR that only showed casting the body to a string, but this PR has a lot of extraneous additions.


Queue Reconstruction By Height

Coverage remained the same at 100.0% when pulling e6a9d73bb01b4cb1eb3acd4e06c24f6606dc6f0a on queue-reconstruction-by-height into ca3001ff7835b37d3a014f241ab20c9d28ea2045 on master.


Selection stuck on mouse movement

Prerequisites

[X] Can you reproduce the problem in safe mode?
[X] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[X] Did you check the FAQs on Discuss?
[X] Are you reporting to the correct repository?
[X] Did you perform a cursory search to see if your bug or enhancement is already reported?

Description
After I click in an editor window, moving the mouse will select the text. Atom behaves as if I did not release the mouse button.
Steps to Reproduce

Start atom (in normal or safe mode) and open an editor
Press and release the left mouse button
Move the mouse cursor

Expected behavior: [What you expected to happen]
Text should not be selected because I clicked and  released the mouse button
Actual behavior: [What actually happened]
Text is selected as if I had not release the mouse button
Versions
Atom    : 1.7.3
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1
on
Ubuntu 15.10 (Wily Werewolf)

I have the same problem. Same steps as above
Versions
Atom    : 1.7.3
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1
on
Fedora 23

Same problem with version 1.5.4

Can any of you reproduce this on the latest master? We recently updated the version of Electron to v0.37.8 on master (which brings Chrome 49 with it) and I wonder if that fixes things.

I see this in 1.8 beta. building master now..

The version of Electron I mentioned above should now be in the Beta channel. Let us know if anyone is still running into this!

I had this issue on Arch Linux for ages, too (ever since the first Atom release) . It seemed to be triggered randomly and can not be fixed for me by reopening the file. It also affects all files I open in Atom.. Not even a restart of Atom helps. I'd be happy to provide more details if you tell me what exactly you need (it is reproducable in safe mode, but I don't know what triggers it)

Update: Issue is present in 1.8.0. B3, too. I have as of now found no way of fixing this problem once it occurs with my Atom installation.

@XYunknown As @lee-dohm mentioned above, please try the 1.9.0 betas.

Tried 1.9, still the same issue.

What I do on Linux to fix this is to restart into a Wayland session, then
log back in an X11 session. Works every time.
On Jun 18, 2016 4:38 AM, "XYunknown"<EMAIL_ADDRESS>wrote:

Tried 1.9, still the same issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/11691#issuecomment-226929715, or mute
the thread
https://github.com/notifications/unsubscribe/AAIm_k1GMEuXoH5lVuSzt39QaDiLlsAdks5qM66VgaJpZM4IW_LL
.

I suspect this to be a problem with X and electron, too. But your proposed solution doesn't solve the issue in the long run.. It works for me again after restarting X. This might be a bug in electron?

Same problem on Fedora 23 GNOME
Atom    : 1.8.0
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1

I was able to reproduce this on Fedora 24 GNOME
Atom    : 1.8.0
Electron: 0.36.8
Chrome  : 47.0.2526.110
Node    : 5.1.1

Start Atom
Suspend
Resume
Click anywhere in an open file and try to move the mouse.

if I ignore it sometimes goes away but always comes back after resume, I am pretty sure the problem is limited to the touchpad and not a usb mouse.
I switched my session to wayland and so far problem seems to be fixed for me.

@emptyemail Try Atom 1.9.8 and see if that works.

@50Wliu works much better, no issues yet. Thanks!

@50Wliu I spoke too soon, looks like its happening again.

I have the same problem
atom 1.10.2

Have it too

The same here:
Fedora 24 with Gnome 3.20.2
Atom 1.10.0
A lot of comments suggests a relation to Gnome shell.

I have the same problem.
Ubuntu Gnome 16.10
Atom 1.10.2

I can reproduce it on Fedora 24 with Gnome 3.20.4 and Atom 1.10.0
I can reliably trigger the select behavior by opening the screen keyboard with https://extensions.gnome.org/extension/993/slide-for-keyboard/ while the screen keyboard is disabled in accessibility settings.
A tap on the touchscreen fixes it.
Atom doesn't need to be running while doing these things.

Same on Ubuntu 16.04 LTS with Gnome 3.18.5, Atom 1.9.9. Atom restart doesn't help. Tired rebooting computer two times a day (-:

Archlinux here, and its happening very frequently.

I have the same issue. Archlinux with i3 as WM here. I used to be able to fix this issue by using xinput to disable and enable my touch screen, which would periodically fix it, but now this no longer fixes it (after a recent system upgrade).

I'm on Atom 1.10.2, Gnome 3.22 and even closing the application didn't help until I tapped Atom with the touchscreen.  Wow, super annoying but I'm happy that it can be fixed.

I use a Mac Book Pro running Ubuntu 16.04 in a VM and see the same problem. I also use an external mouse and just discovered that once this occurs with my external mouse, tapping the touch pad fixes it. Maybe for those without a touch screen/pad, moving your mouse to a different USB port and clicking could help? Still sucks, but maybe better than rebooting until this is fixed.

@dschissler Same here, thanks, tap with a touchscreen helps!

Same issue
Arch (Manjaro) with Gnome, 'fixed' by tapping the touchscreen.
I just wanted to comment so I get updates for this thread.

1.10.2 on Fedora 25
STILL same issue, and touching or disable/renabling the touchscreen via xinput no longer solves it.

Thanks for the thread, thought I'd shed some light on the situation.
This doesn't seem to be a problem with Electron or Atom specifically. I'm running GNOME 3.20 with a touchscreen, and occasionally my system will enter a state where tapping anywhere onscreen will raise the onscreen keyboard (known as Caribou) in a smaller state (presumably to quickly enter keypresses when not typing large text.)

For reference, this is what Caribou normally looks like.

I have a hunch that the state of "Annoying Caribou" and Atom always highlighting selections are related somehow. "Annoying Caribou" seems to happen more often when I am using the "Slide For Keyboard" GNOME extension, and especially when I am using the "Caribou-Resize-Workspace" GNOME extension.
If this helps narrow down why any of this is happening, I will be happy knowing I helped.

Like @Orangestar12 I have a notebook with touchscreen (but I don't use it).
The same problem on Ubuntu GNOME 16.10, Atom v.1.11.2.

I also confirm that a tap on the touch screen fixes the annoying behavior.

I can confirm was well running Debian testing that a tap on the touchscreen fixed this for me as well.

I sometimes get the same behaviour in IntelliJ if it can help.

I had the same issue.
I own a touchscreen laptop (looks like it's a quite common factor among those affected) and the issue happened only after it going to sleep and then a subsequent restore.
I was running atom-1.7.3-0.1.fc21.x86_64, on both on Fedora 23 and Fedora 24.  Restarting gnome wouldn't fix it.
I'm updating Atom to the latest version (atom-1.7.3-0.1.fc21.x86_64) and will see if the issue is fixed.

Well, looks like it's been fixed! 👍

I also have this issue on Fedora 25 GNOME 3.22. Tapping my touchscreen seemed to fix it too

same issue here on 1.13.1. Tapping the touchscreen is a good to know workaround. Thanks.

Same issue here on 1.13.0. I have the touchscreen disabled, so tapping it is not an option. What did the trick for me was enabling and disabling it again (using xinput).

Same issue here, Fedora 25 with Gnome, XPS 13 with touchscreen.

Same Issue here. Ubuntu 17.04 and touching the touchscreen solves it.... However, this is really annoying. Atom used to be my favorite Editor and I was close to abandoning it before I found this thread! Please fix this!

Same issue here on 1.17.2, Arch Linux and a touch screen, and like others, touching the touchscreen solves it.

I think the problem is more about the system/X than Atom because it happens with TeXstudio and Okular  as well, and they are all affected at the same time, i.e. if one if affected they all are.  Closing and restarting the programs has no effect, but simply giving some mouse input via the touchscreen fixes it, until the next time it happens of course.

A similar error seems to happen when using the touch screen with Eye of Gnome. Occasionally when doing swipes or taps, the tap will "catch" and any other taps are treated like a multi-touch tap around the first one, leading to many rotations and scalings.

Observation: using Visual Studio Code for ~6 months. There is no such bug in VS Code.

This is definitely a touchscreen related issue.
I have a Dell XPS 13 w/touch and I get the same behaviour in telegram, atom and sometimes some weirdness with items on the gnome dock when using mouse/touch pad.
When this happens, I found that if I start scrolling with the touchscreen the issue resolves itself.

@JamesTiberiusKirk Thank you

On Ubuntu Gnome 17.04 and atom 1.18.0. on a surface pro 3.
I can confirm that touching the screen fixes the problem

Same issue on Windows 7 SP1 64-bit and Atom 1.19.0 x64. I have no touchscreen to touch unfortunately, so the problem cannot be solved for me at the moment, rebooting doesn't help either.

have this issue right now on windows 10, this happening with my mouse (no touchscreen), please help :(

I had the same issue but restarting atom in safe mode fixed my issue, The only thing that worked without safe mode was renaming the .atom folder. Just started this morning do not know why/how it happened

Can confirm disabling atom-terminal-panel and restarting Atom stops this behavior

Nice work @Vitzkrieg. I also have atom-terminal and saw the deprecated function alert. But why today when I have had that plugin installed before the issue appeared.

Sounds like that's specifically causing the problem on Windows. I personally use the platformio-ide-terminal package and even then the issue appeared long before I installed that and long after I disabled it.

@Orangestar12 Difficult to pin-point your issue since you have the variable of "touchscreen" while in my case I use a vanilla setup. Removing my .atom directory fixed my issue, I did have a KB security update yesterday. I also checked my old .atom/packages folder for any files modified on yesterday. Nothing... So maybe the KB was the culprit in my case

The same for me normal mouse ( no-touchscreen)  on Win8.1 x64:
Atom: 1.19.1 x64
Electron: 1.6.9
atom-terminal-panel enabled - disabling stops this behavior!

Thank you @Vitzkrieg . Disabling atom-terminal-panel resolved this for me also.
Mac 10.12.6
Atom  1.19.2
normal mouse, no touchscreen

I was having this problem too after installing atom-terminal-panel. Uninstalled it and restarted Atom. Fixed.
Mac 10.11.3
Atom 1.19.1
Touchpad, Macbook Pro, no touchscreen.

I'm using Atom 1.15.0 x64 on Ubuntu 16.04, and a note with touchscreen.
From time to time this problem appears.
To solve it, I just touch anywhere in the text in the file edited.
I hope this information save someone or help to fix the bug.


npx nuxi@latest (3.7.3) is broken -  ERROR  Cannot start nuxt:  Cannot redefine property: __internal__deprecationWarning

Environment
On my current project:

Operating System: Darwin
Node Version:     v20.6.0
Nuxt Version:     3.7.3
CLI Version:      3.8.4
Nitro Version:    2.6.3
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      pages, modules, supabase, devtools
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

I've also tried to create a completely new project and see if it works, using:
npx nuxi@latest init

Operating System: Darwin
Node Version:     v20.6.0
Nuxt Version:     -
CLI Version:      3.8.4
Nitro Version:    -
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
Tried to upgrade from 3.7.1 to 3.7.3 an existing project but received:
ERROR  Cannot redefine property: __internal__deprecationWarning                                                                                18:21:36
at Function.defineProperty ()
at Object. (node_modules/@babel/types/lib/index.js:66:8)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Module.require (node:internal/modules/cjs/loader:1115:19)
at require (node:internal/modules/helpers:130:18)
at Object. (node_modules/@babel/types/lib/builders/validateNode.js:8:14)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
https://codesandbox.io/p/sandbox/nuxt-starter-z4660?file=/package.json:1,1-32,2
Describe the bug
My upgrade from 3.7.1 to 3.7.3 received:
ERROR  Cannot redefine property: __internal__deprecationWarning                                                                                18:21:36
at Function.defineProperty ()
at Object. (node_modules/@babel/types/lib/index.js:66:8)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Module.require (node:internal/modules/cjs/loader:1115:19)
at require (node:internal/modules/helpers:130:18)
at Object. (node_modules/@babel/types/lib/builders/validateNode.js:8:14)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
My package.json is:
{
"name": "nuxt-app",
"private": true,
"scripts": {
"build": "nuxt build",
"dev": "nuxt dev",
"generate": "nuxt generate",
"preview": "nuxt preview",
"postinstall": "nuxt prepare"
},
"prisma": {
"seed": "node prisma/seed.js"
},
"devDependencies": {
"@nuxt/devtools": "latest",
"@nuxtjs/supabase": "^1.1.0",
"nuxt": "^3.7.3"
},
"dependencies": {
"@headlessui/vue": "^1.7.16",
"@heroicons/vue": "^2.0.18",
"@jridgewell/sourcemap-codec": "^1.4.15",
"@nuxtjs/tailwindcss": "^6.8.0",
"@pinia/nuxt": "^0.4.11",
"@prisma/client": "^5.3.0",
"@rollup/plugin-terser": "^0.4.3",
"@vite-pwa/nuxt": "^0.1.1",
"nuxt-icon": "^0.5.0",
"prisma": "^5.3.0",
"uuid": "^9.0.1"
}
}
I've also tried to create a new project using npx nuxi@latest init  and similarly it is broken.
package.json is:
{
"name": "nuxt-app",
"private": true,
"type": "module",
"scripts": {
"build": "nuxt build",
"dev": "nuxt dev",
"generate": "nuxt generate",
"preview": "nuxt preview",
"postinstall": "nuxt prepare"
},
"devDependencies": {
"@nuxt/devtools": "latest",
"nuxt": "^3.7.3"
}
}
ERROR  Cannot redefine property: __internal__deprecationWarning                                                                                18:38:39
at Function.defineProperty ()
at Object. (node_modules/@babel/types/lib/index.js:66:8)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1295:10)
at Module.load (node:internal/modules/cjs/loader:1091:32)
at Module._load (node:internal/modules/cjs/loader:938:12)
at Module.require (node:internal/modules/cjs/loader:1115:19)
at require (node:internal/modules/helpers:130:18)
at Object. (node_modules/@babel/types/lib/builders/validateNode.js:8:14)
at Module._compile (node:internal/modules/cjs/loader:1241:14)
Needless to say it was working before the upgrade.
Additional context
No response
Logs
(base) XXXX ~/mydev/projects  $ tail -100 /Users/XXXX/.npm/_logs/2023-09-17T17_37_16_032Z-debug-0.log
4685 timing build:link:node_modules/@npmcli/run-script/node_modules/which Completed in 6ms
4686 timing build:link:node_modules/cacache/node_modules/glob Completed in 6ms
4687 timing build:link:node_modules/is-wsl/node_modules/is-docker Completed in 6ms
4688 timing build:link:node_modules/make-dir/node_modules/semver Completed in 6ms
4689 timing build:link:node_modules/make-fetch-happen/node_modules/glob Completed in 6ms
4690 timing build:link:node_modules/postcss-url/node_modules/mime Completed in 6ms
4691 timing build:link:node_modules/node-gyp/node_modules/nopt Completed in 6ms
4692 timing build:link:node_modules/postcss/node_modules/nanoid Completed in 6ms
4693 timing build:link:node_modules/@nuxt/devtools Completed in 8ms
4694 timing build:link:node_modules/open/node_modules/is-docker Completed in 6ms
4695 timing build:link:node_modules/@mapbox/node-pre-gyp Completed in 8ms
4696 timing build:link:node_modules/@nuxt/devtools-wizard Completed in 8ms
4697 timing build:link:node_modules/@nuxt/telemetry Completed in 8ms
4698 timing build:link:node_modules/@npmcli/installed-package-contents Completed in 8ms
4699 timing build:link:node_modules/autoprefixer Completed in 8ms
4700 timing build:link:node_modules/send/node_modules/mime Completed in 6ms
4701 timing build:link:node_modules/@vercel/nft Completed in 8ms
4702 timing build:link:node_modules/acorn Completed in 8ms
4703 timing build:link:node_modules/crc-32 Completed in 7ms
4704 timing build:link:node_modules/browserslist Completed in 7ms
4705 timing build:link:node_modules/read-package-json/node_modules/glob Completed in 6ms
4706 timing build:link:node_modules/vite/node_modules/esbuild Completed in 6ms
4707 timing build:link:node_modules/errno Completed in 7ms
4708 timing build:link:node_modules/esbuild Completed in 7ms
4709 timing build:link:node_modules/color-support Completed in 7ms
4710 timing build:link:node_modules/cssesc Completed in 7ms
4711 timing build:link:node_modules/esno Completed in 7ms
4712 timing build:link:node_modules/jiti Completed in 7ms
4713 timing build:link:node_modules/flat Completed in 7ms
4714 timing build:link:node_modules/is-docker Completed in 7ms
4715 timing build:link:node_modules/giget Completed in 7ms
4716 timing build:link:node_modules/is-inside-container Completed in 7ms
4717 timing build:link:node_modules/esprima Completed in 7ms
4718 timing build:link:node_modules/listhen Completed in 7ms
4719 timing build:link:node_modules/mime Completed in 7ms
4720 timing build:link:node_modules/json5 Completed in 7ms
4721 timing build:link:node_modules/nitropack Completed in 7ms
4722 timing build:link:node_modules/js-yaml Completed in 7ms
4723 timing build:link:node_modules/mkdirp Completed in 7ms
4724 timing build:link:node_modules/jsesc Completed in 7ms
4725 timing build:link:node_modules/node-gyp Completed in 7ms
4726 timing build:link:node_modules/node-gyp-build Completed in 7ms
4727 timing build:link:node_modules/nypm Completed in 7ms
4728 timing build:link:node_modules/nanoid Completed in 7ms
4729 timing build:link:node_modules/nuxi Completed in 7ms
4730 timing build:link:node_modules/nopt Completed in 7ms
4731 timing build:link:node_modules/resolve Completed in 7ms
4732 timing build:link:node_modules/openapi-typescript Completed in 7ms
4733 timing build:link:node_modules/pacote Completed in 7ms
4734 timing build:link:node_modules/rimraf Completed in 7ms
4735 timing build:link:node_modules/semver Completed in 7ms
4736 timing build:link:node_modules/rollup Completed in 7ms
4737 timing build:link:node_modules/svgo Completed in 7ms
4738 timing build:link:node_modules/terser Completed in 7ms
4739 timing build:link:node_modules/untun Completed in 7ms
4740 timing build:link:node_modules/rollup-plugin-visualizer Completed in 7ms
4741 timing build:link:node_modules/tsx Completed in 7ms
4742 timing build:link:node_modules/vite Completed in 7ms
4743 timing build:link:node_modules/vite-node Completed in 7ms
4744 timing build:link:node_modules/untyped Completed in 7ms
4745 timing build:link:node_modules/update-browserslist-db Completed in 7ms
4746 timing build:link:node_modules/wait-on Completed in 7ms
4747 timing build:link:node_modules/vscode-languageserver Completed in 7ms
4748 timing build:link:node_modules/which Completed in 7ms
4749 timing build:link:node_modules/node-gyp/node_modules/which Completed in 6ms
4750 timing build:link Completed in 8ms
4751 info run<EMAIL_ADDRESS>postinstall node_modules/esbuild node install.js
4752 info run<EMAIL_ADDRESS>postinstall node_modules/@esbuild-kit/core-utils/node_modules/esbuild node install.js
4753 info run<EMAIL_ADDRESS>postinstall node_modules/vite/node_modules/esbuild node install.js
4754 info run<EMAIL_ADDRESS>postinstall { code: 0, signal: null }
4755 timing build:run:postinstall:node_modules/vite/node_modules/esbuild Completed in 197ms
4756 info run<EMAIL_ADDRESS>postinstall { code: 0, signal: null }
4757 timing build:run:postinstall:node_modules/@esbuild-kit/core-utils/node_modules/esbuild Completed in 283ms
4758 info run<EMAIL_ADDRESS>postinstall { code: 0, signal: null }
4759 timing build:run:postinstall:node_modules/esbuild Completed in 421ms
4760 timing build:run:postinstall Completed in 422ms
4761 timing build:deps Completed in 438ms
4762 timing build Completed in 438ms
4763 timing reify:build Completed in 440ms
4764 timing reify:trash Completed in 3ms
4765 timing reify:save Completed in 91ms
4766 timing reify Completed in 82812ms
4767 timing command:install Completed in 83371ms
4768 verbose stack Error: command failed
4768 verbose stack     at ChildProcess.<anonymous> (/opt/homebrew/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:53:27)
4768 verbose stack     at ChildProcess.emit (node:events:514:28)
4768 verbose stack     at maybeClose (node:internal/child_process:1105:16)
4768 verbose stack     at ChildProcess._handle.onexit (node:internal/child_process:305:5)
4769 verbose cwd /Users/xxxxx/mydev/projects/xxxxx
4770 verbose Darwin 22.6.0
4771 verbose node v20.6.0
4772 verbose npm  v9.8.1
4773 error code 1
4774 error path /Users/xxxxx/mydev/projects/xxxx
4775 error command failed
4776 error command sh -c nuxt prepare
4777 verbose exit 1
4778 timing npm Completed in 83462ms
4779 verbose code 1
4780 error A complete log of this run can be found in: /Users/XXXXXXX/.npm/_logs/2023-09-17T17_37_16_032Z-debug-0.log

This was an upstream bug in Node 20.5 that is now resolved upstream: https://github.com/nuxt/nuxt/issues/23020

Oh, silly me, I should have tried rolling back to node TLS!
Lots of thanks @danielroe, super appreciated !!
I didn't install beyond TLS consciously - I think brew upgrade did it.
For those who have mac, to downgrade back to TLS in brew:
brew install node@18
brew unlink node
brew link node@18
node -v

Dear fellow humans.
Always be on the safe side and install node v.18.18.2 which is the LTS.


VS Code just deleted all my files

Type: Performance Issue
This is an emergency. I clicked source control and initialize repository then it connected to my pc. I later hit reverse saved changes and it deleted all my files permanently. I need them recovered please I can't find them anywhere... obviously i never commited anything because i didnt want to commit my personal files to github and now I've lost it all
VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:48:05.904Z)
OS version: Windows_NT x64 10.0.19045
Modes: Unsupported

System Info

Item
Value

CPUs
AMD Ryzen 5 5600 6-Core Processor               (12 x 3500)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.93GB (18.16GB free)

Process Argv
--crash-reporter-id f61b7fa5-ddc2-4c34-9f2b-5614a991840c

Screen Reader
no

VM
40%

Process Info
CPU %	Mem MB	   PID	Process
    1	    99	 16836	code main
    0	   105	  1564	shared-process
    1	   215	  5672	extensionHost [1]
    0	    39	  8816	   utility-network-service
    0	    28	  9060	   crashpad-handler
    0	    98	 12320	   gpu-process
    0	    83	 19172	fileWatcher [1]
    0	   508	 20396	window [1] (version_2.py - recovery - Visual Studio Code)
    0	    89	 20528	window [2] (Issue Reporter)

Workspace Info
|  Window (version_2.py - recovery - Visual Studio Code)
|    Folder (recovery): more than 73574 files
|      File types: gif(3679) xml(1330) png(1022) pyi(866) dll(643) mui(527)
|                  p7x(515) t(256) file(251) svg(147)
|      Conf files:;

Extensions (17)

Extension
Author (truncated)
Version

copilot
Git
1.128.0

copilot-chat
Git
0.8.0

remotehub
Git
0.62.0

gc-excelviewer
Gra
4.2.58

vscode-dotnet-runtime
ms-
1.8.1

python
ms-
2023.18.0

vscode-pylance
ms-
2023.10.40

jupyter
ms-
2023.9.1102792234

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.17

vscode-jupyter-cell-tags
ms-
0.1.8

vscode-jupyter-slideshow
ms-
0.1.5

remote-wsl
ms-
0.81.8

azure-repos
ms-
0.38.0

remote-repositories
ms-
0.40.0

azurerm-vscode-tools
msa
0.15.11

perl
ric
2.6.1

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
py29gd2263:30856252
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
3biah626:30602489
f6dab269:30613381
vscrp:30673768
2i9eh265:30646982
showlangstatbar:30737416
03d35959:30757346
pythonfmttext:30731395
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30866041
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
copilotsettingc:30859502
dsvsc013:30795093
dsvsc014:30804076
diffeditorv2:30821572
dsvsc015:30845448
pyreplss1:30865275
pythonmypyd1:30859726
pythontbext0:30864172

Did you get a confirmation dialog like this? If so, how did you respond to it?

I tried cancelling and undoing the connection but was unable to disconnect the repository after clicking on the top button of the 2 in the source control tab. I restarted but was still unable to disconnect. I was under the assumption it would permanently remove them from being attached to my vs code/repository but it turns out it's for the drive on my pc. I had to use easeUS to recover what I could, system restore and recuva didn't help. most my larger files ended up being corrupted. Would running check disk or something similar help with fixing the corrupted files or should I just reformat and move on with what I have recovered already?


Kata Containers 1.11.0-alpha1

scripts: set a default path to the yq binary
AArch64: Build rust image on aarch64
image-builder: Add NSDAX_BIN for passing in compiled nsdax tool
rootfs: Don't overwrite /sbin/init if it already exists
tests: Improve running test_images.sh locally

1c063af scripts: set a default path to the yq binary
67343a1 rust-agent: Separate the build up of rust-agent and go-agent
a390a36 rootfs: remove RUST_SRC_PATH
41aaa36 ubuntu/debian: create aarch64-specific Dockerfile.in
9cba8c4 musl: install musl on aarch64
87a5d5c rootfs: Don't overwrite /sbin/init if it already exists
4004bd8 image-builder: Add NSDAX_BIN for passing in compiled nsdax tool
134175b tests: Document the changed KATA_DEV_MODE behavior
0f4eac4 tests: Skip initrd/image launch if KATA_DEV_MODE
762ec28 tests: Drop kata-runtime env validation if KATA_DEV_MODE is set
6f17b9c tests: Skip set_runtime if KATA_DEV_MODE is set
17a8fb1 tests: Skip all kata-manager usage if KATA_DEV_MODE is set
e787bb0 tests: Define KATA_DEV_MODE
cef2591 tests: Rework dracut docker bind mounts
f3ab6d2 tests: Don't run commands with chronic if DEBUG is set
7a8e816 tests: Specify DRACUT_OVERLAY_DIR
7dd99c0 tests: Add project_dir helper variable
1ae3922 tests: Have DEBUG=1 set bash xtrace
555ddf3 tests: Remove unused USE_DOCKER export
0e6a12c tests: Pass DOCKER_RUNTIME to osbuilder scripts
e8624d8 tests: Rename docker_build_runtime -> DOCKER_RUNTIME
cd46d09 tests: Remove hardcoded 'runc' reference
c574ec0 tests: Remove dead unset images_dir check
44f2931 tests: Remove unused test_func_prefix

/test


Only allow clicks on 'manage chat channels' icon on teams list if you're a member of the team

@keybase/react-hackers
Trying to load Manage Chat Channels for a team you're an implicit admin of doesn't work, so remove the onClick handler from the icon on the main team list in that case.
While we have yourOperations entries for a team once you've loaded it, the main team list is rendered without any teams loaded.  Instead we get an untrusted team list from the server.  That includes a field for our role in each team, so this PR uses "role !== 'none'" as the canManageChannels equivalent, rather than yourOperations.

Why show the icon at all? Seems like that was the intent of the original jsx, but they never passed in null.

@buoyad Yeah, I tried that first but didn't like the way it looked:

So I guess our choices are:

this screenshot

chat icon isn't present if you can't chat and there's an empty space where it would otherwise be, pushing the files icon to its usual place

chat icon is always present but doesn't have a click handler (so no color change on hover) if you can't chat

chat icon is always present but has some kind of opacity applied if you can't chat

@keybase/design, what'd you think?  This is for the team list when you're an implicit admin of a team so you can't go into its chat channels screen yet.

Any reason to not swap the order (chat then folder)?

Rather than hiding the Chat icon, why not disabling it and have a tooltip that says "You need to be a member of the team to be able to chat."?

Cool, this should do it.  (Does this seem like the best way to do a conditional tooltip?)


value of $\tau$

Hi Thanks for the great work, I wonder how this $\tau$ value in Eq. 1 is calculated? In the paper, it is said τ is the pre-defined maximum feature magnitude determined on the trainset only i.e., point at which the distributions first meet, can you please provide any codes for this calculation?

Hi Thomas, $\tau$ can be estimated by first plotting the distributions as shown in Figure 1 of the main paper. You can refer to the code in plots_cm16.py to get the gist. Alternatively, you can set $\tau =  10$  or $\tau =  100$, depending on the task this should still allow the model to learn separability between classes. Hope this helps.


ENG-7825 - Add new startAppFlow Command

Add new command for multi use case in one app
Will work with existing start/startSession commands
Adds linkedSiteId to packet header for backend use. This will be cleared on stop/stopSession but not before.

Sonar error is on test duplication but should be ignored


Import name fix

Change import name to nacl_encrypted_fields
Move settings.py to tests app
Exclude tests app in setup.py

Moved to #9


community: OpenAPI agent - support PUT, DELETE and PATCH

Description: Add PUT, DELETE and PATCH tools to tool list for OpenAPI agent if dangerous requests are allowed.
Issue: https://github.com/langchain-ai/langchain/issues/20469

@eyurtsev Ok, it is a good point, I will add it.

@eyurtsev GET requests will be definitely in the default settings but do you want to keep POST requests there as well?

@eyurtsev If you are ok with the update, I believe we should also update this doc.

@eyurtsev Also, could you guess why dependency checks and tests fail with the following error?

=========================== short test summary info ============================
FAILED tests/unit_tests/embeddings/test_ovhcloud.py::test_ovhcloud_embed_documents - ValueError: Request failed with status code: 401, {"message":"Bad token; invalid JSON"}
========== 1 failed, 890 passed, 471 skipped, 4440 warnings in 11.71s ==========
make: *** [Makefile:19: test] Error 1
Error: Process completed with exit code 2.

It's a bug on master. I'm on mobile right now so can't do it from the phone, but you should be able to use the UI to update the PR to use latest master, if not I'll do it on your behalf when back at a computer

@pow3rpi could you allow maintainers to edit the PR -- that would allow me to resolve issues and merge in the future


CHALLENGE! Let's try something new!

@axseinga @aaron-watts
I want to try something new!

Create a new yourname.html page in /docs.
Link that new page to a new yourname.css file in /docs/css.
If you need images, save them to /docs/images.
Add a yourname.js if you like in /docs/scripts.
Modify the existing /src/index.html and insert a simple navigation menu linking to your new .html page.

Not really a difficult challenge.
But if more than one person modifies the index.html and submit Pull Requests at the same time, this gives me the opportunity to see how a more complicated Merge works.
Comment below if you would like to have a try at this, thanks!

@dvdmon
:) Will you accept this Challenge?
Instructions at the top.

@jjaimealeman thanks for tagging me.  Just started looking around so hadn't looked in the docs folder yet, and am not familiar enough with Github to look at "Issues" (so will have to look at that as well, lol).  But yes, I'll do this but it will need to wait till tomorrow.  Unlike the cliche programmer, I tend to go to sleep on the earlier side.  11:30pm is actually pretty late for me  to be still up on the computer, although it IS a Saturday!


5.x

Add "Express.js Blueprints, Packt Publishing, May 2015" to Books section.
(

)

@gavincardoza please don't use the 5.x branch for now.

@gavincardoza Please open a new PR against the gh-pages branch which determines what's on expressjs.com.   We're not currently working on the 5.x branch.


Add a boolean in CheckSchemaRequest to differentiate checking new schema from already registered schemas

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


Differences from existing platforms

Matrix is an widely-adopted, federated, and mature chat protocol with a wide variety of clients. It can bridge to many chat networks including Discord, Slack, Telegram, WhatsApp, Instagram DM, and many more.
ActivityPub is a widely-adopted, standardized, federated and mature microblogging and forum protocol (used by Mastodon, Lemmy, PeerTube, Pixelfed, Pleroma, Misskey, WriteFreely). Each platform has multiple client app alternatives.
Federation using an existing protocol is an advantage that every open source project needs.
Any new ActivityPub-based project starts with an already existing user base, because they can reach users on other servers (even when they are using different software). So does any new Matrix client or server.
What are the advantages of building a centralized platform with no alternative client apps and a user base starting from zero?

I appreciate your interest in the project. Essentially, it comes down to a couple factors.

Meower's history. We have gone through many changes over the years without much focus. Over that period of time, developers started creating alternative clients without our "permission", but acceptance. Hence it became part of culture. Changing now would be hard to implement and make it more difficult for our established developers. We do have a bridge to Discord, though.

We want to control moderation and the stream of users, as well as the source of our userbase. Federation is prone to leaking users' information, which obviously causes multiple privacy concerns. Granted, we'd like our userbase to grow, and allowing other people to make clients is the best way to achieve that goal.

Hopefully that answered your question :) feel free to follow up if you have more.

Closing because of inactivity. Thanks for taking an interest, however!


Make this build on NetBSD/macppc specifically, and hopefully...

...improve portability to 32-bit ports:

Avoid trying to do u64 * u32, as rust may not implement that on 32-bit ports (it doesn't on 32-bit powerpc).
Fix type mismatch between variable and funciton parameter.
Fix XChangeWindowAttributes parameter declaration to match (u64 -> c_ulong).

Thanks for the PR!


Slow loading on lastest version

Describe the bug
loading local files are a bit slower, it loads for a while before starting the playback (on android)
on macos its the same speed as previous versions
network has the same problem, but it may be due internet speed
Expected behavior
it was much faster on previous versions
Log
https://justpaste.it/aifn6

The difference is previously ffmpeg 6.1 was used, now it's ffmpeg master branch. We noticed the performance downgrade a few months ago in ffmpeg 7.0 and later. We guess ffmpeg code is miscompiled or is broken. Can you try this https://sourceforge.net/projects/avbuild/files/android/ffmpeg-master-android-revert-8c936e9.tar.gz/download

The difference is previously ffmpeg 6.1 was used, now it's ffmpeg master branch. We noticed the performance downgrade a few months ago in ffmpeg 7.0 and later. We guess ffmpeg code is miscompiled or is broken. Can you try this https://sourceforge.net/projects/avbuild/files/android/ffmpeg-master-android-revert-8c936e9.tar.gz/download

Will try and let you know, can we open an issue for ffmpeg maybe it's something they can fix?

Need more tests to confirm which ffmpeg commit breaks

Need more tests to confirm which ffmpeg commit breaks

Okay, I will try to use the binaries you provided and if all is good then we can revert to it until we are sure all good I guess.

i am sorry i am confused on how to use this

The difference is previously ffmpeg 6.1 was used, now it's ffmpeg master branch. We noticed the performance downgrade a few months ago in ffmpeg 7.0 and later. We guess ffmpeg code is miscompiled or is broken. Can you try this https://sourceforge.net/projects/avbuild/files/android/ffmpeg-master-android-revert-8c936e9.tar.gz/download

replace mdk-sdk/lib/arm64-v8a/libffmpeg.so and rebuild

replace mdk-sdk/lib/arm64-v8a/libffmpeg.so and rebuild

doing that made the loading go from 3 sec to less than 0.5 sec, very weird that the higher version of ffmpeg has that problem

I'm reverting that commit in my build. I don't why, only android is slow, maybe a compiler bug

if you need me to test anything let me know , i dont mind trying again

the latest mdk's ffmpeg is patched. you can rebuild with env var FVP_DEPS_LATEST=1

ok thank you very much <3


User Friendly message should be displayed -> if the shared post is Deleted and viewed -> after sharing.

Open "https://staging.fightpandemics.work"
Login using valid email/pwd
Share own post using 'Share'

Test data - https://staging.fightpandemics.work/post/5f0d4323632a6c00124017c4 [link of shared post]
The post will shared successfully i.e. can be viewed from other phone or browser or so.

Now, delete the above shared post:

Issue: The shared link will not work and will be stuck in 'Loading' mode only.
Expected Result: User friendly message should be displayed that, the post is no longer available.
Note: This issue will come when the visibility of the POST expires as the post will be deleted as per the functionality by the shared link can be accessed for that respective post.

I'm not sure if we should have a specific message or redirect to 404. Thoughts @ppagarawal ?

I'm not sure if we should have a specific message or redirect to 404. Thoughts @ppagarawal ?

For such scenarios, we need to let the user know that the post has been deleted. This will be different from 404 message. Please update the user with a message "This post has been deleted.
Check our help board for more posts"
Embed a link on the helpboard to the helpboard.
@Yu-Alexa-Zhao it'll be good to create a new page design for such use cases.


Pod install conflicting names

After running npx pod-install and I got this error
Installing JitsiWebRTC (111.0.2)
Installing react-native-webrtc (111.0.0-daily.1)
[!] The 'Pods-Project' target has frameworks with conflicting names: webrtc.xcframework.
Couldn't install Pods. Updating the Pods project and trying again...
Command `pod install` failed.
└─ Cause: The 'Pods-Project' target has frameworks with conflicting names: webrtc.xcframework.

"react": "18.2.0",
"react-native": "^0.71.8"

Hi @rjuevesano,
If you remove node_modules and ios/Pods, and install the dependencies again, npm i and npx pod-install, are you still able to reproduce the issue ?

Since we are unable to reproduce it and haven't received further feedback, we are closing this issue for now. Feel free to create a new one in case you are still facing it.


weighttp benchmark fail - OSError: [Errno 22] Invalid argument

Long story short
aiohttp fails when benchmarking with weighttp
  File "/Users/walkr/.virtualenvs/main3/lib/python3.5/site-packages/aiohttp/parsers.py", line 256, in set_tcp_nodelay
    self._socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, value)
OSError: [Errno 22] Invalid argument

Actual behavior
It should not fail
Steps to reproduce
I'm benchmarking the following code:
from aiohttp import web

async def handle(request):
    name = request.match_info.get('name', "Anonymous")
    text = "Hello, " + name
    return web.Response(body=text.encode('utf-8'))

app = web.Application()
app.router.add_route('GET', '/{name}', handle)

web.run_app(app)

Then while benchmarking it with weighttp
$ weighttp -t 2 -c 10 -n 1000 localhost:8080/name

... I get the following error:
Error handling request
Traceback (most recent call last):
  File "/Users/walkr/.virtualenvs/main3/lib/python3.5/site-packages/aiohttp/server.py", line 266, in start
    yield from self.handle_request(message, payload)
  File "/Users/walkr/.virtualenvs/main3/lib/python3.5/site-packages/aiohttp/web.py", line 100, in handle_request
    yield from resp.write_eof()
  File "/Users/walkr/.virtualenvs/main3/lib/python3.5/site-packages/aiohttp/web_reqrep.py", line 857, in write_eof
    self.set_tcp_nodelay(True)
  File "/Users/walkr/.virtualenvs/main3/lib/python3.5/site-packages/aiohttp/web_reqrep.py", line 624, in set_tcp_nodelay
    self._resp_impl.transport.set_tcp_nodelay(value)
  File "/Users/walkr/.virtualenvs/main3/lib/python3.5/site-packages/aiohttp/parsers.py", line 256, in set_tcp_nodelay
    self._socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, value)
OSError: [Errno 22] Invalid argument

Any thoughts?
Your environment
Python: 3.5
Platform: OS X El Capitan

Wow! I believe MacOSX has TCP_NODELAY support.
Could you run the following snippet?
import socket
s = socket.socket()
s.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, True)
s.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, False)

No errors when I run the code.

I'm not able to reproduce this on either OSX 10.10.5 or 10.11.5.

I'm seeing the same issue with a similar repro, on OSX 10.10.5 and Python 3.5
I can see errors even if I run the benchmarks as:
weighttp -k -t 1 -c 1 -n 10 localhost:8080/
But it's more intermittent than when I'm doing more requests / higher concurrency, and I get lots of errors on average
It seems when the setsockopt call fails the raddr of the socket is not set, and trying to call socket.getpeername() on that socket also results in OSError: [Errno 22] Invalid Argument
Also, if I use wrk instead of weighttp I don't get any errors on a concurrency of 1, but as I increase concurrency I get n-1 errors at the end of a run, for instance:
wrk -t1 -c7 -d3s http://localhost:8080/
would give me exactly 6 OSError exceptions at the end of the 3 seconds run, or however long I make it
I'm not familiar enough with UNIX sockets but I'll see if I can diagnose it better

@asvetlov I concur the problem. I ran the same app on two different Macs with OS X 10.10.5 and 10.11.5 in a fresh virtualenv with Homebrewed Python 3.5.1 (only adjusted the port to 8889) and benchmarked it with wrk.
It stopped to reproduce on 10.11.5 after a while, but it never stopped on 10.10.5.
OS X 10.11.5
$ uname -a
Darwin daedra15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64 i386 MacBookPro12,1 Darwin
$ wrk -t1 -c7 -d3s http://localhost:8889/name
Running 3s test @ http://localhost:8889/name
  1 threads and 7 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     3.37ms    1.17ms  19.11ms   94.64%
    Req/Sec     2.12k   295.00     2.34k    90.32%
  6550 requests in 3.10s, 780.48KB read
Requests/sec:   2112.34
Transfer/sec:    251.70KB

$ python3 app.py
======== Running on http://<IP_ADDRESS>:8889/ ========
(Press CTRL+C to quit)
Error handling request
Traceback (most recent call last):
  File "/Users/semenov/work/socketerr/lib/python3.5/site-packages/aiohttp/server.py", line 266, in start
    yield from self.handle_request(message, payload)
  File "/Users/semenov/work/socketerr/lib/python3.5/site-packages/aiohttp/web.py", line 100, in handle_request
    yield from resp.write_eof()
  File "/Users/semenov/work/socketerr/lib/python3.5/site-packages/aiohttp/web_reqrep.py", line 857, in write_eof
    self.set_tcp_nodelay(True)
  File "/Users/semenov/work/socketerr/lib/python3.5/site-packages/aiohttp/web_reqrep.py", line 624, in set_tcp_nodelay
    self._resp_impl.transport.set_tcp_nodelay(value)
  File "/Users/semenov/work/socketerr/lib/python3.5/site-packages/aiohttp/parsers.py", line 256, in set_tcp_nodelay
    self._socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, value)
OSError: [Errno 22] Invalid argument
Error handling request

(the error repeated two times)
OS X 10.10.5
$ uname -a
Darwin eerie 14.5.0 Darwin Kernel Version 14.5.0: Mon Jan 11 18:48:35 PST 2016; root:xnu-2782.50.2~1/RELEASE_X86_64 x86_64
$ wrk -t1 -c7 -d3s http://localhost:8889/
Running 3s test @ http://localhost:8889/
  1 threads and 7 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency     4.40ms    0.88ms  15.03ms   96.30%
    Req/Sec     1.60k    98.95     1.69k    90.32%
  4944 requests in 3.10s, 835.42KB read
  Non-2xx or 3xx responses: 4944
Requests/sec:   1594.70
Transfer/sec:    269.47KB

$ python3 app.py
======== Running on http://<IP_ADDRESS>:8889/ ========
(Press CTRL+C to quit)
Error handling request
Traceback (most recent call last):
  File "/Users/vadim/socketerr/lib/python3.5/site-packages/aiohttp/server.py", line 266, in start
    yield from self.handle_request(message, payload)
  File "/Users/vadim/socketerr/lib/python3.5/site-packages/aiohttp/web.py", line 100, in handle_request
    yield from resp.write_eof()
  File "/Users/vadim/socketerr/lib/python3.5/site-packages/aiohttp/web_reqrep.py", line 857, in write_eof
    self.set_tcp_nodelay(True)
  File "/Users/vadim/socketerr/lib/python3.5/site-packages/aiohttp/web_reqrep.py", line 624, in set_tcp_nodelay
    self._resp_impl.transport.set_tcp_nodelay(value)
  File "/Users/vadim/socketerr/lib/python3.5/site-packages/aiohttp/parsers.py", line 256, in set_tcp_nodelay
    self._socket.setsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY, value)
OSError: [Errno 22] Invalid argument

(the error repeated 4 times)
Another more rare error on OS X 10.10.5
I got this a few times on 10.10.5:
======== Running on http://<IP_ADDRESS>:8889/ ========
(Press CTRL+C to quit)
Fatal write error on socket transport
protocol: <RequestHandler GET:/ connected>
transport: <_SelectorSocketTransport fd=13 read=polling write=<idle, bufsize=0>>
Traceback (most recent call last):
  File "/usr/local/Cellar/python3/3.5.1/Frameworks/Python.framework/Versions/3.5/lib/python3.5/asyncio/selector_events.py", line 702, in write
    n = self._sock.send(data)
OSError: [Errno 41] Protocol wrong type for socket

which then was followed by the above "Invalid argument" errors.

On my 10.10.5 it even happens in non-benchmark use, simply when the browser loads page images via router.add_static

Interestingly enough, when I benchmark 10.10.5 from different computers (Macs and Linuxes), it never spits a single error, even though the load is similar (>1K req/s).

Monkey patch for whoever needs it
from aiohttp.web_reqrep import StreamResponse
StreamResponse.set_tcp_nodelay = lambda self, value: None

This consistently removed all benchmarking errors on my Macs without degrading performance (actually performance even slightly increased).
Sorry for spamming, guys, that would be it.


server example is wrong

server example is wrong

@joestump assuming this is fixed in latest readme edits...


Change schema to conform to linkml

This repo has a biolinkml schema
there is a migration guide here
https://github.com/linkml/linkml/blob/f08d32ff94451676b67ad006d90bd6305c060065/Migration.md
but I think it should be simple, just change the CURIE in the imports

@cmungall I think I made the correct change: https://github.com/HOT-Ecosystem/tccm/pull/10/commits/7a8413238380ed4dc0fd5e082ca3eb12133d0322
I added to this PR: #10
These need to be regenerated in order for the update to be complete in rendered files, but I'm hesitant to do that righ tnow, as I don't think the directory / code structure will be finalized until @hsolbrig  reviews.

Thanks!
On Fri, May 6, 2022 at 2:01 PM Joe Flack @.***> wrote:

@cmungall https://github.com/cmungall I think I made the correct
change: 7a84132
https://github.com/HOT-Ecosystem/tccm/commit/7a8413238380ed4dc0fd5e082ca3eb12133d0322
I added to this PR: #10 https://github.com/HOT-Ecosystem/tccm/pull/10
These need to be regenerated in order for the update to be complete in
rendered files, but I'm hesitant to do that righ tnow, as I don't think the
directory / code structure will be finalized until @hsolbrig
https://github.com/hsolbrig reviews.
[image: Screen Shot 2022-05-06 at 4 55 03 PM]
https://user-images.githubusercontent.com/13045020/167215744-9d0e4b67-6945-454a-a9be-f89500aa17b2.png
—
Reply to this email directly, view it on GitHub
https://github.com/HOT-Ecosystem/tccm/issues/6#issuecomment-1120004537,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOOFJ4UBYM6A6KYYD4LVIWCAVANCNFSM5UTZCX3A
.
You are receiving this because you were mentioned.Message ID:
@.***>

Dang, you must have a long email backlog Chris! =P


fix(parse-dsl): fix issue with infinite loops triggered when parsing some models

Description
We had some issues in our grammar causing infinite loops when trying to parse, especially when extraneous spaces or newlines were found.
We still have some issues with parsing comments, but it has been limited.
References

Closes #77
Review Checklist

[x] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[x] I have added tests to validate that the change in functionality is working as expected

@adriantam this should be ready for review

Only question is whether we want to allow comment before "relations" - and we can defer this to later PR.  Other than that, LGTM.

Only question is whether we want to allow comment before "relations" - and we can defer this to later PR. Other than that, LGTM.

Comments before relations won't be allowed, but there should be one before define - however it is also triggering the infinite loop, so removed it for now.


Update GP installer to work in ArcGIS Pro and install arcrest in the correct enviroment

Update GP installer to work in ArcGIS Pro and install arcrest in the correct enviroment

@MikeMillerGIS this is most likely related to the use of virtual envs.


Adding PhysicsImpostor to mesh loaded from gltf causes unexpected collision area

Using plane.glb in plane.zip
Bug repro on https://playground.babylonjs.com/#6MTUAW
Updated repro that does not rely on gltf: https://playground.babylonjs.com/#6MTUAW#1
Expected result: collision matches rendered mesh position
Current result: collision seems to be where the mesh would be rendered if the rotation was left handed

Workaround this for now by setting:
plane.rotationQuaternion.x *=-1
plane.rotationQuaternion.y *=-1
This breaks the rendering of the mesh to the wrong position but fixes the collision hitbox.

@RaananW unless you have time to check it before end of next week


What is "the code"?

In the Aliases example, it says "and in the code use it as following:" but what is "the code"? The example puts it in the Program.cs file, but is that the only place it can go? Are there other places it could go instead?

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

ID: ff707668-94d6-25a5-9139-b18cc1b6b446
Version Independent ID: 494847b9-4894-0beb-7ffa-39a2359999fa
Content: NuGet PackageReference in project files
Content Source: docs/consume-packages/Package-References-in-Project-Files.md
Service: nuget
GitHub Login: @nkolev92
Microsoft Alias: nikolev

The example puts it in the Program.cs file, but is that the only place it can go? Are there other places it could go instead?

It can go in any file you want it to go in.
That is just 1 example as you said.


pull request for e2e test at 02/04/2017 18:26:08

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Chat changes

Created a Chat class and gathered chat related functions
Added min and max width to chat history style
Chat auto scrolling when scrolled to bottom
Fixed chat log of new connected players
Minor logic fixes

epic

(1)
Observation: When resizing the chat, you go up in chat a bit.
Expected: When resizing the chat, you should always stay at the position you were looking at (e.g. bottom of chat)
(2)
Observation: Clicking the chat history highlights it.
Expected: Clicking the chat history does not highlight it.
(3)
Observation: When client A connects everything works. When client B connects, client A does not receive a message saying client A connected.
Expected: See a message from client A when they connect from client B.

What do you mean they see a message when they connect from client B?

No Client name has joined messages are sent ever. Only disconnect messages are logged.

No Client name has joined messages are sent ever. Only disconnect messages are logged.

Are you saying that:
If client B joins AFTER client A, client A should receive a message? Or, when client B joins, client B should receive a message stating that client A joined?
Or something else?

I'm saying

If client B joins AFTER client A, client A should receive a message.


Adds polyfill support

This PR adds Polyfill support for node-fetch, this is required to use 3rd party packages which depend on fetch.
See the README changes for more info.

I beleve this was explicitly built for node. For browser version there is the https://github.com/github/fetch

This is for Node exclusively, NOT for the browser, NOT for isomorphic environments. You cannot use 3rd party modules that depend on or extend fetch, e.g. fetchival, frisbee etc. if you don't polyfill fetch in Node.
Same with the documentation for Webpack, it is exclusively for demonstrating how to use with the Webpack node target mode and will not work on the browser.

You cannot use 3rd party modules that depend on or extend fetch, e.g. fetchival, frisbee etc. if you don't polyfill fetch in Node.

https://github.com/typicode/fetchival#usage-examples has a Node.js example that doesn't use global fetch.
frisbee recommends isomorphic-fetch and uses global fetch, since it is designed to be isomorphic, not "Node exclusively."
All in all, this patch just goes against the Node.js way. If a Node.js-only module requires fetch being in the global scope, the module is doing it wrong.

@TimothyGu I don't agree with your assessment, in particular because fetch

@tarikjn, you raised some good points, but I believe that is slightly misguided.
babel-polyfill deals with a different issue: it polyfills standard JavaScript/ECMAScript features, while Node.js is designed as a full-featured JavaScript interpreter. In other words, babel-polyfill helps Node.js better fulfill its original mission.
node-fetch is a different case. Fetch is not part of standard JavaScript, but rather available as an open Web API. Node.js is not designed as a browser implementing Web APIs, and globalizing Fetch is actually making Node.js something it is not.
For a more radical example, one could look at how Promise is handled in node-fetch. Even though Promise is part of standard ECMAScript, instead of relying on a global Promise being always available as a browser module would, node-fetch allows using a custom Promise.
For the point about identical APIs, I believe your argument can be reduced to the following statement: because node-fetch emulates the browser API, it should emulate the browser behavior to the fullest extent – including a global reference, despite that being a big no-no in Node.js land. This is just like an Englishman who is learning French, insisting on speaking French in England, despite English being the common language in England.

That being said, I will not be extremely upset if this pull request gets merged, since the polyfill is not imported by default – what I am against is thinking of this module as if it is designed to be a polyfill in the sense that babel-polyfill is, which it is not.

Even if this patch is to be merged, a check for global.fetch is necessary so we aren't causing any conflicts (a problem only possible to occur if globals are polluted). We also might want to make global Response, Request, and other related classes, since they are marked as Exposed in the spec.

Here is my view on this:

A module designed for node.js should not depend on a global fetch, because node.js core doesn't have it.

I don't see why node-fetch need to provide this, because it's a one-line module and you can already write yourself, and better yet, publish on npm (there is probably existing ones).

I don't see the reason to avoid isomorphic-fetch, which does add a global fetch to your code.

I'm using node-fetch only on the server. So this is not something I would really want to be merged.
node-fetch is also not fully poly filled if a third party lib would think that it exist then it could fail cuz of it when it trying to do res.blob() which node-fetch or the node environment don't have - if you add node-fetch to the global window then it could break other applications because of this
If it's on the web then i use something else.
Fetch polyfill that use XmlHttpRequest and are more built for the browser, others frameworks ajax function like jQuery's ajax, angulars $http and so on, or just plain old XmlHttpRequest that has support for progress event (unlike most framework)
Adding node-fetch to browser with webpack is a big overhead, you would need to bring in the stream and http modules as well when using it with webpack something that the browser don't have.
node-fetch would also need to bring more to the table if we are going to think about supporting browsers as well it would halt the development of going forward cuz we have to build browser specific hacks for IE...

@TimothyGu thanks for your feedback, it's very helpful. The comparison would be more like an Englishman in England who is learning French and inviting a bunch of Frenchmen at his house for dinner who don't speak English (the fetch userland).
For Promise, there is actually a check if it is available as a global and then it is used if so. We can't and shouldn't always expect libraries that extend or depend on fetch to provide an option for the user to point to where the fetch lib is. Besides, doing this would be a leaking configuration abstraction.
And I agree with you on how to see it, default notde-fetch usage is a CommonJS style, but for users who want an emulation closer to the native fetch API and more library compatibility having that option would be useful. This is a pragmatic approach.
@bitinn

That's precisely the problem, we don't know if a module is designed for Node or the browser, most modules will simply depend on fetch and may actually just work on Node out of the box. e.g. Frisbee. Most of the time these modules should not even be concerned about their environment, it should be the concern of the user where to run them.
I've thought about this but it seem it would be more user-friendly to provide/document this in the package. If a package on npm extend this, it will either have to follow all the releases or be a peer dependency. Either way it doesn't feel like a separate feature or an extension but more like a different loading option. It might make sense if it was an isomorphic option, but it's not.
This doesn't have much to to with isomorphicity but more about how to correctly abstract and interface fetch

@jimmywarting you're confused, this is not for the browser. As for cases where libraries depending on fetch may not work, this is a different issue and is documented there in LIMITS.

@tarikjn I am still on the no side, simply because frisbee decides to depend on a global fetch is not a reason for node-fetch to encourage a global fetch polyfill.
If you don't care about environment you are talking about isomorphism, whether you use universal javascript or other names doesn't really change this fact.
isomorphic-fetch will always export the correct fetch module into global space, even if you don't use it on client-side, it's still a good option for Node environment.

One other way to look at it is that defining on the global is a more flexible way of defining a peer dependency. It allows the user to bring-their-own-fetch. It doesn't mean an isomorphic approach, but it means there is a concern for portability, which is one of the main point of node.js.
Not only it's more flexible, I think this is the best practice for anything that want to work with fetch i.e. a library that extends fetch SHOULD assume it is on the global. If, say, it provided users with a way to pass in a reference to fetch, it would be a worse integration as it would have to be configured at every require -- unless if using some configuration injection, anyway those configuration points end up located in entry points that will not be located in the 'right' places. It's outside their concern because they are building on a standardized API, and eventual portability happens in the user environment.
You're basically trading off familiarity with the CommonJS approach of Node for a divergent API abstraction to fetch that will make it worse for integrations over time.
I do think your approach to using the underlying node APIs vs emulating XHR is very good approach thought, but that's on the 'back-end', the fetch integration is part of the implementation front-end (not referring to the browser folks!) where it should not necessarily follow the idiomatic Node approach.

Coverage remained the same at 100.0% when pulling bd8c1e7e192033531fcda98f55528d1f46540ced on tarikjn:master into e1fcc2315acd9bcb211ca6c0b1e7218093289763 on bitinn:master.

Closing this as I have updated document to point users towards isomorphic-fetch, and if they don't want side-effect, fetch-ponyfill.


Change usage of std::string to movable object

Constructor of std::string does not allow any moving. Instead, it always copies all data.
Except if pointer std::string is not used. However, that is used minorly in project.
This leads to too many unnecessary copying around data, which can be size of block (64mb).
Proposal, use custom class that will not be copying data, but moving it. Also, it will control number of owners and gets destructed when owners<=0
class Slice {
  char* ptr;
  uint64_t size;
  atomic<int> owners;
}

Other way is to use std::shared_ptrstd::string
Solving this will do some improvement to performance

Thanks for pointing out @olzhabay.
I totally get your point, however, in many sections of the code whenever expensive string assignment was done I forced the move using std::move(std::string). In such case I understood that it will move the internal data. Yet I do not know the internals of std::move. What do you think?

It does not move if std::string goes out of stack scope. Also, std::string generates too much assembly code. Examples:

std::string
slice

I have reviewed the proposed slice class which is a class that wraps basically a string (length and char array) plus some directives to allow fast concurrent access.
I also understand the rationale of the proposed idea, you find std::string inefficient for our project and slices provides a custom way for us to tweek and optimize the block content handling.
std::move in C++ strings
Still we can totally use std::move in the strings in those two scenarios:
First one
 string a = "hello", b;
 b = std::move(a);

Second one
string fun(){
  string a = "100"
  return  std::move(a); // std::move is useless, compiler will do RVO if possible
}

string b = fun();

Summary
Using slice for block abstraction instead of string will allow us:

Concurrent access to its content. YAGNI, we use one thread and proactor pattern:-1:
Tailored class to our block case (large size). Good point :+1:

Ditching std::string in favor of slices will cost us:

One more class to maintain and debug. KISS
There is so much support and optimization for std::string (inside BOOST and stdlib). Think about alignment and other things. Important

Verdict
I do not want to turn down good ideas and work. I think you have in mind a bigger refactor than slice custom class where slices class makes much more sense for that purpose. As I see it for now, it is premature optimization as we try to solve a problem that our architecture does not have (yet).
If it is part of a bigger optimization and you are thinking to change the architecture to multi-threaded, it will come super handy, I will happily accept slices along its change of architecture.
As for now I am reticent to ditch std::string
If you think I am mistaken, please point it out and lets keep the conversation. If you can't still convince me, do it by facts and benchmarks :)
signed-off<EMAIL_ADDRESS>

std::string performance
----------------------------------------------------------------------------
Benchmark                     Time           CPU Iterations UserCounters...

Did you drop the buffer cache before the benchmarks?
On Fri, Oct 12, 2018, 19:53 Olzhas Kaiyrakhmet<EMAIL_ADDRESS>wrote:

std::string performance

Benchmark                     Time           CPU Iterations UserCounters...

Reply to this email directly, view it on GitHub
https://github.com/DICL/VeloxDFS/issues/144#issuecomment-429286600, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA5XFncphW-11LhSEE32roPVETT-aXmrks5ukHSfgaJpZM4XJs1O
.

You must have a future computer to have petabytes per second throughout haha
On Fri, Oct 12, 2018, 21:35 Vicente Adolfo Bolea Sánchez <
<EMAIL_ADDRESS>wrote:

Hey the numbers are too high.
Did you drop the buffer cache before the benchmarks?
On Fri, Oct 12, 2018, 19:53 Olzhas Kaiyrakhmet<EMAIL_ADDRESS>wrote:

std::string performance

Benchmark                     Time           CPU Iterations UserCounters...

Reply to this email directly, view it on GitHub
https://github.com/DICL/VeloxDFS/issues/144#issuecomment-429286600, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA5XFncphW-11LhSEE32roPVETT-aXmrks5ukHSfgaJpZM4XJs1O
.

Update on performance benchmark results
Here are again comparison of slice and std::string
In this case we compare their performance on serialization and deserialization.
Sample benchmark code:
static void BM_serialization(benchmark::State& state) {
  char* data = new char[state.range(0)];
  srand(0);
  int ascii = (std::rand() % 255) + 1;
  memset(data, ascii, state.range(0));
  TYPE str(data, state.range(0));
  for (auto _ : state) {
    std::ofstream ofs("stream");
    {
      boost::archive::binary_oarchive oa(ofs);
      oa << str;
    }
    TYPE new_str;
    {
      std::ifstream ifs("stream");
      boost::archive::binary_iarchive ia(ifs);
      ia >> new_str;
    }
    assert(str == new_str);
  }
}
BENCHMARK(BM_serialization)->Arg(8)->Arg(64)->Arg(512)->Arg(1<<10)->Arg(8<<10)->Arg(64<<20);

Results for std::string
---------------------------------------------------------------------------------
Benchmark                          Time           CPU Iterations UserCounters...
---------------------------------------------------------------------------------
BM_serialization/8            257080 ns      96024 ns       7136
BM_serialization/64           272027 ns     102924 ns      10258
BM_serialization/512          259539 ns      90391 ns      10055
BM_serialization/1024         261867 ns     103443 ns       6890
BM_serialization/8192         312548 ns     124600 ns       6665
BM_serialization/67108864<PHONE_NUMBER> ns   92877561 ns         11

Results for slice
---------------------------------------------------------------------------------
Benchmark                          Time           CPU Iterations UserCounters...
---------------------------------------------------------------------------------
BM_serialization/8            265745 ns      94510 ns       7766
BM_serialization/64           295327 ns     107273 ns       8124
BM_serialization/512          297243 ns     106744 ns       7802
BM_serialization/1024         260830 ns      98153 ns       9907
BM_serialization/8192         260027 ns      97212 ns       9469
BM_serialization/67108864     300611 ns      87311 ns       7906

We can see significant result performance improvement on 64MB data serialization/deserialization


Improve UI and integration of Sort command with Add and Edit commands

Coverage decreased (-0.03%) to 73.646% when pulling 48b9ba5a2b621379342318d0b1d691cab3fb6aec on maggie-0.4 into 5035879b5a29c65f277bae945261280ae1785580 on v0.4.


Set up regression test workflow

Description
Regression tests should be executed after every new deployment of the events component.
The workflow should be hosted in this github repository and triggered as a part of the release pipeline in Azure DevOps.
The tests already have the option of running an extended number of tests, and this option should be used for the regression tests.
Storage and notifications already have this set up and can be used as inspiration.
Additional Information
No response
Tasks

[ ] Set up workflow for regression test AT
[ ] Set up workflow for regression test TT
[ ] Set up workflow for regression test Prod
[ ] Set up trigger of workflow from AzDO release pipeline
[ ] QA
[ ] Manual testing

Acceptance Criterias
Regression tests are executed after each new deployment

Full test set is being run for use case tests. We could consider closing the issue or triggering the use case test workflow after deploy. What do you think, @olebhansen  @SandGrainOne  ?

I think we should implement the same differentiation between use-case and regression as we have for storage and notifications. Even is the tests are the same for now.

We're more likely to rewrite parts of file-scan to accomodate the features added by "Defender for Storage".


MapView stuck in loading on Android (works fine on iOS)

Bug report
MapView component does not load on Android devices on production environment.
Testing it in debug with expo it works fine.
On iOS it works both in debug and production environment.
Environment info
react-native: https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz
react: 16.13.1
react-native-maps: 0.28.0
Reproducible sample code
<MapView
toolbarEnabled
mapType="standard"
loadingEnabled
region={{
latitude: 43.60733,
longitude: 13.49821,
latitudeDelta: 0.005,
longitudeDelta: 0.001
}}

@lillamu usually such issues means GoogleMaps is not being initialized correctly.
Please make sure that

google play services are enabled properly on the device. (sometimes you have to download them via google play)
google services and SDKs imported properly in the android project
https://developers.google.com/maps/documentation/android-sdk/start
make sure that you have a google maps API key that supports android apps and no issues with whitelisting / permissions.

I have the same issue in android standalone app (IOS works fine), is this problem resolved ?

I have the same issue in android standalone app (IOS works fine), is this problem resolved ?

Same but they're ignore it. I've seen other issue mention this, my key work fine on example in flutter app so i'm sure that my config is fine. but on this package it's always display blank map with logo

I have the same issue in android standalone app (IOS works fine), is this problem resolved ?

Check the google maps API key permissions, my problem was due to it!

i got the same error because i forgot to add SHA-1 certificate fingerprint from the playstore  (in Setup-> App Integrity -> App Signing) to google maps API.

I had the same problem following these instructions https://docs.expo.dev/versions/latest/sdk/map-view/#deploy-app-with-google-maps . Turns out I needed to add the SHA-1 certificate fingerprint from Google Play console instead of expo.

If anyone is still having this issue, add the following configuration in Google Api Key (Android restrictions section):
Package name      | Fingerprint
{your_package_name} {App signing key certificate => SHA-1 certificate fingerprint}
{your_package_name} {Upload key certificate => SHA-1 certificate fingerprint}


Question: the struggle is real

Hi Guys,
this is more of a question i have. I got started and tried the one example to display the users.
That worked fine. However, after that i tried to find a notion page by it's id.
So my first question, where to find that page_id ? I thought about it's the hash value on the link
of the notion page (however, in the example it includes - and in the hash not.
After that, i just wanted to list all pages that are available, how to do that?
I could not find anything like notion.pages.list() .
Last but not least, and more of a general understanding question what are blocks?
How to see what blocks are saved?
Sorry if this questions are to simple for you, peeps.
Cheers
Chris

So my first question, where to find that page_id ?

Read this https://github.com/ramnes/notion-sdk-py/discussions/31

what are blocks?

From Notion HQ: “A block is any single piece of content you add to your page, like a to-do item, an image, a code block, an embedded file, etc. Think of your page as being made up of these building blocks.”


Adding implementations for SuspendProcesses and ResumeProcesses

Adding implementations for AutoScaling SuspendProcesses and ResumeProcesses

Ran into some problems with the AZRebalance colliding with some custom loadbalancing, so used the opportunity to implement the API functions.

Thanks for the contribution.


Cache Data fails to generate for Ubuntu 22.04

It seems there is a bug in the system , while trying to setup the code on newer systems like Ubuntu 22.04 where when attempting to setup discovery tool (instructions here) it seems that the cached_data.json fails to assemble leading for the tool to not have anything to search for when testing the project locally. @pleia2 any thoughts  ?

Yes, @arshPratap. When I tried to run it locally I was facing the same issue where cached_data.json is not generating on Ubuntu 22.04.

@pleia2 thanks for this..I just checked it and I realized the main issue is with IBMZ-container-registry.json file name incorrectly listed in the supported distros. As far as i remember, we had a PR #99 that included changing its name  and the same change needs to be reflected in the data repository.
If possible let me add a quick PR there.

@pleia2 oh I think we need to update our git submodule for distro_data currently its pointing towards the commits made for the may-branch

@pleia2 @Princee215 I have added another PR with a slight update in the instructions for correctly initialising the git submodules.

Thanks @arshPratap I tried and checked, and it is working well now.

@Princee215 thanks for the update ! Closing the issue


Team 15 Hazard Analysis Review: Some fit criteria could be more rigorous

Some of the fit criteria for requirements such as PR1, PR14 and HS2, do not seem sufficient enough.
For PR1 and PR14, consider testing these requirements by ensuring that a certain percentage (ex. 95%) of user interactions and annotations meet this requirement, as it may be hard or unrealistic to expect 100% of interactions to be near-instantaneous or have less than the max delay at all times.
For HS2, consider testing this requirement by using a user survey or rating to understand if your users are comfortable using the system.
TA: @Lyuyang0130

resolved in: 68fbfae53dbfda0980220b49e69f32be92e37994


Possible basic approach for mult-table searching

This isn't necessarily what we'll do, but I thought I'd get it checked in in case something from this approach winds up being useful.

Is this possibly missing the controller file?

I didn't add a controller portion because I wasn't sure what we want the API to look like

Ah, okay, makes sense.  Thought it was already query-able.


Add Boot

Codecov Report

Merging #110 (487745d) into master (b437990) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #110   +/-   ##
========================================
  Coverage      1.21%   1.21%
  Complexity        4       4
========================================
  Files            14      14
  Lines           577     577
  Branches         46      46
========================================
  Hits              7       7
  Misses          569     569
  Partials          1       1

Continue to review full report at Codecov.

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


Populate state column of rule_type table.

Summary
This change sets status to alpha for existing rule types.
Fixes #4243
Change Type

[ ] Bug fix (resolves an issue without affecting existing features)
[X] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Manual testing.
Review Checklist:

[X] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

Are states anything that would be acted on? Why not have a labeling system or annotations instead?


chore: remove CODEOWNERS

Codeowners are a great idea, but it emails every owner on every PR to review it.  It also means every comment on every PR also sends an email.  This is insane and I can't see emails where I'm actually mentioned and need to pay attention.
I've already disabled required codeowner approval, but this did not stop the emails.  All owners are still pinged and emailed, even though they are not required.  PRs still require a review, just not from codeowners.  I think we can be big boys and girls and do the right thing without the enforced list of "approved" approvers.

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS

We still need to lock down to the core team here...


emoji not found

the Crossed Swords is not coming up on search. Can you please add it?

Not sure if you still remember what you wanted to use them for but now you can! :crossed_swords:


[Bug]  admin user cannot load all tables below the db

Search before asking

[X] I searched the issues and found no similar issues.

Linkis Component
linkis-orchestrator
What happened + What you expected to happen
When I set up the admin user and use it to log in to dss, it should load all the tables under a certain library, but only the tables it owns can be loaded
Relevent platform
linkis1.1.3
Reproduction script
wds.linkis.metadata.hive.db.admin=hadoop
Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

I want to fix this issues，you can assign it to me


Natural language FPs with rule 932236 PL2

This issue is part of the ongoing quantitative testing natural language FPs improvement task. See the main issue for details: #3392
Description
Rule 932236 struggles with false positives on natural language input. This is because there are many English-language words in the regexp-assemble files for this rule, e.g. "history", "composer", "local", etc.
Rule 932236 is one of the new/overhauled Unix command detection rules in v4.0:
Remote Command Execution: Unix Command Injection (command without evasion)
...
#  .932236 (stricter sibling of 932230, 932235, 932250, 932260, PL2,
#       - with and without prefix
#       - words of any length)

Logs
The biggest offenders by far were "As " followed by "At ".
Here is a summary of the relevant matched payloads I could find:
[data "Matched Data:  Links  found within ARGS_NAMES: Links family-friendly community event from 1-4 p.m. when your library will be transformed into a miniature golf and bowling center for one day only.:  Links family-friendly community event from 1-4 p.m. when your library will be transformed into a miniature golf and bowling center for one day only."]
[data "Matched Data: Arch  found within ARGS:payload: Arch Capital is Watford\\xe2\\x80\\x99s largest shareholder with a 12.6% stake, according to Refinitiv Eikon data."]
[data "Matched Data: As  found within ARGS:payload: As you near your last year of trick or treating, though, sometimes jokes aren\\xe2\\x80\\x99t enough."]
[data "Matched Data: At  found within ARGS:payload: At any moment we can make a decision to change."]
[data "Matched Data: Composer  found within ARGS:payload: Composer Chris Ruenes livens things up, too, with a percussion-heavy score that is playful and offbeat."]
[data "Matched Data: Curl  found within ARGS:payload: Curl up with a good book and snuggly blanket."]
[data "Matched Data: Cut  found within ARGS:payload: Cut orange quarters into crosswise slices about 1/8-inch thick."]
[data "Matched Data: Dash  found within ARGS:payload: Dash (DASH) traded 0.2% higher against the dollar and now trades at $69.27 or 0.00757243 BTC."]
[data "Matched Data: Dialog  found within ARGS:payload: Dialog Semiconductor Plc develops and distributes highly integrated, mixed signal integrated circuits (ICs) for personal, portable, hand-held devices, low energy short-range wireless, LED solid-state lighting, and automotive applications worldwide."]
[data "Matched Data: Expect  found within ARGS:payload: Expect mobile, alternating lane closures Monday through Friday from 7 a.m. to 7 p.m."]
[data "Matched Data: Find  found within ARGS:payload: Find new news sources!\\xe2\\x80\\x9d"]
[data "Matched Data: Get  found within ARGS:payload: Get on course with the rest of the world and set an example of what to do, instead of what not to do."]
[data "Matched Data: Go  found within ARGS:payload: Go early, go hard, go Jacinda."]
[data "Matched Data: Head  found within ARGS:payload: Head of Xbox Phil Spencer was playing the Xbox Series X in 2019, long before it was available to the public."]
[data "Matched Data: History  found within ARGS:payload: History tells us people in the regions, mostly in northern Namibia always enjoyed reading in their local languages."]
[data "Matched Data: Id found within ARGS:payload: Identity politics is the politics of narcissism and ingratitude."]
[data "Matched Data: Id found within ARGS:payload: Idlib province and its surroundings have been a dead end for many people previously displaced by Russian-backed regime operations against former rebel strongholds across the country."]
[data "Matched Data: Last  found within ARGS:payload: Last year, the use of plain Japanese spread to other local governments, including Tokyo, and the Immigration Services Agency decided to create a guideline for using the simpler language form."]
[data "Matched Data: Local  found within ARGS:payload: Local fishing is beneath their concern."]
[data "Matched Data: Look  found within ARGS:payload: Look at you now!"]
[data "Matched Data: Make  found within ARGS:payload: Make contingency plans."]
[data "Matched Data: Mount  found within ARGS:payload: Mount Airy basketball coach Bryan Hayes lectures his team during a third-quarter timeout in the 2018 Frank Spencer Tournament."]
[data "Matched Data: Net  found within ARGS:payload: Net cash outflows last year were $3.968 billion."]
[data "Matched Data: RED  found within ARGS:payload: RED WING \\xe2\\x80\\x94 A former church bookkeeper pleaded guilty Monday to stealing more than $33,000 over three years."]
[data "Matched Data: Self  found within ARGS:payload: Self was second on the team in kills with 11 along with a block and three digs."]
[data "Matched Data: Shadow  found within ARGS:payload: Shadow Treasurer Jim Chalmers has called on the government to release its JobKeeper review."]
[data "Matched Data: Snap  found within ARGS:payload: Snap also said it would stop promoting Mr. Trump\\xe2\\x80\\x99s Snapchat account after determining that his public comments off the site could incite violence."]
[data "Matched Data: Top found within ARGS:payload: Top administration officials, under growing pressure to act, are dismissing the need for immediate, broad-based measures to shore up the economy but have begun suggesting that a smaller-scale response might be necessary."]
[data "Matched Data: Wall  found within ARGS:payload: Wall Street\\xe2\\x80\\x99s benchmark stock index struck an all-time high on Tuesday, having rallied more than 50 per cent from the darkest days of the coronavirus crisis, despite persistent investor unease about the US economy."]
[data "Matched Data: time as  found within ARGS:payload: Abela had attempted to justify the move as necessary at the time as a way of controlling coronavirus infections in the country."]
[data "Matched Data: time as  found within ARGS:payload: We settled into domestic life quite well, both using the downtime as a reset button on our lives."]
[data "Matched Data: time at  found within ARGS:payload: Arshad, 51, said during his time at home, he is working on a few scripts which he intends to direct someday."]
[data "Matched Data: time last  found within ARGS:payload: \\xe2\\x80\\x9cAround this time last year, I called up asking for a bit of information, and they just said they can't release any information,\\xe2\\x80\\x9d he said."]

How to reproduce the misbehavior (-> curl call)
curl https://sandbox.coreruleset.org -H 'x-format-output: txt-matched-rules' -H 'x-crs-paranoia-level: 2' --data "payload=Expect mobile, alternating lane closures Monday through Friday from 7 a.m. to 7 p.m."

Your Environment

CRS version (e.g., v3.3.4): v4.0.0-rc2
Paranoia level setting (e.g. PL1) : PL 2
Operating System and version: CRS modsec2-apache container

Confirmation
[x] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.

I tested the reported false positives:

payload=Expect mobile -> match
payload=You expect mobile -> no match
payload=Wall street -> match
payload=The Wall street" -> no match

The problem with most of the false positives is the start of the string ^ evasion prefix. By removing this ^,  29 out of the 33 (87%) of the false positives reported above would be gone.
I think, because this start of the string prefix causes so many false positives, we should consider removing it. And I think this is less dangerous than removing the ;  for example, that is used to concatenate commands.
Then we have a second problem that causes the rest (4 out of 33) of the false positives reported above: the time prefix. Unfortunately this prefix is a common English word and in rare cases two combined English words trigger a false positive, like time at, time as or time last.
3 out of the 4 false positives were caused by a as or at. By adding the two "biggest offenders" as and at, maybe also last, to the exclude file unix-shell-fps-pl2.ra, we could solve most of the false positives.
I could open a PR solving the problems, but I would like to hear other opinions and if this is still safe or if this causes too many bypasses?

https://github.com/coreruleset/coreruleset/blob/v4.0/dev/regex-assembly/include/unix-shell-evasion-prefix-start-of-string.ra#L7 says it's used by 932250 and 932260. Apparently also by more or less unrelated 932236.
It's a lot of false positives, but it's also a PL2 rule.
How useful is the ^ at all? I mean it's relatively easy to add something in front of the command to bypass this, is not it? I know we are catching some of these evasion methods, but other ones go indetected and execute just fine (e.g. \ifconfig).
So I think we could remove that but I would prefer to keep the time since this is PL2 and I do not expect many users aiming for a level above.
Just my 2 cents.

Yes, I've seen this wrong comment and I would fix this too.
Thanks for your opinion about the ^.
I wouldn't remove the time prefix, but I would add as and at to the exclusion file for pl2.

Yes, but still. If we solve 80% of the problem with the ^ prefix, then I think we can leave it at that for 4.0.0 and gain more experience before we rush into the 2nd step.

Ok, now I see. I thougt I was not clear enough.

I had a look at this issue again and tested how many of the tests will fail if we remove the start of the string ^ evasion prefix. Then the tests 14, 15, 16, 17, 40, 41, 50, 51 are failing. Some of them are BB tests. That's bad I think.
Then I tested what happens if I add the words above to the already existing exclusion file at pl2. And I think this is the way to go. I even think we can add the words starting with a upper case letter -> then no tests will fail. And in natural language the start of a sentence is always an upper case letter. Unix is case sensitive, so we would be safe I think. I'll open a PR, then we can discuss this approach.

Honestly, I think we should merge unix-shell-evasion-prefix.ra and unix-shell-evasion-prefix-start-of-string.ra. The former has received some updates that are missing in the latter, the latter has the additional ^ and = matches. I had never analysed the prefixes when I deconstructed them, I had just made sure that we keep them as they were originally written. Looking at them now, I don't see any advantage in having both.
Additionally, the way that time is bing used in the ...start-of-string.ra file is wrong, IMO. It should be identical to ...evasion-prefix.ra (prefix instead of alterneration).
In conclusion:

add = to ...evasion-prefix.ra
remove ...start-of-string.ra

Re: @franbuehler : I think the uppercase thought is great. Never thought about this in relation to FPs!

Upper case won't work. File system case sensitivity is the choice of the user. I always use case-insensitive.

I have never heard anyone doing that. Is it a widespread practice?
I'd probably opt to ignore what seems to be an exotic setting and still make use of case sensitivity for regexes (apparently not for PM) when it helps us fight FPs, namely in PL1 and PL2.
But I am open to hear different opinions on the subject. Maybe I am just not up to date how people run their servers.

I've been running macOS case-insensitive for years. Whether it's wide spread, particularly on servers, I don't know. Probably not, but we just don't know.

The POSIX specification actually allows for case insensitivity, but I think on Linux these filesystems are very uncommon (although ext4 seems to support it) and it is not worth suffering false positives by triggering on it.

I've found a bit of information on the subject:
https://www.collabora.com/news-and-blog/blog/2020/08/27/using-the-linux-kernel-case-insensitive-feature-in-ext4/
It seems to be a fairly new addition to ext4 and other filesystems and it is namely used for Windows (Mac if your will) compatibility.
I'd still say we ignore this use case for lower PLs in favor of fighting false positives effectively.

As I wrote above, I believe the regular expression is wrong. IMO, the discussion around case sensitivity is moot as long as that's the case.

Cross-posting from the PR:
After running the quantitative testing script against this branch (using the same 10k sample set used elsewhere), the changes in this PR take the false positive rate for rule 932236 from:
268 -> 28

I've analysed the contents of the prefixes and rule 932236. I still believe that we should merge the prefixes but it's probably better to do that another time. For now we should:

add = to ...evasion-prefix.ra
align the "prefix commands" (e.g., time) in both files

As for the FPs, I now believe that @franbuehler is right and we should exclude as, at, etc.. However, we should not add them to unix-shell-fps-pl2.ra, as that file is used by multiple rules. Instead, we should add them to a new exclusion file.
I also wouldn't want to remove the ^ match, for the reason @franbuehler has given.
I will update @franbuehler's PR.

Thanks for taking this over and looking into it while @franbuehler is on holiday.

This is on the cusp of being solved, IMO. Just need to sort out the tests in the PR.


Add Dry::Struct::VERSION to gemspec

Currently this is waiting on https://github.com/dry-rb/dry-configurable/issues/7 being resolved. Once I can inline the version I can also drop the version_spec I added in #3.

Resolved in https://github.com/dry-rb/dry-configurable/commit/dfb68af455a3e962d6f6883b2b35a2dd4c8c6485#comments


Add Windows signatures for 515.1616

get_misc_by_id had to be reworked from scratch so it might be unstable now. variable_names and the other var sigs are also probably unstable.
Tested on 515.1616, most likely compatible with 1515 but I don't expect anyone to use that.

Would this allow for the VSC debugger to start working again on 515?

VSC Debugger still works on 515.1609 older versions can be downloaded here. This would allow it to work on 515.1620 now.


fake BLE beacon implementation

This PR is meant to update my lit-beta branch with the fake_ble.py module I got working (send advertisements only) includes 1 example and changes to docs.

I'm making an executive decision in the way of forwards progress. Receiving BLE beacon advertisements may be possible via end-user because the FakeBLE.whiten(), crc24_ble(), and reverse_bits() are publicly exposed in the fake_ble.py module. However, this has not tested... yet. For reference, one can look to the source code in the Arduino library named "BTLE" (available in the Arduino library manager also) that uses the TMRh20 Arduino library as a dependency.