Configurable allocation sizes

This adds an AllocationSizes struct to both the Vulkan and DX12 Allocator and AllocatorCreateDesc which allows users to configure the size of the memory blocks that are created to be suballocated from.
This doesn't currently clamp it to 256MB, which afaik is a problem for systems that don't support Resizable BAR, but I also don't know how to properly detect if someone is or isn't using Resizable BAR.
I also don't know if we need to enforce alignment, and if so what values do we need to use for alignment?
Closes #156

I think it needs to be 4MB aligned for DX12 MSAA support? https://github.com/Traverse-Research/gpu-allocator/blob/5ff4300b3ac47c939aac3da2934c31e771533aec/src/d3d12/mod.rs#L338
Would you rather I clamp it between 4MB and 256MB and silently force 4MB alignment, or return an error on creation if the values the user passes in aren't aligned?

Afaik for vulkan it'd technically be more correct to move the alignment requirement check to when the allocator is created and query the device for minMemoryMapAlignment, but based on https://vulkan.gpuinfo.org/displaydevicelimit.php?name=minMemoryMapAlignment I don't think it's really necessary.

Bumping this, @manon-traverse @MarijnS95 is what I have here with just allowing setting a static allocation size within a reasonable range acceptable?
If you'd like, I could move it into the backend impls and query the device for minimum/maximum allocation sizes, but I don't think it's necessary with the  4MB to 256MB clamp I'm currently using.
We could also try to do some fancy automatically scaling heap size based on memory usage, but that seems a lot more complicated and may have performance pitfalls.

Sorry for not paying attention to this PR!
I think it's fine the way you have it right now, and I'll merge it


Badge: Move the user's badge list in a dedicated tab

Merge the first PRs but need the following actions:

[ ] Complete Unit Test
[ ] Test update tags: check hash is rebuilt when tag id is changed -> User should be unlogged
[ ] Migration

[ ] Set all the tags props 'issuer' aligned with users (select user with issuer = true + update all their issuer tags to true)
[ ] Align changed/created by/on of tag with user also

[ ] Jumps:

[ ] Jump from Tag to User list
[ ] Jump from Tag to Session list
[ ] Jump from User to Tag list
[ ] Jump from User to Session list

[ ] Tag Create/Update pop-up

Add a drop down list Status to change the status of the Tag (values: Active, Inactive)
[ ] Create/Update Site: Select Company but only with issuer = true
[ ] Create/Update Site Area: Select Site but only with issuer = true

Ok


[HTM-645] Redesign persistence layer

Please read design document first! https://b3partners.atlassian.net/wiki/spaces/HT/pages/328073223/Herbouw+Tailormap+admin

merging so we can benefit from set-up CI


Minimal server for inputs only

Hello,
I think this product is amazing and I'm quite impressed that it works this well. I've been fiddling with low-level inputs using the shell sendevent, but as others have pointed out, this is very slow due to needing to create a java runtime environment for each command.
I find myself unable to disentangle the codebase for scrcpy to make a simple adb implementation of injecting InputEvents to the android device.
Could you help me get started with what steps I need to do.
I imagine that I will need to set up a server-client socket and send events from client to server to instruct on input events to inject. But even where to start, what packages to import, how to use the hidden API for the interface etc.
Any help is appreciated.

Could you help me get started with what steps I need to do.

I guess you already read this comment: https://github.com/Genymobile/scrcpy/issues/231#issuecomment-414111753
The client just serializes an event (in some format) and send it to the server. The server receives the event and injects it to the device.

Hello,
I think this product is amazing and I'm quite impressed that it works this well. I've been fiddling with low-level inputs using the shell sendevent, but as others have pointed out, this is very slow due to needing to create a java runtime environment for each command.
I find myself unable to disentangle the codebase for scrcpy to make a simple adb implementation of injecting InputEvents to the android device.
Could you help me get started with what steps I need to do.
I imagine that I will need to set up a server-client socket and send events from client to server to instruct on input events to inject. But even where to start, what packages to import, how to use the hidden API for the interface etc.
Any help is appreciated.

I'd be interested to hear if you made any progress with this please as I too am looking to do something similar.

A small amount, I have a very simple code snippet for event injections, but I want to take a device screenshot and am stumbling how to do this from an app_process with no android context.
Here is the code snippet that is simple enough for myself to understand :p
public class InjectEvent {
    private static InputManager im;
    private static final String GET_INSTANCE = "getInstance";
    private static final String INJECT_INPUT_EVENT = "injectInputEvent";
    private static Method injectInputEventMethod;

    static{
        try {
            im = (InputManager) InputManager.class.getDeclaredMethod(GET_INSTANCE, new Class[0])
                    .invoke(null, new Object[0]);
            injectInputEventMethod = InputManager.class.getMethod(
                    INJECT_INPUT_EVENT, new Class[]{InputEvent.class, int.class});
        } catch(Exception e){System.out.println("Failed to create wrapper");}
    }
    public static void injectInputEvent (InputEvent event, int sync)
            throws IllegalAccessException, InvocationTargetException{
        injectInputEventMethod.invoke(im, new Object[]{event, sync});
    }
}

What the static block does is get an instance of InputManager using reflection, and it gets the inject event method using reflection, and the injectInputEvent method invokes the method.
All of this was inspired/deduced or straight up copied from scrcpy. Just stripped of every piece of the puzzle that might not be necessary for input injections.


Error when adding maps from commons with long title / desc

