docs(readme): mention that pnpm zip will erase dist-zip

Priority*

[ ] High: This PR needs to be merged first, before other tasks.
[ ] Medium: This PR should be merged quickly to prevent conflicts due to common changes. (default)
[x] Low: This PR does not affect other tasks, so it can be merged later.

Purpose of the PR*
Submitting this PR after I renamed extension.zip to something else and ran pnpm zip again... only to find out that my renamed extension was gone :)

#811

I think we can replace it with the above PR.

As the above PR is merged, no modifications to the README.md are required, so I'm closing this PR. Thank you for your contribution.


new term request: 6-hydroxymethyladenine

It would be great if 6-hydroxymethyladenine could be added. It has recently been discovered to be present in mammalian DNA [Xiong et al., Nucleic Acids Research 2018; gky1218].
For consistency with the existing methyladenines, I would appreciate its being added similarly (i.e. with the oxyribose).
Suggested outgoing annotations:

 has functional parent adenine (CHEBI:16708)
 is a 6-alkylaminopurine (CHEBI:17524)

I have created a new entry for 6-hydroxymethyladenine (ChEBI=142766).
Best Regards,
Adnan


After restarting linked container, the ENV variables of recipient doesn't update.

Hello, I've noticed some weird behavior after restarting the linked container. Let's see this simple example:
docker run -d --name db training/webapp python app.py
docker inspect -f '{{ .NetworkSettings.IPAddress }}' db
<IP_ADDRESS> # ip of db

docker run -d -P --name web --link db:db training/webapp python app.py
docker exec web cat /etc/hosts
<IP_ADDRESS>     4379cf90c3016
<IP_ADDRESS>	    localhost
...
<IP_ADDRESS>     db

docker exec web env
...
DB_PORT=tcp://<IP_ADDRESS>:5000
DB_PORT_5000_TCP=tcp://<IP_ADDRESS>:5000
DB_PORT_5000_TCP_ADDR=<IP_ADDRESS>
DB_PORT_5000_TCP_PORT=5000
DB_PORT_5000_TCP_PROTO=tcp
DB_NAME=/web/db
...

Now, lets restart db container and see what was changed in web container:
docker restart db
docker inspect -f '{{ .NetworkSettings.IPAddress }}' db
<IP_ADDRESS>

docker exec web cat /etc/hosts
<IP_ADDRESS>     4379cf90c3016
<IP_ADDRESS>	    localhost
...
<IP_ADDRESS>     db  #OK!

docker exec web env
...
DB_PORT=tcp://<IP_ADDRESS>:5000  #IP ADDRESS DOESN'T CHANGE
DB_PORT_5000_TCP=tcp://<IP_ADDRESS>:5000
DB_PORT_5000_TCP_ADDR=<IP_ADDRESS>
DB_PORT_5000_TCP_PORT=5000
DB_PORT_5000_TCP_PROTO=tcp
DB_NAME=/web/db
...

What's going on? May be I do something wrong?

I think this is a known issue (but thinking of that, if it is, it is something that should be documented). The environment variables for links may even go away in the future because they don't really add much useful information (e.g., you have to know the port-number in order to get the right name of the environment-variable that contains the port-number :))
I realise this doesn't solve the issue, but would it work in your situation to use the hostname that's added in /etc/hosts in stead?

Yeap, using entry in the hosts file is quite enough for me (at least for now)! :)

related to #9526

I added some notes to the documentation to explain that the ENV-vars are not automatically updated; https://github.com/docker/docker/pull/10170
Also some additional explanation as to "why" that doesn't work and future changes can be found here; https://github.com/docker/docker/issues/10164#issuecomment-70407731
With those, I suggest to close this issue; updating the ENV-vars is not possible and alternatives will be implemented with the new networking?

I'm going to go ahead and close this as it's basically a dup of #3155
Feel free to ping here or on IRC if you have any questions/concerns.

@kalopsia you could use docker-fw to start them, then ports would be kept as before the stop. See also #8723

Thanks)


Access Env in nameTemplate

This is more a question, but for the nameTemplate, is there a way to access the env variable? Currently this is the template that I'm using:
"{{.Project.Name}}-{{.Project.Env}}-{{.Function.Name}}"
The output would look like:  Example-qa-hello

You should be able to get at any of the config, it's not documented well at the moment, but you can see https://github.com/apex/apex/blob/master/project/project.go#L42-L74 for reference

Thanks TJ
What I did manage to figure out is that the flag --env will populate the
.Project.Environment template variable, it does not acknowledge the
defaultEnvironment setting however. So if I don't provide the --env, then
the variable ends up blank.
On Fri, Jul 7, 2017 at 6:07 PM TJ Holowaychuk<EMAIL_ADDRESS>wrote:

You should be able to get at any of the config, it's not documented well
at the moment, but you can see
https://github.com/apex/apex/blob/master/project/project.go#L42-L74 for
reference
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apex/apex/issues/781#issuecomment-313823952, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AANH-M6h7X5IJIN5Ow04VKEjD41z67UJks5sLtZrgaJpZM4ORR7E
.


Crypto Revolution Token Logo

Hi guys. Please I neen my token logo to be visible. My friends told me people from Trust Wallet githib can help me

](url)

Thank you in advance if someone will help :)

Wrong repo, see: https://developer.trustwallet.com/add_new_asset


Install slap locally

If I do not have root permissions to install Node, slap should be able to install and run locally.
This can be a great enhancement

I fond a way to install npm locally and that in turn would install slap locally. Would blog about it

As a matter of fact, even with npm installed globally, you can install slap locally:
$ npm install slap # installs into ./node_modules/slap

You can then run cd node_modules/slap && ./index.js <file1> <file2>. You can add $CWD/node_modules/.bin to your PATH if you want slap accessible anywhere.
Glad you got it working!


Cancel word not working on Demo

Hi!
I follow the instructions for running the Demo and it works great! Thanks to uezo e all contributors!
I am having a minor issue with the cancel word where the prompt will keep [Listening...] event after the Cancel Word is identified
The goodbye response comes duplicated and then a hello response triggers [Listening...]
I don't know how to debug this to give adicional information, any help is appreciated.
Thank you guys!

Hi @brunoatvenosa ,
I reproduced the situation where the cancel word doesn't work👍
The found that the recognized text ends with "\n".
I will fix this issue in next update by replacing trailing \n and trimming before evaluate cancel words.
If you want a quick fix, change the code as following:
https://github.com/uezo/ChatdollKit/blob/master/Scripts/Dialog/RequestProvider/VoiceRequestProviderBase.cs#L166
to
var text = request.Text.Replace("\n", "").Trim();


Block Matmul non-deterministic hang with WH

When using the block based api matmul_block for WH, we spot a non-deterministic hang when subblock dim > 1.
When subblock_h (rt_dim) and subblock_w (ct_dim) both equal to 1, there is no hang.
when subblock_w > 1, it hangs randomly.
To Reproduce
go to branch main
run the pytest pytest tests/tt_eager/python_api_testing/unit_testing/test_bert_ops.py

@yugaoTT , any update here? Since it is P0_showstopper, i don't think it is great to leave it 5 days without updating.

@jliangTT Here is what we find since:
With interm/output cb inplace removed, the L1 corruption gone
We think it is the sync between packer and math causing the hang.
no cb_reserve, no pack_tile, no hangs
no pack_tile, no hangs
no partial pack_tile, hangs
Delay matmul_block by 500 iterations, no hang
Delay matmul_block by 100 iterations, no hang
Delay matmul_block by 50 iterations, no hang
Delay matmul_block by 10 iterations, hang

Delay matmul_pack by 500 iterations, no hang
Delay matmul_pack by 100 iterations, hang
Delay matmul_pack by 10 iterations, hang

Delay in0 mcast by 500 iterations, hang
Delay in0 mcast by 100 iterations, hang
Delay in0 mcast by 10 iterations, hang

Is this an LLK team work item? Is it still a P0?

@jliangTT it is still being debugged by me and @rtawfik01, we narrowed down to single core hang.

sounds good. following it in the slack now. thanks for driving this.

Updates on ND hangs:

We were able to slow down the ai clk to 500 Mhz and the matmul test passed for 5000 iterations in fast dispatch mode. Previously in 1000Mhz it hangs at 100-200 iterations.
@ttmtrajkovic and @acejkov find the frequency range: 918 and higher hangs, 909 and lower passes
next steps: more test runs to confirm freq range. adding staggering in the dispatch cores to see if that affects fmax.
provide repro instructions to syseng team to check on their end.

With very little information, this is sounding like the hang I'm looking at Buda side. Hasn't been root caused but while investigating, I found a bug in a workaround for a hardware bug, tracked in gitlab issue budabackend/issues/2348
This bug had to do with RAW hazard scenarios. For sub-word stores and loads, there is a hardware bug that could accidentally reorder the read before the write, even if they target the same address. @pgkeller put in a gcc pass to kill the reordering inside the risc but the pass missed some cases. We're waiting on a fix to close those gaps.
The one thing I'm seeing different here is that on BUDA I was decoupling math and pack and doing so didn't resolve the hang - so maybe it's different.
@yugaoTT are you always seeing the hang on the same core?

@SeanNijjar The hang is not always on the same core, although from what I have seen, it usually at a specific row (row 4)
Were you able to repro this hang on single core?
Also, if the ND hang we are seeing is also related to the RAW hazard, does reduce frequency affect it?

@SeanNijjar The hang is not always on the same core, although from what I have seen, it usually at a specific row (row 4) Were you able to repro this hang on single core?

I was never able to reproduce this on a small setup with a single chip and/or core. However, given that the kernel code paths we are working with are probably quite different, I wouldn't necessarily find it that surprising.
All hangs were on galaxy machines with large-grid ops (8x8) and hangs would be anywhere from 1-4 hung cores. Sometimes those cores were in a row but not always. The hung chip could change from run to run. The way the test is setup it wouldn't really be possible for multiple chips to be hung at the same time.
There were definitely some rows that seemed more likely to hit the hang (like noc0 rows 4,5,7, and 9)

Also, if the ND hang we are seeing is also related to the RAW hazard, does reduce frequency affect it?

I'm not sure. I think this would depend on clock domains between noc, tensix, triscs, L1, which I have no idea about. At the very least, slower clocks change timing of communication with host which can change when different event sequences kick off.
One other nugget which may apply is that when a given core is hung, usually only a couple of tiles have made their way through math from the looks of it (say < 10), so it's not really in the "middle" of a given kernel. Some other obvious differences are that we are using overlay but I'm not seeing any issues whatsoever on the overlay side.

