Release of xsct?

Hi,
I'd like to bring this package to Debian (as an alternative to the sct package that Debian currently has), as I see this package being more/better maintained than setcolortemperature upstream. Also the mult-display support is a good to have feature.
For tracking upstream changes, it is really helpful to package only released versions. Do you think, you could make a release of xsct as it currently is and prepare follow-up release whenever you see fit?
For me, a release version tag on this Git repo is sufficient as a release.
Thanks,
Mike (aka sunweaver at debian.org)

Hi Mike,

Do you think, you could make a release of xsct as it currently is and prepare follow-up release whenever you see fit?

Absolutely. There have been different versions of this project already, but no corresponding git tags. I've tagged the current state of master as version 1.6, which is consistent with CHANGELOG:
https://github.com/faf0/sct/blob/f73e8736b3b03eb36d3c8ac96c047a2ddafa301b/CHANGELOG#L3
Also, I appreciate your efforts to release xsct as a Debian package. Thank you!
Best,
Fabian

Hi @sunweaver .
See also https://sourceforge.net/projects/debiannoofficial/files/wheezy-update/x11/xsct_1.5-wheezy_i386.deb


how to determin the proper nis threshold for each hoi category?

Hi, thanks for your wonderful job!
NIS strategy has been proved to be very effective for HOI detection task. As shown in the code,  both TIN and IDN set different NIS thresholds for different hoi categories. Could please tell me how do you search it?
Thanks a lot!

A common way is to randomly select some samples from the train set for each HOI and construct a validation set, then use a grid search to find an optimal threshold for each HOI. But for different models, NIS may perform differently for the same thresholds, due to the various prediction biases of different models.
For some rare HOIs, please be careful. Because NIS may delete all samples in an image when all pairs are below the threshold. Sometimes, rare HOIs containing only one or several images are better to be excluded from NIS.

A common way is to randomly select some samples from the train set for each HOI and construct a validation set, then use a grid search to find an optimal threshold for each HOI. But for different models, NIS may perform differently for the same thresholds, due to the various prediction biases of different models.
For some rare HOIs, please be careful. Because NIS may delete all samples in an image when all pairs are below the threshold. Sometimes, rare HOIs containing only one or several images are better to be excluded from NIS.

Get it. Thanks for your answer^_^.
By the way, in the inference stage of IDN, it seems that the model output would be devided by a factor(fac_i, fac_a and fac_d) before mAP evaluation. what's the meaning of these factors and why are they different?

Get it. Thanks for your answer^_^.
By the way, in the inference stage of IDN, it seems that the model output would be devided by a factor(fac_i, fac_a and fac_d) before mAP evaluation. what's the meaning of these factors and why are they different?

We incorporate three streams into one final inference result.
AE stream outputs logits and uses sigmoid function to project the output into probability, and the other two streams output distances and use exponentional function to project the output into probability.
This makes the combination tricky, since the diverse characteristic held by the three streams.
Besides, different streams also learn different biases, which also needs mitigating.
To solve this, we take inspiration from LIS, proposed by TIN. We impose an LIS-like function on the output of the three streams before projecting them into the probability space. In detail, we divide the output logits/distances with a factor for each class. By doing this, we expect that the transformed probability of different streams could be coherent, and the bias of different streams could be mitigated.
We got the factors by collecting about 6000 images from the training set as the validation set, then providing 20 candidate factors per class per stream. The goal is to select the factors that could produce the best performance on the collected validation set. By the way, we found that it tends to assign smaller factors for streams that performs relatively better on a class.
The factors are also learnable, however, the performance wasn't as good as choosing from given candidates, which we attributes to the over-detailed characteristic of the learning process.

We incorporate three streams into one final inference result.
AE stream outputs logits and uses sigmoid function to project the output into probability, and the other two streams output distances and use exponentional function to project the output into probability.
This makes the combination tricky, since the diverse characteristic held by the three streams.
Besides, different streams also learn different biases, which also needs mitigating.
To solve this, we take inspiration from LIS, proposed by TIN. We impose an LIS-like function on the output of the three streams before projecting them into the probability space. In detail, we divide the output logits/distances with a factor for each class. By doing this, we expect that the transformed probability of different streams could be coherent, and the bias of different streams could be mitigated.
We got the factors by collecting about 6000 images from the training set as the validation set, then providing 20 candidate factors per class per stream. The goal is to select the factors that could produce the best performance on the collected validation set. By the way, we found that it tends to assign smaller factors for streams that performs relatively better on a class.
The factors are also learnable, however, the performance wasn't as good as choosing from given candidates, which we attributes to the over-detailed characteristic of the learning process.


Implement a standardized pattern for setting parameters on Bicep examples

Benefit/Result/Outcome
So that an IT Admin has flexibility in how to run Bicep/ARM templates in the bicep/examples folder.
Description
Most of our examples use the shared variable pattern for invoking the Bicep templates. It is a good pattern, however, it is limited because the user is required to have a json file with a hard-coded name and structure, and Bicep compiles the contents of the file into the ARM template, preventing us from adding the ARM template to the repo.
We want to continue to support the shared variable file pattern, but we need to also support other patterns for setting parameters, including using a parameters file, a PoweShell object, command line parameters, environment variables, and the deployment resource provider.
The scope of this work includes:

Establishing a pattern that all examples can implement, including required files, file names, etc.
Implementing the pattern on all existing examples
Documentation in the bicep/examples/README.md

There may be need to add additional templates to each example, e.g., using the shared variable file pattern may require having a separate template that loads the shared variable file and executes the main example template as a module.
Here's an example of what the pattern could look like. This is not a specification, but an example of how to implement the acceptance criteria for this backlog item.
examples
└── tier3
    ├── deployment-rp.tier3.bicep  <-- Bicep template that uses Azure deployment resource provider to look up MLZ deployment outputs and map to tier3 template inputs.
    ├── README.md                    <-- Parameter documentation. Link to parent folder README.md for how to execute the template.
    ├── parameters.tier3.json        <-- Example of a Bicep parameters file in json, with values defaulted from tier3.bicep.
    ├── parameters.tier3.ps1         <-- Example of a PowerShell parameters object, with values defaulted from tier3.bicep.
    ├── shared-variable.tier3.bicep  <-- Bicep template that uses the shared variable file pattern and maps parameter values to tier3.bicep.
    ├── tier3.bicep                  <-- The main template for the example.
    └── tier3.json                   <-- The ARM template compiled from the tier3.bicep template.

NOTE: The above is an example of a repeatable pattern to implement for all examples. It is not requirements or specification.

Automation could be used to generate some of the files, like the json parameters file and the PowerShell parameters object file.
See #536 for additional context.
Acceptance Criteria

The bicep/examples folder contains a readme with descriptions of the patterns and examples for running the examples using the patterns below.
A pattern is established for all examples and guidance exists for developers on how to implement the pattern.
Naming conventions are established for files in the examples folder.
Optional: an automated way of generating some of the files, like a json parameters file and a PowerShell parameters object.
All examples are updated to allow for using these methods to set template parameters:

Command line
json parameters file
Environment variables
PowerShell object file
Shared variable file pattern
Deployments resource provider

Not implementing.


Add support for dbt core 1.4

Resolves https://github.com/dbt-msft/dbt-sqlserver/issues/333.
Checklist:

