Highlighting fails after switching between monorepo projects (when switching python interpreters)

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?
Basically, I expect the highlighting on the Jupyter notebook to update when I switch from one project to another. However, when I switch from one project to another it fails to update the highlighting until I either reload the window or I restart the extension host. Note that normal python files highlight just fine.
To reproduce this see the following codesandbox
After you've loaded into the codesandbox, open it in vscode. Make sure that you have the following extensions:

pylance
jupyter
python envy (teticio.python-envy)

open "third_project/another_one.ipynb" and select the appropriate .venv which is located at "third_project/.venv". Notice that things are highlighting.

open other_project/init.py
You can also get here by navigating to the definition of the "other_project" module. Notice that python envy changes the interpreter.

Now navigate back to the "third_project/another_one.ipynb". If you're "lucky" you'll see that when you scroll down and then back up (to force re-draw the highlihgts) that sometimes it freezes. When it freezes like this it's frozen indefinitely.

NOTE:

It may be somewhat difficult to reproduce the results, and you may have to go back and forth between notebooks / files quickly in order to overload the system and then force the behavior. However, note that in larger codebases it happens nearly every time you switch between notebooks / project interpreters.
I am using poetry to import from other modules in the monorepo using their relative path importing system

VS Code Version
1.90.0
Jupyter Extension Version
v2024.5.0
Jupyter logs
Visual Studio Code (1.90.0, ssh-remote, desktop)
Jupyter Extension Version: 2024.5.0.
Python Extension Version: 2024.8.0.
Pylance Extension Version: 2024.6.1.
Platform: linux (x64).
Workspace folder /project/workspace, Home = /root
14:55:37.492 [info] Starting Kernel (Python Path: /project/workspace/third_project/.venv/bin/python, Poetry, 3.8.19) for '/project/workspace/third_project/another_one.ipynb' (disableUI=true)
14:55:38.300 [info] Process Execution: /project/workspace/third_project/.venv/bin/python -m pip list
14:55:38.367 [info] Process Execution: /project/workspace/third_project/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
14:55:38.382 [info] Process Execution: /project/workspace/third_project/.venv/bin/python -m ipykernel_launcher --f=/~/.local/share/jupyter/runtime/kernel-v2-18791fQR1MB8Io0Zd.json
    > cwd: //project/workspace/third_project
14:55:40.250 [info] Kernel successfully started
14:55:40.270 [info] Process Execution: /project/workspace/third_project/.venv/bin/python /~/.vscode-server/extensions/ms-toolsai.jupyter-2024.5.0-linux-x64/pythonFiles/printJupyterDataDir.py
14:58:47.202 [info] Starting Kernel (Python Path: /project/workspace/.venv/bin/python, Poetry, 3.8.19) for '/project/workspace/notebook.ipynb' (disableUI=true)
14:58:48.116 [info] Process Execution: /project/workspace/.venv/bin/python -m pip list
14:58:48.189 [info] Process Execution: /project/workspace/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
14:58:48.206 [info] Process Execution: /project/workspace/.venv/bin/python -m ipykernel_launcher --f=/~/.local/share/jupyter/runtime/kernel-v2-18791DaYZEb5bjEdQ.json
    > cwd: //project/workspace
14:58:50.302 [info] Kernel successfully started
14:58:50.317 [info] Process Execution: /project/workspace/.venv/bin/python /~/.vscode-server/extensions/ms-toolsai.jupyter-2024.5.0-linux-x64/pythonFiles/printJupyterDataDir.py
14:58:57.241 [info] Starting Kernel (Python Path: /project/workspace/other_project/.venv/bin/python, Poetry, 3.8.19) for '/project/workspace/other_project/other.ipynb' (disableUI=true)
14:58:57.949 [info] Process Execution: /project/workspace/other_project/.venv/bin/python -m pip list
14:58:58.162 [info] Process Execution: /project/workspace/other_project/.venv/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
14:58:58.192 [info] Process Execution: /project/workspace/other_project/.venv/bin/python -m ipykernel_launcher --f=/~/.local/share/jupyter/runtime/kernel-v2-18791UmM5kZOsfZ8o.json
    > cwd: //project/workspace/other_project
14:59:00.672 [info] Kernel successfully started
14:59:00.691 [info] Process Execution: /project/workspace/other_project/.venv/bin/python /~/.vscode-server/extensions/ms-toolsai.jupyter-2024.5.0-linux-x64/pythonFiles/printJupyterDataDir.py

Coding Language and Runtime Version
python v3.8
Language Extension Version (if applicable)
Pylance v2024.6.1
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote

NOTE: I think it has something to do with pylance not finishing loading with one module before switching to another. I found that if I switch back to the previous module and then wait for the highlights to paint that it sometimes unsticks the jupyter notebook.
i.e. starting at notebook a in module A going to file b in module B, if you go back to a too quickly then it seems to get stuck. But if you navigate back to b and wait for a little bit, it sometimes allows a to paint as well.

Also, I've noticed that my notebook stops saving properly when this happens as well. It claims that it's failed to save and no matter how many times I retry it fails to save. This is very frustrating because it causes me to lose progress. I'm not sure if that's a different problem associated with restarting the extension host, though.

Another behavior I noticed was that if the highlighting is frozen and you change the project interpreter manually (i.e. cmd + shift + p -> select interpreter) it unfreezes the highlights. But then if you go back to the interpreter that's the same as one being used for the jupyter kernel it will then freeze again.

Here's a video of me reproducing the problem, it took me a few tries but you'll see near the end that it freezes as described:
https://www.loom.com/share/d7cb8b8ec70942998904e5d6f4e9c6f6?sid=4ea8ca7d-972f-4274-97e3-cb1fecdb176c


Error with NZBGet and CouchPotato

I'm getting a script failure in the NZBGet log that references a UNC share but is using double the "". For example "\\<IP_ADDRESS>\myshare\shared\filename". I'm using mapped drive letters and not UNC. I've looked in the logs and config files and nothing obvious jumps out at me.

Can you post the error and some logging info? Also post your autoProcess settings
Sent from my iPhone

On Jan 28, 2016, at 10:12, charlieny100<EMAIL_ADDRESS>wrote:
I'm getting a script failure in the NZBGet log that references a UNC share but is using double the "" For example "\19216811\myshare\shared\filename" I'm using mapped drive letters and not UNC I've looked in the logs and config files and nothing obvious jumps out at me
—
Reply to this email directly or view it on GitHub.

I just checked and that movie was converted and moved so it looks like it worked. I'm not sure why NZBGet is reporting it as a failure. So while I have a problem, it is a smaller problem than I thought.
Is there a way to make the file size smaller? I'm used to transcoding to smaller file size.


tuifimanager: 4.0.0 -> 4.0.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for tuifimanager is: A cross-platform terminal-based termux-oriented file manager
meta.homepage for tuifimanager is: https://github.com/GiorgosXou/TUIFIManager
meta.changelog for tuifimanager is: https://github.com/GiorgosXou/TUIFIManager/blob/refs/tags/v4.0.5/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.0.5 with grep in /nix/store/06bmrva8zg5msxv27ia9g6ba5j91rc81-tuifimanager-4.0.5
found 4.0.5 in filename of file in /nix/store/06bmrva8zg5msxv27ia9g6ba5j91rc81-tuifimanager-4.0.5

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