@SeanNijjar, @TTDRosen,
One important difference between the two failures (Sean’s and this one) is that Sean has tried to reproduce the problem at a lower clock and it was still failing. With this test case, early results (still to be confirmed) are that frequency sensitivity exists and that failing frequency is determined.
milos

Update on reproduce:
go to branch yugao/gs_wh_block_matmul_hang
To run the test with hangs (AI clk set to 1000Mhz):
run pytest tests/tt_eager/python_api_testing/unit_testing/test_bert_ops.py --timeout 6000
To run test without hangs (set AI clk to 500Mhz)

In tt_metal/third_party/umd/device/tt_silicon_driver.cpp , line 4362 comment out set_power_state(tt_DevicePowerState::BUSY);
make clean, make build should bring the AI clk down to 500Mhz
run pytest tests/tt_eager/python_api_testing/unit_testing/test_bert_ops.py --timeout 6000

I pushed a change to branch pkeller/wh-hang-4968 to allow staggering the start of each core at kernel launch.  Cherry pick the last commit to the branch of interest.  The diffs are trivial, functionality is: set DELAY_CYCLES_PER_Y to n to have each row stall by an extra n cycles.  No need to rebuild after each change (the file is runtime built).

@pgkeller Thank you, I'll do experiments based on the changes

btw: I was wondering yesterday if a more robust solution would be to increase the current draw when running any application.  on device init we could start the triscs in a loop that sends some work to tensix while waiting for the next kernel.  this isn't fully robust, though, as we could have a kernel w/ low work load followed by a kernel w/ high work load

I tried increasing the initial stagger to 10K cycles, it still hangs around 150 iteration. One thing weird is when I enable the DPRINT on one core, the DPRINT server seems to fail much sooner (around 30 iterations) and stop printing.

I'd suggest we run an extreme number, like million cycles, as 10k is only 10us and that may not be enough.
On another note, are individual rows of cores doing multicasts or gathers for activations to make sure entire inner dim is collected on every core? If every core could do the gather, then we could stagger gather commands from every core which would effectively ensure that data arrives later on some cores in a row.
Is that an option @davorchap, @pgkeller?

I tried 100k and still hangs.
The cores in a row are doing mcast send/recv for activations. If we change to gather, then each core would fetch blocks from all other cores in a row, even if there is stagger, at some point, I think all the core will perform gather at the same time.

1M cycles hangs too.

thanks @yugaoTT.
I believe we are not doing exactly as slow dispatch does and there's gotta be something that helps in case of slow dispatch. I'd focus next experiments there.
Regarding gather vs mcast, if there was a way to control the start of gather, then cores starting gather later would effectively get data later and therefore start doing math later. I may be missing something

@davorchap,
this should be downgraded from P0_Showstopper to P1 item where different staggering methods need to be explored

@davorchap,
this should be downgraded from P0_Showstopper to P1 item where different staggering methods need to be explored

Done & re-assigned.

I have the SPI ROM firmware ready from syseng team with added voltage margin to run at 1GHz. They have tested it against the failing stressful matmul 1d/2d, across SS, TT and FF parts, also confirmed with scope captures.
I’d like to test this a bit more with some more full model/demo workloads so I’d appreciate if someone could provide me with the list of tests to run. I can run resnet, but its currently not running well on wormhole (~1k fps) so I am not sure how stressful it’s going to be.
The bottom line is that this is not a bullet-proof solution as we’ve established that not only severity of the workload matters, but also frequency of droops. For example, by running matmul 2d test in a test loop, allowing more time between iterations wasn’t causing the failure, while more frequent iterations would cause a fail. Explanation is that we could be hitting multiple levels of droop, and if workload would stop and then restart while the board droop is still happening, we are more likely to cause a fail.
This means that as fast dispatch becomes available and demos start to be more performant end to end, we need to make sure they don’t fail. It’s hard to differentiate between a functional hang and di/dt hang but that doesn’t mean that every hang should be attributed to this as its unlikely that voltage margin is not enough. Sensitivity to clocks and voltage will give an ultimate answer.

11 month old bug.

This is really related to didt debug that is still ongoing.
Overall, we can close this one since we understand the problem, but didt conclusion isn't done yet.
Closing this given that we understand the problem and created a separate debug stream for it.


Optimized diff iterator

Hoisted checks that before the loop

It looks like the libdav1d hack with an upgrade-in-place to Ubuntu Lunar doesn't work any more, and it won't upgrade libc6.

the set doesn't seem bad though.

What do you mean?

Included in #3261


adding changes

This PR fixes the issue where the edit command was incorrectly inserting a newline and removing the trailing newline during edits, as described in CODY-3236.
Test plan
https://www.loom.com/share/03636c746e33478f804d6c0a7cf75b6c
Changelog

Need to rebase with the latest changes.


Is there a way to avoid these broadcast calls?

https://github.com/GEOS-ESM/MAPL/blob/0dbe0f14adf059e53d29112d0ee2da9f4d560275/base/MAPL_sun_uc.F90#L2748-L2753
Can we do some kind of parallel read here instead of having the root node broadcast everything.  This is trapping a load imbalance from the moist physics leading to a significant overhead in Surface times.
Every PE is opening and closing the file currently as it is written

Also, does this have to happen every tilmestep??? It seems like it is. It probably needs to happen just once per simulated day, on the frequency of the daily data in the file

Hi @wmputman , I am taking a look and also pinging @mathomp4 who had a major role in the development of this part of the solar source code. Peter.

Coming at this cold:

The 3 Bcasts can certainly be turned into a single bcast with 3 items.  But this is only useful if the call is frequent.
If what @dr0cloud says is correct, then should not the open/read not only be on the root process but also only during init rather than using a TableCreated flag?

@wmputman I can see how to optimize this a bit. I talked with @dr0cloud and we can make it better.


[BUG] Deprecation message spamming logs from Security plugin

Describe the bug
Deprecation message spamming the logs

**To Reproduce**
Steps to reproduce the behavior:
1. Stream logs from logstash to OpenSearch with username, password.

**Expected behavior**
No spamming of logs

@CEHENKLE the logging is from OS, not from the security plugin. Please provide details on how the message can be suppressed by the security plugin or disable it on the OS side.

I am also seeing this issue when I running a periodic health check against the REST endpoint /_cluster/health.
According to the Elastic System Indices Feature, the /_cluster/health path should allow access to to system indices. However, it seems like with the security plugin installed, that is no longer the case.
I've gone through the source code for both OpenSearch and this plugin and I think the issue is with how the plugin injects the authentication validation code before all REST route handlers.
Here is what I've found:
In org.opensearch.security.filter.SecurityRestFilter, the wrap(RestHandler, AdminDNs) method takes the original RestHandler that is passed in and creates a new one with only the handleRequest(RestRequest, RestChannel, NodeClient) overridden. However, there are additional default methods of the interface that are not overridden in the method. So when a request to /_cluster/health comes through, the new handler that is "wrapped" uses the default implementation of allowSystemIndexAccessByDefault(), which always returns false while the original handler of class org.opensearch.rest.action.admin.cluster.RestClusterHealthAction has allowSystemIndexAccessByDefault() overridden to always be true.
Since the method returns false,  org.opensearch.rest.RestController sets the thread local field of IndexNameExpressionResolver.SYSTEM_INDEX_ACCESS_CONTROL_HEADER_KEY to false, which gets checked byorg.opensearch.cluster.metadata.IndexNameExpressionResolver and thus these error messages are printed.

Based on https://github.com/elastic/elasticsearch/pull/63274 the warning should only be enabled for SNAPSHOT builds.

@nknize @dblock @CEHENKLE Is warning still expected to be enabled for SNAPSHOTS build only? If not, when this was changed?

Another related issue https://github.com/opendistro-for-elasticsearch/k-NN/issues/356

Tried the same scenario on ES 7.10.2 and I don't see any warning. The issue is introduced by OpenSearch.

Looks like this is coming from https://github.com/opensearch-project/OpenSearch/blob/0ba0e7cc26060f964fcbf6ee45bae53b3a9941d0/server/src/main/java/org/opensearch/action/admin/indices/alias/get/TransportGetAliasesAction.java#L140. We probably want to log it once? Moving this issue to the OpenSearch project.


Update developer guide

@louisdavinlie apologies there seem to be a merge conflict, could resolve the conflict and push the changes again?

@whoisjunhong resolved!


Test Setup

Hi
I am gopher newbie. I will try setup and run tests of the project. To make it run all tests I asked to install  necessary packages required in tests. It would be better if we make a script where user can install all necessary packages at a single shot. If you guys agree with my point I would make a PR. Thanks.

 We need to update this in README. Shall I do it?

I think this is a feature of golang, developers should know this information from golang's document, gorm should not teach you that ;)


AuthenticateAsClientAsync doesn't respect ReadTimeout in a certain scenario

FTP Server OS: Windows
FTP Server Type: FileZilla
Client Computer OS: Windows
FluentFTP Version: 49.0.2
Framework: .NET 8
If I try to connect using ftp & ftps it perfectly works. Though ftpes for some reason somehow blocked in my network.  Though directly from the machine I can connect.
The issue is in the following code:
				try {
#if NETSTANDARD || NET5_0_OR_GREATER
					m_sslStream.AuthenticateAsClientAsync(targetHost, clientCerts, sslProtocols, Client.Config.ValidateCertificateRevocation).Wait();
#else
					m_sslStream.AuthenticateAsClient(targetHost, clientCerts, sslProtocols, Client.Config.ValidateCertificateRevocation);
#endif
				}

Looks like AuthenticateAsClientAsync doesn't default respect ReadTimeout of 15 seconds and hangs forever. On the other hand AuthenticateAsClient perfectly works.
I can't find any hints in the documentation on why  AuthenticateAsClientAsync  can behave differently. But I don't see any benefits here to use this function over AuthenticateAsClient as the code is completely sync.
Here are my differences from default client config (for ftpes):
            conn.Config.EncryptionMode = FtpEncryptionMode.Explicit;
            conn.Config.DataConnectionEncryption = true;
            conn.Config.SslBuffering = FtpsBuffering.Off;
            conn.Config.SslProtocols = System.Security.Authentication.SslProtocols.Tls12;

I also found this #682 where looks like SslBuffering.Off was a worarkound. This no longer works.
If it helps here's what i see in console logs:

# Connect(False)
Status:   FluentFTP <IP_ADDRESS>(.NET 8.0) FtpClient
Status:   Connecting to IP #1= ***:21
Status:   Waiting for a response
Response: 220-FileZilla Server 0.9.60 beta
Response: 220-written by Tim Kosse<EMAIL_ADDRESS>Response: 220 Please visit https://filezilla-project.org/ [738984.382d]
Status:   Detected FTP server: FileZilla
Command:  AUTH TLS
Status:   Waiting for response to: AUTH TLS
Response: 234 Using authentication type TLS [52ms]

Using a CancellationToken on AuthenticateAsClientAsync also works. Ideally I think API should be completely async with CancellationToken support starting from Connect()
Also worth mentioning that in documentation this function has no timeout exception apart from OperationCanceledException. Implicitly it looks like it is not supposed to respect any timeouts. Though this is also true for AuthenticateAsClient

Thanks for this report. Let's take it apart into separate pieces:

I also found this https://github.com/robinrodricks/FluentFTP/issues/682 where looks like SslBuffering.Off was a worarkound. This no longer works.

Let's check that SSL Buffering is actually turned off. There should be a message in the log (verbose!) stating that no SSL Buffering is actually being used (because->.NET 8).  And since this doesn't help for your problem... I understand.

I can't find any hints in the documentation on why AuthenticateAsClientAsync can behave differently.

Same for me

On the other hand AuthenticateAsClient perfectly works.

So, in the end, we should perhaps simply use AuthenticateAsClient on the SyncClient in all cases? I think so.
And if that were so, why do we actually think we need to turn SSL Buffering off (at least, in the SYNC client)? Looks like some testing is in order.

Well the decision is up to the author I think here.
I can confirm the following:

Buffering is off for me.

AuthenticateAsClientAsync hangs forever looks like.

AuthenticateAsClient after 15 seconds (ReadTimeout) throws IOException with inner SocketException  with the message: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond..

AuthenticateAsClientAsync can still be cancelled with a cancellation token.

Inside ActivateEncryptionAsync AuthenticateAsClientAsync is called with provided CancellationToken for .NET >5 which is how it should be. But note that again Token should be cancelled explicitly as ReadTimeout won't be respected.

There is no provision for CancellationToken(s) in the entirety of the SyncClient. Thus using AuthenticateAsClientAsync seems problematic, so much for that.
So two open problems, in my mind:
SyncClient: Remove usage of AuthenticateAsClientAsync overall.
AsyncClient: Need to somehow respect ReadTimeout if .NET > 5.

I would like you to test the current master as to the problems you reported. I have just merged a first take on the SYNC side of this topic. Can do?

Sync/Async code has been extensively modified. If this is still relevant, please re-open an issue with up to date information.

Thanks, so far we stopped reproducing it


Read every image in folder recursive with option to cancel

https://github.com/TheJoeFin/Text-Grab/blob/603af9629ee3519f578c7a13f9dc75e88c80a932/Text-Grab/Views/EditTextWindow.xaml.cs#L1204

I commented on my closed issue and not familiar with github so I'm not sure if it will notify you. Will comment it here too as it's somewhat related:
Have just tested the new update and it's great. The only thing that would make the folder scan even better is the ability to 'right click' in the area of the located text and have the option to: 'open the file', and 'open file location' (open the folder) while selecting that particular file so you don't have to navigate to it.
Not sure if that would be doable, I guess it would just need to find the nearest filename above the clicking point along with it's origin folder (stored at the top) (you'd probably have to change the filename format so it's easy to find)
Also I am scanning a folder with 15k pictures so it did take a while but I noticed the scan used barely any CPU, if it's possible to increase/decrease the CPU usage when performing the OCR that would be amazing although not sure if Microsoft will give that option

Awesome feature! Thinking of further automation, could there be a way to implement folder scan via CLI, so it could be added to a folder's context menu, and auto generate a (folder).txt output? Instead of manually having to open the editor, clicking scan folder buried in a sub-menu, input the folder and then saving the output.

As mentioned with the bulk OCR, would love the ability to generate a txt file for each image in a folder so it's way easier to find the image in question as the current giant text dump (even though it's useful for certain tasks) is hard to navigate and find the corresponding photo. It means I can find an image using windows explorer search.

@astandarduser responding to your comment in reverse order.
The changes to the directory scanning did not improve speed (yet, working on parallelizing the work, but it is being unexpectedly strange). Mostly more tolerant to bad files, paths, etc.
For your comment about generating a text file for each image file, that would be possible, and I can look into it. I would not want that to be the default behavior for directory scanning. So I am curious where do you expected to be able to initiate this directory scanning, and how should users be able to choose different options?

That's great, it would be neat to have it in a right click menu in explorer that expands to either the default, or generate txt files. Otherwise just in the same place


Make subscriptions optional for client configuration and standalone able to be set

Really enjoying sensu, like a breath of fresh air. Like using Ansible for the first time.
All my clients are standalone. It seems it would be more consistent with the check config if I didn't have to specify "subscriptions": [ "none" ] but instead could use the option "standalone": true for the client config.
If there is an issue of that being a required field, it could be populated with the string  'standalone' as it is set to true.

The 0.25 release is going to hit today with fewer features than originally anticipated & primarily only some internal improvements. Moving this issue to 0.26.

0.26 is now stable, which includes an automatic client subscription. There is a known validation error, which is fixed by https://github.com/sensu/sensu-settings/pull/48 0.26.5 will include it.


fix(network-manager): Fix race condition in webRTC test

copilot:all

Current dependencies on/for this PR:

main

PR #3368   👈

This comment was auto-generated by Graphite.


Add common UI library for confirmation prompts.

This library:

Is testable.
Is consistent across the CLI.

Related to (does not fix) #2510, #2296 and #2204.
Summary

Release Note
NONE
Documentation
N/A (though eventually we want to document common conventions for users).

Codecov Report

Merging #2572 (6a60cbf) into main (ed437f1) will increase coverage by 0.49%.
The diff coverage is 51.64%.

@@            Coverage Diff             @@
##             main    #2572      +/-   ##
==========================================
+ Coverage   30.00%   30.50%   +0.49%
==========================================
  Files         140      144       +4
  Lines        8654     8678      +24
==========================================
+ Hits         2597     2647      +50
+ Misses       5675     5649      -26
  Partials      382      382

Impacted Files
Coverage Δ

cmd/cosign/cli/clean.go
0.00% <0.00%> (ø)

cmd/cosign/cli/fulcio/fulcio.go
16.66% <0.00%> (-0.14%)
:arrow_down:

cmd/cosign/cli/generate/generate_key_pair.go
9.45% <0.00%> (+0.70%)
:arrow_up:

cmd/cosign/cli/importkeypair/import_key_pair.go
16.66% <0.00%> (+2.08%)
:arrow_up:

pkg/cosign/common.go
0.00% <ø> (ø)

cmd/cosign/cli/sign/sign.go
16.34% <22.22%> (+0.67%)
:arrow_up:

internal/ui/env.go
60.00% <60.00%> (ø)

internal/ui/prompt.go
74.07% <74.07%> (ø)

internal/ui/log.go
100.00% <100.00%> (ø)

pkg/cosign/keys.go
58.33% <0.00%> (-3.04%)
:arrow_down:

... and 15 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Rebased!


Create a profile class and derive GeoadminTileGrid from it

We recently added the Grid class wich can define any kind of regular grid.
This class can generate any kind of

extent
origin (x and y axis direction)
cell size (rectangular supported)

We must now create a Profile class which will be used to create any kind of tileGrid (in a cartesian space only)
As a result GeoadminTileGrid will only be a pre-parametrized class of Profile which will make use of Grid.
I don't know if I prefer Pyramid or Profile yet though.

You may also use Mapproxy
e.g.:
https://gist.github.com/procrastinatio/713a92701651bc2b82090aa61a902359

indeed


[pcl:x64-linux] build failure

Host Environment

OS: [Ubuntu 18.04]
Compiler: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04)
vcpkg version: Vcpkg package management program version 2021-01-13-unknownhash

To Reproduce
Steps to reproduce the behavior:
./vcpkg install pcl:x64-linux
Failure logs
[388/416] /usr/bin/c++ -DUNICODE -D_UNICODE -Iinclude -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/common/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/search/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/kdtree/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/octree/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/qhull/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/surface/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/surface -isystem /opt/vcpkg/installed/x64-linux/include/eigen3 -isystem /opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/recognition/include/pcl/recognition/3rdparty -isystem /opt/vcpkg/installed/x64-linux/include -fPIC -fopenmp -g   -fext-numeric-literals -fopenmp -std=c++14 -MD -MT surface/CMakeFiles/pcl_surface.dir/src/mls.cpp.o -MF surface/CMakeFiles/pcl_surface.dir/src/mls.cpp.o.d -o surface/CMakeFiles/pcl_surface.dir/src/mls.cpp.o -c /opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/surface/src/mls.cpp
FAILED: surface/CMakeFiles/pcl_surface.dir/src/mls.cpp.o
/usr/bin/c++ -DUNICODE -D_UNICODE -Iinclude -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/common/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/search/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/kdtree/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/octree/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/qhull/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/surface/include -I/opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/surface -isystem /opt/vcpkg/installed/x64-linux/include/eigen3 -isystem /opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/recognition/include/pcl/recognition/3rdparty -isystem /opt/vcpkg/installed/x64-linux/include -fPIC -fopenmp -g   -fext-numeric-literals -fopenmp -std=c++14 -MD -MT surface/CMakeFiles/pcl_surface.dir/src/mls.cpp.o -MF surface/CMakeFiles/pcl_surface.dir/src/mls.cpp.o.d -o surface/CMakeFiles/pcl_surface.dir/src/mls.cpp.o -c /opt/vcpkg/buildtrees/pcl/src/ade837d55c-07e97416c9.clean/surface/src/mls.cpp
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
log file
install-x64-linux-dbg-out.log

After several rebooting my computer. The problem is solved.
Good luck.


Unable to Use Wildcard When Targeting Data Streams with UpdateByQuery

When using UpdateByQuery, I am unable to target a data stream using a wildcard.
For example:
 indexPatterns := []string{'mydatastreamprefix-*'}
 res, err := client.UpdateByQuery(
	        indexPatterns,
		client.UpdateByQuery.WithContext(ctx),
		client.UpdateByQuery.WithPretty(),
		client.UpdateByQuery.WithConflicts("proceed"),
		client.UpdateByQuery.WithBody(read),
		client.UpdateByQuery.WithRefresh(true),
		client.UpdateByQuery.WithWaitForCompletion(true),
 )