[x]  support Python 3.11 (only if your adapter's dependencies allow)
[x]  Consolidate timestamp functions & macros
[x]  Replace deprecated exception functions
[ ]  Add support for more tests

Works with my dbt projects using both Azure SQL Database and Microsoft SQL Server 2017.
This PR requires changes around incremental_predicates, but as I do not use incremental materialisations much, I do not have time to test everything properly and write tests, so for now I have marked this feature as not implemented. The changes required do not look huge, so I may try to add them later.
I believe, there are some problems with the CI in this repository, but as you can see all the tests are green here:
https://github.com/l-j/dbt-sqlserver/pull/4/checks

Hello guys! Any news about this PR?

Looks like we need a CI-container for Python 3.11. Who knows how to get that in here?

@mikaelene My understanding is that with the current Github Actions configuration, we can only have a container for the changes that are already on the master branch (see: https://github.com/l-j/dbt-sqlserver/blob/master/.github/workflows/publish-docker.yml#L9).
And basically, this is what I did to my fork to make CI work. so maybe we should also build it for pull requests to master? I cannot see the list of maintainers for this repository. @dataders, can you help with that?

Ahh. Get it now. So basically these test will not pass until we merge this to master. Maybe we should create a PR for just building the containers for 3.11? I am a maintainer (and also the creator), but haven't been very active in a while. If you create a PR for just building more versions of the containers, I can approve. It is always easier to merge a PR with green checkmarks.
I haven't used incremental predicates but it looks like a neat feature. But I guess they are not needed to make this release. Maybe should write something in the docs on this.

@mikaelene I think this will be enough:
https://github.com/dbt-msft/dbt-sqlserver/pull/345/commits/03b490c35ddfa23cd1535186d2ad0067afa7b90a
Now build process is waiting for approval.

@mikaelene I see that the step Publish Docker images failed with the following error message:
ERROR: denied: installation not allowed to Write organization package
Error: buildx failed with: ERROR: denied: installation not allowed to Write organization package

And indeed, according to this page, it can be caused by missing permissions.
If we change the trigger rule to allow pull requests to trigger the publication of Docker images, we will need to make additional changes to the repository configuration as described [here] (https://github.com/actions/runner/issues/1039#issuecomment-1019972535).

After modifying setup.py, we get the following:
The conflict is caused by:
    dbt-tests-adapter 1.4.1 depends on dbt-core==1.4.1
    dbt-sqlserver 1.4.0 depends on dbt-core~=1.4.5

so I loosen the dev requirements and pin dbt-tests-adapter to the dbt-core version.

closing because your commits were merged via #350. Thanks @l-j for getting the ball rolling on this btw!


[ENTESB-22698] Upgrade to Spring Framework 5.3.32

Fixes: #

Should be a minor change. No rush @igarashitm ;)

One of the failures is:
Could not extract archive: '/Users/runner/.m2/repository/com/github/eirslett/node/14.17.3/node-14.17.3-darwin-x64.tar.gz': EOFException

definitely not Spring Framework related ;)

Merging - windows/java8 passed, windows/java11 is stuck at download but must be unrelated.


Ensure checks will successfully run for resource-manager prs

This is a test. if python - servicebus - ci runs, this is a success and we can broaden the yml update to the rest of the repository.

Can one of the admins verify this patch?

/azp run python - servicebus - ci

/azp run python - servicebus - ci


PVF: NaN canonicalization & deteriministic stack

Closes https://github.com/paritytech/substrate/issues/8395
Closes https://github.com/paritytech/substrate/issues/8393
Closes #9038
It would be great to run a burn-in with within the PVF context.
polkadot companion: https://github.com/paritytech/polkadot/pull/3373

@ordian @athei please make a note that now the limits are passed from the polkadot side. They are still hardcoded there. The explaination how the values are chosen live there now.

bot merge


get Hardware Serial Number in Windows giving me "To be filled by O.E.M."

Thanks for your nice effort.
Can you please help me why I am getting this "To be filled by O.E.M." instead of the serial number in windows 7 machine?
Thanks in advance.

Please check in regedit this path:
Computer\HKEY_LOCAL_MACHINE\HARDWARE\DESCRIPTION\System\BIOS
Is there any keys here with the value "To be filled by O.E.M."?


Anthropic's Terms of Service

What does potential violation of Anthropic's Terms of Service mean?

For any questions about Anthropic's Terms of Service, please contact Anthropic directly. ClaudeSync operates independently and is not affiliated with Anthropic.


Feature : replace hand-crafted auth things with Supabase Remix's package ?

Hello there,
Someone ask this and maybe it's a good idea to not scatter people with multiple ways to handle auth in Remix with Supabase.
Maybe I should rewrite auth with https://supabase.com/docs/guides/auth/auth-helpers/remix.
I don't want to replace Prisma 🥶 but only the Auth part.
After that, it should be a breeze to replace Prisma with Supabase to query your database if this It what you need for your project.
I'll probably do some abstraction to keep helpers like requireAuthSession and keep things simple to use in protected loaders/actions.
Is It something you are interested in or do you prefer to be able to modify what you want with the actual auth implementation?

I’m waiting to be sure that the way it handles cookies (HttpOnly: false) feets my security requirements.

First of all, thanks for your work because it's very helpful. I used your stack to bootstrap my app, but I bypassed all prisma to make sure RLS policies work for my multi-tenancy use cases.
Now that I'm wanting to upgrade to v2, I have a lot of work to do. :) One of the things that I'd love to see in the future is a way to pull in the latest changes from this stack without worrying I'm going to lose any changes.  For example, I extended AuthSession to add custom claims in the jwt metadata.
export type AuthSession = {
    accessToken: string;
    refreshToken: string;
    userId: string;
    email: string;
    expiresIn: number;
    expiresAt: number;
    claims: {
      provider?: string
      [key: string]: any
    }
  }

Thanks @timgit ,
Unfortunately, Remix provides no way to upgrade a Stack after creating your app :(
For sure, I'm not the best to don't make any breaking changes as I change a lot of things recently, improving from my daily use of the code in this stack 🤣
I'll try to make more atomics commits to make it easy to follow.
I have to admit that this stack is not the best for RLS because I mainly use Supabase through Prisma (mainly for performance reasons).
I thought of doing an npm package with everything to handle auth and get a supabase client, but now there is the official Supabase auth package I don't know.
Basically, things that you may be interested in are :

auth module
user service
Supabase integration

For your AuthSession extends, should should modify this mapper.


Add setting to show attack roll result (AC check) card to players

Closes #3156

@krbz999 Thanks for quick review (were hoping to grab a built minjs, but you don't build them for PRs)
Fixed the code, tested on my own instance, works as intended without reload, PTAL.
Player (left) side, GM side (right) False/True:

Can be improved by an addional logic to hide/show precise AC number for players, but i think it's a separate commit.


Moving all coins to all deposits to one address?

How would I be able to do this simply?

@jonleach445 This can be done if you will be using a cryptocurrency payment provider. But keep in mind that they will charge a commission for this

@jonleach445 You can't use one address for each user. You don't need to go through each user's seed phrases from the database, the bot will send you notifications about new top-ups along with the seed phrase.

Ah, okay, it's quite tedious not just because of that, but because I get hundreds of notifications of each deposit a day that I have to be taking out, it's a lot of work to do manually

@jonleach445 in this case, maybe it makes sense for you to develop a script that will auto-withdraw all cryptocurrency from your mnemonic phrases to the same address. But note that it will work only with BTC and LTC, for auto withdrawal of USDT TRC-20 will need TRON. Also USDT TRC-20 transactions do not support multiple inputs.

@jonleach445 email me at<EMAIL_ADDRESS>with your Telegram username and I'll message you on Telegram.

This functionality comes only on a paid basis. At the moment it is implemented to withdraw BTC and LTC deposits of users to one address directly from the bot's admin.
Buy.


ZED SDK on XAVIER ISSUE

I am currenlty playing with Jetson Xavier Dev Kit. The sdk 2.7 for xavier is installed (the terminal says its installed at least). However, the tools in the tools directory are installed as  a shared library rather than executable. The tools cannot be accessed and the SDK doesnot recognise the camera. I tried to make it executable but did not succed. I have been using ZED sdk for my PC with ubuntu 16.04 LTS which works perfectly fine with all the APIs. But the current jetpack comes with 18.04 LTS image which I might not be familiar with. Any suggestions on this.

Hi @kdhakal18,
I think you have installed the wrong version of the SDK. Have you download the SDK for the Xavier?
https://download.stereolabs.com/zedsdk/2.7/tegraxavier

Hi @Myzhar No, I have installed the right SDK. I went through some ubuntu forums and there were issues regarding the handling of executable files for 18.04 LTS. I will try to run update and upgrade ubuntu and reinstall SDK. Lets see if things get sorted out.

@Myzhar No success!!

I forward the issue to the dev team and we will be back to you as soon as possible

.It works with giving the permission through terminal with "chmod" command. It makes sense as ubuntu 18.04 is based upon GNOME unlike 16.04 which was based on Unity. Thanks for the support


smaller binaries when compiled with static ldflag

What version of Go are you using (go version)?
go version go1.6.3 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/spotter/gocode"
GORACE=""
GOROOT="/usr/lib/go-1.6"
GOTOOLDIR="/usr/lib/go-1.6/pkg/tool/linux_amd64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"
What did you do?
compiling a project that includes cgo files, hence would normally make a dynamic linked binary (against C runtime) and then compiles it statically.
i.e.
go build ./path/to/command.go
vs
go build --ldflags '-extldflags "-static"' ./path/to/command.go
What did you expect to see?
I expected the dynamic binary to be smaller than the fully statically linked binary.
What did you see instead?
the statically linked binary was significantly smaller, and I'm not the only one to see this
see this from reddit where someone sees similar behavior
https://www.reddit.com/r/golang/comments/46gbdz/binary_sizes_in_go/d058h1u/

For questions about Go, see https://golang.org/wiki/Questions.
It looks like you're not comparing dynamic vs static, but dynamic vs static+stripped.

Stripped is even smaller (similar) in both cases.


Fix date. 30 September 2021 is a date in the future!

Fix date. 30 September 2021 is a date in the future!

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


[memoize] does not have typescript definitions

Hello, as in the title the memoize package does not have typescript definition which makes it annoying to use with typescript (no type checking and eslint error).

Hello, good catch. Can you make a PR to add them? 🙂


Tensorization happens during bind not evaluation.

An issue was filed on WinML GitHub where the customer pointed out that our docs say that tensorization happens on evaluation. https://github.com/Microsoft/Windows-Machine-Learning/issues/132#issuecomment-457689179
This change fixes this statement.

OPS Build status updates of commit 29dced9:
:clock10: Preparing: average preparing time is 45 sec(s)

OPS Build status updates of commit 29dced9:
:clock10: Preparing: average preparing time is 45 sec(s)

OPS Build status updates of commit 29dced9:
:clock10: Incremental building: average incremental building time is 22 sec(s)

OPS Build status updates of commit 29dced9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/integrate-model.md
:white_check_mark:Succeeded
View

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


jmx-plugin - tidy up JMX operation page

The JMX operation page could use a bit of layout work.  Perhaps some descriptive text for starters explaining what the page does, maybe improve the list layout of the operations, etc.
Also the buttons that do stuff (execute, reset etc) for the form should maybe go underneath the form.  And the "Back" button could maybe just be a list icon.

@davsclaus, have worked over this page a bit, would love some feedback...

super work @gashcrumb


compilation error

Hello Leon,
I am admiring of all yours creations . Great !
I would like to make the WIFI clock (with the Wemos d1 mini board)
I selected the board LOLIN (Wemos) D1 R2 & mini (in the choise list of boards there is no Wemos D1 mini)
Below is the error message when compiling
Since 3 weeks I try to solve the problem .... Without success
If I use the library Adafruit_Neopixel (of course by modifying your program a bit): it works .... But I would like to understand my mistake
Thanks for your help
errors.pdf

You should upgrade your fastled library to at least 3.2.6

thanks a lot for your help
De : ThEWiZ76<EMAIL_ADDRESS>Envoyé : vendredi 21 juin 2019 08:01
À : leonvandenbeukel/Round-LED-Clock<EMAIL_ADDRESS>Cc : Pierre01480<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Objet : Re: [leonvandenbeukel/Round-LED-Clock] compilation error (#9)
You should upgrade your fastled library to at least 3.2.6
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/leonvandenbeukel/Round-LED-Clock/issues/9?email_source=notifications&email_token=AMEPERVLW6LADSPJ2L4VYTLP3RVCHA5CNFSM4HZUVOJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYHQN5Q#issuecomment-504301302 , or mute the thread https://github.com/notifications/unsubscribe-auth/AMEPERTWPTWDKHDH7OIFMDTP3RVCHANCNFSM4HZUVOJQ .


Fixing Manta inversions in varfish_annotator/annotate_sv (#245)

@eudesbarbosa this should resolve the issues that we had with DRAGEN

@eudesbarbosa I agree that having no tests is bad in principle. I'm adding a ticket for this but we need a solution now. Crafting the tests would also require creating a fake reference sequence...

@eudesbarbosa should be good to merge

Hrm, I'm getting a NPE now from VarfishAnnotator. Oh, well.


Client framework created

I've found an easier way to install and run this code. I'm closing this PR


apollo 5.5 & 6.0 module/planning/tasks/deciders: LaneChangeDecider::IsPerceptionBlocked() question

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 18.04): Linux Ubuntu 20.04
Apollo installed from (source or binary): official git reporsitory
Apollo version (3.5, 5.0, 5.5, 6.0): version 5.5 & 6.0
Output of apollo.sh config if on master branch: don't know what this mean

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:
hello dear developers, I have a question when reading planning module code:
in LaneChangeDecider::IsPerceptionBlocked():

right_most_angle = beam_heading
...
left_most_angle = beam_heading - search_angle

then:
std::fabs(common::math::NormalizeAngle(left_most_angle - right_most_angle))

is this angle the search_angle when beam first blocked by obstacle poligon point?
what is the meaning of this angle?
should left_most_angle = beam_heading and then the angle mentioned before becomes the angle that beam blocked by the obstacle?
Supporting materials (screenshots, command lines, code/script snippets):

The beam_heading is rotate from right to left, and when it found obstacle then will search for the obstacle left boundary. If the (left-right) > 0.5(radian) then means it is blocked.
sorted
reference_line_info.path_decision().obstacles() should be sort from right to left, Otherwise right_most_angle will be wrong
right_most_angle
if obstacles are sorted, then right_most_angle will found only once be the right boundary of the rightmost obstacle.
left_most_angle
after found right_most_angle, left_most_angle will continue found be 0
In summary
So, this is an issue to be fixed, thank you for your submission.
The real intention is shown in the figure below

Hi @daohu527,
I want to ask about the formula in functionIsPerceptionBlocked.
In fact, I'm fine with your XY-plane figure visualizing the left_most_angle and right_most_angle. But when I see in the actual code (after @randomacco's fixed commit), I still cannot figure out how dev calculated left_most_angle.
const double beam_heading = common::math::NormalizeAngle(
          adv_heading - 0.5 * search_range + search_angle);
...

left_most_angle = beam_heading - search_angle;

And this infers left_most_angle = adv_heading - 0.5 * search_range which is a difference of 2 constant values, and consequently the result of left_most_angle is constant and does not depend on search_angle.
How this could be correct because left_most_angle and right_most_angle need to vary dynamically based on size of specific obstacle.

Yes I think it needs to be added in addition to fixing here
      if (right_most_found && !obstacle_polygon.HasOverlap(search_beam)) {
        left_most_angle = beam_heading;
        break;
      }

Yes I think it needs to be added in addition to fixing here
      if (right_most_found && !obstacle_polygon.HasOverlap(search_beam)) {
        left_most_angle = beam_heading;
        break;
      }

Thank for your answer. I've thought the same as you, and cannot explain why they calculated differently in the actual code.


typo fix in update_items/app.py

Found a slight typo in update file. 'isActive' was 'itActive' and adding another column/attribute to the table. Cheers! Absolutely phenomenal serverless CRUD demo!

thank you


Inaccurate reproduction results on QM9

When I finetune the model from checkpoint "N-Step-Checkpoint_3_30000.ckpt",
the reproduction results are much higher than them report in the paper.
For example, I got 1.4575 on u0 task, while the reported result on the same task is 0.3211.
I have checked the finetune code several times, I cannot find issues.
Is there anyone who get similar results to the reported ones on any regression task?

Please see the README. The provided checkpoints are for 10% ZINC + 10% PubChem, not the full MoLFormer-XL weights.


FetchContent and cmake preset in separate build directory lead to Intellisense include issue

Brief Issue Summary

When using FetchContent together with cmake preset with a separate build directory, Intellisense does not find included files.

I think it is the minimal example to reproduce the issue.
main.cpp
#include <Eigen/Core>

int main()
{
    return 0;
}

CMakeLists.txt
cmake_minimum_required(VERSION 3.14)
project(foo)

set(BUILD_TESTING OFF)
include(FetchContent)
FetchContent_Declare(
    Eigen
    GIT_REPOSITORY https://gitlab.com/libeigen/eigen.git
    GIT_TAG        3.3.9
)
FetchContent_MakeAvailable(Eigen)

CMakePresets.json
{
    "version": 2,
    "configurePresets": [
        {
            "name": "default",
            "generator": "Unix Makefiles",
            "binaryDir": "${sourceDir}/../build/${presetName}/test/",
            "warnings": {
                "dev": false
            }
        }
    ],
    "buildPresets": [
        {
            "name": "default"
        }
    ]
}

In main.cpp, on the first line, I have the two follow errors from Intellisense
#include errors detected based on information provided by the configurationProvider setting. Squiggles are disabled for this translation unit (/home/clement/test/main.cpp).C/C++(1696)
cannot open source file "Eigen/Core"C/C++(1696)
CMake Tools Diagnostics

{
  "os": "linux",
  "vscodeVersion": "1.63.2",
  "cmtVersion": "1.9.2",
  "configurations": [
    {
      "folder": "/home/clement/test",
      "cmakeVersion": "3.22.1",
      "configured": true,
      "generator": "Unix Makefiles",
      "usesPresets": true,
      "compilers": {
        "C": "/usr/bin/cc",
        "CXX": "/usr/bin/c++"
      }
    }
  ],
  "cpptoolsIntegration": {
    "isReady": true,
    "hasCodeModel": true,
    "activeBuildType": "",
    "buildTypesSeen": [
      ""
    ],
    "requests": [
      "file:///home/clement/test/main.cpp"
    ],
    "responses": [],
    "partialMatches": [],
    "targetCount": 372,
    "executablesCount": 357,
    "librariesCount": 4,
    "targets": []
  },
  "settings": [
    {
      "communicationMode": "automatic",
      "useCMakePresets": "auto",
      "configureOnOpen": true
    }
  ]
}

Debug Log

[main] Building folder: test
[main] Saving open files before configure/build
[build] Starting build
[driver] Start build
[proc] Executing command: /opt/cmake/cmake-3.22.1-linux-x86_64/bin/cmake --build /home/clement/build/default/test
[cmakefileapi-parser] Read reply folder: /home/clement/build/default/test/.cmake/api/v1/reply
[cmakefileapi-parser] Found index files: ["cache-v2-28ad9dc0cb89a8db0155.json","codemodel-v2-7ac9e5dea8c71725fc68.json","directory-.-f5ebdc15457944623624.json","directory-_deps.eigen-build-073bd620eba4f00979fc.json","directory-_deps.eigen-build.Eigen-81b45db3303cfbdab0fb.json","directory-_deps.eigen-build.bench.spbench-b97669f5033dfa0d36b7.json","directory-_deps.eigen-build.blas-96e09d93579be95e5c8b.json","directory-_deps.eigen-build.demos-04642bc911a1cf43e9b5.json","directory-_deps.eigen-build.doc-90334daed98bd008726a.json","directory-_deps.eigen-build.doc.examples-70b743515d7b898f1bf3.json","directory-_deps.eigen-build.doc.snippets-93545466ed40fa64097c.json","directory-_deps.eigen-build.doc.special_examples-f86e1339c6bdeab96d2f.json","directory-_deps.eigen-build.lapack-5855e6c00e40820dce6f.json","directory-_deps.eigen-build.scripts-a3f8355f074a23808fab.json","directory-_deps.eigen-build.unsupported-c92e0d2c4f43baa3564c.json","directory-_deps.eigen-build.unsupported.Eigen-ac56fe3da282f41d0ce0.json","directory-_deps.eigen-build.unsupported.Eigen.CXX11-3952c2de2ab3be97b9b4.json","directory-_deps.eigen-build.unsupported.doc-c7f23cc7ebabe7fc522c.json","directory-_deps.eigen-build.unsupported.doc.examples-cfb9f106ad3859e4543f.json","directory-_deps.eigen-build.unsupported.doc.snippets-e4311abf5def70ab27f5.json","index-2022-01-17T14-47-14-0327.json","target-CustomizingEigen_Inheritance-40612f40a8ec15f25d9e.json","target-Cwise_erf-23ef15b66ab30153c085.json","target-Cwise_erfc-8dafb66c8c0adc462b67.json","target-Cwise_lgamma-32693dcad718d64002ab.json","target-DenseBase_middleCols_int-f44c25a8fe64ade25467.json","target-DenseBase_middleRows_int-577d5e41c21dc3443c8e.json","target-DenseBase_template_int_middleCols-8e0f425c576f7bc10272.json","target-DenseBase_template_int_middleRows-c52ad0e245b97173bdea.json","target-QuickStart_example-d865d275e9bf080abb1e.json","target-QuickStart_example2_dynamic-13a2ed625e6be1f1950f.json","target-QuickStart_example2_fixed-47e64378408811466e8e.json","target-TemplateKeyword_flexible-570efa05edd797384a5e.json","target-TemplateKeyword_simple-09da5e9766f20889f2cb.json","target-TutorialInplaceLU-96502f7dcb67ab7c1062.json","target-TutorialLinAlgComputeTwice-de9fcecdcb5aa74ef3c8.json","target-TutorialLinAlgExComputeSolveError-4e0e294bd123b7c4e0d2.json","target-TutorialLinAlgExSolveColPivHouseholderQR-63945017c63674005ee0.json","target-TutorialLinAlgExSolveLDLT-40c3bd727e14898f78e8.json","target-TutorialLinAlgInverseDeterminant-7c9d4ccc12d7abf447c6.json","target-TutorialLinAlgRankRevealing-051f53c5c0b1d1aca209.json","target-TutorialLinAlgSVDSolve-077d395b9ef820a7bf2b.json","target-TutorialLinAlgSelfAdjointEigenSolver-8da062a736a7de87db7f.json","target-TutorialLinAlgSetThreshold-af25e144b930fea81d46.json","target-Tutorial_ArrayClass_accessors-69a3403125314e157baa.json","target-Tutorial_ArrayClass_addition-e113c78b8b598832238a.json","target-Tutorial_ArrayClass_cwise_other-032b34e8c83224fb7882.json","target-Tutorial_ArrayClass_interop-3d6394b54d2784bfff77.json","target-Tutorial_ArrayClass_interop_matrix-37eb284ce699c751c5a3.json","target-Tutorial_ArrayClass_mult-9beb85e13938d335b97c.json","target-Tutorial_BlockOperations_block_assignment-911e9ff4e8bea36d75ba.json","target-Tutorial_BlockOperations_colrow-7450bab96797ae79506e.json","target-Tutorial_BlockOperations_corner-7b02127146e9f7be354e.json","target-Tutorial_BlockOperations_print_block-5cddf8a4d42ad0ce6e7e.json","target-Tutorial_BlockOperations_vector-92f3a4f030e38b2f50fe.json","target-Tutorial_PartialLU_solve-a1ec62a2a84b384ff3c4.json","target-Tutorial_ReductionsVisitorsBroadcasting_broadcast_1nn-d44c79ea9178d7b46050.json","target-Tutorial_ReductionsVisitorsBroadcasting_broadcast_simple-dbc0337a7c5b863e16a8.json","target-Tutorial_ReductionsVisitorsBroadcasting_broadcast_simple_rowwise-3f2ca209636ba38475ee.json","target-Tutorial_ReductionsVisitorsBroadcasting_colwise-8763b4bef33dfb299fc7.json","target-Tutorial_ReductionsVisitorsBroadcasting_maxnorm-33850d8186080c307d0c.json","target-Tutorial_ReductionsVisitorsBroadcasting_reductions_bool-b8638fbcfb19943a524a.json","target-Tutorial_ReductionsVisitorsBroadcasting_reductions_norm-a8e15758e1350f2a3f8a.json","target-Tutorial_ReductionsVisitorsBroadcasting_reductions_operatornorm-237019f06c78c6bc086e.json","target-Tutorial_ReductionsVisitorsBroadcasting_rowwise-7d7ae276806290a8b982.json","target-Tutorial_ReductionsVisitorsBroadcasting_visitors-e525f2fd25511b784ddb.json","target-Tutorial_simple_example_dynamic_size-b10c47bad1828473feec.json","target-Tutorial_simple_example_fixed_size-c79ecf91ac51d44e424c.json","target-all_examples-6e3aa8ec34c9aff0b001.json","target-all_snippets-29c800548dcda621c31d.json","target-blas-c98d776e6c03e19b4bd1.json","target-class_Block-389d6ebf93def2b22665.json","target-class_CwiseBinaryOp-40e276c5e4c727217aae.json","target-class_CwiseUnaryOp-730310106af07224d69e.json","target-class_CwiseUnaryOp_ptrfun-103fdd13ef7ef344077e.json","target-class_FixedBlock-6865b6ad7aa5819cef48.json","target-class_FixedVectorBlock-b8fcc3b58f0a29c2616f.json","target-class_VectorBlock-7f3f2c06e5b4b87dea39.json","target-compile_AngleAxis_mimic_euler-14acfe1094594471ef27.json","target-compile_BiCGSTAB_simple-c560f1acd9549c2d6bea.json","target-compile_BiCGSTAB_step_by_step-cf44ff8189bc6c9c5d36.json","target-compile_ColPivHouseholderQR_solve-a74bb8723b900e4d2f04.json","target-compile_ComplexEigenSolver_compute-2db3423c128526705292.json","target-compile_ComplexEigenSolver_eigenvalues-c46517c1b13d5a96aeea.json","target-compile_ComplexEigenSolver_eigenvectors-85b203bb5a2e25424ad6.json","target-compile_ComplexSchur_compute-87c710616fd970c9d30b.json","target-compile_ComplexSchur_matrixT-32ebbb5140b87efe33e4.json","target-compile_ComplexSchur_matrixU-0753734e625f07905330.json","target-compile_Cwise_abs-dcbe51ae414713275215.json","target-compile_Cwise_abs2-b3a0aae2d409720760c6.json","target-compile_Cwise_acos-d0fd2c103b0b02edd07a.json","target-compile_Cwise_arg-a80af23e0500c0149b92.json","target-compile_Cwise_array_power_array-d1d60ac96108a6f59651.json","target-compile_Cwise_asin-381183ba1b212026f4c7.json","target-compile_Cwise_atan-4ce620539b4eee993a54.json","target-compile_Cwise_boolean_and-3d95dda55e5bc1e42271.json","target-compile_Cwise_boolean_not-aea892b6308809d2ce04.json","target-compile_Cwise_boolean_or-e233a549dd7cef88cba3.json","target-compile_Cwise_boolean_xor-c46334ef78212ca17132.json","target-compile_Cwise_ceil-ec8056ff2c0effc97ee1.json","target-compile_Cwise_cos-0f6dc6c3c5d8cf212ee7.json","target-compile_Cwise_cosh-128c1fb2e10fc6356d70.json","target-compile_Cwise_cube-84d469e475fd93b91909.json","target-compile_Cwise_equal_equal-449397929d8eb146cba7.json","target-compile_Cwise_exp-bb4d18d79317fb2ead85.json","target-compile_Cwise_floor-37fe615fa3320d0d2354.json","target-compile_Cwise_greater-5cd67d2e61d4fac27f6c.json","target-compile_Cwise_greater_equal-f7e6a4da991544055bf5.json","target-compile_Cwise_inverse-3c6f98b78b6736a9ccf3.json","target-compile_Cwise_isFinite-05b44b03f86e3661a8b3.json","target-compile_Cwise_isInf-8b4ffd4d42b08ba7f4e1.json","target-compile_Cwise_isNaN-d6d2d7622342236b8119.json","target-compile_Cwise_less-9a1c0150f4bf59c5dd6f.json","target-compile_Cwise_less_equal-f9015f533cc0c5776133.json","target-compile_Cwise_log-4e1f59cc0b054f515027.json","target-compile_Cwise_log10-f630a20d9cc8f6e3066c.json","target-compile_Cwise_max-aa7503563705e36732dc.json","target-compile_Cwise_min-fde8da92ecc9849ca030.json","target-compile_Cwise_minus-3f62cac7dbbc356f95c9.json","target-compile_Cwise_minus_equal-3d981608c532c5f798e0.json","target-compile_Cwise_not_equal-d2353e8bda21afe6a84c.json","target-compile_Cwise_plus-dcb32ae7de35b769203d.json","target-compile_Cwise_plus_equal-9097b9399052c1ac9b25.json","target-compile_Cwise_pow-8524eddca28de299cb4a.json","target-compile_Cwise_product-515285b3c9899ca06f93.json","target-compile_Cwise_quotient-25358fcb58092c38007e.json","target-compile_Cwise_round-ee9d364ad25631aab0ad.json","target-compile_Cwise_scalar_power_array-dcad88af540a83144a01.json","target-compile_Cwise_sign-0d4679a7be1acbeefa91.json","target-compile_Cwise_sin-2dcb210a2653e6dbda43.json","target-compile_Cwise_sinh-cd0c3bd4a17f1fee3dfb.json","target-compile_Cwise_slash_equal-363c67e0bff852367eb3.json","target-compile_Cwise_sqrt-3c5bd9840f68123ec7b7.json","target-compile_Cwise_square-82ce5a750405d8a337ea.json","target-compile_Cwise_tan-851ed7afdfa7329160fc.json","target-compile_Cwise_tanh-b692de9eb99a86131e46.json","target-compile_Cwise_times_equal-58145b40146fc007c519.json","target-compile_DenseBase_LinSpaced-f4e4fb4ddce5c24295bb.json","target-compile_DenseBase_LinSpacedInt-5d1259fcd3e67b7a8d34.json","target-compile_DenseBase_LinSpaced_seq-34b57d9f7e06ff9284c4.json","target-compile_DenseBase_setLinSpaced-75db6561a6cedb7dc8d6.json","target-compile_DirectionWise_hnormalized-fea0b994cc6b3b66d275.json","target-compile_DirectionWise_replicate-a1bf27a0ee41a3c5a05f.json","target-compile_DirectionWise_replicate_int-e065aab747f3c38345cc.json","target-compile_EigenSolver_EigenSolver_MatrixType-e499de953513368ef467.json","target-compile_EigenSolver_compute-c6b68f7852fdb8edb286.json","target-compile_EigenSolver_eigenvalues-709e69908691595c32e8.json","target-compile_EigenSolver_eigenvectors-726a04bea0df3ee9392c.json","target-compile_EigenSolver_pseudoEigenvectors-b14c3c94ed9de04cdf8f.json","target-compile_FullPivHouseholderQR_solve-2a606034c5efd101e814.json","target-compile_FullPivLU_image-5640eaa58691c0619aaf.json","target-compile_FullPivLU_kernel-3d5f33cf71860211700a.json","target-compile_FullPivLU_solve-7f423b5f3e2dfaa23327.json","target-compile_GeneralizedEigenSolver-63385d024f13f5483997.json","target-compile_HessenbergDecomposition_compute-55929e51977fd2ae75d9.json","target-compile_HessenbergDecomposition_matrixH-55bd0a5b094e514ae05b.json","target-compile_HessenbergDecomposition_packedMatrix-5bfc3ff5fccf021fda1c.json","target-compile_HouseholderQR_householderQ-cae275e46a29e33ed4dd.json","target-compile_HouseholderQR_solve-de5ec1bf0e2f2dac19d3.json","target-compile_HouseholderSequence_HouseholderSequence-ccf4086e25d8ec694a17.json","target-compile_IOFormat-55f7297ea2f0c4d65408.json","target-compile_JacobiSVD_basic-5644f3c367ff5531a2ce.json","target-compile_Jacobi_makeGivens-873cbed757adaa8d9f68.json","target-compile_Jacobi_makeJacobi-6e8d6074bbead25487c6.json","target-compile_LLT_example-ebec4afa36f286b9d047.json","target-compile_LLT_solve-62823b43c34e904c8abf.json","target-compile_LeastSquaresNormalEquations-e07f121fc98454e1b32f.json","target-compile_LeastSquaresQR-1f54b74dbaff48c49640.json","target-compile_Map_general_stride-7f3e375a509b6166257d.json","target-compile_Map_inner_stride-fd6c457d04255f2f8a1d.json","target-compile_Map_outer_stride-844ce3a58019877ae617.json","target-compile_Map_placement_new-7b9346b6fc81583b9bff.json","target-compile_Map_simple-4a493ae45755db77cbae.json","target-compile_MatrixBase_adjoint-1a7c8cfe90fbd1ac6b5b.json","target-compile_MatrixBase_all-7a3fe758908d5afbb73a.json","target-compile_MatrixBase_applyOnTheLeft-e2f9983a5e0e67c8601f.json","target-compile_MatrixBase_applyOnTheRight-817c82a5b8c0e4c81b8e.json","target-compile_MatrixBase_array-8f1b56ed30ec567864c2.json","target-compile_MatrixBase_array_const-4b07b685d428a379e018.json","target-compile_MatrixBase_asDiagonal-a4d44a109b380ade80e1.json","target-compile_MatrixBase_block_int_int-2312f8f6c69317ab53fd.json","target-compile_MatrixBase_block_int_int_int_int-7b70d60c9442c16d2d7b.json","target-compile_MatrixBase_bottomLeftCorner_int_int-b4cbd18ea5bfb13bedc7.json","target-compile_MatrixBase_bottomRightCorner_int_int-a6d9aa7234285e2445be.json","target-compile_MatrixBase_bottomRows_int-fa6a3bed8de2b79de0bd.json","target-compile_MatrixBase_cast-7bafeb351d71ec9a2615.json","target-compile_MatrixBase_col-d9d15ac04e8117d0ab0c.json","target-compile_MatrixBase_colwise-299dd5470ae329fede5c.json","target-compile_MatrixBase_computeInverseAndDetWithCheck-a7e877eb7edef98006e7.json","target-compile_MatrixBase_computeInverseWithCheck-89500b458ca3e258f156.json","target-compile_MatrixBase_cwiseAbs-068b2a43ed006750aab3.json","target-compile_MatrixBase_cwiseAbs2-8f1597ac699509a7ddd9.json","target-compile_MatrixBase_cwiseEqual-75e8b7deb72f443f2b3b.json","target-compile_MatrixBase_cwiseInverse-b810eed10f92fb2fe809.json","target-compile_MatrixBase_cwiseMax-40f1fe5e8c3972054a02.json","target-compile_MatrixBase_cwiseMin-8ddb9dfc8adfb629c2f9.json","target-compile_MatrixBase_cwiseNotEqual-29034ea0e230cd16047b.json","target-compile_MatrixBase_cwiseProduct-4107e968565c1cf08589.json","target-compile_MatrixBase_cwiseQuotient-58d255d1543f0fd59256.json","target-compile_MatrixBase_cwiseSign-5e5b1475e9386beca5e0.json","target-compile_MatrixBase_cwiseSqrt-d909e8da0353a50bf2a3.json","target-compile_MatrixBase_diagonal-8fb879a621694b4d32ca.json","target-compile_MatrixBase_diagonal_int-c87c09a71c893c896b50.json","target-compile_MatrixBase_diagonal_template_int-582732ef2522d4c9f505.json","target-compile_MatrixBase_eigenvalues-37c33f92c812e35782a8.json","target-compile_MatrixBase_end_int-510c7ddfa281a71e6d38.json","target-compile_MatrixBase_eval-1b4ab34d77be76a8ca8d.json","target-compile_MatrixBase_fixedBlock_int_int-9085af100b94b381f249.json","target-compile_MatrixBase_hnormalized-61d7c2d832265b74f14f.json","target-compile_MatrixBase_homogeneous-92a4cf7bd8016231d2d8.json","target-compile_MatrixBase_identity-c147a2cdeedbdfd9b50e.json","target-compile_MatrixBase_identity_int_int-e908f099c40b65eda4b3.json","target-compile_MatrixBase_inverse-77b0d144fcff46a3f0e7.json","target-compile_MatrixBase_isDiagonal-aa2751cd9c1bcb32fa94.json","target-compile_MatrixBase_isIdentity-ead6d29d05fdd092f954.json","target-compile_MatrixBase_isOnes-6a2d085409aaca1d6bc4.json","target-compile_MatrixBase_isOrthogonal-68e2dd1ca11bae677b0f.json","target-compile_MatrixBase_isUnitary-2ae37ec7b2c611b9cbfe.json","target-compile_MatrixBase_isZero-a14275f93333326ba300.json","target-compile_MatrixBase_leftCols_int-b019c8968ab12e18be93.json","target-compile_MatrixBase_noalias-fee3cca311c4bf40484e.json","target-compile_MatrixBase_ones-50f52b1f0189ae9319d9.json","target-compile_MatrixBase_ones_int-54ea3c2d00a272bf5947.json","target-compile_MatrixBase_ones_int_int-18ec750e11837606d1e6.json","target-compile_MatrixBase_operatorNorm-28ed297bc3f9fb8717a9.json","target-compile_MatrixBase_prod-ea21dbe54afb2cb1200a.json","target-compile_MatrixBase_random-acebbc35b378725eb73d.json","target-compile_MatrixBase_random_int-19fab042723390a0f811.json","target-compile_MatrixBase_random_int_int-a2e96083323fc3fcf11b.json","target-compile_MatrixBase_replicate-23a5c2dae3925d4758e3.json","target-compile_MatrixBase_replicate_int_int-a537fcb68bdac027cfe0.json","target-compile_MatrixBase_reverse-11c2bb22e1fcc425a63e.json","target-compile_MatrixBase_rightCols_int-20c412e7deb91f12db01.json","target-compile_MatrixBase_row-16a2b900d248c0a1a944.json","target-compile_MatrixBase_rowwise-b6a80484bfd38197bf69.json","target-compile_MatrixBase_segment_int_int-0e02bef8e8fe2babdd6e.json","target-compile_MatrixBase_select-65c4e81bf3ef7fe80649.json","target-compile_MatrixBase_selfadjointView-aeedff3142f321f3ee54.json","target-compile_MatrixBase_set-a812724f7a3213e14a16.json","target-compile_MatrixBase_setIdentity-34df6918379725fb401a.json","target-compile_MatrixBase_setOnes-418e9412f0f69cf81622.json","target-compile_MatrixBase_setRandom-3bf549ec9e1b2595e374.json","target-compile_MatrixBase_setZero-cf62f2cf5dfc29f915eb.json","target-compile_MatrixBase_start_int-dcd808ce14ea353c3d18.json","target-compile_MatrixBase_template_int_bottomRows-8744c1aa7c8d3cb1bd3b.json","target-compile_MatrixBase_template_int_end-45d7776415db3927cce0.json","target-compile_MatrixBase_template_int_int_block_int_int_int_int-4d1788bc2891a5f87e0f.json","target-compile_MatrixBase_template_int_int_bottomLeftCorner-0091af06a3ff755509ab.json","target-compile_MatrixBase_template_int_int_bottomLeftCorner_int_int-74717446854727970e42.json","target-compile_MatrixBase_template_int_int_bottomRightCorner-9567b6d7a248483fe74e.json","target-compile_MatrixBase_template_int_int_bottomRightCorner_int_int-0a77b8e328b7f622b64e.json","target-compile_MatrixBase_template_int_int_topLeftCorner-b664ea6258aadb124abf.json","target-compile_MatrixBase_template_int_int_topLeftCorner_int_int-663f4a1ae31ca5ac5af4.json","target-compile_MatrixBase_template_int_int_topRightCorner-6a7eaf543f111c5e11ab.json","target-compile_MatrixBase_template_int_int_topRightCorner_int_int-0783c0b8b6c43374c49d.json","target-compile_MatrixBase_template_int_leftCols-3e6be6d55e5b9936f0e7.json","target-compile_MatrixBase_template_int_rightCols-9af54bb94096a3f9f898.json","target-compile_MatrixBase_template_int_segment-8c4974bae02b94881a22.json","target-compile_MatrixBase_template_int_start-c113c76efbc8dc203e91.json","target-compile_MatrixBase_template_int_topRows-f032fb4bb766613606ae.json","target-compile_MatrixBase_topLeftCorner_int_int-35f8390340dcb93ae366.json","target-compile_MatrixBase_topRightCorner_int_int-41f93cd399af78e27b79.json","target-compile_MatrixBase_topRows_int-11fde3063c29b6cb479d.json","target-compile_MatrixBase_transpose-a35ab44f68e4992ea7a0.json","target-compile_MatrixBase_triangularView-f1f045fe3f91b77c0e2d.json","target-compile_MatrixBase_zero-81571a82dc3d323789ba.json","target-compile_MatrixBase_zero_int-11f0f50d0952a7a8f0da.json","target-compile_MatrixBase_zero_int_int-38a356ae0fa11754f0b9.json","target-compile_Matrix_Map_stride-dea707f07dcb1af408fe.json","target-compile_Matrix_resize_NoChange_int-28d11a8fd89af40f619f.json","target-compile_Matrix_resize_int-4dd220d4da3e83d2d8fd.json","target-compile_Matrix_resize_int_NoChange-cdfb4fed36c89b10d1ad.json","target-compile_Matrix_resize_int_int-8f744b5ff869c81995d1.json","target-compile_Matrix_setConstant_int-9192a7a96bd3512641e5.json","target-compile_Matrix_setConstant_int_int-d3b0d33ae3ddf897c520.json","target-compile_Matrix_setIdentity_int_int-d3d590ec0f0d0759c4a9.json","target-compile_Matrix_setOnes_int-c92eaef42347f7506f6b.json","target-compile_Matrix_setOnes_int_int-2c65e28de10929bd4faa.json","target-compile_Matrix_setRandom_int-df2a38f326fef5c67f03.json","target-compile_Matrix_setRandom_int_int-a1c7c815ff56ae9e9045.json","target-compile_Matrix_setZero_int-c053281385fc883a8b99.json","target-compile_Matrix_setZero_int_int-4c7d2d76872b3ff4b3b2.json","target-compile_PartialPivLU_solve-6a3d6cd68f0b312577da.json","target-compile_PartialRedux_count-d42cf9af9fa0443cc755.json","target-compile_PartialRedux_maxCoeff-779558643b6813399572.json","target-compile_PartialRedux_minCoeff-ba2bab9f9cfc2001eece.json","target-compile_PartialRedux_norm-bc7059a436aab3857392.json","target-compile_PartialRedux_prod-9fbe7711cc40902bcff0.json","target-compile_PartialRedux_squaredNorm-5eb752c2f5459799f84e.json","target-compile_PartialRedux_sum-c00d5fe7693e80ab2866.json","target-compile_RealQZ_compute-9228447660b00f74be4b.json","target-compile_RealSchur_RealSchur_MatrixType-3cf44a05a6bee4071828.json","target-compile_RealSchur_compute-b40211ee377fb5d703d3.json","target-compile_SelfAdjointEigenSolver_SelfAdjointEigenSolver-c1ee8d49f5928101245f.json","target-compile_SelfAdjointEigenSolver_SelfAdjointEigenSolver_MatrixType-ffc730e400bdfff2d22d.json","target-compile_SelfAdjointEigenSolver_SelfAdjointEigenSolver_MatrixType2-b9f5525881db65a90299.json","target-compile_SelfAdjointEigenSolver_compute_MatrixType-ab230dbcedffe55485dc.json","target-compile_SelfAdjointEigenSolver_compute_MatrixType2-262266b8fb9289414b6f.json","target-compile_SelfAdjointEigenSolver_eigenvalues-82e1f25aac73ef5edca2.json","target-compile_SelfAdjointEigenSolver_eigenvectors-6f9bf9a39a48570fe55d.json","target-compile_SelfAdjointEigenSolver_operatorInverseSqrt-f59c25d99e61ee26711d.json","target-compile_SelfAdjointEigenSolver_operatorSqrt-1d6d88f59139cbdad575.json","target-compile_SelfAdjointView_eigenvalues-b94bc4c4dad63a069f66.json","target-compile_SelfAdjointView_operatorNorm-edae6b3c2f5f8d7c302b.json","target-compile_SparseMatrix_coeffs-31c29b961f1e501965f5.json","target-compile_TopicAliasing_block-22df1a86fbcfed896252.json","target-compile_TopicAliasing_block_correct-c4e9f78fb4c739c8fb27.json","target-compile_TopicAliasing_cwise-3457e430c45014871d04.json","target-compile_TopicAliasing_mult1-a7a1f79509a73c2fb953.json","target-compile_TopicAliasing_mult2-5b48c7c95ab7c76088ba.json","target-compile_TopicAliasing_mult3-589f3ebfaba4004f23af.json","target-compile_TopicAliasing_mult4-5c4757bd0fc95f72f1b0.json","target-compile_TopicAliasing_mult5-14f8c620805a9ea1a7f4.json","target-compile_TopicStorageOrders_example-86314f4260bccd016fb2.json","target-compile_Triangular_solve-f84d03ba2202419f21a8.json","target-compile_Tridiagonalization_Tridiagonalization_MatrixType-fe825392abdedcee0b7d.json","target-compile_Tridiagonalization_compute-af2f8ccd06333e565f1a.json","target-compile_Tridiagonalization_decomposeInPlace-f5c5cf231c4ae85c6b8a.json","target-compile_Tridiagonalization_diagonal-93c7a9402ad6dac39ec6.json","target-compile_Tridiagonalization_householderCoefficients-e7d785dd426584ef382f.json","target-compile_Tridiagonalization_packedMatrix-fb4f6bfd220445b03d99.json","target-compile_Tutorial_AdvancedInitialization_Block-5f1d9202cf6d7e115ae7.json","target-compile_Tutorial_AdvancedInitialization_CommaTemporary-c3ef23c05b0fc5ade26e.json","target-compile_Tutorial_AdvancedInitialization_Join-0ce627fc7ba0be2c76ad.json","target-compile_Tutorial_AdvancedInitialization_LinSpaced-1352b4df89d21774e273.json","target-compile_Tutorial_AdvancedInitialization_ThreeWays-60676c4d02ebca6b65d7.json","target-compile_Tutorial_AdvancedInitialization_Zero-58dbbae0bdcc22050f72.json","target-compile_Tutorial_Map_rowmajor-ec9473d2cc9cba2958ac.json","target-compile_Tutorial_Map_using-4b34a79903c68e20e582.json","target-compile_Tutorial_ReshapeMat2Mat-4da9bfc5e5ec28ce2292.json","target-compile_Tutorial_ReshapeMat2Vec-c92a4c220de6e77bfacf.json","target-compile_Tutorial_SlicingCol-9266b34c6968065e80b0.json","target-compile_Tutorial_SlicingVec-3031709133c5d69cdb8b.json","target-compile_Tutorial_commainit_01-727c9c2cc950e05e7ce6.json","target-compile_Tutorial_commainit_01b-9fb0f6176c3c7425927b.json","target-compile_Tutorial_commainit_02-fcaf58d3ebc1ebf371f9.json","target-compile_Tutorial_solve_matrix_inverse-b3c6e9a516a1968841eb.json","target-compile_Tutorial_solve_multiple_rhs-6b96b5a078199b3371f1.json","target-compile_Tutorial_solve_reuse_decomposition-c8084fd53477d37dc82b.json","target-compile_Tutorial_solve_singular-a6a6c0f1d1a468aa92c5.json","target-compile_Tutorial_solve_triangular-6ff40293cb095792ed7a.json","target-compile_Tutorial_solve_triangular_inplace-0eebc03784f545ad025c.json","target-compile_VectorwiseOp_homogeneous-b0a461c54a974f8c7abd.json","target-compile_Vectorwise_reverse-2bedf42555290d1858a1.json","target-compile_class_FullPivLU-92e5a31e0a9f862438d3.json","target-compile_tut_arithmetic_redux_minmax-c5da6e3fea1b58b5caad.json","target-compile_tut_arithmetic_transpose_aliasing-4e89930c1722006e3b21.json","target-compile_tut_arithmetic_transpose_conjugate-33b8c189402a635a5c68.json","target-compile_tut_arithmetic_transpose_inplace-cb9bf16a9b70b5aec9c0.json","target-compile_tut_matrix_assignment_resizing-118d5b347d59da31bab3.json","target-demos-ac554539b638fe4443eb.json","target-doc-6d2eb329d9e2e8f325f5.json","target-doc-eigen-prerequisites-d659d42b15b6eb8da4ad.json","target-doc-unsupported-prerequisites-8bc43a55fa56018ffd7a.json","target-eigen_blas-7789f677d2cef062274f.json","target-eigen_blas_static-bc7d3290e59805fb0182.json","target-eigen_lapack-a06128b672715ea7442a.json","target-eigen_lapack_static-963abea373a54df03760.json","target-example_BVH_Example-21bc3a5fbc4310d08d8c.json","target-example_EulerAngles-a5a6bb6b03bdb51a89af.json","target-example_FFT-4a16aea1474e845372d5.json","target-example_MatrixExponential-449d646d4458393c4f81.json","target-example_MatrixFunction-9e01f776e5cfb0bbf526.json","target-example_MatrixLogarithm-1879e006388fbf3e4694.json","target-example_MatrixPower-fca1debf2ef67791211e.json","target-example_MatrixPower_optimal-9cd9de140df21034545b.json","target-example_MatrixSine-24273e6e6c67be08c807.json","target-example_MatrixSinh-0db560ea0644ef6df57f.json","target-example_MatrixSquareRoot-c53a5e6be50c95840384.json","target-example_PolynomialSolver1-f770bd74c517932bce44.json","target-example_PolynomialUtils1-0501ab6a166ae1f58589.json","target-function_taking_eigenbase-7351af37ce72b30752b4.json","target-function_taking_ref-254a891bd9ac584e5989.json","target-lapack-5af0f71581b72e341ea7.json","target-make_circulant-0040e7974a5787ab9a9a.json","target-make_circulant2-d1116a6f2ea61cccdb71.json","target-matrixfree_cg-61baa377e51a26480def.json","target-nullary_indexing-f3bbfa98d459a5023a71.json","target-random_cpp11-c231d2b5319aea6ceda9.json","target-spbenchsolver-aa58c6b33c79b92fc339.json","target-spsolver-59c300e8da2de43fb0b1.json","target-test_sparseLU-b6bbbe5c9f030da913d9.json","target-tut_arithmetic_add_sub-7dd5b9387c8864e59ddf.json","target-tut_arithmetic_dot_cross-e517e171e9a1e3946627.json","target-tut_arithmetic_matrix_mul-0a3d741b879b9d1bf80b.json","target-tut_arithmetic_redux_basic-c9850c5ff98c51eccd74.json","target-tut_arithmetic_scalar_mul_div-21d74a5b4b063149e0ec.json","target-tut_matrix_coefficient_accessors-2d10c7a972240105d4e0.json","target-tut_matrix_resize-9d6b585bdb192dabde03.json","target-tut_matrix_resize_fixed_size-9b71d88439d1f3c0aeda.json","target-uninstall-311436923be2bf2f8906.json","target-unsupported_examples-d687b606e9d616ae9937.json","target-unsupported_snippets-cbb77c221b5bb724c1dc.json","toolchains-v1-ec6e94d0d30e763f979b.json"]
[driver] Run _refreshExpansions
[driver] Run _refreshExpansions cb
[cache] Reading CMake cache file /home/clement/build/default/test/CMakeCache.txt
[cache] Parsing CMake cache string
[cpptools] Unknown C standard control flag: -std=c++03
[build] Build finished with exit code 0
[extension] [4195] cmake.build finished (returned 0)

I don't see where you're including main.cpp in a target in your CMakeLists.txt.  Did you just share a snippet, or is that the whole thing?  It is also suspicious that the extension does not think there is a build type set.  I thought presets version 2 required setting CMAKE_BUILD_TYPE, but I'd need to go back and look at the code to see what we do in that case.

Hi, thank you for your answer. It is just a snippet. I work on a large project.
Actually, the issue was somewhere else. After weeks having this issue, it is working today.
Today, the "C/C++" extension has been upgraded from v1.7.0 to v1.7.1 on my build server and it fixed the issue. It seems that I was affected by the issue https://github.com/microsoft/vscode-cpptools/issues/8276

Sorry for the inconvenience. I'm glad to hear that it's working for you now.


[Navigator] How to pass props when using Navigator?

I used to have an app built on NavigatorIOS, and I use passProps to communicate for parent-children communication.
I am now switching to Navigator but it seems that passProps is no longer effective. What's the good pattern to pass properties in Navigator?
Many thanks for your help.

You can use renderScene of navigator which gives you access to the route and navigator objects.
Then when you want to push a new scene you can pass the properties and have them accessible inside the route object.
Example of the renderScene function:
renderScene(route, navigator) {
  switch (route.id) {
    case 'home':
    return <Home navigator={navigator} data={route.data} />;
  }
}

Example of the pushing a new scene:
this.props.navigator.push({
  id: 'home',
  data: Object
})

Thank you so much for looking @christopherdro!

@mkonicek No Problem! :)
@macelii Going to close this issue out for now since this questions seems more appropriate for Stack Overflow. Feel free to post your question there or join us on Discord if you'd like some more help.
Hope you get it figured out! :)

Thanks @christopherdro , this help many

If you want to pass a bunch of props, you can do this:
    this.props.navigator.push({
      id: viewId,
      props: {
        someProp: this.props.someProp
      }
    });

and in your navigator's parent:
renderScene(route, navigator) {
  switch (route.id) {
    case 'home':
    return <Home navigator={navigator} {... route.props} />;
  }
}

@coconup, and we only need to remember that: Home will copy all route.props as its own props.
So , to use those route.props within Home, e.g someProp, just access via this.props.someProp.

I alway fount issue in redirection "Cannot read property 'push' of undefined". what is making wrong ?
import React, { Component } from 'react';
import {
AppRegistry,
StyleSheet,Navigator,
Text,TouchableOpacity,
View
} from 'react-native';
export default class Main extends Component {
changepage(a){
alert("Page name: "+a);
this.props.navigator.push({
id: a,
})
}
render() {
return (

   <TouchableOpacity >
		<Text style={styles.welcome}  onPress={this.changepage('Test')}>
		Login please
	 </Text>
	 </TouchableOpacity>

    <Text style={styles.instructions}>
      To get started, edit index.ios.js
    </Text>

  </View>
);

}
renderScene(route, navigator) {
switch (route.id) {
case 'Test':
return ;
}
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
justifyContent: 'center',
alignItems: 'center',
backgroundColor: '#F5FCFF',
},
instructions: {
textAlign: 'center',
color: '#333333',
marginBottom: 5,
},
});
AppRegistry.registerComponent('Main', () => Main);

