Undress App: The Best Undress AI Tool of 2024

Discover why Undress App is the leading Undress AI tool in 2024!
With cutting-edge AI technology, this app allows users to create high-quality, realistic undressed images in seconds. Its user-friendly interface makes it accessible to everyone, while top-tier privacy features ensure your data remains safe and secure. Whether you’re exploring creative projects or testing the limits of AI-powered image editing, Undress App delivers fast, reliable, and realistic results every time. Experience the best in undressing AI technology today!
🟢 ➤ ➤ ➤ 🌐 Get Free Undress AI
🟢 ➤ ➤ ➤ 🌐 Get Free Undress AI
🟢 ➤ ➤ ➤ 🌐 Get Free Undress AI

✅  TOP 25 UNDRESS AI TOOLS 2024
![TOP 25 UNDRESS AI TOOLS  2024](https://undressing.tools/assets/images/meta/undress_ai.png'TOP 25 UNDRESS AI TOOLS  2024')

Women Undress AI Create Deepnude Images Online Free
Undress with AI that creates deepnude images from women’s photos online free. Generate realistic image with precision and ease!
Click to Undress Free - 👉 https://undresswith.ai
Click to Undress Free - 👉 https://undresswith.ai
Click to Undress Free - 👉 https://undresswith.ai

Remove in cloth

Remove in cloth

Undress with AI that creates deepnude images from women’s photos online free. Generate realistic image with precision and ease!

Explore advanced AI tools for fun and creativity! Try our free, online AI-powered tools to undress clothes from photos effortlessly. Start now—it's fast and free!
Click to Undress Free - 👉 Upload images Now
Click to Undress Free - 👉 Undress images Now
Click to Undress Free - 👉 Upload images Now

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike. Users can enjoy: https://deepnudefree.online/
Or: https://securecd-smrtnd.com/S9tOCSI3RS
No cost: Completely free with no hidden charges.
Accessibility: Available on various platforms.
Advanced results: Crisp and accurate outputs.
Why Choose DeepNude AI?
Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

Get free undress ai : https://securecd-smrtnd.com/S9tOCSI3RS
Get free undress ai : https://securecd-smrtnd.com/S9tOCSI3RS
Get free undress ai : https://securecd-smrtnd.com/S9tOCSI3RS
Get free undress ai : https://securecd-smrtnd.com/S9tOCSI3RS
Get free undress ai : https://securecd-smrtnd.com/S9tOCSI3RS

Get free undress ai without sing up : https://smrturl.co/d0f9f3d
Get free undress ai without sing up : https://smrturl.co/d0f9f3d
Get free undress ai without sing up : https://smrturl.co/d0f9f3d

Get free undress ai : https://www.3636.bio/
Get free undress ai : https://www.3636.bio/
Get free undress ai : https://www.3636.bio/
Get free undress ai : https://www.3636.bio/
Get free undress ai : https://www.3636.bio/
Get free undress ai : https://www.3636.bio/
Get free undress ai : https://www.3636.bio/

Get free undress ai without sing up : https://7070.us/
Get free undress ai without sing up : https://7070.us/
Get free undress ai without sing up : https://7070.us/

Get free undress ai without sing up : https://7070.lo/
Get free undress ai without sing up : https://7070.lo/
Get free undress ai without sing up : https://7070.lo/
Get free undress ai without sing up : https://7070.lo/
Get free undress ai without sing up : https://7070.lo/
Get free undress ai without sing up : https://7070.lo/

Best undress ai for free without sing up : https://7070.lol/
Best undress ai for free without sing up : https://7070.lol/
Best undress ai for free without sing up : https://7070.lol/
Best undress ai for free without sing up : https://7070.lol/
Best undress ai for free without sing up : https://7070.lol/
Best undress ai for free without sing up : https://7070.lol/

👇Click for a free trial👇👇Click for a free trial👇👇Click for a free trial👇👇Click for a free trial👇
👇Click for a free trial👇👇Click for a free trial👇👇Click for a free trial👇👇Click for a free trial👇
Free deepnude ai :
Free deepnude ai :
Free deepnude ai : https://bt-fr-cl.com/tds/ae?tdsId=s7451sto_r&tds_campaign=s7451sto&s1=ps&utm_source=int&utm_sub=opnfn&subid={subid}&subid2={subid2}&clickid={clickid}l&affid=181c7b69
Free deepnude ai :
Free deepnude ai : https://bt-fr-cl.com/tds/ae?tdsId=s7451sto_r&tds_campaign=s7451sto&s1=ps&utm_source=int&utm_sub=opnfn&subid={subid}&subid2={subid2}&clickid={clickid}l&affid=181c7b69

I personally use this platform for undressing images. It's easy to use, and the pricing is quite affordable.
https://www.undressly.com/

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike. Users can enjoy: https://deepnudefree.online/
Or: https://securecd-smrtnd.com/S9tOCSI3RS
3- Best undress ai for free without sing up : https://7070.lol/
4- surprise For an iPhone at a surprising price : https://cd-sec.com/?a=256440&c=383557&co=316585&mt=21
No cost: Completely free with no hidden charges.
Accessibility: Available on various platforms.
Advanced results: Crisp and accurate outputs.
Why Choose DeepNude AI? https://7070.us/
Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike. Users can enjoy: https://deepnudefree.online/
Or: https://securecd-smrtnd.com/S9tOCSI3RS
3- Best undress ai for free without sing up : https://7070.lol/
4- surprise For an iPhone at a surprising price : https://cd-sec.com/?a=256440&c=383557&co=316585&mt=21
No cost: Completely free with no hidden charges.
Accessibility: Available on various platforms.
Advanced results: Crisp and accurate outputs.
Why Choose DeepNude AI? https://7070.us
Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

I found this tool really helpful. For anyone interested in exploring more, there's a useful resource here:
👉Get free undress ai without sing up : . Check it out for more details. 👍
👉Get free undress ai without sing up .
👉Get free undress ai without sing up .

AI Undresser with AI creates deepnude images online for free. Generate realistic image with precision and ease!
Click to use for free AI Undresser App - 👉 DeepNude
Click to use for free AI Undresser App - 👉 DeepNude
Click to use for free AI Undresser App - 👉 DeepNude

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.  With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.
Advanced results: Crisp and accurate outputs.
Why Choose DeepNude AI? https://7070.us
Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.  With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.
Advanced results: Crisp and accurate outputs.
Why Choose DeepNude AI? https://7070.us
Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.  With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.
Advanced results: Crisp and accurate outputs.
Why Choose DeepNude AI? https://7070.us
Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.  With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike.
Advanced results: Crisp and accurate outputs.
Why Choose DeepNude AI? https://7070.us
Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

I just discovered an amazing tool that's super helpful! 🚀 If you're curious to try it out, check these resources for free access — no sign-up needed! 🙌

🔗 👉🔴 Unlock AI magic for free here!
🔗 👉 🔴Explore free AI features now!
🔗 👉🔴 Get started with AI — no sign-up required!
🔗 👉 🔴Try more AI features for free!

Don't miss out! 🌟

I just came across an incredible tool that's incredibly useful! 🚀✨ If you want to give it a try, explore these resources for free access—no sign-up required! 🙌🔗
🔗 👉🔴 Unlock AI magic for free here! ✅
🔗 👉 🔴** Explore free AI features now! ✅
3- Best undress ai for free without sing up :Click HERE >>
4- surprise For an iPhone at a surprising price :Click HERE >>

👇Click For A Free Trial No "Vcc" No "Sing Up"👇
👉👉Directly from here
👉👉Directly from here

👉🔴 Click HERE >>
👉🔴 Click HERE >>
👉🔴 Click HERE >>

Here To Get Free Tools Undress Ai Tools : Click Here

Searching for 'DeepNude Free' might expose you to malware or illegal content.  Advanced results: Crisp and accurate outputs. Why Choose DeepNude AI? https://7070.us/ Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

withount sing up : 👍
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
Accessibility: Available on various platforms. Advanced results: Crisp and accurate outputs. Why Choose DeepNude AI? https://www.3636.bio/ Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

withount sing up : 👍
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
🟢 ➤ ➤ ➤ 🌐 Get Free Deep Nude AI
Accessibility: Available on various platforms. Advanced results: Crisp and accurate outputs. Why Choose DeepNude AI? https://www.3636.bio/ Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike. Users can enjoy: https://deepnudefree.online/
👉 Deepnude Free + Without Sing Up
OR : 👉 Deepnude Free + Without Sing Up
OR 👍👉🔴 Click HERE >>
3- Best undress ai for free without sing up : 👉 Deepnude
4- surprise For an iPhone at a surprising price : https://securecd-smrtnd.com/s?a=256440&sm=46517&co=316585&mt=21
No cost: Completely free with no hidden charges.

👉🔴 Get Free undress ai >>
👉🔴 Get Free undress ai >>
👉🔴 Get Free undress ai >>
Accessibility: Available on various platforms. Advanced results: Crisp and accurate outputs. Why Choose DeepNude AI? https://frestr20.blogspot.com/ Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions
withount sing up : 👍
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE
DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike. Users can enjoy: https://deepnudefree.online/
👉 Deepnude Free + Without Sing Up
OR : 👉 Deepnude Free + Without Sing Up
OR 👍👉🔴 Click HERE >>
3- Best undress ai for free without sing up : 👉 Deepnude
4- surprise For an iPhone at a surprising price : https://securecd-smrtnd.com/s?a=256440&sm=46517&co=316585&mt=21
No cost: Completely free with no hidden charges.

👉🔴 Get Free undress ai >>
👉🔴 Get Free undress ai >>
👉🔴 Get Free undress ai >>
Accessibility: Available on various platforms. Advanced results: Crisp and accurate outputs. Why Choose DeepNude AI? https://frestr20.blogspot.com/ Trusted worldwide for its efficiency, DeepNude AI combines simplicity with reliability, making it an ideal choice for users seeking fast, effective AI solutions
withount sing up : 👍
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE
➤ ➤ DeepNude FREE

DeepNude AI offers advanced tools for generating high-quality AI-powered imagery. With features like precision, ease of use, and seamless integration, it caters to beginners and professionals alike. Users can enjoy: https://deepnudefree.online/
👉 Deepnude Free + Without Sing Up
OR : 👉 Deepnude Free + Without Sing Up
OR 👍👉🔴 Click HERE >>
3- Best undress ai for free without sing up : 👉 Deepnude
4- surprise For an iPhone at a surprising price : https://securecd-smrtnd.com/s?a=256440&sm=46517&co=316585&mt=21
No cost: Completely free with no hidden charges.
👉🔴 Get Free undress ai >>
👉🔴 Get Free undress ai >>
👉🔴 Get Free undress ai >>


add preferGlobal field

A yeoman generator is supposed to be installed globally.
So by setting preferGlobal: true will make the installation instruction
on npmjs.com matches that intention.
it'll be written as npm install -g generator-nm
instead of npm install generator-nm

Nah. I stopped using it as it shows a warning if you install it locally, which is totally valid. Maybe if npm removed the warning output.

@sindresorhus npm v5.1 no longer warns about preferGlobal:

57225d394 #17120 npm will no longer warn about preferGlobal, and the option is now deprecated.


add built-in config for standalone compile-to-css files

Allows users to just start coding styles in standalone files with the appropriate extension once they install the appropriate loaders and their peer dependencies, similar to how style elements currently work in .vue components.

@yyx990803 Resolves #33.

Shouldn't these be extracted in production build too? I think these two should reuse the same dev/prod settings.

Yeah, probably. I only use external files for branding variables that are imported into style elements in .vue components. I'll update.

@Grafikart beat you to it in #84 - sorry Chris ;)

That's fantastic! I'll never complain when someone does work so I don't have to. 😄


perf_rollup_queue fails on archived pod

Log has "ContainerGroup#my_zone delegated to ext_management_system.my_zone, but ext_management_system is nil" messages e.g.:
[----] E, [2017-02-13T14:00:27.312317 #2654:114714c] ERROR -- : [Module::DelegationError]: ContainerGroup#my_zone delegated to ext_management_system.my_zone, but ext_management_system is nil: #<ManageIQ::Providers::Kubernetes::ContainerManager::ContainerGroup id:<PHONE_NUMBER>0321, ems_ref: "b6bf6582-f1ea-11e6-9d5a-54ee759b98ac", name: "manageiq-img-scan-b0cf2", ems_created_on: "2017-02-13 12:48:27", resource_version: "149740", restart_policy: "Never", dns_policy: "ClusterFirst", ems_id: nil, container_node_id: nil, last_perf_capture_on: "2017-02-13 12:50:20", container_replicator_id: nil, ipaddress: "<IP_ADDRESS>", type: "ManageIQ::Providers::Kubernetes::ContainerManager:...", container_project_id: nil, phase: "Running", message: nil, reason: nil, container_build_pod_id: nil, created_on: "2017-02-13 12:49:06", deleted_on: "2017-02-13 12:55:19", old_ems_id:<PHONE_NUMBER>0028, old_container_project_id:<PHONE_NUMBER>0027>  Method:[rescue in deliver]
[----] E, [2017-02-13T14:00:27.312568 #2654:114714c] ERROR -- : /var/www/miq/vmdb/app/models/container_group.rb:36:in `rescue in my_zone'
/var/www/miq/vmdb/app/models/container_group.rb:36:in `my_zone'
/var/www/miq/vmdb/app/models/metric/ci_mixin/rollup.rb:62:in `perf_rollup_queue'
/var/www/miq/vmdb/app/models/metric/ci_mixin/rollup.rb:30:in `block (3 levels) in perf_rollup_to_parents'
...

Saw it several times on manageiq-img-scan, not sure if significant.
The pod is archived — has deleted_on, no ems_id but has old_ems_id.
See also byebug with fuller stack trace: https://gist.github.com/cben/7f8507c5e91a49878e3cdbfdbf4c17eb
@zeari @yaacov @simon3z Should perf_rollup run on archived pods?  If yes, it should use old_ems_id.  Either way sounds like a bug...
@miq-bot add-labels providers/containers, bug

see: https://github.com/ManageIQ/manageiq/pull/13686

Is this fixed with #13686 ?

@zeari ^^^ was this a dup of the BZ you fixed?

@cben @chessbyte yep we can close this.


Eagerly evaluate require/use for immediate completion

Often I add a require form to a segment and wish to complete symbols from its namespace in the very next form. Currently I have to evaluate the segment and refocus it to do so. Would there be any downsides to evaluating new requires when the completion is activated?

One of my principles with Gorilla has been to keep it as simple and unsurprising as possible. I think that this behaviour, although it could save some typing, might be a bit surprising to users, so I'd not favour adding it.


Update modern-desktop-deployment-and-management-lab.md

Fixed missing word in system recomendations

@cdmm12  Can I merge this?

@JGruszczyk - can you review and merge?


Feature/ Remove calls to add and remove members endpoints from v2 client

this pr contains changes related to
https://github.com/openreview/openreview-api/pull/495
and
https://github.com/openreview/openreview-web/pull/2028
to remove call to add/remove members endpoints because they are removed in https://github.com/openreview/openreview-api/pull/495

yes, I can take a look.


Consents: Remove old terms from code

This fixes #2293.

@elichad Ready for your review! This is a pretty big PR, I don't really know what could help you dig into it easily. I tried to follow the checklist in https://github.com/carpentries/amy/issues/2293 but in some cases I had to come up with custom solutions, or sometimes I did things in a different order.
Let me know if I can help you with this PR somehow.


Error: Input buffer has corrupt header: glib

Description
Getting an error every second time that I run gridsome develop:
Steps to reproduce
Not sure if anyone else has this issue but, include an svg file via the g-image component eg. <g-image src="~/assets/images/loader.svg" alt="loading"></g-image>
Expected result
dev should startup every time without throwing error
Actual result
ERROR in ./src/assets/images/loader.svg (./gridsome/lib/webpack/loaders/assets-loader.js?alt=loading!./src/assets/images/loader.svg) Module build failed (from ./gridsome/lib/webpack/loaders/assets-loader.js): Error: Input buffer has corrupt header: glib: Error domain 1 code 65 on line 1 column 306 of data: attributes construct error
Environment

Libs:
- gridsome version: 0.6.4
- @gridsome/cli version: 0.6.4

Issue was an unsupported character within the svg file itself.


Vulnerability in nested underscore dependency

Today I just started seeing this:
npm audit report
underscore  1.3.2 - 1.12.0
Severity: high
Arbitrary Code Execution - https://npmjs.com/advisories/1674
No fix available
node_modules/underscore
country-language  *
Depends on vulnerable versions of underscore
node_modules/country-language
@ladjs/i18n  *
Depends on vulnerable versions of country-language
Depends on vulnerable versions of i18n-locales
node_modules/@ladjs/i18n
i18n-locales  >=0.0.3
Depends on vulnerable versions of country-language
node_modules/i18n-locales
A dependency update would be greatly appreciated.

Done!  THANK YOU!  download v7.2.0 to use!
https://github.com/ladjs/i18n/releases/tag/v7.2.0

Thank you for the update, but I still get the following:
npm audit report
underscore  1.3.2 - 1.12.0
Severity: high
Arbitrary Code Execution - https://npmjs.com/advisories/1674
No fix available
node_modules/underscore
country-language  *
Depends on vulnerable versions of underscore
node_modules/country-language
@ladjs/i18n  *
Depends on vulnerable versions of country-language
node_modules/@ladjs/i18n

Oh derp, my bad I forgot to fix it in this package (not just in i18n-locales)
Sec!

OK https://github.com/ladjs/i18n/releases/tag/v7.2.1 v7.2.1 should be good to go!

Thanx!


Npm module which is having dependencies not working

I got error when using npm module which is having module dependencies. For example:

the Error message is like "stream is not defined" btw stream is a npm module dependencies inside NPM DDP module, so the error will be gone if I just simply "npm install stream". But there will be another error because the dependencies issues like this. And I think installing one by one is not good solution though.

Could you please post the output of npm ls?
Mine looks like this:
$ npm ls
@ /home/jeick/git/tabris-js/examples/animation
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └─┬<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └─┬<EMAIL_ADDRESS>│   │   ├──<EMAIL_ADDRESS>│   │   ├──<EMAIL_ADDRESS>│   │   ├──<EMAIL_ADDRESS>│   │   └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

Hello @jonek , thanks for the response
btw I am also successful if the case just installing npm module. But the error was not it.

After add "ddp" to package and doing "npm install", it was successfully installed

<EMAIL_ADDRESS>node_modules/ddp
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS>
But when I am running this simple code to subscribe data from server

var page = tabris.create("Page", {
    title: "piyiku",
    topLevel: true
});

tabris.create("TextView", {
    alignment: "center",
    text: "Hello"
}).appendTo(page);

var DDPClient = require("ddp");

var ddpclient = new DDPClient({
    // All properties optional, defaults shown
    host: "localhost",
    port: 3000,
    ssl: false,
    autoReconnect: true,
    autoReconnectTimer: 500,
    maintainCollections: true,
    ddpVersion: '1', // ['1', 'pre2', 'pre1'] available
    // uses the SockJs protocol to create the connection
    // this still uses websockets, but allows to get the benefits
    // from projects like meteorhacks:cluster
    // (for load balancing and service discovery)
    // do not use `path` option when you are using useSockJs
    useSockJs: true,
    // Use a full url instead of a set of `host`, `port` and `ssl`
    // do not set `useSockJs` option if `url` is used
    url: 'wss://example.com/websocket'
});

/*
 * Subscribe to a Meteor Collection
 */
ddpclient.subscribe(
        'news', // name of Meteor Publish function to subscribe to
        [], // any parameters used by the Publish function
        function() {             // callback when the subscription is complete
            console.log('posts complete:');
            console.log(ddpclient.collections.news);
        }
);

it said error module "util not found", but I have fixed it using this https://github.com/eclipsesource/tabris-js/issues/244.

After adding "require("tabris-js-node");" on top of my code to remove "util" error. There was another error caused by node_modules inside ddp node_modules (dependencies). The error message was "Could not load main module: Error: Cannot find module 'events'".

The error will be gone too, if I just manually install "npm install events", but I think that's not solution, and make thing worst. Any idea about this?

Thanks

btw here my "npm ls" as you requested, I think it just the same with yours
├─┬<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├──<EMAIL_ADDRESS>│ ├─┬<EMAIL_ADDRESS>│ │ └─┬<EMAIL_ADDRESS>│ │   └──<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └─┬<EMAIL_ADDRESS>│   │   ├──<EMAIL_ADDRESS>│   │   ├──<EMAIL_ADDRESS>│   │   ├──<EMAIL_ADDRESS>│   │   └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ ├──<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   ├──<EMAIL_ADDRESS>│   └──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>extraneous

events is a built-in node module, just like util. This module is not yet available for Tabris.js.

Closing this issue as it's not a general problem with the module system. The support for the ddp module is tracked by #467.

@ralfstx thanks I'll wait


Transformed Static Title to the Title of the Project.

issue addressed: #90

How?

Used the document.title field to set up the title, it changes back to the env title's value once you click the Ayushma Logo, that was also taken care of.

-Supporting Images.

Possible enhancements.
We can use NextJS 13's new metadata API.

Update Chanelog:
Update: Changed the traditional implementation to use a package called react-helmet.
Plus Points: Eases the declaration of meta-tags and lets us use them in the client component :) , one can write a dynamic description tag pretty easily as well.

@yogeshbhutkar I don't think we need react helmet. document.title should do our bidding.


CI: Fix "error: externally-managed-environment" in CSI

What this PR does / why we need it:
PR #2414 missed fixing this for Cinder and Manila e2e tests, this makes sure these tests work too.
Which issue this PR fixes(if applicable):
fixes #2412
Special notes for reviewers:

Release note:

NONE

/approve
/lgtm

/cherry-pick release-1.26
/cherry-pick release-1.27
/cherry-pick release-1.28

/cherry-pick release-1.27

/cherry-pick release-1.28


Travis: Update Ruby versions in CI matrix

This PR updates Ruby versions to latest releases in their series.

jruby-1.7.27
2.2.7
2.3.4
wrap rake ci in bundle exec

Perhaps we could let go of 2.1?

The current JRuby 1.7 build failure is about http_form's required_ruby_version in its .gemspec which does not preclude 1.9 Rubies from automatically using it.
It'd be nice if that gem had such metadata in its .gemspec.

JRuby 1.7 is EOL'd, would it be more beneficial in the long run to hop over to JRuby <IP_ADDRESS>?

@olleolleolle I'm sorry about that. Will fix form_data asap

@olleolleolle Can you please re-run tests. v1.0.3 of form data now fixed to play nice with jruby 1.7 and ruby 1.9+

@ixti That fixed things here! Yes!
:hearts: :yellow_heart: :green_heart: :blue_heart: :purple_heart:

@digitalextremist Is there anything more you'd like from this PR? Or, any change you'd like to see done to it?

thank you - i think this is great as a specific PR, and i'm curious as to your thoughts about my other comments and what i've done to CI and deps in my own PR. i would be happy to revert/rebase from this!
.travis.yml
Gemfile
reel.gemspec

@tarcieri I'm ready for code review on this one, now.

@kenichi Oh, there we are, merged and good to go. Thank you for all of the input, it made this a lot better. Better is better!


NEW CONTROL - Adaptive Card Host

Hello,
I've been working with Adaptive Cards, I really like the new ACE model and in general I like the fact that I can describe the UI of a Web Part in a declarative way and be able to change it at runtime, like a configuration.
After some tests on this, I created a React control that allows you to render an Adaptive Card as a component, also using the templating part and the ability to invoke commands defined using the "Action.Execute" model.
I would like to make it a control of this library, what do you think?

Hi @fabiofranzini , that would be a great addition in my opinion. I was actually discussing this with @joaojmendes a few days ago as he was considering a similar control. Perhaps we could use this thread as a starting point to avoid duplication of effort and duplicated PRs?
Are you both able to describe your approach so we could all brainstorm the best way to move this forward and hopefully benefit from both solutions?

Hi @joelfmrodrigues,
in recent days I chatted with @joaojmendes about this thing, we can join forces and bring the best of our solutions.
The idea is to have a control that can host Adaptive Cards in both Web Parts and Application Customizer, so that they can be used as a UI.
Also, as I have already implemented in some examples, we could extend the Adaptive Cards 'standard' set of controls with Fluent UI controls or as suggested by @joaojmendes with Microsoft Graph Toolkit controls.
@joaojmendes , we need to set up a call to discuss this :)

Hi @AJIXuMuK, yes and thanks for the suggestion! The purpose is to create a reusable control and extend the common set of controls that come from Adaptive Cards.

Hi, all,
I think that we can accept the control of @fabiofranzini and the new improvements will be implemented on that .
Thanks
João
From: Fabio Franzini @.>
Date: Tuesday, 18 January 2022 at 16:24
To: pnp/sp-dev-fx-controls-react @.>
Cc: João Mendes @.>, Mention @.>
Subject: Re: [pnp/sp-dev-fx-controls-react] NEW CONTROL - Adaptive Card Host (Issue #1096)
Hi @AJIXuMuKhttps://github.com/AJIXuMuK, yes and thanks for the suggestion! The purpose is to create a reusable control and extend the common set of controls that come from Adaptive Cards.
—
Reply to this email directly, view it on GitHubhttps://github.com/pnp/sp-dev-fx-controls-react/issues/1096#issuecomment-1015577984, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC7YHVP6HWRVMCJMS5TOYE3UWWH2BANCNFSM5MFGDKJQ.
You are receiving this because you were mentioned.Message ID: @.***>

Tomorrow I and @joaojmendes will synchronize and let's see how to collaborate on this component 👍


fix: use upstream go-git. Fixes #10091

Fixes #10091
Motivation
go-git is back to maintenance and active for a couple of months already so we should contribute any changes back to upstream and switch back to upstream go-git: go-git/go-git
Modifications
Replace our own fork with upstream go-git

Verification
CI Tests

I wasn't able to dedicate a lot of time to this due to work commitments.
I will provide an update on this over the weekend. If I find that I cannot work on this, I will also communicate that in my update.

It seems like I can find some time this week to fix this.

Closing in favor of https://github.com/argoproj/argo-workflows/pull/11149

Superseded by #12515


datadog: HTTP client portion of new tracing library

This is part of the initiative described in https://github.com/envoyproxy/envoy/pull/23958.
This revision adds a component that will be used in the future when more of the new library is integrated into the Datadog tracing extension.
AgentHTTPClient allows the new tracing library to send spans to the Datadog Agent by making HTTP POST requests to a configured cluster. AgentHTTPClient implements the datadog::tracing::HTTPClient interface and the Envoy::Http::AsyncClient::Callbacks interface.

/assign

Thanks for the review. I'll commit some changes within the next couple of days.

/retest

Code coverage for source/extensions/tracers/datadog is lower than limit of 96.6 (96.5)

hmmmm

Ping @wbpcode


document search after

Description
fix #4077
I'm not sure what to add more than that line.
somewhat unrelated, document possible improvements to the partial_request_cache, that apply particularly to search_after

Can you add an example?

Approved, can you just take into account my minor comments?


Lora-server unknow problem

loraserver[981]: time="2019-05-29T15:33:19+08:00" level=error msg="finished unary call with code Unknown" error="rpc error: code = Unknown desc = lorawan/band: invalid data-rate" grpc.code=Unknown grpc.method=SendProprietaryPayload grpc.service=ns.NetworkServerService grpc.start_time="2019-05-29T15:33:19+08:00" grpc.time_ms=0.033 peer.address="<IP_ADDRESS>:56964" span.kind=server system=grpc
i run into this problem and i can't get reply  from the server to the end node?
this error show often but i manage to sent and receiving data to loraserver

Please see: https://forum.loraserver.io/search?q=invalid data-rate.


Add cupy.einsum_path

Part of #6078.
For the previous discussion about the einsum_path refactoring, please see #6261 and #6677.
This PR adds the missing cupy.einsum_path function for NumPy compatibility. In order to avoid the infinite __array_function__ dispatching, I followed the advice from upstream (see https://github.com/numpy/numpy/issues/21379) and created dummy NumPy arrays (of zero size) to reuse numpy.einsum_path(). The path computation only cares about the array dimension and shape; actual data, memory layout, or dtype are irrelevant.
cuTensorNet support will be added in a separate PR.
Question for the team: Should I also remove all related code copied from NumPy (specifically, cupy/linalg/_einsum_opt.py) as part of this PR, since they are redundant now?

Interesting, Dask already follows the same approach:
https://github.com/dask/dask/blob/cccb9d8d8e33a891396b1275c2448c352ef40c27/dask/array/einsumfuncs.py#L219

Question for the team: Should I also remove all related code copied from NumPy (specifically, cupy/linalg/_einsum_opt.py) as part of this PR, since they are redundant now?

I think it's safe to remove it, do you have any comments @toslunar?

Calling numpy.einsum_path can eliminate the copied code (cupy/linalg/_einsum_opt.py).
My concern is about the performance. cupy.einsum will have to parse args twice, while numpy.einsum parses them only once by using hidden einsum_call=True option of numpy.einsum_path. In my opinion,

Keeping the copied code is better than using NumPy's hidden option because the latter may break suddenly.
Calling public numpy.einsum_path seems a tradeoff between cleanness and speed.  It's great if the performance drop is minor.

Thanks guys! I'll do some quick checks for the potential perf hit, but for now I'm thinking two ways out:

Use the hidden einsum_call option: It's been there since einsum_path was added (2015) and for the same reason (don't parse twice) I don't think NumPy would ever consider removing it. AFAIK the NumPy einsum related code has been stable for quite some time.
Refactor einsum such that internally we let NumPy do input verification by delegating to numpy.einsum_path (and also get a path back if succeeds): I think this is feasible and has the additional benefit that we will always generate the same errors, but I need to experiment it a bit after I do the perf check.

I did some quick checks on the overhead of double parsing and it's a bit large (50-80us). The way I checked is to simply replace this block by einsum_path, so it's arguably not the most optimal approach.
However, what's concerning is before arriving this block, CuPy did several simplifications that mutate the inputs, which makes reusing einsum_path very challenging. As a result I'd suggest we defer the refactoring to later, and focus on making this API available. WDYT @toslunar?

However, what's concerning is before arriving this block, CuPy did several simplifications that mutate the inputs, which makes reusing einsum_path very challenging. As a result I'd suggest we defer the refactoring to later, and focus on making this API available. WDYT @toslunar?

I'd like to postpone the refactoring, too.  It looks OK to me to make cupy.einsum_path return the same result as numpy.einsum_path does.
An issue already CuPy has is that a path computed by cupy.einsum is sometimes different than NumPy's.  (For example, the simplifications you mentioned include internal trace, therefore cupy.einsum does not reproduce the bug numpy/numpy#20962.)  It's not a big issue, but it might be going to be more visible from users in the sense that
path = cupy.einsum_path(*operands, optimize=True)[0]
cupy.einsum(*operands, optimize=path)

is different than
cupy.einsum(*operands, optimize=True)

After the PR is merged, I'm willing to make these code equivalent by sharing some implementations between cupy.einsum and cupy.einsum_path, which is a kind of opposite of eliminating _einsum_opt.py.

@toslunar Hmmm... good point... I am concerned now, because it means this branch
https://github.com/cupy/cupy/blob/292bb3c80d6631b429bb6adfdf434ec718e4920d/cupy/linalg/_einsum.py#L646-L647
is already technically incorrect (irrelevant of the present PR). The user-provided path must be mutated accordingly before it can be used in the pairwise contraction loop below, isn't it?

Technically yes.  It seems similar to the question "should cupy.einsum support genuine optimize=False einsum?"
cupy.einsum's actual path is a subdivision of the given path (if we ignore the execution order of unary ops and binary ops). In other words, cupy follows users' intention and may optimize further.  For the Qij,Qkk->ij example, the (unique) path [(0, 1)] is interpreted like [(1,), (0, 1)].
Drawbacks of this further optimization are

extra memory, which is as small as the order of inputs, outputs, or intermediate results in the original path
accuracy or reproducibility, for example

>>> for xp in [numpy, cupy]: xp.einsum('i,j->', xp.array([1e308, 1e308]), xp.array([1e-8, 1e-9]))
2.2e+300
array(inf)

Let me close this one as I don't have time to address the challenges discussed above.


No Longer works with Leaflet 1.0

Any idea how to make it work with leaflet 1.0?

I've already created an updated version if you wanted me to upload.

If you make a pull request I can merge
Jeremy Fergason
Sent from
https://polymail.io/
On Mon, Mar 13, 2017 at 10:31 AM revivedtitan
<
mailto:revivedtitan<EMAIL_ADDRESS>
wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }
I've already created an updated version if you wanted me to upload.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly,
https://github.com/jdfergason/Leaflet.Ellipse/issues/5#issuecomment-286182319
, or
https://github.com/notifications/unsubscribe-auth/AAtmZSrWTzG05JpmUyCWlB-6bRvaDiKWks5rlX14gaJpZM4MJT68
.

Sounds good, I'll do that this afternoon after work

Any progress?
Thanks.

I've created the pull request, just waiting for jdfergason to review and complete the merge/addition.

Pull request closed and updated to 1.0


[BEAM-2939, BEAM-10057][release-2.22.0] Ensure that we can process an EmptyUnboundedSource and also prevent splitting on it.

Looks like the only failure in Java PreCommit was VideoIntelligenceIT. A known flake fixed on master BEAM-10050. I'll go ahead and merge.


P4RT-3.2 PacketOut

Hi @hariramnat ,This is PR for P4RT-3.2 PacketIn for GDP #74 . For the P4RT client library, it will be moved to a new location later. Also it's using the wbb wrapper code which is still in PR and we will update this PR after wbb PR is in main.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1314

Relevant Lines:
1841

💛  - Coveralls

LGTM.

Thanks @hariramnat for helping review it. @dplore and @hariramnat could you please help get another one to review as well? the process requires 2 approvals.

Hi @sezhang2 , I don't have permission to trigger gcbrun or merge the PR. Could you please help on that?

/gcbrun


Fresnel - making API more consistent with existing code?

attn @douglase @kuravih
I'm trying to work through some more of the details of this, in part while sorting out how to handle image planes better. Here is a minor API detail, which led me to think about some larger goals.
Right now the distance between optics seems to need to be in 2 different places. In the Hubble example:
# Propagate to secondary
gw.propagate_fresnel(d_pri_sec, display_intermed=False)

#apply secondary
gw.apply_optic(g2,d_pri_sec)

The d_pri_sec term shows up in both. Why? In propagate_fresnel, that makes sense, that's how far to propagate. In apply_optic, it's used to calculate the beam radius at that position. But couldn't it also get that information from the .z attribute of the wavefront object?
I guess right now I don't totally understand the mix of what's happening in apply_optic versus the propagation. In the original Fraunhofer regime code, there is a clear line between propagation and interaction with optics, such that a given optic can be applied to a wavefront without need for considering the details of what came before. The wavefront object alone contains all the info the optic needed to access.  It seems like that should also be feasible here, that we can keep enough state with the fresnel.Wavefront such that it can be accessed by any optics.  Or am I missing something?
Here is some hand-wavy mock code we could work towards?
FS = FresnelOpticalSystem(diam=2.4)
FS.addOptic(hubble_primary)
FS.addOptic(hubble_secondary, distance=d_pri_sec)
FS.addDetector(pixelscale=whatever, distance=d_sec_to_focus)
fresnelPSF = FS.calcPSF(args)

Then inside the Fresnel version of calcPSF, instead of the current code that does
        for optic in self.planes:
            wavefront.propagateTo(optic)
            wavefront *= optic
            current_plane_index += 1

instead we would have something like:
        for optic, distance in zip(self.planes, self.distances):
            wavefront.propagate(distance)
            wavefront *= optic
            current_plane_index += 1

Does that make sense? I'm trying to think whether we can make the Fresnel code have as user-friendly an interface as possible modeled on the Fraunhofer code.

I think this makes sense, the other scenario I can think of would be someone wanting to just do Gaussian laser beam optics to find the waist at each optic, and they might not care to take the processing time to propagate the wavefront through.
But in that case this same loop could work, except we add an ignore_wavefront flag as there is in  apply_optic() to the propagate_fresnel().

At this point I have the FresnelOpticalSystem infrastructure pretty much working in my local repository, with an API close to the mock code above (but not exactly).
Still TBD is carefully sorting through the issue #104 stuff, and getting the image plane coordinates conversion working. For the latter I think I'm going to add some infrastructure to Wavefront to track focal length and f ratio of the beam, which will enable automatic support for pupil coordinates in angular units as well as meters.

I have just pushed a very substantial set of changes to the Fresnel branch. These implement the FresnelOpticalSystem, including support for image planes.  As part of this there has also been some refactoring of the API to bring it more consistent with the rest of poppy.   This probably breaks essentially all existing code using the Fresnel parts - apologies for that, but better sooner than later to restructure the API.  After the change it's all very closely consistent to the regular OpticalSystem API.
Specifically:

renaming of fresnel.Wavefront to FresnelWavefront, various propagation routines to e.g. _propagate_wts and so forth
apply_optic is now apply_lens_power and the call signature changed. There is no need to pass in a distance z since the FresnelWavefront keeps track of its own location.
in any case you don't need to call apply_optic manually since it can now be applied just by multiplying by the object, like any other OpticalElement
FresnelOpticalSystem provides a high level container for a series of elements, with a consistent API and outputs as regular OpticalSystem

There is now a new notebook in the Notebooks directory that demonstrates all of this. See https://github.com/mperrin/poppy/blob/fresnel/notebooks/Fresnel_Propagation_Demo.ipynb
There's also a bunch of new unit tests including the Hubble example worked pretty thoroughly.
Some caveats:

Detector classes not yet supported in FresnelOpticalSystem; you can get PSFs out just fine, but on the pixel sampling defined by the FFT. This is probably the next thing to add.
the force_fresnel parameter was removed, since now FresnelWavefront does always propagate via Fresnel and does not attempt to fall back to Fraunhofer. Mixed propagation like that wasn't workable in practice with the revised infrastructure, and in any case the support for image planes in the regular Fresnel propagation is a better way of handling them than switching propagation types midstream. That was just too confusing. (and I can't think of a compelling use case for this)
The new API is pretty clean; general users can just use poppy.FresnelOpticalSystem and add elements to that, and everything is handled automatically in terms of getting a FresnelWavefront instead of regular Wavefront, and converting plane types and so forth. But the price to pay for cleaner code in the future is having to change a bunch of stuff now. Apologies again.
There's almost certainly still some rough edges in places. Let me know what breaks. And suggestions for further tweaks are much welcomed.

I'm away on vacation next week but will be checking email at least one a day. I wanted to push what I've managed to get done sooner rather than later. Let me know what you think...

Nice notebook! Should we open a PR from mperrin/poppy@fresnel? Then we can comment on the code as well.

Fresnel PR has been merged to master.


Contribution to "Exposure of sensitive information in follow-redirects"

Updates

Affected products

Advisory is wrong - patched version is 1.14.8:
https://github.com/follow-redirects/follow-redirects/compare/v1.14.7...main


Allow passing table parameter to GPTSQLStructStoreIndex

PR to address: https://github.com/jerryjliu/gpt_index/issues/203
Core issue:  In SQLAlchemy MetaData(bind=self._engine).reflect() only returns metadata for tables, not views.
However, it is still possible to get view metadata explicitly with
my_view = Table('some_view', MetaData(bind=engine), autoload=True)

See https://docs.sqlalchemy.org/en/14/core/reflection.html#reflecting-views for details
Amongst the suggestions in that documentation is that for views you may want to specific additional context, such as hints on primary and foreign keys:
my_view = Table(
    "some_view",
    metadata,
    Column("view_id", Integer, primary_key=True),
    Column("related_thing", Integer, ForeignKey("othertable.thing_id")),
    autoload_with=engine,
)

So we have one possible option of simply replacing
table = self.sql_database.metadata_obj.tables[table_name]

with
table = Table(tablename, autolad_with=engine)

However the issue with that is that it doesn't allow us to easily specify those primary and foreign key constraints easily. (*)
Which leads to the approach taken here: allow the creator of the GPTSQLStructStoreIndex to pass the table structure in instead of the table_name.
(*) That said there is a general case performance improvement that we could make by doing this in favor of the full metadata_obj.reflect() that currently exists in the SQLDatabase object.  We only need metadata for the one table, and the full reflect() will do the entire schema.  This is outside the scope of what this PR is trying to achieve, so is not included.

To test:
# This fails with a KeyError trying to lookup `metadata.tables['my_view']`
index = GPTSQLStructStoreIndex(
    documents=[],
    sql_engine=engine,
    table_name='my_view',
)

# This succeeds and produces a usable index
index = GPTSQLStructStoreIndex(
    documents=[],
    sql_engine=engine,
    table= Table('my_view', MetaData(bind=engine), autoload=True)
)

this is amazing! will get to this tonight

There is a lint failure here.  I think resulting from:
        table: Optional[Table] = None,
...
        self.table_name = table_name or table.name

Which could result in us trying to get table.name of None, that would of course fail.
In practice... not super likely
        if table_name is None and table is None:
            raise ValueError("table_name must be specified")
        self.table_name = table_name or table.name

Should ensure that if table_name is present we'll use that, if it's not present then we would have already errored with the ValueError.
But its still theoretically valid if table_name == '', 0, or some other falsey but not None value.

There is a lint failure here. I think resulting from:
        table: Optional[Table] = None,
...
        self.table_name = table_name or table.name

Which could result in us trying to get table.name of None, that would of course fail.
In practice... not super likely
        if table_name is None and table is None:
            raise ValueError("table_name must be specified")
        self.table_name = table_name or table.name

Should ensure that if table_name is present we'll use that, if it's not present then we would have already errored with the ValueError.
But its still theoretically valid if table_name == '', 0, or some other falsey but not None value.

a cast should work - i can help with that, one sec


[Feature Request] Add support for changing the preset

A lot of .sf2 files support changing the instruments and/or presets. Would be nice if there was a way to change the preset besides the default one in this library.

Changing instrument feature added now. When I find a way to edit the midi channel in iOS, I will add it.


Load events

Added code to load and add R^2 for each electrode in electrode table.

@bendichter think this is ready to be merged.


get-instance-view should accept quoted string for ids

this works: az vm get-instance-view --ids id1 id2
but not this: az vm get-instance-view --ids "id1 id2"
It would be helpful if it accepts quoted string. For example, this fails:
az vm list --query "join(' ',[*].id)" | xargs -I {} -P 8 az vm get-instance-view --ids {}
or is there a way for me to make jmespath give me unquoted string ? The jp has Unquoted Output : https://github.com/jmespath/jp , but azure-cli jmespath query cant do unquoted output.

The quoted/unquoted output depends on the output formatter. If you are using json as the output, then it will be quoted (in order to be well formed json). You can use --out tsv to get unquoted "raw" tab separated output.
Does that address your immediate problem?
That said, arguments have been made that we should support space separated values for the --ids parameter specifically since that would allow the use of piping similar to:
az vm list --query "[].id" --out tsv | az vm get-instance-view --ids @-

using the -o tsv does resolve the quote issue. But for some reason the pipe-lining does not seem to work.
even with your example : az vm list --query "[].id" --out tsv | az vm get-instance-view --ids @-
or with my originial one with -o tsv : az vm list --query "join(' ',[*].id)" -o tsv | xargs -I {} -P 8 az vm get-instance-view --ids {}

Hi @ashokez the reason @- is not working in this instance is because the @ syntax takes the supplied file (stdout for -) and reads its contents into a string. Thus you are getting the space separated list of IDs, but they are then being interpreted as a single string argument. The best example for the use of @ currently is with commands that accept JSON encoded strings. Typing these on the command line is painful, but using @ you can just point to a JSON file and everything will work.
We have an open issue #944 to have an alternate syntax for treating a file as a list. This would enable your scenario.

Cleaning u old issues, reopen if this is still active.


json instead of markdown?

Hi. Thanks a lot for this nice plugin!
Is it possible to store my data into json files instead of markdown files in the /src/ directory?

@justfunk should not be a problem.
Metalsmith reads all files in the directory.
As for this plugin, you can set the pattern to only read from json
pattern: **/*.json
Contents of the file will still be in the content prop.

@justfunk
Closing this. Please reopen if needed.
Thanks!

Hi @yeojz , I'm also want to use json instead of markdown for the data I'll pass into the React template, when I've added a json file although it is being read and used it's just interpreted as one big string. Is there something I need to do so that it's being treated as a proper json object?
Thanks

@ablackledge you'll probably need to use JSON.parse() on the value.

Oh damn sorry, so simple should have come to that conclusion myself! 😳
Thanks for the quick reply


[add-resource] New Plugin

I would like to add my new plugin '"TecArt Session Login"' to the Grav Repository.
Here are the project details: repository on github.com
I am looking forward to get feedback!

Added to GPM for next update


Add disjunctive facet search

disjunctiveFacetSearch changes how we handle multiple facet filters.  See this spec to understand.
To understand better the following explanation, lets consider that we have two facets fields:

color

red
blue

genres

drama
action

Current behavior
When performing a search requiring that color is red and genres is drama, instant-meilisearch is going to perform ONE search requests with the following filters:
Only search request:
[["genres=drama"], ["color=red"]]

Unfortunately, this is not the expected behavior when using facets on most websites.
Disjunctive facet search
Using disjunctive facet search, we make as many requests as their are different facets filters.
For example, in our case above, we should have made 3 requests.
Search requests:
first request
[["genres:Adventure"], ["color:red"]],

Second request:
[["color:red"]],

Third request:
[["genres:Adventure"]],

The good news is that instantsearch provides us with the required requests. For example, if we ask for color blue and genres Adventure on a movie index, instantsearch provides us with the following objects:
( objects were reduced for readability )
[
  {
    "indexName": "movies",
    "params": {
      "facetFilters": [["genres:Adventure"], ["color:blue"]],
      "facets": ["genres","color"],
      "maxValuesPerFacet": 10,
      "query": "",
      "tagFilters": ""
    }
  },
  {
    "indexName": "movies",
    "params": {
      "facetFilters": [["color:blue"]],
      "facets": "genres",
      "hitsPerPage": 0,
      "maxValuesPerFacet": 10,
      "page": 0,
      "query": ""
    }
  },
  {
    "indexName": "movies",
    "params": {
      "facetFilters": [["genres:Adventure"]],
      "facets": "color",
      "hitsPerPage": 0,
      "maxValuesPerFacet": 10,
      "page": 0,
      "query": ""
    }
  },
]

We can then make a search request per element provided by instantsearch. Some elements are important to take into account:

The first request is the default one, lets call it the hits request. It returns the hits and uses all the facet filters.
The following requests, lets call them the facets requests are only used to provide the number of documents available for each facet
The facets requests provide us with important field that must overide the current instantsearch context:

hitsPerPage is either 0 or 1 depending on the instantsearch plugin used. See corner cases
Page is always 0
The field facets is provided helping us knowing that this is a facets requests and not the hits request

Corner cases

When using disjunctive facet search with a multi index search, all indexes must have the facets added to their filterableAttributes.
disjunctive facet search is only used when the operator of refinementList is or
Depending on the instantsearch environment the hitsPerPage value can be different when performing a facets request. For example in 'react-instantsearch-hooks-web' hitsPerPage is 0, but in react-instantsearch-dom hitsPerPage is 1

I am not sure if the issue I am having is related to this, but for me a weird thing is that I am setting up my project exactly like the code in this example:
https://codesandbox.io/s/ms-is-mese9?fontsize=14&hidenavigation=1&theme=dark&file=/index.html:952-1057
But for me, disjunctive facetting does not work at all. When I select a facet, it filters correctly, but then removes all other options (which do have a hit count also), as if it were a non disjunctive facet. I can not figure out why the same code does not behave like in the example above.
Am I missing something in configuring the index maybe? Should a facet that is used with disjunctive always be stored as an array in the index f.e.?

Hey @engel-m, are you using the current release of instant-meilisearch or this branch ? #888

@bidoubiwa Update on this:
I have the problem with both branches.
I found out I was not able to get disjunctive facets to work because I had not configured keepZeroFacets to be set to true.
If I do, I can select multiple options for a facet without the rest disappearing. This would mean that when selecting a facet value, the result count of the other selectable values goes to zero.

Could you show me your configuration? keepZeroFacets is not working currently with multi-index/disjunctive facet search. I'm working on fixing that issue.

@bidoubiwa I tried every possible configuration combination there is, but with the exception of keepZeroFacets set to true and operator or , I can not even select multiple values for a facet. Once refined, the rest disappears.
Basically, I have the same problem as in this issue:
https://github.com/meilisearch/instant-meilisearch/issues/789
But when I install your #888 branch it doesn't change anything for me.

Sorry, I may not have been clear. keepZeroFacets=true does not work currently on the multi-index search.
See the todo at the end of the body of the PR https://github.com/meilisearch/instant-meilisearch/pull/888
I'm working on the fix :)

It is released on npm :) Here

Is there a way to force a particular facet is always taken into account? For example what if we always want to make sure the correct genre was returned, but then for other facets we don't care that much and they can fallback to less and less specific filters?
Our specific example is that we have a diets facet in our recipes app, and obviously if someone selects vegetarian we do not want to fall back to non-vegetarian recipes. But for all other facets it's fine.

Can the and operator solve your issue? Otherwise I would use the searchFunction or a wrapper around the instantMeilisearch.search method to change the value of facets/filters. This guide might help you

Are we close to getting this one merged in?

It is available in a beta version. You can try it out already :) See release notes on how to try it.
We are waiting for additional feedbacks to merge it

can the same be done through APIs?

Works great! 🎉 thanks so much for implementing this feature 🙏

Hey @MoustafaElsaghier, the multi-index search in the API is in consideration. We are discussing it here. Could you provide the reason why it would be useful to you there?
Thanks a lot for your feedback 🙏

Hello @bidoubiwa, I'm looking for the disjunctive feature to be in API not a multi-index search
to be more clear, I need the disjunctive feature in the same index search same as the main GitHub issue in this thread

Hi @bidoubiwa are we close to having this feature out of beta?

Released on the latest dist tag on npm :)


Choose which Db provider to use at pull server creation

As discussed in #201 it would be very helpful to be able to choose which Db provider to use when creating a pull server, instead of having to manually switch.
I want to be able to set up a pull server using the OleDb provider. Currently, I think it just depends on OS version, and the default is ESENT, which causes the C:\Program Files\WindowsPowerShell\DscService\ directory to fill up with tons of edb log files.

I think it just depends on OS Version

OLEDB is deprecated and incompatible with server core (requires the GUI to be installed) whereas ESENT works with server core and GUI variants.

@megamorf Well, if you are using a GUI version of Windows Server then indeed you have the option to use either OleDb and ESENT; given the instability issues plus the incessant writing of 128KB log files with ESENT an option should be given to the users on which to use (for the time being at least).

As I commented on the DSC repo, i dont think we should have an option.
The script today checks your OS level and based on that decides if its ESENT or OleDB
and it should stay like that.
The issues with ESENT will somewhat be dealt with in WMF 5.1 and the excess logs you can deal with a schedules task to clean them periodically (not the best solution but its something).
I'm Not a big fan of ESENT but the metadata needs to be inside a storage of some sort. I'm glad we have Loeb as it helped me and some other overcome issues at the start with early WMF and xPSDSC version bugs but going forward id even go to say we need a different DB technology, sort of the LocalDB that comes bundled with VisualStudio without installing any SQL components or even better a JSON based NOSQL solution (though that would require going open source on at least the data layer)
The basic concept of "if you are using a GUI version of Windows Server ",  is where the change should start ;)


[0.71.0-rc.0] Gap, flexWrap & alignContent renders wrong size

Description
When using gap, flexWrap and alignContent, size is miscalculated, because gap isn't taken into account when computing the sizes, so if any wrapping happens because of gap, it is not computed properly
Please note that I have tried with and without legacyStretchBehavior enabled (by patching react-native).
Version
0.71.0-rc.0
Output of npx react-native info
System:
OS: macOS 12.6
CPU: (8) arm64 Apple M1
Memory: 155.78 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.11.0 - /usr/local/bin/node
Yarn: 1.22.17 - /opt/homebrew/bin/yarn
npm: 8.19.2 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 13.4/13F17a - /usr/bin/xcodebuild
Languages:
Java: 11.0.15 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.0-rc.0 => 0.71.0-rc.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
In order to reproduce you need to have:

1 container with flexWrap: ‘wrap’ & alignContent: ‘stretch’ & gap: someValue
Children that wrap only because of the gap property (they would fit in the container otherwise)

When that happens the size calculated by alignContent: ’stretch’ doesn’t take into account the wrap, so each child will have the full container size instead of half

.
Example:

Container of 300 x 300 direction 'row', flexWrap: 'wrap', alignContent: 'stretch'
5 children of width: 60,  flexGrow: 1

Before adding gap: 1

After adding gap: 1

Note that if the child where already wrapping (example width: 61) this would not happen. It only happens if the wrapping is caused by gap

Snack, code example, screenshot, or link to a repository
Web equivalent:
https://jsfiddle.net/t8q6xevj/1/
Native Code used to test:
Feel free to alter gap of container / width of children
import React from 'react';
import {
  SafeAreaView,
  View,
} from 'react-native';

function App(): JSX.Element {
  return (
    <SafeAreaView style={{flexGrow: 1, alignItems: 'center', justifyContent: 'center'}}>
        <View
          style={{
            height: 300,
            width: 300,
            backgroundColor: 'blue',
            flexWrap: 'wrap',
            flexDirection: 'row',
            alignContent: 'stretch',
            gap: 1,
          }}>
          <View
            style={redChild}></View>
          <View
            style={greenChild}></View>
          <View
            style={redChild}></View>
          <View
            style={greenChild}></View>
          <View
            style={redChild}></View>
        </View>
    </SafeAreaView>
  );
}

const child = {
  flexGrow: 1,
  width: 60,
}

const redChild = {
  ...child,
  backgroundColor: 'red',
};
const greenChild = {
  ...child,
  backgroundColor: 'green',
}

export default App;

cc @necolas @NickGerleman

Good report (and good we can fix before much usage). Gap should not cause the height to increase when it is the reason for wrapping. Will take a look and add this as a test. FYI @jacobp100
YGCalculateCollectFlexItemsRowValues possibly prepares something unexpected, or a later step is doing something wrong to set cross-axis dimensions. Should be able to debug this.

Since gap sets both columnGap and rowGap, I wonder if it happens when you only set columnGap. That's the property that causes it to overflow - but it could be rowGap that is actually the issue

Still happens with just columnGap. I have a fixture working which causes a failing unit test.

Planning to dig in a bit, since I know running these UTs is currently a giant pain in OSS (I thought I would have added the CMake baed UTs a while back but have been awful about maintaining focus recently). But should be manually reproable as well.

If you post the branch name I can dig a bit too

Maybe it's worth adding a disclaimer about gap in the release notes too. Warn people it may have bugs, and that fixing those bugs later on may break their layouts

@intergalacticspacehighway FYI too

Maybe it's worth adding a disclaimer about gap in the release notes too. Warn people it may have bugs, and that fixing those bugs later on may break their layouts

This is actually something that I was talking about with @Titozzz: is there a way to maybe have the flex-gap stuff hidden behind some experimental flag so that folks know that fix/issues/bugs and breaking changes might come at a later stage as things pop up?

Debugging this, comparing wrap with gap vs wrap due to size overflow.
Step 8: "MULTI-LINE CONTENT ALIGNMENT" is normally what sets things up. Children should most recently have been called with cross axis YGMeasureModeAtMost which measures cross-axis size is at zero, but YGAlignStretch will set the cross-dimension based on available size divided by line count.
In the gap case, measured cross-axis dimensions are 300px at this step. In the non-gap case it is transiently this (I think it is the result of YGMeasureModeUndefined?). But it means at some previous step we are not measuring cross-axis correctly specifically in the gap case.

Maybe it's worth adding a disclaimer about gap in the release notes too. Warn people it may have bugs, and that fixing those bugs later on may break their layouts

This is actually something that I was talking about with @Titozzz: is there a way to maybe have the flex-gap stuff hidden behind some experimental flag so that folks know that fixes/issues/bugs and breaking changes might come at a later stage as things pop up?

I don't think we should gate it. There are more conformance tests we could maybe add to have caught this (e.g. a plan was to generate more Yoga fixtures from WPT), but real usage is also what led to bug discovery here, and putting the feature behind a flag would prevent that.
I do want to gate future capabilities behind StrictLayout, where we want to explicitly allows instability to make  conformance fixes while staging. But flex gap is already here, and we have told people they will get it.

I think the issue could be on this statement where it doesn't account gap and childCrossSize gets set to availableInnerCrossDim i.e. 300px. Maybe we should account gap here as well.

 currentRelativeChild->getGapForAxis(crossAxis, availableInnerCrossDim).isUndefined()

Adding this fixes the issue!

Okay, so I think I'm understanding this?
In YGDistributeFreeSpaceSecondPass, if we do not have overflow (determined by flexBasisOverflows), we have stretch cross-alignment, and we reason that nothing can add to main axis dimensions, we know we're a single line and want to take full cross dimensions. and can set YGMeasureModeExactly which uses parent dimensions. Guessing an optimization?
If we do have overflow, then we set YGMeasureModeAtMost to find minimum possible cross-axis dimensions instead. I confirmed this is normally taken.
Probably worth checking the other usages of flexBasisOverflows in case there are other options taken in the non-overflow case that only accounts for basis.

Yeah, it looks like totalOuterFlexBasis, used for overflow logic, is more than just flex basis, it also includes margins already. It is also used for setting main axis measure mode to parent width instead of minimum size if we have overflow.
I think the right solution here is to rename this, and incorporate gap spacing into its checks.

PR here: https://github.com/facebook/yoga/pull/1173
New UT and previous ones are now passing.

I also think we should not gate it, but warn users that if it doesn't match the spec there will be breaking changes might be a good idea

A general strategy for compatibility fixes has been:

Enable the fix everywhere if we think breaks are unlikely. I.e. does the change cause issues if we turn it on for an experiment group in a very large codebase?
Put the continuing set of the rest of the breaking fixes under StrictLayout.

We are starting off at zero usage of gap within the RN ecosystem, so we are probably safe to make fixes while the usage is building, but after, we could fold likely impacting changes into StrictLayout.

It's also one of the reasons I want to gate new major additions behind StrictLayout, since it makes that guarantee explicit (unless you opt into a quirk).


closing extension host window doesn't terminate debug session

Regression in VS Code Insiders:

start extension host debugging
close extension host window

Observe: debug session doesn't stop
This did worked in VS Code 1.22

The issue here is that I am not getting the exit event from the adapter.
When I compare it to stable there I am getting the exit event nicely from the adapter.
Forwarding to @weinand and @roblourens so they first investigate on their side.

Most likely this is not an adapter issue but a problem of the refactored VS Code code.
I will investigate.

@isidorn No, this is a regression introduced through your fix for #43516.
I've reverted the fix via https://github.com/Microsoft/vscode/commit/bb77f586648e23b369168800acdf4693c152cc7f and re-openend #43516.


function doOnNotAuthenticated should use $location properly

The current function has a bad behavior, which I caused.
I had to use this function to change the default next url to whatever I needed, but if the url has a next parameter then it starts replacing (which actually works), but it leaves a comma (,) in the url :disappointed:
The correct behavior instead of replacing the url via regex is to use the built in $location.path() and $location.search().
The method then should look like:
config.doOnNotAuthenticated = ["$location", "restrictedUrl", function ($location, restrictedUrl) {
  $location.path(config.loginRoute).search('next', restrictedUrl);
}];

Also it would be handy if we could change the next url manually whenever we needed, so please add it to the provider with:
visor.addNextToUrl = function addNextToUrl(restrictedUrl){
  $location.search('next', restrictedUrl);
};

What do you mean by "The current function has a bad behavior, which I caused." , what was the bad behavior?
Can you give me an example of a Url that was added badly to the Next url and what was the result?

Also note that $location.path(config.loginRoute).search('next', restrictedUrl); isn't correct, since someone can have a config.loginRoute with search parameters or a hash.

I created an example for the issue. Maybe it could be much more simpler but I wanted to show you the full context.
http://codepen.io/ocReaper/pen/wMBBYz
here is the fix for that issue:
http://codepen.io/ocReaper/pen/wMBBQz

The only way I can see this situation happening in an actual application is if the loginRoute contains a next parameter by default.
Is that what happened?
I'll fix the issue that next doesn't get overridden but rather is added in addition (effectively creating an array in the parameter), but I just want to make sure that your underlying issue is fixed.
What was the scenario that originated this issue?

My default url is /#/dashboard. If the user is not authenticated than I throw him back to /#/login.
I had a login form on /#/login and after a successful authentication he will be navigated to a /#/company-selector url, which is not the default url where visor would navigate, so I add the next parameter to the url before calling visor.setAuthenticated().
The problem appears when the user fails the login and the next parameter stays in the url.
At the second attempt he tries to login he succeeds but that comma appears in the url which is causing an error.

I've changed the config.doOnNotAuthenticated to use $location.url and $location.search .
This should fix similar issues.
From what I understand the issue that you had was because you used addNextToUrl directly and you solved it by just using $location.search instead, right?
Since I'm now using $location.search directly, this should solve any theoretical issue.

Yes it solves my problem!
Thanks for the fix, and the fast response time!


Remove index in calls to the RAMSTKComboBox.do_load_combo() method and then remove index from the argument list.

This issue was automatically generated from a TODO comment in the file src/ramstk/gui/gtk/ramstk/Combo.py.

Fixed in commit e0e46bea8c9950503b3c4acbf8636fa2046a64c7


priority of the indentation line is too high, sometimes covers the characters

The priority of the indentation line is too high, sometimes it covers the characters and it's very uncomfortable.
缩进线的优先级太高了，有时候会遮住字符，就很难受

You haven't provided enough information, please give me a screenshot.

like this, when i input "if", char "i" can't be seen at first
gif

the gif link can't open, and github can upload gif directly

sry, but I still can't see the gif

maybe you need wait for a minute after paste into github

fine now

Is this problem occurring after formatting the code?

no, befor formatting

I'm sorry that I didn't reproduce this issue. Please make sure you are using the latest version of the plugin, because similar issues have indeed occurred before.

OK! Thank u

Has the issue been resolved? I will close this issue for now. If there are any other problems or if a stable reproduction method is found, please let me know for free~


[Manual] - Keyboard is opened when no focus for comment or reply field on the screen

Commit number: 7f3d09256e9b78b6e4cd0207ad47b75f4691d65e
Preconditions: test user is signed in
Steps to reproduce:

Open "Post" or "Comment" screen
Set focus to "Comment" or "Reply" field
Slide the screen partially to the right, but don't navigate to the previous screen and return back to the current screen

Actual Result: The keyboard is still opened on the screen, but no "Comment" or "Reply" field on the screen.
Expected Result: The keyboard is closed and "Comment" or "Reply" field without focus is displayed on the screen

Verified on a build from commit number 87972900b3daeb656a8ae610bfa0da5a9235a9f9


Clarify that prop default() cannot call a method or access a computed property

See issue:
https://github.com/vuejs/vue/issues/6013
Documentation for props does not mention that computed properties and methods are not accessible when the prop default() is called. While it makes reasonable sense that this should be limited, the documentation should at least mention this limitation.
I'll take a stab at creating some new language for this and submit the PR.

Just merged this! Thanks. 🙂


firefox: 74.0.1 -> 75.0 and related updates

Motivation for this change
This updates firefox to the latest stable version.
Firefox sadly doesn't allow using a system sqlite database anymore. They removed the option from this version of the release. At least that means the backports will be easier for us…
I had to bump the libvpx version to the 1.8 branch as that is what they require now. I did introduce it as a dedicated attribute for now as it breaks building the ESR release of Firefox and likely others as well. In the long term I'd like to swap the arguments (the newest/latest one being libvpx and the old one only being used where it makes sense). Given the potential impact of that change (and that we've to rebuild everything that depends on libvpx) that is an effort for a dedicated PR.
Note the previous attempts of updating libvpx was discussed in #60826.
Pre-Release-Changelog: https://raw.githubusercontent.com/mozilla/release-notes/master/releases/firefox-75.0-release.json
Things done
Firefox:

[X] Tested on NixOS x86_64-linux
[X] Tested on NixOS aarch64-linux

Firefox-esr:

[x] Tested on NixOS x86_64-linux
[x] Tested on NixOS aarch64-linux

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/firefox-not-up-to-date/5941/9

Tested firefox-wayland and firefox, both worked well for me.
P.S.: This release adds MPRIS support, so people might want to enable media.hardwaremediakeys.enabled on Linux.

trying to unblock that stuck darwin build...
@GrahamcOfBorg  build libvpx_1_8

Firefox runs well for me.


Add number at the beggining of filename when downloading from list

It would be convenient if numeration would exist in file names after downloading a full album from a list, for example. Playing titles in correct order would be possible after that.
Example: 01-Artist-Songname.mp3, 02-Artist-Songname.mp3, ...

Solved it by using easytag.


Dynamic Resources And Texture Footprint Queries

In https://github.com/shader-slang/slang/pull/2970 support was added for texture footprint queries.
On D3D this is implemented using NVAPI. The NVAPI feature requires supplying the binding (register/space) of the resource to be queried to be passed in as integer values. The original implementation achieved the appropriate behavior by looking for IRBindingQuery derived instructions. It introduces parameters of the bindings from the call site that then are passed down and are available at the footprint intrinsic. As it stands it does so looking for the static global binding that is associated with the originating call.
This means as it stands a shader that dynamically references a resource, cannot compile. Take the example below...
uniform Texture2D textures[] : register(t2, space10);
uniform SamplerState sampler;
uniform RWStructuredBuffer<uint> outputBuffer;

Texture2D getTexture2d(uint texIdx)
{
    return textures[NonUniformResourceIndex(texIdx)];
}

cbuffer Uniforms
{
    uniform float2 coords;
    uniform uint granularity;
};

void fragmentMain(
    float v : VARYING)
{
    uint index = uint(v);
   TextureFootprint2D f = getTexture2d(index).queryFootprintCoarse(granularity, sampler, coords);

    outputBuffer[index] = f.mask.x;
}

What is needed here is for index to be taken into account when calculating the binding. In this example this is relatively straight forward in that it is (2 + index, 10). This calculation can be produced by working out the path the the resource, and then using layout to determine how to calculate the binding.
Ideally an implementation would allow this and more complicated dynamic resource usage to work, at least until there is parity with VK.

This should be fixed with the recent texture intrinsics clean up. We no longer inline the call so the texture remain used.


(WIP) Branding

https://github.com/CenterForOpenScience/osf.io/pull/6293

@hmoco  is this PR relevant still? There will be more work for branding coming soon.


Add workflow to run evaluation for chronos-bolt-tiny on a subset of datasets

Issue #, if available:
Description of changes: This PR adds a workflow that will run the evaluation script on chronos-bolt-tiny for a subset of datasets specified in ci/evaluate/backtest_configs.yaml. After evaluation, a comment will be made on the PR. The workflow will only run if the run-eval label is present on a PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Evaluation Metrics

dataset
model
MASE
WQL

ETTh
amazon/chronos-bolt-tiny
0.7948305944396085
0.0748624476805626

monash_covid_deaths
amazon/chronos-bolt-tiny
40.640740664078855
0.0670648919735542

monash_fred_md
amazon/chronos-bolt-tiny
0.6133426935299197
0.04746329539586572

monash_m3_quarterly
amazon/chronos-bolt-tiny
1.3633424628367963
0.07873051309371093

monash_nn5_weekly
amazon/chronos-bolt-tiny
0.9325957817519015
0.084742535576688

monash_tourism_yearly
amazon/chronos-bolt-tiny
4.038943100958313
0.1726199493328989

taxi_30min
amazon/chronos-bolt-tiny
0.9122173974466276
0.28005610322283847


Will there be English translations?

Very impressive project you built. I will be following closely :)
Are there any English translations available?
Keep up the great work 👍 and greetings from Germany. 👍
PS the flow graph demo has a bug when you drop an Item it shows a giant SVG image.

Hello brother, thanks for following.
Currently only a small part of the text supports multiple languages, you can find them from the src/locales directory.
I have been working on something called application designer recently. This WFD project has not been updated for a long time. I will make a better project that includes process designer and application designer later.


query string parameters have the wrong name

query string parameter configuration was updated in MockServer but node javascript client was not updated so query string parameters are now broken

fixed


Implement support for root package rendering

We need to render root package as well, but in order to achieve backward compatibility that needs to be done with a yaml config option that tells the compiler to actually render it, eg something like: render_root: [true|false](false by default). Root package contents should be added on top level, without a section. #44

@ronaldtse  This one was implemented via https://github.com/metanorma/metanorma-plugin-lutaml/commit/f8216f303c473384862be8b1f3f74b295dfd449d, the syntax is like this(yaml config file):
include_root: true


added hello peasy offscreen example

I have added an example with a P3D offscreen canvas, which is drawn onto a P2D context. To use peasycam in this scenario, you have to apply the state of the current cam to the canvas.
// apply view matrix of peasy to canvas
cam.getState().apply(canvas);

I have used another rendering (cube with a sphere) as the hellopeasy example, but if you would like to have consistency over all examples, I could change that.

Thank you.


dropdown improvements: auto-select if only option, handle more keys

dropdown improvements to auto-select if only option and handle tab, page up and page down.

Thanks


Calculation of Tresca stress in TF winding pack

In GitLab by @mkovari on Nov 9, 2017, 08:45
Section 2.4.3 of the PROCESS engineering paper explains that

Because the structural material inside the winding pack is assumed to take the form of radial and tangential webs (Fig. 7), the limiting von Mises stress in this zone is given by the larger of the two values:

I think we should adopt the same method when calculating the two Tresca stresses:

Calculate the radial stress in the radial webs, and combine with the vertical stress;
Calculate the tangential stress in the tangential webs, and combine with the vertical stress.

We need to think about how these are derived from the single set of smeared stresses.

look at this line
Array equation
    sig_tf_tresca_tmp1 = numpy.maximum(
        numpy.absolute(sig_tf_r - sig_tf_t), numpy.absolute(sig_tf_r - sig_tf_z)


Capitalize "Tribes" universally

On 10/29/21, Shawn Brouwer requested that we capitalize "Tribes" universally on the site.
Normally, this is not correct when using sentence case, as is our standard. But we don't know whether this might be seen as disrespectful to Tribes, and want to err on the side of caution there. So we'll make the change. If we find documentation that this is in fact incorrect and it's not commonplace to capitalize the T, we can revert.
UPDATE: According to the US Government Publishing Style Manual, "Tribe" and "Tribal" are always capitalized as a sign of respect to federally-recognized American Indian or Alaska Native tribes. That seems definitive and authoritative. Recommend we adopt.

[x] Identify all the places we use "tribes" or "tribal" (Drought assistance and the staged Tribal lands)
[x] Capitalize
[x] Stage
[x] Publish

Completed 10/29/21 and notified Shawn.


torch compile tensorrt error

🐛 Describe the bug
When compiling segment_anything with torch_tensorrt,
I got the error We don't have an op for aten::floor_divide but it isn't a special case.
My reproducible code is:
from segment_anything import sam_model_registry, SamPredictor
import torch_tensorrt

sam = sam_model_registry["vit_b"](checkpoint="sam_vit_b_01ec64.pth")
input_signature = ([torch_tensorrt.Input(shape=frame.shape, dtype=torch.half)])
enabled_precisions = {torch.half,}
sam.image_encoder = torch_tensorrt.compile(sam.image_encoder, input_signature=input_signature, enabled_precisions=enabled_precisions)

The error message is:
Traceback (most recent call last):
  File "realtime.py", line 144, in <module>
    main()
  File "realtime.py", line 116, in main
    sam = newSam(frame)
  File "realtime.py", line 86, in newSam
    sam.image_encoder = torch_tensorrt.compile(sam.image_encoder, input_signature=input_signature, enabled_precisions=enabled_precisions)
  File "/home/topunion/.local/lib/python3.8/site-packages/torch_tensorrt/_compile.py", line 133, in compile
    return torch_tensorrt.ts.compile(
  File "/home/topunion/.local/lib/python3.8/site-packages/torch_tensorrt/ts/_compiler.py", line 139, in compile
    compiled_cpp_mod = _C.compile_graph(module._c, _parse_compile_spec(spec))
RuntimeError: 0 INTERNAL ASSERT FAILED at "../torch/csrc/jit/ir/alias_analysis.cpp":615, please report a bug to PyTorch. We don't have an op for aten::floor_divide but it isn't a special case.  Argument types: int, int,

Candidates:
	aten::floor_divide(Tensor self, Tensor other) -> Tensor
	aten::floor_divide.Scalar(Tensor self, Scalar other) -> Tensor
	aten::floor_divide.out(Tensor self, Tensor other, *, Tensor(a!) out) -> Tensor(a!)

Versions
Collecting environment information...
PyTorch version: 2.0.1+cu118
Is debug build: False
CUDA used to build PyTorch: 11.8
ROCM used to build PyTorch: N/A
OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0
Clang version: Could not collect
CMake version: version 3.25.0
Libc version: glibc-2.31
Python version: 3.8.10 (default, May 26 2023, 14:05:08)  [GCC 9.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-73-generic-x86_64-with-glibc2.29
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3060
Nvidia driver version: 530.41.03
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   43 bits physical, 48 bits virtual
CPU(s):                          12
On-line CPU(s) list:             0-11
Thread(s) per core:              2
Core(s) per socket:              6
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       AuthenticAMD
CPU family:                      23
Model:                           113
Model name:                      AMD Ryzen 5 3600 6-Core Processor
Stepping:                        0
Frequency boost:                 enabled
CPU MHz:                         2200.000
CPU max MHz:                     3600.0000
CPU min MHz:                     2200.0000
BogoMIPS:                        7200.08
Virtualization:                  AMD-V
L1d cache:                       192 KiB
L1i cache:                       192 KiB
L2 cache:                        3 MiB
L3 cache:                        32 MiB
NUMA node0 CPU(s):               0-11
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Mitigation; untrained return thunk; SMT enabled with STIBP protection
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Retpolines, IBPB conditional, STIBP always-on, RSB filling, PBRSB-eIBRS Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca sme sev sev_es
Versions of relevant libraries:
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.24.1
[pip3] torch==2.0.1+cu118
[pip3] torch-tensorrt==1.4.0
[pip3] torchaudio==2.0.2+cu118
[pip3] torchvision==0.15.2+cu118
[pip3] triton==2.0.0
[conda] Could not collect

I also met the same problem, it seems that attention module in ImageEncoderViT has some trouble

It is because torch-trt dont support % op, you need to change % to int(a - b * torch.floor(torch.div(a, b))), the compute is the same, but can convert by torch-trt. Function window_partition in segment_anything/modeling/image_encoder.py contain % op.

hi @Mythos-Rudy have been able to compile the encoder part to tensorrt?

It is because torch-trt dont support % op, you need to change % to int(a - b * torch.floor(torch.div(a, b))), the compute is the same, but can convert by torch-trt. Function window_partition in segment_anything/modeling/image_encoder.py contain % op.

This is helpful for me, thank you.
I use this code below to replace % op:
def TakeRemainder(x: int, y: int) -> int:
    return x - y * int(x / y)


[JK] Update success() calls

.success() has been deprecated for a while, and officially removed from angular starting from v 1.6. This converts from .success() and .error() to .then() and .catch().

This is 👍


custom pytest_assertrepr_compare

Approach:

new method on some types, e.g. __inequality_details__(op) should return a list of strings
add a utility function to check for __inequality_details__ and call it if required,
instructions on calling that function from pytest_assertrepr_compare

rough prototype for Contains:
def pytest_assertrepr_compare(config, op, left, right):
    if isinstance(right, Contains):
        word = 'not' if op == '==' else 'unexpectedly'
        if len(right.contained_values) == 1:
            descr = f'Container: {right.contained_values[0]!r} {word} found in'
        else:
            descr = f'Container: {right.contained_values!r} all {word} found in'
        return [
            f'[dirty-equals] "{op}" failed',
            descr,
            *pformat(left).split('\n'),
        ]

Any interest in me taking a crack at this?

I think best to leave it, I have some pretty strong ideas about how to go about it and it might require changes to other libraries to make it work.

while taking a look at some details, i took note that hamcrest implement a lot of the description stuff as well as a actual equals mapper


NPE in MultiplexBluetoothTransport.java : mmOutStream

Stacktrace:
com.smartdevicelink.transport.MultiplexBluetoothTransport.com.smartdevicelink.transport.MultiplexBluetoothTransport$ConnectedWriteThread.write(SourceFile:1732)
       at com.smartdevicelink.transport.SdlRouterService.writeBytesToTransport(SourceFile:1254)
       at com.smartdevicelink.transport.SdlRouterService$PacketWriteTask.run(SourceFile:2357)
       at com.smartdevicelink.transport.SdlRouterService$PacketWriteTaskMaster.run(SourceFile:2390)

Error occurs at
https://github.com/smartdevicelink/sdl_android/blob/master/sdl_android_lib/src/com/smartdevicelink/transport/MultiplexBluetoothTransport.java#L732
mmOutStream is null here

Proposal is to catch NullPointerException alongside IOException


Research existing datasets

Are there any existing datasets derived from human speech we could use?

Particularly interested in conversational style, and noisy/messy data (lots of filler words, differences in transcription etc.).

Also worth investigating datasets used as part of the MTQE project

Other datasets which could be useful include those used for disfluency detection, in particular Disfl-QA which includes both an original question (derived from SQuADv2 and a human-altered question containing added disfluencies.


DefectDojo social-authentication with Gitlab

I want to use Gitlab as a OAuth2 provider and I followed documention but it didn't work.
In the documention I need to edit the settings with the following information:
DD_SOCIAL_AUTH_GITLAB_KEY=(str, 'xxxxxxxxxxxx'),
DD_SOCIAL_AUTH_GITLAB_SECRET=(str, 'xxxxxxxxxxxx'),
DD_SOCIAL_AUTH_GITLAB_API_URL=(str, 'https://xx.xxx.xxx.xx'),
DD_SOCIAL_AUTH_GITLAB_OAUTH2_ENABLED = True
*https://documentation.defectdojo.com/integrations/social-authentication/#gitlab
I also read the documention of configuration, environment variables in my local_settings.py must have no DD_ prefix. So I edit the settings like this but it didn't work:
SOCIAL_AUTH_GITLAB_KEY = 'xxxxxxxxxxxx'
SOCIAL_AUTH_GITLAB_SECRET = 'xxxxxxxxxxxx'
SOCIAL_AUTH_GITLAB_API_URL= 'https://xx.xxx.xxx.xx'
SOCIAL_AUTH_GITLAB_OAUTH2_ENABLED = True
*https://documentation.defectdojo.com/getting_started/configuration/
When I read the code of DefectDojo, I found that in the /dojo/settings/settings.dist.py , the variable is GITLAB_OAUTH2_ENABLED, not SOCIAL_AUTH_GITLAB_OAUTH2_ENABLED.
So I edit the settings like this and restart DefectDojo, I finally see a Login with Gitlab button on the login page:
SOCIAL_AUTH_GITLAB_KEY = 'xxxxxxxxxxxx'
SOCIAL_AUTH_GITLAB_SECRET = 'xxxxxxxxxxxx'
SOCIAL_AUTH_GITLAB_API_URL = 'https://xx.xxx.xxx.xx'
GITLAB_OAUTH2_ENABLED = True
I think it is necessary to write the documention more clearly or name variables uniformly :)

Hi @Yuan-Yubin,
were you successful? And if yes, could you please make a PR to update the docs?

Do you also have an answer on this: https://github.com/DefectDojo/django-DefectDojo/issues/9084 ?

Do you also have an answer on this: #9084 ?

No...

You can add this values in docker-compose.yml
uwsgi:
  image: defectdojo/defectdojo-django
  environment:
    DD_DEBUG: "true"
    ***
    DD_SOCIAL_AUTH_GITLAB_KEY: "****"
    DD_SOCIAL_AUTH_GITLAB_SECRET: "****"
    DD_SOCIAL_AUTH_GITLAB_API_URL: "https://gitlib.domain.ext"
    DD_SOCIAL_AUTH_GITLAB_OAUTH2_ENABLED: "true"

@Yuan-Yubin , did this information from @wywerne help you to fix the issue?
You can also take a look here https://defectdojo.github.io/django-DefectDojo/integrations/social-authentication/#gitlab
I guess this can be closed @mtesauro


Make top-level code variables @MainActor @_predatesConcurrency

This patch gets the semantics roughly where we want them. The top-level code context is set to run on the main actor and the top-level variables are @MainActor @_predatesConcurrency. This pairing reduces the number of hops between actors for top-level code, provides some level of safety, and keeps the code breakage fairly minimal.
The next PR contains await detection to turn the top-level code into an async context once the first use of await is used in the top-level. If no awaits are used, the top-level should behave exactly the same as it does today to keep current scripts working.

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 8a8bd57316958bffd3f6894e312d4b8caf9574fd

It looks like all of the API's have changed... D:
Missing predatesConcurrency and swift::ActorIsolation::forGlobalActor!? Interesting.

predatesConcurrency has been changed into preconcurrency in #40680

Build failed
Swift Test OS X Platform
Git Sha - 8a8bd57316958bffd3f6894e312d4b8caf9574fd

@swift-ci please test


Commits in wrong order

I detected, that the order of some commits is wrong. They aren't sorted by their date.

Same as in github/android #420

Commits shouldn't be sorted by date in git.
They are sorted following the tree, which is not necessarily chronological.

Ah ok


Benchmark release

Thank you for your excellent contributions!
May I ask if the test set of MONET could be made public available in the future?

I've shared the validation and test sets. Please check the updated README.md.


documented server.ts ( still need to add more ) + added dummyHPC

create job with hpc == "dummy_hpc"

@zimo-xiao Can you have a look at this PR ?

/lgtm