tuifimanager

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/06bmrva8zg5msxv27ia9g6ba5j91rc81-tuifimanager-4.0.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tuifimanager https://github.com/r-ryantm/nixpkgs/archive/5de554215db9c4d7e0fb48d8403f8441cd94b5d1.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5de554215db9c4d7e0fb48d8403f8441cd94b5d1#tuifimanager

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/06bmrva8zg5msxv27ia9g6ba5j91rc81-tuifimanager-4.0.5
ls -la /nix/store/06bmrva8zg5msxv27ia9g6ba5j91rc81-tuifimanager-4.0.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages built:

tuifimanager
tuifimanager.dist

Maintainer pings
cc @michaelBelsanti @Sigmanificient for testing.

The changelog.md is officially depreciated thus it should be removed from meta See: GiorgosXou/TUIFIManager#103

Done

Since this package is under the by-name hierarchy, you may use nixpkgs-merge-bot to merge it yourself. Would you like to give it a try?

sure, @NixOS/nixpkgs-merge-bot merge

sure, @NixOS/nixpkgs-merge-bot merge

Try again with the exact message? Seems that it's not happy with the sure part: https://github.com/NixOS/nixpkgs-merge-bot/blob/cae47034242b6604db5199a73e5f4ce5121ffa74/nixpkgs_merge_bot/webhook/issue_comment.py#L33

sure, @NixOS/nixpkgs-merge-bot merge

Try again with the exact message? Seems that it's not happy with the sure part<EMAIL_ADDRESS>
Whoops!

@NixOS/nixpkgs-merge-bot merge

Oh we have to wait for ofborg, come back later!

i guess we need to wait until ofborg-eval is done

I will add support for the new dnd experimental feature in the following pr.
Already have some work done on the repository flake itself, but not sure how I should do it within nixpkgs

Any specific concerns other than adding a few dependencies?

Any specific concerns other than adding a few dependencies?

Since it is experimental, shouldn't be it treated in a specific way? I know some packages has boolean inputs, but i dont get how it works

Any specific concerns other than adding a few dependencies?

Since it is experimental, shouldn't be it treated in a specific way? I know some packages has boolean inputs, but i dont get how it works

If the dependencies are small in size, we usually don't bother. If you want to make them conditional (only added if explicitly enabled), you can grep x11Support for examples.

Any specific concerns other than adding a few dependencies?

Since it is experimental, shouldn't be it treated in a specific way? I know some packages has boolean inputs, but i dont get how it works

If the dependencies are small in size, we usually don't bother. If you want to make them conditional (only added if explicitly enabled), you can grep x11Support for examples.

Due to the way terminal drag & drop works, it adds quite a few dependencies, including Qt

@NixOS/nixpkgs-merge-bot merge


Placeholders inputs not centered with Android 4.1.2

Hi, I have a problem with placeholders inputs in mobile theme of topcoat v0.8.0 when testing on a android phone in version 4.1.2. Placeholders are not centered. The problem affect just placeholder not value like you can see in screenshots. With a computer browser i haven't the problem.

We are cleaning up and getting ready for a new start on Topcoat from a team within Adobe. The next release has a new design and will start from an orphaned branch, so none of this will still exist.


Create .NET 8.0 Pluggable Agent

Since the .NET 8.0 preview is out, we should create a pluggable agent extension and test it with the engine. This issue covers the testing part, since the extension will be a separate project.

:tada: This issue has been resolved in version 2.0.0-alpha8 :tada:
The release is available on:

GitHub Release
NuGet Package


Bower component not generated in windows

I am using Pattern Lab Node- Gulp Edition v1.3.2 on Windows.
Expected Behavior
Bower component in /styleguide should be generated
Actual Behavior
Not generated and resulting 404 on home
Steps to Reproduce
Run all just like documentation tells in Windows 7

I also had this issue. The problem appears to be in the pl-copy:styleguide task. Use Gulp debug to see what the task is grabbing and where it is moving those files. For me changing the task to the following worked:
// Styleguide Copy everything but css
gulp.task('pl-copy:styleguide', function(){
  return gulp.src('**/!(*.css)', {cwd: paths().source.styleguide})
    .pipe(gulp.dest(path.resolve(paths().public.root + '/styleguide')))
    .pipe(browserSync.stream());
});

I haven't run PL Node on Windows 7 in a long long time, but can confirm that this is working on Windows 10 against a copy of this repo.

What version of node are you running? node - v

Update: I tested this tonight and am getting a ton of 404's on the client - which is not expected.
Investigating.

@arianjinx a fix for this is now on the dev branch. will go out with next release

Hello thank you @bmuenzenmeyer sorry i just read the update, nice 😆 .
I managed to have some temporary fix by changing styleguide path to this (adding cwd).
return gulp.src(path.resolve(paths().source.styleguide, 'styleguide/**/!(*.css)'), { cwd: path.resolve(paths().source.styleguide, 'styleguide') })
Although it breaks gulp and needs to restart sometimes, but it's okay.

Sorry to say this issue is still unresolved for me. I am running Windows 10, Node v6.8.1, npm v3.10.9, gulp-cli 1.2.2, and gulp v4.0.0-alpha.2
Steps to reproduce:

clone repo
run npm install
run gulp pl-copy:styleguide

This results in an empty folder dist in public/styleguide/.
If I run gulp pl-copy:styleguide-css the folder structure looks like this public/styleguide/css/dist/ whereas dist is empty too.

https://github.com/pattern-lab/edition-node-gulp/releases/tag/v1.3.4 should resolve this - would appreciate independent verification!

I hereby confirm: it is working as expected. Thank you very much!


Fix lag when loading the Name_layer_special group

When a group is deleted, it is "merged" into the Name_layer_special group by adding a redirection from the original group's ID to Name_layer_special's ID in the faction_id table.
Then, it deletes all members of the group. However, that breaks this statement which is an INNER JOIN, and only returns a row if there is a row in both tables.
Since the deleted group does not have any members, this query will not return the deleted group's ID, and that ID will not be associated with this group.
This caused a problem, because the deleted group's ID is still associated with all the reinforcements with that group. Whenever the group of a reinforcement is looked up, it will find the Name_layer_special group through the faction_id table's association. However, the lookup will not be cached, because the cache key is based on any IDs associated with the resultant group, and in this case, it does not include the deleted group's ID.
Therefore, with no caching, a database lookup will occur every time the group is needed, which will be performed on the main thread and can occur several times during, for instance, a single /cti or block break.
The fix involves using LEFT JOIN instead of INNER JOIN, so that the deleted group will still be returned even though it does not have any members.

based


good job,but i cant find "swap face.ipynb"

thank you,that's great work...

It is not yet released.
Sorry about that.

Any updates on this? Is the release of the face-swap part still planned?

It is not yet released.
Sorry about that.

Any update? Thx.

https://github.com/AliaksandrSiarohin/motion-cosegmentation
python part_swap.py --source_image ... --target_video ... --checkpoint vox-first-order.pth.tar --config config/vox-256-10segments.yaml --supervised --first_order_motion_model