E, [2016-02-09T15:22:03.969891 #27356] ERROR -- : PG::StringDataRightTruncation: ERROR:  value too long for type character varying(255)
: INSERT INTO "maps" ("created_at", "description", "image_url", "import_id", "map_type", "mask_status", "owner_id", "page_id", "rough_state", "source_uri", "status", "title", "unique_id", "updated_at") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14) RETURNING "id"
When importing https://commons.wikimedia.org/wiki/Category:Old_maps_of_Helsinki
74 maps, some of which have long titles (larger than 255 characters)
E, [2016-02-09T15:22:03.970701 #27356] ERROR -- : Error with import #<ActiveRecord::StatementInvalid: PG::StringDataRightTruncation: ERROR:  value too long for type character varying(255)
: INSERT INTO "maps" ("created_at", "description", "image_url", "import_id", "map_type", "mask_status", "owner_id", "page_id", "rough_state", "source_uri", "status", "title", "unique_id", "updated_at") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14) RETURNING "id">
E, [2016-02-09T15:22:03.970818 #27356]

https://www.mediawiki.org/wiki/Page_title_size_limitations
So the title should fit within a postgres varchar /ruby string but it's when we calculate the image url and store this that we are seeing problems.

Would need to change image_url only I think from string to text

I've copied one of the helsinki maps to beta commons: http://commons.wikimedia.beta.wmflabs.org/wiki/File:Plan_Charta_öfver_Helsingfors_Stad_Utvisande_så_väl_dess_ännu_varande_gamla_och_och_Qvarter_och_Gator_som_äfven_den_nya_af_Hans_Kejserliga_Majestät_i_Nåder_approberade_Reglering_2.jpeg
and this causes the error
PG::StringDataRightTruncation: ERROR: value too long for type character varying(255) : INSERT INTO "maps" ("created_at", "description", "height", "image_url", "map_type", "mask_status", "owner_id", "page_id", "rough_state", "source_uri", "status", "title", "unique_id", "updated_at", "upload_content_type", "upload_file_name", "upload_file_size", "width") VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18) RETURNING "id"
Extracted source (around line #94):
respond_to do |format|
  if @map.save
    flash[:notice] = 'Map was successfully created.'
    format.html { redirect_to<EMAIL_ADDRESS>}
  else

This should be fixed in commit 100644


Missing push error message.

5f70bf18a086: Pushed
30170ad1cf54: Pushed
b57dae4cd99e: Pushing [==================================================>]  34.36MB
c494be6f7d61: Pushed
cdd7c7392317: Pushing [=================================================> ]  77.21MB/77.81MB
error parsing HTTP 416 response body: no error details found in HTTP response body: "{}"

Sometimes the worker would unexpectedly return a 416 error when pushing images.

Is this a production worker or being run in wrangler?
Does this always happen with the same image (or of similar characteristics) or have you observed this happening with more?

This is in a production worker environment. And it will happen unexpectedly with different images.
When it shows up every time, it will be created one or more incomplete Ongoing Multipart Upload Objects on R2.
Then the object is not available to continue uploading by re-run the push command instead will upload another object to complete all the image layers.

Thanks! I will take a look and see if I can repro locally

Maybe we made some wrong assumption about docker push here.
Does this help as an env variable in the meantime?
PUSH_COMPATIBILITY_MODE=full

You can also check the state of the upload in the UPLOADS kv.
You can search the ID in the R2 bucket. Any ongoing upload in the R2 bucket is the one that failed, if we take that ID and search for it in the KV we could retrieve the upload state.

Maybe we made some wrong assumption about docker push here. Does this help as an env variable in your worker?
PUSH_COMPATIBILITY_MODE=full

What is printed in your client with:
docker version

This is my docker version
Client:
 Cloud integration: v1.0.35-desktop+001
 Version:           24.0.5
 API version:       1.43
 Go version:        go1.20.6
 Git commit:        ced0996
 Built:             Fri Jul 21 20:36:24 2023
 OS/Arch:           windows/amd64
 Context:           default

Server: Docker Desktop 4.22.1 (118664)
 Engine:
  Version:          24.0.5
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.6
  Git commit:       a61e2b4
  Built:            Fri Jul 21 20:35:45 2023
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.21
  GitCommit:        3dce8eb055cbb6872793272b4f20ed16117344f8
 runc:
  Version:          1.1.7
  GitCommit:        v1.1.7-0-g860f061
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

I will check up with the env PUSH_COMPATIBILITY_MODE later.

You can also check the state of the upload in the UPLOADS kv. You can search the ID in the R2 bucket. Any ongoing upload in the R2 bucket is the one that failed, if we take that ID and search for it in the KV we could retrieve the upload state.

I can see the record in KV, but the retrieve process hasn't done well.

The value of the record is a jwt. If you decode it in a tool like jwt.io, what's the state that appears?

For my initial case, I have two objects are Ongoing Multipart Upload:

0969706f-013a-48fc-a405-1ee623c1e14c

{
  "uploadId": "AGhrTbnEB0AC3xYiEdqWwMvNtcnQaNFTu1r6PXjyKune1DmqnJNF28usMno_vPjvd4yNj3JgGi0sURfXY_7Ig5_sWbxf1sqxBqdKhsQoJacX47wIhuGnJQRvT97Q4Ms6MgMPGfuqoVmSEZpfommiqa_AY81uNkDNot_NY937mDPTrhbhjvRz9l9uP1zIhENKZDVZkIK0N9Mwibg1ZEmSN8GiGUfJFkkMPYTnsuKJJOoftk7p4wJjwLDuOBye2cz8peKGs2oJD_S9Aj_KMLq5bFlWavNyZNfZ3RNYO65ph2b7mu0NjSytJrBrSNwnw8mHswztg2UZATvCnyn2dBqHdRU",
  "parts": [
    {
      "partNumber": 1,
      "etag": "739350224836ba140338b0f3eb1b1452"
    }
  ],
  "registryUploadId": "0969706f-013a-48fc-a405-1ee623c1e14c",
  "byteRange": 11112020,
  "name": "cms-api",
  "chunks": [
    {
      "type": "multi-part-chunk",
      "size": 11112020,
      "uploadId": "0969706f-013a-48fc-a405-1ee623c1e14c"
    }
  ],
  "exp":<PHONE_NUMBER>,
  "iat":<PHONE_NUMBER>
}

3ee9b027-75dd-4435-9a25-38a4980312cc

{
  "uploadId": "ABwfoAMUtcdd28pbMfuAU9VVQKqPwpklt4RWK76xbOaQQNyBSNQTSmzvukigNzn_rFUR699LgTVp8fyho9mvdQHSuVaLEvE8sJjkXHcCMHNmdOHApRSZdmx7tT-wmjsZyyCc1rTPAtEx2UV2OuCIUJ3UxcdMqu0RYynYjbj1Ge05d9qYrLJHpvwYg4doy7WAYZrjbSCQe7dV_mhjJfQPQHRWFJuNblg0IVbhmfhEUP5ei4pJmBFm6cvjzsq5UWZR3806OYbYYukxPp25MCw_zvkRasLuNh2BFpnS1NUG9h1n3EEvcp7qjIE2obXbYRcOmx0apgf0lX-NtI_h1YkTJJY",
  "parts": [],
  "registryUploadId": "3ee9b027-75dd-4435-9a25-38a4980312cc",
  "byteRange": 0,
  "name": "cms-api",
  "chunks": [],
  "exp":<PHONE_NUMBER>,
  "iat":<PHONE_NUMBER>
}

I've updated with a commit in main that adds more context to the error if you want to deploy a new version in the meantime

Thanks!

Alright, I finally tested out the error msg!
5f70bf18a086: Pushed
3d6c675388d4: Pushed
818595c560de: Pushed
d25de9d69a33: Pushed
cdd7c7392317: Pushed
unknown: {"errors":[{"code":"RANGE_ERROR","message":"state eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cGxvYWRJZCI6IkFQa1FJSU9jZnF0MndzTVVfa0ZKdFJxQnpYS3hYZ1lmMzhhQTVWN05fRVNPTlBNMDhzTWdYQVU2TTliQ3ZXQ3BpeTFOQUdHdHRkaVVBZ3hjUUtFZnF1blQ3Wk9rNUY5TUVNc0ZxR19YSGlGb2RYOE1SVkdVNjZWY3BzeVNsTXRrU1k5dE9rYVJlWXl2Sk82SnRKMUd4bzR6enlITnpabms4TnJDR01RQ1o4V2NrUC1obndjYWtRTHN0MFQwbFp3eVlDbW0tY0lmdWF6RFhSX1c2TXpPOHhwVEVES21WUmQtSHF3MXhyTFUzWE5OdWhiemg5ODI2VkxKSUxMUjBhV3VFSGZoVmp4V1ZGLUJ2WkRkdGp1QlF4Z3JkbE9RMVJOTFB2YmgtNjV0WWo0TXZXdlI0elRweWs5dS1hOU9ub2hEbUtCS2ttbmx2V3NTTjlKR1BmSS1IRDQiLCJwYXJ0cyI6W10sInJlZ2lzdHJ5VXBsb2FkSWQiOiI3NmU3ODkxYy0xZjA4LTRiMDktODdkOC1jNjllZWRlZmE5YzciLCJieXRlUmFuZ2UiOjAsIm5hbWUiOiJncm91cCIsImNodW5rcyI6W10sImV4cCI6MTcwOTU4NTQxMywiaWF0IjoxNzA5NTg0MjEzfQ.sNWeXBF7fTKomNhzGzcYdziLhTe7w0gCntdRmXN67vQ is not satisfiable (upload id: 76e7891c-1f08-4b09-87d8-c69eedefa9c7)","detail":{"uploadId":"APkQIIOcfqt2wsMU_kFJtRqBzXKxXgYf38aA5V7N_ESONPM08sMgXAU6M9bCvWCpiy1NAGGttdiUAgxcQKEfqunT7ZOk5F9MEMsFqG_XHiFodX8MRVGU66VcpsySlMtkSY9tOkaReYyvJO6JtJ1Gxo4zzyHNzZnk8NrCGMQCZ8WckP-hnwcakQLst0T0lZwyYCmm-cIfuazDXR_W6MzO8xpTEDKmVRd-Hqw1xrLU3XNNuhbzh9826VLJILLR0aWuEHfhVjxWVF-BvZDdtjuBQxgrdlOQ1RNLPvbh-65tYj4MvWvR4zTpyk9u-a9OnohDmKBKkmnlvWsSN9JGPfI-HD4","parts":[],"registryUploadId":"76e7891c-1f08-4b09-87d8-c69eedefa9c7","byteRange":0,"name":"group","chunks":[],"exp":1709585413,"iat":1709584213,"string":"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1cGxvYWRJZCI6IkFQa1FJSU9jZnF0MndzTVVfa0ZKdFJxQnpYS3hYZ1lmMzhhQTVWN05fRVNPTlBNMDhzTWdYQVU2TTliQ3ZXQ3BpeTFOQUdHdHRkaVVBZ3hjUUtFZnF1blQ3Wk9rNUY5TUVNc0ZxR19YSGlGb2RYOE1SVkdVNjZWY3BzeVNsTXRrU1k5dE9rYVJlWXl2Sk82SnRKMUd4bzR6enlITnpabms4TnJDR01RQ1o4V2NrUC1obndjYWtRTHN0MFQwbFp3eVlDbW0tY0lmdWF6RFhSX1c2TXpPOHhwVEVES21WUmQtSHF3MXhyTFUzWE5OdWhiemg5ODI2VkxKSUxMUjBhV3VFSGZoVmp4V1ZGLUJ2WkRkdGp1QlF4Z3JkbE9RMVJOTFB2YmgtNjV0WWo0TXZXdlI0elRweWs5dS1hOU9ub2hEbUtCS2ttbmx2V3NTTjlKR1BmSS1IRDQiLCJwYXJ0cyI6W10sInJlZ2lzdHJ5VXBsb2FkSWQiOiI3NmU3ODkxYy0xZjA4LTRiMDktODdkOC1jNjllZWRlZmE5YzciLCJieXRlUmFuZ2UiOjAsIm5hbWUiOiJncm91cCIsImNodW5rcyI6W10sImV4cCI6MTcwOTU4NTQxMywiaWF0IjoxNzA5NTg0MjEzfQ.sNWeXBF7fTKomNhzGzcYdziLhTe7w0gCntdRmXN67vQ"}}]}

{
  "uploadId": "APkQIIOcfqt2wsMU_kFJtRqBzXKxXgYf38aA5V7N_ESONPM08sMgXAU6M9bCvWCpiy1NAGGttdiUAgxcQKEfqunT7ZOk5F9MEMsFqG_XHiFodX8MRVGU66VcpsySlMtkSY9tOkaReYyvJO6JtJ1Gxo4zzyHNzZnk8NrCGMQCZ8WckP-hnwcakQLst0T0lZwyYCmm-cIfuazDXR_W6MzO8xpTEDKmVRd-Hqw1xrLU3XNNuhbzh9826VLJILLR0aWuEHfhVjxWVF-BvZDdtjuBQxgrdlOQ1RNLPvbh-65tYj4MvWvR4zTpyk9u-a9OnohDmKBKkmnlvWsSN9JGPfI-HD4",
  "parts": [],
  "registryUploadId": "76e7891c-1f08-4b09-87d8-c69eedefa9c7",
  "byteRange": 0,
  "name": "group",
  "chunks": [],
  "exp":<PHONE_NUMBER>,
  "iat":<PHONE_NUMBER>
}

So the code is a RANGE_ERROR.

I am starting to have a good guess of what's going on then! Will provide a branch for you to try out tomorrow maybe, will see how it goes.

https://github.com/cloudflare/serverless-registry/compare/gv/r2-instead?expand=1
Could you try out this branch?

It seems the changes made other problems show up.
5f70bf18a086: Retrying in 15 seconds
b3636174f992: Retrying in 11 seconds
34aad3fbfe4f: Pushing [==================================================>]  30.12MB
1f32df1e1b28: Pushing [==================================================>]  30.12MB
cdd7c7392317: Retrying in 8 seconds

it keeps retrying to push the image layers to the server but fails.
then received unexpected HTTP status: 500 Internal Server Error

With worker logs:

Hello @keyskull, I added a change to the branch, I tested both locally and prod and the push seems to work now.
Can you try a repro?

Hello @keyskull, I added a change to the branch, I tested both locally and prod and the push seems to work now. Can you try a repro?

It looks like the issue has been resolved, I've pushed 10 times and still haven't seen the error.

@keyskull Thanks for the bug submission! We will try to merge the fix today into main.


Client Allocation Request for: Joyce Cao

Client Allocation Questions
Core Information

Name: Joyce Cao
Website / Social Media: github:acfreemanwl  ;   Slack ：caoyang
Region: Greater China Region
DataCap Requested: 512GiB
Addresses to be Notarized: f13zoirpur6earrtaad4rsn7ftr7kunc4nwcqqdha
Notary Requested: 1LISA2

@acfreemanwl Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Nice to see your application,
Do you have a website, are you a company or an individual applying for dc?

As an indivual, and I don't have any official website. I have been woking as an translator for years, lately as a freelancer. So I need some space to put  the translation materials together for reference, one day i may make them into a personal memory database in trados or memoQ to largely  improve my work efficiency; my computer gets slower and I took a lot of videos since my baby was born, so it takes a lot of space.

Could you please show me your storage example, you don't have the official website and business license, so please show me more what kind of data you need to store, thank you.

https://drive.google.com/drive/folders/1qUGZ9AWWQgO7ajt99UaoOCDrBnQZeb2q?usp=sharing
Hi, part of data samples attached, please click the link above; those materials  almost about translation and teaching.

OK, thanks for the information.
In most cases, FIL+ is for enterprises, but I personally think that there are certain storage requirements as individual users.
Therefore, we may be able to grant applications from individual users.

Looking forward to more notaries commenting on this

@jbenet @dannyob @Stebalien Anyone who can help me here? Many thanks


Keep only data for requested model year

The biggest memory hog in the built models is the timeseries data. Since the model is built for a specific year, only that year of data should be kept in all timeseries datasets.
From what I can tell, PV and wind timeseries data covers the full time range of the data accessed from renewables.ninja (2000-2016?). This should be cut to just the model year of interest, which would decrease their disk usage by a factor of 10.

I agree with you that there is something odd here. The disadvantage of your approach is that it makes running the pre-built model for another year even more difficult (or impossible). But maybe that's a disadvantage that one has to accept when using pre-built models.
As this would be a breaking change, I propose to add it with a new config flag: keep-all-ninja-data or something like that so that one can omit the new behaviour.

Well, you already can't run for another year since the demand and hydro data is only given for the year of choice. This is more about stripping out the weather data that doesn't match with the other datasets, so I don't see it as breaking...

It's breaking because I am using it. ;-) I am using it with all other data fixed to 2016.

:O
Fair enough, adding with a flag seems like a reasonable compromise.


Building from source, how to install and detect arrow and numpy libraries ?

Hi
I need some help building turbodbc from sources,  got following error running cmake, which packages need to install and environment variables set to detect properly arrow and numpy libraries ?
Ubuntu 18.4.2 LTS
git clone https://github.com/blue-yonder/turbodbc.git
git submodule init
git submodule update
cmake CMakefile.txt
Package arrow was not found in the pkg-config search path.
Perhaps you should add the directory containing arrow.pc' to the PKG_CONFIG_PATH environment variable No package 'arrow' found -- Arrow ABI version: Package arrow was not found in the pkg-config search path. Perhaps you should add the directory containing arrow.pc'
to the PKG_CONFIG_PATH environment variable
No package 'arrow' found
-- Arrow SO version:
-- Found ARROW_LIB_PATH-NOTFOUND in
-- Found the Arrow core library: ARROW_LIB_PATH-NOTFOUND
-- Found the Arrow Python library: ARROW_PYTHON_LIB_PATH-NOTFOUND
-- Boost version: 1.65.1
-- Found the following Boost libraries:
--   system
-- Detecting unixODBC library
--   Found header files at: /usr/include
--   Found library at: /usr/lib/x86_64-linux-gnu/libodbc.so
Package arrow was not found in the pkg-config search path.
Perhaps you should add the directory containing arrow.pc' to the PKG_CONFIG_PATH environment variable No package 'arrow' found -- Arrow ABI version: Package arrow was not found in the pkg-config search path. Perhaps you should add the directory containing arrow.pc'
to the PKG_CONFIG_PATH environment variable
No package 'arrow' found
-- Arrow SO version:
-- Found ARROW_LIB_PATH-NOTFOUND in
-- Found the Arrow core library: ARROW_LIB_PATH-NOTFOUND
-- Found the Arrow Python library: ARROW_PYTHON_LIB_PATH-NOTFOUND
CMake Error at cpp/turbodbc_arrow/CMakeLists.txt:15 (set_target_properties):
set_target_properties called with incorrect number of arguments.
CMake Error at cpp/turbodbc_arrow/CMakeLists.txt:17 (set_target_properties):
set_target_properties called with incorrect number of arguments.
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
ARROW_INCLUDE_DIR (ADVANCED)
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
Numpy_INCLUDE_DIR
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_numpy/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Library
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
used as include directory in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
PYTHON_LIBRARY (ADVANCED)
linked by target "turbodbc_arrow_test" in directory /home/eiomrec/turbodbc/cpp/turbodbc_arrow/Test
-- Configuring incomplete, errors occurred!
See also "/home/eiomrec/CMakeFiles/CMakeOutput.log".

@emiliocolo I've closed out my issue and added a minimum viable dockerfile setup here. Hope this helps!


autoscaling: introduce auto scaling API

What problem does this PR solve?
Solve #2621.
What is changed and how it works?
This PR is trying to implement the basic framework of auto scaling API.
Check List

Tests

Unit test

Release note

/cc @nolouch @Yisaer @howardlau1999 @HunDunDM

/merge

/merge

/merge

/merge

/merge

/merge

/merge


Fix test_cppcheck.py

Fix arguments of cppcheck test and some cppcheck warnings (version 1.87)

test me

Build Failed :confused:
https://cyberbotics2.cyberbotics.com:8443/job/Webots/629/consoleText

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

On my machine with cppcheck version 1.87 I'm getting many cppcheck warnings. They are mainly about shadows functions and variables and style warnings.
I started fixing the warnings in the src file and only it remains only these about using std built-in functions for loops:
[/home/stefi/develop/webots/src/wren/PostProcessingEffect.hpp:213]: (style) Consider using std::find_if algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Transform.hpp:63]: (style) Consider using std::transform algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Transform.hpp:75]: (style) Consider using std::transform algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/DynamicMesh.cpp:545]: (style) Consider using std::transform algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Frustum.cpp:71]: (style) Consider using std::any_of algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Frustum.cpp:80]: (style) Consider using std::any_of algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/FrameBuffer.cpp:79]: (style) Consider using std::any_of, std::all_of, std::none_of, or std::accumulate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Material.cpp:47]: (style) Consider using std::any_of, std::all_of, std::none_of, or std::accumulate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Material.cpp:98]: (style) Consider using std::any_of, std::all_of, std::none_of, or std::accumulate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Material.cpp:151]: (style) Consider using std::count_if algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/PbrMaterial.cpp:80]: (style) Consider using std::fill or std::generate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/PbrMaterial.cpp:83]: (style) Consider using std::fill or std::generate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/PhongMaterial.cpp:62]: (style) Consider using std::fill or std::generate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/PhongMaterial.cpp:65]: (style) Consider using std::fill or std::generate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Primitive.cpp:346]: (style) Consider using std::accumulate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/ShadowVolumeCaster.cpp:173] -> [/home/stefi/develop/webots/src/wren/ShadowVolumeCaster.cpp:182]: (style) Local variable normal shadows outer variable
[/home/stefi/develop/webots/src/wren/ShadowVolumeCaster.cpp:264] -> [/home/stefi/develop/webots/src/wren/ShadowVolumeCaster.cpp:274]: (style) Local variable normal shadows outer variable
[/home/stefi/develop/webots/src/wren/Skeleton.cpp:74]: (style) Consider using std::find_if algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Skeleton.cpp:85]: (style) Consider using std::accumulate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Texture.cpp:173]: (style) Consider using std::any_of algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Texture2d.cpp:57]: (style) Consider using std::count_if algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/TextureTransform.cpp:92]: (style) Consider using std::any_of algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/Transform.cpp:53]: (style) Consider using std::accumulate algorithm instead of a raw loop.
[/home/stefi/develop/webots/src/wren/StaticMesh.cpp:1528]: (style) Consider using std::count_if algorithm instead of a raw loop.

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

