GH-39700: [C++] Feature: use inplace_merge to replace merge.

Rationale for this change
just like https://github.com/StarRocks/starrocks/pull/14609
we can use std::inplace_merge to replace merge.
Since our indices are also a whole block of memory, after using std::inplace_merge, we can reduce the memory allocation of temp_indices and reduce std::copy operations, which has a natural advantage for us, so here I think std::inplace_merge is more suitable
What changes are included in this PR?
sort operator, vector_sort.cc
Are these changes tested?
yes, run vector_sort_test.cc
Are there any user-facing changes?
no.

Closes: #39700

I didn't review it carefully but generally this looks ok to me, I think this is because inplace_merge is introduced in C++17.
Would you mind fix the lint first?

Details
The formatting problem has been solved, thank you

Did you run some benchmarks? You can't claim something improves performance without measuring it.
std::inplace_merge does not avoid a memory allocation, it just allocates the memory implicitly. Quoting the documentation:

This function attempts to allocate a temporary buffer. If the allocation fails, the less efficient algorithm is chosen.

https://conbench.ursa.dev
It seems that the regression results of the benchmark have nothing to do with my changes.

It seems that the regression results of the benchmark have nothing to do with my changes.

That's true, but there doesn't seem to be any improvement either.
I've run the benchmarks locally and neither do I see any improvement.
We can try to reason on the code changes here:

the original code allocates the temporary buffer once at the beginning of the sort operation, and reuses it for all std::merge calls
the changed code lets std::inplace_merge allocate a new temporary buffer at each invocation

So, at least theoretically, the code in this PR is less efficient. Unless you can exhibit benchmark improvements on some configuration, I would recommend rejecting this.

Also, if you filter for chunked array sorts on https://conbench.ursa.dev/compare/runs/6961d70de8424138aaf0b77dc6cba908...d3ea371166c146d4845ac4625d70d2ad/ and https://conbench.ursa.dev/compare/runs/d0e8a5b5cde24106b3a2c60699933ea1...37da92dc9fca4e159568f2563f562a1d/, you'll see that most benchmarks show a slight performance decrease (between 0 and 10%).

Also, if you filter for chunked array sorts on https://conbench.ursa.dev/compare/runs/6961d70de8424138aaf0b77dc6cba908...d3ea371166c146d4845ac4625d70d2ad/ and https://conbench.ursa.dev/compare/runs/d0e8a5b5cde24106b3a2c60699933ea1...37da92dc9fca4e159568f2563f562a1d/, you'll see that most benchmarks show a slight performance decrease (between 0 and 10%).

Indeed....local testing is down a bit

A possible experiment would be to use three-way merging instead of two-way merging. This might increase performance as indexing a chunked array is not trivial.


PlayReady only has little-endian key IDs on Edge & IE

In addition to the tests run by our build bot on Linux, I will also run tests in our lab on IE11, Edge, and Tizen to verify this change.  I don't expect any issues, but I want to be careful.

Tests passed on IE, Edge, and Tizen, too.


Disabling auto-start/stop and the VTherm is off cause auto-start/stop

The case is the following:

put a VTherm in auto-start/stop,
wait for a stop,
disable auto-start/stop through VTherm UI Card,

What we observe: the VTherm stays OFF with reason auto-start/stop
What we want: the VTherm turns ON and restore its last state (preset, havc_mode) before it was turned off by the auto-start/stop feature.

Seems a bit similar to https://github.com/jmcollin78/versatile_thermostat/issues/653, although not exactly the same.

Hello @t0mb080 ,
It is not the same and #653 is already fixed (available in the 6.8.0.beta pre-release). This one should have its own fix

https://github.com/jmcollin78/versatile_thermostat/releases/tag/6.8.1


Allow Chai 4.0.0 as a valid peerDependency

Current trying to upgrade to Chai 4 causes the following NPM error:
npm WARN<EMAIL_ADDRESS>requires a peer of chai@>= 2.1.2 < 4 but none was installed.

Can the library be updated to allow Chai 4 as a valid peerDep?

Thanks for this @moberemk. We're currently tracking this through #157. I'll close this one for now, if you'd like to get updates on this - you should subscribe to that issue.

Ah, sorry, I missed that issue earlier--thanks for the link, will follow that issue instead.


swaybar don't show external scripts anymore

Hi,
I have an issue with showing output of external script.
when I use only i3status it work good.

bar {
status_command i3status
#status_command ~/.config/i3/i3status.bash
tray_output primary
}

but when I use external script, which is written just like mentioned here:

http://i3wm.org/i3status/manpage.html#_external_scripts_programs_with_i3status

Whole swaybar shows only unprintable chars.  In previous versions of sway it worked, now it doesn't work.
Do you know, how to fix it or do you have some recommendation for using another printer with similar settings as i3status?
Thanks

Would it be possible to post the script you are using (or a minimal example that shows the problem) then it would be easier to test.

It's not in the script. When I try the minimal script, it behaves the same way:

$ cat .config/i3/i3status.bash
#!/usr/bin/bash
# shell script to prepend i3status with more stuff

i3status | while :
do
read line
echo "$line" || exit 1
done

I think it's something about output_format.
When I run this script in terminal, it prints correctly the rows
It also prints before it:

i3status: trying to auto-detect output_format setting
i3status: falling back to "none"

The output format in i3status should be "none" when running it this way. Should auto detect if you don't set the value.
I can't replicate the issue, it looks fine when I run the minimal script you posted. What happens if you run i3status as status_command, but set output_format = "none" in the config, does that work?

Let's start by checking that you're running the latest version of sway, @podhorsky-ksj.

I just pull out the latest version of wlc and sway and build. Still the same behaviour.
But when I add to block general {} in i3status/config the

output_format = "none"

i3status (without the external script):

status_command i3status

shows the same unprintable chars.
So, somehow the bar can't  show the output formated with:

output_format = "none".

Can you share your sway log? See the FAQ

Ok here is the file:
sway.txt
Here is also script  how I run sway.
Maybe some features are obsolete, I created it when I used orbment.
sway-run.txt
And yes, I rebooted before it.
Also, when I exited sway, to get log from i3status, some segfault was occured and then process sway-msg put CPU into heavy load.
I have always enabled logging, so there is log from it. I'm not sure if it is connected with sway.
sway-segfault.txt

Could you also post the i3status config you use? I suspect it has something in it that messes up the bar, since I can't replicate the issue with my own config.

Ok, here it is:
i3status.txt

@podhorsky-ksj thanks for reporting it, I don't know why I couldn't trigger the issue without your config, but it's fixed now.

@mikkeloscar fix is ok, thanks.
A what about the segfault. Is it connected with sway?

We need you to run addr2line on the backtrace and post it, so we can get an idea of what's going on.
You can use this helper script: https://gist.github.com/mikkeloscar/badebca2b9766a067397
cat swaylog | python addr2line_sway.py /path/to/sway-binary

And please create a new issue for this.

Ok thanks. I recompiled the binary, but if the issue will occur again, this script will help.


Update tutorial-core-validators.md

The maxSize validator validates in bytes, so the example was incorrect (it was 1GB instead of 1MB).

Thanks!


about zod customize some error messages when creating a schema.

When I created zod schema, I customized some error messages for verification.
But when I tried to verify, the custom error message didn't work.
code
user.scheme.ts
const loginSchema = z.object({
  email: z
    .string()
    .email({ message: "Please enter the correct email address" }),
  password: z.string(),
});

export const { schemas: userSchemas, $ref } = buildJsonSchemas({
  ....
  loginSchema,
});

user.route.ts

async function userRoutes(server: FastifyInstance) {
  server.post(
    "/login",
    {
      schema: {
        body: $ref("loginSchema"),
        response: {
          200: $ref("loginResponseSchema"),
        },
      },
    },
    loginHandler
  );
}

app.ts

for (const schema of [...userSchemas, ...productSchemas]) {
    server.addSchema(schema);
  }

Send a request
{"email":"ad12dadasda","password":""}

response

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "body.email should match format \"email\""
}

I have the same issue and tried everything and still doesn't pick the custom error message
Did u know how to fix it?

Would be great if we get an update on this since I'm facing the same issue.

No, I used another library.   👉 fastify-type-provider-zod

R4Y-repo

No, I used another library.   👉 fastify-type-provider-zod

Hi!
Sorry for the late reply.
I have just published 1.3.2, with support for custom error messages, as well as instructions on how to enable them:

- For custom error messages, you must enable error messages when building the schemas, as well as [configuring fastify to handle them](https://www.fastify.io/docs/latest/Reference/Validation-and-Serialization/#schemaerrorformatter):
// Define custom messages
const TodoItemId = z.object({
  id: z.string().uuid("this is not a valid id!"),
});

// Then configure fastify
const f = fastify({
  ajv: {
    customOptions: {
      allErrors: true,
    },
  },
  plugins: [require("ajv-errors")],
});

await register(f, {
  jsonSchemas: buildJsonSchemas(models, { errorMessages: true }),
});

Does this solve your problem?

Hi!
Sorry for the late reply.
I have just published 1.3.2, with support for custom error messages, as well as instructions on how to enable them:

For custom error messages, you must enable error messages when building the schemas, as well as configuring fastify to handle them:

// Define custom messages
const TodoItemId = z.object({
  id: z.string().uuid("this is not a valid id!"),
});

// Then configure fastify
const f = fastify({
  ajv: {
    customOptions: {
      allErrors: true,
    },
  },
  plugins: [require("ajv-errors")],
});

await register(f, {
  jsonSchemas: buildJsonSchemas(models, { errorMessages: true }),
});

Does this solve your problem?

what would be the right code for fastify-zod with typescript?


Is Redis worker supposed to exit after completing a single job?

I've been trying to make Redis worker work with no success, unless I'm misunderstanding something. I'm using this example with my own cog image: https://github.com/replicate/cog-redis-example
I add a message to the queue, the worker picks it up. Logs shows that it processes it but then it exits with the message:
Shutting down worker: bye bye!
No error messages, just that. I'm wondering if this is the intended behaviour of a cog. I expected it to continue listening for messages but maybe I understood the worker wrong. If this is the intended behaviour, are there any ways to make it not exit after a single job completion?

When I try to use the example with this image it also quits after a single job, no reason given is to why: https://replicate.com/stability-ai/stable-diffusion/api
If I use this with this image, it doesn't quit after one job: https://replicate.com/nitrosocke/redshift-diffusion/api
I don't understand why it's quitting with one and not the other. It doesn't say why it does that, just says Shutting down worker: bye bye!


Show underlines even when first label has no message

In ariadne v0.3.0, any label would cause its span to be underlined, but also add blank lines to the output even when it had no message.
In v0.4.0, the extraneous blank lines were removed, but the behaviour regarding underlines was also changed: When the first label has no message set, no underlines at all are shown:
    const SOURCE: &str = "a b c d e f";
    // also supports labels with no messages to only emphasis on some areas
    Report::build(ReportKind::Error, (), 34)
        .with_message("Incompatible types")
        .with_label(Label::new(0..1).with_color(Color::Red))
        .with_label(
            Label::new(2..3)
                .with_color(Color::Blue)
                .with_message("`b` for banana")
                .with_order(1),
        )
        .with_label(Label::new(4..5).with_color(Color::Green))
        .with_label(
            Label::new(7..9)
                .with_color(Color::Cyan)
                .with_message("`e` for emerald"),
        )
        .finish()
        .print(Source::from(SOURCE))
        .unwrap();

(Based on examples/simple.rs without compact.)
This will show
Error: Incompatible types
   ╭─[<unknown>:?:?]
   │
 1 │ a b c d e f
   │   │     │
   │   │     ╰── `e` for emerald
   │   │
   │   ╰──────── `b` for banana
───╯

But when the first label for a has a message, all spans have underlines:
Error: Incompatible types
   ╭─[<unknown>:?:?]
   │
 1 │ a b c d e f
   │ ┬ ┬ ─  ─┬
   │ ╰────────── a
   │   │     │
   │   │     ╰── `e` for emerald
   │   │
   │   ╰──────── `b` for banana
───╯

With this PR, underlines will be shown regardless of whether the first label has a message:
Error: Incompatible types
   ╭─[<unknown>:?:?]
   │
 1 │ a b c d e f
   │ ─ ┬ ─  ─┬
   │   │     │
   │   │     ╰── `e` for emerald
   │   │
   │   ╰──────── `b` for banana
───╯

Thanks, this seems like a sensible change! I'll try to find some time to review this over the next day or two, I'm not sure I can assure myself of its correctness at just a glance.


Add tests/utils/scripts for running integration tests

Add a suite of integration tests in the test/ directory, as well as utilities for testing in the testutil/ directory.
You can use the bin/test-run script to run the full suite of tests, and the bin/test-cleanup script to cleanup after the tests.
The test README.md has more information about running tests.
@pcalcado, @franziskagoltz, and @rmars also contributed to this change. 🎉
Fixes #419.

(btw I'm generally 👍  this but wasn't able to run it on my box just yet so didnt want to click approve)

@siggy Thanks for the additional suggestions -- have updated in the latest commit. Re: docker for mac + k8s -- k8s support is only available in edge versions of docker for mac. I don't think we need to explicitly call out that we don't support an experimental environment.


JSON serialization performance

Currently, serializing and deserializing in JSON a List of DestinyHistoricalStatsPeriodGroup is quite slow using the default  IBungieNetJsonSerializer. For a list of 3000 activities, it takes around 40s to parse the json.
Is there any tips to improve performance when serializing a List of DestinyHistoricalStatsPeriodGroup into JSON (for indexedDb)?

@samuel-chp https://github.com/dotnet/runtime/issues/40386

I found an ugly workaround for now: I've selected only some properties from each DestinyHistoricalStatsPeriodGroup in the list I want to give to JS (for example, the "kills" or "assists" per game).
Then I use marshal types with the new JS interop from net7 (https://learn.microsoft.com/en-us/aspnet/core/blazor/javascript-interoperability/import-export-interop?view=aspnetcore-7.0), passing arrays of double essentially.
It's very ugly and not very handy but I went from 40s of transfer to 1.2s.

Well, I guess for now making a proper serializer for this kind of thing is impossible after all?

Try publishing with AOT enabled and see if the slowness resolves. It is a pain as the AOT compilation takes a long time, but in my application parsing a 6MB json went from around 6 seconds to almost nothing.

Well for the manifest it's manageable, I just handle the download with JS directly so that I don't have to transfer a lot of data with Blazor JS interop. It becomes annoying when I want to access a big chunk of data from indexed db multiple times and process it with blazor. The transfer times are quite long.
The AOT indeed works great. I went from 4s to 0.4s once the app is published. Yet in development it remains an issue to wait this long.

@samuel-chp you can do lazy loading on definitions, like, save them in memory for later use


Optimize BlockManager.join_on for special types

Currently using the Cython function merge_indexer_object, could be much faster with compatible types

This is addressed by the new merge infrastructure, I think. Closing the issue


Remove version: Tencent.COSBrowser version 2.11.4

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

URL: https://cos5.cloud.tencent.com/cosbrowser/cosbrowser-setup-2.11.4.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 896)


Ford Kuga loading not started after 5min. off

Describe the bug
Vehicle: Ford Kuga
Wallbox: Go-E-Charger V3
Steps to reproduce

Vehicle unplugged and locked
EVCC set to off
plugged in cable to vehicle
wait 8min.
set evcc to charge immediately
Go-E goes to green, but loading the vehicle is not starting.
When Go-E -charger is unplugge at vehicle or power, and plugged in again, charging is starting.

Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: debug
levels:
  cache: error

# unique installation id
plant: e67e6b4569d06c59a533a861c2e68b8aeac6bf9d5381941d947d84556013e555

interval: 10s # control cycle interval

sponsortoken:

# sponsors can set telemetry: true to enable anonymous data aggregation
# see https://github.com/evcc-io/evcc/discussions/4554
telemetry: true

meters:
- type: template
  template: huawei-dongle-powersensor
  id: 1
  host: <IP_ADDRESS>
  port: 502
  usage: grid
  modbus: tcpip
  name: grid1
- type: template
  template: huawei-dongle-powersensor
  id: 1
  host: <IP_ADDRESS>
  port: 502
  usage: pv
  modbus: tcpip
  name: pv2
- type: template
  template: huawei-dongle-powersensor
  id: 1
  host: <IP_ADDRESS>
  port: 502
  usage: battery
  modbus: tcpip
  name: battery3

chargers:
- type: template
  template: go-e-v3
  host: <IP_ADDRESS>
  name: wallbox4

loadpoints:
- title: Garage
  charger: wallbox4
  mode: pv
  phases: 3
  mincurrent: 6
  maxcurrent: 16
  resetOnDisconnect: false
vehicles:
- name: Ford Kuga
  type: template
  template: ford
  title: # Wird in der Benutzeroberfläche angezeigt (Optional)
  user<EMAIL_ADDRESS>  password: userpw
  vin: vim # Erforderlich, wenn mehrere Fahrzeuge des Herstellers vorhanden sind (Optional)
  capacity: 14 # Akkukapazität in kWh (Optional)
  phases: 1

site:
  title: kunde
  meters:
    grid: grid1
    pv:
    - pv2
    battery:
    - battery3

Log details
no log

What type of operating system are you running?
Linux
Version
0.120.3

Missing log

Hi, for all who have the same problem.
I found the problem already.
The problem was, that you have to set a option on the go-e-charger,  "simulate unplug and plug again" must be set on for the Ford Kuga.
This setting is in vehicle-settings directly on the go-e app avaiable.
So it has nothing todo with the evcc-software.

Das könnte einen Hinweis im GoE Template wert sein.
/cc @VolkerK62

@gereic  see https://github.com/evcc-io/evcc/issues/10301
I do not have go-e and the app, would you please add a screenshot off the vehicle-setting page to this issue


Change floating point tests to be approximate instead of exact

IEEE754 does not lead to reproducible results across platforms, so tests of numerical
routines should be whether the results lay within predetermined bounds instead of testing exact values.

I have used assert_approx_eq! for this kind of thing.

statrs has a similar function in prec.rs.
At the time of this issue the pattern was more widespread that some tests compared to exact floating point numbers, while others used absolute difference within some epsilon. I've left this issue open because we've been moving away from absolute differences to relative ones which are more insightful over different orders of magnitude. That transition has not been finished.

We already have an assert_almost_eq! macro for this.

The cleanup would be nice, also appears heavily in the docstrings. I can start chipping away at that.
here's a list of what I found on a cursory glance

function

[ ] beta
[ ] erf
[ ] evaluate
[ ] exponential
[ ] factorial
[ ] gamma
[ ] harmonic
[ ] logistic

testing_boiler

[x] in implementation of self
[ ] use boiler in distribution tests

distribution

[ ] all docstrings
whatever is remaining


MSL uses ModelicaReference

Reported by beutlich on 11 Nov 2016 13:30 UTC
Should the MSL have an uses annotation on ModelicaReference since there are modelica URIs inside MSL referring to it?

Migrated-From: https://trac.modelica.org/Modelica/ticket/2108

Question is if the URI dependency in the documentation is enough to have a uses clause. So you could argue that technically the MSL does not depend on Modelica Reference to function the documentation might be targeting some dead links. This is currently not an issue since Modelica Reference is shipped side by side with Modelica. So I like to postpone this until we have a modular version of Modelica Reference.

Not a relevant issue.


Possibilities without kubernetes alpha features?

I am using Kubernetes on GCE and the only way I can use alpha features is if I create an alpha cluster which is deleted after 30 days.
Obviously in the README it says alpha features are required. I set it up anyways but it seems unstable. Do you have any advice for running elasticsearch 5.5.* on kubernetes without kubernetes alpha features?

I think that warning is no longer valid.

I believe that the CronJob resources still require alpha features to be enabled.

Thanks, good to know. It actually seems very stable now - I think I had an unstable set of nodes for some reason.

I'm re-opening the issue because documentation should be clear about this.

Coming with k8s 1.8 the cronjob api will be moved to beta and be enabled by default, so should not be an issue for long anymore :)

Yay!


Why does watchify notify of updates to package.json?

Watchify watches package.json files and fires an update whenever they're changed.  It also puts the file package contents into a map, pkgcache, but doesn't appear to do anything with them.
A few questions:

Why is the watcher in place?  Is the idea that you could write code to dynamically run npm install on a package.json update, then rebundle?  I can see the utility of this, but there should be a README entry somewhere noting this.

What's the purpose of pckgcache?

https://github.com/substack/watchify/issues/226

https://github.com/substack/module-deps/blob/0e290c/index.js#L30

Great!  Thanks, this is helpful.


operator project-quay (3.8.0)

Add v3.8.0 to community operators

@quay-devel would be great to have a couple more sentences in the operator description (CSV).

/merge possible


console runner: changeFile

Implement the command changeFile in the console runner. Gets the path of a file, the name of a placeholder and a string that should be inserted or the path of a file with the content that should inserted. Maybe you need to use named parameters.

The second paramter is implemented as JSON object. It contains the placeholder and the content respectively the path to the file the content is get from. The placeholder parameter is optional. If no placeholder is given, all content is replaced.


Format document inserting 2 spaces instead of 4

Steps to Reproduce:
open user settings
set "editor.tabSize": 4
"editor.detectIndentation": false
right-click "Format Document"
I use the latest vscode-insiders

Fixed! Was the 'Prettier' plugin.


Month title not updates quickly

When I scroll quickly over months the month title not update. How can I fix this please?

This library is a UICollectionView.
Therefore use what every UICollectionView function there is to accomplish this.
For example, try putting the month updating code in this function:
func calendar(_ calendar: JTAppleCalendarView, willScrollToDateSegmentWith visibleDates: DateSegmentInfo)

let me know if this helped

Great, that was very helpful, but I found 2 bugs in willScrollToDateSegmentWith that don't present in didScrollToDateSegmentWith, the first is willScrollToDateSegmentWith not called when I scroll to date in viewDidLoad, second July month appears as June, so when I scroll from June to July the month title stay June, although willScrollToDateSegmentWith is called when scrolling.

I saw the issue u mentioned.
I did not call willScroll for the scrollToDateFunction
looking into why i missed that.

in the mean time, add the header update code both in the willScroll and the didScroll delegate functions. I think of a fix for this

In regards to the wrong month being displayed. I am not experiencing this.
Maybe a sample application demonstrating this will help.

Thank you! I will check it in a few hours and get back to you.

Okay I create a sample project and June-July wrong month issue is still there, please check it here:
https://github.com/fawzirifai/TestingJTAppleCalendar/

if you are online, texting is faster here -> https://gitter.im/patchthecode/JTAppleCalendar

I am not seeing the problem you spoke of.

Maybe it is timezone related issue?

Yes it is -->  If you are on the east side of the world, then you will see this.
This happens with every calendar library on github.
Here is a detailed explanation of the issue --> https://github.com/patchthecode/JTAppleCalendar/issues/252

In order to fix it, do this:
In your configureCalendar delegate function, please provide a calendar configured with the time zone settings that you want
let parameters = ConfigurationParameters(startDate: Calendar.current.date(byAdding: .month, value: -4, to: Date())!,
                                                 endDate: Calendar.current.date(byAdding: .month, value: +4, to: Date())!,
                                                 calendar: Calendar())

Let me try.

As for the first issue --> calling the willScroll delegate when a developer calls the scrollToDate function. I am still thinking about if I should do this or not.

It is not a big problem, I can configure the label when the calendar loaded. Regarding to the second issue, why it is happens only with willScroll? the issue is not present in didScroll.

Regarding to the second issue

2nd issue being the wrong month is shown?

Okay.

issue resolved with master branch code.


Exception: variable does not exist;

I run this pystan 3.0 with the eight schools case, and find out an error:
File "/opt/python3/lib/python3.6/site-packages/stan/model.py", line 189, in build
raise RuntimeError(response_payload["error"]["message"])
RuntimeError: Error calling param_names: `Exception: variable does not exist; processing stage=data initialization; variable name=J; base type=int (in 'unknown file name' at line 3)
Could you please check it? Thank you.
The source code is :
import stan
program_code = """
data {
int<lower=0> J; // number of schools
real y[J]; // estimated treatment effects
real<lower=0> sigma[J]; // s.e. of effect estimates
}
parameters {
real mu;
real<lower=0> tau;
real eta[J];
}
transformed parameters {
real theta[J];
for (j in 1:J)
theta[j] = mu + tau * eta[j];
}
model {
target += normal_lpdf(eta | 0, 1);
target += normal_lpdf(y | theta, sigma);
}
"""
data = {'J': 8,
'y': [28,  8, -3,  7, -1,  1, 18, 12],
'sigma': [15, 10, 16, 11,  9, 11, 10, 18]}
posterior = stan.build(program_code, data=data)
fit = posterior.sample(num_chains=4, num_samples=1000)

Yes, I've been getting this myself in some virtualenvs but not others. I
haven't been able to figure out what is happening.
The tests pass on travis with the code you provided (eight schools is
one of the tests), so it's not something obvious.
Also, pystan 3 is not quite ready for testing. Try back in a week.
(There's one or two changes in httpstan that need to be made.)
On 11/8/18 10:26 PM, L619 wrote:

I run this pystan 3.0 with the eight schools case, and find out an error:
File "/opt/python3/lib/python3.6/site-packages/stan/model.py", line 189,
in build
raise RuntimeError(response_payload["error"]["message"])
RuntimeError: Error calling param_names: `Exception: variable does not
exist; processing stage=data initialization; variable name=J; base
type=int (in 'unknown file name' at line 3)
Could you please check it? Thank you.
The source code is :
import stan
program_code = """
data {
int<lower=0> J; // number of schools
real y[J]; // estimated treatment effects
real<lower=0> sigma[J]; // s.e. of effect estimates
}
parameters {
real mu;
real<lower=0> tau;
real eta[J];
}
transformed parameters {
real theta[J];
for (j in 1:J)
theta[j] = mu + tau * eta[j];
}
model {
target += normal_lpdf(eta | 0, 1);
target += normal_lpdf(y | theta, sigma);
}
"""
data = {'J': 8,
'y': [28, 8, -3, 7, -1, 1, 18, 12],
'sigma': [15, 10, 16, 11, 9, 11, 10, 18]}
posterior = stan.build(program_code, data=data)
fit = posterior.sample(num_chains=4, num_samples=1000)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/pystan-next/issues/35, or mute the thread
https://github.com/notifications/unsubscribe-auth/AmFA1nb3uxGEihpLaVQ0L5eh25jyLx5zks5utPXVgaJpZM4YV5U-.

Currently,the version of httpstan I installed is 0.6.1.  In your env,what is the version of httpstan?  Thank you.

This is happening across versions for me.
On 11/10/18 9:14 PM, L619 wrote:

Currently,the version of httpstan I installed is 0.6.1. In your env,what
is the version of httpstan? Thank you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/pystan-next/issues/35#issuecomment-437637680,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmFA1kjLQ9ESxdAWjr_QNmPDUmIfjs-dks5ut4gagaJpZM4YV5U-.

ERROR:aiohttp.server:Error handling request
Traceback (most recent call last):
File "/opt/python3/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 390, in start
resp = await self._request_handler(request)
File "/opt/python3/lib/python3.6/site-packages/aiohttp/web_app.py", line 366, in _handle
resp = await handler(request)
File "/opt/python3/lib/python3.6/site-packages/httpstan/views.py", line 157, in handle_show_params
param_names_bytes = model_module.param_names(array_var_context_capsule)
File "model_22236aa30d.pyx", line 47, in model_22236aa30d.param_names
RuntimeError: Exception: variable does not exist; processing stage=data initialization; variable name=J; base type=int (in 'unknown file name' at line 3)
response <Response [500]>
Traceback (most recent call last):
File "test_pystan3.0.py", line 54, in
test_func_small_case()
File "test_pystan3.0.py", line 46, in test_func_small_case
posterior = stan.build(program_code, data=data)
File "/opt/python3/lib/python3.6/site-packages/stan/model.py", line 185, in build
response_payload = response.json()
File "/opt/python3/lib/python3.6/site-packages/requests/models.py", line 897, in json
return complexjson.loads(self.text, **kwargs)
File "/opt/python3/lib/python3.6/json/init.py", line 354, in loads
return _default_decoder.decode(s)
File "/opt/python3/lib/python3.6/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/opt/python3/lib/python3.6/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
This problem is still not solved. This is whole error info, could you please fix? Thank you.

The provided code works for me with the current pystan-next branch ( d61542a).

After searching the branch, but I  don't find the version. Could you please give me link address of the version?  Thank you.

Can you just try installing from master?
On 12/7/18 2:47 AM, L619 wrote:

After searching the branch, but I don't find the version. Could you
please give me link address of the version? Thank you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/pystan-next/issues/35#issuecomment-445150427,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmFA1uTKdEUu09z-LbNlaRvbGdbQKs7eks5u2h0CgaJpZM4YV5U-.

The master version have same error.  I want to try your vesion(pystan-next branch  d61542a).  I don't I don't find it. Thank you.

I'm getting this error with a fresh virtualenv. I'll keep trying to figure out what is going on.

Try installing the wheel from pypi with:
pip install pystan==<IP_ADDRESS>a6

I'm getting the error on one Linux system but not on another. Using a virtualenv in both cases. The error is occurring with Python 3.6.7 (Debian-based). It works fine on Python 3.6.5 (RHEL). pip freeze shows identical packages.
@ahartikainen can you try this out?

I can try when I have time.
This error is httpstan error not in pystan. In pystan is just fails to read empty data.
httpstan:
File "/opt/python3/lib/python3.6/site-packages/httpstan/views.py", line 157, in handle_show_params
param_names_bytes = model_module.param_names(array_var_context_capsule)
File "model_22236aa30d.pyx", line 47, in model_22236aa30d.param_names
RuntimeError: Exception: variable does not exist; processing stage=data initialization; variable name=J;
base type=int (in 'unknown file name' at line 3)

Notice
 param_names_bytes = model_module.param_names(array_var_context_capsule)

RuntimeError: Exception: variable does not exist;

processing stage=data initialization; variable name=J; base type=int

Is it missing ;? I hope there are no newline symbols or anything like that?
pystan:
File "/opt/python3/lib/python3.6/site-packages/stan/model.py", line 185, in build
response_payload = response.json()

To get better error message, it might mean that we need to first check if response can extract json?
In conclusion:
Maybe there is something wrong with the JSON library? Are there any external parts (other than Python).

If I install from the tarball (from PyPI) instead of using the wheels, everything works on Python 3.6.7 (Debian-based). @L619 you might try that.
This still doesn't explain why Python 3.6.5 (RHEL) accepts the wheels and Python 3.6.7 (Debian-based) doesn't.

I think this may be a problem with an incompatibility between the manylinux wheels and the freshly-compiled module. I could well be wrong.
Here's a possibly-relevant comment: https://github.com/pypa/manylinux/issues/118#issuecomment-308901809

... If you have two extension modules that use C++ internally but that only communicate via python interfaces (i.e., they're not directly linking to each other or smuggling function pointers through pycapsules or something), then you should be OK with either static linking or vendoring libstdc++. (Watch out for cython's cimport functionality, which under the covers involves smuggling function pointers through pycapsules; otherwise I think you'll know if you're doing this.)

Since we are smuggling pointers via pycapsules between two extension modules that use C++ internally -- I'm assuming this might well be a problem.
Perhaps compiling with -static-libstdc++ would help. Once I learn how to compile these manylinux wheels using docker locally, I'll give it a try.
In the short term, I'll make a new release of httpstan with no wheels (source only). I think this should fix things for @L619 .

@riddell-stan, thank you, but for my stan model ,there is still other error, could you please help fix it? Thank you.
The error is :
posterior = stan.build(program_code, data=dat)
File "/root/python3/lib/python3.6/site-packages/stan/model.py", line 186, in build
response = requests.post(f"http://{host}:{port}{path}", json=payload)
File "/root/python3/lib/python3.6/site-packages/requests/api.py", line 116, in post
return request('post', url, data=data, json=json, **kwargs)
File "/root/python3/lib/python3.6/site-packages/requests/api.py", line 60, in request
return session.request(method=method, url=url, **kwargs)
File "/root/python3/lib/python3.6/site-packages/requests/sessions.py", line 519, in request
prep = self.prepare_request(req)
File "/root/python3/lib/python3.6/site-packages/requests/sessions.py", line 462, in prepare_request
hooks=merge_hooks(request.hooks, self.hooks),
File "/root/python3/lib/python3.6/site-packages/requests/models.py", line 316, in prepare
self.prepare_body(data, files, json)
File "/root/python3/lib/python3.6/site-packages/requests/models.py", line 466, in prepare_body
body = complexjson.dumps(json)
File "/root/python3/lib/python3.6/json/init.py", line 231, in dumps
return _default_encoder.encode(obj)
File "/root/python3/lib/python3.6/json/encoder.py", line 199, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/root/python3/lib/python3.6/json/encoder.py", line 257, in iterencode
return _iterencode(o, 0)
File "/root/python3/lib/python3.6/json/encoder.py", line 180, in default
o.class.name)
TypeError: Object of type 'Series' is not JSON serializable
The model is:

The model is :
line_model_code = """
data {
int T;                                // Sample size
int<lower=1> K;                       // Number of seasonal vectors
real t[T];                            // Day
real y[T];                            // Time-series
int S;                                // Number of changepoints
real A[T, S];                   // Split indicators
real t_change[S];                 // Index of changepoints
real X[T,K];                // season vectors
vector[K] sigmas;              // scale on seasonality prior
real<lower=0> tau;                  // scale on changepoints prior
}
        parameters {
          real k;                            // Base growth rate
          real m;                            // offset
          real delta[S];                       // Rate adjustments
          real<lower=0> sigma_obs;               // Observation noise (incl. seasonal variation)
          real beta[K];                    // seasonal vector
        }

        transformed parameters {
          real gamma[S];                  // adjusted offsets, for piecewise continuity

          for (i in 1:S) {
            gamma[i] = -t_change[i] * delta[i];
          }
        }

        model {
          real Y[T];

          //priors
          k ~ normal(0, 5);
          m ~ normal(0, 5);
          delta ~ double_exponential(0, tau);
          sigma_obs ~ normal(0, 0.5);
          beta ~ normal(0, sigmas);

          // Likelihood
          for (i in 1:T) {
            Y[i] = (dot_product(A[i], delta) + k) * t[i] + (dot_product(A[i], gamma) + m) + dot_product(X[i], beta);
          }
          y ~ normal(Y, sigma_obs);
        }
        """