Unable to debug asp.net core api (.net core 2.1 / VS 2017)

I am unable to debug sample asp.net core web api application created through https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?view=aspnetcore-2.1.
I am using windows 10 / iis express / .net core 2.1 / latest vs 2017
Getting error: An error occurred attempting to determine the process id of dotnet.exe which is hosting your application. A task was canceled.
There was warning in event log: The directory specified for caching compressed content C:\inetpub\temp\IIS Temporary Compressed Files\xxxxx AppPool is invalid.  Static compression is being disabled.
Even though above path is wrong as i am using iis express, After creating above path, nothing get logged in event log but still getting error.

Please report VS debugging issues through the VS feedback tool.

Can you run without debugging (CTL+F5)?

Yeah I can

I've primarily seen this for sites that have enabled client certificates or windows auth. Have you enabled any non-default IIS Express settings?

Yup initially i was thinking same, but everything is default. I can attach to dotnet.exe after running thru ctrl + f5 and debug it then,

I am using windows 10 / iis / .net core 2.1 / latest vs 2017 and I have the some problem and yes, the only way to debug it is to attach dotnet.exe after running ctrl + f5.

Glad you got it working! Closing this issue.

I had a similar issue when running multiple (two) startup projects. Switching to start the .net core project alone and so going back to run both helped in my case.

I encountered this error when trying to launch a downloaded project in which the target framework version was different from the version installed in my environment. I opened the “.csproj” file in a text editor, corrected the version in the “TargetFramework” node and saved the modified file. In order to be sure to make the changes take effect, I closed and reopened the Visual Studio solution containing the project. Then the project started correctly.


Create draft example project workflow

I think a lot of people see Git as abstract, so having an example up front will be really important to ground people before they look at the details.
Could we make a draft workflow this week?

Is this the kind of thing that is intended to go into Project-Flows?
https://github.com/deepskies/DeepWiki/wiki/Project-Flows

@bnord  Is this what you were thinking about? https://github.com/deepskies/DeepWiki/wiki/Project-Flows/9ad590c2c05a05be49b8d9349e0938950ca0a7c3


Refactor part of server settings code

It's difficult to fix some corner case, such as

turn share_printers and remote_any on, keep remote_admin off
turn share_printers off.
remote_admin is still take effect.

found a similar problem #158

We need to do a lot of regression testing here - the proposed changes look like they might cause problems when updating a customized cupsd.conf file, and we absolutely want to minimize how much of the cupsd.conf file is changed. The most common support advice is "enable debug logging with cupsctl --debug-logging", but if doing so wrecks an otherwise working configuration then we'll have angry users...

The intention here is only change the order of options in cupsd.conf. If this is not desired, we need write options in two place as before.

First time encountering a option.
Write any required missing option.

But we don‘t need to record if the option was changed (don't need test the condition remote_admin >=0, just assign old_remote_admin to remote_admin in first place), because it will write to new cupsd.conf file anyway。It is this part that complicates things。I can update the patch if it makes sense to you。

@reddevillg Thanks for the feedback! I'm not specifically opposed to your changes, I just want to make sure they don't introduce any regressions... I'd be doing the same if I was making the changes, if only because I've broken things a time or two in the past... :)

Any update on this?

Hi @AtariDreams ,
I'm planning refactor the cupsctl code to prevent removal of comments, so cupsctl can be used more widely (this will need more explicit comments in the cupsd.conf, so then we won't need to add comments of our own during the execution of the command) - I'm keeping this PR opened for later checking the functionality from PR is in the new code as well.

Hi @reddevillg ,
thank you for the PR! We are trying to implement comment preserving functionality in https://github.com/OpenPrinting/cups/pull/640/ , so it would be great if the PR didn't add comments and didn't change the position of directives, because if it does, it can move the directive from the comment which is relevant to the directive.
Would you mind adjusting the PR based on this premise or you don't mind if I do it?
Either way we should add cupsctl tests into test suite as well before merging this PR.

@zdohnal I'm not sure if "comment preserving" is a good idea. Thinking about someone adding a comment to explain the following directives, cupsctl changes server settings later, but preserving the comment which explain the directives changed before.
I think user(admin) should aware that if change cupsd.conf by manual, it should do it always.

@zdohnal I'm not sure if "comment preserving" is a good idea. Thinking about someone adding a comment to explain the following directives, cupsctl changes server settings later, but preserving the comment which explain the directives changed before.

We've updated the default comments to be as generic as they can be, so they could make sense with more configuration combinations. So unless the user doesn't add the exact comment like "This allows remote access", we're ok. But in such cases IMO it is a user error - if user adds comments on his own, he is responsible for its contents.

I think user(admin) should aware that if change cupsd.conf by manual, it should do it always.

IMO the combined use of manual edit and of a tool is ok - tool should manipulate with directives and its values, limit or policy scopes and shouldn't touch comments at all, and manual edit is here for more precise changes.

@zdohnal OK, I can live with that :)
Back to the original issue, i'm glad to continue the PR, but I need some help to clear up the concepts here:

Is "remote_admin" related to "remote_any"? Can i turn remote_admin on and keep remote_any off?

Definitely not for 2.4.x, maybe for 2.5.
@zdohnal Can I get you to look at this since it affects the cupsd.conf code?


Factorize REGISTER_* macros and logic for ports and nifs

esp32, rp2040 and stm32 all use the same logic to use .ctor runtime to register drivers and nifs collections.
Also use the smaller constructor name for nifs of RP2040 on other platforms to maintain compatibility as RP2040 builds have to explicitely list nifs so they are not gc'd. EPS32 is unaffected as enabling of nifs is done through menuconfig.
These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

Everything looks good, but I'm not sure if I understood this:

Also use the smaller constructor name for nifs of RP2040 on other platforms to maintain compatibility as RP2040 builds have to explicitely list nifs so they are not gc'd. EPS32 is unaffected as enabling of nifs is done through menuconfig.

Can you clarify it?

The three sets of macros (esp32, stm32, rp2040) were identical, except for the name of the constructor for NIFs.
In rp2040_sys.h, line 72:
    __attribute__((constructor)) void NAME##_nif()                          \

In stm_sys.h, line 84
    __attribute__((constructor)) void NAME##register_nif_collection()       \

In esp32_sys.h, line 75
    __attribute__((constructor)) void NAME##register_nif_collection()       \

I chose the name from rp2040_sys.h because it's referred to in CMakeLists.txt with -Wl,-u -Wl,<name>_nif:
    target_link_options(libAtomVM${PLATFORM_LIB_SUFFIX} PUBLIC "SHELL:-Wl,-u -Wl,networkregister_port_driver -Wl,-u -Wl,otp_socket_nif -Wl,-u -Wl,otp_net_nif -Wl,-u -Wl,otp_ssl_nif")
endif()

target_link_options(libAtomVM${PLATFORM_LIB_SUFFIX} PUBLIC "SHELL:-Wl,-u -Wl,gpio_nif -Wl,-u -Wl,otp_crypto_nif")


[Bug]: Building (cross-compiling) dlib into amd64 container fails

