Ivan Kozlovic

@alexshpilkin The pkg-config file was added by an external contributor. Would you mind contributing at fixing this since it looks like you have a grasp on what the exact issue...

@suddas I did not run on mips64. You may get more chance to ask this question on our slack channel? Here is the link to join: https://slack.nats.io/

Not clear on what is not working: NATS Server or (config-reloader, nats-box, etc)? Because this is the repo to produce docker image of the NATS Server.

Not sure where you get that they have manifest that say that they support arm64? ``` $ docker run --rm -ti mplatform/mquery synadia/nats-box:latest Image: synadia/nats-box:latest (digest: sha256:caf0c9fe15a9a88d001c74fd9d80f7f6fd57474aa243cd63a9a086eda9e202be) * Manifest List:...

@wallyqs @variadico Not sure who creates the docker images for the aforementioned tools in the `natsio` docker repo, but the one hosted on Synadia correctly shows only support for linux/amd64...

I am trying to reproduce, same topic name and subjects spaced filled with same amount of messages and random payload up to 1Kb and then creating a durable pull consumer...

I have been checking the 100 subjects that I have (WAREHOUSE.documents.T00 to WAREHOUSE.documents.T99) randomly, and the test passes. I am running from main branch, so will now try from actual...

I have used 2.8.4 to generate the data, then run test to consume (randomly) from all subjects (in both the original version and v2.9.0), and so far no issue. Staring...

We think this is addressed with PR #3486.

@denis-tingaikin Thank you for the report and we can of course update the go.mod, but the link to the CVE shows: ``` net/http in Go before 1.16.12 and 1.17.x before...