Glad it fixed the problem. Thanks for bringing the problem to our attention.
You can't pass pandas Series as values in the data dictionary. We
should add some checks here. I suspect many people will do what you do.
But this is something for another issue.
On 12/13/18 7:00 AM, L619 wrote:

@riddell-stan https://github.com/riddell-stan, thank you, but for my
stan model ,there is still other error, could you please help fix it?
Thank you.
The error is :
posterior = stan.build(program_code, data=dat)
File "/root/python3/lib/python3.6/site-packages/stan/model.py", line
186, in build
response = requests.post(f"http://{host}:{port}{path}", json=payload)
File "/root/python3/lib/python3.6/site-packages/requests/api.py", line
116, in post
return request('post', url, data=data, json=json, **kwargs)
File "/root/python3/lib/python3.6/site-packages/requests/api.py", line
60, in request
return session.request(method=method, url=url, **kwargs)
File "/root/python3/lib/python3.6/site-packages/requests/sessions.py",
line 519, in request
prep = self.prepare_request(req)
File "/root/python3/lib/python3.6/site-packages/requests/sessions.py",
line 462, in prepare_request
hooks=merge_hooks(request.hooks, self.hooks),
File "/root/python3/lib/python3.6/site-packages/requests/models.py",
line 316, in prepare
self.prepare_body(data, files, json)
File "/root/python3/lib/python3.6/site-packages/requests/models.py",
line 466, in prepare_body
body = complexjson.dumps(json)
File "/root/python3/lib/python3.6/json/init.py", line 231, in dumps
return _default_encoder.encode(obj)
File "/root/python3/lib/python3.6/json/encoder.py", line 199, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/root/python3/lib/python3.6/json/encoder.py", line 257, in iterencode
return _iterencode(o, 0)
File "/root/python3/lib/python3.6/json/encoder.py", line 180, in default
o.class.name)
TypeError: Object of type 'Series' is not JSON serializable
The model is:
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/pystan-next/issues/35#issuecomment-446944090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AmFA1lvTcOgoj3D9paRQ0oI6DkItwCMyks5u4kFQgaJpZM4YV5U-.

We could use np.asarray ?

Let's continue this in #51. I also think we need a new issue for the C++ wheel issue.

@riddell-stan ,But I tranform the dat to array, still have same error "TypeError: Object of type 'Series' is not JSON serializable". Could you please help fix it again? Thank you.
The modified code is(now seasonal_features is numpy.ndarray type):
dat = {'T': history.shape[0],
'K': seasonal_features.shape[1],
'S': len(self.changepoints_t),
'y': np.array(history['y_scaled'].values),
't': np.array(history['t'].values),
't_change': np.array(self.changepoints_t),
'X': seasonal_features.values,
'sigmas': np.array(prior_scales),
'tau': self.changepoint_prior_scale,
'trend_indicator': int(self.growth == 'logistic'),
's_a': np.array(component_cols['additive_terms'].values),
's_m': np.array(component_cols['multiplicative_terms'].values)
}


Notifications choosen language issue

Hi, I have a Samsung Galaxy Note 5 with Android 6.0.1, my device language is set to Spanish and k9 mail language is set to English (because in Spanish notification delete button is hidden because "mark as read" text, is to long), the thing is that some times notification is shown correctly in English and some times is shown in spanish, I haven't figure out why.
I have a screen video recorded, try to attached here, if I can't please tell me where to send over email.
Thanks.
tmp_22194-2017_02_16_16_12_05.mp4964100838.zip

because in Spanish notification delete button is hidden because "mark as read" text, is to long

Can we not just fix this translation? That seems like something we'd want to do anyway.
The fact that you can configure K9 to have a separate language has always struck me as an odd feature.
Regardless I have worked out why this happens and will submit a PR for it.

Hi,
Well yes, that it'll be helpful, maybe you can make an easy fix just leaving only icons on notification buttons, everyone knows what's each button for.
Thanks.