However, this works fine if I target an index with a wildcard. Is this functionality missing from the client?
Thanks!
Wes

Hi @weslambert the client doesn't know the difference between an index and a datastream. If one works so should the other.
If you follow the documentation on how to set up a datastream, you'll see that the index pattern named my-data-stream* then leads to creating a datastream with the name my-data-stream which is what should be used when referring to this specific datastream.
By the look of your code, it seems you are trying to target the index pattern of the index template rather than the datastream's name.
You can check for your datastream names using a GET /_data_stream of course.
Am I missing something ? If so, please let me know!

Right, I (think) am aware of how data streams work.
The nomenclature in the code is poorly worded.
As I mentioned, I cannot target a group of data streams using a pattern, such as:
logs-blah1
logs-blah-2
...with something like logs-*

All clear, what you want is expansion of the datastream name.
Like /my-data-stream-*/_update_by_query would translate to /my-data-stream-1,my-data-stream-2/_update_by_query automatically.
I've managed to replicate your issue within my test setup directly in Kibana, I'm going to dig further and will update this issue accordingly.
In the meantime could you provide the version of the Elasticsearch cluster you are running on ?

Correct, thank you! This was tested using version 8.3.x.

Hi @Anaethelion, I just wanted to follow up an see if you were able to find out anything else around this issue.
Thanks!
Wes

Hi @weslambert
Sorry for the late reply, I took extra time to check and this limitation isn't on client side.
I've created https://github.com/elastic/elasticsearch/issues/90272 to track this issue.
Closing this one.

Great, thank you!


Question: multiple servers

I'm curious if multiple servers can be monitored at the same time by the same bot.  Or, alternately, if multiple bots can run in the same process.
I'm asking because one thing I am trying to do is have the IRC bot watch one IRC server, and ping people in a different server when it sees certain messages.  I can't figure out how to do it without this ability (that is, without resorting to offloading the work to a backend job processor, or some other complicated thing).
I know there's an old issue #29 that talks more about multiple bot instances, but that was 5 years ago, so I'm not sure it's still relevant.

I'm curious if multiple servers can be monitored at the same time by the same bot

No. A single Bot instance can only connect to a single server.

Or, alternately, if multiple bots can run in the same process

Normal Ruby applies. Run each Bot#start in its own thread and you can have as many bots, web servers and missile launchers in the same process as you want.

Thanks @dominikh!  I wasn't sure if it was thread safe or not.  Glad to hear I can make the bot launch my missiles 🚀  😄


SidreDataCollection changes, rename "asctoolkit" to "axom".  [exo-dev]

This PR relates to a name change of Sidre's underlying codebase from asctoolkit to axom and a refactoring of the class names within Sidre (e.g. from asctoolkit::sidre::DataGroup to axom::sidre::Group).
It also adds the ability to encode parallel meshes within the SidreDataCollection class through a new sidre::Group called adjacencies.
Finally, it modifies how SidreDataCollection uses the Sidre API to avoid/reduce the verbosity of warnings when mfem is run in debug mode.

@rieben1 and @rhornung67, any objections to merging this?

No. Merge away

@kennyweiss, when you are ready: merge this manually in next and add the in-next tag to this PR. After a week of testing in next if everything looks good we will merge the PR.

I manually merged this PR into next.


fix: messenger.ForHostname fails if the hostname is an IP

fixes #135

Fixed in my setup with this patch.

:ship:


Add a script to create backup disk for jenkins home from source code

Add a script to create backup disk for jenkins home from source code
Add steps to run the script in README

Make sure you update your branch also from upstream master.

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed

This is a test.

Jenkins job istio-testing/pr-master passed

Jenkins job istio-testing/pr-master passed

This is a test.


Updating packages dec21

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.1%) to 80.831%

Files with Coverage Reduction
New Missed Lines
%

src/DevOpsMetrics.Core/Models/Common/Build.cs
3
90.77%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
2571

Relevant Lines:
3137

💛  - Coveralls


some questions

您好！
首先十分感谢大佬能提供代码学习
我有些问题想问一下：
如果我要用HGGD对新的物体进行抓取，可以直接用你提供的checkpoint吗？还是要构建自己的数据集并训练？
请问您是如何构建自己的数据集的呢（比如制作工具）？

I have a similar problem.
I want to deploy this work on my robot, but the gripper and camera angle direction of my robot are different from yours in the paper. I need to rebuild the dataset, so I want to know how to build the dataset.
Especially, my camera perspective is not at the top, which will result in poor quality of point cloud information and will lead to bad grasp-results if you use your dataset directly.

Okay, I just saw in another issue that you said the dataset generation code will be released soon. Thank you for your contribution, and look forward to updates!
https://github.com/THU-VCLab/HGGD/issues/3

您好！ 首先十分感谢大佬能提供代码学习 我有些问题想问一下：
如果我要用HGGD对新的物体进行抓取，可以直接用你提供的checkpoint吗？还是要构建自己的数据集并训练？
请问您是如何构建自己的数据集的呢（比如制作工具）？

你好！如果需要对对新的物体进行抓取可以直接用你提供的 checkpoint 去检测抓取，我们的工作与之前的 GSNet、GraspNet-baseline 都是不依赖于具体的物体模型的，理论上具有比较好的泛化能力
关于数据构建，我们基于 GraspNet 的原始标注做了一定的过滤和转换，目前我们这个工作的后续工作仍在进行，数据处理的代码可能会在未来随着我们方法的改进版本一起放出

I have a similar problem. I want to deploy this work on my robot, but the gripper and camera angle direction of my robot are different from yours in the paper. I need to rebuild the dataset, so I want to know how to build the dataset. Especially, my camera perspective is not at the top, which will result in poor quality of point cloud information and will lead to bad grasp-results if you use your dataset directly.

Thank you for your interest of our work. Actually, GraspNet-1B dataset is captures from multiple camera angle directions, not only from the top. As for the gripper, every grasp is predicted with a specific width, which can be used for filtering or any post-processing to be adopted on different grippers. You can just try the pretrained checkpoint to check the prediction.


Websockets

Does this project support websockets (either only through jetty or through other servers as well)? If not, could support be added?

Yes, there's a library for Aleph and HTTP-Kit, both of which have websocket support.

Awesome! Could you provide an example with aleph? I'm not sure where to throw the (aleph/websocket-connection req) function

If you create a new Duct project with:
lein new duct foo +web +example

Or:
lein new duct foo +web +example +ataraxy

Then you'll see an example of how to fit a handler into a Duct project. The actual specifics of how to get the websocket vary between the different adapters, so you'll need to consult their documentation.


marksman: 2023-03-04 -> 2023-07-25

Description of changes
These releases happened since the last update:
https://github.com/artempyanykh/marksman/releases/tag/2023-07-25
https://github.com/artempyanykh/marksman/releases/tag/2023-07-01
https://github.com/artempyanykh/marksman/releases/tag/2023-06-23
https://github.com/artempyanykh/marksman/releases/tag/2023-06-05
https://github.com/artempyanykh/marksman/releases/tag/2023-06-01
https://github.com/artempyanykh/marksman/releases/tag/2023-04-12
https://github.com/artempyanykh/marksman/releases/tag/2023-04-06
https://github.com/artempyanykh/marksman/releases/tag/2023-04-02 (This release updated dotnet to version 7)
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@stasjok pr is ready to be reviewed

Looks good to me. Thanks for updating dotnet version, because update script doesn't handle that. But I don't have any permissions here to mark it as reviewed.

I'm glad it's looking good to you. In the maintainers list you are the only one, who should we inform now?


Import isn't failing but some of the nodes are just missing

I have access to a lot of the features and it doesn't show any error on loading but i'm missing the sound node, lora loader shows up in menu when I right click on checkpoint loader but it wont actually add the lora. Also they don't show up in the node search menu except for PresetText | pysssss and it loads in fine. Weird issue but my favorite extension!

Are you able to edit custom_nodes\ComfyUI-Custom-Scripts\pysssss.json and set "logging": true
Then copy the output from the console on startup to here please.
Can you also then go to settings (the little cog on the menu), View Logs, and export those logs too please
Thanks