test me

test me

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

:+1:

What do others think about it?

I'm quite neutral with this topic. I have a small preference to use the std loops. I don't see any issue with std loops and they are now fundamentally implemented in C++. I'm also not very familiar with this, but it's not a big deal to me to adopt them, and I'm glad to learn new C++ features.

I also think they are not very simple to read, for loops it is ok, but something like this:
std::accumulate(mChildren.begin(), mChildren.end(), mChildren.size(), [](int sum, const Node *n) { return sum + n->computeChildCount(); });

Is in my point of view less readable than:
int count = mChildren.size();
for (Node *n : mChildren)
  count += n->computeChildCount();

But that's probably because we are not used to these functions.

This is what cppcheck suggests to do, but we can suppress all the stl algorithm warnings.
The first time it is necessary to read the docs to really understand  how these functions works, and then for simplicity I also used the lambda function that we never used before.
Note that these functions are very similar to the Javascript Array functions "forEach", "some", etc.

I personally agree with the comment of @DavidMansolino. The only point that would convince me to use std algorithms would be the CPU performance, but it doesn't seem obvious that the std algorithms are more performant than the loops. Do we have any hint on that?

Here is the link to an article explaining the introduction of these warnings:
http://pfultz2.com/blog/2018/11/04/stl-alogrithms/

I don't have any preferences about the two solutions.
The built-in algorithms do exactly what we want to achieve with the raw loop even if they seem to be less readable.
For me it is just important to be consistent and use the STL algorithm everywhere when possible or suppress the warnings.

I don't have any preferences about the two solutions.
The built-in algorithms do exactly what we want to achieve with the raw loop even if they seem to be less readable.
For me it is just important to be consistent and use the STL algorithm everywhere when possible or suppress the warnings.

OK, so I would tend to give priority to readability versus supposed performance. I believe that performance should be addressed if a bottleneck is identified. So, if nobody objects, I would prefer that we drop this STL algorithms warning and revert back to the more readable loops. Also, performance-wise, I believe that we have more control with loops where we could later decide to use openmp to parallelize them if needed, whereas STL algorithms don't offer this level of control and remain a black box.

test me

test me

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

test me

test me

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

Build Passed :ok_hand:
You can safely merge 'hotfix-test-cppcheck' into 'revision'.

:+1:


When i import hyperlpr3 as lpr3 something error