really awesome! christopherdro. your advice helped me a lot

@christopherdro! I am trying your suggestion. But renderScene never gets called in my case. Any idea what I might be missing ?


Why is youtube blocked by default?

It seems to work fine on my end, just wondering

youtube take much off my time :). It is configurable..you can go to the setting for browser-plus and specify which web site need to blocked..by default I have it as youtube I think.again there is a browser-plus-block sample plugin..if you wanted to make it more elobrate (maintain time between which you needed to block kind of stuff and keywords etc) and release a plugin


Fix processing of copyrights along with its performance issues

Previously, CopyrightStatements.process() was called once per license finding file location by the LicenseInfoResolver.
This does not make sense and leads to poor performance as the process() function is not super fast (but fast enough if not called only reasonably often). Once more, the license API was designed to hold the pre-processed copyright statements. This does not make any sense because the processing is different depending on the use case.
Do the processing properly, thereby reduce the number of calls to process() tremendously and change the design such that copyright statements are always processed on-the-fly. This fixes #3511.

@fviernau is this indeed still a draft PR, or ready for review by now?

@fviernau is this indeed still a draft PR, or ready for review by now?

Thanks for the hint @sschuberth! I've removed the draft state.


[v3.0.1] Prefer https links where available

This updates links to apache.org (including in examples), iana.org, ietf.org and semver.org to https for security and consistency. It leaves http links to json-schema.org, yaml.org and commonmark.org as they either don't provide https or Firefox 57 complains about their https setup.
(ping @handrews)