Microsoft Windows [Version 10.0.19045.3324]
(c) Microsoft Corporation. All rights reserved.
A:\ComfyUI\venv\Scripts>activate
A:\ComfyUI\venv\Scripts>activate
(venv) A:\ComfyUI\ass\Scripts>cd A:\ComfyUI
(venv) A:\ComfyUI>python main.py
** ComfyUI start up time: 2023-08-24 09:20:35.547433
Prestartup times for custom nodes:
(venv) A:\ComfyUI\venv\Scripts>cd A:\ComfyUI
(venv) A:\ComfyUI>python main.py
** ComfyUI start up time: 2023-08-24 09:20:35.547433
Prestartup times for custom nodes:
0.0 seconds: A:\ComfyUI\custom_nodes\rgthree-comfy
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI-Manager
Total VRAM 8192 MB, total RAM 32585 MB
xformers version: 0.0.20
bin C:\Users\milksteak\AppData\Roaming\Python\Python39\site-packages\bitsandbytes\libbitsandbytes_cuda118.dll
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 3070 Ti : cudaMallocAsync
Using xformers cross attention
Skip A:\ComfyUI\custom_nodes\51NfTmeV.py module for custom nodes due to the lack of NODE_CLASS_MAPPINGS.
Total VRAM 8192 MB, total RAM 32585 MB
xformers version: 0.0.20
Set vram state to: NORMAL_VRAM
Device: cuda:0 NVIDIA GeForce RTX 3070 Ti : cudaMallocAsync
Copying: BilboX web...
ComfyUI-FaceSwap: Check dependencies
ComfyUI-FaceSwap: Check basic models
Loading: ComfyUI-Impact-Pack (V3.24.1)
Loading: ComfyUI-Impact-Pack (Subpack: V0.2)
Loading: ComfyUI-Manager (V0.26.2)
ComfyUI Revision: 1334 [f081017c]
INFO:comfyui-prompt-control:Advanced prompt encoding nodes not found.
Davemane42 Custom Nodes: Loaded
Traceback (most recent call last):
File "A:\ComfyUI\nodes.py", line 1693, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 850, in exec_module
File "", line 228, in call_with_frames_removed
File "A:\ComfyUI\custom_nodes\ComfyUI_FizzNodes_init.py", line 57, in
from .ScheduledNodes import ValueSchedule, PromptSchedule, PromptScheduleNodeFlow, PromptScheduleNodeFlowEnd, PromptScheduleEncodeSDXL #, PromptScheduleGLIGEN
File "A:\ComfyUI\custom_nodes\ComfyUI_FizzNodes\ScheduledNodes.py", line 9, in
import simplejson as json
ModuleNotFoundError: No module named 'simplejson'
Cannot import A:\ComfyUI\custom_nodes\ComfyUI_FizzNodes module for custom nodes: No module named 'simplejson'
Fooocus combined KSampler: loaded
Traceback (most recent call last):
File "A:\ComfyUI\custom_nodes\ComfyUI_InterpolateEverything_init_.py", line 18, in
spec.loader.exec_module(comfy_controlnet_preprocessors)
File "", line 846, in exec_module
File "", line 982, in get_code
File "", line 1039, in get_data
FileNotFoundError: [Errno 2] No such file or directory: 'A:\ComfyUI\custom_nodes/comfy_controlnet_preprocessors/init.py'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "A:\ComfyUI\nodes.py", line 1693, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 850, in exec_module
File "", line 228, in call_with_frames_removed
File "A:\ComfyUI\custom_nodes\ComfyUI_InterpolateEverything_init.py", line 20, in
raise ImportError("Failed to load comfy_controlnet_preprocessors: {}".format(e))
ImportError: Failed to load comfy_controlnet_preprocessors: [Errno 2] No such file or directory: 'A:\ComfyUI\custom_nodes/comfy_controlnet_preprocessors/init.py'
Cannot import A:\ComfyUI\custom_nodes\ComfyUI_InterpolateEverything module for custom nodes: Failed to load comfy_controlnet_preprocessors: [Errno 2] No such file or directory: 'A:\ComfyUI\custom_nodes/comfy_controlnet_preprocessors/init.py'
Traceback (most recent call last):
File "A:\ComfyUI\nodes.py", line 1693, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 850, in exec_module
File "", line 228, in call_with_frames_removed
File "A:\ComfyUI\custom_nodes\ComfyUI_Load_Image_With_Metadata_init.py", line 8, in
from .nodes import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
File "A:\ComfyUI\custom_nodes\ComfyUI_Load_Image_With_Metadata\nodes.py", line 6, in
from .util.image_data_reader import ImageDataReader
File "A:\ComfyUI\custom_nodes\ComfyUI_Load_Image_With_Metadata\util\image_data_reader.py", line 374
match prompt[end_node]["class_type"]:
^
SyntaxError: invalid syntax
Cannot import A:\ComfyUI\custom_nodes\ComfyUI_Load_Image_With_Metadata module for custom nodes: invalid syntax (image_data_reader.py, line 374)
2023-08-24 09:20:57,742 - roop - STATUS - roop v0.0.2
[tinyterraNodes] Loaded
Traceback (most recent call last):
File "A:\ComfyUI\nodes.py", line 1693, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 846, in exec_module
File "", line 983, in get_code
File "", line 913, in source_to_code
File "", line 228, in call_with_frames_removed
File "A:\ComfyUI\custom_nodes\comfy_mtb_init.py", line 56
if filename.suffix == ".
^
SyntaxError: EOL while scanning string literal
Cannot import A:\ComfyUI\custom_nodes\comfy_mtb module for custom nodes: EOL while scanning string literal (init.py, line 56)
Traceback (most recent call last):
File "A:\ComfyUI\nodes.py", line 1693, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 850, in exec_module
File "", line 228, in call_with_frames_removed
File "A:\ComfyUI\custom_nodes\DTAIComfyPromptAgent_init.py", line 5, in
from custom_nodes.DTGlobalVariables import variables
ModuleNotFoundError: No module named 'custom_nodes.DTGlobalVariables'
Cannot import A:\ComfyUI\custom_nodes\DTAIComfyPromptAgent module for custom nodes: No module named 'custom_nodes.DTGlobalVariables'
!! Trying to start the node
A:\ComfyUI\custom_nodes\failfast-comfyui-extensions\extensions
A:\ComfyUI\web\extensions\failfast-comfyui-extensions
Traceback (most recent call last):
File "A:\ComfyUI\nodes.py", line 1693, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 850, in exec_module
File "", line 228, in call_with_frames_removed
File "A:\ComfyUI\custom_nodes\rgthree-comfy_init.py", line 43, in
for file in glob.glob('.py', root_dir=DIR_PY) + glob.glob('.js', root_dir=DIR_DEV_JS):
TypeError: glob() got an unexpected keyword argument 'root_dir'
Cannot import A:\ComfyUI\custom_nodes\rgthree-comfy module for custom nodes: glob() got an unexpected keyword argument 'root_dir'
WAS Node Suite: OpenCV Python FFMPEG support is enabled
WAS Node Suite: ffmpeg_bin_path is set to: C:♀fmpein
WAS Node Suite: Finished. Loaded 192 nodes successfully.
    "The best revenge is massive success." - Frank Sinatra

