Skip internal scripts for breakpoints without printing an error

Closes #35211.
This removes:
ERROR: get_breakpoints: Condition ' base.begins_with("local://")

while running a project with blank scripts caused by deleting (#33313) or moving (#27635), or built-in scripts which are not yet saved within a scene on running a project.
This simply prevents the error to be printed. The check for internal scripts is handled without printing any errors in other places within the plugin already, I don't see why this should print an error here (I've always found it annoying from "Day 1" I started using Godot).
This part of code predates the time Godot was made open-source.

Thanks!

Cherry-picked for 3.2.3.


Error: Cannot initialize VectorStoreIndex without nodes or indexStruct

using latest create llamaindex project with next.js
using pdf in data folder.
We run npm run generate but index_store.json is not created.
We then try to run npm run dev and once we try a chat we get this error.

Hi @nstylianides what are your other options when creating llama app? I had a try on NextJS template but could not reproduce you issue:
❯ npx create-llama@latest
✔ What is your project named? … my-app
✔ Which template would you like to use? › Agentic RAG (e.g. chat with docs)
✔ Which framework would you like to use? › NextJS
✔ Would you like to set up observability? › No
✔ Please provide your OpenAI API key (leave blank to skip): …
✔ Which data source would you like to use? › Use an example PDF
✔ Would you like to add another data source? › No
✔ Would you like to use LlamaParse (improved parser for RAG - requires API key)? … no / yes
✔ Would you like to use a vector database? › No, just store the data in the file system
✔ Would you like to build an agent using tools? If so, select the tools here, otherwise just press enter ›
✔ How would you like to proceed? › Generate code, install dependencies, and run the app (~2 min)

If you don't have index_store.json in the cache folder then i guess you had chosen the No data source option. Please make sure you had a file in the data folder.

Hi there. I have resolved the issue by using WSL env in my windows.
When using llamaindex index in windows i have concluded to the following:

Python example in Windows it works.
LlamaIndex.ts in windows it always fails to create the index_store.json
LlamaIndex.ts in windows WSL it works like a charm.

I am not sure what is the issue since error reporting is either missing or confusing. e.g. "contextWindow" could be easily confused with browser context windows.
THANK YOU FOR THIS LIBRARY for it can be a swiss knife in every dev toolset.
But, IMHO, it needs much better documentation, reference and howto based on cases.
Is there an official Course on how to better utilize the Llmaindex library?

closing this as we're running a e2e test using windows with LlamaIndex.ts. @nstylianides fill free to reopen with a reproducible test case


Improve integration test

Improve integration tests to select System APIs without using type as SYSTEM due to changes being introduced in following PR https://github.com/wso2/carbon-identity-framework/pull/5108

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6969264771

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6969264771
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/6976274720

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/6976274720
Status: success


[BUG] Add XWBO special close days on the last trading day of the year since 2017.

This PR is to add a special close day for XWBO on the last trading day of the year. This is similar to XETR, with minor differences:

This was introduced in 2017; see https://www.wienerborse.at/en/news/vienna-stock-exchange-news/modified-trading-hours-on-last-trading-day-29-december-2017/
The closing auction for equities starts at 14:15 CET.

Notes:

I've put a link to the search form on XWBO's website into the code which can be used to pull up all the official announcements regarding the last trading day of the year. Can be used to check past and future behaviour.
The closing time is the time the closing auction for equities starts. I think this is in line with other exchanges.
Bonds e.g. close a bit later, so this is not reflected.

BTW: There seems to be a bug, possibly in the base TradingCalendar class. When I amended the XWBO CSV file with the remaining handful of dates for 2020, some tests failed since the calendar apparently didn't see 2020-12-30 as a special close day (which it was since it was the last trading day of the year). Adding 2021-01-04 (the first trading day of the new year) to the CSV fixed that issue.
I'm not sure where exactly the bug is located, but it has to do with creating a calendar with an end date x, where the last trading day before x is a special close (or open?) day. Maybe worth checking.
This doesn't show up e.g. for XETR since the corresponding CSV doesn't stops a few days before Christmas, so it doesn't end with the last trading day of the year which is also a half day.

Thanks - good catch here. All the code changes LGTM.
I suspect that there's some issue with searching through the array of holidays. Do you mind filing an issue on that and I'll take a look?

Thanks - good catch here. All the code changes LGTM.
I suspect that there's some issue with searching through the array of holidays. Do you mind filing an issue on that and I'll take a look?

Thanks - good catch here. All the code changes LGTM.
I suspect that there's some issue with searching through the array of holidays. Do you mind filing an issue on that and I'll take a look?

sure

Thanks - good catch here. All the code changes LGTM.
I suspect that there's some issue with searching through the array of holidays. Do you mind filing an issue on that and I'll take a look?

sure


Restrict thread checks to the main thread