Sigh.  GitHub pages won't allow HTTPS with custom domains (you can do one or the other but not both).  And we don't actually own the DNS account, although one of the former JSON Schema editors has a way to pay for it (how that works I do not know).  We really need to find some way to claim that account or give up and get a new domain name and host it somewhere that will support HTTPS :-/

Sigh.

:( as long as you're aware.

Oh, we are so very aware.  It's the same reason why there's a json-schema/json-schema GitHub account still lying around.  Someone files a bug on all this at least once or twice a year.


Escape chat message to prevent the HTML entities converted/decoded

Details

We are decoding the text from user chat, so we should always escape the chat that user sends.
Fixed Issues

$ https://github.com/Expensify/App/issues/15508
PROPOSAL: https://github.com/Expensify/App/issues/15508#issuecomment-1453054412
Tests

Same as QA Steps

[x] Verify that no errors appear in the JS console

Offline tests

Same as QA Steps
QA Steps

Open any chat
Send & as a message
Verify the text sent shows & and not &

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://user-images.githubusercontent.com/50919443/225225187-d32d30a9-3ca5-4078-8af9-59d0419dca10.mov

Mobile Web - Chrome

https://user-images.githubusercontent.com/50919443/225225227-61080e9b-d3fd-4a5a-8661-43a1ba6423e6.mp4

Mobile Web - Safari

https://user-images.githubusercontent.com/50919443/225225321-394b1f35-189f-4541-8290-0641da69d876.mov

Desktop

https://user-images.githubusercontent.com/50919443/225225332-0005c511-4b00-45ac-b04e-fb5082b63ccb.mov

iOS

https://user-images.githubusercontent.com/50919443/225225344-ef8081a0-5ed1-473c-b30d-f7d9b8845057.mov

Android

https://user-images.githubusercontent.com/50919443/225225368-f8c1f71f-2b49-4a25-875c-9ae9202aa809.mp4

@yuwenmemon @s77rt One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Reviewer Checklist

[X] I have verified the author checklist is complete (all boxes are checked off).
[X] I verified the correct issue is linked in the ### Fixed Issues section above
[X] I verified testing steps are clear and they cover the changes made in this PR

[X] I verified the steps for local testing are in the Tests section
[X] I verified the steps for Staging and/or Production testing are in the QA steps section
[X] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[X] I checked that screenshots or videos are included for tests on all platforms
[X] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[X] Android / native
[X] Android / Chrome
[ ] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[X] I verified proper code patterns were followed (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I verified that this PR follows the guidelines as stated in the Review Guidelines
[X] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://user-images.githubusercontent.com/16493223/226902972-89cac3ec-19f5-48de-89f8-1bc97439be4c.mp4

Mobile Web - Chrome
https://user-images.githubusercontent.com/16493223/226902926-232591d9-416e-404b-a352-7f213318f037.mp4

Mobile Web - Safari
https://user-images.githubusercontent.com/16493223/226902902-c55068f2-4eee-4b3f-bdd2-ae3642a5a5d3.mp4

Desktop
https://user-images.githubusercontent.com/16493223/226902848-57f4cc68-c2ca-4043-87b4-4eb916a39790.mp4

iOS
I'm having problems building iOS App on main.

Android
https://user-images.githubusercontent.com/16493223/226902704-07f5f515-5d27-452f-8c2d-216a09c03f48.mp4

Overall looks good. I still need to test on iOS as I'm having problems building the App on iOS. Asked on Slack. @bernhardoj Can you confirm if you can build the iOS App on main? If so the problem may be just from my side and we should proceed.

I will try it when I back home.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/luacmartins in version: 1.2.89-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Rancher 2.4 Scaling Targets

Rancher aims to hit 2,000 clusters and 100,000 nodes under management.
Based on Kubernetes published limits a single cluster can have 5000 nodes. If we were to run maxed out nodes, we could have (20) clusters with our 100,000 node target. At the opposite end of the spectrum, we would like to achieve a maximum configuration from a cluster stand point we could have 10,000 clusters with 50 nodes each.
We need to determine in these tests, where etcd tips over. Once determined, we need to prove we can exceed these limits with k3s against alternate backends.
Test cases:
Hit a maximum of 10,000 single node clusters. (maximum of 10,000 clusters)
Attach 400 clusters with 250 nodes per cluster. (100,000 nodes)
Attach 20 clusters each with 5,000 nodes per cluster. (Maximum sized k8s clusters)
Hit a maximum of 2,000 clusters with 50 nodes in each cluster. (max clusters with max nodes)
Attach 1,000 clusters each with 100 nodes per cluster. (Mid point test)
Constraints:
This will be a test of Rancher in HA mode. A single Rancher server node Should not need more than 32vCPUs and 128GB of Ram.
For each of these tests:
Clusters will be imported.
All Rancher agents need to be deployed, operational and in a green state from the UI, and maintain status.
Rancher management pods need to be able to go down to scale 0, and back up to the number of nodes.
Rancher management pods need to be upgraded from one version to the next.
Rancher should be able to deploy a multi-cluster app to all clusters.
Rancher needs to be able to support 100 concurrent cluster provisions.
API SLOs / SLAs:
Any single object DELETE,POST,GET,PUT response should return in <200ms, in cases of large objects TTFB can be used.
Any list API call <5s
UI Load should <10s
Deliverables:

Enable Rancher server level prometheus metrics for increased visibility in the the Rancher controllers. This can be based on work of one of our community members: https://github.com/rancher/rancher/pull/21351

This should produce a Grafana dashboard for monitoring Rancher servers with Rancher metrics if deployed into the local cluster.

UI Should introduce a concept of tagging/grouping to accommodate management of nodes and clusters.

This issue will likely spawn additional issues to address bottlenecks.

On restart at 2k clusters rancher should:

Connect to all downstream clusters within 1min - The UI should be usable in the downstream cluster with the expectation that side affects of the controllers running won't happen until they are running for that cluster
Within 5 min all downstream clusters controllers are running and CPU load on the rancher host/s have settled into an idle state.

Please refer to https://rancher.com/docs/rancher/v2.x/en/installation/requirements/#hardware-requirements for the latest sizing guide based on number of nodes and clusters that you want to manage.


[YouTube] Support @owner format in uploader_id etc

Boilerplate: own code, bug fix
## Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
According to #31530, YouTube has changed its metadata so that the owner URL has the format .../@ownerslug rather than .../user/user_id or .../channel/channel_id. Some, if not all, music videos retain the previous scheme.
This caused several problems:

Owing to an extraction bug, failing to match the previous patterns crashed the extractor.
After resolving the crash, various metadata items were not being extracted, and some study was needed to work out what values should be extracted.
The resolution of this meant that many tests failed.

Proposed final resolution from linked post:

uploader is the author text value
channel is the same
uploader_id becomes the @... value
channel_id is channelId
uploader_url is the author URL with<EMAIL_ADDRESS>channel_url is /channel/{channel_id} at least while that is valid.

The linked post identifies that these metadata items may be available in various parts of the YT webpage, with slightly different access paths depending on the page type.
Thus, this PR

updates the YouTube extractor to handle the new format
returns values as proposed in https://github.com/ytdl-org/youtube-dl/issues/31530#issuecomment-1435734719
updates the tests affected by the changes
to support one of the tests, solves a long-standing issue in the download test that prevented testing cases where the id changed.

Closes #31568
Resolves #31530

These tests pass locally but not in CI:
2023-02-24T03:41:39.4591969Z ======================================================================
2023-02-24T03:41:39.4592162Z FAIL: test_YoutubePlaylist_2 (test.test_download.TestDownload):
2023-02-24T03:41:39.4592438Z ----------------------------------------------------------------------
2023-02-24T03:41:39.4592564Z Traceback (most recent call last):
2023-02-24T03:41:39.4592944Z   File "/home/runner/work/youtube-dl/youtube-dl/test/test_download.py", line 192, in test_template
2023-02-24T03:41:39.4593104Z     len(res_dict['entries'])))
2023-02-24T03:41:39.4593493Z   File "/home/runner/work/youtube-dl/youtube-dl/test/helper.py", line 266, in assertGreaterEqual
2023-02-24T03:41:39.4593638Z     self.assertTrue(got >= expected, msg)
2023-02-24T03:41:39.4593974Z AssertionError: Expected at least 1 in playlist https://www.youtube.com/embed/videoseries?list=PL6IaIsEjSbf96XFRuNccS_RuEXwNdsoEu, but got only 0
2023-02-24T03:41:39.4594254Z -------------------- >> begin captured stdout << ---------------------
2023-02-24T03:41:39.4594455Z [youtube:tab] PL6IaIsEjSbf96XFRuNccS_RuEXwNdsoEu: Downloading webpage
2023-02-24T03:41:39.4594594Z [download] Downloading playlist: JODA15
2023-02-24T03:41:39.4594749Z [youtube:tab] playlist JODA15: Downloading 0 videos
2023-02-24T03:41:39.4594907Z [download] Finished downloading playlist: JODA15
2023-02-24T03:41:39.4594916Z
2023-02-24T03:41:39.4595193Z --------------------- >> end captured stdout << ----------------------
2023-02-24T03:41:39.4595201Z
2023-02-24T03:41:39.4595314Z ======================================================================
2023-02-24T03:41:39.4595497Z FAIL: test_YoutubeTab_20 (test.test_download.TestDownload):
2023-02-24T03:41:39.4595767Z ----------------------------------------------------------------------
2023-02-24T03:41:39.4596076Z Traceback (most recent call last):
2023-02-24T03:41:39.4596472Z   File "/home/runner/work/youtube-dl/youtube-dl/test/test_download.py", line 192, in test_template
2023-02-24T03:41:39.4596647Z     len(res_dict['entries'])))
2023-02-24T03:41:39.4597023Z   File "/home/runner/work/youtube-dl/youtube-dl/test/helper.py", line 266, in assertGreaterEqual
2023-02-24T03:41:39.4597169Z     self.assertTrue(got >= expected, msg)
2023-02-24T03:41:39.4597425Z AssertionError: Expected at least 350 in playlist https://www.youtube.com/hashtag/cctv9, but got only 339
2023-02-24T03:41:39.4597704Z -------------------- >> begin captured stdout << ---------------------
2023-02-24T03:41:39.4597826Z [youtube:tab] cctv9: Downloading webpage
2023-02-24T03:41:39.4597964Z [download] Downloading playlist: #cctv9
2023-02-24T03:41:39.4598090Z [youtube:tab] Downloading page 1
2023-02-24T03:41:39.4598211Z [youtube:tab] Downloading page 2
2023-02-24T03:41:39.4598333Z [youtube:tab] Downloading page 3
2023-02-24T03:41:39.4598459Z [youtube:tab] Downloading page 4
2023-02-24T03:41:39.4598579Z [youtube:tab] Downloading page 5
2023-02-24T03:41:39.4598720Z [youtube:tab] playlist #cctv9: Downloading 339 videos
2023-02-24T03:41:39.4598850Z [download] Downloading video 1 of 339
2023-02-24T03:41:39.4598979Z [download] Downloading video 2 of 339
...
2023-02-24T03:41:39.4650471Z [download] Downloading video 338 of 339
2023-02-24T03:41:39.4650595Z [download] Downloading video 339 of 339
2023-02-24T03:41:39.4650765Z [download] Finished downloading playlist: #cctv9
2023-02-24T03:41:39.4650935Z
2023-02-24T03:41:39.4651433Z --------------------- >> end captured stdout << ----------------------
2023-02-24T03:41:39.4651442Z
2023-02-24T03:41:39.4651570Z ======================================================================