Hi,
I was thinking that maybe if you do it like that, removing text from notifications buttons, probably you may add the other icons, just like when reading e-mail, all buttons could be reply to all (cover reply and reply to all or separete if better), forward, mark as read, move to folder, delete, I think these are the most common used.
Thanks.
Regards.

Closing because of #2262. If the problem itself persists, it should be solved by way of a different translation string.


null.osm

There is a submission in the Cruz Roja Huaquillas data set that sets the OSM file in the data.json to null.osm. This is not right. In the data, there is an actual OSM file. Determine what bug has caused this to happen.
http://posm.local/omk/data/submissions/ecuador_buildings/0c2fd24d-d08b-48b5-9bac-790cb03c2f73/data.json

what's up with this file name?
OSMNode-9_2016-04-25T135201Z.osm
http://omkserver.com/omk/data/submissions/buildings/bfb5c56a-4e4f-4dec-8084-4024794c290d/

Someone submitted with an old version of the app on their phone. Hasn't been this way in a long while.


Packer issue on Soft layer integration

I have installed and configured Go ( GOPATH, GOROOT configured) but still struggling to configure packer for Soft Layer. please give your insight.
Error:
[root@renbuild ~]# cd $GOPATH/src/github.com/leonidlm/packer-builder-softlayer
[root@renbuild packer-builder-softlayer]# go build -o /usr/local/packer/packer-builder-softlayer main.go
builder/softlayer/step_create_ssh_key.go:4:2: cannot find package "code.google.com/p/gosshold/ssh" in any of:
/usr/local/go/src/code.google.com/p/gosshold/ssh (from $GOROOT)
/usr/local/src/code.google.com/p/gosshold/ssh (from $GOPATH)
builder/softlayer/builder.go:6:2: cannot find package "github.com/mitchellh/multistep" in any of:
/usr/local/go/src/github.com/mitchellh/multistep (from $GOROOT)
/usr/local/src/github.com/mitchellh/multistep (from $GOPATH)
builder/softlayer/builder.go:7:2: cannot find package "github.com/mitchellh/packer/common" in any of:
/usr/local/go/src/github.com/mitchellh/packer/common (from $GOROOT)
/usr/local/src/github.com/mitchellh/packer/common (from $GOPATH)
builder/softlayer/step_create_ssh_key.go:11:2: cannot find package "github.com/mitchellh/packer/common/uuid" in any of:
/usr/local/go/src/github.com/mitchellh/packer/common/uuid (from $GOROOT)
/usr/local/src/github.com/mitchellh/packer/common/uuid (from $GOPATH)
builder/softlayer/builder.go:8:2: cannot find package "github.com/mitchellh/packer/helper/communicator" in any of:
/usr/local/go/src/github.com/mitchellh/packer/helper/communicator (from $GOROOT)
/usr/local/src/github.com/mitchellh/packer/helper/communicator (from $GOPATH)
builder/softlayer/builder.go:9:2: cannot find package "github.com/mitchellh/packer/helper/config" in any of:
/usr/local/go/src/github.com/mitchellh/packer/helper/config (from $GOROOT)
/usr/local/src/github.com/mitchellh/packer/helper/config (from $GOPATH)
builder/softlayer/builder.go:10:2: cannot find package "github.com/mitchellh/packer/packer" in any of:
/usr/local/go/src/github.com/mitchellh/packer/packer (from $GOROOT)
/usr/local/src/github.com/mitchellh/packer/packer (from $GOPATH)
main.go:5:2: cannot find package "github.com/mitchellh/packer/packer/plugin" in any of:
/usr/local/go/src/github.com/mitchellh/packer/packer/plugin (from $GOROOT)
/usr/local/src/github.com/mitchellh/packer/packer/plugin (from $GOPATH)
builder/softlayer/builder.go:11:2: cannot find package "github.com/mitchellh/packer/template/interpolate" in any of:
/usr/local/go/src/github.com/mitchellh/packer/template/interpolate (from $GOROOT)
/usr/local/src/github.com/mitchellh/packer/template/interpolate (from $GOPATH)
builder/softlayer/ssh.go:7:2: cannot find package "golang.org/x/crypto/ssh" in any of:
/usr/local/go/src/golang.org/x/crypto/ssh (from $GOROOT)
/usr/local/src/golang.org/x/crypto/ssh (from $GOPATH)
import cycle not allowed
package github.com/leonidlm/packer-builder-softlayer/builder/softlayer
imports bytes
imports errors
imports runtime
imports runtime/internal/atomic
imports runtime
[root@renbuild packer-builder-softlayer]#

Fixed here https://github.com/watson-platform/packer-builder-softlayer


Error occurred while importing

I tried to launch an import task using this CLI to upload to Linear github issues.
It failed with the following message:
Error occurred while importing:

{
  "errors": [
    {
      "message": "invalid issue description",
      "path": [
        "issueCreate"
      ],
      "locations": [
        {
          "line": 12,
          "column": 13
        }
      ],
      "extensions": {
        "type": "invalid input",
        "userError": true,
        "userPresentableMessage": {}
      }
    }
  ],
  "data": null
}

I retried a second time and it failed exactly on the same issue. Unfortunately I cannot paste here the issue description that caused this error.

I've narrowed down the specific content in the issue description that seem to trigger the error:
mutation {
  issueCreate(
    input: {
      title: "This does not work"
      description: "- <whatever>:\r\n![image](https://i.imgur.com/eK1Xi1j.jpg)"
      teamId: "<teamid>"
    }
  ) {
    success
    issue {
      id
    }
  }
}

This will systematically result in an error:
{
  "errors": [
    {
      "message": "invalid issue description",
      "path": [
        "issueCreate"
      ],
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "extensions": {
        "type": "invalid input",
        "userError": true,
        "userPresentableMessage": {}
      }
    }
  ],
  "data": null
}

There are also weird behaviors associated to the presence of the image it seems. Sometimes, the image will be loaded, sometimes it won't. The text content can also not be present.
description: "![image](https://i.imgur.com/eK1Xi1j.jpg)" (success: true)

description: "- <whatever>: ![image](https://i.imgur.com/eK1Xi1j.jpg)" (success: true):

description: "- whatever:" (success: true):

I've narrowed down the specific content in the issue description that seem to trigger the error:
mutation {
  issueCreate(
    input: {
      title: "This does not work"
      description: "- <whatever>:\r\n![image](https://i.imgur.com/eK1Xi1j.jpg)"
      teamId: "<teamid>"
    }
  ) {
    success
    issue {
      id
    }
  }
}

This will systematically result in an error:
{
  "errors": [
    {
      "message": "invalid issue description",
      "path": [
        "issueCreate"
      ],
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "extensions": {
        "type": "invalid input",
        "userError": true,
        "userPresentableMessage": {}
      }
    }
  ],
  "data": null
}

There are also weird behaviors associated to the presence of the image it seems. Sometimes, the image will be loaded, sometimes it won't. The text content can also not be present.
description: "![image](https://i.imgur.com/eK1Xi1j.jpg)" (success: true)

description: "- <whatever>: ![image](https://i.imgur.com/eK1Xi1j.jpg)" (success: true):

description: "- whatever:" (success: true):

This was an API side problem rather than an importer issue. I've merged a fix, and that should be live soon (~15-20 minutes). Let me know if you still see problems!

This was an API side problem rather than an importer issue. I've merged a fix, and that should be live soon (~15-20 minutes). Let me know if you still see problems!

@rlargman Thanks for taking a look. Indeed an API problem, please let me know if there'd have been a better place to post the issue.
For the issue itself, I was able to redo the test and indeed the server will issue a success response for all of these cases.
However the result within the Linear app is still a bit surprising, here are 2 examples:
description: "- whatever: ![image](https://i.imgur.com/eK1Xi1j.jpg)" results in:

(no image)
description: "- whatever:\n![image](https://i.imgur.com/eK1Xi1j.jpg)"

(image not imported and replaced with a placeholder saying 'image')

@rlargman Thanks for taking a look. Indeed an API problem, please let me know if there'd have been a better place to post the issue.
For the issue itself, I was able to redo the test and indeed the server will issue a success response for all of these cases.
However the result within the Linear app is still a bit surprising, here are 2 examples:
description: "- whatever: ![image](https://i.imgur.com/eK1Xi1j.jpg)" results in:

(no image)
description: "- whatever:\n![image](https://i.imgur.com/eK1Xi1j.jpg)"

(image not imported and replaced with a placeholder saying 'image')

@alxckn For Linear app issues, you can report bugs or request features through the app itself, under Help & Feedback at the bottom of the sidebar, or by joining our Slack group.
Currently, you can only add images to issues via markdown through the API. To add them in the app you must upload them through drag & drop, or by selecting or pasting them. But, it's a good suggestion to be able to add images through markdown as well!

@alxckn For Linear app issues, you can report bugs or request features through the app itself, under Help & Feedback at the bottom of the sidebar, or by joining our Slack group.
Currently, you can only add images to issues via markdown through the API. To add them in the app you must upload them through drag & drop, or by selecting or pasting them. But, it's a good suggestion to be able to add images through markdown as well!

@rlargman thanks!

Currently, you can only add images to issues via markdown through the API

Just to clarify, I do think there is still a bug with this very feature, i.e. depending on the markdown content formatting uploaded via the API, some words or images will be discarded. As a result the content copied over from github might be missing things.
Also, I did retry a full import from github using linear-import but it failed again with the same kind of error, this time on another github issue (invalid issue description).

@rlargman thanks!

Currently, you can only add images to issues via markdown through the API

Just to clarify, I do think there is still a bug with this very feature, i.e. depending on the markdown content formatting uploaded via the API, some words or images will be discarded. As a result the content copied over from github might be missing things.
Also, I did retry a full import from github using linear-import but it failed again with the same kind of error, this time on another github issue (invalid issue description).