What Operating System(s) are you seeing this problem on?
Linux (x86-64), macOS (Apple Silicon)
dlib version
19.24.1
Python version
3.12
Compiler
GNU C 12.2.0
Expected Behavior
It should build and install fine
Current Behavior
It fails when building docker container on Apple M1 using
docker buildx build --platform=linux/amd64 -t myimage .

facerecogsvc git:(main) ✗ docker buildx build --platform=linux/amd64 -t registry.gitlab.com/digicard/mldlcv/facerecogsvc-amd64 .
[+] Building 269.7s (9/16)                                                                                docker-container:mybuilder
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 2.20kB                                                                                0.0s
 => [internal] load metadata for docker.io/library/python:3.12-slim                                                                                0.7s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [ 1/12] FROM docker.io/library/python:3.12-slim@sha256:2b0079146a74e23bf4ae8f6a28e1b484c6292f6fb904cbb51825b4a19812fcd8                                                                        0.0s
 => => resolve docker.io/library/python:3.12-slim@sha256:2b0079146a74e23bf4ae8f6a28e1b484c6292f6fb904cbb51825b4a19812fcd8                                                                          0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 9.59kB                                                                                0.0s
 => CACHED [ 2/12] RUN apt-get update && apt-get install -y build-essential cmake                                                                                0.0s
 => CACHED [ 3/12] RUN mkdir /app                                                                                0.0s
 => CACHED [ 4/12] WORKDIR /app                                                                                0.0s
 => ERROR [ 5/12] RUN pip install dlib                                                                                268.8s
------
 > [ 5/12] RUN pip install dlib:
1.789 Collecting dlib
1.893   Downloading dlib-19.24.6.tar.gz (3.4 MB)
2.088      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3.4/3.4 MB 20.9 MB/s eta 0:00:00
2.506   Installing build dependencies: started
4.436   Installing build dependencies: finished with status 'done'
4.438   Getting requirements to build wheel: started
4.828   Getting requirements to build wheel: finished with status 'done'
4.830   Preparing metadata (pyproject.toml): started
5.182   Preparing metadata (pyproject.toml): finished with status 'done'
5.185 Building wheels for collected packages: dlib
5.186   Building wheel for dlib (pyproject.toml): started
65.27   Building wheel for dlib (pyproject.toml): still running...
132.2   Building wheel for dlib (pyproject.toml): still running...
199.2   Building wheel for dlib (pyproject.toml): still running...
259.5   Building wheel for dlib (pyproject.toml): still running...
268.1   Building wheel for dlib (pyproject.toml): finished with status 'error'
268.2   error: subprocess-exited-with-error
268.2
268.2   × Building wheel for dlib (pyproject.toml) did not run successfully.
268.2   │ exit code: 1
268.2   ╰─> [617 lines of output]
268.2       <string>:234: SyntaxWarning: invalid escape sequence '\('
268.2       <string>:235: SyntaxWarning: invalid escape sequence '\('
268.2       <string>:236: SyntaxWarning: invalid escape sequence '\('
268.2       running bdist_wheel
268.2       running build
268.2       running build_ext
268.2       Building extension for Python 3.12.8 (main, Dec  4 2024, 20:39:59) [GCC 12.2.0]
268.2       Invoking CMake setup: 'cmake /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/tools/python -DCMAKE_LIBRARY_OUTPUT_DIRECTORY=/tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/build/lib.linux-x86_64-cpython-312 -DPYTHON_EXECUTABLE=/usr/local/bin/python3.12 -DDLIB_USE_FFMPEG=OFF -DCMAKE_BUILD_TYPE=Release'
268.2       -- The C compiler identification is GNU 12.2.0
268.2       -- The CXX compiler identification is GNU 12.2.0
268.2       -- Detecting C compiler ABI info
268.2       -- Detecting C compiler ABI info - done
268.2       -- Check for working C compiler: /usr/bin/cc - skipped
268.2       -- Detecting C compile features
268.2       -- Detecting C compile features - done
268.2       -- Detecting CXX compiler ABI info
268.2       -- Detecting CXX compiler ABI info - done
268.2       -- Check for working CXX compiler: /usr/bin/c++ - skipped
268.2       -- Detecting CXX compile features
268.2       -- Detecting CXX compile features - done
268.2       -- pybind11 v2.12.0
268.2       -- Found PythonInterp: /usr/local/bin/python3.12 (found suitable version "3.12.8", minimum required is "3.6")
268.2       -- Found PythonLibs: /usr/local/lib/libpython3.12.so
268.2       -- Performing Test HAS_FLTO
268.2       -- Performing Test HAS_FLTO - Success
268.2       -- Using CMake version: 3.25.1
268.2       -- Compiling dlib version: 19.24.6
268.2       -- SSE4 instructions can be executed by the host processor.
268.2       -- Enabling SSE4 instructions
268.2       -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
268.2       -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
268.2       -- Found Threads: TRUE
268.2       -- Could NOT find X11 (missing: X11_X11_INCLUDE_PATH X11_X11_LIB)
268.2        *****************************************************************************
268.2        *** DLIB GUI SUPPORT DISABLED BECAUSE X11 DEVELOPMENT LIBRARIES NOT FOUND ***
268.2        *** Make sure libx11-dev is installed if you want GUI support.            ***
268.2        *** On Ubuntu run: sudo apt-get install libx11-dev                        ***
268.2        *****************************************************************************
268.2       -- Searching for JPEG XL
268.2       -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
268.2       -- PkgConfig could not be found, JPEG XL support won't be available
268.2       -- Searching for BLAS and LAPACK
268.2       -- Searching for BLAS and LAPACK
268.2       -- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
268.2       -- Looking for cblas_ddot
268.2       -- Looking for cblas_ddot - not found
268.2       -- Looking for sys/types.h
268.2       -- Looking for sys/types.h - found
268.2       -- Looking for stdint.h
268.2       -- Looking for stdint.h - found
268.2       -- Looking for stddef.h
268.2       -- Looking for stddef.h - found
268.2       -- Check size of void*
268.2       -- Check size of void* - done
268.2        *****************************************************************************
268.2        *** No BLAS library found so using dlib's built in BLAS.  However, if you ***
268.2        *** install an optimized BLAS such as OpenBLAS or the Intel MKL your code ***
268.2        *** will run faster.  On Ubuntu you can install OpenBLAS by executing:    ***
268.2        ***    sudo apt-get install libopenblas-dev liblapack-dev                 ***
268.2        *** Or you can easily install OpenBLAS from source by downloading the     ***
268.2        *** source tar file from http://www.openblas.net, extracting it, and      ***
268.2        *** running:                                                              ***
268.2        ***    make; sudo make install                                            ***
268.2        *****************************************************************************
268.2       CUDA_TOOLKIT_ROOT_DIR not found or specified
268.2       -- Could NOT find CUDA (missing: CUDA_TOOLKIT_ROOT_DIR CUDA_NVCC_EXECUTABLE CUDA_INCLUDE_DIRS CUDA_CUDART_LIBRARY) (Required is at least version "7.5")
268.2       -- Found CUDA, but CMake was unable to find the cuBLAS libraries that should be part of every basic CUDA install. Your CUDA install is somehow broken or incomplete. Since cuBLAS is required for dlib to use CUDA we won't use CUDA.
268.2       -- DID NOT FIND CUDA
268.2       -- Disabling CUDA support for dlib.    Stop.
268.2       make[3]: *** Waiting for unfinished jobs....
268.2       make[3]: *** write jobserver: Bad file descriptor.  Stop.
268.2       lto-wrapper: fatal error: make returned 2 exit status
268.2       compilation terminated.
268.2       /usr/bin/ld: error: lto-wrapper failed
268.2       collect2: error: ld returned 1 exit status
268.2       gmake[2]: *** [CMakeFiles/_dlib_pybind11.dir/build.make:482: /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/build/lib.linux-x86_64-cpython-312/_dlib_pybind11.cpython-312-x86_64-linux-gnu.so] Error 1
268.2       gmake[1]: *** [CMakeFiles/Makefile2:118: CMakeFiles/_dlib_pybind11.dir/all] Error 2
268.2       gmake: *** [Makefile:91: all] Error 2
268.2       Traceback (most recent call last):
268.2         File "/usr/local/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
268.2           main()
268.2         File "/usr/local/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
268.2           json_out['return_val'] = hook(**hook_input['kwargs'])
268.2                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
268.2         File "/usr/local/lib/python3.12/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
268.2           return _build_backend().build_wheel(wheel_directory, config_settings,
268.2                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 438, in build_wheel
268.2           return _build(['bdist_wheel', '--dist-info-dir', str(metadata_directory)])
268.2                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 426, in _build
268.2           return self._build_with_temp_dir(
268.2                  ^^^^^^^^^^^^^^^^^^^^^^^^^^
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 407, in _build_with_temp_dir
268.2           self.run_setup()
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 522, in run_setup
268.2           super().run_setup(setup_script=setup_script)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/build_meta.py", line 320, in run_setup
268.2           exec(code, locals())
268.2         File "<string>", line 243, in <module>
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/__init__.py", line 117, in setup
268.2           return distutils.core.setup(**attrs)
268.2                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 183, in setup
268.2           return run_commands(dist)
268.2                  ^^^^^^^^^^^^^^^^^^
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/core.py", line 199, in run_commands
268.2           dist.run_commands()
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 954, in run_commands
268.2           self.run_command(cmd)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 995, in run_command
268.2           super().run_command(command)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
268.2           cmd_obj.run()
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/command/bdist_wheel.py", line 381, in run
268.2           self.run_command("build")
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
268.2           self.distribution.run_command(command)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 995, in run_command
268.2           super().run_command(command)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
268.2           cmd_obj.run()
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/command/build.py", line 135, in run
268.2           self.run_command(cmd_name)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/cmd.py", line 316, in run_command
268.2           self.distribution.run_command(command)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/dist.py", line 995, in run_command
268.2           super().run_command(command)
268.2         File "/tmp/pip-build-env-bxn3aff6/overlay/lib/python3.12/site-packages/setuptools/_distutils/dist.py", line 973, in run_command
268.2           cmd_obj.run()
268.2         File "<string>", line 168, in run
268.2         File "<string>", line 209, in build_extension
268.2         File "/usr/local/lib/python3.12/subprocess.py", line 413, in check_call
268.2           raise CalledProcessError(retcode, cmd)
268.2       subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '--', '-j4']' returned non-zero exit status 2.
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘initialize_scanners’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_svm_object_detection_problem.h:499:34,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_svm_object_detection_problem.h:94:32,
268.2           inlined from ‘train_impl’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_object_detection_trainer.h:371:17,
268.2           inlined from ‘train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_object_detection_trainer.h:327:80,
268.2           inlined from ‘train_simple_object_detector_on_images’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/tools/python/src/simple_object_detector.h:225:32,
268.2           inlined from ‘train_simple_object_detector’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/tools/python/src/simple_object_detector.h:260:133:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘train_simple_object_detector’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix_data_layout.h:335:43,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix.h:1127:26,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/function.h:55:13,
268.2           inlined from ‘do_train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/svm_c_trainer.h:262:87:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘do_train’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘deserialize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:273:30,
268.2           inlined from ‘deserialize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:276:28,
268.2           inlined from ‘deserialize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_processing/../image_processing/scan_fhog_pyramid.h:502:20:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘deserialize’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix_data_layout.h:335:43,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix.h:1440:34,
268.2           inlined from ‘do_train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/svm_c_trainer.h:247:37:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘do_train’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘push_back.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:769:30:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘push_back.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘push_back.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:769:30:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘push_back.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix_data_layout.h:335:43,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix.h:1440:34,
268.2           inlined from ‘do_train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/svm_c_trainer.h:247:37:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘do_train’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix_data_layout.h:335:43,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix.h:1440:34,
268.2           inlined from ‘do_train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/svm_c_trainer.h:247:37:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘do_train’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘set_max_size.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix_data_layout.h:335:43,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix.h:1127:26,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/function.h:55:13,
268.2           inlined from ‘do_train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/svm_c_trainer.h:262:87:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘do_train’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix_data_layout.h:335:43,
268.2           inlined from ‘set_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/matrix.h:1440:34,
268.2           inlined from ‘do_train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/svm_c_trainer.h:247:37:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In member function ‘do_train’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘push_back’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:769:30,
268.2           inlined from ‘push_back’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:794:18,
268.2           inlined from ‘add_image_left_right_flips’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_processing/../image_processing/../image_transforms/interpolation.h:1208:29,
268.2           inlined from ‘train_simple_object_detector_on_images.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/tools/python/src/simple_object_detector.h:223:39:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘train_simple_object_detector_on_images.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘initialize_scanners’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_svm_object_detection_problem.h:499:34,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_svm_object_detection_problem.h:94:32,
268.2           inlined from ‘train_impl’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_object_detection_trainer.h:371:17,
268.2           inlined from ‘train’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/svm/structural_object_detection_trainer.h:327:80,
268.2           inlined from ‘train_simple_object_detector_on_images.constprop’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/tools/python/src/simple_object_detector.h:225:32:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘train_simple_object_detector_on_images.constprop’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       In member function ‘allocate_array’,
268.2           inlined from ‘set_max_size’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:438:59,
268.2           inlined from ‘resize’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:654:30,
268.2           inlined from ‘__ct ’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/matrix/../array/array_kernel.h:121:19,
268.2           inlined from ‘extract_image_chips.constprop.isra’ at /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/image_transforms/interpolation.h:1882:79:
268.2       /tmp/pip-install-qduxqlts/dlib_cd96a1845678482a977c19680cedfa9e/dlib/../dlib/memory_manager_stateless/memory_manager_stateless_kernel_1.h:54:24: warning: argument 1 value ‘18446744073709551615’ exceeds maximum object size<PHONE_NUMBER>854775807 [-Walloc-size-larger-than=]
268.2          54 |                 return new T[size];
268.2             |                        ^
268.2       /usr/include/c++/12/new: In function ‘extract_image_chips.constprop.isra’:
268.2       /usr/include/c++/12/new:128:26: note: in a call to allocation function ‘operator new []’ declared here
268.2         128 | _GLIBCXX_NODISCARD void* operator new[](std::size_t) _GLIBCXX_THROW (std::bad_alloc)
268.2             |                          ^
268.2       [end of output]
268.2
268.2   note: This error originates from a subprocess, and is likely not a problem with pip.
268.2   ERROR: Failed building wheel for dlib
268.2 Failed to build dlib
268.5 ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (dlib)
------
WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Dockerfile:40
--------------------
  38 |     # RUN pip install cmake
  39 |     # RUN pip install dlib==19.24.4
  40 | >>> RUN pip install dlib
  41 |
  42 |     # install remaining dependencies
--------------------
ERROR: failed to solve: process "/bin/sh -c pip install dlib" did not complete successfully: exit code: 1

Steps to Reproduce
Place:
FROM python:3.12-slim
RUN apt-get update && apt-get install -y build-essential cmake
RUN pip install dlib

into a Dockerfile and run:
docker buildx build --platform=linux/amd64 -t myimage .

Anything else?
It builds ok on linux/arm64 or  Apple M1 platforms

Update:
Changing install command to RUN LDFLAGS=-fno-lto  pip install dlib makes the build proceed.
But the test program fails on start with:
Traceback (most recent call last):
  File "/app/frapi-start.py", line 14, in <module>
    import FRAPI_impl
  File "/app/FRAPI_impl.py", line 18, in <module>
    import face_recognition
  File "/usr/local/lib/python3.12/site-packages/face_recognition/__init__.py", line 7, in <module>
    from .api import load_image_file, face_locations, batch_face_locations, face_landmarks, face_encodings, compare_faces, face_distance
  File "/usr/local/lib/python3.12/site-packages/face_recognition/api.py", line 4, in <module>
    import dlib
  File "/usr/local/lib/python3.12/site-packages/dlib/__init__.py", line 19, in <module>
    from _dlib_pybind11 import *
ImportError: dynamic module does not define module export function (PyInit__dlib_pybind11)

The same error is produced in linux/amd64 and linux/arm64 platforms

Cool.  Can you send me a PR that makes it work for you? :)