Presumably there is some regional difference in the availability of the playlist items.

Does this mean I can update youtube-dl using youtube-dl -U and get the fix now?

No. That requires an actual release.

I don't really understand the difference between merging a commit into the master branch, and doing a release. Isn't that the same thing?

Starting from a selected commit, there's preparation (eg changelog), and a build step, and a deployment step to make the built versions available.

On 3/3/23 16:14, dirkf wrote:

Starting from a selected commit, there's preparation (eg changelog), and
a build step, and a deployment step to make the built versions available.

Would you consider posting it to this ticket when that occurs?

@dirkf Could you please please please make a new release now?

Follow #31350.

Thank you @dirkf for the fix ! Everything goes fine now :)

Tried to upgrade with brew the version there is from 2021
Warning: youtube-dl 2021.12.17 already installed

Tried to upgrade with brew the version there is from 2021

Read #31530.

Today this is happening again: (with the last version 2021.12.17)
youtube-dl -F https://www.youtube.com/watch?v=bYsDfGASWV4
[youtube] bYsDfGASWV4: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

idem:
youtube-dl https://www.youtube.com/watch\?v\=yY9lL4Jxkd8 --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['https://www.youtube.com/watch?v=yY9lL4Jxkd8', '--verbose']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: ac0663ae5
[debug] Python version 3.11.3 (CPython) - macOS-13.3.1-arm64-arm-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] yY9lL4Jxkd8: Downloading webpage
WARNING: unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[debug] Default format spec: best/bestvideo+bestaudio
[debug] Invoking downloader on 'https://rr5---sn-oguesndl.googlevideo.com/videoplayback?expire=1681979600&ei=cKRAZJ3YBsKDrQTGq5bwDg&ip=<IP_ADDRESS>&id=o-AAbyL4vJ9FwrvwJ_Xj66ErrhKEQAJnyEL4SH9x4SltSA&itag=22&source=youtube&requiressl=yes&mh=HU&mm=31%2C29&mn=sn-oguesndl%2Csn-oguelnl7&ms=au%2Crdu&mv=m&mvi=5&pl=24&initcwndbps=733750&vprv=1&mime=video%2Fmp4&ns=sta-jV5M0zXOaAT29ONiE7gM&cnr=14&ratebypass=yes&dur=403.284&lmt=1681930934724193&mt=1681957731&fvip=5&fexp=24007246&c=WEB&txp=5318224&n=KvP63n5rHoQuri&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cns%2Ccnr%2Cratebypass%2Cdur%2Clmt&sig=AOq0QJ8wRQIhANfYYAoltP5niJL0ejb7eEyLkJBJ3yp1LMzyrYzuvABgAiA7hfSBvtdUX5j8UuuMWRsIjZShOg-w9vjNuN5a-moSPw%3D%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRAIgWBuzeXhs3MCj0JzexJoeCFtuRFPFbG6Zh0gklb2YA0kCIDxnG-larL5FRW1Gm589jhEdUmN12a7RrbciMWoe1V9q'
[download] Error _ Testing with Foundry-yY9lL4Jxkd8.mp4 has already been downloaded
[download] 100% of 15.53MiB