Traceback (most recent call last):
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\connectionpool.py", line 714, in urlopen
httplib_response = self._make_request(
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\connectionpool.py", line 466, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\connectionpool.py", line 461, in _make_request
httplib_response = conn.getresponse()
File "D:\Software\Anaconda3\envs\DL\lib\http\client.py", line 1348, in getresponse
response.begin()
File "D:\Software\Anaconda3\envs\DL\lib\http\client.py", line 316, in begin
version, status, reason = self._read_status()
File "D:\Software\Anaconda3\envs\DL\lib\http\client.py", line 285, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\adapters.py", line 486, in send
resp = conn.urlopen(
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\connectionpool.py", line 798, in urlopen
retries = retries.increment(
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\util\retry.py", line 550, in increment
raise six.reraise(type(error), error, _stacktrace)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\packages\six.py", line 769, in reraise
raise value.with_traceback(tb)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\connectionpool.py", line 714, in urlopen
httplib_response = self._make_request(
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\connectionpool.py", line 466, in _make_request
six.raise_from(e, None)
File "", line 3, in raise_from
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\urllib3\connectionpool.py", line 461, in _make_request
httplib_response = conn.getresponse()
File "D:\Software\Anaconda3\envs\DL\lib\http\client.py", line 1348, in getresponse
response.begin()
File "D:\Software\Anaconda3\envs\DL\lib\http\client.py", line 316, in begin
version, status, reason = self._read_status()
File "D:\Software\Anaconda3\envs\DL\lib\http\client.py", line 285, in _read_status
raise RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "car_rec.py", line 4, in
import hyperlpr3 as lpr3
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\hyperlpr3_init_.py", line 1, in
from .hyperlpr3 import LicensePlateCatcher
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\hyperlpr3\hyperlpr3.py", line 9, in
initialization()
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\hyperlpr3\config\configuration.py", line 62, in initialization
down_model_zip(target_url, DEFAULT_FOLDER, True)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\hyperlpr3\config\configuration.py", line 24, in down_model_zip
resp = requests.get(url, stream=True)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\api.py", line 73, in get
return request("get", url, params=params, **kwargs)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\api.py", line 59, in request
return session.request(method=method, url=url, **kwargs)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\sessions.py", line 589, in request
resp = self.send(prep, **send_kwargs)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\sessions.py", line 725, in send
history = [resp for resp in gen]
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\sessions.py", line 725, in
history = [resp for resp in gen]
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\sessions.py", line 266, in resolve_redirects
resp = self.send(
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\sessions.py", line 703, in send
r = adapter.send(request, **kwargs)
File "D:\Software\Anaconda3\envs\DL\lib\site-packages\requests\adapters.py", line 501, in send
raise ConnectionError(err, request=request)
requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

From what you're describing, it seems like unstable network issues are preventing you from downloading the necessary resources from a remote server. I'd suggest trying to:

Adjust your network and try multiple times;
Download the resource package and manually install it. Url is [http://hyperlpr.tunm.top/raw/20230229.zip](Resource URL) , unzip it and place it in the .hyperlpr3 folder in your user's root directory.

哈罗，邮件收到了，我会尽快查看，回复，谢谢！


[Firestore] Cannot read property 'DEADLINE_EXCEEDED' of undefined while processing firestore query

Describe your environment

Operating System version: mac os mojave 10.14.6 (18G3020)
Firebase SDK version: 8.11.0
Firebase Product: Firestore
Node.js version: v12.16.2
NPM version: 6.14.4

[REQUIRED] Step 3: Describe the problem
While executing a query from server side, I get this error in the catch
TypeError: Cannot read property 'DEADLINE_EXCEEDED' of undefined\n    at /.../server/node_modules/@google-cloud/firestore/build/src/util.js:125:99\n    at Array.map ()\n    at Object.isPermanentRpcError (/.../server/node_modules/@google-cloud/firestore/build/src/util.js:125:63)\n    at Firestore._retry (/.../server/node_modules/@google-cloud/firestore/build/src/index.js:828:28)\n    at runMicrotasks ()\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)
Relevant Code:

 const r = firestore.collection('acollection');

        r
            .where('somefield', '=', somevalue)
            .where('timestampfield', '>=', unixformattimestamp)
            .get().catch()

my timestamp format is maybe incorrect, but the error reported is not appropriate
I cannot reproduce the issue is I remove the second where condition

setting a composite index fixes the issue, however the error reported is misleading.

@ad34 Sorry for not looking at this much earlier.
I suspect that you are getting the error because the version of google-gax you are using does not export the Status enum. This was added in v1.13.0 of Google Gax, which this library now depends on. Can you confirm what version of google-gax you have installed?

@schmidt-sebastian  thanks, you are right, forcing the dependency to 1.13 like this solved the issue
"resolutions": {
"**/google-gax": "1.13.0"
}
the message is clear now :
9 FAILED_PRECONDITION: The query requires an index. You can create it here: https://console.firebase.google.com/v1/r/project/xxxxx/firestore/indexes?create_comp

I saw this error while trying to run the firebase emulator to test functions. Turns out I had used a mix of yarn and npm to install dependencies. Cleaning out node_modules, removing lock files, and then re-installing with only either yarn or npm helped


gcsfs returns wrong number of rows

When reading a file with gcsfs (through pandas but that's not a factor here) I get a wrong number of rows.
To reproduce:

Download https://drive.google.com/file/d/1X306FSCUE5dQyC9sOihc0P-yrelEMEtH/view?usp=sharing
Put on a GCS filesystem
Open the file:

import gcsfs
import pandas as pd
fs = gcsfs.GCSFileSystem()
filepath_or_buffer = fs.open("gs://your/bucket/weird.tsv", "r")
gcsfs_ = pd.read_csv(filepath_or_buffer, sep="\t", header=None)
gcsfs_.shape

Returns
(3408, 32)

Now, if you read with the tensorflow api:
from tensorflow.python.lib.io import file_io
with file_io.FileIO("gs://your/bucket/weird.tsv", "r") as f:
    df = pd.read_csv(f, sep="\t", header=None)
    df.shape

The shape is correct:
(2869, 32)

It's also correct if you open the file from your local filesystem. I even did a character count, and the file read through gcsfs returns a wrong number of \n characters.
I can post more details here, if needed.
Versions:
In [2]: import sys

In [3]: sys.version
Out[3]: '3.6.9 |Anaconda, Inc.| (default, Jul 30 2019, 19:07:31) \n[GCC 7.3.0]'

In [4]: import gcsfs

In [5]: gcsfs.__version__
Out[5]: '0.3.0'

In [6]: import pandas as pd
p
In [7]: pd.__version__
Out[7]: '0.25.0'

In [8]: import tensorflow as tf
tf._
In [9]: tf.__version__
Out[9]: '1.12.0'

In [10]: sys.platform
Out[10]: 'linux'

In [11]: import platform

In [12]: platform.platform()
Out[12]: 'Linux-4.9.0-8-amd64-x86_64-with-debian-9.9'

Please try with fsspec most recent release or with master?

Please wait for the fix to be merged, and the following release of fsspec...


Support for response_body option of gRPC-JSON transcoding #4172

Motivation:
Sometime we need the top-level json array in request body instead of json object. And in https://github.com/googleapis/googleapis/blob/36e9ea95c12129db02c218b36f2e34a56b14d159/google/api/http.proto#L360 it already defines request_body field that support extracting top-level message.
Modifications:

passing a Function<HttpData, HttpData> responseBodyConverter to frameAndServe
and using it in singleSubscriber.

Result:

Closes #4132

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: natsumehu:x: huguanghuguang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@ikhoon I think it's ready for review

@ikhoon @jrhee17 I thinks it's ready for another round.

@ikhoon  I thinks it's ready for another round.

Thanks a lot, @natsumehu 🙇


Missing LICENSE

If possible could you decide on a license type and add a LICENSE file? I'd love to use this in a project but I require an explicit published license to do so. Thanks!

Hi, i just added a MIT license.
thanx

@sebest Thanks so much!

Thanks for adding a license. Now we can use your package!

You said "MIT" here in the comments, but committed Mozilla Public License Version 2.0. Was this intentional?

@webRat I copied the wrong file, i just fixed it. Thanx for noticing.


[bug] Next Starter Vercel Deploy button doesn't work

This issue has been present for a bit now just reconfirmed:

I've been able to mitigate by cloning the monorepo and then setting the following:

Note any attempt to set the directory different I was seeing issues with, as well as not manually specifying Next as the framework. 🤔
The button should be removed ASAP if this can't be resolved to avoid causing pain to new devs attempting to try out tamagui and getting a sour taste in their mouth.

Good catch removed for now


How to disable multiline for class atrributes?

I really like this formatter, but its kind of a pain for me when class names are broken into their own lines, especially tailwind css classes as in the picture, is there a way to disable and enable this feature
such that classes are aligned like this?

@CRIMSON-CORP did you figure out how to fix this?

@CRIMSON-CORP did you figure out how to fix this?

No, i went to use another formatter, i didn't see anyone having my issue in all the list of issues, i thought that was the way the package was, so i discarded it
I think I'll reopen the issue

@corepilotcloud @CRIMSON-CORP I'm working on taking the list of TW classes from somewhere in the right order, but maybe in the meantime I'll just add an option to keep multiple classes on the same line until we reach the max line width boundary, would that help?

Yes that would be awesome 🔥, well done ✅

i would love for this to not happen as well! appreciate it!

Finally fixed in #33! I'm about to publish a new minor 🙌


How to start the demo? I click contact device no effect.

Clicking "Connect device" should open your browser's USB device selection prompt. If nothing happens, your browser either doesn't support WebUSB (only modern versions of Chromium do) or it doesn't work correctly on your platform (which might be possible if you're using Chromium on old versions of Android). It might also be caused by a modified version of Chromium that unintentionally broke WebUSB support.
Regardless of the cause, I can't do much about the issue in those cases because it's on the browser side. You can try one of the official WebUSB demos at https://webusb.github.io/arduino/demos/console/ to confirm this.


Update UI

As a ...  user/business owner
I need ...  the UI to update a recommendation
So that ...  I can change a recommendation for a specific product
Details & Assumptions:

The REST API of updating recommendations by products is fully devleoped

Acceptance Criteria:
Given the UI
When I enter the product or id including the new recommendation to the input box
Then the recommendation is updated.

This issue as well, needs to cover BDD of Updating the UI


Initial commit with code and templates

Adding templates and initial code. Templates will be enabled after merge.

Merged! Went ahead and pushed the gh-pages branch and the docs are now live for review.


api.update() causes OSError: [Errno 18] Invalid cross-device link

On Linux, /tmp might be a separate filesystem, e.g. of type tmpfs
$ df /tmp/
Filesystem     1K-blocks  Used Available Use% Mounted on
tmpfs           16286060 92280  16193780   1% /tmp

This causes an error with os.rename() as rename is not allowed across different filesystems.
$ python3
Python 3.12.4 (main, Jul 15 2024, 12:17:32) [GCC 13.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import olman_client.api as o
>>> o.update()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/tp/projects/o/olman.git/.venv/lib/python3.12/site-packages/olman_client/api.py", line 10, in update
    return remote_index.update(force=force)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/tp/projects/o/olman.git/.venv/lib/python3.12/site-packages/olman_client/internal/remote_index.py", line 58, in update
    _download()
  File "/home/tp/projects/o/olman.git/.venv/lib/python3.12/site-packages/olman_client/internal/remote_index.py", line 27, in _download
    downloadFile(
  File "/home/tp/projects/o/olman.git/.venv/lib/python3.12/site-packages/olman_vcs_utils/vcs_utils.py", line 91, in downloadFile
    dst = tmp_path.rename(dst)
          ^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/pathlib.py", line 1365, in rename
    os.rename(self, target)
OSError: [Errno 18] Invalid cross-device link: '/tmp/tmpcz4wvnae' -> '/home/tp/.local/share/olman/remote_index.json'
>>>

With dst being the Path() of the target file, something like
tf = NamedTemporaryFile(dir = dst.parent, prefix=dst.stem + ".", suffix=dst.suffix)
tmp_path, response = urlretrieve(url=url, filename=tf.name)

should be safe as it will always store the temp file in the same folder.


Tidy go.sum

Results of running go mod tidy
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

Codecov Report

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

@@            Coverage Diff             @@
##           master   #10677      +/-   ##
==========================================
- Coverage   43.59%   43.58%   -0.02%
==========================================
  Files         589      589
  Lines       82561    82561
==========================================
- Hits        35996    35986      -10
- Misses      42104    42111       +7
- Partials     4461     4464       +3

Impacted Files
Coverage Δ

models/repo_mirror.go
2.12% <0%> (-10.64%)
:arrow_down:

services/pull/check.go
50.6% <0%> (-3.66%)
:arrow_down:

modules/git/command.go
86.95% <0%> (-2.61%)
:arrow_down:

modules/queue/unique_queue_disk_channel.go
53.84% <0%> (-1.93%)
:arrow_down:

services/pull/pull.go
34.7% <0%> (-1.18%)
:arrow_down:

services/mirror/mirror.go
18.75% <0%> (-0.66%)
:arrow_down:

models/error.go
28.71% <0%> (-0.52%)
:arrow_down:

models/gpg_key.go
53.95% <0%> (+0.52%)
:arrow_up:

routers/repo/view.go
36.82% <0%> (+0.67%)
:arrow_up:

models/unit.go
39.5% <0%> (+2.46%)
:arrow_up:

... and 2 more

Continue to review full report at Codecov.

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


⚠ Spryr has degraded performance

In 0bc25a1, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3727 ms

Resolved: Spryr performance has improved in 83bf3be after 16 minutes.


Add VALARM to birthday events to trigger a reminder at midnight

You can now configure the time of date you want to receive a reminder (set environment variable BIRTHDAY_REMINDER_AT_HOUR=9 to get a reminder at 9am.)

I hope the x-wr-alarmuiis not required

Thanks @rluetzner for adding a remind feature!


try explicit non-utf8 encoding

Re-run this please

Hmm, not sure what's going on here. The .cpg file says it's in UTF-8 and QGIS can open the file just fine.

I couldn't figure it out either.

Stale


Test CI [do not merge]

Jenkins, retest this please

Jenkins, retest this please

Jenkins, retest this please

Test jenkins


Continuous build system

As with many other large software projects, it is imperative to have a stable and functional continuous build system to facilitate a better collaboration between the contributors.

Let's clarify the problems that we're facing without a CI system so far. This might be obvious but let's ensure that we are all on the same page.
The first and foremost, there is no automatic way to verify that every pull request will not cause a regression. With a CI system that integrates with GitHub pull request workflow, a build can be produced for each feature branch and the test suite against that build can be executed automatically.
Binary package is done manually by some of us, PhantomJS contributors. This means that the packager builds the binaries for Windows/Linux/OS X on their own machine. The packager becomes the bottleneck every time there has to be a new release. On top of that, this does not permit a binary build for any development versions, whether it is for every commit or for milestone releases (alpha, beta, preview, etc).

Now, how about some challenges?
Challenge 1: PhantomJS code base is huge and it takes a lot of time to build. Since there are tons of object files, 4 GB RAM is also required for the linker to produce the final executable. Hence, the build process must run on a beefy system because we can't wait forever until the build finishes.
Challenge 2: Since we want to treat every OS equally (no second-class citizen), the build system needs to facilitate producing the build and running the test suite for all supported platforms (Windows, OS X, Linux).
(Of course, there are also the following bits not necessarily specific to PhantomJS)
Challenge 3: The cost for running it should be zero (ideally) or very low (realistically).
Technically speaking, this limitation can be alleviated if there is an entity that is willing to cover the cost (without asking for anything in return). Even more awesome if there is a capable hosted CI system that will waive the cost.
Challenge 4: The build system should require zero (ideally) or minimal (realistically) maintenance effort.
This is quite hard to overcome. Every PhantomJS contributor rather focuses on developing PhantomJS than babysitting the build system. It is thus not likely to be negotiate-able (we can't magically "create" time for additional maintenance work).

Can't you install and use Jenkins on AWS?
In theory it is possible. In practice, someone needs to volunteer their time to do that (see also Challenge 4 described above).
Beside, Jenkins still needs a build slave to operate and that requires time, effort, and money (see Challenge 3).

Can't you use Travis CI?
This has been attempted before. The problem is that Travis CI build machine has limited resources and therefore the compilation will fail at some point because it exhausts all the available the memory.
Beside, Travis CI does not offer Windows build.

Can't you use CircleCI?
According to https://circleci.com/pricing, the free tier of CircleCI only offers 1,500 build minutes per month. See also #13721.
Beside, CircleCI does not provide Windows or OS X build.

Can't you use HostedCI?
Already signed up for the "free" plan, https://hosted-ci.com/plan/free, and still not heard from them. There is also a limitation of 20 hours build time per month for this plan.
Beside, HostedCI only offers OS X build.

Can't you use AppVeyor?
According to http://www.appveyor.com/pricing, there is a build time limitation of 30 minutes per run. This is likely insufficient for PhantomJS.
Beside, AppVeyor is only for building on Windows.

Half-baked idea: The builds would be much cheaper, and therefore we would have more options, if we didn't have to build qtwebkit on every single iteration.  I wonder how difficult it would be to arrange to build qtbase and qtwebkit separately from the core pjs code, then pull in pre-baked libraries for most changes.

@zackw I think eventually we have to migrate to the modular approach in the near future. Yet, hopefully there is still a suitable solution for the current situation.

Can't you use Snap CI?
From a quick attempt, Snap CI build setup is limited to 2 GB RAM. Eventually, the build fails.
Beside, Snap CI provides only Linux build.

Currently I'm exploring Semaphore (https://semaphoreci.com/) and it seems to be promising.
Its build machine is, as promised, quite mighty: lots of RAM and CPU power. I'm sure it's still somehow virtualized, yet lscpu reports 8 available cores. Running the full PhantomJS build takes about 15 minutes, pretty impressive for a hosted CI system.
Since the host system is Linux 64-bit only, this is hardly useful to run the full build of all PhantomJS supported platforms. However, it should be sufficient as a mechanism to verify a pull request (build + run tests), consider its fast build time.
Although the wordings are a bit ambiguous, https://semaphoreci.com/blog/2014/08/14/semaphore-gets-free.html mentions that FOSS project gets only 100 builds per month. I think this should be sufficient given the current rate of our pull request.

@ariya To address the ambiguity, Semaphore offers up to 100 free builds for private projects and unlimited builds for open source projects.
I'm a Semaphore engineer so feel free to get in touch if you need any help. PhantomJS is very popular on Semaphore so we would be more than happy to help. Cheers.

Thanks for the clarifications @strika! I'll keep everyone posted with my experiment and perhaps I will reach out if I need some more help.

@ariya how did you achieve 15 minutes? Mine is killed after 1 hour: https://semaphoreci.com/vanuan/phantomjs/branches/master/builds/3

openssl + icu build takes 15 minutes.

Ok, build succeeds, but it picks up shared libraries for some reason. Probably, pkg-config returns shared library options.

What is your build machine setup?

I used Ubuntu 14.04 LTS v1512 (beta with Docker support) as a platform in settings

What is your build machine setup?

I used Ubuntu 14.04 LTS v1512 (beta with Docker support) as a platform in settings

@ariya You have some vaguely similar needs to Homebrew here (we also have automatic phantomjs builds). The only real option we've found for long-running builds is having dedicated bare metal machines (or beefy VMs) donated by someone or, in our case, bought through a Kickstarter. Feel free to mail me directly if you'd like to talk any more about this.

(we also have automatic phantomjs builds)

Did you mean brew builds?

Did you mean brew builds?

Yes. It involves building PhantomJS from source across three OS X versions so is comparable to doing the same on Windows/Mac/Linux, I think.

Ah, got it. So you prepare phantomjs brew packages by building from source.
Sadly, nobody's preparing deb and rpm packages for different distributions.

Ah, got it. So you prepare phantomjs brew packages by building from source.
Sadly, nobody's preparing deb and rpm packages for different Linux distributions.

@Vanuan The OpenSUSE Build Service is a bit unwieldy but, in my past life doing cross-platform Qt development, was the tool I found best for this.
I'm sure this is well known but the main source of your troubles here is the Qt build; if you can use an unpatched Qt version and link against it dynamically then the distros will do the legwork for you and Travis CI and friends suddenly become a lot more useful. That may end up being less work than managing your own CI/build infrastructure.

The only real option we've found for long-running builds...

I remember reading an article on how this was setup for Homebrew. I think the difference here is that Homebrew builds thousands of packages, hence the effort is amortized over time. In our case, it would be ideal if we don't spend too much time for the setup and the maintenance.

I'm sure this is well known but the main source of your troubles here is the Qt build...

Yes, this is well known. I explained how we end up going that path already: https://groups.google.com/forum/#!topic/phantomjs/r0hPOmnCUpc.
Using upstream Qt warrants a separate discussion, but frankly looking at the current state of affair with Qt 5.x and its QtWebKit module, I doubt that it's going to be promising.

I remember reading an article on how this was setup for Homebrew. I think the difference here is that Homebrew builds thousands of packages, hence the effort is amortized over time. In our case, it would be ideal if we don't spend too much time for the setup and the maintenance.

Agreed; even for Homebrew it's time that takes away from development and I'd rather we didn't spend. Unfortunately though from my personal research/experience given the requirements you have it's pretty much the only option. Your best bet might be trying to convince sponsors to run those machines for you as part of their infrastructure.

Yes, this is well known. I explained how we end up going that path already: https://groups.google.com/forum/#!topic/phantomjs/r0hPOmnCUpc.
Using upstream Qt warrants a separate discussion, but frankly looking at the current state of affair with Qt 5.x and its QtWebKit module, I doubt that it's going to be promising.

Sure, I understand the logic behind it. I think it's related to this discussion because a dynamically linked Qt suddenly solves a lot of your CI problems. That's just my opinion, though, so I'll drop it for now.

You could also setup Buildbot on a custom server, add some docker slaves for building and reuse some of the scripts from Chromium/Webkit/Mozilla to save time.

Hi! I'm working on the Semaphore platform. The current plan is to double the number of cores available in the Docker enabled platform, starting from the next platform update, scheduled for Tuesday (19.02.2016). I hope this will have a positive effect on your project. Let me know if there's anything else I can help you with.

@ervinb Sounds awesome! I hope it will be enough to have a build in less than an hour.

Semaphore is a very good service.
Mozilla has published an interesting description of their build farm:
http://taras.glek.net/blog/2014/05/09/how-amazon-ec2-got-15x-cheaper-in-6-months/
They say that it costs them $0.035 / hour.
Now of course this is not free. It will be necessary to raise funding for the farm.
It seems that this can be done pretty well on https://salt.bountysource.com

Hi @ervinb, thanks for chiming in!
Just to clarify: currently we can't use Semaphore for this purpose unless it allows building for OS X and Windows as well. However, we plan to use Semaphore for a subset of the task, i.e. building and testing a feature branch in a pull request, see #13850 for the details. For this particular task, we don't need Docker support as we can run in the bare system just fine.

@jakoch @vassilevsky Thanks for the suggestions. But keep in mind that the whole point of this investigation is to find out a ready-to-use system that we can use right away. Yes, we can setup Bamboo/Jenkins/TeamCity/what-have-you ourselves, but that is the main goal here. See again four challenges I've mentioned earlier.

Your best bet might be trying to convince sponsors to run those machines for you as part of their infrastructure.

In fact, I won't object to that idea! Even if it costs money, it is better to spend that money to fund an entity that is specialized in the field rather than us spending our time/effort doing tasks not directly related to the development.

For this particular task, we don't need Docker support as we can run in the bare system just fine.

But we need it to provide pre-release static binaries

But we need it to provide pre-release static binaries

Unless every binary is available for all platforms, I won't support that idea. Otherwise, we'll get another mob attack just like the current situation.

We'll settle with CircleCi for the minimum build for now. Once we revive the development (see #15344), we'll revisit more CI systems for macOS and Windows. Thank you!


npm create vite@latest my-app -- --template vue-ts IS BROKEN

Describe the bug
when i do a fresh run of
npm create vite@latest my-app -- --template vue-ts

i get the result with a package.json with a build command like:
...
"scripts": {
    "dev": "vite",
    "build": "vue-tsc -b && vite build",
    "preview": "vite preview"
  },
  "dependencies": {
    "vue": "^3.5.13"
  },
  "devDependencies": {
    "@vitejs/plugin-vue": "^5.2.1",
    "typescript": "~5.7.2",
    "vite": "^6.0.1",
    "vue-tsc": "^2.1.10"
  }
...

which results in:
> vue-tsc -b && vite build

/Users/rex-fab-alt/Documents/code/squirlgame/node_modules/vue-tsc/index.js:34
            throw err;
            ^
Search string not found: "/supportedTSExtensions = .*(?=;)/"
(Use `node --trace-uncaught ...` to show where the exception was thrown)

related to:
https://github.com/vuejs/language-tools/issues/5018
Reproduction
https://stackblitz.com/edit/vitejs-vite-hz7bbd?file=package.json,src%2Fmain.ts,src%2FApp.vue,src%2Fcomponents%2FHelloWorld.vue,tsconfig.json,tsconfig.app.json,tsconfig.node.json,index.html,src%2Fassets%2Fvue.svg&terminal=dev
Steps to reproduce
npm create vite@latest my-app -- --template vue-ts
cd my-app && npm i
npm run build

System Info
System:
    OS: macOS 15.0.1
    CPU: (11) arm64 Apple M3 Pro
    Memory: 264.75 MB / 36.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
  Browsers:
    Chrome: 131.0.6778.86
    Safari: 18.0.1
  npmPackages:
    @vitejs/plugin-vue: ^5.2.1 => 5.2.1
    vite: ^6.0.1 => 6.0.1

Used Package Manager
npm
Logs
could be resolved by fixing this dependencies in the starter script so it's not broken after create:
"typescript": "5.6.2",
"vue-tsc": "2.0.29"
or remove the vue-tsc from the build command will also builds ... but not sure if this is a good solution
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I did not manage to reproduce this. The current vue-ts template should pin the TypeScript version to "~5.6.2" (this is what I'm getting when executing  npm create vite@latest my-app -- --template vue-ts).
probably related to https://github.com/vitejs/vite/issues/18402 (that was fixed 🤔)

Yeah I believe this is already fixed by default. I can't reproduce it either. Make sure you're not updating the template's TypeScript version to 5.7 which would fail. It's not updated by default in create-vite's CLI.

@bluwy @pguilbert  thanks! today with a fresh run i get the same fixed version of ts and it works. strange. thanks for helping so quickly!


Directories can be dragged to one file share snapshot editor

Storage Explorer Version: 1.1.0
Platform: All
Architecture: ia32/x64
Build Number: 20180529.3
Commit: 1b431f90
Regression From: Not a regression
Steps to Reproduce:

Launch Storage Explorer and expand Storage Account.

Open one file share and create a snapshot for it.

Go to the created snapshot editor then drag directories to it.

Expected Experience:
The directory can't be dragged to the snapshot editor.
Actual Experience:
The directory can be dragged to the snapshot editor.
More info:

This issue doesn't reproduce when dragging files to the snapshot editor.
The uploaded directory doesn't display on the snapshot editor after refreshing.

@v-xuanzh Please provide more info. This sounds like expected behavior. Creating a snapshot doesn't change the state of the share or the view. It just creates a checkpoint of sorts you can return to later. The share is still just as editable as before.

Hi Craig,
For this issue, The below notification pops up when dragging files to one snapshot editor.

But the dragged directory will display well in the snapshot editor and no notification pops up like the post screenshot.

In addition, the dragged directory displays in the Current file share after backing to Current from the comb box.

OK, so you were just missing a repro step. You didn't say that you switched to a snapshot view.
What happens when you refresh?

The uploaded directory doesn't display in the snapshot view but displays in Current file share editor after refreshing.

Similar to #411

Verified this issue on the latest build 20190614.7. It still reproduces.

This issue is fixed on build master 20200509.2.
The info bar prompts when trying to drag directories to file share snapshots view.

So we close it.


Removes most references to getenvoy

Commit Message: Removes most references to getenvoy
Additional Description:
This removes the website links of getenvoy for everything except system
packages which #16867 will solve.
It also removes the section about nightlies as I don't think they are being
maintained and certainly won't be moving forward.
Risk Level: Low
Testing: None
Docs Changes: Only Docs
Release Notes: No
Platform Specific Features: No

@phlax once #16866 is also solved, there should be no confusion left around getenvoy especially as I'll be following up to change the website and remove content except CLI usage.

@codefromthecrypt can we keep this as is for now - im hoping we can resolve most of the issues you have posted so far fairly quickly

@phlax the main problem is people are coming to getenvoy because of these links and looking for support and we can't give it to them. So, I think it is probably better to remove the links. The ones removed here are completely redundant to upstream. Make sense?

yep, i see - let me look over this a bit further later today

I know there's often confusion, but there's basically no more work happening on these repos, and there is no plan to do anything except archive them. There is no plan for example, to migrate these redundant repos to CNCF. So, we should remove the links to the tetrate repos especially ones that cause confusion (the redundant ones)

fyi this is follow-up as we're pretty much good except getenvoy website edits after the various things I raised https://github.com/tetratelabs/getenvoy-package/issues/119
much appreciate the support @phlax!


Adding a linter to enforce a code style during PRs

We've had a couple of PRs go in today that had syntax errors. At a project this scale, we can't expect any maintainer to catch those things manually. I propose adding a linter / syntax checker that will run and enforce that code is at least proper python on every PR.
How do people feel about that?
Before this is merged, a maintainer should enable travis for this repo, enabling the checkbox for "only build if travis.yml file is present". We can then make sure this branch passes and thus proves the travis linter integration is working before merging it and enforcing it elsewhere.

i agree, definitely something useful.

you save me days of work.

Please help to review/merge code. @TheSavior


Remove version: Stackers.Stack version 3.11.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://binaries.getstack.app/builds/prod/win/x64/Stack Setup 3.11.1-x64.exe
Response status code does not indicate success: 530 ().
(Automated message - build 896)


Validate an image release

By:

Checking that the requested image is valid (i.e. has a tag)
Checking that the image exists in the repository.

Fixes #172
Fixes #232
Fixes #257

Unable to test due to repository structure. Will add tests for this after refactor.


Added Tribute page Abdul_kalam.html

Added tribute page for Dr APJ Abdul Kalam Azad .

@mrsaifullah52 Please review & merge this PR.


problems in this segmentation pipeline

i am  so sorry to bother you
i meet some probles like this,i think  this file named L1W.laz wrong, do you think?
then how can i slove it.
Traceback (most recent call last):
File "/home/keeping/下载/TreeLearn/tools/pipeline/pipeline.py", line 183, in
run_treelearn_pipeline(config, args.config)
File "/home/keeping/下载/TreeLearn/tools/pipeline/pipeline.py", line 47, in run_treelearn_pipeline
generate_tiles(config.sample_generation, config.forest_path, logger, config.save_cfg.return_type)
File "/home/keeping/下载/TreeLearn/tree_learn/util/pipeline.py", line 43, in generate_tiles
data = load_data(forest_path)
File "/home/keeping/下载/TreeLearn/tree_learn/util/data_preparation.py", line 27, in load_data
las_file = laspy.read(path)
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/lib.py", line 254, in read_las
return reader.read()
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/lasreader.py", line 126, in read
points = self.read_points(-1)
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/lasreader.py", line 107, in read_points
self.point_source.read_n_points(n), self.header.point_format
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/lasreader.py", line 75, in point_source
self._point_source = self._create_point_source(self._source)
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/lasreader.py", line 291, in _create_point_source
point_source = self._create_laz_backend(source)
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/lasreader.py", line 286, in _create_laz_backend
raise last_error
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/lasreader.py", line 274, in _create_laz_backend
reader: IPointReader = backend.create_reader(
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/_compression/backend.py", line 61, in create_reader
return self._get().create_reader(
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/_compression/lazrsbackend.py", line 50, in create_reader
return LazrsPointReader(
File "/home/keeping/anaconda3/envs/TreeLearn/lib/python3.9/site-packages/laspy/_compression/lazrsbackend.py", line 85, in init
self.decompressor = lazrs.LasZipDecompressor(
lazrs.LazrsError: IoError: failed to fill whole buffer

ok  this problem is solved.    but  cuda version how to fit?
RuntimeError: CUDA error: no kernel image is available for execution on the device
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.


Falcosidekick image 'falcosecurity/falcosidekick' published with 99.99.99 tag.

I use Renovate to maintain some Kubernetes manifests and it opened a PR for bumping the docker image version of falcosidekick from 2.27 to 99.99.99
My assumption here is that this tag was published by mistake or as part of some test run? If so can someone remove it since it can be confusing both for end-users as well as for dependency management software.
Thank you.

Hi,
Sorry for this. We recently revamped the Github Actions workflow to add signature and SBOM to all images. This "fake" version has been created to test it, we removed the artifacts in Github but forgot to remove the resulting images on Dockerhub. I don't have the right to delete tags myself on Dockerhub, I requested some help from the other maintainers.


aws-c-s3: 0.1.43 -> 0.1.46

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/aws-c-s3/versions.
meta.description for aws-c-s3 is: "C99 library implementation for communicating with the S3 service"
meta.homepage for aws-c-s3 is: "https://github.com/awslabs/aws-c-s3"
meta.changelog for aws-c-s3 is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.1.46 with grep in /nix/store/95njy76k6rdcc5zm1c3vszql4gziwa11-aws-c-s3-0.1.46
found 0.1.46 in filename of file in /nix/store/95njy76k6rdcc5zm1c3vszql4gziwa11-aws-c-s3-0.1.46

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

273 total rebuild path(s)

273 package rebuild(s)

First fifty rebuilds by attrpath
appvm
arrow-cpp
arrow-glib
aws-c-s3
aws-crt-cpp
aws-sdk-cpp
bundix
cabal2nix
cached-nix-shell
cachix
colmena
comma
common-updater-scripts
crate2nix
crystal2nix
dep2nix
dydisnix
fusionInventory
gnome.gnome-packagekit
gnome.gnome-software
gnome.simple-scan
go2nix
haskellPackages.cabal2nix-unstable
haskellPackages.cachix
haskellPackages.hercules-ci-agent
haskellPackages.hercules-ci-cli
haskellPackages.hercules-ci-cnix-expr
haskellPackages.hercules-ci-cnix-store
haskellPackages.nix-paths
haskellPackages.nvfetcher
haskellPackages.update-nix-fetchgit
hci
hercules-ci-agent
home-assistant-component-tests.environment_canada
home-manager
hydra_unstable
intensity-normalization
libnixxml
libsForQt5.discover
libsForQt5.packagekit-qt
libsForQt512.discover
libsForQt512.packagekit-qt
libsForQt514.discover
libsForQt514.packagekit-qt
libsForQt515.discover
libsForQt515.packagekit-qt
lispPackages.quicklisp-to-nix
lispPackages.quicklisp-to-nix-system-info
napari
nix

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/95njy76k6rdcc5zm1c3vszql4gziwa11-aws-c-s3-0.1.46 \
  --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 aws-c-s3 https://github.com/r-ryantm/nixpkgs/archive/354c9be184c5ccb9231d6bd8f81d421eb0b817aa.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/95njy76k6rdcc5zm1c3vszql4gziwa11-aws-c-s3-0.1.46
ls -la /nix/store/95njy76k6rdcc5zm1c3vszql4gziwa11-aws-c-s3-0.1.46/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @r-burns for testing.

@ofborg eval


[GUI] User is logged off when he changes his data

When the user himself changes his data, he is logged off and the message "No credentials found for given 'iss'" is displayed.
Is the expected behavior?
Steps to reproduce the problem:

Log in with a different user from admin
Open this user's details screen
Click save.
Open this user's details screen
Click save. The user is logged off and the message appears.

Affected Version: 0.3.0-nightly_20181010

Test OK.


Backport2.7: Show error message only if there was an error

Description
Backport of #919 to mbedtls-2.7
Status
READY

@andresag01 @sbutcher-arm plaease review

retest

retest

CI now passing.


Random IPs returned by DNS cause issue only in Debian distro

Hi @vincent99 and @ibuildthecloud,
I have launched a stack which consist of:

redis service (scale=2): <IP_ADDRESS> and <IP_ADDRESS>
debian service (scale=1)

Firstly, I loged in to the shell of debian container and issue a ping command to redis service:

root@d5a75ff509b7:/# ping -c1 redis
PING redis (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=64 time=0.046 ms
--- redis ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.046/0.046/0.046/0.000 ms
root@d5a75ff509b7:/# ping -c1 redis
PING redis (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=64 time=0.063 ms
--- redis ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.063/0.063/0.063/0.000 ms
root@d5a75ff509b7:/# ping -c1 redis
PING redis (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=64 time=0.045 ms
--- redis ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.045/0.045/0.045/0.000 ms

Theoretically, the ping command should return the IPs randomly. In this case, if the first ping return IP <IP_ADDRESS>, the second one should return another IP <IP_ADDRESS>. However, I've tried it many time but it only returned the first one.
Additionally,  I also try to ping another public domain to verify the theory. In this case, it works correctly.

root@d5a75ff509b7:/# ping -c1 haivl.com
PING haivl.com (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=61 time=193.795 ms
--- haivl.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 193.795/193.795/193.795/0.000 ms
root@d5a75ff509b7:/# ping -c1 haivl.com
PING haivl.com (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=61 time=193.762 ms
--- haivl.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 193.762/193.762/193.762/0.000 ms

I then tried another case, this time I used ubuntu as a host to issue ping command, it doesn't have any issue as above. So I think this could be a DNS problem only in debian distro.
Thanks

Works for me with debian:latest; Does your image maybe have dnsmasq or something else that's doing local caching?
ping -c1 test several times:
PING test.rancher.internal (<IP_ADDRESS>): 56 data bytes
PING test.rancher.internal (<IP_ADDRESS>): 56 data bytes
PING test.rancher.internal (<IP_ADDRESS>): 56 data bytes
PING test.rancher.internal (<IP_ADDRESS>): 56 data bytes
PING not7.rancher.internal (<IP_ADDRESS>): 56 data bytes

root@0f24785dfd11:/# dig not7

; <<>> DiG 9.9.5-9+deb8u4-Debian <<>> test
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26558
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;test.                          IN      A

;; ANSWER SECTION:
test.                   600     IN      A       <IP_ADDRESS>
test.                   600     IN      A       <IP_ADDRESS>

;; Query time: 7 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Wed Jan 13 19:17:40 UTC 2016
;; MSG SIZE  rcvd: 54

root@0f24785dfd11:/# uname -a
Linux 0f24785dfd11 3.16.0-57-generic #77~14.04.1-Ubuntu SMP Thu Dec 17 23:20:00
UTC 2015 x86_64 GNU/Linux

root@0f24785dfd11:/# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="https://bugs.debian.org/"

@CBR09 If you are still having this issue, please re-open. As @vincent99 mentioned, he didn't have any issues with debian:latest.


Update puppeteer to 13.3.1

Same process as https://github.com/RecordReplay/playwright/pull/7 :)

I like the guide!

@bhackett1024 - I tried this out on an ubuntu VM and my recording attempts failed but they also failed with the current release. Can you give it a try and let me know if it works for you?

@bhackett1024 - I tried this out on an ubuntu VM and my recording attempts failed but they also failed with the current release. Can you give it a try and let me know if it works for you?

In what way are things failing?  I just tried to create a recording of our single puppeteer example (https://github.com/RecordReplay/puppeteer-tests/blob/main/examples/whatsmyuseragent.js) and it worked fine --- I ran node whatsmyuseragent.js and then replay-recordings ls and the new recording was there.  I uploaded it as https://app.replay.io/recording/db675d7a-9a78-49d2-84c5-27698fb92f28 and that worked too, though I haven't been able to view the recording because I'm unable to login to replay.

I tried running a similar script and never completes. There's an entry in the recording log but the status is "crashed". I'm running this on an DigitalOcean Ubuntu 20 droplet. I expect there's some config I'm missing but I'm not sure what it would be.

I tried running a similar script and never completes. There's an entry in the recording log but the status is "crashed". I'm running this on an DigitalOcean Ubuntu 20 droplet. I expect there's some config I'm missing but I'm not sure what it would be.

Hmm, I'm not sure how to get the browser output from puppeteer to see where things crashed.  Can you try launching the browser directly (~/.replay/playwright/chrome-linux/chrome) with RECORD_REPLAY_VERBOSE set and visit the site you're crashing on?  The chromium browser always records everything so this should show why things are crashing.

I tried running chrome --headless but received the following error:
root@ubuntu-s-1vcpu-1gb-sfo3-01:~# ~/.replay/puppeteer/chrome-linux/chrome --headless https://example.com
[0215/233313.838411:WARNING:headless_browser_main_parts.cc(89)] Cannot create Pref Service with no user data dir.
[0215/233313.850611:ERROR:gl_implementation.cc(394)] Failed to load /root/.replay/puppeteer/chrome-linux/swiftshader/libGLESv2.so: /root/.replay/puppeteer/chrome-linux/swiftshader/libGLESv2.so: cannot open shared object file: No such file or directory

So i copied libGLESv2.so and libEGL.so from chrome-linux into a new swiftshader directory and tried again:
$ ~/.replay/puppeteer/chrome-linux/chrome --headless https://example.com
[0215/232516.800945:WARNING:headless_browser_main_parts.cc(89)] Cannot create Pref Service with no user data dir.
[0215/232516.867568:ERROR:angle_platform_impl.cc(44)] Display.cpp:840 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[0215/232516.867852:ERROR:gl_surface_egl.cc(780)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[0215/232516.867969:ERROR:gl_surface_egl.cc(1361)] eglInitialize SwiftShader failed with error EGL_NOT_INITIALIZED
[0215/232516.868077:ERROR:gl_initializer_linux_x11.cc(178)] GLSurfaceEGL::InitializeOneOff failed.
[0215/232516.884552:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[0215/232516.912646:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled

So I tried to setup Xvfb and then received:
$ ~/.replay/puppeteer/chrome-linux/chrome --headless https://example.com
[0215/233553.822703:WARNING:headless_browser_main_parts.cc(89)] Cannot create Pref Service with no user data dir.
[0215/233554.069497:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

Thanks, this stack overflow article might help with the last error: https://stackoverflow.com/questions/69037458/selenium-chromedriver-gives-initializesandbox-called-with-multiple-threads-in

I looked at that article but not sure how to apply it since it's referencing how to specify the driver for selenium which I'm not currently trying to use (at least when launching directly).
I don't want to burn too much time on this but I do think we need to understand the requirements for configuring a linux CI environment. If vanilla puppeteer didn't work, I'd assume that it was an environmental problem but since vanilla does but neither the current version nor my branch work, there must be an important step for our version that I'm missing.

I looked at that article but not sure how to apply it since it's referencing how to specify the driver for selenium which I'm not currently trying to use (at least when launching directly).
I don't want to burn too much time on this but I do think we need to understand the requirements for configuring a linux CI environment. If vanilla puppeteer didn't work, I'd assume that it was an environmental problem but since vanilla does but neither the current version nor my branch work, there must be an important step for our version that I'm missing.

OK, I should have been clearer, there are suggestions at the bottom to see if things aren't broken with --disable-gpu and --disable-software-rasterizer.
I agree we shouldn't spend a lot of time on this until we're ready to more fully support our chromium port.  We have a linux development machine (linux-development in tailscale) which is used for building browsers and is usually idle and can be used to test other stuff.  I just tried launching chrome there, and I had to create a swiftshader directory like you did, but after that I was able to get the browser to launch and make recordings (just created https://app.replay.io/recording/841f76f3-e3e9-47a4-aa0d-c4c05dd324a2):
ubuntu@ip-172-16-162-168:~/.replay/playwright/chrome-linux$ DISPLAY=:1 ~/.replay/playwright/chrome-linux/chrome www.npr.org
[2044714:2044714:0216/121310.178584:ERROR:angle_platform_impl.cc(44)] Display.cpp:840 (initialize): ANGLE Display::initialize error 12289: GLX is not present.
[2044714:2044714:0216/121310.178768:ERROR:gl_surface_egl.cc(780)] EGL Driver message (Critical) eglInitialize: GLX is not present.
[2044714:2044714:0216/121310.178846:ERROR:gl_surface_egl.cc(1361)] eglInitialize SwiftShader failed with error EGL_NOT_INITIALIZED
[2044714:2044714:0216/121310.178936:ERROR:gl_initializer_linux_x11.cc(178)] GLSurfaceEGL::InitializeOneOff failed.
[2044714:2044714:0216/121310.186019:ERROR:viz_main_impl.cc(161)] Exiting GPU process due to errors during initialization
[2044744:2044744:0216/121310.262952:ERROR:gpu_init.cc(440)] Passthrough is not supported, GL is disabled
[2044744:2044744:0216/121310.263392:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.

@bhackett1024 - I don't think the issues I'm seeing are related to this update but I'm not sure. I opened #3 to continue the investigation because I think the fix will be independent of this PR.


javadoc: fix no @param (description) for

Description of changes:
Fix a couple of javadoc warnings:
.../aws-java-nio-spi-for-s3/src/main/java/software/amazon/nio/spi/s3/S3ClientProvider.java:139: warning: no @param for <T>
    public <T extends AwsClient> T universalClient(boolean async) {
                                   ^
.../aws-java-nio-spi-for-s3/src/main/java/software/amazon/nio/spi/s3/S3FileSystemProvider.java:587: warning: no description for @param
     * @param <V>
       ^
2 warnings

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

As you have a few PRs open I will let you merge this in the order you think is best.

This one can be merged asap too👍


Alter schema structure to use a cleaner model set definition

Description
This implements the suggested change in #333, that moves a configuration having to explicitly list the modules as [core] modules = ['soil', ...] with defaults to an explicit requirement to put a (possibly minimal) configuration entry for each required module:
[core]
[soil]

Fixes #333 - see that issue for the rationale for this PR.
Type of change

[ ] New feature (non-breaking change which adds functionality)
[x] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist

[x] Make sure you've run the pre-commit checks: $ pre-commit run -a
[x] All tests pass: $ poetry run pytest

Further checks

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

@jacobcook1995 I'm not convinced by a default set of models - I think the minimum configuration should be an explicit list of the modules to be used (which is a very short TOML doc/string). Even within testing, I can't really see many circumstances where a default set of modules, as opposed to a minimal set for testing particular features, is useful.


templates(discord-bots/starter-ts): updated robo dependencies

Automated PR for... Branch: templates/discord-bots/starter-ts

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

recheck


Support for Laravel 8

Hello,
Could you add support for Laravel 8 please? Thank you!
Works like charm on my Laravel 7 project, but then, I started another project with Laravel 8 and found out that I cant install from composer :(

Added thanks

Wow thank you so much!


Add draggable handle to console to resize the height

Resolves #256
This adds a drag handle to the console and allows the user to drag it up and down to resize the height of the console.
To test:

Create a plan
Verify that the console doesn't have a draggable handle when it's closed
Expand the console
Verify that the drag handle is present and draggable
Verify that the console resizes as expected
Make note of the current size of the console and close it
Verify that reopening the console reverts to the noted size prior to closing

Seeing a lot of text highlighting when I resize – not entirely sure if there's a way to avoid this but maybe you have ideas?

Also is there any way to have some sort of max height on the console so that we avoid getting into the situation where the collapse button and drag handle are hidden by the nav (if you drag all the way up)?

@AaronPlave thanks! I was able to add preventDefault and that got rid of the highlighting. I think it's pretty safe to apply that to this component. I'm open to other solutions though.
I've also added a max height of 600, but we can maybe play with that number when we get more feedback.

@duranb Testing locally the panel does not seem to open when clicking on one of the buttons (all, scheduling errors, simulation errors)

@camargo thanks for catching that! hopefully it's fine now

Looks great! Suppose we could do something like setting max height to some percentage of window height? But 600px max isn't bad

Yeah, that's a good point. I'll see if I can come up with something really quick.

@AaronPlave @camargo now it supports percentage height limits!


What will occur if not close redis?

hi,
If I don't call close() method,will mem leak occur?

it keepalive the connection after execute command, see _do_cmd and _do_eval_cmd function.

The post above is correct, close as of now.


Package error for burn to mint [CODE-SHARE]

Closing because we're going to do burn-to-mint using pre-mint hooks instead.


Add alternative WARP download links

Microsoft AppCenter is down, so add alternative WARP download links from one.one.one.one

Not needed anymore, MS AppCenter is back up


Correct the documentation for raw pointers.

Fixed the third code example. line 37 demonstrates declaring a non-const pointer but actually declared a const pointer. Deleted 'const' keyword from line 37.

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

#label:"aq-pr-triaged"

@neonbhai
Sorry about taking so long to get back to you; I've been on vacation for the last two weeks. Thanks for taking time to work on improving the docs. Unfortunately, while I appreciate your efforts here, your change isn't correct and leads to a compiler error:
error C2440: 'initializing': cannot convert from 'const int *' to 'int *'
Pointers to int are declared like so, depending on constness and East-const or West-const preference:

int is const
Pointer is const
Declaration

No
No
int i = 42; int * p_i = &i;

No
Yes
int i = 42; int * const kp_i = &i;

Yes
No
int const ki = 42; int const * p_ki = &ki; // "East const" const int ki = 42; const int * p_ki = &ki; // "West const"

Yes
Yes
int const ki = 42; int const * const kp_ki = &ki; // "East const" const int ki = 42; const int * const kp_ki = &ki; // "West const"

I hope this illustrates why I'm closing your PR unmerged.


update QnA

Docs Build status updates of commit 05394ac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

<EMAIL_ADDRESS>:bulb:Suggestion

Details

<EMAIL_ADDRESS>
[Suggestion] Missing attribute: title. Add a title string to show in search engine results.

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


Documentation for ordered_json should show proper use of the parse() function.

https://json.nlohmann.me/features/object_order/ shows inserting objects in a particular order, but doesn't show how to properly use the parse() function to get the same result for existing JSON documents.
In particular, it needs to be this:
auto j = nlohmann::ordered_json::parse(text);

and not this:
nlohmann::ordered_json j = json::parse(text);

Can't change the labels, should be docs or enhancement or something like that.

Done: https://json.nlohmann.me/features/object_order/#notes-on-parsing