No Davis, it didn't work. It builds ok but fails in run.
The only way I was able to build the package was building it with clang. With both gnuc 10 and 12 the build fails.
It appears to be a problem related to LTO (A link optimization technique) bug either on dlib or pybind11.
I couldn't invest more time researching. Building with clang did the trick to me.
Hope it helps you too find the fix.

That Bad file descriptor makes it sound like your computer just ran out of file descriptors.  Maybe you have your descriptor limit set unusually low (e.g. do ulimit -n 10000 to increase it).

That Bad file descriptor makes it sound like your computer just ran out of file descriptors. Maybe you have your descriptor limit set unusually low (e.g. do ulimit -n 10000 to increase it).

It must be a linux-in-docker setting... I'll try your suggestion and post results here.
Thanks!

I encountered exactly the same problem. I am on a Mac building for linux/amd64... I am glad I found this... was going nuts trying all sorts. Nothing worked, including LDFLAGS=-fno-lto or ulimit.
Will go back to arm64... life is too short for this.

I encountered exactly the same problem. I am on a Mac building for linux/amd64... I am glad I found this... was going nuts trying all sorts. Nothing worked, including LDFLAGS=-fno-lto or ulimit.
Will go back to arm64... life is too short for this.

Only way of making it work I've found is to build using clang.
# -----------------------------------
# pre-install dlib to shorten following steps
# Install CLANG and build dlib with it
# and clean up dev tools afterwards
ARG BUILD_PKGS="wget build-essential cmake"
ARG CLANG_DEPS=""
ARG CLANG_PKGS="clang-15 lldb-15 lld-15"
RUN apt-get update && \
    apt-get install -y ${BUILD_PKGS} && \
    echo "deb http://apt.llvm.org/bullseye/ llvm-toolchain-bullseye main" >> /etc/apt/sources.list && \
    echo "deb-src http://apt.llvm.org/bullseye/ llvm-toolchain-bullseye main" >> /etc/apt/sources.list && \
    echo "deb http://apt.llvm.org/bullseye/ llvm-toolchain-bullseye-15 main" >> /etc/apt/sources.list && \
    echo "deb-src http://apt.llvm.org/bullseye/ llvm-toolchain-bullseye-15 main" >> /etc/apt/sources.list && \
    wget -O - https://apt.llvm.org/llvm-snapshot.gpg.key | apt-key add -  && \
    apt update && apt -y upgrade && \
    apt-get install -y ${CLANG_DEPS} && \
    apt-get install -y ${CLANG_PKGS} && \
    CC=clang-15 CXX=clang++-15 LD=lld-15 pip install dlib==19.24.6 && \
    apt-get remove -y ${BUILD_PKGS} ${CLANG_DEPS} ${CLANG_PKGS}


CI/Makefile: disable uninlined_format_args clippy lint

New version of clippy introduced the uninlined_format_args lint which recommends putting variable names directly into format strings, like this:
let what = "world";
println!("Hello, {what}!");

// Instead of:
println!("Hello, {}!", what);

The problem with this feature is that rust-analyzer does not support renaming variables inside format strings yet. The lint has been downgraded to pedantic level and will most likely appear as such in the next release.
This commit disables the new lint in the CI and local Makefile. We can turn it on again after this feature gets better support from rust-analyzer.
Pre-review checklist

[x] I have split my patch into logically separate commits.
[x] All commit messages clearly explain what they change and why.
[ ] ~I added relevant tests for new features and bug fixes.~
[x] All commits compile, pass static checks and pass test.
[x] PR description sums up the changes and reasons why they should be introduced.
[ ] ~I added appropriate Fixes: annotations to PR description.~

println!("Hello, {}!", world);

You've probably meant:
println!("Hello, {}!", what);

println!("Hello, {}!", world);

You've probably meant: println!("Hello, {}!", what);

Thanks, I corrected the PR description and the commit message.


UP-4853: Convert admin tools portlet to app launchers

Checklist

[x] the individual contributor license agreement is signed
[x] commit message follows commit guidelines
[x] view conforms with WCAG 2.0 AA

Description of change

https://issues.jasig.org/browse/UP-4853
In the spirit of continuing to improve uPortals user interface @drewwills  suggested that the admin tools portlet, which is currently a list of plain text links, could be converted into a series of app launchers. One launcher for each link with icons making each one easier to identify and making the admin page easier on the eyes.

Some requests...

Add app-launchers for Announcements Admin, Please Register, and Emergency Alert Admin (and remove those 3 from the layout)
Publish all with chrome=no-chrome
Re-do the icons with some color and perhaps a touch of drop shadow... something to give them some texture

Coverage increased (+0.01%) to 22.89% when pulling 84976d5ce4a6e69858bbacf8b5fae485bcedd658 on ChristianMurphy:UP-4853 into ce925e5ed28f05585fa3287b869f18bae151c405 on Jasig:master.

Nice visual improvement!

Coverage increased (+0.01%) to 22.89% when pulling c7cf0b08806878f7ebd663e5dba1c3a392c77326 on ChristianMurphy:UP-4853 into ce925e5ed28f05585fa3287b869f18bae151c405 on Jasig:master.

@ChristianMurphy 👍
Definitely a very nice idea to use app-launcher for that ! for what told you @drewwills you can find also insight in Ionicons (MIT License).
It could be perhaps great to find for uPortal 5 or 6 a way to centralized the place where artworks (img, font, svg) are. Because pictures (drawer img, app-launcher icons, mobile icons, etc.) are locate at different places in tree.
something like https://myhuskynet.univ.edu/artworks/images https://myhuskynet.univ.edu/artworks/font
I don't know if it's something interesting but it may be practical.