@alxckn In your comment above, if I make a request with the description you provided like so:
mutation {
  issueCreate(
    input: {
      title: "New Issue Title 2",
      teamId: "xxx-my-team-id",
      description: "- whatever:\n![image](https://i.imgur.com/eK1Xi1j.jpg)",
    }
  ) {
    success
    issue {
      id
      title
      state {
        id
        name
      }
    }
  }
}

It works as expected:

What is the query you are doing with that description?
For the other description you provided: description: "- whatever: ![image](https://i.imgur.com/eK1Xi1j.jpg)", an image cannot be an item in a bulleted list, so that behavior is as expected.
Do you have examples of the other github issues where the issue description was invalid in the import? There could still be some other edge cases we haven't accounted for with images in descriptions that I need to fix.

@alxckn In your comment above, if I make a request with the description you provided like so:
mutation {
  issueCreate(
    input: {
      title: "New Issue Title 2",
      teamId: "xxx-my-team-id",
      description: "- whatever:\n![image](https://i.imgur.com/eK1Xi1j.jpg)",
    }
  ) {
    success
    issue {
      id
      title
      state {
        id
        name
      }
    }
  }
}

It works as expected:

What is the query you are doing with that description?
For the other description you provided: description: "- whatever: ![image](https://i.imgur.com/eK1Xi1j.jpg)", an image cannot be an item in a bulleted list, so that behavior is as expected.
Do you have examples of the other github issues where the issue description was invalid in the import? There could still be some other edge cases we haven't accounted for with images in descriptions that I need to fix.

@rlargman
I just did the following query:
mutation {
  issueCreate(
    input: {
      title: "Text followed by a line break and an image"
      description: "- some text:\n![image](https://i.imgur.com/uDIxI5P.jpg)"
      teamId: "xxxx"
    }
  ) {
    success
    issue {
      id
      title
    }
  }
}

and end up with this:

an image cannot be an item in a bulleted list, so that behavior is as expected

Good to know. To be honest I don't even know whether we have such a case within our issues, I was just trying to find relevant test cases. One thing to note is that putting - whatever: ![image](https://i.imgur.com/eK1Xi1j.jpg) in a github issue description or comment will work (as in it will then display a bullet point followed by an image below).
I stripped the issue description+comments that were blocking the last import and got to this issue mutation query with a seemingly pretty harmless description:
mutation {
  issueCreate(
    input: {
      title: "A new breaking issue"
      description: "---**@bobo** 2019-04-11\n\n![image](https://i.imgur.com/uDIxI5P.jpg)"
      teamId: "xxx-team-id"
    }
  ) {
    success
    issue {
      id
      title
    }
  }
}

Which results in:
{
  "errors": [
    {
      "message": "invalid issue description",
      "path": [
        "issueCreate"
      ],
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "extensions": {
        "type": "invalid input",
        "userError": true,
        "userPresentableMessage": {}
      }
    }
  ],
  "data": null
}

@rlargman
I just did the following query:
mutation {
  issueCreate(
    input: {
      title: "Text followed by a line break and an image"
      description: "- some text:\n![image](https://i.imgur.com/uDIxI5P.jpg)"
      teamId: "xxxx"
    }
  ) {
    success
    issue {
      id
      title
    }
  }
}

and end up with this:

an image cannot be an item in a bulleted list, so that behavior is as expected

Good to know. To be honest I don't even know whether we have such a case within our issues, I was just trying to find relevant test cases. One thing to note is that putting - whatever: ![image](https://i.imgur.com/eK1Xi1j.jpg) in a github issue description or comment will work (as in it will then display a bullet point followed by an image below).
I stripped the issue description+comments that were blocking the last import and got to this issue mutation query with a seemingly pretty harmless description:
mutation {
  issueCreate(
    input: {
      title: "A new breaking issue"
      description: "---**@bobo** 2019-04-11\n\n![image](https://i.imgur.com/uDIxI5P.jpg)"
      teamId: "xxx-team-id"
    }
  ) {
    success
    issue {
      id
      title
    }
  }
}

Which results in:
{
  "errors": [
    {
      "message": "invalid issue description",
      "path": [
        "issueCreate"
      ],
      "locations": [
        {
          "line": 2,
          "column": 3
        }
      ],
      "extensions": {
        "type": "invalid input",
        "userError": true,
        "userPresentableMessage": {}
      }
    }
  ],
  "data": null
}

@alxckn The issue with image uploads not working properly should be fixed now. I've tried with both of the issue descriptions you have above, and both are working for me now. How does it look on your end?

@alxckn The issue with image uploads not working properly should be fixed now. I've tried with both of the issue descriptions you have above, and both are working for me now. How does it look on your end?

@rlargman I was able to complete a full import today, thanks!


Improve Errors and Update Readme

Refactored the error handling to use fmt.Errorf instead of log.Println and os.Exit. This allows to return errors from the RunE function, which is a more idiomatic approach in Cobra applications.

I've updated the README to reflect the changes in how the --packages and --replaces works now.

I am signing the commits using gitsign  following https://docs.sigstore.dev/signing/gitsign/
Why the cert are not getting verified?

Is it because of https://github.com/chainguard-dev/gobump/blob/b10c54a40ba783d7dd7aec4127dc809b22d7f3d3/.chainguard/source.yaml#L9
And I need to have chainguard.dev email account that matches with the regex?
chainguard-enforce docs is not clear.
/cc @hectorj2f

thanks @debasishbsws! I merged your PR.


The provided value 'undefined' is not a valid enum value of type XMLHttpRequestResponseType

it gives this error . it is not working.
Packages: cfs:base-package
cfs:filesystem
cfs:collection
cfs:collection-filters
cfs:standard-packages
cfs:power-queue
cfs:micro-queue
cfs:reactive-list
cfs:ui
cfs:upload-http
cfs:transfer
cfs:tempstore
cfs:ejson-file
cfs:worker
cfs:upload-ddp
cfs:data-man
cfs:storage-adapter
cfs:http-publish
cfs:http-methods
cfs:filesaver
cfs:reactive-property
cfs:gridfs

https://github.com/CollectionFS/Meteor-CollectionFS/issues/688


add new logo to repo

I added the new logo to the repo. You can see I changed the favicon logo on the docs page. I also added the logo with text to the beginning of readme.

@apirogov if you also have any feedback about the placement and usage of the new logo, please let me know

Well, there are the options of putting the image

above the text headline, or
below

and the variation in alignment.
I am not sure about either combination being "better", just want to point out I did it for dirschema in exactly the "opposite" way :rofl:
So TL;DR: LGTM, but maybe we should agree on a consistent way of doing it for our repos

FYI: I am pro "having it halfway consistent", but no strong feelings about how exactly.

I feel like the logo is getting in the way of context if it is after the title; this is why I put it before the title. Of course, both ways work perfectly in my opinion 😄

@hofmannv I gave the direct links of github to show logos. If we change the logos at a later time, the naming should be consistent or we will have broken links in our readme and documentations.

yes - that is why they are in an open git repo (i.e. to be usable from there). We could actually think about PURLs... ;-)


chore: remove all reference to minification from API category, now that this is centralized in CLI

Description of changes
Now that CFN minification has been centralized in the Amplify CLI https://github.com/aws-amplify/amplify-cli/pull/12072 remove explicit handling from these packages.
CDK / CloudFormation Parameters Changed
No params changed, but we will no longer internally write CFN files in a minified (e.g. no whitespace) format.
Issue #, if available
N/A - cleanup associated w/ bug fix.
Description of how you validated changes
Unit tests, e2e tests in CLI.
Checklist

[x] PR description included
[x] yarn test passes

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1290 (6681321) into main (2b4e87e) will increase coverage by 0.00%.
The diff coverage is 40.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main    #1290   +/-   ##
=======================================
  Coverage   63.63%   63.64%
=======================================
  Files         297      297
  Lines       18618    18616    -2
  Branches     4493     4487    -6
=======================================
  Hits        11848    11848
+ Misses       6150     6148    -2
  Partials      620      620

Impacted Files
Coverage Δ

...graphql-transformer/transform-graphql-schema-v1.ts
8.96% <ø> (ø)

...graphql-transformer/transform-graphql-schema-v2.ts
19.41% <0.00%> (ø)

.../src/graphql-transformer/transformer-options-v2.ts
14.76% <ø> (ø)

.../graphql-transformer-core/src/util/amplifyUtils.ts
9.66% <0.00%> (+0.05%)
:arrow_up:

...lify-category-api/src/graphql-transformer/utils.ts
73.05% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Initial work on "at-mixin-argumentless-call-parentheses" fix

This PR adds fix functionality to at-mixin-argumentless-call-parentheses. There is one problem, though: it should also depend on at-mixin-parentheses-space-before rule for spacing but currently there is no way to check against other rule. There is stylelint.utils.checkAgainstRule helper utility, but it doesn’t know about other SCSS rules since Jest Stylelint setup works only for one rule. Does it make sense to upgrade Jest config to allow additional configuration to account for these changes?

Thanks!

There is one problem, though: it should also depend on at-mixin-parentheses-space-before rule for spacing but currently there is no way to check against other rule.

I agree, the if the fix is applied, then it should not cause other rules to throw warnings.

Does it make sense to upgrade Jest config to allow additional configuration to account for these changes?

Yes, the Jest config can be updated if needed for better testing.

It looks like I was wrong in approach to this, Stylelint doesn’t support dependeant rules configuration (yet): https://github.com/stylelint/stylelint/issues/3210#issuecomment-372288465, https://github.com/stylelint/stylelint/issues/2532#issuecomment-302109499
Should we still create fixer for this and let users know caveats regarding using it?