Hi, Youtube-dl said it is up too date although it is obsolete since February 2012. ( Broken support for YouTube)
pip install --upgrade youtube-dl give
Requirement already satisfied: youtube-dl in /data/data/com.termux/files/usr/lib/python3.11/site-packages (2021.12.17)
Please give me the fix for youtube-dl --no-cache-dir --extract-audio --audio-format mp3 -w -i -o "%(title)s.%(ext)s" https://m.youtube.com/watch?v=JQCD5LBJ1jU --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--no-cache-dir', '--extract-audio', '--audio-format', 'mp3', '-w', '-i', '-o', '%(title)s.%(ext)s', 'https://m.youtube.com/watch?v=JQCD5LBJ1jU', '--verbose']
[debug] Encodings: locale utf-8, fs utf-8, out utf-8, pref utf-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.11.3 (CPython) - Linux-4.19.157-perf+-aarch64-with-libc
[debug] exe versions: ffmpeg 6.0, ffprobe 6.0
[debug] Proxy map: {}
[youtube] JQCD5LBJ1jU: Downloading webpage
[youtube] JQCD5LBJ1jU: Downloading MPD manifest
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
return func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
ie_result = ie.extract(url)
^^^^^^^^^^^^^^^
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 534, in extract
ie_result = self._real_extract(url)
^^^^^^^^^^^^^^^^^^^^^^^
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see https://yt-dl.org/update on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Add a quote, <Ctrl+Shift+.>
Add code, <Ctrl+e>
Add a link, <Ctrl+k>
Directly mention a user or team
Reference an issue, pull request, or discussion
Add saved reply