Coverage increased (+0.01%) to 22.89% when pulling 5b5342d34de944d3649b2c233f96492c530b91bf on ChristianMurphy:UP-4853 into ce925e5ed28f05585fa3287b869f18bae151c405 on Jasig:master.

Add app-launchers for Announcements Admin, Please Register, and Emergency Alert Admin (and remove those 3 from the layout)
Publish all with chrome=no-chrome

Done and Done!
Thanks for the suggestions

Re-do the icons with some color and perhaps a touch of drop shadow... something to give them some texture

I agree this could use some more spice. :hot_pepper:
However with the current implementation of app launchers, adding color or shadow effects would require modifying the original font-awesome images.
Those images fall under the Open Font License which has a share and share alike cause that would require uPortal also be under the Open Font License. :scroll:
An approach that could preserve license integrity and address @cousquer's comment

It could be perhaps great to find for uPortal 5 or 6 a way to centralized the place where artworks (img, font, svg) are

Would be to add icon font support to app launchers, so the fonts could be styled with CSS which is allowed under the Open Font License, as well as allowing for centralization in Resource Server.

👍🏻 That's exactly what I was thinking, christian.

Jaffathecake has write something really interesting for you:
https://jakearchibald.com/2017/combining-fonts/

@ChristianMurphy -- I've glanced through all the XML deltas and they look great.  :+1:
Do you have time to export new versions of the images with some transparent padding around the icons, like we brainstormed?  (I think those would look better.)

Coverage increased (+0.01%) to 22.89% when pulling ec590da32cfbc165c2c43d716ffc3f5f3910ec5c on ChristianMurphy:UP-4853 into ce925e5ed28f05585fa3287b869f18bae151c405 on Jasig:master.

Coverage increased (+0.006%) to 22.886% when pulling 16cc7f8ccf5ec2410d93ffd578a895fe189926dc on ChristianMurphy:UP-4853 into ce925e5ed28f05585fa3287b869f18bae151c405 on Jasig:master.

@apetro -- Looks like your feedback was implemented.  I'm going to go ahead and merge.


dbeaver/pro#1711 Dictionary enhancements

Two queries on opening (loading page with current value):
SELECT rental_id dbvrvalue, rental_id FROM public.rental WHERE rental_id >= 3407 ORDER BY rental_id ASC
LIMIT 100
SELECT rental_id dbvrvalue, rental_id FROM public.rental WHERE rental_id < 3407 ORDER BY rental_id DESC
LIMIT 100

On pagination:
SELECT rental_id dbvrvalue, rental_id FROM public.rental WHERE rental_id >= 3407 ORDER BY rental_id ASC
LIMIT 200 OFFSET 300

[ ] sorting works correctly
[ ] pagination works correctly
[ ] search works correctly
[x] it works comparable fast on big tables

For data types that are not string, numeric or datetime only one value should appear in the dictionary panel. Search should work only on equality.
Please, check at least on string, numeric, date/time/timestamp, uuid. You can find uuid and date fk in PostgreSQL 12: dvdrental.Elizabeth.123table. Numeric fk can be found in the streamings table of the same schema. But it would be nice to check it on some other database too.

pagination fast-forward makes the arrow inactive

verified with an additional ticket  https://github.com/dbeaver/dbeaver/issues/20897


Refactor config provider

This PR introduces more abstract about ConfigProvider and hides more ini references.

CI failure is related


Can't type * into Hex View

When I open a new file in Hex View and click in the ascii area, I can't type the * character (0x2a). Entering in the hex code on the binary side works, of course, but that's annoying.
I've seen this on Mac and Windows (both QWERTY, in case that matters).

This is intended -- * in that context is "Follow pointer". If the address under your cursor is a pointer, it will follow it.
I'm closing this for now -- once we have user customizable keystrokes you'll be able to remove this mapping yourself if you prefer, but in the meantime this is by design.

Oh wait, I misunderstood the request. I see what you mean. Yeah, agreed in the ascii side it should probably work.

Fixed in build 1457


2.x Client InterestChannel Should Implement InstanceInfo Cleanup

When the client InterestChannel receive a change(Interest) command, it should have the option to explicitly unregister from the registry instanceInfos that are no longer wanted by any consumer. This is useful for users with tighter memory requirements.

archiving as eureka2 work is going through some larger internal changes.


Digital Rights reviewer: insecure apps get full score (lioapp)

The lioapp get score 4,4 but is hosted on http domain, not https

hey @larrysalibra can you please address this.

Using https seems like it should be a basic criteria for app mining eligibility.  We can create a policy to catch these and flag these during our review, but it seems like something that can be caught before app mining reviews even starts either by looking at the list or making the application form not accept URLs that don't start with https://. Thoughts @hstove @GinaAbrams @pstan26 ?

Sounds like the next step is to update our docs with an https requirement.

Asked about this in #201.


feat: Initial TEE Plugin

Relates to:

Risks
Low as this is an optional plugin to include for TEE based agents.

Background
Create a boilerplate plugin for deploying agents in TEE and provide 2 key functions for agents:

Derive Key for deriving private keys within a TEE running the [Dstack SDK]
Remote Attestation for generating RA Quote on report data passed in as a parameter