This is some implementation for the middle ground solution I've proposed in #802 .
Store(initialState:... should always run on the main thread and thread safety is checked at runtime.
Store.uncheckedThreadStore(initialState:... are stores opting out from thread safety checks. This initializer should be used for background stores.

Maybe uncheckedThreadStore should be renamed withUncheckedThread.

This looks like it would definitely solve the problems we are seeing 👍

This probably should be closed in favor of #807.


openssl s_time does not work well

I am testing the tls1.3 handshake speed using the s_time command.
I created a server with an ECDSAP256 certificate and a server with an RSA3072 certificate. Both of them are signed by a self-signed root CA.
The test result shows here:
Server with RSA
7380 connections in 5.02s; 1470.12 connections/user sec, bytes read 0
7380 connections in 31 real seconds, 0 bytes read per connection

Server with P256
19755 connections in 16.49s; 1198.00 connections/user sec, bytes read 0
19755 connections in 31 real seconds, 0 bytes read per connection

In theory, ECDSA should perform better than RSA in the same security level but the test result shows the opposite.
There is another problem. I find that the test result for adding the -new flag and adding the -reuse flag is basically the same.
Server with RSA with -new
6221 connections in 4.24s; 1467.22 connections/user sec, bytes read 0
6221 connections in 31 real seconds, 0 bytes read per connection

Server with RSA with -reuse
6325 connections in 4.26s; 1484.74 connections/user sec, bytes read 0
6325 connections in 31 real seconds, 0 bytes read per connection

Then I added -msg on the server-side. I found that for both situations, the CertificateVerify message is sent. However, in tls1.3 doing session resumption should not send the CertificateVerify message.
My test commands are here, $1 will be replaced by folder names:
openssl s_server -key $1_test/server/server.key -cert $1_test/server/server.pem -accept 4330 -CAfile $1_test/rootCA/demoCA/root.pem -verify_return_error -msg -msgfile outfile.txt

openssl s_time -connect localhost:4330 -CAfile $1/rootCA/demoCA/root.pem

My questions are:
Why the test result using s_time is different from the theory?
What are the difference between using -new and -reuse flags?

Can you reproduce the issue in "stock builds", i.e., builds not done by you? Do the results remain as reported across different and longer repetitions? What is your execution environment? Dedicated machine (architecture? OS? etc) or VM (notoriously known for "surprising" handshake timing results)?

Can you reproduce the issue in "stock builds", i.e., builds not done by you? Do the results remain as reported across different and longer repetitions? What is your execution environment? Dedicated machine (architecture? OS? etc) or VM (notoriously known for "surprising" handshake timing results)?

I have tried to reproduce the issue on different computer with different OpenSSL version (1.1.1m, 1.1.1, 1.1.1f) and I always get the same result. I will try to find my friend to test it again next. I also run the test for many times so the result should be reliable. My execution environment is Ubuntu 18.04 LTS, not virtual machine

Thanks for the additional information. Could you possibly share the script(s) to reproduce your runs? Key/cert gen through server/client setup and actual s_time calls? Most importantly, I'm curious what value is used for verify [depth] (and/or how the results differ with different cert check depths) -- but also I'd like to run it in my test env...

Thanks for the additional information. Could you possibly share the script(s) to reproduce your runs? Key/cert gen through server/client setup and actual s_time calls? Most importantly, I'm curious what value is used for verify [depth] (and/or how the results differ with different cert check depths) -- but also I'd like to run it in my test env...

Yeah sure!
My experiment files are here
test1.zip
This is the test describe in this post. It contains two folder named ecc_test and rsa_test. In ecc_test contains a root CA and a server. The server has a certificate signed by root CA using ECDSAP256. In rsa_test everything are the same except that the signature algorithm is RSA3072
ALL $1 in the command need to be replaced by folder name (i.e. ecc_test or rsa_test).
The server is set up using this command:
openssl s_server -key $1_test/server/server.key -cert $1_test/server/server.pem -accept 4433 -verify_return_error -www -state.
The s_time is specified here:
openssl s_time -connect localhost:$4433 -CAfile $1_test/rootCA/demoCA/root.pem -new
Before testing with s_time, I usually run s_client first to make sure that the handshake has no error. Here is my s_client command:
openssl s_client -connect localhost:4433 -CAfile $1_test/rootCA/demoCA/root.pem -verify_return_error -state

I can also provide files for another test described here #363
test2.zip
This test contains two folder sp256_crsa_test and srsa_cp256_test.
sp256_crsa_test contains a root CA, a server and a client. The server has certificate signed by the root CA using ECDSAP256. The client has certificate signed by the root CA using RSA3072.
srsa_cp256_test contains a root CA, a server and a client. The server has certificate signed by the root CA using RSA3072. The client has certificate signed by the root CA using ECDSAP256.
Test commands I used are here:
Set up server
openssl s_server -key $1/server/server.key -cert $1_test/server/server.pem -accept 4433 -CAfile $1/rootCA/demoCA/root.pem -verify_return_error -Verify 1 -www -state
Test handshake
openssl s_client -key $1/client/client.key  -cert $1/client/client.pem -connect localhost:4433 -CAfile $1/rootCA/demoCA/root.pem -verify_return_error -state
Test handshake performance
openssl s_time -key $1/client/client.key -cert $1/client/client.pem -connect localhost:4433 -CAfile $1/rootCA/demoCA/root.pem -new

Thanks for sharing your setup. Below some observations:

In theory, ECDSA should perform better than RSA in the same security level but the test result shows the opposite.

As per your measurements: 19755 P256 connections in 31 secs vs. 7380 RSA connections in 31 secs indicates that P256 is clearly faster than RSA -- as expected.
I do agree that the measurement statement about "user time" is pretty misleading, though. It surely is worth while understanding the deviation between wall clock time and "user time" collected by https://github.com/openssl/openssl/blob/db44b55aaa42141921217183667800425227b658/apps/s_time.c#L311

I find that the test result for adding the -new flag and adding the -reuse flag is basically the same.

In my own runs, these measurements are not the same. They are similar, agreed, but consistently -new performs worse than -renew -- as one would expect it. I do agree that the difference (ca. 5%) is very low, though: Shouldn't connection reuse be much faster than new connection establishment? What puzzles me is that the letter 'r' is never output when running the connection reuse test as it would be expected when reading the code for this: https://github.com/openssl/openssl/blob/db44b55aaa42141921217183667800425227b658/apps/s_time.c#L377-L378
So you see the same ("*") output? If so, the question is: Why is connection reuse apparently never done even though the same scon object is passed at each iteration?  https://github.com/openssl/openssl/blob/db44b55aaa42141921217183667800425227b658/apps/s_time.c#L361
Some code digging required, it seems...

Is this resumption supported in OpenSSL?

I'd absolutely say so: See for example https://www.openssl.org/docs/manmaster/man3/SSL_psk_server_cb_func.html . What puzzles me though, is that s_time doesn't call SSL_CTX_set_psk_use_session_callback. This to me would indicate that s_time doesn't handle PSK and accordingly doesn't "re-create" "session resume" in "TLS1.3 style". The one statement hinting at that is
Because this program does not have all the options of the [openssl-s_client(1)](https://www.openssl.org/docs/man3.0/man1/openssl-s_client.html) program to turn protocols on and off, you may not be able to measure the performance of all protocols with all servers.

(from https://www.openssl.org/docs/man3.0/man1/openssl-s_time.html)
--> TLS1.3 PSK seems to be such option (missing from s_time and hence not usable there). So I guess one would have to add the code for setting up PSK (and users also should not forget to set it when starting the server).
This question in my eyes is resolved, thus.
It might lead to someone opening an explicit ticket to support TLS1.3 PSK to enable "TLS1.3 reuse" s_time runs, though.

Then I found the code of double app_tminterval(int stop, int usertime)

This is platform-dependent code to determine user time that looks good to me. The real question is why is there such a big difference between user time and wall clock time -- and why does the difference seem larger for P256 than RSA?
The only one reason I can think of is that much more data is transported for RSA keys. As this time most likely is not accounted for in user time tracking, EC appears worse than RSA: More EC connections are made, requiring more user CPU time to process them. But then again, one could argue this reporting makes sense: only the time spent to operate the EC/RSA crypto is counted -- which in turn seems to indicate better optimizations for RSA code to exist than for EC code. But that's something openssl speed should answer: What's the (3kRSA vs P256EC comparative) results there on your machine? At least on mine, P256 ECDSA verify is slower that 3kRSA verify -- which arguably explains the (lack in) compute time difference (per iteration).
In other words, these numbers (ECC/RSA [non-]difference) seem to make sense, also resolving this question.

Thanks for your patient reply, but I still have the last question.

What's the (3kRSA vs P256EC comparative) results there on your machine?

On my machine, 3kRSA indeed verifies faster than P256EC. I understand what you mean. 3kRSA has a larger size for key and signature so it needs more time to be processed. This processing time may not be included in user time tracking. This explanation indeed makes sense for this case.
However, this couldn't explain the second test I mentioned here: https://github.com/openssl/openssl/issues/17964#issuecomment-1082548884
Allow me to describe the test again:
I set two Groups of server-client:

Group1 contains a Server1 with a RSA3072 certificate and a Client1 with a ECDSAP256 certificate
Group2 contains a Server2 with a ECDSAP256 certificate and a Client2 with a RSA3072 certificate

Then I run mutual authentication test (both server and client need to check each other's certificate) using s_time. The test result is shown here:

Group1:
5696 connections in 5.46s; 1043.22 connections/user sec, bytes read 0
5696 connections in 31 real seconds, 0 bytes read per connection

Group2:
5652 connections in 23.03s; 245.42 connections/user sec, bytes read 0
5652 connections in 31 real seconds, 0 bytes read per connection

In your theory, the user time and the speed for process handshake of these two groups should be roughly the same. But here the first group is significantly faster than the second group.
Could you please help me explain this? Is it because the user time here only counts client verify server but does not count server verify client?

In your theory, the user time and the speed for process handshake of these two groups should be roughly the same.

No, they should not be roughly the same: What the two setups/groups do is a) introduce private key operations on the client side and b) turn around the amount of public/private key processing on the client side: In Group 1 the client needs to do P256 signing, in Group 2 it needs to do RSA signing. Now, at least on my machine, RSA3k private key ops are much slower than P256 private key ops. Accordingly, Group 2 needs more time per connection. This measurement actually confirms my theory.

Is it because the user time here only counts client verify server but does not count server verify client?

No, it's because of client auth effort/time accruing on the client side.

No, they should not be roughly the same

As you said if we only consider the operation on the client-side, then the result is reasonable. However, I think the handshake should also contain the server-side.
For group 1 the server needs to do RSA signing. For group 2 the server needs to do ECDSA signing. Therefore, for both groups, the handshake should contain one RSA signing, one ECDSA signing, two RSA verifying, and two ECDSA verifying. That is why I said the connection speed for these two groups should be roughly the same.

No, it's because of client auth effort/time accruing on the client-side.

Sorry that I am not very clear about what does this sentence mean. Do you mean that s_time only measures the auth time on the client side?
If you mean that s_time only measures the user auth time on the client-side then indeed group1 should be faster than group2.

No, they should not be roughly the same

As you said if we only consider the operation on the client-side, then the result is reasonable. However, I think the handshake should also contain the server-side. For group 1 the server needs to do RSA signing. For group 2 the server needs to do ECDSA signing. Therefore, for both groups, the handshake should contain one RSA signing, one ECDSA signing, two RSA verifying, and two ECDSA verifying. That is why I said the connection speed for these two groups should be roughly the same.

They are roughly the same if you look at the number of total connections in the same amount of wall-clock time (31 secs).
For historical reasons, the average is reported in terms of connections / user-seconds and that is where you see a difference in the 2 groups: user-time is the time spent in userland (so it excludes all time spent between handing over data to the operating system to ship over TCP to the other peer, time the data travels over the network, time spent by the peer's OS handling received traffic, time spent on userland computation on the peer, time spent by the peer's OS to handle the response, time spent by the response to travel over the network, and finally time spent by the local OS to handle the incoming traffic and give it back to s_time userland to do some more computation).
When looking at user-time like s_time does by default, you have a client centric measure of how many handshakes per second you can do, so group1 and group2 looks drastically different in user-time because it changes which side is doing the more expensive operation!

OK, I now understand. After clarifying the definition of user time all the test results are now reasonable. Thank @baentsch and @romen for your warm reply! The question is solved so I will just close this problem. Again, truly appreciate your answer and your help!


code collation

…les in the preemption plugin
Ⅰ. Describe what this PR does

optimise the handling of error
optimise the initialisation logic of variables in the preemption plugin

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/approve


📦 NEW: Web sec consultant ChatBot example

📦 NEW: Web sec consultant ChatBot example based on https://beta.langbase.com/examples/web-sec-consultant
The following files were updated

readme (authors, image, bullet points, codeblocks, pipelinks)
header comp (pipe links)
layout comp (metadata)
package.json (package name)
opening comp (pipe links)
added env example file

review-requested:[@ahmadbilaldev ]


how do i install this in android

I don't have a rooted phone

jwz, the author of xscreensaver, also provides an Android app: https://play.google.com/store/apps/details?id=org.jwz.android.xscreensaver
But from what I see in the changelog, screensavers (or “hacks” in xscreensaver terms) are added by rebuilding the app.
I’m afraid I can’t help you more here. You can try contacting jwz and ask him for an advice<EMAIL_ADDRESS>


feat: Make tracing object fluent

This could make writing tracing code easier and more readable depending on your preference.
The upside is that this unlocks a fluent way of writing. I don't think there are any actual downsides (apart from BC).
I believe this is a backward incompatible change, especially Span is not a final class so I don't think we can make this change in 3.x but maybe this is a good start for 4.x and allows us to make the tracing code simpeler/shorter to use. Possibly we could already convert the final classes but not a 100% sure if that is also a BC.
If we think this is acceptable and a good change I would propose that going forward (possibly starting with 4.x) to make all future APIs fluent where it makes sense.

A small example partly taken from the laravel codebase:
Before:
$context = TransactionContext::fromHeaders($sentryTraceHeader, $baggageHeader);
$context->setOp('http.server');
$context->setData([
    'url' => '/' . ltrim($request->path(), '/'),
    'method' => strtoupper($request->method()),
]);
$context->setStartTimestamp($requestStartTime);

$bootstrapSpan = $this->addAppBootstrapSpan($request);

$appContextStart = new SpanContext();
$appContextStart->setOp('laravel.handle');
$appContextStart->setStartTimestamp($bootstrapSpan ? $bootstrapSpan->getEndTimestamp() : microtime(true));

$this->transaction->startChild($appContextStart);

After:
$context = TransactionContext::fromHeaders($sentryTraceHeader, $baggageHeader)
    ->setStartTimestamp($requestStartTime)
    ->setOp('http.server')
    ->setData([
        'url' => '/' . ltrim($request->path(), '/'),
        'method' => strtoupper($request->method()),
    ]);

$bootstrapSpan = $this->addAppBootstrapSpan($request);

$appContextStart = (new SpanContext)
    ->setStartTimestamp($bootstrapSpan ? $bootstrapSpan->getEndTimestamp() : microtime(true))
    ->setOp('laravel.handle');

I really like how this would improve our API.
On the other hand, we will force people to update all their instrumentation code when they upgrade to 4.0.
And I have the feeling that this work is not really worth the gain for them 🙁

Why would they? The old code still works with this change. In my description, both code blocks work perfectly fine after this change 😄
The only thing is that people extending our classes (read: Span) need to add return $this;. But I'm not sure why people would extend our Span class in the first place so unsure this is a real problem.

Ok, then let's mark Span as final.
I would like to have a discussion about this in a different issue, where we could discuss annotating stuff as @internal vs making everything final and impossible for people to extend (there might be uses-cases for that).

Closing for now but keeping the branch for later 🙂

Closing this in favor of #1601.


How to convert between OpenCV Mat and k4a::image?

cv::Mat and k4a::image both provide access to the raw buffers, images, sizes, and pixel format (e.g. bytes/pixel). You can use this information to copy data to/from each image type. You can also use this information to "wrap" the raw data without copying it. You have the choice of copy or wrap.
The greenscreen example has some code from which you can learn https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/master/examples/green_screen/main.cpp

cv::Mat and k4a::image both provide access to the raw buffers, images, sizes, and pixel format (e.g. bytes/pixel). You can use this information to copy data to/from each image type. You can also use this information to "wrap" the raw data without copying it. You have the choice of copy or wrap.
The greenscreen example has some code from which you can learn https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/master/examples/green_screen/main.cpp

If you have a k4a_image  colorImage , you can convert the k4a_image to an OpenCV Mat with this code:
`cv::Mat cImg = cv::Mat(k4a_image_get_height_pixels(colorImage), k4a_image_get_width_pixels(colorImage), CV_8UC4, k4a_image_get_buffer(colorImage));`

Convert this OpenCV Mat back into a k4a_image:
	k4a_image_create(K4A_IMAGE_FORMAT_COLOR_BGRA32, cImg.cols, cImg.rows, cImg.cols * 4 * (int)sizeof(uint8_t), &newk4aImage);
	memcpy(k4a_image_get_buffer(newk4aImage), &cImg.ptr<cv::Vec4b>(0)[0], cImg.rows * cImg.cols * sizeof(cv::Vec4b));

You can see this file for more context:
https://github.com/MarekKowalski/LiveScan3D/blob/AzureKinect/src/LiveScanClient/azureKinectCapture.cpp#L160

If you have a k4a_image  colorImage , you can convert the k4a_image to an OpenCV Mat with this code:
`cv::Mat cImg = cv::Mat(k4a_image_get_height_pixels(colorImage), k4a_image_get_width_pixels(colorImage), CV_8UC4, k4a_image_get_buffer(colorImage));`

Convert this OpenCV Mat back into a k4a_image:
	k4a_image_create(K4A_IMAGE_FORMAT_COLOR_BGRA32, cImg.cols, cImg.rows, cImg.cols * 4 * (int)sizeof(uint8_t), &newk4aImage);
	memcpy(k4a_image_get_buffer(newk4aImage), &cImg.ptr<cv::Vec4b>(0)[0], cImg.rows * cImg.cols * sizeof(cv::Vec4b));

You can see this file for more context:
https://github.com/MarekKowalski/LiveScan3D/blob/AzureKinect/src/LiveScanClient/azureKinectCapture.cpp#L160

@ChristopherRemde examples have several errors in them. Important when exchanging raw image data between different SDK/systems to declare the step or stride. It is not guaranteed for both systems (cv and k4a) to use the same stride. As fact, k4a aligns row strides to 32-byte boundaries and cv uses 64-byte boundaries. Therefore, add the step/stride parameter to both of his examples.
The color image from a k4a sensor can be many formats. https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/group___enumerations_gabd9688eb20d5cb878fd22d36de882ddb.html#gabd9688eb20d5cb878fd22d36de882ddb
The byte size and step/stride are different for them all. So you can not always assume it is 4 bytes with CV_8UC4. You will need to consult the documentation for k4a SDK and cv for the color image for you choose. The NV12 and YUY2 are usually more difficult for beginners, so I recommend you choose BGRA to begin.
It is also not safe to use memcpy() as he did. It is not guaranteed for the complete byte size of an image buffer to be the (rows * col * pixelsize). Image buffers are not guaranteed to be continuous/contiguous. The image buffer you are given can have different step/strides and may put additional unused bytes at the end of each row. I isolated data corruptions bugs in the k4a SDK itself where Microsoft didn't follow these rules.
Always stride and step. No exceptions when exchanging images between foreign systems. Even if you look at the internals of the SDKs, they can change change their alignment defaults at any time or the SDK can have differnet stride rules when you compile for different platforms (32-bit, 64-bit, Windows, Linux, Mac, etc.)
In all the no-copy examples, remember to manage the lifetime of the original source image. You must keep it alive while you are using the wrapped image. If you don't, then when you access the wrapped image, it will try to access deallocated memory and your app will probably crash.
Here is a corrected wrap (no copy) example
cv::Mat wrappedk4aimage {
  yourk4aimage.get_height_pixels(),
  yourk4aimage.get_width_pixels(),
  CV_8UC4, // calculate this with a function or hard code it if you guarantee it will never change
  yourk4aimage.get_buffer(),
  (size_t)yourk4aimage.get_stride_bytes()
};

His 2nd example is a copy which is different than his first example (no copy). Here is a corrected copy example.
auto yourk4aimage = k4a::image::create(
  K4A_IMAGE_FORMAT_COLOR_BGRA32, // again calculate with function or hard code
  cvimage.cols,
  cvimage.rows,
  (int)cvimage.step
);

// using memcpy like this is somewhat inflexible/dangerous; I use it only for quick example
memcpy(
  yourk4aimage.get_buffer(),
  cvimage.data,
  cvimage.step * cvimage.rows
);

And here is a (no copy) wrap of a cv image with a k4 image.
k4a::image::create_from_buffer(
  K4A_IMAGE_FORMAT_COLOR_BGRA32, // again calculate with function or hard code
  cvimage.cols,
  cvimage.rows,
  (int)cvimage.step,
  cvimage.data,
  cvimage.step * cvimage.rows,
  nullptr,
  nullptr
);

@ChristopherRemde examples have several errors in them. Important when exchanging raw image data between different SDK/systems to declare the step or stride. It is not guaranteed for both systems (cv and k4a) to use the same stride. As fact, k4a aligns row strides to 32-byte boundaries and cv uses 64-byte boundaries. Therefore, add the step/stride parameter to both of his examples.
The color image from a k4a sensor can be many formats. https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/group___enumerations_gabd9688eb20d5cb878fd22d36de882ddb.html#gabd9688eb20d5cb878fd22d36de882ddb
The byte size and step/stride are different for them all. So you can not always assume it is 4 bytes with CV_8UC4. You will need to consult the documentation for k4a SDK and cv for the color image for you choose. The NV12 and YUY2 are usually more difficult for beginners, so I recommend you choose BGRA to begin.
It is also not safe to use memcpy() as he did. It is not guaranteed for the complete byte size of an image buffer to be the (rows * col * pixelsize). Image buffers are not guaranteed to be continuous/contiguous. The image buffer you are given can have different step/strides and may put additional unused bytes at the end of each row. I isolated data corruptions bugs in the k4a SDK itself where Microsoft didn't follow these rules.
Always stride and step. No exceptions when exchanging images between foreign systems. Even if you look at the internals of the SDKs, they can change change their alignment defaults at any time or the SDK can have differnet stride rules when you compile for different platforms (32-bit, 64-bit, Windows, Linux, Mac, etc.)
In all the no-copy examples, remember to manage the lifetime of the original source image. You must keep it alive while you are using the wrapped image. If you don't, then when you access the wrapped image, it will try to access deallocated memory and your app will probably crash.
Here is a corrected wrap (no copy) example
cv::Mat wrappedk4aimage {
  yourk4aimage.get_height_pixels(),
  yourk4aimage.get_width_pixels(),
  CV_8UC4, // calculate this with a function or hard code it if you guarantee it will never change
  yourk4aimage.get_buffer(),
  (size_t)yourk4aimage.get_stride_bytes()
};

His 2nd example is a copy which is different than his first example (no copy). Here is a corrected copy example.
auto yourk4aimage = k4a::image::create(
  K4A_IMAGE_FORMAT_COLOR_BGRA32, // again calculate with function or hard code
  cvimage.cols,
  cvimage.rows,
  (int)cvimage.step
);

// using memcpy like this is somewhat inflexible/dangerous; I use it only for quick example
memcpy(
  yourk4aimage.get_buffer(),
  cvimage.data,
  cvimage.step * cvimage.rows
);

And here is a (no copy) wrap of a cv image with a k4 image.
k4a::image::create_from_buffer(
  K4A_IMAGE_FORMAT_COLOR_BGRA32, // again calculate with function or hard code
  cvimage.cols,
  cvimage.rows,
  (int)cvimage.step,
  cvimage.data,
  cvimage.step * cvimage.rows,
  nullptr,
  nullptr
);

@diablodale Thank your for your very detailled explanation! I learned quite a few new things, and will try to correct the code!

@diablodale Thank your for your very detailled explanation! I learned quite a few new things, and will try to correct the code!

My main code is as follows:
k4a::calibration kinectCalibration = _device.get_calibration(config.depth_mode, config.color_resolution); k4a::transformation imageTransformation(kinectCalibration); k4a::image depthImage = dataCaptured.get_depth_image(); positionImage = k4a::image::create(K4A_IMAGE_FORMAT_CUSTOM, positionWidth, positionHeight,positionWidth*6); const Position* mPosition = reinterpret_cast<Position*>(positionImage.get_buffer()); imageTransformation.depth_image_to_point_cloud(depthImage, K4A_CALIBRATION_TYPE_DEPTH, &positionImage); size_t depthPixelNum = depthWidth * depthHeight;	 pcl::PointCloud<pcl::PointXYZRGB> pointCloud.reset(new pcl::PointCloud<pcl::PointXYZRGB>(depthWidth, depthHeight)); auto& points = pointCloud->points;				 for(size_t i = 0; i < depthPixelNum; ++i) { 	auto& point = points[i]; 	{ 		const Position& pos = mPosition[i]; 		point.x = 0.001f * static_cast<float>(pos.mX); 		point.y = 0.001f * static_cast<float>(pos.mY); 		point.z = 0.001f * static_cast<float>(pos.mZ); 	} } cv::Mat combinedRgbMat.create(depthHeight, depthWidth, CV_8UC3); for (std::uint32_t j = 0; j < pointCloud->width; j++) { 	for (std::uint32_t i = 0; i < pointCloud->height; i++) 	{	 		combinedRgbMat.at<cv::Vec3b>(i, j) = cv::Vec3b((*pointCloud)(j, i).b, (*pointCloud)(j, i).g,  (*pointCloud)(j, i).r); 	} }
when i use OpenCV  image "combinedRgbMat"  to detect person to get 2D (x,y)coordinates , How to convert OpenCV 2D coordinates to X and Y coordinates of point cloud?

My main code is as follows:
k4a::calibration kinectCalibration = _device.get_calibration(config.depth_mode, config.color_resolution); k4a::transformation imageTransformation(kinectCalibration); k4a::image depthImage = dataCaptured.get_depth_image(); positionImage = k4a::image::create(K4A_IMAGE_FORMAT_CUSTOM, positionWidth, positionHeight,positionWidth*6); const Position* mPosition = reinterpret_cast<Position*>(positionImage.get_buffer()); imageTransformation.depth_image_to_point_cloud(depthImage, K4A_CALIBRATION_TYPE_DEPTH, &positionImage); size_t depthPixelNum = depthWidth * depthHeight;	 pcl::PointCloud<pcl::PointXYZRGB> pointCloud.reset(new pcl::PointCloud<pcl::PointXYZRGB>(depthWidth, depthHeight)); auto& points = pointCloud->points;				 for(size_t i = 0; i < depthPixelNum; ++i) { 	auto& point = points[i]; 	{ 		const Position& pos = mPosition[i]; 		point.x = 0.001f * static_cast<float>(pos.mX); 		point.y = 0.001f * static_cast<float>(pos.mY); 		point.z = 0.001f * static_cast<float>(pos.mZ); 	} } cv::Mat combinedRgbMat.create(depthHeight, depthWidth, CV_8UC3); for (std::uint32_t j = 0; j < pointCloud->width; j++) { 	for (std::uint32_t i = 0; i < pointCloud->height; i++) 	{	 		combinedRgbMat.at<cv::Vec3b>(i, j) = cv::Vec3b((*pointCloud)(j, i).b, (*pointCloud)(j, i).g,  (*pointCloud)(j, i).r); 	} }
when i use OpenCV  image "combinedRgbMat"  to detect person to get 2D (x,y)coordinates , How to convert OpenCV 2D coordinates to X and Y coordinates of point cloud?

I recommend you read https://docs.microsoft.com/en-us/azure/kinect-dk/use-image-transformation and reference the examples. You are raising a different off-topic question.

I recommend you read https://docs.microsoft.com/en-us/azure/kinect-dk/use-image-transformation and reference the examples. You are raising a different off-topic question.


Fixed typo variable name PublishDirDir to become PublishDir

Publish target failing due to wrong PublishDir variable name
It returns error MSB3932: Failed to unzip file "\LibpostalData.zip" because the file does not exist or is inaccessible
because the code was using variable PublishDirDir instead of PublishDir

Saw the PR after I've opened it, anyway it refs to #55
It would be great if you can merge it ASAP.
Thanks in advance.

@marcoCasamento @bard83 thanks for your contribution.  This has now been merged and released.


Can't switch accounts after deleting team

I started to play around with creating a Team on Now for a small project I'm working on, but decided against it. The team was active on the now CLI at the point that I deleted the team.
If I try to use now, I get the follow error:

Error! Your team was deleted. You can switch to a different one using "now switch".

Totally reasonable, except that now switch throws a JavaScript exception
> Error! An unexpected error occurred in switch: TypeError: Cannot read property 'slug' of undefined
    at module.exports.__webpack_exports__.default.choices.findIndex.choice (/snapshot/repo/dist/index.js:42977:46)
    at Array.findIndex (<anonymous>)
    at module.exports.__webpack_exports__.default (/snapshot/repo/dist/index.js:42976:27)
    at process._tickCallback (internal/process/next_tick.js:68:7)

I was able to get myself un-stuck by deleting $HOME/.now and logging in again

I had the same issue, but @alexlafroscia's solution worked for me. Would be nice if there was a clear, built-in way to get around this.

This is still valid. Here's the output from Now CLI v16.1.2-canary.2 after deleting the currently "scoped" team:
$ now team ls
⠴ Fetching teams> Error! Unauthorized

001 ▲ 111 +1 → ~/Code/zeit/now-cli (canary) $ now switch
> Error! You are not a part of the current team anymore

This bug is still here and I have no idea what $HOME/.now is.

I was able to solve this by deleting ~/.local/share/com.vercel.cli.


"Export from Query" always omits schema name

Description
Even when the "Omit schema name" export setting is unchecked, the schema is omitted from the output.
This is not the case for full table exports.
DBeaver Version
CE Version <IP_ADDRESS>309282157
Operating System
Arch linux
Database and driver
PostgreSQL 14
PostgreSQL JDBC Driver [42.5.0]
Steps to reproduce
If I write the expression:
SELECT * FROM markets.towns ...
And preform "Export from Query", the result does not include the schema:
INSERT INTO towns ...
This is not expected. I would expect the schema to be included.
Also if I use ${schema} in the output file name that comes out blank.
Additional context
When I click "Export Data" on the same table with SQL target, the results include the schema name:
INSERT INTO markets.towns ...
This is expected.
My end goal is to have a complex SQL script with a bunch of tables from different schemas and export to SQL files.

Hello @jonocodes
Thanks for the report.
Yes, the "Omit schema name" export setting works correctly for the export from the table but not for the export from the query. I can reproduce it.


How work without DOCTYPE tag

Hi
I found w2ui does not work without DOCTYPE tag.
Because svg namespace conflict in my html, I can not use <! DOCTYPE> tag,
Can you tell me how can I use w2ui without <! DOCTYPE>?
thanks

I have tested in my local and there is no problem without DOCTYPE tag. What kind of problems do you see?

Hi @vitmalina
My environment is IE9, it does not work without DOCTYPE tag,
but when I joined the following statement it is a good job.
<meta http-equiv = "X-UA-Compatible" content = "IE = edge, chrome = 1">

On the other way, I'm used IE11 with in IE9 compatibility mode, it can also work fine, so I think this might be my browser environmental problems, or problems IE9.
thanks

Well, since it affects only IE and there is a quick fix, I am closing this issue.


Restore the ability to (up/down)load individual files

I can see the original version of this allowed the (up/down)load of individual files:
https://github.com/prasmussen/gdrive
gdrive [global] download [options]
gdrive [global] upload [options]
The latest version seems to have this removed (!!) - which I think cripples things quite a bit
Why this is important to me:
The original version no longer seems to work - Google Drive seems to block it
I'm wanting to download individual files to a computer cluster I am using
Pulling my whole drive is slow and wasteful - the cluster admins will not be happy with me filling up GBs
Importantly: Using ".driveignore" is not an option. It is likely other cluster users will use my Docker container for the extra productivity I am designing it for (making it easy to switch between using Google Colab and using the cluster) - and I don't want the other users to have to muck around with ".driveignore" - or not have ".driveignore" correctly configured and annoy the cluster admins by filling up the cluster with unneeded GBs

... nevermind - just worked out I can use "drive pull "


Decrypt token

#2

Manually merged in https://github.com/SuprDewd/simpletracker/commit/864ed91b9e4c8959f599bf209ef45fe3cb5ec019


[W5.11][F09-4] Seah Xi Qi, Nicholas

Wew finished W5.11

Really like the new sorting function! Really improves the user experience.
However, I feel that you should add examples into the UserGuide to make it even more foolproof.
Great job!


Update scala-compiler, scala-library to 2.13.14

About this PR
📦 Updates

org.scala-lang:scala-compiler
org.scala-lang:scala-library

from 2.13.9 to 2.13.14
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #234.


media type method?

search_results = twitter_client.user_timeline("bbc", {:count => 4})
search_results.each do |tweet|
  if tweet.media?
    tweet.media.each do |media|
      puts media.type
    end
end

does not work, but i'd expect it to what am i doing wrong? i want to know if the media is a photo or animated gif or video

Hi @chrisallick, thanks for reporting this. #type wasn't an attribute we'd included on media objects. I've fixed this in master (77238b540edfbc76aa2f25bc4398c3dad8f55edb) so it'll be included in the next release.

this is not work

this gem is so difficult to use!


[BUG][DEPLOY] internal testathon feedback

Describe the bug

Hints/Notes: If the correct snapshot format (1.0.0-SNAPSHOT-2020-04-01-02-43-31) is not used then the start.sh script used to install ACM will timeout and fail at Wait for multiclusterhub-operator to reach running state (4min). The default snapshot will also be replaced with the mistyped snapshot. To resolve use the correct snapshot format when prompted and the script will run successfully.
Also the script will also fail at Wait for multiclusterhub-operator to reach running state (4min). if the correct pull-secret is not used. Make sure when generating the pull secret from Quay, you select Kubernetes Secret as it will generate the wrong format. You'll see in the script an error at apply per-requisites with the pull secret if the wrong one is used. "Failed to read Resources YAML file [pull-secret.yaml] encounters a format error.

Are we handling the above in deploy doc or improvements to the start.sh ? eg, script can verify format of the user-provided snapshot.  script can verify quay credentials prior to beginning the pulls.

I have added some additional formating logic to the deploy repo to handle the snapshot format:
https://github.com/open-cluster-management/deploy/blob/master/start.sh#L76-L85
For the quay pull-secret I will look at what I can do to validate that although I'm not entirely sure how much validation logic I can add for that.


Version by File updates

@Rick-Anderson @wadepickett ... This will remove the dummy files and take a handful (~6) Blazor topics over to the new system. I just want to make sure that everything works well with a handful of topics first before going further with it.
Note that I'm still not quite on 6.0 preview bits yet. Soon tho! I prefer RC1 for that move, if possible. Therefore, this places some 6.0 topics versioned by file but uses 5.x snippet sample apps in them. That's fine for now. There will be significant updates for Blazor 6.0 snippet samples. I will get new 6.0 Blazor snippet samples up ASAP on my move to 6.0 RC bits (or earlier if I do adopt preview bits). It's fine for now tho.
We can wait until DocFX reviews before merging this PR, BUT ... I can't be held up too much by their review. If we don't hear back by EOD Friday, then I propose that we go ahead and merge this PR. I have a lot of work to do to adopt the new world order here, which is virtually required for one major Blazor update for 6.0 👉 Blazor Server apps are offloading their HTML layout content from _Host.cshtml to _Layout.cshtml, which touches 19 Blazor topics in 65 spots. Version by file is my savior here (i.e., saves me from a bunch of moniker ranges/duplicated content in current topics), and I need to get on with gett'in on with it 🏃🏃🏃🏃😅.
~... and I see a build warnings/errors ... no worries ... I'll see what's what and get them cleaned up here shortly.~ Done! :+1:

I licked those build probs; but to do so, I had to exclude the new includes folders for Blazor versioned by file content. So, I went from ...
{ "files": [ "**/*.md" ], "group": "aspnetcore-3.1", "src": "3.1" },
{ "files": [ "**/*.md" ], "group": "aspnetcore-5.0", "src": "5.0" },
{ "files": [ "**/*.md" ], "group": "aspnetcore-6.0", "src": "6.0" }

... to ...
{ "files": [ "**/*.md" ], "exclude": [ "**/includes/**" ], "group": "aspnetcore-3.1", "src": "3.1" },
{ "files": [ "**/*.md" ], "exclude": [ "**/includes/**" ], "group": "aspnetcore-5.0", "src": "5.0" },
{ "files": [ "**/*.md" ], "exclude": [ "**/includes/**" ], "group": "aspnetcore-6.0", "src": "6.0" }

... in docfx.json. You/I may need to alert the DocFX engineer to this change for their look given that the live file doesn't have that ☝ update.

Also, local resource files weren't available, so I added the following to the resources node of docfx.json ...
{ "files": [ "**/*.png", "**/*.jpg", "**/*.gif", "**/*.svg", "**/*.pdf" ], "exclude": [ "**/includes/**" ], "group": "aspnetcore-3.1", "src": "3.1" },
{ "files": [ "**/*.png", "**/*.jpg", "**/*.gif", "**/*.svg", "**/*.pdf" ], "exclude": [ "**/includes/**" ], "group": "aspnetcore-5.0", "src": "5.0" },
{ "files": [ "**/*.png", "**/*.jpg", "**/*.gif", "**/*.svg", "**/*.pdf" ], "exclude": [ "**/includes/**" ], "group": "aspnetcore-6.0", "src": "6.0" }

Discussed offline ... we're going to merge this now. The DocFX engineer can look at the merged, finished docfx.json file. I'll confirm all is well with the repo after this goes live.


ResultExt doesn't integrate very well with E's which do not implement Error

Currently, ResultExt is implemented for:
Result<T, E> where     E: Error + Send + Sync + 'static
Types like eyre::Report don't implement Error, so we cannot use the internal extension method to convert an Err(eyre!("oops")) to a Problem.

Hi @dbofmmbt! Sorry for the delay.
Internally, Problem stores an eyre::Report, created internally; this is why we require the Error bound in (IIRC) all constructors.
Is your code that calls eyre! or is it a dependency? Internally we deal with internal error either via .internal() or simply panicking, but I think that being able to create an internal error from a string is a good feature to have. We'll try to add a function for this.


incompatible character encodings: UTF-8 and ASCII-8BIT

After using any wiki cipher block in a wiki site i can 'use the wiki history compare or show method for this site change without error.
As soo as i i try to compate this site or show the historic change i get an error. I dont't have this problem when i don't use the cyper macro in the site.
ActionView::Template::Error (incompatible character encodings: UTF-8 and ASCII-8BIT):
39:
40: <% end %>
41:
42: <%= render(:partial => "wiki/content", :locals => {:content => @content}) %>
43:
44: <%= link_to_attachments @page %>
45:
activesupport (3.2.11) lib/active_support/core_ext/string/output_safety.rb:133:in concat'   activesupport (3.2.11) lib/active_support/core_ext/string/output_safety.rb:133:in concat'
actionpack (3.2.11) lib/action_view/buffers.rb:11:in <<'   plugins/redmine_wikicipher/app/views/wiki/show.html.erb:42:in _plugins_redmine_wikicipher_app_views_wiki_show_html_erb__972499250_116039270'
actionpack (3.2.11) lib/action_view/template.rb:145:in block in render'   activesupport (3.2.11) lib/active_support/notifications.rb:125:in instrument'

As no extra feedback was provided upon changes made to solve the issue, I'm assuming that it has been fixed. I'll close this issue for now (if problems still persists please re-open the issue or post a new one).


.NET core self contained exe held open

Issue Title
.NET core self contained exe held open
General
I have a .NET Core self contained application (Foo.exe), where the csproj file is configured in the following way:
  <PropertyGroup>
   <TargetFramework>netcoreapp3.0</TargetFramework>
   <GenerateAssemblyInfo>false</GenerateAssemblyInfo>
   <OutputType>Exe</OutputType>
   <PublishTrimmed>true</PublishTrimmed>
   <PublishSingleFile>true</PublishSingleFile>
   <RuntimeIdentifier>win-x86</RuntimeIdentifier>
 </PropertyGroup>

I run the following command to publish the exe, which produces Foo.exe:
dotnet publish -c release
When I run the Foo.exe from the publish folder, I can see that everything is extracted and running from a temp folder as expected.
One thing I'm slightly confused about is that if I try to delete Foo.exe from the publish folder (not the temp folder), then I get an error saying the file is already open by Foo.exe. Using process explorer I can also see that the Foo.exe from the publish folder is held open by a file that itself is called Foo.exe.
I thought that given the application is self-contained, I can delete and change the executable from the publish folder freely, because the actual app is running from the temp folder. Any idea why the exe seems to be held open by a file that has the same name as the exe itself?
EDIT
The exe is configured to run as a windows service.

Diplicate of https://github.com/dotnet/runtime/issues/1260

@swaroop-sridhar Having read the linked issue, I don't feel it's quite the same as the one I'm facing.
In the linked issue, the file is being held open when launching the exe a second time with the content already extracted. In my case, however, the file is locked when I launch the exe for the first time.
I'm even wondering now, why is the exe kept running anyway? I would have thought that the self extracted content is run using dotnet.exe by invoking the extracted dll against it? Shouldn't the exe be simply used for the self extraction, and closed afterwards?
Following link contains a minimal reproduciable example for windows.
https://github.com/IIFE/LockIssue
If you run dotnet publish -c release /p:Platform="any cpu", and run the exe from the publish folder, when you try to delete the exe from the publish folder, you'll get the file lock error.
Will the proposed fix from the linked issue fix this problem?


Update release-it to ^14.12.5 and regenerate yarn.lock

Thanks!  Merging!
I love release-it. by the way. Perfect software.  Thanks again @webpro

Thanks guys! Much appreciated 😃


[WIP] History API rework

NOTE: This PR is a work-in-progress, and is not ready to be merged as-is. There are ongoing discussions about the new API design.
This PR aims to overhaul the history API of reedline in order to make it usable outside of the crate. It also aims to make it more robust, more intuitive and less error-prone.
Following discussions in #680 (original PR), #735 (discussion), also embedding future discussions for #746.
For newcomers in the discussion, please read #680 first, as it will help you understand the motivations and existing discussion behind this PR.
TODO list (includes unvoted tasks):

[ ] Global API rewrite
[ ] Introduce a new, fast history backend with all available features (e.g. sled-backed?)
[ ] Remove the sync API (see #746)
[ ] Add new documentation and add integration examples
[ ] Move the History::session method someplace else (to move session detection logic outside of the history implementation)

cc @stormasm @fdncred @sholderbach

Seems like this won't materialize. I'm not sure we'd accept it anyway. I'd suggest smaller PRs so they're easier to review.


fix for boolean type conversion

Fix for #77

Thanks for the review! I fixed most of review comments.
Regarding the first one about the method of passing arguments to clickhouse_driver.Client - currently there's 23 arguments, most of them are optionals. So, minimal boilerplate version should use something like Pydantic. And it looks like a little overkill to me. What do you think?

Regarding the first one about the method of passing arguments to clickhouse_driver.Client - currently there's 23 arguments, most of them are optionals. So, minimal boilerplate version should use something like Pydantic. And it looks like a little overkill to me. What do you think?

Hi @akurdyukov, yes, definitely using an external library is an overkill here. I suggest to hardcode all the arguments: clickhouse-driver is not expected to change them often, so we may accept new PRs once the arguments change in the underlying library.


[Date/Time]Picker: Request for textFieldProps prop

I want to remove the underline from the TextField that gets embedded as part of a DatePicker or TimePicker. The only prop that is exposed to me that comes close is textFieldStyle but this still doesn't cut it, because the line is created by a hr element within TextField that I can't eliminate with CSS.
What i'm looking for is the ability to set underlineShow: false on that TextField. So what I'm thinking, to eliminate issues like this, is to drop the textFieldStyle prop in favor of textFieldProps prop. This way you can pass in an object of properties for TextField, one of which could be style or underlineShow. So you get to keep the existing functionality, but also gain much more, for very little work.
I'd see it working like this under the hood:
<TextField
  ...
  {...textFieldProps}
/>

This issue arises because I am trying to use a custom root element to launch the picker. I just want the modal aspects of these components, but not the form element that sticks on the page. Alternatively, is there a way to imperatively call the opening of a Date or Time picker?
Right now I am wrapping this component around my custom component:
<DatePicker>
  <CustomElement />
</DatePicker>

... but this is how I get "stuck" with the TextField line.

Closing for #4787 and #4796


Amazon Cloud Player script

Hi @SteVwonder. Thanks for your work. I've added in-line comments for some minor issues and here come other two:

Increase the icon size in Makefile to 128 ICON_SIZE ?= 128.

You should add support for other national variants.

Original implementation in Nuvola Player 2: settings.js, integration.js
Example how to do it in Nuvola Player 3: Web apps with a variable home page URL - Multiple Website Variants

Hi @SteVwonder. Are you going to address issues from this code review or should I adopt your integration script?

I cannot accept this pull request because of incomplete copyright information.

Sorry that I abandoned this PR.  My semester at school caught up with me.  I will review everything this week and submit a new PR.


ocamldoc (/) comment reformats badly

(**/**) in OCaml will refmt to /**/**/ in Reason, causing a syntax error.
EDIT: Submitted too soon

Why this matters - ocamldoc and odoc use (**/**) to indicate any following values/types/etc should not be included in any rendered documentation.


Cannot test endpoint from /docs page

Basically it requires authentication, but currently doesn't work

I think this has now been superseded by the full stack testing in #35


Server language detection not working in Safari (dependency update needed)

Describe the bug
Safari is sending the Accept-Language in a lowercase manner (e.g. en-us). Because the current used version of i18next-express-middleware detects this string as en- instead of en the sever language detection is not working as expected.
Occurs in next-i18next version
4.2.1
Additional context
This issue has been discussed here and got fixed in<EMAIL_ADDRESS>Is it possible to bump the dependency to a recent version? Thanks!

@timonweber Presently, this line creates a type clash between next-i18next and i18next-express-middleware, preventing that upgrade.
Any good with TS? Feel like contributing?

@isaachinman Not good enough probably, I’m still learning. But I guess you solved that issue already by yourself. Thank you very much for the fast action! 🙂

It's still not working for me after updating to 4.3.0

@Kenpa Can you create a reproducible example? @timonweber Is the issue resolved on your end?

I just updated to 4.3.0, run next server.js (custom server), and still got english content instead of french in Safari... Works fine in Chrome and Firefox

@isaachinman Sorry for the late reply. Unfortunately the problem is still present on my end. But I had a deeper look into it and it seems that this issue is not only related to the casing of the language string but also to the presence of a region code.
For example: When I configure an app with a default language of en and a subpath for both en and de I getting a redirect to /en when I send Accept-Language: de-DE. But when I send Accept-Language: de the redirection correctly points to /de. That’s odd because when I manually test the original regex of i18next-express-middleware everything gets detected as expected.
So this issue seems to be not only present in Safari, but in every client where the only parameter in Accept-Language contains a region code. For example: Chrome sends Accept-Language: de-DE,de so the second option is successfully matched.
But maybe this issue should be addressed to i18next-express-middleware directly, sorry for the inconvenience.

Check the configuration options. Specifically, load: languageOnly.

@isaachinman Sorry, I totally missed that option! I tested it again and yes, everything is working as expected after the update. Both Accept-Language: de-DE and Accept-Language: de-de are correctly pointing to /de.
Thanks again! 🙂

@isaachinman Sorry, missed that option too! Works fine now! Just one thing that seems odd to me in Safari: when i try to get the current language with i18n.language, it also returns me the region, en-US, instead of only en in Chrome and Firefox

Please raise any questions like that via StackOverflow, or via the relevant i18next repository.

Hi @timonweber @isaachinman, could you please explain where to put that option to get the current language? Thanks!


Notes section lacks bullets

Any topic that has a notes section, such as Receive-PSSession, New-PSSessionOption and Register-PSSessionConfiguration.
The markdown output has no bullets. The technet version has bullets (see screen cap).
In the maml file, there is a tag, maml:alert, which wraps one or more maml:para tags. The technet page renders one bullet for each maml:alert tag, which can include multiple paragraphs. Can we get this as a list, one bullet per alert tag?

Yes, we can do it in New-MarkdownHelp.

That turned out to be a trickier problem, then I expected.
As @TimShererAtAquent said, in maml, there is <maml:para> tag that provides bullet-point.
However, help object doesn't have any corresponding entity.
We use help object to produce maml.
So, if we want this functionality, we need to plug it before converting maml into help object.
Also, in the Get-Help output itself this distinctions creates problems already
For example, here is a fragment of output of Get-Help Receive-PSSession

And corresponding technet article

So this is not new, but we can try to solve it with platyPS.

I made it work, but markdown doesn't look good eather
https://gist.github.com/vors/c06c7876bbe400fc9a3dc93e65d2c9d0#notes

Addressed in 69d5663 and 8c6e40e
New-MarkdownHelp -ConvertNotesToList


CONTRIBUTING: remove 404 link and add API guidelines link

Signed-off-by: Lonng<EMAIL_ADDRESS>
What have you changed? (mandatory)

Remove 404 link
Add API guidelines link

seem conflicted with #4694

@siddontang OK, I think the API guidelines should be added to the docs.

@Hoverbear PTAL


Esl2017

Current implementation assumes theta in Equation 4 doesn't decrease with time, therefore there's some overshoot for the inferred angular rate at the start of the measurement where angular rate is larger. However, the results stills calculate the inferred angular rate with high accuracy, since the initial angle is small, therefore the assumption for constant amplitude for theta holds. We can use a second-order damped model to model theta as a function of time to further increase the accuracy for larger angle oscillations.

Current implementation assumes theta in Equation 4 doesn't decrease with time, therefore there's some overshoot for the inferred angular rate at the start of the measurement where angular rate is larger. However, the results stills calculate the inferred angular rate with high accuracy, since the initial angle is small, therefore the assumption for constant amplitude for theta holds. We can use a second-order damped model to model theta as a function of time to further increase the accuracy for larger angle oscillations.

Current implementation assumes theta in Equation 4 doesn't decrease with time, therefore there's some overshoot for the inferred angular rate at the start of the measurement where angular rate is larger. However, the results stills calculate the inferred angular rate with high accuracy, since the initial angle is small, therefore the assumption for constant amplitude for theta holds. We can use a second-order damped model to model theta as a function of time to further increase the accuracy for larger angle oscillations.


PIN CE of ESP32

There issue when we use in the same time an SPI on ESP32 (in our case to communicate with LORA module) and DS1302. In the library CE pin of DS1302 is connected the IO5 of ESP32. But this pin is used for SPI communication (NSS pin). Is there possibility the change CE pin (use other GPIO )?

Hi @saadsdz, Thanks for using my library. Yes, you can use any GPIO pin, because this library uses low-level bit-banging.
See https://github.com/Erriez/ErriezDS1302/blob/0093bc7bd60a79021bfb5e8527ff903f05c27716/src/ErriezDS1302.h#L102
Does this answer your question?


chore: fix winterfell deprecations and no-std build setup

This change addresses upstream deprecations/changes from facebook/winterfell#262 and 0xPolygonMiden/crypto#290.
As a necessary side effect of those deprecations, our no-std build setup needed to be adjusted. See the above-mentioned PRs for more info, but the gist of the change is to always build with #![no_std], and enable std features conditionally, rather than the reverse. For the most part this has little effect on how code is actually written, aside from needing to be more explicit about imports in some cases (anything that would normally be provided by the libstd prelude).

There seems to be one standing warning:
2024-03-21T18:06:15.0030965Z error: the item `Box` is imported redundantly
2024-03-21T18:06:15.0089521Z ##[error] --> mock/src/main.rs:1:11
2024-03-21T18:06:15.0161020Z   |
2024-03-21T18:06:15.0162741Z 1 | use std::{boxed::Box, fs::File, io::Write, path::PathBuf, time::Instant};
2024-03-21T18:06:15.0164185Z   |           ^^^^^^^^^^
2024-03-21T18:06:15.0165886Z  --> /rustc/1388d7a069d872bcfe5e5dd97ef61fa0a586fac0/library/std/src/prelude/mod.rs:125:13
2024-03-21T18:06:15.0167515Z   |
2024-03-21T18:06:15.0169363Z   = note: the item `Box` is already defined here
2024-03-21T18:06:15.0170161Z   |
2024-03-21T18:06:15.0171029Z   = note: `-D unused-imports` implied by `-D warnings`

@hackaugusto I've gotta remember to re-run all my checks with both stable and nightly toolchains, that's why I missed those items, sorry about that!
Everything is green now, so I've gone ahead and merged, but let me know if anything else comes up related to those changes.

@Dominik1999  Once we merge next into main these will go away. Is there any reason to do it sooner?

@bobbinth yes, the question is if we need to fix this before we merge docs PRs. PRs that touch the docs would go to main. And we can merge with the clippy warning, but that might be bad practice.

I think if it affecting only docs, clippy warnings are ok.


Changes to allow keg-only glibc

Not tested yet.
See Homebrew/homebrew-core#109998 and Homebrew/homebrew-core#110779, the latter of which is what the install changes are based on.
If it works, it'll need to be merged at the same time as Homebrew/homebrew-core#109998 (if the change moving glibc to keg-only is made).

Review period will end on 2022-09-16 at 13:16:48 UTC.

Do we also need to make sure the path to the glibc headers is added to the include paths?

I think our GCC handles that. I don't know about LLVM though.
I guess if we're adding it as a dependency everywhere, it might already be added like other dependencies are. Really the correct way would probably be how we handle<EMAIL_ADDRESS>but it seems like we've got away so far without.

Review period ended.

Test bot has spoken. This is ready to ship! 😄


Make auto close html smarter

Given the amount of open issues I don't have high hopes for this being addressed, but...

Checkbox is required.

If I accidentally erase the closing > before Checkbox, e.g.:
<p class="text-danger" ng-message="required"Checkbox is required.

and then add it in again, autoclose-html turns it into this wonderful HTML:

Checkbox is required.

Can we make it a bit smarter to check if a matching closing tag is already in place, and then just leave the HTML alone?

This is a dupe of #108 so I'm going to close it. Would love to have this functionality, but it's a hairier problem than it seems, as it requires knowledge of which tags are currently open as well as scanning forward in the document and arbitrary distance to see what closing tags there are.
You quickly get into the weeds with things like:

If you're dealing with a
 within a
 which was the closing tag intended for?
What if there are malformed tags, the current regex based tag recognition system isn't really great for things like this (or really ideal for html parsing in general)

Long story short, this would be a great feature to have, but it's unlikely something I will personally be able to address in the short term

@mattberkowitz thanks for the clarification.
I appreciate the difficulties involved, but I think some relatively simple rules could go a long way. For example, simply find a matching tag on the same line. This is most likely to be the correct matching tag. Not always, true, but 95% of the time it would be.
I'll subscribe to issue 108.


Add new logo in all the UIs

We have essentially 2 types of logos: the "full logo" and the "icon logo".
The new logos should be used in all the following places:

[ ] chooser UI (full) - dark mode + light mode
[ ] MLFlow UI (full)
[ ] Aim UI (icon)
[ ] favicon everywhere

For MLH fellow


Add CHANGELOG-v0.1.0-alpha.md

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #34
Special notes for your reviewer:
Release note:

@andyzhangx The Changelog is generated using https://github.com/github-changelog-generator/github-changelog-generator#installation. Please review.

hi @Masquerade0097 can you also Add CHANGELOG-v0.1.0-alpha.md in azurefile driver? thanks.

@andyzhangx Ya, sure.


Example of leak sanitizer shows no debug information (so did applying sanitizer in my own project)

What I ran and what I got:
@bruno:lsan% RUSTFLAGS='-Z sanitizer=leak' cargo run --example rc-cycle --target x86_64-unknown-linux-gnu
   Compiling lsan v0.1.0 (file:///home/bruno/prog/rust/rust-san/lsan)
    Finished dev [optimized + debuginfo] target(s) in 0.58s
     Running `target/x86_64-unknown-linux-gnu/debug/examples/rc-cycle`

=================================================================
==29114==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 32 byte(s) in 1 object(s) allocated from:
    #0 0x55669bd75236  (/home/bruno/prog/rust/rust-san/lsan/target/x86_64-unknown-linux-gnu/debug/examples/rc-cycle+0xa236)
    #1 0x55669bd70fc5  (/home/bruno/prog/rust/rust-san/lsan/target/x86_64-unknown-linux-gnu/debug/examples/rc-cycle+0x5fc5)

SUMMARY: LeakSanitizer: 32 byte(s) leaked in 1 allocation(s).

Rust version:
@bruno:lsan% rustc --version
rustc 1.30.0-nightly (9395f0af7 2018-09-02)

This solved my issue: https://stackoverflow.com/questions/24566416/how-do-i-get-line-numbers-in-the-debug-output-with-clangs-fsanitize-address
I think it is worth putting it on readme.

Sorry to continue posting here, but which answer exactly solved your issue?
I tried putting ASAN_SYMBOLIZER_PATH=/usr/local/bin/llvm-symbolize-6.0 in front of the whole sanitizer command, but it didn't help.

@japaric I'm also running into this. Could you please clarify what we need to do to see the sanitizer output?


Install django-haystack in mozillians.org.

Basic index for public profiles.

Coverage increased (+0.1%) to 93.341% when pulling 3a8d8f49af99a050e2500cdf545c82db18f6eaea on akatsoulas:django-haystack into 1bcd32456fb6c98a675c14e41b9382b711746b06 on mozilla:master.


removed monitors.py

Cleanup, removing unused code, adding tests, improving naming

we should not overfit classif problems or if we need code only for classif
it should be explicit in the function or module name

The functions now inside are expected to be removed, that was what I meant with my comment to @sliwy  regarding refactoring this. They are only used inside this test atm.
For further clarification, the per-class-sum described in my comment refers to a code inside the example:
 np.array(
                [np.mean(p, axis=1) for p in preds_per_trial]
            )

And the current to-be-removed _compute_preds_per_trial_from_crops is more generic, it collects all the predictions that belong to each trial and removes duplicate predictions. Similar functionality already exists in scoring.py now and should be used here inside this test.

ok great !

Concretely, function that should be used now (also inside this test):
https://github.com/braindecode/braindecode/blob/c9df8f987da3241631f4a31a7e2d1f8fee29e1c1/braindecode/scoring.py#L19-L83
Example usage of this function here:
https://github.com/braindecode/braindecode/blob/c9df8f987da3241631f4a31a7e2d1f8fee29e1c1/braindecode/scoring.py#L156-L184
This function trial_preds_from_supercrop_preds also prime candidate to be the next to have a proper test for :)

Codecov Report

Merging #96 into master will increase coverage by 2.42%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #96      +/-   ##
==========================================
+ Coverage   58.88%   61.30%   +2.42%
==========================================
  Files          37       36       -1
  Lines        2308     2132     -176
==========================================
- Hits         1359     1307      -52
+ Misses        949      825     -124


chore: update GoReleaser to v2

https://github.com/container-tools/spectrum/issues/95

While I looked into #95 , I found GoReleaser was very old.
To resolve #95 , I think we should upgrade GoReleaser to the latest version.
This pull request updates GoReleaser to the latest version and updates the configuration file.
Test
I've confirmed I could build pre-built binary for darwin/arm64 and the naming style wasn't changed.
$ goreleaser -v
  ____       ____      _
 / ___| ___ |  _ \ ___| | ___  __ _ ___  ___ _ __
| |  _ / _ \| |_) / _ \ |/ _ \/ _` / __|/ _ \ '__|
| |_| | (_) |  _ <  __/ |  __/ (_| \__ \  __/ |
 \____|\___/|_| \_\___|_|\___|\__,_|___/\___|_|
goreleaser: Deliver Go Binaries as fast and easily as possible
https://goreleaser.com

GitVersion:    2.0.1
GitCommit:     684c1805864e5f29acc204e34e1770eb74918d15
GitTreeState:  false
BuildDate:     2024-06-11T01:45:52Z
BuiltBy:       goreleaser
GoVersion:     go1.22.4
Compiler:      gc
ModuleSum:     h1:Wx2peRnvixEBRKxU6T0Gh+3wlire+Jv2IOW5eNPan3U=
Platform:      darwin/arm64

$ goreleaser release --snapshot --clean
  • starting release...
  • loading                                          path=.goreleaser.yml
  • skipping announce, publish and validate...
  • loading environment variables
  • getting and validating git state
    • git state                                      commit=aae3e613c9f03b346e5d58b23d0f2291c5c309cd branch=chore-update-goreleaser current_tag=v0.6.44 previous_tag=v0.6.43 dirty=true
    • pipe skipped                                   reason=disabled during snapshot mode
  • parsing tag
  • setting defaults
  • snapshotting
    • building snapshot...                           version=v0.6.44-next
  • running before hooks
    • running                                        hook=go mod download
  • checking distribution directory
    • cleaning dist
  • setting up metadata
  • storing release metadata
    • writing                                        file=dist/metadata.json
  • loading go mod information
  • build prerequisites
  • writing effective config file
    • writing                                        config=dist/config.yaml
  • building binaries
    • building                                       binary=dist/spectrum_windows_386/spectrum.exe
    • building                                       binary=dist/spectrum_darwin_amd64_v1/spectrum
    • building                                       binary=dist/spectrum_darwin_arm64/spectrum
    • building                                       binary=dist/spectrum_linux_386/spectrum
    • building                                       binary=dist/spectrum_linux_amd64_v1/spectrum
    • building                                       binary=dist/spectrum_linux_arm64/spectrum
    • building                                       binary=dist/spectrum_windows_amd64_v1/spectrum.exe
    • building                                       binary=dist/spectrum_windows_arm64/spectrum.exe
    • took: 1s
  • archives
    • creating                                       archive=dist/spectrum_v0.6.44-next_Windows_i386.tar.gz
    • creating                                       archive=dist/spectrum_v0.6.44-next_Windows_x86_64.tar.gz
    • creating                                       archive=dist/spectrum_v0.6.44-next_Windows_arm64.tar.gz
    • creating                                       archive=dist/spectrum_v0.6.44-next_Linux_arm64.tar.gz
    • creating                                       archive=dist/spectrum_v0.6.44-next_Linux_i386.tar.gz
    • creating                                       archive=dist/spectrum_v0.6.44-next_Darwin_x86_64.tar.gz
    • creating                                       archive=dist/spectrum_v0.6.44-next_Linux_x86_64.tar.gz
    • creating                                       archive=dist/spectrum_v0.6.44-next_Darwin_arm64.tar.gz
    • took: 1s
  • calculating checksums
  • docker images
    • building docker image                          image=quay.io/container-tools/spectrum:v0.6.44
    • took: 1s
  • storing artifacts metadata
    • writing                                        file=dist/artifacts.json
  • release succeeded after 4s
  • thanks for using goreleaser!

$ ls dist
artifacts.json            spectrum_linux_amd64_v1                     spectrum_v0.6.44-next_Windows_arm64.tar.gz
checksums.txt             spectrum_linux_arm64                        spectrum_v0.6.44-next_Windows_i386.tar.gz
config.yaml               spectrum_v0.6.44-next_Darwin_arm64.tar.gz   spectrum_v0.6.44-next_Windows_x86_64.tar.gz
metadata.json             spectrum_v0.6.44-next_Darwin_x86_64.tar.gz  spectrum_windows_386
spectrum_darwin_amd64_v1  spectrum_v0.6.44-next_Linux_arm64.tar.gz    spectrum_windows_amd64_v1
spectrum_darwin_arm64     spectrum_v0.6.44-next_Linux_i386.tar.gz     spectrum_windows_arm64
spectrum_linux_386        spectrum_v0.6.44-next_Linux_x86_64.tar.gz

I found the prefix v was added.
spectrum_v0.6.44-next_Darwin_arm64.tar.gz should be spectrum_0.6.44-next_Darwin_arm64.tar.gz.
I'm looking into how to trim v.

I found the prefix v was added. spectrum_v0.6.44-next_Darwin_arm64.tar.gz should be spectrum_0.6.44-next_Darwin_arm64.tar.gz. I'm looking into how to trim v.

I've tested and found the prefix v was removed from GitHub Releases.
https://github.com/suzuki-shunsuke/spectrum/releases/tag/v0.6.45-2
So there is no problem.

Thanks, lgtm. However mind that we're planning to archive this project soon. It was born as a side project for Camel K and it was deprecated over there in favour of Jib, so, likely this is the last release we're getting out.

Oh, I see. Okay.
I'm a maintainer of aqua, which is a CLI version manager. https://aquaproj.github.io/
aqua supports spectrum and I found the issue #95 , so I handled the issue.

Let me know if this is good to merge now.

Please merge at your timing.
This pull request is already ready.


tx push errors with "No project"

I've recently been in the process of updating frc-docs-translations to support the new CLI. Using the attached config file (the repo config file has not been updated yet), I am getting the following freeze when attempting to run tx push --source --skip.
# Resource o:wpilib:p:frc-docs:r:docs--hardware--sensors--triangulating-rangefinders

 SUCCESS  Resource with slug 'docs--hardware--sensors--triangulating-rangefinders' found
  ERROR   Fetching stats: 404, not_found: No `Project` resource found with the identifier `o:wpilib:p:frc-docs`

Hey @Daltz333, thanks for reporting this.
I have some questions to understand this problem better:

Does this happen to all resources?
What happens if you try to push this specific resource? Do you have the same output?

Also, please add the CLI version you are currently using. You can get it by running tx --version or tx -v

Does this happen to all resources?

Yes

What happens if you try to push this specific resource? Do you have the same output?

Yep
I'm running 1.1.0

Hello @Daltz333 ,
Is there a chance that your API token does not have access to the project? Can you try running
export TRANSIFEX_TOKEN=...
curl -H "Authorization: Bearer $TRANSIFEX_TOKEN" https://rest.api.transifex.com/projects/o:wpilib:p:frc-docs

using the API token found in your ~/.transifexrc file?

@Daltz333 @kbairak I will close this for now, because of inactivity. Feel free to open it again if needed.

Hello @Daltz333 ,
Is there a chance that your API token does not have access to the project? Can you try running
export TRANSIFEX_TOKEN=...
curl -H "Authorization: Bearer $TRANSIFEX_TOKEN" https://rest.api.transifex.com/projects/o:wpilib:p:frc-docs

using the API token found in your ~/.transifexrc file?

Hello @kbairak,
I've encountered a similar issue (another issue was reported that describes a similar issue https://github.com/transifex/cli/issues/180). It appears to be connected to the API token I generated. I followed the curl command you provided, which successfully retrieved project details. I can pull the latest translations without any problems, but I'm experiencing failures when attempting tx push. Would be great if you can shed some light on how you resolved this issue.

We have a similar issue. The person can pull and push translations, but not the source. It seems that this is a permission issue with a correct, but unhelpful error message. Our main admin-account can push, the translator cannot.


Nested Reducers?

Hi,
Nested Reducers it can be done?
for example:
{
  login: loginReducer: {....}
  parent: parentReducer: {
   sub: subReducer: {
    subsub: subsubReducer: {.......}
  },
 }
}

It is achievable with usage of a function combineReducers(). Try setting something like that:
import { combineReducers } from '@ngrx/store';

let reducers = {
    login: loginReducer,
    parent: combineReducers({
        sub: subReducer,
        something: somethingReducer
    })
}


EXCEPTION: Token must be defined when building with AOT

I get a really annoying error message and crash when I build my project with ahead of time compilation.
EXCEPTION: Token must be defined!
...
EXCEPTION: Uncaught (in promise): Error: Token must be defined!
...
Unhandled Promise rejection: Token must be defined! ; Zone: angular ; Task: Promise.then ; Value: Error: Token must be defined!
...

I use Angular 2.4.1 with angular2-cookie v1.2.6. Might this be related to #37?

Am getting this too


Spam Domain Submission

Duplicate Domains

[X] Yes, I checked that the domain is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
https://www.youtube.com/watch?v=VM1CbIbCdHE&lc=Ugys7EqDov4i6ADV1X54AaABAg.9YbqxzBXNoY9Ybr8x58c7X
(Optional) Screenshot of comments using the domain

(Required) List of the spam domains
sexy-nudegirls.host
Notes
Comment sourced from @gregovin here

added


[macOS] Add vagrant to macOS-12

Description
As we get virualbox back to macOS-12 we can also install vagrant.
Related issue:
https://github.com/actions/virtual-environments/issues/5583#issuecomment-1171886280
Check list

[x] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run macos1015, macos11, macos12


[Autocomplete] differentiate between hover and keyboard highlight states

I would have liked to use css for the mouse "cursor", but I wasn't able to test it properly.
If thats preferred, then I could use some help on detecting that in a test.
fix #23916

[ x] I have followed (at least) the PR section of the contributing guide.

Hi @cjtroiano. Sorry it took us so long to get to review your PR.
Regarding the implementation - I don't think having .Mui-focused and .Mui-focusVisible on different elements isn't the best solution. If we're going with the pattern used by Chrome's omnibox, I think that styling elements on hover with CSS should be enough.
What I'm worried about, though, is that it'll change the behavior in existing applications and there may be developers relying on the current behavior.
We may need to wait until v6 before we fix it this way.
Two things that come to my mind that we can do today:

put this behavior behind a prop (disableHighlightOnHover) that's false by default
expose the highlightedItem as a controlled prop. This way, it will become possible for developers to decide when a highlight should be changed

cc @mnajdova for thoughts

put this behavior behind a prop (disableHighlightOnHover) that's false by default

Agree, we should do this as part of this PR, in v6 we could make this default behavior and drop the prop.

expose the highlightedItem as a controlled prop. This way, it will become possible for developers to decide when a highlight should be changed

Agree, we can anyway do this regardless of the previous implementation. Having a controlled prop for it sounds reasonable.

Hey! Thanks @mnajdova - quick question - is there an issue that I could track when this is done? :) Right now it causes a small regression for our project. No show stopper, but it would be good to be able to see when to update the library 👍🏽

@einvalentin I can prioritize reviewing it if we have a contribution from the community, but I have no bandwidth to do it myself.


simulation configuration bug with assigning sources value

Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

Description of the bug
Integer values are not accounted
Steps To Reproduce
NA
Which Operating System are you using?
Windows
Which Python version are you using?
3.10
Installed packages
Pyaedt

Resolved and fix merged in PyEDB


Temperature incorrect when reported in F

When a device reports temperature in Fahrenheit, it is being reported/interpreted as Celsius. The matter spec apparently only supports reporting in Celsius. For example, 72 F gets reported as 72 C or 162 F.

Hi,
thanks for pointing it up.
I will check it.
Or we do a conversion or Matter supports it.


Enable SerializeFeature.MapSortField for deterministic order

Similar to the change you already merged for JSONPParseTest2.java:
Test parses a text to a JSONObject and compares its toJSONString representation to a hard-coded string. However, JSONObject uses a HashMap that does not guarantee any specific order of entries. Therefore, the assertion in the test can fail if the order differs.
This PR uses SerializerFeature.MapSortField to make the order deterministic and appropriately modifies the corresponding test assertion.

Codecov Report

Merging #3165 into master will decrease coverage by 0.12%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3165      +/-   ##
============================================
- Coverage     80.53%   80.40%   -0.13%
- Complexity     7235     7312      +77
============================================
  Files           145      155      +10
  Lines         27131    27380     +249
  Branches       6501     6564      +63
============================================
+ Hits          21851    22016     +165
- Misses         3398     3456      +58
- Partials       1882     1908      +26

Impacted Files
Coverage Δ
Complexity Δ

...tjson/parser/deserializer/SqlDateDeserializer.java
84.72% <0.00%> (-8.83%)
21.00% <0.00%> (+1.00%)
:arrow_down:

...java/com/alibaba/fastjson/parser/ParserConfig.java
80.33% <0.00%> (-3.67%)
216.00% <0.00%> (+9.00%)
:arrow_down:

.../fastjson/parser/deserializer/MapDeserializer.java
86.36% <0.00%> (-2.84%)
65.00% <0.00%> (+1.00%)
:arrow_down:

...n/java/com/alibaba/fastjson/util/JavaBeanInfo.java
86.34% <0.00%> (-1.43%)
210.00% <0.00%> (+2.00%)
:arrow_down:

src/main/java/com/alibaba/fastjson/JSONObject.java
85.43% <0.00%> (-0.63%)
95.00% <0.00%> (+1.00%)
:arrow_down:

...main/java/com/alibaba/fastjson/util/FieldInfo.java
86.20% <0.00%> (-0.35%)
91.00% <0.00%> (ø%)

src/main/java/com/alibaba/fastjson/JSON.java
84.56% <0.00%> (-0.31%)
149.00% <0.00%> (+1.00%)
:arrow_down:

...com/alibaba/fastjson/parser/DefaultJSONParser.java
88.03% <0.00%> (-0.25%)
321.00% <0.00%> (+1.00%)
:arrow_down:

.../java/com/alibaba/fastjson/parser/JSONScanner.java
76.01% <0.00%> (-0.19%)
512.00% <0.00%> (+3.00%)
:arrow_down:

src/main/java/com/alibaba/fastjson/JSONPath.java
76.01% <0.00%> (-0.06%)
263.00% <0.00%> (+5.00%)
:arrow_down:

... and 21 more

Continue to review full report at Codecov.

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


[Feature Request] show_tabs

Is there any way to change from [hide_tabs] to [show_tabs].
Because when i add some new view, every time i have to change exceptions conditions of hide_tabs for all devices.

show_tabs is on my list of features to add so stay tuned

Sorry for offtop, but is any way to increase height from 48px to 64px?

@KKnishev  It's not something I'm going to add to the card, but I've mentioned how you can edit it yourself here:
https://community.home-assistant.io/t/compact-custom-header-custom-user-device-views/83716/386

@maykar thanks a lot! -48px is what I want ;)

Added in 1.0.0b6


cruft update writing to STDOUT and not showing interactive mode

cruft Version: 2.7.0
Python 3.9.1
macos 10.15.7
using zsh
I'm using

cruft update -c target-branch
I see a ton of content going to STDOUT (I think it's all of the template data)
process exits. I see no interactive prompt and I don't see changes stages in the git repo

Given the lack of information in this issue, I am closing this.


For MSVC windowsSdkVersion & compilerPath should be auto detected.

For different PC, they may different.

rescan resolved.