Checklist

[ x] I'm reporting a broken site support issue
[x ] I've verified that I'm running youtube-dl version 2021.12.17
[x ] I've checked that all provided URLs are alive and playable in a browser
[x ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ x] I've searched the bugtracker for similar bug reports including closed ones
[x ] I've read bugs section in FAQ

Verbose log

youtube-dl --no-cache-dir --extract-audio --audio-format mp3 -w -i -o "%(title)s.%(ext)s" https://m.youtube.com/watch?v=JQCD5LBJ1jU --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--no-cache-dir', '--extract-audio', '--audio-format', 'mp3', '-w', '-i', '-o', '%(title)s.%(ext)s', 'https://m.youtube.com/watch?v=JQCD5LBJ1jU', '--verbose']
[debug] Encodings: locale utf-8, fs utf-8, out utf-8, pref utf-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.11.3 (CPython) - Linux-4.19.157-perf+-aarch64-with-libc
[debug] exe versions: ffmpeg 6.0, ffprobe 6.0
[debug] Proxy map: {}
[youtube] JQCD5LBJ1jU: Downloading webpage
[youtube] JQCD5LBJ1jU: Downloading MPD manifest
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
    ie_result = ie.extract(url)
                ^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 534, in extract
    ie_result = self._real_extract(url)
                ^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
    'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description