Yeah actually now I remember that there was already some discussion about it (the issue 3210).
What jeddy3 said about rules not having to worry about introducing warnings for other rules is then the way we should do it.

@kristerkari changes pushed!

Looks good now, thanks!

@kristerkari should I mention that fix could clash with other rules?

sure, I think that it's good to let the users know about it if they use the fix option.

@kristerkari done!

Awesome, this is going out in the next release. Thanks again!


it does not  provide results in associations

mongoid_search provides only search results. when we looping through these results causes hitting of database and  data in associations also hitting again database . even  relevant_search option is also not working in getting data from associations

@santoshkumar611 Could you provide code snippet or test case?

@santoshkumar611 can the isuue be closed by last version or is it just outdated?


HtmlHelperOptions.ClientValidationEnabled = false is ignored

services.AddMvc().AddViewOptions(o =>             {                 if (_env.IsDevelopment())                 {                     o.HtmlHelperOptions.ClientValidationEnabled = false;                 }             })
is currently not working on the register page of the asp.net identity template.

@muratg , is that expected not to work on razor pages and be applicable only to traditional mvc views?

@Ponant I don't know.
cc @danroth27

@rynowak

Thanks for contacting us, @Ponant.
@javiercn, can you please look into this? Thanks!

This is a product bug.
The issue is that PageActionInvokerProvider takes in IOptions<HtmlHelperOptions> directly in the constructor instead of IOptions<MvcViewOptions> as it should.
https://github.com/aspnet/AspNetCore/blob/master/src/Mvc/Mvc.RazorPages/src/Infrastructure/PageActionInvokerProvider.cs#L55
The impact is that htmloptions set in mvcviewoptions are not respected for pages.
There are several trivial workarounds for it:

Set the option in _ViewStart.cshtml
Set the option in both places by additionally calling services.Configure<HtmlHelperOptions>(o=> o.ClientValidationEnabled = false)

The fix for 3.0 is to make a breaking change and have the constructor take in the right parameter.
The fix for downlevel versions, should we  choose to implement it, is to modify createactioninvoker to pass in the right options.
The risk of this downlevel fix is that someone might have workaround it using option 2, and then we would break them.
We could consider this for patching, but my personal take is that we don't, given that there is a trivial workaround, the scenario is not very common and that we would risk breaking other people that has workaround it.
            var properOptions = actionContext.HttpContext.RequestServices.GetRequiredService<IOptions<MvcViewOptions>>()

            return new PageActionInvoker(
                _selector,
                _diagnosticListener,
                _logger,
                _actionContextAccessor,
                _mapper,
                pageContext,
                filters,
                cacheEntry,
                _parameterBinder,
                _tempDataFactory,
                properOptions.Value.HtmlHelperOptions);

https://github.com/aspnet/AspNetCore/pull/9289

Still not working in .Net Core 3.,0 Preview4
             services.AddRazorPages().AddViewOptions(x => x.HtmlHelperOptions.ClientValidationEnabled = false)                 .AddNewtonsoftJson();

This is fixed in preview5.


Russian language

please add Russian. I want to create a Russian voiceover for an old game and your instrument is perfect for this

After Russian is added I would also like to see Bulgarian language implemented as well since the Cyrillic alphabet is identical with only 3 letters less to Russian and a slight difference in pronunciation.

It would be nice if the repository had instructions on how to train the model to another language.

I'm looking also for Spanish <3


⚠ ClamAV has degraded performance

In 67ddebe, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 482 ms

Resolved: ClamAV performance has improved in 4bdfd35.


how to disable the edge-json-viewer flag

In previous version, we can disable edge-json-viewer in edge://flags/.
But now( version: 123.0.2420.53 (正式版本) (x86_64)   ), I can not find this:

https://github.com/MicrosoftEdge/DevTools/issues/87
https://github.com/zxlie/FeHelper/issues/312
https://github.com/tulios/json-viewer/issues/339

Thanks for filing. I'll discuss with the team about this and we'll get back to this issue with an update.

Is there any other way to disable JSON Viewer？

We have a fix almost ready, and are working on getting it deployed in Edge.

Did they fix the problem? because that detail has just been presented to me

Any update on this please? I've had to resort to using Chrome because of this, and I'd much rather be back using Edge.

The flag that's used to disable the built-in JSON viewer will be available again in Edge starting with the next release, shipping on April 18.

Closing this as fixed based on my latest comment. But if you still don't have the flag and you have verified that you have Edge 124+, then feel free to comment and I'll re-open the issue.

@captainbrosset

@captainbrosset  - Still don't see the flag after updating to '124.0.2478.51'

Closing this as fixed based on my latest comment. But if you still don't have the flag and you have verified that you have Edge 124+, then feel free to comment and I'll re-open the issue.

@captainbrosset still no sign of the flag in 124.0.2478.51

Sorry for the inconvenience. Looking into this now ...

without flag

Still not available :(

Thank you. We are aware of the problem and of the fact that some people prefer using extensions instead. We're working on bringing the flag back for good.

Thank you for working on it very quick and looking into it. I don't want to sound impatient but still want to ask out of planning purposes. Do we have an idea approximately when the remedy would be out? I think I had 2 Edge updates since. If it's going to take over a month, it might be better for developers to move their setup to another Chromium-based browser to not to affect the productivity while working with JSON APIs?

I have some update on this. Thank you all for your patience, but it looks like I'll have to ask for even more patience.
While we did mean for the flag to be added again in Edge 124 (the current stable release), that didn't happen. I just confirmed that the flag is in Edge version 125 though:

This next version is due to become stable on May 16th, 2024. So, in a little more than 2 weeks from now, the flag to disable the JSON Viewer will be available in Microsoft Edge again.
Apologies again for the inconvenience. But also, if there are features of other JSON viewers that you wished were in the Edge one, please do let us know by creating a new issue on this repository.

@captainbrosset thanks for the update. For our use case it's not that features are missing, it's that we use browser extensions to take JSON data and make it editable. One example of this allows administrators to make easy updates and fixes to records in Microsoft Dataverse on data that isn't necessarily displayed on the frontend.
Those extensions can't function when Edge hijacks the JSON rendering.

@BenClist-BC2 thanks for the comment. I moved your request to a new issue, and asked a few questions about it there: https://github.com/MicrosoftEdge/DevTools/issues/251. Please take a look if you have some time. Thanks a lot!

Will anyone adding some kind of json viewer/editor extension from the stores have to disable the flag to be able to use them? Is it a concern to divert more from the other Chromium-based browsers and to widen the differences gap? Just asking.

Will anyone adding some kind of json viewer/editor extension from the stores have to disable the flag to be able to use them? Is it a concern to divert more from the other Chromium-based browsers and to widen the differences gap? Just asking.

see here
have been waiting sooooooooo long to get the flag back

edge://flags/#edge-json-viewer is now available on version 125.0.2535.51

I have some update on this. Thank you all for your patience, but it looks like I'll have to ask for even more patience. While we did mean for the flag to be added again in Edge 124 (the current stable release), that didn't happen. I just confirmed that the flag is in Edge version 125 though:

This next version is due to become stable on May 16th, 2024. So, in a little more than 2 weeks from now, the flag to disable the JSON Viewer will be available in Microsoft Edge again.
Apologies again for the inconvenience. But also, if there are features of other JSON viewers that you wished were in the Edge one, please do let us know by creating a new issue on this repository.

god bless you! thanks a lot 🙆♂


See if #85 is triggered by tests

On second thoughts, reopening. I'd like to run the proxy with this assertion and see if we hit it. If so that would confirm that a) my hypothesis in https://github.com/matrix-org/sliding-sync/issues/85#issue-1683543826 is correct, and b) my interpretation of the sentry tracebacks in https://github.com/matrix-org/sliding-sync/issues/85#issuecomment-1522135939 is correct.

internal.Assert only panics in debug mode, so maybe just test with a direct panic("oh no")

The cause is understood. New PR to follow with a test that reproduces the bug.


undefined method `[]' for #<..::EmbedsMany>

I'm trying to use mongoid-history, but I'm confronted with the following error message when trying to save an object. Disabling mongoid-history lets me save my objects just fine.
undefined method `[]' for #Mongoid::Association::Embedded::EmbedsMany:0x000055c671c28fe8
I am running Rails 5.2.0 on ruby 2.5.1, together with mongoid 7.0.0 and mongoid-history 0.8.0.
Following are my models:
class Recipe
  include Mongoid::Document
  include Mongoid::Timestamps
  include Mongoid::History::Trackable

  field :name, type: String
  field :intro, type: String
  field :quantity, type: String
  field :instructions, type: String
  field :tags, type: Array, default: []

  embeds_many :ingredients
  accepts_nested_attributes_for :ingredients, :allow_destroy => true

  track_history on: [:fields, :embedded_relations],
                :modifier_field => :modifier,
                :modifier_field_inverse_of => :nil,
                :version_field => :version,
                :track_create   =>  true,
                :track_update   =>  true,
                :track_destroy  =>  true

  def tags_list=(arg)
    self.tags = arg.split
  end

  def tags_list
    self.tags.join(' ')
  end
end

class Ingredient
  include Mongoid::Document
  field :quantity, type: String
  field :unit, type: String
  field :name, type: String
  embedded_in :recipe, :inverse_of => :ingredients
end

class User
  include Mongoid::Document
  include Mongoid::Timestamps
  include ActiveModel::SecurePassword

  field :name, type: String
  field :email, type: String
  field :password_digest, type: String
  field :active, type: Mongoid::Boolean
  field :restricted, type: Mongoid::Boolean
  field :avatar, type: BSON::Binary

  has_secure_password
  validates_presence_of :password, :on => :create

  index({ name: 1 }, { unique: true, name: 'name_idx' })
end

Doing something like the following results in the above mentioned error:
user = User.first
recipe = Recipe.first
recipe.name = "Something Else"
recipe.modifier = user
recipe.save

Might just be an configuration issue, but I can't figure out what's wrong.

That's probably because support for mongoid 7 hasn't been added. Care to PR it? Start by adding to .travis.yml and seeing what breaks? Also we should lock things down to mongoid < 8 to avoid similar problems in the future.

I opened https://github.com/mongoid/mongoid-history/issues/220 too.

Maybe Mongoid7 changed the class names? Check what relation_of(field) returns now?

Btw, Donate $50 to my charity and I can take care of it :)