Import times for custom nodes:
0.0 seconds: A:\ComfyUI\custom_nodes\Pseudo_HDR_ally.py
0.0 seconds: A:\ComfyUI\custom_nodes\imageflip_ally.py
0.0 seconds: A:\ComfyUI\custom_nodes\histogram_equalization.py
0.0 seconds: A:\ComfyUI\custom_nodes\sdxl_utility.py
0.0 seconds: A:\ComfyUI\custom_nodes\gaussian_blur_ally.py
0.0 seconds: A:\ComfyUI\custom_nodes\bsz-auto-hires.py
0.0 seconds: A:\ComfyUI\custom_nodes\brightness_contrast_ally.py
0.0 seconds: A:\ComfyUI\custom_nodes\fcSuite.py
0.0 seconds: A:\ComfyUI\custom_nodes\sharpness_ally.py
0.0 seconds: A:\ComfyUI\custom_nodes\saturation_ally.py
0.0 seconds: A:\ComfyUI\custom_nodes\ksampler_sdxl.py
0.0 seconds (IMPORT FAILED): A:\ComfyUI\custom_nodes\51NfTmeV.py
0.0 seconds: A:\ComfyUI\custom_nodes\sdxl_prompt_styler
0.0 seconds: A:\ComfyUI\custom_nodes\comfyui_lora_tag_loader
0.0 seconds: A:\ComfyUI\custom_nodes\Artists_Compendium
0.0 seconds: A:\ComfyUI\custom_nodes\pfaeff-comfyui
0.0 seconds: A:\ComfyUI\custom_nodes\Mile_High_Styler
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_JPS-Nodes
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI-Custom-Scripts
0.0 seconds: A:\ComfyUI\custom_nodes\sdxl_model_merging.py
0.0 seconds: A:\ComfyUI\custom_nodes\MergeBlockWeighted_fo_ComfyUI
0.0 seconds: A:\ComfyUI\custom_nodes\masquerade-nodes-comfyui
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_Cutoff
0.0 seconds: A:\ComfyUI\custom_nodes\SeargeSDXL
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_TiledKSampler
0.0 seconds: A:\ComfyUI\custom_nodes\facedetailer
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI-Advanced-ControlNet
0.0 seconds: A:\ComfyUI\custom_nodes\wlsh_nodes
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI-post-processing-nodes
0.0 seconds: A:\ComfyUI\custom_nodes\mikey_nodes
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_SeeCoder
0.0 seconds: A:\ComfyUI\custom_nodes\ambw_comfyui
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI-QualityOfLifeSuit_Omar92
0.0 seconds (IMPORT FAILED): A:\ComfyUI\custom_nodes\DTAIComfyPromptAgent
0.0 seconds (IMPORT FAILED): A:\ComfyUI\custom_nodes\comfy_mtb
0.0 seconds (IMPORT FAILED): A:\ComfyUI\custom_nodes\ComfyUI_InterpolateEverything
0.0 seconds: A:\ComfyUI\custom_nodes\OneButtonPrompt
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI-Saveaswebp
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_UltimateSDUpscale
0.0 seconds: A:\ComfyUI\custom_nodes\comfyui-reactor-node
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_roop
0.0 seconds: A:\ComfyUI\custom_nodes\comfyui_controlnet_aux
0.0 seconds (IMPORT FAILED): A:\ComfyUI\custom_nodes\ComfyUI_FizzNodes
0.0 seconds: A:\ComfyUI\custom_nodes\Derfuu_ComfyUI_ModdedNodes
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_Comfyroll_CustomNodes
0.0 seconds (IMPORT FAILED): A:\ComfyUI\custom_nodes\ComfyUI_Load_Image_With_Metadata
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_Fooocus_KSampler
0.0 seconds: A:\ComfyUI\custom_nodes\facerestore
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_NestedNodeBuilder
0.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_Dave_CustomNode
0.1 seconds: A:\ComfyUI\custom_nodes\comfyui-prompt-control
0.1 seconds (IMPORT FAILED): A:\ComfyUI\custom_nodes\rgthree-comfy
0.1 seconds: A:\ComfyUI\custom_nodes\failfast-comfyui-extensions
0.1 seconds: A:\ComfyUI\custom_nodes\ComfyI2I
0.2 seconds: A:\ComfyUI\custom_nodes\comfyui-PromptAttention
0.3 seconds: A:\ComfyUI\custom_nodes\ComfyUI_Custom_Nodes_AlekPet
0.4 seconds: A:\ComfyUI\custom_nodes\ComfyUI-Manager
0.5 seconds: A:\ComfyUI\custom_nodes\clipseg.py
0.8 seconds: A:\ComfyUI\custom_nodes\bilbox-comfyui
1.0 seconds: A:\ComfyUI\custom_nodes\ComfyUI_tinyterraNodes
1.2 seconds: A:\ComfyUI\custom_nodes\ComfyUI-FaceSwap
1.3 seconds: A:\ComfyUI\custom_nodes\was-node-suite-comfyui
1.6 seconds: A:\ComfyUI\custom_nodes\ComfyUI_Inpaint
1.7 seconds: A:\ComfyUI\custom_nodes\efficiency-nodes-comfyui
1.9 seconds: A:\ComfyUI\custom_nodes\ComfyUI-Impact-Pack
Starting server
To see the GUI go to: http://<IP_ADDRESS>:8188
And these are the logs:
[
{
"source": "ComfyUI.Logging",
"type": "debug",
"timestamp": "2023-08-24T13:26:16.919Z",
"message": {
"UserAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
}
},
{
"source": "Comfy.App",
"type": "debug",
"timestamp": "2023-08-24T13:26:16.932Z",
"message": {
"Extensions": [
"/extensions/AlekPet_Nodes/extras_node.js",
"/extensions/AlekPet_Nodes/painter_node.js",
"/extensions/AlekPet_Nodes/pose_node.js",
"/extensions/bilbox/bilboxContextMenuEnhance.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/betterCombos.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/contextMenuHook.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/customColors.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/faviconStatus.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/graphArrange.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/imageFeed.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/kSamplerAdvDenoise.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/linkRenderMode.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/locking.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/loraInfo.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/mathExpression.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/nodeFinder.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/playSound.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/presetText.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/quickNodes.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/repeater.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/reroutePrimitive.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/showImageOnMenu.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/showText.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/snapToGrid.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/stringFunction.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/touchEvents.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/widgetDefaults.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/workflowImage.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/workflows.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/assets/canvas2svg.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/common/lightbox.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/common/spinner.js",
"/extensions/ComfyUI-Custom-Scripts/web/js/common/utils.js",
"/extensions/ComfyUI-OpenPose-Editor/fabric.min.js",
"/extensions/ComfyUI-OpenPose-Editor/openpose.js",
"/extensions/ComfyUI_NestedNodeBuilder/dialog.js",
"/extensions/ComfyUI_NestedNodeBuilder/nestedNode.js",
"/extensions/ComfyUI_NestedNodeBuilder/nodeMenu.js",
"/extensions/ComfyUI_NestedNodeBuilder/queue.js",
"/extensions/comfy_mtb/web/comfy_shared.js",
"/extensions/comfy_mtb/web/debug.js",
"/extensions/comfy_mtb/web/imageFeed.js",
"/extensions/comfy_mtb/web/mtb_widgets.js",
"/extensions/comfy_mtb/web/notify.js",
"/extensions/comfy_mtb/web/extern/parse-css.js",
"/extensions/core/clipspace.js",
"/extensions/core/colorPalette.js",
"/extensions/core/contextMenuFilter.js",
"/extensions/core/dynamicPrompts.js",
"/extensions/core/editAttention.js",
"/extensions/core/invertMenuScrolling.js",
"/extensions/core/keybinds.js",
"/extensions/core/linkRenderMode.js",
"/extensions/core/maskeditor.js",
"/extensions/core/nodeTemplates.js",
"/extensions/core/noteNode.js",
"/extensions/core/rerouteNode.js",
"/extensions/core/saveImageExtraOutput.js",
"/extensions/core/slotDefaults.js",
"/extensions/core/snapToGrid.js",
"/extensions/core/uploadImage.js",
"/extensions/core/widgetInputs.js",
"/extensions/Davemane42/MultiAreaConditioning.js",
"/extensions/Davemane42/MultiLatentComposite.js",
"/extensions/Davemane42/utils.js",
"/extensions/efficiency-nodes-comfyui/efficiency_nodes.js",
"/extensions/failfast-comfyui-extensions/arrange.js",
"/extensions/failfast-comfyui-extensions/colors.js",
"/extensions/failfast-comfyui-extensions/connectionsWidth.js",
"/extensions/failfast-comfyui-extensions/forceBoxNodes.js",
"/extensions/failfast-comfyui-extensions/forceSnapToGrid.js",
"/extensions/failfast-comfyui-extensions/groups.js",
"/extensions/failfast-comfyui-extensions/images.js",
"/extensions/failfast-comfyui-extensions/nodes.js",
"/extensions/failfast-comfyui-extensions/pinNodes.js",
"/extensions/failfast-comfyui-extensions/renderShadows.js",
"/extensions/failfast-comfyui-extensions/reroutes.js",
"/extensions/failfast-comfyui-extensions/textFields.js",
"/extensions/image-gallery/imageGallery.js",
"/extensions/rgthree/base_node_dispatcher.js",
"/extensions/rgthree/bypasser.js",
"/extensions/rgthree/context.js",
"/extensions/rgthree/display_int.js",
"/extensions/rgthree/muter.js",
"/extensions/rgthree/node_combiner.js",
"/extensions/rgthree/power_prompt.js",
"/extensions/rgthree/reroute.js",
"/extensions/rgthree/seed.js",
"/extensions/rgthree/smartswitch.js",
"/extensions/rgthree/utils.js",
"/extensions/tinyterraNodes/ttN.js",
"/extensions/tinyterraNodes/ttNdynamicWidgets.js",
"/extensions/tinyterraNodes/ttNembedAC.js",
"/extensions/tinyterraNodes/ttNinterface.js",
"/extensions/tinyterraNodes/ttNwidgets.js",
"/extensions/tinyterraNodes/ttNxyPlot.js",
"/extensions/webpinfo/webpinfo.js",
"/extensions/ComfyUI-Custom-Scripts/js/betterCombos.js",
"/extensions/ComfyUI-Custom-Scripts/js/contextMenuHook.js",
"/extensions/ComfyUI-Custom-Scripts/js/customColors.js",
"/extensions/ComfyUI-Custom-Scripts/js/faviconStatus.js",
"/extensions/ComfyUI-Custom-Scripts/js/graphArrange.js",
"/extensions/ComfyUI-Custom-Scripts/js/imageFeed.js",
"/extensions/ComfyUI-Custom-Scripts/js/kSamplerAdvDenoise.js",
"/extensions/ComfyUI-Custom-Scripts/js/linkRenderMode.js",
"/extensions/ComfyUI-Custom-Scripts/js/locking.js",
"/extensions/ComfyUI-Custom-Scripts/js/loraInfo.js",
"/extensions/ComfyUI-Custom-Scripts/js/mathExpression.js",
"/extensions/ComfyUI-Custom-Scripts/js/nodeFinder.js",
"/extensions/ComfyUI-Custom-Scripts/js/playSound.js",
"/extensions/ComfyUI-Custom-Scripts/js/presetText.js",
"/extensions/ComfyUI-Custom-Scripts/js/quickNodes.js",
"/extensions/ComfyUI-Custom-Scripts/js/repeater.js",
"/extensions/ComfyUI-Custom-Scripts/js/reroutePrimitive.js",
"/extensions/ComfyUI-Custom-Scripts/js/showImageOnMenu.js",
"/extensions/ComfyUI-Custom-Scripts/js/showText.js",
"/extensions/ComfyUI-Custom-Scripts/js/snapToGrid.js",
"/extensions/ComfyUI-Custom-Scripts/js/stringFunction.js",
"/extensions/ComfyUI-Custom-Scripts/js/touchEvents.js",
"/extensions/ComfyUI-Custom-Scripts/js/widgetDefaults.js",
"/extensions/ComfyUI-Custom-Scripts/js/workflowImage.js",
"/extensions/ComfyUI-Custom-Scripts/js/workflows.js",
"/extensions/ComfyUI-Custom-Scripts/js/assets/canvas2svg.js",
"/extensions/ComfyUI-Custom-Scripts/js/common/lightbox.js",
"/extensions/ComfyUI-Custom-Scripts/js/common/spinner.js",
"/extensions/ComfyUI-Custom-Scripts/js/common/utils.js",
"/extensions/ComfyUI-Impact-Pack/comboBoolMigration.js",
"/extensions/ComfyUI-Impact-Pack/impact-pack.js",
"/extensions/ComfyUI-Impact-Pack/impact-sam-editor.js",
"/extensions/ComfyUI-Manager/comfyui-manager.js"
]
}
},
{
"source": "ComfyUI.Logging",
"type": "debug",
"timestamp": "2023-08-24T13:26:16.945Z",
"message": {
"system": {
"os": "nt",
"python_version": "3.9.13 (tags/v3.9.13:6de2ca5, May 17 2022, 16:36:42) [MSC v.1929 64 bit (AMD64)]",
"embedded_python": false
},
"devices": {
"name": "cuda:0 NVIDIA GeForce RTX 3070 Ti : cudaMallocAsync",
"type": "cuda",
"index": 0,
"vram_total":<PHONE_NUMBER>,
"vram_free":<PHONE_NUMBER>,
"torch_vram_total": 0,
"torch_vram_free": 0
}
}
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.955Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/betterCombos.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/betterCombos.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/betterCombos.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.956Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/contextMenuHook.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/contextMenuHook.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/contextMenuHook.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.957Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/customColors.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/customColors.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/customColors.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.957Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/faviconStatus.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/faviconStatus.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/faviconStatus.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.957Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/graphArrange.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/graphArrange.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/graphArrange.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.958Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/imageFeed.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/imageFeed.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/imageFeed.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.962Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/kSamplerAdvDenoise.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/kSamplerAdvDenoise.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/kSamplerAdvDenoise.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.963Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/linkRenderMode.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/linkRenderMode.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/linkRenderMode.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.963Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/locking.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/locking.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/locking.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.963Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/loraInfo.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/loraInfo.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/loraInfo.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.964Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/mathExpression.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/mathExpression.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/mathExpression.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.964Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/nodeFinder.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/nodeFinder.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/nodeFinder.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.965Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/playSound.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/playSound.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/playSound.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.966Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/presetText.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/presetText.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/presetText.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.966Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/quickNodes.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/quickNodes.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/quickNodes.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.966Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/repeater.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/repeater.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/repeater.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.966Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/reroutePrimitive.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/reroutePrimitive.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/reroutePrimitive.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.966Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/showImageOnMenu.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/showImageOnMenu.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/showImageOnMenu.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.967Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/showText.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/showText.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/showText.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.967Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/snapToGrid.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/snapToGrid.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/snapToGrid.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.967Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/stringFunction.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/stringFunction.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/stringFunction.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.968Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/touchEvents.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/touchEvents.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/touchEvents.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.968Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/widgetDefaults.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/widgetDefaults.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/widgetDefaults.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.969Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/workflowImage.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/workflowImage.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/workflowImage.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.969Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/workflows.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/workflows.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/workflows.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.970Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/assets/canvas2svg.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/assets/canvas2svg.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/assets/canvas2svg.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.970Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/common/lightbox.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/common/lightbox.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/common/lightbox.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.971Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/common/spinner.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/common/spinner.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/common/spinner.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:16.971Z",
"message": [
"Error loading extension",
"/extensions/ComfyUI-Custom-Scripts/web/js/common/utils.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/common/utils.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/ComfyUI-Custom-Scripts/web/js/common/utils.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:17.041Z",
"message": [
"Error loading extension",
"/extensions/comfy_mtb/web/debug.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/comfy_mtb/web/debug.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/comfy_mtb/web/debug.js\n"
]
},
{
"source": "console",
"type": "error",
"timestamp": "2023-08-24T13:26:17.041Z",
"message": [
"Error loading extension",
"/extensions/comfy_mtb/web/mtb_widgets.js",
"TypeError\nFailed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/comfy_mtb/web/mtb_widgets.js\nTypeError: Failed to fetch dynamically imported module: http://<IP_ADDRESS>:8188/extensions/comfy_mtb/web/mtb_widgets.js\n"
]
},
{
"source": "console",
"type": "log",
"timestamp": "2023-08-24T13:26:17.059Z",
"message": "[BilboX] Installing bilbox.css..."
},
{
"source": "console",
"type": "warn",
"timestamp": "2023-08-24T13:26:17.060Z",
"message": "[mtb] - Aborting the loading of mtb's imageFeed in favor of pysssss.ImageFeed"
},
{
"source": "console",
"type": "log",
"timestamp": "2023-08-24T13:26:17.794Z",
"message": [
"%c[🐍 pysssss]",
"color: limegreen",
"Skipping LinkRenderMode as core extension found"
]
}
]
It's probably just a problem on my end because i'm very new with python environments in general but thanks for looking.

On the latest one im not seeing any errors for my scripts? And it still isn't working?
Can you try downloading a fresh build from: https://github.com/comfyanonymous/ComfyUI/releases/tag/latest
And only set up one extension at a time to see where it breaks. I'm seeing errors from a bunch of custom nodes that might be causing issues

Yeah, thanks for the help, but i don't think it's this script. They just aren't showing up because of some other node error probably. But i'm on a local install and the last problem I have seems to be with mtb nodes.

All fixed, deleted mtb nodes and I had the json file set to True instead of true


Windows + Ninja + MSVC + CMakePresets.json - does this combination work?

Brief Issue Summary
I created the simplest HelloWorld project using CMakePresets.json, using the standard Ninja generator and CMake couldn't find MSVC. I couldn't work out a solution using the docs.
I switched to Ninja Multi-Config it just worked. The Visual Studio 2022 generator also works.
Is there anything special that needs to be done to use the Ninja generator on Windows with Visual Studio 2022 or there is an issue?

Hi @Zingam, we're going to need more information/logs.  I've been doing quite a bit of testing this week with Windows + Ninja + MSVC + CMakePresets and it works fine for me.
Please share your CMakePresets.json and the output from the CMakeL Log Diagnostics command.  It would also be helpful to have the debug logs too if you're able to share them (set cmake.loggingLevel to "debug" and reload the window)

I probably did something wrong with the Ninja preset as I seemingly got it working now. So I apologize for the trouble.
Yet this made me wonder why isn't the extension using the same mechanism already implemented by the "compiler kits" to select from a list of available compilers.
The above instead of:
"architecture": {
   "value": "x64",
   "strategy": "set"
},
"cacheVariables": {
   "CMAKE_BUILD_TYPE": "Debug",
   "CMAKE_C_COMPILER": "cl",
   "CMAKE_CXX_COMPILER": "cl",
   "CMAKE_INSTALL_PREFIX": "${sourceDir}/out/install/${presetName}"
 },

I use the extension on macOS and Linux primarily where it just picks up the default compiler and everything is smooth.
I dislike the idea to have to hardcode the COMPILER variables or to make even more User preset combinations.

Yet this made me wonder why isn't the extension using the same mechanism already implemented by the "compiler kits" to select from a list of available compilers.

If you configure with presets outside of VS Code, the "kits" aren't used.  Presets is intended to be portable across environments.  You can get away with not setting the C and CXX compiler variables in some cases, but it will depend on your environment how CMake will pick the compiler and we don't guarantee the same results in CMake Tools.

If cmake is run on the command line it should be run in a vsvars.bat shell anyway.

Yes, Ninja + MSVC requires the VS build environment to be pre-configured.  But we don't know to do that for you automatically unless you specify "cl" as the compiler.  What if the developer wanted clang/gcc on Windows instead?  It's less of an issue on mac/linux because the default compilers there (gcc/clang) don't require a bunch of environment variables to be set.

@Zingam
The following are my examples of CMakePresets.json using MSVC compilers with Ninja/Ninja Multi-Config generators. You can take them for reference.
According to my experience and research, you need to specify 3 settings in Configure Presets:

"toolset" field with "external" strategy.
"architecture" field with "external" strategy.
Environemnt Variables or Cache Variables for MSVC compiler.

{
  "version": 3,
  "cmakeMinimumRequired": {
    "major": 3,
    "minor": 21,
    "patch": 0
  },
  "configurePresets": [
    {
      "name": "win32-msvc16-x64-ninja-debug",
      "displayName": "Windows MSVC16 x64 (Ninja) Debug",
      "description": "Using MSVC16 x64 compiler with \"Ninja\" generator on Windows - Debug",
      "generator": "Ninja",
      "toolset": {
        "value": "v142,host=x64",
        "strategy": "external"
      },
      "architecture": {
        "value": "x64",
        "strategy": "external"
      },
      "cacheVariables": {
        "CMAKE_C_COMPILER": "cl.exe",
        "CMAKE_CXX_COMPILER": "cl.exe",
        "CMAKE_BUILD_TYPE": "Debug"
      }
    },
    {
      "name": "win32-msvc17-x64_x86-ninja-multi",
      "displayName": "Windows MSVC17 x64_x86 (Ninja Multi-Config)",
      "description": "Using MSVC17 x64_x86 compiler with \"Ninja Multi-Config\" generator on Windows",
      "generator": "Ninja Multi-Config",
      "toolset": {
        "value": "v143,host=x64",
        "strategy": "external"
      },
      "architecture": {
        "value": "x86",
        "strategy": "external"
      },
      "cacheVariables": {
        "CMAKE_C_COMPILER": "cl.exe",
        "CMAKE_CXX_COMPILER": "cl.exe"
      }
    }
  ]
}

@Zingam
The following are my examples of CMakePresets.json using MSVC compilers with Ninja/Ninja Multi-Config generators. You can take them for reference.
According to my experience and research, you need to specify 3 settings in Configure Presets:

"toolset" field with "external" strategy.
"architecture" field with "external" strategy.
Environemnt Variables or Cache Variables for MSVC compiler.

{
  "version": 3,
  "cmakeMinimumRequired": {
    "major": 3,
    "minor": 21,
    "patch": 0
  },
  "configurePresets": [
    {
      "name": "windows-only",
      "displayName": "Windows-only configuration",
      "description": "This build is only available on Windows",
      "cmakeExecutable": "C:/Program Files/CMake/bin/cmake.exe",
      "binaryDir": "${sourceDir}/build/${presetName}",
      "installDir": "${sourceDir}/install/${presetName}",
      "hidden": true,
      "condition": {
        "type": "equals",
        "lhs": "${hostSystemName}",
        "rhs": "Windows"
      }
    },
    {
      "inherits": "windows-only",
      "name": "win32-msvc16-x64-ninja-debug",
      "displayName": "Windows MSVC16 x64 (Ninja) Debug",
      "description": "Using MSVC16 x64 compiler with \"Ninja\" generator on Windows - Debug",
      "generator": "Ninja",
      "toolset": {
        "value": "v142,host=x64",
        "strategy": "external"
      },
      "architecture": {
        "value": "x64",
        "strategy": "external"
      },
      "cacheVariables": {
        "CMAKE_C_COMPILER": "cl.exe",
        "CMAKE_CXX_COMPILER": "cl.exe",
        "CMAKE_BUILD_TYPE": "Debug"
      }
    },
    {
      "inherits": "windows-only",
      "name": "win32-msvc17-x64_x86-ninja-multi",
      "displayName": "Windows MSVC17 x64_x86 (Ninja Multi-Config)",
      "description": "Using MSVC17 x64_x86 compiler with \"Ninja Multi-Config\" generator on Windows",
      "generator": "Ninja Multi-Config",
      "toolset": {
        "value": "v143,host=x64",
        "strategy": "external"
      },
      "architecture": {
        "value": "x86",
        "strategy": "external"
      },
      "cacheVariables": {
        "CMAKE_C_COMPILER": "cl.exe",
        "CMAKE_CXX_COMPILER": "cl.exe"
      }
    }
  ]
}

@hwhsu1231 Thank you! I'll try your solution. I also got it to work. I did something wrong intimacy later I managed to get it working and I am quick to complain.

Yet this made me wonder why isn't the extension using the same mechanism already implemented by the "compiler kits" to select from a list of available compilers.

If you configure with presets outside of VS Code, the "kits" aren't used. Presets is intended to be portable across environments. You can get away with not setting the C and CXX compiler variables in some cases, but it will depend on your environment how CMake will pick the compiler and we don't guarantee the same results in CMake Tools.

If cmake is run on the command line it should be run in a vsvars.bat shell anyway.

Yes, Ninja + MSVC requires the VS build environment to be pre-configured. But we don't know to do that for you automatically unless you specify "cl" as the compiler. What if the developer wanted clang/gcc on Windows instead? It's less of an issue on mac/linux because the default compilers there (gcc/clang) don't require a bunch of environment variables to be set.

My idea is: to also have the option with a single CMake preset to automatically selecting the compiler via the kits option. Would that be theoretically possible and practically feasible?
Technically this workflow can be done with User presets but then I still have to figure out where my compilers are located manually.
This would be convenient for a quick, lazy project setup.
I hope I have explained my case clearly.

My idea is: to also have the option with a single CMake preset to automatically selecting the compiler via the kits option. Would that be theoretically possible and practically feasible?

It's theoretically possible.  In CMakePresets.json, it is possible to add additional data in the 'vendor' field and CMake will ignore that.  I don't think we'll do it though, because the purpose of presets is to be able to create a portable configuration that both CMake and the IDE's can understand.  Such a configuration would suffer from working only in VS Code with our extension.
To aid you in creating presets that are tied to Kits, though, we added a "Add Configure Preset" command that lets you use one of the Kits as a starting point.  (Though I see there's a problem with those commands appearing that I am fixing with #2977)

@bobbrow I've written a short CMake script, that extracts the environment from any of the MSBuild PlatformToolset's BuiltTask. What it it does is that it runs the set command of cmd.exe both from the env of the caller and inside a dummy MSBuild project inside an add_custom_command, then it computes a delta of the two environments and saves it in a file of the user's choice in CMakePresets format. I include this file in my CMakeUserPresets.json so that I need no equivalent to environmentSetupScript in presets. My issue is that CMake Tools seems to completely disregard the environment I setup this way. MSVC happens to work from VS Code (because the compiler is set as cl.exe, but clang-cl.exe doesn't, even though from the command-line this approach works flawlessly. Using the script I do something like:
{
	"version": 4,
	"cmakeMinimumRequired": {
		"major": 3,
		"minor": 22,
		"patch": 0
	},
	"include": [
		"C:\\Users\\mate\\OneDrive\\Develop\\Visual Studio\\Toolchain-MSVC-MakefileGenerators.json",
		"C:\\Users\\mate\\OneDrive\\Develop\\Visual Studio\\Toolchain-ClangCL-MakefileGenerators.json"
	],
	"configurePresets": [
		{
			"name": "generator-ninja-multi-config",
			"hidden": true,
			"generator": "Ninja Multi-Config",
			"cacheVariables": {
				"CMAKE_MAKE_PROGRAM": "C:\\Kellekek\\Ninja\\bin\\ninja.exe"
			},
			"architecture": {
				"value": "x64",
				"strategy": "external"
			}
		},
		{
			"name": "toolchain-makefiles-c/c++-msvc-v143",
			"hidden": true,
			"cacheVariables": {
				"CMAKE_C_COMPILER": "cl.exe",
				"CMAKE_C_LINK_EXECUTABLE": "link.exe",
				"CMAKE_CXX_COMPILER": "cl.exe",
				"CMAKE_CXX_LINK_EXECUTABLE": "link.exe",
				"CMAKE_RC_COMPILER": "rc.exe",
				"CMAKE_MT": "mt.exe"
			},
			"toolset": {
				"value": "v143,version=14.34,host=x64",
				"strategy": "external"
			}
		},
		{
			"name": "toolchain-makefiles-c/c++-clangcl",
			"hidden": true,
			"cacheVariables": {
				"CMAKE_C_COMPILER": "clang-cl.exe",
				"CMAKE_C_LINK_EXECUTABLE": "llvm-link.exe",
				"CMAKE_CXX_COMPILER": "clang-cl.exe",
				"CMAKE_CXX_LINK_EXECUTABLE": "llvm-link.exe",
				"CMAKE_RC_COMPILER": "rc.exe",
				"CMAKE_MT": "mt.exe"
			},
			"toolset": {
				"value": "ClangCL,version=14.34,host=x64",
				"strategy": "external"
			}
		},
		{
			"name": "msvc-arch-native-strict-iso-high-warn",
			"hidden": true,
			"cacheVariables": {
				"CMAKE_C_FLAGS": "/arch:AVX2 /W4",
				"CMAKE_CXX_FLAGS": "/arch:AVX2 /EHsc /permissive- /W4"
			}
		},
		{
			"name": "clangcl-arch-native-strict-iso-high-warn",
			"hidden": true,
			"cacheVariables": {
				"CMAKE_C_FLAGS": "/arch:AVX2 /W4 -fuse-ld=llvm-link",
				"CMAKE_CXX_FLAGS": "/arch:AVX2 /EHsc /permissive- /W4 -fuse-ld=llvm-link"
			}
		},
		{
			"name": "ninja-msvc-v143",
			"displayName": "Ninja MSVC v143",
			"inherits": [
				"layout",
				"generator-ninja-multi-config",
				"toolchain-makefiles-c/c++-msvc-v143",
				"developer-command-prompt-msvc-v143-x64",
				"msvc-arch-native-strict-iso-high-warn"
			]
		},
		{
			"name": "ninja-clangcl",
			"displayName": "Ninja ClangCL",
			"inherits": [
				"layout",
				"generator-ninja-multi-config",
				"toolchain-makefiles-c/c++-clangcl",
				"developer-command-prompt-clangcl-x64",
				"clangcl-arch-native-strict-iso-high-warn"
			]
		}
	],
	"buildPresets": [
		{
			"name": "ninja-parallel",
			"hidden": true,
			"nativeToolOptions": [
				"-j$env{NUMBER_OF_PROCESSORS}"
			]
		},
		{
			"name": "ninja-verbose",
			"hidden": true,
			"verbose": true
		},
		{
			"name": "ninja-msvc-v143-debug",
			"displayName": "Debug",
			"configuration": "Debug",
			"configurePreset": "ninja-msvc-v143",
			"inherits": [
				"ninja-parallel"
			]
		},
		{
			"name": "ninja-msvc-v143-release",
			"displayName": "Release",
			"configuration": "Release",
			"configurePreset": "ninja-msvc-v143",
			"inherits": [
				"ninja-parallel"
			]
		},
		{
			"name": "ninja-clangcl-debug",
			"displayName": "Debug",
			"configuration": "Debug",
			"configurePreset": "ninja-clangcl",
			"inherits": [
				"ninja-parallel"
			]
		},
		{
			"name": "ninja-clangcl-release",
			"displayName": "Release",
			"configuration": "Release",
			"configurePreset": "ninja-clangcl",
			"inherits": [
				"ninja-parallel"
			]
		}
	]
}

If it works outside the IDE, I would like CMake Tools to play along with this setup. This is the closest I could get to telling CMake via a preset how to use a toolchain without setting up the environment otherwise.

@bobbrow Any update on this? CMake Tools and Presets which set their own environment still don't mix well.

For anyone encountering this issue and spending hours on figuring it out, I can confirm that what @hwhsu1231 wrote above indeed seems to work.
The trick for using "generator": "Ninja" together with Visual Studio 2022 Build Tools is adding the following to your preset:
"toolset": {
    "value": "v143,host=x64",
    "strategy": "external"
},
"architecture": {
    "value": "x64",
    "strategy": "external"
},

and
"cacheVariables": {
    "CMAKE_C_COMPILER": "cl.exe",
    "CMAKE_CXX_COMPILER": "cl.exe",
    ... anything else you want ...
}

Without these, it does not work and it will complain that it cannot find Ninja and the compilers.

Even if I set:
"toolset": {
    "value": "v143,host=x64",
    "strategy": "external"
},
"architecture": {
    "value": "x64",
    "strategy": "external"
},
"cacheVariables": {
    "CMAKE_C_COMPILER": "cl.exe",
    "CMAKE_CXX_COMPILER": "cl.exe"
}

it complains for me that it cannot find Ninja with:
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
Even if I set CMAKE_MAKE_PROGRAM to point to the ninja executable, it still complains with the same error.
However if I launch VS Code from the "Developer Command prompt for VS 2022" all works fine. I would like to avoid launching from that or messing with the environment variables.
This used to work for me, but stopped working on two independent computers for me in the recent weeks. Has anything changed regarding how this should be setup?
I am using vcpkg and thus also setting CMAKE_TOOLCHAIN_FILE if that is of importance.

@Zitrax To my knowledge nothing has been changed regarding how this is setup, but hopefully we can chat and see what might be going on.
How were you defining CMAKE_MAKE_PROGRAM?

I tried:
"CMAKE_MAKE_PROGRAM": "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe"

this path has been verified to exist.
This time it moves on (not sure why it did not last time), but stops at:
[cmake] CMake Error at CMakeLists.txt:2 (project):
[cmake]   The CMAKE_CXX_COMPILER:
[cmake]
[cmake]     cl.exe
[cmake]
[cmake]   is not a full path and was not found in the PATH.

So next I try to provide the full path to cl.exe, but it leads to new errors:
[cmake]     RC Pass 1: command "rc /fo CMakeFiles\cmTC_6c10a.dir/manifest.res CMakeFiles\cmTC_6c10a.dir/manifest.rc" failed (exit code 0) with the following output:
[cmake]     The system cannot find the file specified

when it's testing the compiler. But specifying full paths to everything feels wrong anyway so I assume something else is wrong.
I also tried to repair the VS 2022 install and toggling some of the options there on and off without further luck. I also tried to download "Build Tools for Visual Studio 2022".
One possible oddity is that I do not have VS installed on the C drive but another drive letter.
Unsure how I should debug it further.


Update it_IT

@yaichenbaum let's not loose hope to have a fully translated 1.0 version 😂

@yaichenbaum let's not loose hope to have a fully translated 1.0 version 😂

We still have some time for it to happen 😃


Testcafe changes AJAX Requests

What is your Test Scenario?
We would like to test a Wicket application that frequently uses AJAX queries.
Large parts of the page are changed by AJAX Behaviour.
What is the Current behavior?
The AJAX request is answered by the server, but Testcafe builds its own HTML code for it...
Because of the manipulated Response the Application does not work.
Original HTML
<?xml version="1.0" encoding="UTF-8"?><ajax-response><component id="paneld6d" ><![CDATA[

Veräußerer erfassen

    ...

Manipulated HTML
<meta class="charset-hammerhead-shadow-ui" charset="utf-8"><link rel="stylesheet" type="text/css" class="ui-stylesheet-hammerhead-shadow-ui" href="http://<IP_ADDRESS>:51248/testcafe-ui-styles.css"><ajax-response><component id="panel1a0">

Veräußerer erfassen

    ...

What is the Expected behavior?
Since we have not set up a HOOK, Testcafe should not manipulate this request.
What is your web application and your TestCafe test code?
This is not possible.
Your website URL (or attach your complete example): Internal
Test Call:
  await t.click(Selector('input').withAttribute('data-ref', 'addDetails'));

Your Environment details:

testcafe version:                   1.1.0
node.js version:                    v10.15.1
command-line arguments:  testcafe firefox testVerwaltung.js
command-line arguments:  testcafe ie testVerwaltung.js
browser name and version: IE 11, Firefox 60.3.0esr
platform and version:          Windows 10 1809
Apache Wicket:                   7.10.0

This is definitely incorrect that this information is added to the ajax response on your side.  However, I was not able to reproduce this behavior using Wicket examples (e.g. http://examples8x.wicket.apache.org/ajax/autocomplete).  Thus, the information we currently have is not sufficient to find the cause of the issue. Could you please provide a small example so that we can reproduce it on our side?

Yes I will prepare a test case that can be downloaded as ZIP. Please give me some time.

Thanks, we'll wait for it.

I prepared a test case: https://github.com/MBurchard/testcafe-3634
But don't rejoice too soon, the test case doesn't lead to the problem.
That's why I took two screenshots. Both are take on the same machine with same version of Testcafe.

The first one is from the testcase I provided. This simply starts a small SpringBoot App locally.

The second one starts a complex portal framework on the local tomcat.
As one can see, the headers are a little different.
May it be, that because of Content-Type or other header parameters Testcafe injects some content into the AJAX Response?
Is this hint sufficient for further research?
What else could I do?

@MBurchard
Since your provided test case doesn't lead to the problem, I'm not able to determine the cause of this issue.

Please provide us with a simple project (or public URL) so we can research it on our side.