Hi
pip install --upgrade --force-reinstall git+https://github.com/ytdl-org/youtube-dl.git
Collecting git+https://github.com/ytdl-org/youtube-dl.git
Give
  Cloning https://github.com/ytdl-org/youtube-dl.git to /data/data/com.termux/files/usr/tmp/pip-req-build-zvolm8k6
  ERROR: Error [Errno 2] No such file or directory: 'git' while executing command git version
ERROR: Cannot find command 'git' - do you have 'git' installed and in your PATH?

pip install --upgrade youtube-dl give
Requirement already satisfied: youtube-dl in /data/data/com.termux/files/usr/lib/python3.11/site-packages (2021.12.17)
YouTube dl doesn't work for 3 mounth and there is zero solution. Zero fix although in this forum it is printed it has been fixed and that there is a 2023's update
Please give me the fix for
youtube-dl --no-cache-dir --extract-audio --audio-format mp3 -w -i -o "%(title)s.%(ext)s" https://m.youtube.com/watch?v=JQCD5LBJ1jU --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--no-cache-dir', '--extract-audio', '--audio-format', 'mp3', '-w', '-i', '-o', '%(title)s.%(ext)s', 'https://m.youtube.com/watch?v=JQCD5LBJ1jU', '--verbose']
[debug] Encodings: locale utf-8, fs utf-8, out utf-8, pref utf-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.11.3 (CPython) - Linux-4.19.157-perf+-aarch64-with-libc
[debug] exe versions: ffmpeg 6.0, ffprobe 6.0
[debug] Proxy map: {}
[youtube] JQCD5LBJ1jU: Downloading webpage
[youtube] JQCD5LBJ1jU: Downloading MPD manifest
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
 File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
   return func(self, *args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/YoutubeDL.py", line 836, in __extract_info
   ie_result = ie.extract(url)
               ^^^^^^^^^^^^^^^
 File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 534, in extract
   ie_result = self._real_extract(url)
               ^^^^^^^^^^^^^^^^^^^^^^^
 File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/youtube.py", line 1794, in _real_extract
   'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 File "/data/data/com.termux/files/usr/lib/python3.11/site-packages/youtube_dl/extractor/common.py", line 1012, in _search_regex
   raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

we could use brew install youtube-dl --HEAD to install latest version

we could use brew install youtube-dl --HEAD to install latest version

The homebrew people seem very unwilling to promote --HEAD, so it isn't recommended in #31530 even though (disclaimer: I don't use homebrew) it would normally be a better solution than the patch they added.

Hello, I am still getting this issue in Ubuntu.
OS : 5.19.0-1024-aws
Already updated:
ubuntu@ip-10-0-54-72:~$ youtube-dl -U
youtube-dl is up-to-date (2021.12.17)