Dup for https://github.com/mongoid/mongoid-history/issues/220, there’s a PR too :)


Refused to execute script from 'http://localhost:8080/dist/main.js

i'm currently using node
when i use the npm run build it builds the dist/main.js along with the ./script/tryingwebpack.js
the ./script/tryingwebpack.js only contains console.log('');
i have no webpack.config.js do i need to use that?
in my package.json i have

"build" :"webpack --mode production --display-error-details --progress --colors  ./scripts/tryingwebpack.js",     "dev" :"webpack --mode development --display-error-details --progress --colors  ./scripts/tryingwebpack.js",
 "devDependencies": {     "webpack": "^4.0.1"   }
  "dependencies": {     "bufferutil": "^3.0.3",     "chai": "^3.5.0",     "chai-http": "^2.0.1",     "ejs": "^2.4.1",     "express": "^4.13.4",     "mongodb": "^2.1.16",     "mongoose": "^5.0.11",     "morgan": "^1.7.0",     "npm": "^5.7.1",     "object-assign": "4.1.0",     "utf-8-validate": "^4.0.0",     "ws": "^5.1.0",     "webpack": "^4.0.1"   },
but the issue is when i import it on the html file using
<script src="dist/main.js"></script> nothing shows up

SLOVED IT by adding
app.use("/dist", express.static(__dirname + "/dist"));
but not sure if its the right thing to do

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue.

@Cariaga did you paste app.use("/dist", express.static(__dirname + "/dist")); into your app.js file?


Cloth sample - how to run?

Hello,
I'm trying to run sample_cloth on Linux by running:
./sample_cloth -i ./envs/office assets/models/cloth/cloth.obj and I don't see the model being loaded into the scene, along with warnings about missing textures.
Am I doing something wrong?

When we overhaul our samples, we should consider using resgen to embed textures and meshes to avoid issues like this.

Maybe, depends on what the sample is trying to achieve.


[Mac Silicon] Fix building

Currently the compilation of kwctl fails on Apple Silicon because of an issue with ring.

@ereslibre can you please add the whole trace/details please?

When compiling ring, the following error is reported:
error: failed to run custom build command for `ring v0.16.20`

Caused by:
  process didn't exit successfully: `/Users/runner/work/kwctl/kwctl/target/release/build/ring-3191974388380180/build-script-build` (exit status: 101)
  --- stdout
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None
  OPT_LEVEL = Some("3")
  TARGET = Some("aarch64-apple-darwin")
  HOST = Some("x86_64-apple-darwin")
  CC_aarch64-apple-darwin = None
  CC_aarch64_apple_darwin = None
  TARGET_CC = None
  CC = None
  CROSS_COMPILE = None
  CFLAGS_aarch64-apple-darwin = None
  CFLAGS_aarch64_apple_darwin = None
  TARGET_CFLAGS = None
  CFLAGS = None
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = None

  --- stderr
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/aesv8-armx-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/aesv8-armx-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/ghashv8-armx-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/ghashv8-armx-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/vpaes-armv8-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/vpaes-armv8-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/armv8-mont-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/armv8-mont-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/chacha-armv8-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/chacha-armv8-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/ecp_nistz256-armv8-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/ecp_nistz256-armv8-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/ghash-neon-armv8-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/ghash-neon-armv8-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/sha512-armv8-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/sha512-armv8-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/sha256-armv8-ios64.o" "/Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/pregenerated/sha256-armv8-ios64.S"
  running "cc" "-O3" "-ffunction-sections" "-fdata-sections" "-fPIC" "-arch" "arm64" "-I" "include" "-Wall" "-Wextra" "-std=c1x" "-Wbad-function-cast" "-Wnested-externs" "-Wstrict-prototypes" "-pedantic" "-pedantic-errors" "-Wall" "-Wextra" "-Wcast-align" "-Wcast-qual" "-Wconversion" "-Wenum-compare" "-Wfloat-equal" "-Wformat=2" "-Winline" "-Winvalid-pch" "-Wmissing-field-initializers" "-Wmissing-include-dirs" "-Wredundant-decls" "-Wshadow" "-Wsign-compare" "-Wsign-conversion" "-Wundef" "-Wuninitialized" "-Wwrite-strings" "-fno-strict-aliasing" "-fvisibility=hidden" "-fstack-protector" "-gfull" "-DNDEBUG" "-c" "-o/Users/runner/work/kwctl/kwctl/target/aarch64-apple-darwin/release/build/ring-5b6959cd4ddce242/out/aes_nohw.o" "crypto/fipsmodule/aes/aes_nohw.c"
  In file included from crypto/fipsmodule/aes/aes_nohw.c:15:
  In file included from include/GFp/aes.h:52:
  In file included from include/GFp/base.h:66:
  In file included from /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:32:
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/cdefs.h:807:2: error: Unsupported architecture
  #error Unsupported architecture
   ^
  In file included from crypto/fipsmodule/aes/aes_nohw.c:15:
  In file included from include/GFp/aes.h:52:
  In file included from include/GFp/base.h:66:
  In file included from /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:33:
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/machine/_types.h:34:2: error: architecture not supported
  #error architecture not supported
   ^
  In file included from crypto/fipsmodule/aes/aes_nohw.c:15:
  In file included from include/GFp/aes.h:52:
  In file included from include/GFp/base.h:66:
  In file included from /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdint.h:52:
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:55:9: error: unknown type name '__int64_t'
  typedef __int64_t       __darwin_blkcnt_t;      /* total blocks */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:56:9: error: unknown type name '__int32_t'
  typedef __int32_t       __darwin_blksize_t;     /* preferred block size */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:57:9: error: unknown type name '__int32_t'
  typedef __int32_t       __darwin_dev_t;         /* dev_t */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:60:9: error: unknown type name '__uint32_t'
  typedef __uint32_t      __darwin_gid_t;         /* [???] process and group IDs */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:61:9: error: unknown type name '__uint32_t'
  typedef __uint32_t      __darwin_id_t;          /* [XSI] pid_t, uid_t, or gid_t*/
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:62:9: error: unknown type name '__uint64_t'; did you mean 'uint64_t'?
  typedef __uint64_t      __darwin_ino64_t;       /* [???] Used for 64 bit inodes */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/_types/_uint64_t.h:31:28: note: 'uint64_t' declared here
  typedef unsigned long long uint64_t;
                             ^
  In file included from crypto/fipsmodule/aes/aes_nohw.c:15:
  In file included from include/GFp/aes.h:52:
  In file included from include/GFp/base.h:66:
  In file included from /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdint.h:52:
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:68:9: error: unknown type name '__darwin_natural_t'
  typedef __darwin_natural_t __darwin_mach_port_name_t; /* Used by mach */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:70:9: error: unknown type name '__uint16_t'
  typedef __uint16_t      __darwin_mode_t;        /* [???] Some file attributes */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:71:9: error: unknown type name '__int64_t'
  typedef __int64_t       __darwin_off_t;         /* [???] Used for file sizes */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:72:9: error: unknown type name '__int32_t'
  typedef __int32_t       __darwin_pid_t;         /* [???] process and group IDs */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:73:9: error: unknown type name '__uint32_t'
  typedef __uint32_t      __darwin_sigset_t;      /* [???] signal set */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:74:9: error: unknown type name '__int32_t'
  typedef __int32_t       __darwin_suseconds_t;   /* [???] microseconds */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:75:9: error: unknown type name '__uint32_t'
  typedef __uint32_t      __darwin_uid_t;         /* [???] user IDs */
          ^
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types.h:76:9: error: unknown type name '__uint32_t'
  typedef __uint32_t      __darwin_useconds_t;    /* [???] microseconds */
          ^
  In file included from crypto/fipsmodule/aes/aes_nohw.c:15:
  In file included from include/GFp/aes.h:52:
  In file included from include/GFp/base.h:66:
  In file included from /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdint.h:53:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types/_intptr_t.h:30:
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/machine/types.h:37:2: error: architecture not supported
  #error architecture not supported
   ^
  In file included from crypto/fipsmodule/aes/aes_nohw.c:15:
  In file included from include/GFp/aes.h:52:
  In file included from include/GFp/base.h:66:
  In file included from /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/clang/12.0.0/include/stdint.h:52:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/stdint.h:53:
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/sys/_types/_intptr_t.h:32:9: error: unknown type name '__darwin_intptr_t'
  typedef __darwin_intptr_t       intptr_t;
          ^
  In file included from crypto/fipsmodule/aes/aes_nohw.c:17:
  In file included from crypto/fipsmodule/aes/../../internal.h:263:
  In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/string.h:61:
  /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/usr/include/_types.h:43:9: error: unknown type name '__uint32_t'
  typedef __uint32_t      __darwin_wctype_t;
          ^
  fatal error: too many errors emitted, stopping now [-ferror-limit=]
  20 errors generated.
  thread 'main' panicked at 'execution failed', /Users/runner/.cargo/registry/src/github.com-1ecc6299db9ec823/ring-0.16.20/build.rs:656:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

...<snip>...

This is an error that comes from the Mac OS 10.15 SDK and as such I think this might be solvable by some cross-compiling dark tricks.

@ereslibre I just moved your comment with the compilation error straight into the body of the issue