Error in Colcon build —symlink-install

i am getting this error when doing colcon build —symlink-install in ~/ASRL/vtr3/main
Please help
colcon build --symlink-install
Starting >>> lgmath
Starting >>> vtr_messages
Starting >>> vtr_logging
Starting >>> cudpp
Starting >>> vtr_documentation
Starting >>> vtr_ui
/home/rishabh/.local/lib/python3.8/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'script-dir' will not be supported in future versions. Please use the underscore name 'script_dir' instead
warnings.warn(
/home/rishabh/.local/lib/python3.8/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'install-scripts' will not be supported in future versions. Please use the underscore name 'install_scripts' instead
warnings.warn(
Finished <<< cudpp [1.40s]
Starting >>> gpusurf
Finished <<< vtr_logging [1.46s]
Finished <<< lgmath [1.58s]
Starting >>> steam
Finished <<< gpusurf [0.45s]
Finished <<< steam [1.00s]
Starting >>> vtr_steam_extensions
Finished <<< vtr_steam_extensions [0.34s]
--- stderr: vtr_ui
/home/rishabh/.local/lib/python3.8/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'script-dir' will not be supported in future versions. Please use the underscore name 'script_dir' instead
warnings.warn(
/home/rishabh/.local/lib/python3.8/site-packages/setuptools/dist.py:772: UserWarning: Usage of dash-separated 'install-scripts' will not be supported in future versions. Please use the underscore name 'install_scripts' instead
warnings.warn(
/home/rishabh/.local/lib/python3.8/site-packages/setuptools/command/easy_install.py:144: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
/home/rishabh/.local/lib/python3.8/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
warnings.warn(
/home/rishabh/.local/lib/python3.8/site-packages/pkg_resources/init.py:123: PkgResourcesDeprecationWarning: 1.13.1-unknown is an invalid version and will not be supported in a future release
warnings.warn(
/home/rishabh/.local/lib/python3.8/site-packages/pkg_resources/init.py:123: PkgResourcesDeprecationWarning: 0.1.36ubuntu1 is an invalid version and will not be supported in a future release
warnings.warn(
/home/rishabh/.local/lib/python3.8/site-packages/pkg_resources/init.py:123: PkgResourcesDeprecationWarning: 0.23ubuntu1 is an invalid version and will not be supported in a future release
warnings.warn(
Finished <<< vtr_ui [5.90s]
Finished <<< vtr_messages [6.68s]
Starting >>> vtr_common
Starting >>> vtr_storage
Starting >>> vtr_lgmath_extensions
Finished <<< vtr_lgmath_extensions [0.30s]
Finished <<< vtr_common [0.39s]
Starting >>> vtr_safety_monitor
Finished <<< vtr_storage [0.73s]
Starting >>> vtr_pose_graph
Finished <<< vtr_safety_monitor [0.49s]
Finished <<< vtr_pose_graph [0.97s]
Starting >>> vtr_path_planning
Starting >>> vtr_path_tracker
Finished <<< vtr_path_planning [0.40s]
Starting >>> vtr_mission_planning
Finished <<< vtr_path_tracker [0.56s]
Finished <<< vtr_documentation [9.40s]
Finished <<< vtr_mission_planning [0.72s]
Starting >>> vtr_tactic
Finished <<< vtr_tactic [0.47s]
Starting >>> vtr_lidar
Starting >>> vtr_vision
Finished <<< vtr_lidar [0.71s]
--- stderr: vtr_vision
/home/rishabh/ASRL/vtr3/main/src/vtr_vision/src/modules/matching/mel_matcher_module.cpp: In member function ‘void vtr::vision::MelMatcherModule::matchChannelGPU(vtr::vision::CameraQueryCache&, const vtr::vision::LandmarkId&, const ChannelLandmarks&)’:
/home/rishabh/ASRL/vtr3/main/src/vtr_vision/src/modules/matching/mel_matcher_module.cpp:362:37: error: ‘const struct vtr::vision::Features’ has no member named ‘gpu_descriptors’; did you mean ‘descriptors’?
362 |     if (query_channel_lm.appearance.gpu_descriptors.empty()) {
|                                     ^~~~~~~~~~~~~~~
|                                     descriptors
/home/rishabh/ASRL/vtr3/main/src/vtr_vision/src/modules/matching/mel_matcher_module.cpp:367:47: error: ‘const struct vtr::vision::Features’ has no member named ‘gpu_descriptors’; did you mean ‘descriptors’?
367 |       qry_descs = query_channel_lm.appearance.gpu_descriptors;
|                                               ^~~~~~~~~~~~~~~
|                                               descriptors
make[2]: *** [CMakeFiles/vtr_vision.dir/build.make:323: CMakeFiles/vtr_vision.dir/src/modules/matching/mel_matcher_module.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:337: CMakeFiles/vtr_vision.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
Failed   <<< vtr_vision [14.5s, exited with code 2]
Summary: 19 packages finished [24.9s]
1 package failed: vtr_vision
2 packages had stderr output: vtr_ui vtr_vision
1 package not processed

Hi Rishabh,
I am not sure what's causing the error.
could you share 1) hardware info (cpu, gpu) and 2) software versions - operating system, cuda, opencv, ros2


Setting QueryParams on Entries.List(space)

Setting the QueryParams on Entries.List(space) seems to crash the application. It also looks like it's not passing on the query parameters in the request. Is this planned on being supported?

Never mind. I'm dumb.


fix(config): cleanup absolute path config function

refs https://github.com/TryGhost/Ghost-CLI/issues/228

don't try to reinvent path.isAbsolute

@kirrg001 the reason we didn't run into this before on Windows is when you download Ghost for development, it ends up using the relative path, so this function worked as intended. Ghost-CLI can't use the relative path, so it ran into this issue.


Inflight Deprecation Warning

Describe the bug
On Installing dependencies after npm create svelte@latest I got npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. Not sure if it is serious or not, saw leaks memory in it thus opened this issue.
Reproduction
By Installing dependencies after npm create svelte@latest.
Logs
No response
System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1235U
    Memory: 4.47 GB / 15.73 GB
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.7.0 - C:\Program Files\nodejs\npm.CMD
  Browsers: {}
  npmPackages:
    @sveltejs/adapter-auto: latest => 3.2.1
    @sveltejs/kit: latest => 2.5.10
    @sveltejs/vite-plugin-svelte: latest => 3.1.0
    svelte: latest => 4.2.17
    vite: latest => 5.2.11

Severity
annoyance
Additional Information
No response

We should move this issue to svelte-preprocess https://github.com/sveltejs/svelte-preprocess
❯ npm why inflight
<EMAIL_ADDRESS>dev
node_modules/inflight
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>  node_modules/glob
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>    node_modules/rimraf
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>      node_modules/sander
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>        node_modules/sorcery
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>          node_modules/svelte-preprocess
<EMAIL_ADDRESS>from<EMAIL_ADDRESS>            node_modules/svelte-check
              dev<EMAIL_ADDRESS>from the root project

Wouldn't the fix be to bump dependencies in https://github.com/rich-harris/sander, not svelte-preprocess? Or, perhaps, to just start using built-in filesystem APIs instead in https://github.com/Rich-Harris/sorcery?

hello when i do the command to install nodered i have this error ,npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
what i can do?thank you

I'm getting this error while trying to install Appium, any idea how it can be resolved?
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.

I'm getting this error while trying to install Appium, any idea how it can be resolved?
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported. npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported. npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.

The author of inflight deprecated the package on Mar 22. https://github.com/isaacs/inflight-DEPRECATED-DO-NOT-USE/issues/5#issuecomment-2126153820

@ananduremanan what should we do with the warnings that appear to us?

@ananduremanan what should we do with the warnings that appear to us?

If the package actually cause memory leak, then that would be a serious problem. The best we could do is find the package that uses inflight and replace it with ‘lru-cache’ as the author of inflight suggests and open a pull request or just wait for some cool people on open source community to fix it.

is this issue on windows devices only or with mac users too?

is this issue on windows devices only or with mac users too?

I don't think so. When a package is deprecated it affects all users of that package, regardless of their operating system.

I am also having this problem when upgrading Capacitor from v.5 to v.6. I am a mac user.

You can run npm why inflight or pnpm why inflight to figure out which package is depending on the deprecated package. In svelte-check’s case we will probably fix it by removing the dependency on inflight; replacing it with native APIs or a different package.

I have a problem when creating a project with Vite using the command npm create vite@latest. I go through all the configuration steps, but when I run the command npm install, I get warnings. This started happening after I followed a tutorial that used ESLint with the command npx eslint --init. After running that command, the warnings started appearing. Would you like me to run any command so you can see what might be going wrong?

I am also trying to install Appium and have gotten the same error message about inflight and a few other things. When I run npm why inflight terminal says  ' no dependencies found matching inflight'
I am a bit lost as to what to do next? Do we just wait for a fix? I am fairly new to this and totally new to automated testing

I am also trying to install Appium and have gotten the same error message about inflight and a few other things. When I run npm why inflight terminal says ' no dependencies found matching inflight'
I am a bit lost as to what to do next? Do we just wait for a fix? I am fairly new to this and totally new to automated testing

I'm using a completely different project that depends on inflight as a sub-dependency, but I saw your post from a Google search and thought I'd pass along some information. I don't know anything about this project, but if it creates a package-lock.json after installation, you may be able to look in there to see what dependencies rely on it, and backtrack it to the parent one from there. That should give you your answer on which dependency is at fault.

Hey guys!
I'm working on an web app rn and thus installed bun in VSCode.
The installation was successfully but I am still concerned about those lines...
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
I am a newbie in the coding space.
Any steps to solve this problem?
Thank you!
ChiefCook

I think Updating glob in https://github.com/Rich-Harris/sander and https://github.com/Rich-Harris/sorcery may fix issues related to SvelteKit. Both of these packages use a lot of deprecated packages and haven't been updated for years.

This is caused by eslint@8 transient dependencies being deprecated, see report https://github.com/eslint/eslint/issues/18528

I'm getting this error while trying to install Appium, any idea how it can be resolved?
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported. npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported. npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.

The author of inflight deprecated the package on Mar 22. isaacs/inflight-DEPRECATED-DO-NOT-USE#5 (comment)
This is common with JavaScript since anyone can came up with a package and when it got deprecated we get a bunch of errors or warnings.

just downgrade the node into 18 may things works because ill do it in next js it works in 20 version but not in 22

Temporary solution: add file-entry-cache override to package.json, delete package-lock.json and npm install
  "overrides": {
    "eslint": {
      "file-entry-cache": "^8.0.0"
    }
  }

In Select additional options mark the option Add ESLint for code linting

svelte-check should remove its dependency on svelte-preprocess: https://github.com/sveltejs/language-tools/issues/2391. That would fix this issue for the majority of SvelteKit users and reduce the number of dependencies, which is always good. We should still fix svelte-preprocess for the users who are using it directly

We should also probably remove sorcery from svelte-preprocess: https://github.com/sveltejs/svelte-preprocess/issues/637

is this issue on windows devices only or with mac users too?

with mac os too
I got this error when installing whatsapp-wep.js package
npm WARN deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm WARN deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
npm WARN deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm WARN deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
npm WARN deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm WARN deprecated<EMAIL_ADDRESS>< 22.6.4 is no longer supported

All dependencies have now been removed from svelte-preprocess: https://x.com/BenjaminMcCann/status/1810698991820321028
Now we'll need to either update svelte-check to use this new version (https://github.com/sveltejs/language-tools/pull/2401) or see if the dependency on it can be removed (https://github.com/sveltejs/language-tools/issues/2391).

Hello I have the same error I am new to this so I have no idea what should I do, do you guys have a solution or just wait for an update or something?

Hello I have the same error I am new to this so I have no idea what should I do, do you guys have a solution or just wait for an update or something?

Hi jexc. Yes, see https://github.com/sveltejs/kit/issues/12258#issuecomment-2218052620 . We’ll have to wait to  a bit before updating to get rid of this warning

hello i getting this warning listed below while cloning Nest-js project , please help me with to get rid of this warning
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
npm warn deprecated<EMAIL_ADDRESS>Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net

Hello, I am getting an npm deprecated warning in my NestJS project. Please help me get rid of this warning
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead
npm warn deprecated<EMAIL_ADDRESS>Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net

Add this to package.json, remove node_modules and package-lock.json, then execute npm install
  "overrides": {
    "eslint": {
      "@humanwhocodes/config-array": "npm:@eslint/config-array",
      "file-entry-cache": "^8.0.0"
    }
  }

some warning gone but some is still there
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Please upgrade to v9.0.0+ as we have fixed a public vulnerability with formidable dependency. Note that v9.0.0+ requires Node.js v14.18.0+. See https://github.com/ladjs/superagent/pull/1800 for insight. This project is supported and maintained by the team at Forward Email @ https://forwardemail.net

You either did not do exactly what I suggested: Add to package.json, remove node_modules and package-lock.json, then execute npm install
or there is another package that is dependent on eslint and you would need to also add that to overrides.

@lorand-horvath
Yes, I did it and it works fine, but I have a doubt- is using overrides in package.json safe? I mean, will it not create problems in the future?

You should not have to set overrides for eslint. Upgrade to eslint 9 instead. You can create a new SvelteKit project if you want to see an example of what it looks like to use eslint 9

@benmccann upgrading to eslint 9 causes npm error
<EMAIL_ADDRESS>invalid: "^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0" from node_modules/eslint-plugin-react-hooks

I wouldn't think you need eslint-plugin-react-hooks in a Svelte project. If you do, then you'll need to upgrade to the latest version and if the latest still doesn't support eslint 9 then that will need to be fixed in that plugin

I’m getting a warning in my NestJS project. If I use override, there’s no warning. Are there any other options to remove the warning without using override?
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/config-array instead
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use @eslint/object-schema instead

can someone please help me with this? im trying to create a new project and this happens everytime:

npm install
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported.
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native atob() and btoa() methods instead
npm warn deprecated<EMAIL_ADDRESS>This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm warn deprecated<EMAIL_ADDRESS>Use your platform's native DOMException instead

added 1552 packages, and audited 1553 packages in 2m
146 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
✅ Your project is ready!

We have started working on a new major version of svelte-check to fix this issue. The new version will drop these dependencies and many others. It will be probably a few weeks until it's ready due to vacation schedules and other commitments, but I'm excited about the improvements.

I have created the new project with Angular 17 version. When i do npm install getting below warning.
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>This package is no longer supported. Please use @npmcli/package-json instead.
npm warn deprecated<EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated<EMAIL_ADDRESS>Rimraf versions prior to v4 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
Can someone please help me with this?

it looks like this issue comes up high when searching for the warning. Please refrain from posting help requests or adding "me too" comments

fwiw i tried both 'override' workarounds (including removing node_modules, package-lock.json and re-running npm install each time) and neither affected the inflight memory leak error at all.
i also find it strange that this has been happening FOR MONTHS in the default- "everybody should create a new project this way" method, and this is generating errors and memory leaks.   isn't svelte more polished that it has something that can be expected to work out of the box?  seems weird to be editing package.json for new project built from a template.  i appreciate the hard work and svelte does seem pretty interesting, but it's frustrating when the most basic things w/a new project need immediate maintenance... esp for a framework that's supposed to be EASIER.

https://github.com/sveltejs/language-tools/releases/tag/svelte-check-4.0.0 just released a few days ago and removes the dependency on the old version of svelte-preprocess that depends on inflight.

Yeah, I merged the fix on Monday, but hadn't cut a release yet. I just did that now, so new projects should no longer generate these warnings.
If you encounter this, please upgrade your project to svelte-check 4. If you have svelte-preprocess in your project make sure it's on version 6 or usually the better solution is to replace it with vitePreprocess: https://kit.svelte.dev/docs/integrations#vitepreprocess
This was difficult to fix because we had to fix so many different dependencies and cut major releases of multiple packages.
We've really reduced the number of dependencies by a lot during this process so that we're much less likely to hit these types of issues in the future. Compare https://npmgraph.js.org/?q=svelte-check@4 vs https://npmgraph.js.org/?q=svelte-check@3. There are plans to remove a majority of the remaining dependencies by upgrading to the upcoming chokidar v4 when it is released.

I am getting the following warning in my NestJS backend project. Even after updating all the packages, I am still encountering this warning. Is there anyone who can help me get rid of it?
PS F:\Test_project\rescueworld-microservice-retteracademy> npm i
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported

it looks like this issue comes up high when searching for the warning. Please refrain from posting help requests or adding "me too" comments

Upgrading the eslint version resolves the issue. If someone else is still esperiencing the issue.
Run:
npm i eslint@latest -D
After that remove node_modules and package-lock.json and rerun:
npm install
The warnings disappeared for me.

i have same error when i install "npm install whatsapp-web.js", how to solved the issue? please if you know about the problem please help me

@ananduremanan what should we do with the warnings that appear to us?

If the package actually causes a memory leak, it would be a serious problem. The best we can do is find the package that uses inflight (as @eltigerchino mentioned in his comment), replace it with lru-cache as the author of inflight suggests, and open a pull request. Alternatively, we could wait for some cool guy from the open-source community(like @Conduitry above) to fix it.

I'm getting the suggestion to use "lru-cache" (here's the whole message: "npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.")


Update Emergent Architecture

Updated the hardware software mapping with recent architectural changes.

Nice work

Looks good, just had to fix my name. (How did I miss that?)

Nice!


DR fixes for java sdk

This PR contains miscellaneous fixes for disaster recovery.

Force refresh database account on write forbidden exception
Force refresh when read request failed due to endpoint unavailable if none of preferred region mentioned in connection policy is available
If we hit scenario like region gone or write forbidden exception twice then code was not doing cache refresh, means it will only handle one disaster recovery .
One bug is still open where we are not doing background location refresh if account is multi-master or user doesn't provided useMultipleWriteLocations = true, need to discuss.

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - ci

/azp run java - cosmos - tests

/azp run java - cosmos - tests

@moderakh thoughts on UT?

@kirankumarkolli for new customers we need to always validate the multi region fail over scenario.
I thought about how we can automate this before to save us time.
My thought for automated testing
We can have a test which uses java azure management sdk to add/remove region (the scenario above), and during that time we can validate that some basic tests work during fail over.
This should be automatable and will save us time. If we decide to add this automated test, I would estimate half a week work for the test setup.

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests

/azp run java - cosmos - tests


Implement fix Eth indexer skipping blocks with multiple dataSources

https://github.com/subquery/subql/issues/2335
Follow for fix here: https://github.com/subquery/subql/pull/2331

https://github.com/subquery/subql/pull/2331

Fixed by subql team


Something missing

[Enter feedback here]
I think there is something missing after
because I do not see any changes to the database.php file. Any help?
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 0ac69cc1-da55-0221-3068-68c32247cf07
Version Independent ID: f990d756-a826-dbdd-29b6-3f7663521595
Content: Tutorial: PHP app with MySQL - Azure App Service
Content Source: articles/app-service/tutorial-php-mysql-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@purvez
Thanks for your feedback! We will investigate and update as appropriate.

Hi @purvez, the third instruction under 3 - Deploy Sample Code is where you would have changed the database.php with the properties of the MySQL instance you created in the prior steps.

In Visual Studio Code in the browser, open config/database.php in the explorer.In the mysql connection, see that the app settings you created earlier for the MySQL connection are already used (DB_HOST, DB_DATABASE, DB_USERNAME, DB_PASSWORD, MYSQL_ATTR_SSL_CA)

Let me know if you need any further help.

I am sorry, I thought those values were automatically used from the application settings that I have set on the web app. I didn’t know that I have to manually change those values.

I would like to ask when do I not have to change it. Because I would like to make these changes in only one place, and I thought it was from the app settings.

You can certainly do that. Application settings are loaded as environment variables on the host and you can access them likewise using getenv("DB_HOST")

@RyanHill-MSFT, I would like to confirm that the wording is a little confusing.  In step 3, you are asking to "confirm you see the values" in the database.php.  You are not asking to make any changes.  The file is already setup to draw from the environment variables.  There is no changes required, and specifically none regarding the certificate in which you are asking to tag the commit with.


[zh-cn]Sync patch-releases.md

release: move markdown tables to shortcode
fllow #36609

Hey @yanrongshi,
It's been a while since the last update, would you like to address issues in the previous comments so that we can move forward?

@yanrongshi Still working on this?


Allow automated archival with 301works.org

Trying to figure this out. Below, an email from Jeff Kaplan of 301works.org:

Hi,
Thanks for contacting Internet Archive regarding 301works.org. There is additional information at http://www.archive.org/details/301works-faq
Becoming a 301works member is easy.
(1) A digital contract is sent to you (I've attached it). I just need a reply that you agree to the principals and terms.
(2) Register for an account at archive.org.
(3) I'll set up a collection page for you and give you uploading privileges (you'll need to email me the address you used for your account registration to set up privs).
(4) I'll send you detailed instructions on how to upload either manually or preferably have it automated using our s3 uploader.
I look forward to hearing back from you. Please let me know if there is any additional information you need.
Regards,
Jeff
Internet Archive Team

Participating Company Agreement -- 301Works.org
301Works.org is an initiative of the Internet Archive, and includes a group of participating URL shorteners.
This document serves as an agreement between 301Works.org and the company or concern named at the bottom of the agreement, hereafter called the Participant for the purposes of this agreement.
The Participant agrees to the following terms of participation in 301works.org, and assert that you have the right to commit the Participant to these terms

The Participant will regularly back up their URL mappings (short and long URLs pairs) to the service provided by the Internet Archive, using one of the supported formats. ‘Regularly’ shall be interpreted as at least once per month. The current support format is a tab-delimited text file, with the following fields: (1) long url, (2) short URL, (3) date of creation, and (4) click count (optional).
In the case of a closure of the URL shortening service, the Participant agrees to transfer technical control of the shortening service domain so that 301Works can perform the redirection of shortened URLs. Note: This does not mean that the Participant will transfer ownership of the domain in such a case. Likewise, the Participant, if closing down these service, will agree to allow 301Works to publish the mappings so that users can remap any shortened URLs they may be using.
The Participant is encouraged to place a ‘301Works’ badge on their website, indicating that they are operating in accordance with these terms of participation. We will generate these badges so they will include the 301works logo and the Participant's logo.
If the Participant that ceases to operate, or fails to comply with the terms of participation, they will be given a short period in which to come into compliance, and if they fail to do so within that time frame, they will no longer be considered a participating company.
If the Participant falls out of compliance with the terms of participation -- such as not updating the company archive, or failing to respond to inquiries from 301works or IA staff -- after a two month period, 301works will open the archived URL mappings to user access.
For the sake of perceived privacy by end users, the retrieval of a long URL will require having the short URL, and only a single URL at a time will be returned through the planned 301works interface. This means that all companies that are considering creation of large numbers of shortened URLs should either keep their own records regarding those mappings, or should negotiate with any URL shortening service to provide a database of the mappings, at the time of their creation.
301works.org will retain the URL mappings archive, and will hold these in escrow solely for the purposes outlined here. The archived URL mappings will not be distributed or exploited for other purposes.
301works may change these terms or participation in the future, following consultation with participating companies, but finals decisions about such changes are the responsibility of 301works.org and the Internet Archive.

Hard blockers: #21
Soft blockers: #18 #43 #16 #42


Add anchor link

Add anchor link for Azure Container Apps

@papeMK2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"


How to incorporate ".ts" migrations?

My setup:

".sql" and ".ts" migration files in "src/migrations"
tsc compiles all ".ts" files under "src" and outputs ".js" files to "dist".

How do I invoke postgres-migrations' migrate function?  I want it to pick up ".sql" files from "src/migrations" and ".js" files from "dist/migrations".
One potential hack is to make our build/watch process copy the ".sql" files into "dist" as well.  But I'd like to avoid that if possible.

You'll need to make your build put the JS and SQL files in the same directory, wherever that is, and point postgres-migrations at that directory.
Sorry, I'm not going to write your build for you! :wink:

I'm not asking you to write my build for me.
It's not that hard to copy the ".sql" files in my one-shot build scripts.  But like many people, I use tsc --watch for incremental recompilation in development, and that doesn't seem to have a way to copy ".sql" files.  It would be nice if postgres-migrations supported that use case.
(And in general, I'm not sure if "just point postgres-migrations at the JS files" works for TS.  For example, for the hash of the migration, I think it might be better to use the hash of the TS file rather than the JS file.)

OK, glad you got it to work.
Honestly, supporting JS-generated migrations is probably my biggest regret in this library!

Oh sorry, to be clear, I only meant to cross out the parenthetical comment.
I'm still not sure how to deal with TS migrations when using tsc --watch.

One potential hack is to make our build/watch process copy the ".sql" files into "dist" as well. But I'd like to avoid that if possible.

Why? That sounds like exactly what a build should do.


Block with id: 'latest' not found.

Component
Anvil
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (7398b65 2023-03-29T00:17:00.135482Z)
What command(s) is the bug in?
Not yet repeatable test case
Operating System
macOS (Apple Silicon)
Describe the bug
I am running Python based test suite against Anvil BNB Chain fork, using automining mode.
Randomly tests fail at eth_getBlock("latest")
The JSON-RPC error message is
Block with id: 'latest' not found

I do not think this happens on any real node or Python Ethereum Tester

There is no clear pattern here when/why this happens so I suspect some sort of internal race condition inside Anvil.

No repeatable test case yet.

can please share more context when this happens?
what's the actual call?

Ok I will attempt to figure this out.
It happens randomly in a long (non-Foundry) test run. The issue makes tests flaky, so I have been dealing with this by just marking the tests flaky. Seems like there is no pattern; it can happen at any time.

Closing—stale and cannot reproduce.


[WIP][AIRFLOW-3529] Simplify k8s executor testing process.

Make sure you have checked all steps below.
Jira

[ ] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-3529
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Currently all integration testing for the kubernetes executor takes place on minikube. This is simultaneously a lot slower and not accurate to real-world use-cases. This PR will create a one-step script to run on a real k8s cluster and write documentation for easier onboarding.
Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
All the public functions and the classes in the PR contain docstrings that explain what it does

Code Quality

[ ] Passes flake8

@dimberman would it make sense if you use #3770 as a base branch for this PR? In my PR I've already fixed git-sync and many other issues in the build. WDYT?


Fix TreeBuilder() deprecation

A tree builder without a root node is deprecated since Symfony 4.2

v3.1.0

The failing test is due to Composer:
Fatal error: Allowed memory size of<PHONE_NUMBER> bytes exhausted (tried to allocate 6291488 bytes) in phar:///home/travis/.phpenv/versions/7.0.25/bin/composer/src/Composer/Util/RemoteFilesystem.php on line 594 can you re-run the TravisCI tests?

v3.1.0

Please notice that the v3.1.0 has been already released :)
Can you tag a v3.1.1 release @omansour?

sure

Thanks @omansour ! Looks like packagist is not being updated with the latest releases.
Can you make sure that the hooks are correctly running for https://packagist.org/packages/m6web/amqp-bundle?
Usually it is enough to to re-authenticate with GitHub again


Update example package to WebView2

Fixes #2526

Docs Build status updates of commit 0165ddc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/guides/Native-Packages.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Merge when ready


Confirm accuracy of JSON interfaces in light of recent spec PR's

Describe the issue
There have been some recent clarifications made to the various JSON serialization-related structs added to L3 of the spec. Make sure this library is still accurate as platform and browser vendors start to return these in the wild:

https://github.com/w3c/webauthn/pull/1878
https://github.com/w3c/webauthn/pull/1887

Types are mostly fine, but I need to add some values to AuthenticatorAttestationResponseJSON. PR #400 will take care of these updates.


(https://mitosis.builder.io): Blank page in Safari

Reproduction case
https://mitosis.builder.io - Open using Safari (desktop or mobile)
Expected Behaviour
Show fiddle or show browser incompatibility message.
Actual Behaviour
Blank white page.
The page is not hydrated.
Additional Information
Os: MacOs 13.1 (22C65)
Safari Version 16.2 (186<IP_ADDRESS>.5)

I have zero clue why this doesn't work with Safari...this is very confusing. The Safari console logs don't really help much in this regard

It's a shot in the dark, but maybe it has to do something with regex if used?
https://github.com/knex/knex/issues/5221

It's a regex issue.
Running the fiddle locally, we get this:
Invalid regular expression: invalid group specifier name
eval@[native code] ../core/src/generators/alpine/generate.ts@http://localhost:3000/_next/static/chunks/src_components_App_tsx.js:23770:5 @http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:713:35 __webpack_require__@http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:37:37 eval code@ eval@[native code] ../core/src/generators/alpine/index.ts@http://localhost:3000/_next/static/chunks/src_components_App_tsx.js:23781:5 @http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:713:35 __webpack_require__@http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:37:37 eval code@ eval@[native code] ../core/src/index.ts@http://localhost:3000/_next/static/chunks/src_components_App_tsx.js:25295:5 @http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:713:35 __webpack_require__@http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:37:37 eval code@ eval@[native code] ./src/components/Talk.tsx@http://localhost:3000/_next/static/chunks/src_components_App_tsx.js:26321:5 @http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:713:35 __webpack_require__@http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:37:37 eval code@ eval@[native code] ./src/components/App.tsx@http://localhost:3000/_next/static/chunks/src_components_App_tsx.js:26244:5 @http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:713:35 __webpack_require__@http://localhost:3000/_next/static/chunks/webpack.js?ts=1674059638226:37:37 fn@[native code] promiseReactionJob@[native code]

The offending line is this:
https://github.com/BuilderIO/mitosis/blob/c6b09461f530cdbc71af036914c9899b02fe95eb/packages/core/src/generators/alpine/generate.ts#L63
When removing the lookahead,
const prefixEvent = (str: string) => str.replace(/event/gm, '$event');
the fiddle works as expected.

Very helpful, thank you @DanielHritcu 🙏

I'm still having a same issue. Have the new website been published yet?

@adhrinae it has, but there seems to be a separate part of the codebase causing the same issue.


Add unit tests for Bmi_Multi_Formulation

Because of the complexity, there is not yet a sufficient suit of unit tests for Bmi_Multi_Formulation.  These need to be created.

Handled in #341.


Support GDPR compliance

Should be configurable by developers using the gem.
Something like:
UffDbLoader.config.gdpr_srubbing =
{
  'Contact' => [:address, :name, :email],
  'User' => :email
}

We might also want to implement automatic deletion of old databases after a configurable time.


Get Contract List GraphQL

As NHS admin I want to be able to get Contract List using new admin portal.
So, we need to implement it using graphql

[x] confluence / schema / features
[x] implement
[ ] test

[ ] please, fix bugs according to test cases

when sorry by CONTRACTOR_LEGAL_ENTITY_EDRPOU_ASC/DESC I receive 500


Fieldset

Use this issue to discuss the fieldset component in the ONS Design System

Fieldset config table refers to 'field' rather than 'fieldset' in places

Remove bottom margin on last field in a fieldset to allow control over fieldset vertical spacing


Error: Unhandled Exception: Child Task<PHONE_NUMBER> error: Unhandled Exception: 599

Describe the bug
It looks like rsconnect is not working to re-deploy the app. The first attempt of this commit which changed to use rsconnect::configureApp(appName = appName, size="xxxlarge") was able to deploy successfully, but re-running the action failed to deploy the app (failed attempts) and same for all following commits:
Error: Unhandled Exception: Child Task<PHONE_NUMBER> error: Unhandled Exception: 599.
At first, I thought it might be due to the shinyapps.io server issue, but it's still not able to deploy for two days and deployment worked on the commit before switching to use configureApp.
Priority (select one)

[ ] Minor ⬇
[ ] Major 📢
[x] Critical 🆘

@rrchai I removed the size argument from configureApp() and the app successfully deployed on the first workflow run and a rerun. I'll look into this size option on another branch.

Thanks @afwillia . This issue is solved in this commit.

I was hasty and left an unnecessary call to configureApp(). This commit removes the extra call so that deployApp() is the last call.

Deployment is also working again in feat-UI-dashboard.


Replace plotly.js-dist with plotly.js-dist-min

This reduces the footprint of the dependency

Can we just delete the dependency :upside_down_face:

Can you provide some documentation around the difference between these two npm packages? I'd like to ensure that we retain compatibility 😄. Have you been able to test that notebooks still work?

This is essentially the minified version of it. I did a version bump as well because I didn't see anything super obvious that breaks.
But yeah this is the exact same library, just minor version bumped and minified.

@chlafreniere Are you okay with merging this in and letting it sit in insiders to make sure we're not breaking anything?

Sorry was late here; catching up on mail 😄. You did the right thing. Thanks, @aaomidi.


Sharepoint Online change log questions

Category

[x] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea

Hello, I have a few questions about Sharepoint Online sites' change logs:

In Sharepoint Online, can users modify the change log retention period, or is it always fixed to 60 days?
Is a site's audit log based on / the same as its change log, or are they totally unrelated?
Is the change log guaranteed to reflect all changes in a site, or are there some changes that are by design not included in the change log? For example, I tried editing a .docx file in a document library with Word Online and then querying the web's change log with its REST API, but there was no corresponding ChangeFile event.

Hi @nozhT
Did you find out anything about point 1?
Thanks


from .ctc_forced_aligner import forced_align as forced_align_cpp error

/opt/conda/lib/python3.10/site-packages/pyannote/audio/core/io.py:43: UserWarning: torchaudio._backend.set_audio_backend has been deprecated. With dispatcher enabled, this function is no-op. You can remove the function call.
  torchaudio.set_audio_backend("soundfile")
Traceback (most recent call last):
  File "/workspace/whisper-diarization/diarize.py", line 21, in <module>
    from ctc_forced_aligner import (
  File "/opt/conda/lib/python3.10/site-packages/ctc_forced_aligner/__init__.py", line 1, in <module>
    from .alignment_utils import (
  File "/opt/conda/lib/python3.10/site-packages/ctc_forced_aligner/alignment_utils.py", line 11, in <module>
    from .ctc_forced_aligner import forced_align as forced_align_cpp
ImportError: /opt/conda/lib/python3.10/site-packages/ctc_forced_aligner/ctc_forced_aligner.cpython-310-x86_64-linux-gnu.so: undefined symbol: _ZNK3c1017SymbolicShapeMeta18init_is_contiguousEv

my env is python 3.10.14 torch==2.1.0 torchvision==0.16.0 torchaudio==2.1.0

My original operating system was Windows 11 and it did not work. But later I change to Ubuntu and was able to execute it. In the same docker environment, I think it was related to the operating system.


Talk more about programming on the landing page

The site looks more like a portfolio for a photographer rather than a software engineer. Add a few more sentences to the section about my love for programming and maybe show off some projects.

I think embedding a GitHub contribution graph might look pretty neat…


Inject Jenkins/git Context When exists

If we detect toscactl is executed from jenkins/git we should inject some variables as suite-parameter such as

git commit GIT_REF
git repo URL GIT_REPO_URL
Jenkins job URL JENKINS_JOB_URL
jenkins Job execution JENKINS_JOB_EXECUTION

Thanks @albertpuente


ionic start don't work

When i try to start a new project i get the following errror:
$ ionic start HybridDemo sideMenu
Running start task...
Creating Ionic app in folder /Users/xxx/Desktop/HybridDemo based on sideMenu project

DOWNLOADING: https://github.com/driftyco/ionic-app-base/archive/master.zip

DOWNLOADING: https://github.com/driftyco/ionic-starter-sideMenu/archive/master.zip
Initializing cordova project.
Fetching plugin "org.apache.cordova.device" via plugin registry
Error: failed to fetch the plugin archive
    at /usr/local/lib/node_modules/cordova/node_modules/plugman/src/registry/registry.js:60:26
    at Request.cb [as _callback] (/usr/local/lib/node_modules/cordova/node_modules/plugman/src/registry/registry.js:251:9)
    at self.callback (/usr/local/lib/node_modules/cordova/node_modules/plugman/node_modules/request/index.js:148:22)
    at Request.EventEmitter.emit (events.js:117:20)
    at ClientRequest.self.clientErrorHandler (/usr/local/lib/node_modules/cordova/node_modules/plugman/node_modules/request/index.js:257:10)
    at ClientRequest.EventEmitter.emit (events.js:95:17)
    at Socket.socketErrorListener (http.js:1547:9)
    at Socket.EventEmitter.emit (events.js:95:17)
    at net.js:440:14
    at process._tickCallback (node.js:415:13)
ERROR: Unable to add plugins. Perhaps your version of Cordova is too old. Try updating (npm install -g cordova), removing this project folder, and trying again.
Exiting.

reproduced on OSX and windows 8. obiuvsly cordova and ionic are up-to date

@saamorim It works. ^_^

Why not using the standard "http_proxy" and "https_proxy" env variables? Pretty much all osx/linux programs support these (including cordova, npm, git...)

@sinedied
Your solution worked for me..!!! Thanks ...
I set my proxy as below :
C:\Users\naj>npm config set proxy http://myUserName:myPassword@<IP_ADDRESS>:8000
C:\Users\naj>npm config set https-proxy http://myUserName:myPassword@<IP_ADDRESS>:8000
and upadate the same in system environment variable  "http_proxy" and "https_proxy". Cloased the cmd prompt once and i opend again ,it worked well..!!!

@vincesp My idea of doing all these stuff behind NTLM  proxy is that use CNTLM to convert your NTLM proxy into a local proxy server which does not require any usernames or passwords. It really makes my life a lot easier.

Here's what I found in Win7.
Setting NPM proxy is not going work with this. I tried forwarding to fiddler by setting the npm proxy and https-proxy like
npm set proxy=http://localhost:8888
and fillder would not capture the request.
I then simply set the proxy like
set proxy=http://localhost:8888 and fillder captured the request and started downloading it.
I think CNTLM will work too. I usually switch between setting the actual proxy
http://username:password@domain:port, fiddler and CNTLM. When none of these work I simply try to download the package or get it working on my home pc and copy over. Windows complains about too many characters in path but somehow after that it manages to work with the proxy.


Update the description

To update the description of your module in the public register ZPM, merge the pull request and update the release in Open Exchange please.
https://openexchange.intersystems.com/markdown?url=assets%2Fdoc%2Freleases.md
Thanks.

Fixed by #9


API docs example setup is missing important step of Leaflet.draw configuration

[x] I'm reporting a bug, not asking for help
[x] I've looked at the documentation to make sure the behaviour is documented and expected
[x] I'm sure this is a Leaflet Draw code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[x] I've searched through the issues to make sure it's not yet reported

How to reproduce

Leaflet version I'm using: 1.0.3
Leaflet Draw version I'm using: 0.4.10
Browser (with version) I'm using: Chrome  60.0.3112.90 (Official Build) (64-bit)
OS/Platform (with version) I'm using: Mac OS 10.12.6

What behaviour I'm expecting and which behaviour I'm seeing
The API documentation is missing an important part of the set up. In the README of this Github repo Example Leaflet.draw config the last code block is:
    map.on(L.Draw.Event.CREATED, function (e) {
        var type = e.layerType,
            layer = e.layer;

        if (type === 'marker') {
            layer.bindPopup('A popup!');
        }

        editableLayers.addLayer(layer);
    });

However, in the API docs' "Adding the edit toolbar", this block is missing.
If this code block is excluded the drawn items will not be added to the map.
Minimal example reproducing the issue

[x] this example is as simple as possible
[x] this example does not rely on any third party code

http://bl.ocks.org/clhenrick/fe2d39ed21b19c407ae062db6bdc45ad/3ce171bde0c67dba18d8c3094d08efddf9916638

Nice catch, thanks!

@ddproxy no problem, I can submit a PR but got lost trying to figure out Leaflet's documentation system and how the docs for this plugin are generated from this repo. If you could point me to documentation / help on understanding Leaflet docs generator I could submit a PR.

@clhenrick Documentation is generated from code comment blocks. Run jake or jake docs to generate documentation.


Angle width and height should be computed from video source

not a problem anymore since it now only supports equirectangular videos


修复iOS11 scrollView bug

修复iOS11 scrollView bug

Hi @shengyangyu, thanks for your pull request, the code logic is duplicated, so could you use the code below and delete the comment.
UIEdgeInsets contentInset;
if (@available(iOS 11.0, *)) {
    contentInset = scrollView.adjustedContentInset;
} else {
    contentInset = scrollView.contentInset;
}

Hi @shengyangyu, thanks for your pull request, the code logic is duplicated, so the following code may be better.
        UIEdgeInsets contentInset;
#ifndef __IPHONE_11_0
        if (@available(iOS 11.0, *)) {
            contentInset = scrollView.adjustedContentInset;
        }
#else
        contentInset = scrollView.contentInset;
#endif

very good for your code,thank for you!


Which Authorization callback URL should be used when setting up a new OAuth app?

Issue #327 seems to address this issue, but I would keep this issue open around new documentation necessary either in the Wiki or in the main README.md
Unfortunately there is no guidance around how to do this correctly from anywhere I can find.

Hi there, the callback for the app is set to https://www.gitify.io/callback. Used to be http://localhost/callback but had some issues when I upgraded electron. Unfortunately I don't have access to an enterprise account so I cannot test this properly.
PS. If anyone is willing to give me access to an enterprise instance (even with no access to repos etc.), that would be amazing!

@manosim as of today I can confirm this works for enterprise ☝

That's great - I'm planning to create a new page on the website with documentation around this and put a link in the Enterprise login page. Will leave this issue open until it's done.


RouteGuide example now works with moving between tabs. Fixes issue 6404.

The test failures seem unrelated. @jcanizales  - OK to merge?

Please create issues to get those flakes fixed, or ping and cross-reference them to this PR if they already exist.

@nicolasnoble or @jtattermusch - Could you opine on the test failures? To me they seem unrelated to the change. If there's a known issue could you please link it here?

To be clear - they are unrelated to this change for sure.

failures are unrelated, restarted the tests.

@jcanizales - does route guide example get tested in the CI system? If not,
what more needs to be done for this PR?
On May 5, 2016 8:49 PM, "Jan Tattermusch"<EMAIL_ADDRESS>wrote:

failures are unrelated, restarted the tests.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/6440#issuecomment-217341823

Merging. There's an open issue already for building the samples in CI.


optimize and cleanup CSS a bit

This looks fine, can you update the compressed version too?

Done.
Maybe it's also a good time to update readme and some metadata stuff like jgrowl.jquery.json? :) Maybe even bump version to 1.4.6 and update it everywhere... in sake of consistency!

@serzhenko thanks for your contribution! If you're interested in submitting metadata or README pro I'm happy to review.  Thanks again!


Support required_version with strict equality

Hi! I'm interested in using this plugin to manage my terraform versions. I think that this plugin might benefit from support for the terraform required_version setting.
I can anticipate some objections to this feature:

it increases the complexity of this module with a detail that's specific to Terraform.
it potentially opens up a slippery slope towards more complexity, namely parsing more sophisticated required_version strings (I don't like to imagine doing that in bash).
main.tf is kind of a lie here... I've written the code to grep the entire dir for required_field, although the more I think about it the more I think that the code should only grep `main.tf.

On the other hand, I think that this feature is nice. I can think of a few reasons, and others might think of more:

required_version with strict equality seems to be a pretty simple and obvious means of communicating the desired Terraform version.
required_version is supported natively by Terraform itself.

I'm not sure if this has been considered or not yet - I could not find any evidence of discussion using GitHub's search. Please let me know if I've missed any context around this feature.
I also took the liberty of simplifying some weird shell stuff that I saw going on. It doesn't seem to have broken any tests (although I suppose there were no tests over parse-legacy-file in the first place). Please also let me know if I misunderstood the intent behind the argument-related code that I've changed.
The contents of my commits, including the commit messages, should tell a good story about my changes & motivations, so please read those and not just the overall diff :) Thanks for maintaining this plugin.

thank you for taking the time to review my PR.
I'll leave the discussion of whether or not to split up this plugin to the maintainers :)
In the meantime, I've done my best to address your review comments.

Once the tests are fixed I'll merge this in.

That's what I mean, the checks from CI. It is only the format one that needs fixed after the last commit.

ah, I see that now. thanks for clarifying.

I just realized that I've failed to account for BSD sed. 🤦 I can fix it.

and done.


Remove stale branding references

Hi @szarkos, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (szark). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Stephen, could you remove the /en-us/ part of the link you updated? That breaks the localized experience by forcing users in the translated article back into the EN-US content set.


Use camel-quarkus-build-parent-it as a direct parent of each test module

not intermediate projects

Good point, let me check, where the parent-it is used on the mid-level

d1f80af: replaced camel-quarkus-build-parent-it with camel-quarkus in integration-tests/pom.xml


Name formatting updates

Support new "honorific" field which can be a prefix or suffix depending on the locale
Support "formal_short" and "formal_long" format styles which allow you to format names like "Dr. Smith" and "Dr. Alicia Smith". That is, honorific + family or honorific + given + family names.
Update Korean name formatting so that prefixes and suffixes are both separated from the name with a space
Updated documentation to make it more clear

Looks good to me!


chore(logeer): change colorful logger time-format

Description
current log time format:
2023-11-17T10:40:25Z WRN connection failed _network={2} addr=["/ip4/<IP_ADDRESS>/tcp/21777"] err="failed to dial: context canceled"
2023-11-17T10:40:25Z WRN connection failed _network={2} addr=["/ip4/<IP_ADDRESS>/tcp/21777"] err="failed to dial: context canceled"
2023-11-17T10:40:25Z INF disconnected from peer _network={0} pid=12D3KooWBGNEH8NqdK1UddSnPV1yRHGLYpaQUcnujC24s7YNWPiq
2023-11-17T10:40:25Z INF disconnected from peer _network={0} pid=12D3KooWCwQZt8UriVXobQHPXPR8m83eceXVoeT6brPNiBHomebc

Related issue(s)
If this Pull Request is related to an issue, mention it here.

Fixes #808

Can we have on;y time with seconds, like 10:40:25

@b00f yes, wait.

10:48:07 INF connected to peer _network={1} direction=Outbound pid=12D3KooWCwQZt8UriVXobQHPXPR8m83eceXVoeT6brPNiBHomebc
10:48:07 WRN connection failed _network={1} addr=["/ip4/<IP_ADDRESS>/tcp/21777"] err="failed to dial: failed to dial 12D3KooWPQAGVMdxbUCeNETPiMkeascvMRorZAwtMUs2UVxftKgZ: all dials failed\n  * [/ip4/<IP_ADDRESS>/tcp/21777] failed to negotiate security protocol: read tcp4 <IP_ADDRESS>:21777-><IP_ADDRESS>:21777: read: connection reset by peer"
10:48:07 WRN connection failed _network={1} addr=["/ip4/<IP_ADDRESS>/tcp/21777"] err="failed to dial: failed to dial 12D3KooWMsi5oYkbbpyyXctmPXzF8UZu2pCvKPRZGyvymhN9BzTD: all dials failed\n  * [/ip4/<IP_ADDRESS>/tcp/21777] failed to negotiate security protocol: EOF"
10:48:07 WRN connection failed _network={1} addr=["/ip4/<IP_ADDRESS>/tcp/21777"] err="failed to dial: failed to dial 12D3KooWSJREEzTZRzc9wpkU3EW2m9ZGfzrC9jjuwS6wR5uaAZme: all dials failed\n  * [/ip4/<IP_ADDRESS>/tcp/21777] failed to negotiate security protocol: EOF"
10:48:07 INF entering new height _consensus="{tpc1p5t7d575 2320/0/new-height/0}" active=false height=2320


suggestion

Submitter: Dominic Stephan
Email<EMAIL_ADDRESS>would like to have ghouls included as well
other tan that i love it

This may be a thing in the future, but not planned as of yet.


make devinstall does not work

Following https://github.com/Seagate/cortx-hare#installation:
[vagrant@cmu hare]$ sudo make devinstall
...
--> Installing hax with 'source /data/hare/.py3venv/bin/activate; python3.6 setup.py develop --prefix /opt/seagate/cortx/hare'
Traceback (most recent call last):
  File "setup.py", line 141, in <module>
    library_dirs=[get_motr_libs_dir()],
  File "setup.py", line 97, in get_motr_libs_dir
    assert P.isfile(libmotr), f'{libmotr}: No such file'
AssertionError: /data/cortx-motr/motr/.libs/libmotr.so: No such file
make: *** [/opt/seagate/cortx/hare/lib/python3.6/site-packages/hax.egg-link] Error 1

Commit 571ae39

Looks like the regression was introduced at commit<PHONE_NUMBER>3088d902110375c723e9154cb31913.
cc @knekrasov

Looks like the correct command should be sudo sh -c 'export M0_SRC_DIR=/data/motr; make devinstall'.

I think by default it checks cortx-motr at ../HARE_SRC. I have created a symlink to cortx-motr at ../HARE_SRC.
This failure can be seen also when cortx-motr is not compiled.


feat: floor_date and round_date now supports quarter as a unit

This allows us to use "quarter" as a unit for

floor_date
round_date

functions.

This addresses #18

Thanks for putting this together! I'll take a look shortly

Sounds good.no rush at all. I'll go ahead and merge this +/- release and look at for more!
Thx for the help!


[textlint] Enforce "backend" vs "back end"

The docs use "backend" in all places except one:
$ find content -type f -exec grep -nH -iEe "\bbackends?\b" {} + | wc -l
     306
$ find content -type f -exec grep -nH -iEe "\bback ends?\b" {} + | wc -l
       1

So I'd suggest that we add a textlint rule for this. @svrnm et al. WDYT?

PR commented!


Use promise instead of callback

Use promise https://github.com/kriskowal/q to be able to stack them. Very usefull in order to wait for all setup to be finished.
Instead of (ES6) :
gpio.setup(40, gpio.DIR_OUT, err => {
   if (err) { throw err; }
   gpio.setup(38, gpio.DIR_OUT, err => {
     if (err) { throw err; }
     gpio.setup(37, gpio.DIR_OUT, err => {
        if (err) { throw err; }
        // do something
     }
   }
});

use :
gpio.setup(40, gpio.DIR_OUT).then(() => {
   // do something
   return gpio.setup(38, gpio.DIR_OUT);
}).then(() => {
   return gpio.setup(37, gpio.DIR_OUT);
}).then(() => {
   // do something
}).catch(err => {
   throw err;
}

Exemple of implementation in rpi-gpio.js :
fs.writeFile(PATH + '/gpio' + pin + '/value', value, cb);

become
var deferred = q.defer();
fs.writeFile(PATH + '/gpio' + pin + '/value', value, (err) => {
   if (err) {
      deferred.reject(err);
   } else {
      deferred.resolve();
   }
});
return deferred.promise;

Hi, thanks for the suggestion, but I'm not sure I want to take the module down this route, for the following reasons:

this is a major breaking change to the API, so there would have to be very compelling reason to do it.
a lot of people using this module are quite new to node / JS, and already struggle with the callback interface. I'm worried that these users will find a promise API even more obscure and confusing.
there is an example in the readme which does a similar setup of 3 pins as in your example, but using the async module. So, I think most advanced users will already be able to use tools like async to help keep their code tidy and avoid nested callbacks.
Promises are just one of many (relatively) new approaches to doing async, and if we are going to change the API, I'd prefer to wait and see what direction the JS community seems to be moving in.

It's worth saying that this module originally came about because I was unhappy with the interfaces of other GPIO modules available, and I specifically wanted one with an err-back interface, which at the time I considered to be the most simple interface achievable while being honest about the asynchronous nature of what was happening.
One option you might like to consider would be to wrap this module in a promise style interface and distribute that as an alternative.
I'll leave this issue open for a bit in case people want to discuss it. Cheers.

Some other libraries I saw opted to leave the callback as an alternative and implement Promises anyways.
So you would have the 2 options to handle the asynchronous task, the callback and the returned promise.
Promises will help error handling also.
Promises are now natively supported in ES6, so I think it's the way to go.
Observables are the new shiny thing out there, but I don't think they apply to this case; they are more for handling a stream of multiple async events.
If you like the idea @JamesBarwell, I could write a PR for you to check out

I ended up here because I had the same issue as #41, and thought that it would be nice to have promises for error hadling. It turns out that you can have one single error handler, which is nice. And it's flexible, so you could also have separated error handlers for each event, which is also nice. The bum is that by default, unhandled errors in promises fail silently :(
Take a look at
http://www.2ality.com/2016/04/unhandled-rejections.html
http://jamesknelson.com/are-es6-promises-swallowing-your-errors/
But I think it's not in the scope of a library to handle application level errors, so we don't have much to do there. Errors will fail silently if unhandled.
The only other option I see is to throw the error without letting the user handle it (except with a try catch block)
What do you think @JamesBarwell ?

The bum is that by default, unhandled errors in promises fail silently :(

This isn't quite true. At the very least it isn't true anymore. Generally a promise will throw an UnhandledPromiseRejection error which will contain the stack trace that lead to the original error.

@canda I've been considering your suggestion of an additional Promises interface alongside the errback interface and think this could work well.

We can avoid any API breaking changes.
Users who prefer the node-style errback interface can continue to use it.
Promises do seem to be settling down to be the new standard way of doing things.

Very happy to receive a PR for this (with some tests please!!).
Yes, there will be some users confused about how to use the Promises just as there are today with the async err-back API, but I don't think that's something to be solved in the code. So I'd say let's just keep it a very standard implementation and just make sure the docs point people in the right direction.

Is there documentation somewhere on how to use the promises interface?  I need to setup an array of promises based on gpio.reads as I am using this for a sprinkler with pump, and do not want to turn on the pump unless at least one zone is open.

There's some brief documentation already in the readme and I will look to add some examples over time, but really this interface just wraps up the existing error-first interface.
It sounds like you might want to investigate using Promise.all to gather the results of multiple read queries. When that Promise.all resolves, you should be able to access each individual read data to check whether any of the zones are open. If you're still stuck then feel free to share some code and maybe I or others can advise.


[Event Request] Page 6057 - Contract Line Selection - OnAfterSetSelectionFilter

Dear ALAppExtensions team,
through this issue we would like to request adding event publisher OnAfterSetSelectionFilter in Page 6057 Contract Line Selection with the following signature:
    procedure SetSelectionFilter()
    begin
        case SelectionFilter of
            SelectionFilter::"All Service Items":
                SetRange("No. of Active Contracts");
            SelectionFilter::"Service Items without Contract":
                SetRange("No. of Active Contracts", 0);
        end;
        //>>New Event
        OnAfterSetSelectionFilter(Rec, SelectionFilter);
        //<<New Event
        CurrPage.Update(false);
    end;

Event:
    [IntegrationEvent(false, false)]
    local procedure OnAfterSetSelectionFilter(var ServiceItem: Record "Service Item"; SelectionFilter: Option "All Service Items","Service Items without Contract")
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 49170.


fix: for fw 3.x mark production with only zero values as EnvoyPoorDataQuality error

When Envoy running FW 3.x restart they may send all zero values with status 200 while the internals are still restoring data. Observations are there may be 2-3 minutes of zero's before the pre-restart values are restored. When using the data with Home Assistant Energy dashboard the effect is a step in production values. See #168 and https://github.com/home-assistant/core/issues/120091.
This PR adds a _validate_data step to the envoy.update method to implement a data validation step. It currently implements 1 validation rule. If major firmware version is 3 and all values in data.system_production are zero it will signal exception EnvoyPoorDataQuality. For Home Assistant this will continue the outage until data is restored and only have a data gap instead of  gap followed by zero values.
Error communicating with API: Data rejected on rule: FW 3.x production all zero at startup (3.9.36).

Hi catsmanac,
Thank you very much for your help and merging a fix.
I am currently admitted to a hospital, so I won't be immediately implement it, but I am confident it is fixed.
Thank you and others who have contributed for maintaining this integration.

Hi @MeanderingNL, sorry to hear that. Wish you all the best in your recovery. Get well first, beterschap.


Feature/strict options

It seems that this PR/issue will be blocked until ionic@4 release: https://github.com/ionic-team/ionic/issues/14358#event-1597774293

After https://github.com/ngx-rocket/generator-ngx-rocket/pull/369 is merged, I'll rebase this PR and it should be okay 🤞

#369 is now merged. @sinedied do you want to proceed with this one? I can have a look myself if you do not have time, but I'm always doubtful towards rebase operations.

@bursauxa If you can take a look at it, do it and yes a merge here is probably the best idea given the shallow conflict surface 👍


Update Style.MD

This example is more straight forward for a new learner. The conflicting attributes(e.g color) in the current example where you have two styles modifying the same text  is confusing. In last TEXT, red is not rendered for example.

This section is about to get an overhaul... and the cascade of CSS likely to get covered. So removing it now would not make sense. Thank you for your suggestion, though! Well be sure to dig in an confuse learners less ;)


Is this project still alive?

Curious if development is still planned for Dot?
I'm really excited about this project and hope it can be rejuvenated!

I do plan to get back to this in a couple of months.  I had taken a break to investigate related things and have a better picture for the overall project now.


Add CockroachDB to reference docs

Describe this PR
Updating reference docs to include CockroachDB:

the schema reference
CLI reference
Connection urls prisma.io/docs/reference/database-reference/connection-urls

Changes

What issue does this fix?
Fixes #2561
Any other relevant information

I made a mess of this because I thought Cockroach was going into GA for 3.13.0, so I was trying to remove Preview references at the same time. I've reverted these now, so this one can go out once I've addressed the review comments and then I'll make a separate one for 3.14.0 to get rid of the Preview references.

We managed to get the proposal on cockroachdb native types accepted and implemented for tomorrow's release, so we'll have to reflect that in the docs. This is what we implemented. I'm ready to help as much as needed in discussing this and/or updating the docs, just ping me :)


bug: need to upgrade to project template

Environment information

ape and plugin versions:

$ ape --version
# ...copy and paste result of above command here...

$ ape plugins list
# ...copy and paste result of above command here...

Python Version: x.x.x
OS: osx/linux/win

What went wrong?
Please include information like:

what command you ran
the code that caused the failure (see this link for help with formatting code)
full output of the error you received

How can it be fixed?
Fill this in if you have ideas on how the bug could be fixed.

merge project template by hand


Synchronize all pending operations

With mpi4jax we are running into a problem when Python exits before a pending operation has the chance to be executed.
When using MPI, MPI_Finalize runs at interpreter exit. Any MPI operation called after that will deadlock, which can happen due to JAX's  asynchronous dispatch.
Is there a way to force synchronization of all pending XLA operations? Then we could register that as an atexit handler that runs before MPI_Finalize.
block_until_ready doesn't work for 2 reasons:

Need to keep track of all running operations
Some of our primitives only return an XLA token which doesn't have a block_until_ready method

On all current XLA platforms, there is only one (default) compute stream per device. That means any asynchronous operation will be enqueued at the end of the current queue for that compute stream, meaning that jax.device_put(0.).block_until_ready() will be a valid way to synchronize the whole device. (We could also add a way to do this directly, but that should work for now!)

That sounds promising, but unfortunately it doesn't seem to work. I can add the line you proposed to the end of the script and see that it runs before my custom XLA call. Is this a CPU vs GPU thing? We're only running on CPU so far.
It does seem to work if I JIT it, though:
jax.jit(lambda: jax.device_put)(0.).block_until_ready()

Does that make sense? It's hard to tell whether this fixes the problem or it just works because it takes longer so execute (so the race condition is less likely to be triggered).

You’re right, of course! The snippet I gave doesn’t synchronize the compute stream because it runs on the independent memcpy stream. Jitting it as in your snippet (or running anything that launches an XLA computation) will synchronize the compute stream.

I use this now:
(jax.device_put(0.) + 0).block_until_ready()

which works OK.
An official way to do this would be nice, though, as this workaround seems a bit brittle (relying on JAX implementation details).

Either way, thanks for the help, of course :)


[sequencer] If all bids from auction attempt fail, remove from cache

Need to remove fully failed auctions from the cache. No point keeping them around.

What determines if a bid fails? If a multipath transfer between 2 routers fails, do both bids fail (e.g. what if only 1 of the two bids was faulty)?
I think we should address why bids (AKA executes) are failing before we just toss out failing ones. That way we can avoid unnecessary work and log reasoning behind decisions to ignore certain bids. So before ever estimating gas, let's do some sanity checks.
So, why would a bid fail?

The router (or one of the routers) has insufficient funds. For this, we should be checking the router's funds before estimating gas and/or sending the transfer. We should not just blindly call estimate gas on the whole execute tx.
The signature is invalid. This is actually a genuine reason to throw out the bid! We should have an off-chain check in utils to make sure the signature is indeed valid; just something that mimics the on-chain check. We may want to wait on this until we have the relayer fees diff in.
The relayer address is not whitelisted. We should always have a reference to who the relayers are for each chain. If we don't, then the chains (and the sequencer) were not configured properly.
The asset is not whitelisted. Should be checked when we receive the bid.
The router is not whitelisted. Should be checked when we receive the bid.

Can't think of any others, except maybe a bug in the contracts... which means that the bid is not the point of failure.


TOMEE-4180 - CXF 3.5.5

Ports the changes made to 9.x to support cxf 3.5.5 (Note: 3.4.x is eol) without the jakarta transformation.
Aligns the CXF patch sources with CXF (including formatting) to ease the way of upgrades - we should proabably get rid of the shading in a next / future step.
This PR might also include a (partial) fix for https://issues.apache.org/jira/browse/TOMEE-4179
Full build:

https://ci-builds.apache.org/job/Tomee/job/pull-request-8.x-manual/9/

i'd you are ok, after this is merged, i would like to make properties to centralize/factorize all these new versions (wss4j santuario staxex cxf etc)

Note: The boms are auto generated. Most of the Versions should already be properties, no?

Note: The boms are auto generated. Most of the Versions should already be properties, no?

right! looks like staxex is there by transitivity and does not currently need its own property.
look good! I might come later to sort the properties by name and add a comment for groupIDs if need be

Thanks for the PR @rzo1 . I triggered yesterday https://ci-builds.apache.org/job/TomEE/job/pull-request-8.x-manual/12/ and it only had one failing test related to (org.eclipse.microprofile.jwt.tck.config.PublicKeyAsFileLocationURLTest.arquillianBeforeClass)
I tested the test locally and is working fine.

Thanks @cesarhernandezgt


expose verbose option to python

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.32%. Comparing base (f48faf0) to head (7a838f1).
Report is 1 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #77      +/-   ##
==========================================
+ Coverage   94.30%   94.32%   +0.02%
==========================================
  Files          38       38
  Lines         843      846       +3
  Branches       79       79
==========================================
+ Hits          795      798       +3
  Misses         48       48

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


outline what happens when API issuer is deprovisioned

a user with "security reader" issues a API within MCAS
what happens when that user leave the company / is deprovisioned?
material needs a clear statement on this - does it reside or is it deleted?

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

ID: a49f4498-7b65-28f7-f31d-c7a21149025e
Version Independent ID: d93e55ac-bec8-5aba-5cba-923cee400542
Content: API token management in Cloud App Security
Content Source: CloudAppSecurityDocs/api-tokens.md
Service: cloud-app-security
Product: ****
Technology: ****
GitHub Login: @shsagir
Microsoft Alias: shsagir

@bakerm00 Thanks for contacting Microsoft with feedback about our product documentation. Depending on the complexity, it could take from a few business days to a few weeks to look further into your question, issue, or suggestion. We'll contact you if we need further information, and you'll receive an email message each time we "@mention" you in a comment.
Thanks again for submitting your feedback. Your suggestions help improve our documentation.

@bakerm00 Thanks again for your feedback. I received the following response from the product team regarding your query:

Deprovisioned users API tokens are retained but have no use. Any attempt to use them will result in a permission denied response.

We've will be submitting a documentation change based on your query, and the updated article should be live by tomorrow. Please let us know if there's anything more we can do for you. To follow up on this issue, leave us a comment with an @mention.


Jesse: Blacklist (?-i:WizardGhosthacker)(?#t.me)

Jesse requests the blacklist of the website (?-i:WizardGhosthacker)(?#t.me). See the MS search here and the Stack Exchange search in text, in URLs, and in code.

(?-i:WizardGhosthacker)(?#t.me) has been seen in 5 true positives, 0 false positives, and 0 NAAs.

Feel free to reject this one, I did another one with blacklist-keyword instead of blacklist-website.

Rejected by Jeff Schaller in Charcoal HQ. Reason: 'in favor of the keyword version in PR 9233'


rty: fix crashes when the terminal window is too small

Hello @maiamcc,
Please review the following commits I made in branch nicks/ch1052/crash:
8c4e8d154169d7349963202253e3c5680b8348b9 (2018-12-11 15:20:59 -0500)
rty: fix crashes when the terminal window is too small

what does it look like when we try to render in a too-small window?


Error if .gnupg is root-owned

Something at-first-run is causing ~/.gnupg to be root-owned, which leads to the following:
❯ boxen
Boxen is up-to-date.
Notice: Compiled catalog for bean.a-rwx.org in environment production in 12.42 seconds
Notice: /Stage[main]/Spaarti/Exec[/Users/akerl/.bin/repo_sync]/returns: executed successfully
Notice: /Stage[main]/Ssh/Exec[remove stale SSH key]/returns: executed successfully
Notice: /Stage[main]/Ssh/Ssh_key[akerl]/ensure: created
Notice: /Stage[main]/Ssh/Github_ssh_key[/Users/akerl/.ssh/id_ed25519.pub]/ensure: created
Notice: /Stage[main]/Ssh/Exec[ssh-add /Users/akerl/.ssh/id_ed25519]/returns: Error connecting to agent: Permission denied
Error: ssh-add /Users/akerl/.ssh/id_ed25519 returned 2 instead of one of [0]
Error: /Stage[main]/Ssh/Exec[ssh-add /Users/akerl/.ssh/id_ed25519]/returns: change from notrun to 0 failed: ssh-add /Users/akerl/.ssh/id_ed25519 returned 2 instead of one of [0]
Notice: /Stage[main]/Ssh/File[/Users/akerl/.ssh/id_ed25519]: Dependency Exec[ssh-add /Users/akerl/.ssh/id_ed25519] has failures: true
Warning: /Stage[main]/Ssh/File[/Users/akerl/.ssh/id_ed25519]: Skipping because of failed dependencies
Notice: Applied catalog in 21.16 seconds

Will re-open on next clean pass to see what causes this


Please add screenshot for "When creating linked service for Azure Synapse serverless SQL pool from UI, choose "enter manually" instead of browsing from subscription."

[Enter feedback here]
Please add screenshot for "When creating linked service for Azure Synapse serverless SQL pool from UI, choose "enter manually" instead of browsing from subscription.

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

ID: b8f48c7b-2f52-6fe0-9ea6-358380e0c815
Version Independent ID: 7f448f1e-8d3d-fb5c-6f68-837e46e7b176
Content: Copy and transform data in Azure Synapse Analytics - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/connector-azure-sql-data-warehouse.md
Service: data-factory
Sub-service: data-movement
GitHub Login: @jianleishen
Microsoft Alias: jianleishen

Please add screenshot for "When creating linked service for Azure Synapse serverless SQL pool from UI, choose "enter manually" instead of browsing from subscription." to tell customer how to find serverless endpoint name and how to configure it in linked service. Contact<EMAIL_ADDRESS>if you want more information

@toastjoqo
Thanks for your feedback! We will investigate and update as appropriate.

@toastjoqo
Thanks for your feedback! We have assigned the issue to author and will provide further updates.

#assign:WilliamDAssafMSFT

Addressed in comments in https://github.com/MicrosoftDocs/azure-docs/pull/98500#issuecomment-1248444077.
#please-close


[build] rcore module does not compile under linux with -std=c99 without -D_GNU_SOURCE

Please, before submitting a new issue verify and check:

[ ] I tested it on latest raylib version from master branch
[ ] I checked there is no similar issue already reported

Issue description
Under Linux, rcore.c cannot compile as c99, without defining _GNU_SOURCE
gcc -c rcore.c -DGRAPHICS_API_OPENGL_33 -DPLATFORM_DESKTOP -std=c99
In file included from rcore.c:128:
rgestures.h: In function ‘rgGetCurrentTime’:
rgestures.h:540:21: error: storage size of ‘now’ isn’t known
  540 |     struct timespec now;
      |                     ^~~
rgestures.h:541:5: warning: implicit declaration of function ‘clock_gettime’ [-Wimplicit-function-declaration]
  541 |     clock_gettime(CLOCK_MONOTONIC, &now);
      |     ^~~~~~~~~~~~~
rgestures.h:541:19: error: ‘CLOCK_MONOTONIC’ undeclared (first use in this function)
  541 |     clock_gettime(CLOCK_MONOTONIC, &now);
      |                   ^~~~~~~~~~~~~~~
rgestures.h:541:19: note: each undeclared identifier is reported only once for each function it appears in
rcore.c: In function ‘GetApplicationDirectory’:
rcore.c:3074:19: warning: implicit declaration of function ‘readlink’ [-Wimplicit-function-declaration]
 3074 |     ssize_t len = readlink("/proc/self/exe", appDir, size);
      |                   ^~~~~~~~
rcore.c: In function ‘WaitTime’:
rcore.c:4782:16: error: variable ‘req’ has initializer but incomplete type
 4782 |         struct timespec req = { 0 };
      |                ^~~~~~~~
rcore.c:4782:33: warning: excess elements in struct initializer
 4782 |         struct timespec req = { 0 };
      |                                 ^
rcore.c:4782:33: note: (near initialization for ‘req’)
rcore.c:4782:25: error: storage size of ‘req’ isn’t known
 4782 |         struct timespec req = { 0 };
      |                         ^~~
rcore.c:4789:16: warning: implicit declaration of function ‘nanosleep’ [-Wimplicit-function-declaration]
 4789 |         while (nanosleep(&req, &req) == -1) continue;
      |                ^~~~~~~~~

Now, adding -D_GNU_SOURCE to that command, it compiles without any errors or warnings
There appears to be some code already trying to handle this case:
https://github.com/raysan5/raylib/blob/587e61def9450dcf64648177e1158acc9762f2a2/src/rcore.c#L154-L157
But, it doesn't seem to work
The raylib Makefile adds -D_GNU_SOURCE, which could be a reason this is overlooked for so long
It also compiles with -std=gnu99, which seems to be what is allowing CMake to work, it uses it by default.
This issue can be reproduced with CMake too, if it is invoked like this:
cmake .. -DCMAKE_C_EXTENSIONS=OFF

@Peter0x44 Could this define just be added under the mentioned lines in rcore? (I don't know it it could have any side effect)

@raysan5 I think it can, but perhaps not in that exact place in rcore
One thing to be aware of is that it must be defined before any other header is included, because some headers can apparently include each other
man feature_test_macros for me says:
       NOTE:  In order to be effective, a feature test macro must be defined before including any header files.  This can be done either in the compilation command (cc -DMACRO=value) or by defining the macro within the source code before including any headers.  The requirement that the macro must be defined
       before including any header file exists because header files may freely include one another.  Thus, for example, in the following lines, defining the _GNU_SOURCE macro may have no effect because the header <abc.h> itself includes <xyz.h> (POSIX explicitly allows this):

@Peter0x44 I reviewed this issue, as far as it is a compilation flag, shouldn't it be added to the build system?


POC: Upfront Fees to Mitigate Channel Jamming

This PR is a proof of concept for the proposal outlined in lightning/bolts/pull/1052.
It needs no reviewer attention - really just squatting here to aid discussion (thanks for having me, as usual).
There are various very proof-of-concpety things about this:

It doesn't survive restarts (needs #7297)
It uses default values for forwarding nodes upfront fees and hardcodes then for receiving nodes

But it does have an itests which passes, which is nice.

Closing for now since this is just a POC, won't be actively developed anytime soon!


Improve Franca support

Add handling of manages keyword.
interface B { version {major 1 minor 0} }
interface C { version {major 1 minor 0} }
interface D { version {major 1 minor 0} }
interface A manages B,C,D {
 version {major 1 minor 0}
}

AST has been extended. Interface object not has an array manages
containing the list of interfaces.

Coverage decreased (-0.2%) to 96.434% when pulling f88967b18d6c9cdd0ebbda56f7c63cfa42c005b5 on warzon:add-manages-keyword-support into dd7ff6849b6122bdfc614d0557d19687ec234279 on zayfod:master.


flood_sleep_threshold unused?

I'm seeing RpcError { name: "FLOOD_WAIT", value: Some(17) }. I have flood_sleep_threshold: Some(60), in my params.
I've cloned entire grammers repo and only 3 mentions of this field are found

none of which actually read that value or pass it down.
Am I missing something or this field is a stub for the future?

This field is a stub for the future.

Ok, thanks for explanation

We can keep this open to track its implementation.
If you (or someone else) is interested in implementing this, it should be as simple as modifying the invoke method:
https://github.com/Lonami/grammers/blob/3ed47232c01dc3c05426cc3c346e7deb1dadc002/lib/grammers-client/src/client/net.rs#L221
to detect this error and sleep automatically before retrying. Telethon is slightly more advanced and keeps a cache of "floodwaited requests" to avoid sending them entirely if we know they would floodwait, but for an initial implementation, it is not necessary.

I saw some implementation in git history. Why it was removed?

Might have been removed unintentionally on accident, or intentionally temporarily during refactoring. I can't really remember. But the idea definitely is for it to be implemented.