Optimize Docker Container to reduce size from 11.1GB to <6GB based on comment from [tebayoso] (https://github.com/ai16z/eliza/pull/293#issuecomment-2474228100) in original docker PR #293
What does this PR do?

Note: To run in TEE, you must have specialized hardware. Reach out to Phala Network for help getting started

Add Support for deploying docker containers in TEE
Create 3 new providers called derive key, remote attestation, and wallet provider
Optimize Dockerfile for deployments
Add docker-compose.yaml file to use docker compose up

What kind of change is this?
Features

Why are we doing this? Any context or related work?
Autonomous Agents that trade onchain have a root of trust problem that requires a human to generate a wallet and provide a private key as part of the environment variables. This is a problem since humans can easily inject themselves into the process and make it easy for them to build ruggable agents. This solution aims to give users some verifiability with remote attestation and allow agents to autonomously generate their wallet within the TEE based on a secret salt instead of a private key. Now agents have a the autonomy to perform actions onchain without the possibility of a human manipulating the wallet since the human can no longer know what the private key since it is generated within the TEE.
Documentation changes needed?

Testing
Where should a reviewer start?
First a developer should use a Ubuntu 24.04 linux machine for best simulation. Character file must include teePlugin.
Detailed testing steps
Run TEE Simultator with docker (make sure docker is started)
docker run --rm -p 8090:8090 phalanetwork/tappd-simulator:latest

Edit Character File to use teePlugin and install
pnpm install
cd packages/core
pnpm install
cd -

Build your project
pnpm build

(Optional) For users running on Mac or Windows update .env file
# If running pnpm start use this endpoint
DSTACK_SIMULATOR_ENDPOINT="http://localhost:8090"
# If using pnpm docker to launch agent
DSTACK_SIMULATOR_ENDPOINT="http://host.docker.internal:8090"

Launch your agent
# For local testing
pnpm start
# For docker testing
pnpm docker

If you want to run on Intel TDX Server
Reach out to Phala Network team or me @HashWarlock to help get you deployed on a real TEE server through our TaaS Force team.

Adding documentation and updating the plugin.

[ ] Documentation on TEE Plugin
[ ] Add functions to derive raw key, derive ed25519 key for Solana, derive ecdsa key for evm chains


Loading zooming.js with head.js does not seem to work

I am not sure what is causing the issue. I follow advice online on how to load a .js file conditionally.
I would like to load zooming.js only on devices with a screen bigger than a certain amount of pixels, or another condition.
In this first test I load zooming.js with <script></script> inside the html and it works fine.
https://codepen.io/zuhocuyixu/pen/oqpdWz
In this second test I try to load zooming.js with head.js with no conditions at all, just to load it.
https://codepen.io/zuhocuyixu/pen/XEVEwG
And it does not work. Instead of head.js I also tried lazyload.js and the result is the same.
Trying to load a .css file with the same code works okay.
Any advice on why the second test does not load the zooming feature for the images?

Unfortunately, I don't have any advice for this issue after some investigation. I would rather not dig further for two reasons:

It's not a feature issue related to zooming itself.
I might be wrong, but I'm not sure about if there's any benefit from loading our library in <head> since zooming only starts listening to images after DOM content is fully loaded.

@kingdido999 Thank you for checking this.
How would you advice to make it so, that zooming is not laded on devices with a screen smaller than certain width in pixels?
Would you please specify what method I should research on achieving this?
Thank you

Posting this for future reference for the less experienced (like me) on how to load zooming conditionally.
In this case on screens bigger than certain amount of pixels.
Here is the original question:
https://stackoverflow.com/questions/49572604/loading-a-js-file-conditionally-how
And here the final result. Loads zooming if browser window width is more than 500px:
https://codepen.io/zuhocuyixu/pen/wmmyOZ


input plugin udp - field/tags additions leaking to other listen section

Version: Logstash 5 Alpha 4, logstash-input-udp-3.0.1
Operating System: last Debian Jessie
Config File (if you have sensitive info, please remove it):
input {
udp {
port => 1514
type => syslog
tags => ["udp1514"]
}
udp {
port => 5514
type => syslog
add_field => [ "dev_type", "spec-dev" ]
tags => ["udp5514"]
}
}
Sample Data:
Steps to Reproduce:
No one packet go to port 5514 (checked via tcpdump),  but cca 2000 packets in minute from port 1514 are "labeled" as going from port 5514.

Sorry, my bad definition. Must be 'add_tag', not 'tags'.
Interesting is: tags was added, but in random... :)
Closing.

Back to trees ... 'tags' is right definition ..

this is a consequence of how logstash output section works
1 event will be passed through the outputs in sequence, so if one output changes the event by adding the tags, then the second output will received the modified event.
If you want to achieve this, you need to use
filter { clone { clones => ["cloned"] } }
output {
  if [type] == "cloned" {
    udp {
      port => 1514
      type => syslog
      tags => ["udp1514"]
    }
  } else {
    udp {
      port => 5514
      type => syslog
      add_field => [ "dev_type", "spec-dev" ]
      tags => ["udp5514"]
    }
  }
}


FI-2723 Fix backend services discovery test versioning error

Summary
Fixes #23
This PR fixes the issue in which the Bulk Data V1 SMART Backend Services tests were using Discovery Tests for SMART STU2.  V1 Discovery Tests have been updated to reflect the requirements in the Bulk Data V1 SMART Backend Services Authorization profile, including:

Ungrouping the SMART Backend Services tests so that SMART Backend Services Authorization tests can be run without Discovery tests (to reflect that use of the well-known endpoint/discovery tests is a MAY, not a SHALL)
Checking the discovery metadata contents for all of the recommended fields.  Though inclusion of all of these fields is a SHOULD, the (optional) metadata contents test requires a correct token_endpoint entry to pass.  This is for two reasons:

The token_endpoint value is used in downstream tests
The token_endpoint value is the only one listed in the Bulk Data V1 IG that is also required in the SMART App Launch STU1 discovery/capabilities.

All other recommended fields tested issue warnings rather than failing the tests.
Bulk Data V2 tests are unchanged.
Testing Guidance
Tests can be run locally - select the Bulk Data Access V1.0.1 suite and use the Inferno Reference server preset.
Spec test included for the new test.

@Jammjammjamm I updated all of the versioning syntax to be consistent with vXXX and responded to both of your comments, so requesting re-review.


Rewritten seems to stop on ignored event

The documentation for Rewriter suggests that it can choose to completely ignore events thereby removing them from the rewritten stream, specifically it says
This may mean ignoring it, mutating it, or adding new events to the [`Writer`]'s buffer.

I am admittedly not completely sure that I fully understand how things are supposed to work, but the implementation of Rewritten does not currently seem to handle this case and seems to stop as soon as a Rewrite implementation does not push any events into the writer.
I tried to demonstrate this in the test case added by the first commit. The second commit tries to resolve this by effectively looping the Iterator::next implementation of Rewritten so that it continues with the next input event in case an output event was ignored completely.

This is definitely a bug in the implementation. Good spot!
The intention is that we'll keep yielding/processing events events from the underlying stream until it runs out. That means we need the loop you've implemented. I'll fix the CI failure on master and hopefully if travis is happy, we should be able to merge.

@adamreichold would you be able to rebase onto master? That should make travis green again.

would you be able to rebase onto master? That should make travis green again.

Pushed the rebase.


"Mean.npy" and "Std.npy"

Hi! What are the "Mean.npy" and "Std.npy" files? If I want to make my own dataset, how do I get the "Mean.npy" and "Std.npy" files?

The Mean.npy and Std.npy save the mean and standard deviation of each joint across all frames in the dataset (Its dimension is 2×(number of joints) since we treat the x and y dimensions separately). It is obtained by concatenating all motion sequences and apply np.mean or np.std across the time dimension. This is the code we used for our datasets.
import os
from tqdm import tqdm
import numpy as np
from os.path import join as pjoin

data_dir = 'your/motions/directory'
save_dir = pjoin(data_dir, '..')

source_list = os.listdir(data_dir)

data = []
for source_file in tqdm(source_list):
    source_data = np.load(pjoin(data_dir, source_file))
    data += [*source_data]

mean = np.mean(data, axis=0)
mean = mean[...,:2]
std = np.std(data, axis=0)
std = std[...,:2]
print(f'mean: {mean}')
print(f'std: {std}')

print(f'saving mean and std to {save_dir}')
np.save(pjoin(save_dir, 'Mean'), mean)
np.save(pjoin(save_dir, 'Std'), std)

The mean = mean[...,:2] row is meant to delete the confidence of the joint (mostly relevant when the joints were predicted by some detector) if it exists.

How do I get.npy files for my own dataset

This issue is discussed in #3 so closing it for now.


Support find-all-references on mapped types.

Need to put a 'mappedTypeOrigin' property in SymbolLinks

Fixes #12450
Thanks @ahejlsberg and @sandersn for the help.

Looks like the baselines for the mappedTypes1 test changed too.