Make Out-of-Bounds Indexing return NaN

Was recently debugging a JAX project and caught a bug where I was accessing the indices of a tensor incorrectly inside a jitted function. I understand that throwing errors from accelerated code isn't feasible, however, wouldn't it make more sense for attempts at accessing Out-of-Bounds indices to something that would indicate an error, such as a NaN?

Ah cool, I'll probably end up using that in the future. But is there any strong reason why NaN isn't the default? It feels like it would make unintentional OOB indexing fail less silently.

It's not yet the default because I haven't yet had the time to change the default and look into all the downstream failures and/or performance impacts. I also firmly believe it should be the default.

On Jake's point: we do define a default fill behavior on int/bool types: https://jax.readthedocs.io/en/latest/_autosummary/jax.lax.gather.html
see in particular the fill_mode argument. Whether those are the best defaults? TBD. But they were the best ideas I had.

Seems reasonable!


JSON linting still very slow on medium size files

Is there an existing issue for this?

[X] I have searched the existing issues. Similar issue https://github.com/super-linter/super-linter/issues/2713 and made comment https://github.com/super-linter/super-linter/issues/2713#issuecomment-1870653818

Current Behavior
I have approximaely 300 mb+ of json files linting in my code base with the biggest files being about 150kb so not huge. This is taking several hours to lint on standard Github runners. A little slow but several hours seems the wrong order of magnitude for JSON linting which should be fairly processor light process.
When debugging is enabled I can see lots of other  linters are running despite only having json linting enabled.
Expected Behavior

Settings show can either enable the linters you want to run or disable the ones you don't. When enabling just JSON linting the expectation would be that only that is run, the majority of use cases of JSON linting do not need to check whether correctly validated as ARM file for example.
Takes a few minutes to run

Super-Linter version
v5.7.2 which as of writing is the latest version

Relevant log output
....

2023-12-27 21:56:33 [DEBUG]   File:[/path/subpath/xxx.json], File_type:[json], Base_file:[xxx.json]
2023-12-27 21:56:33 [DEBUG]   Checking if /path/subpath/xxx.json is an OpenAPI file...
2023-12-27 21:56:33 [DEBUG]   /path/subpath/xxx.json is NOT an OpenAPI descriptor
2023-12-27 21:56:33 [DEBUG]   Checking if /path/subpath/xxx.json is an ARM file...
2023-12-27 21:56:33 [DEBUG]   Checking if /path/subpath/xxx.json is a Cloud Formation file...
2023-12-27 21:56:33 [DEBUG]   Checking if /path/subpath/xxx.json is a AWS states descriptor...

...

Steps To Reproduce
Github Workflow Config
      - name: Lint Code Base
        id: super
        uses<EMAIL_ADDRESS>        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          VALIDATE_ALL_CODEBASE: true
          VALIDATE_JSON: true
          FILTER_REGEX_INCLUDE: (./some_location\/.*)
          ACTIONS_RUNNER_DEBUG: true

Hi @rtk-willm !
Let's try to troubleshoot this issue.
To understand what's happening, we need a few more logs. What I would like to understand is how much time it takes to scan files and to actually lint them.
I'm interested in the timestamps of:

The first log message
The --- ENV (before running linters) --- message
The The script has completed message

Also:

Settings show can either enable the linters you want to run or disable the ones you don't. When enabling just JSON linting the expectation would be that only that is run, the majority of use cases of JSON linting do not need to check whether correctly validated as ARM file for example.

This is already implemented and working as expected, as explained at the bottom of this README section.
What it's not there yet is to avoid potentially expensive I/O operations to get the type of a file if we're not going to lint it anyway. #5094 addresses this particular aspects, but without the data points I pointed out in my previous comment we don't know how much impact it will have on your particular case.

Sorry about slow reply, I couldn't get it to complete on Github runners due to six hour timeout, so couldn't get the information you requested. I spent time configuring to run locally and with the below command
docker run --rm     -e VALIDATE_ALL_CODEBASE=true -e VALIDATE_JSON=true -e FILTER_REGEX_INCLUDE='(./deployments\/f.*)' -e ACTIONS_RUNNER_DEBUG=true -e RUN_LOCAL=true  -w /tmp/lint   -v "$(git rev-parse --show-toplevel)":/tmp/lint github/super-linter:slim-latest > lint_results 2>&1

I got:
The first log message
[0m2024-01-03 18:42:03 ^[[0;34m[DEBUG]^[[0m   Setting FILE_ARRAY_ANSIBLE variable...^[[0m

The --- ENV (before running linters) --- message
[0m2024-01-03 19:06:37 ^[[0;34m[DEBUG]^[[0m   --- ENV (before running linters) ---^[[0

The script has completed message
^[[0m2024-01-03 19:55:50 ^[[0;34m[INFO]^[[0m   The script has completed^[[0m

Whereas if I run this Eslint directly, it is multiple magnitudes faster
time eslint 'deployments/f*.json'

xxx5.json
  13:2  error  Duplicate object key  json/*
  14:2  error  Duplicate object key  json/*
  15:2  error  Duplicate object key  json/*
  16:2  error  Duplicate object key  json/*

✖ 4 problems (4 errors, 0 warnings)

eslint 'deployments/f*.json'  2.96s user 0.32s system 133% cpu 2.469 total

Thanks for these details, these data points are really helpful.
It took about:

23 mins to scan for files: #5094 should mitigate this.
49 mins to lint those files with eslint: I think this is the same as #5043

If you feel adventurous, you test if #5094 has any effect by doing the following:

Clone the super-linter repository:
git clone https://github.com/super-linter/super-linter.git
cd super-linter
git checkout update-detect

Build the super-linter container image (it should take 15ish mins):
make docker

Run super-linter against your code base:

docker run --rm \
  -e VALIDATE_ALL_CODEBASE=true \
  -e VALIDATE_JSON=true \
  -e FILTER_REGEX_INCLUDE='(./deployments\/f.*)' \
  -e ACTIONS_RUNNER_DEBUG=true \
  -e RUN_LOCAL=true  \
  -w /tmp/lint   \
  -v "$(git rev-parse --show-toplevel)":/tmp/lint \
  ghcr.io/super-linter/super-linter:latest > lint_results 2>&1

PS: In your log, what is the version that super-linter reports at the beginning of the log? I expect it to be an old version because the Docker Registry image is not being pushed anymore.

PPS: here are the complete instructions to run super-linter locally: https://github.com/super-linter/super-linter?tab=readme-ov-file#run-super-linter-outside-github-actions

Hi
Here are new results with locally built Docker file
[0m2024-01-04 18:28:05 ESC[0;34m[DEBUG]ESC[0m   Setting FILE_ARRAY_ANSIBLE variable...ESC[0m
...
[0m2024-01-04 18:43:46 ESC[0;34m[DEBUG]ESC[0m   --- ENV (before running linters) ---ESC[0m
...
19:22:46 ESC[0;34m[INFO]ESC[0m   The script has completedESC

So quite a bit faster. Interestingly though if you have a deep look at the logs you can see with super-linter that each files is being linted in the range 1-2s
ESC[0m2024-01-04 18:43:46 ESC[0;34m[DEBUG]ESC[0m   Linting FILE: /tmp/lint/deployments/xxxx.jsonESC[0m
ESC[0m2024-01-04 18:43:46 ESC[0;34m[DEBUG]ESC[0m   FILE_STATUS (xxxx.json) is empty, or not set to 'good' or 'bad'. Assuming it should be linted correctly. Setting FILE_STATUS to 'good'...ESC[0m
ESC[0m2024-01-04 18:43:46 ESC[0;34m[DEBUG]ESC[0m   File: /tmp/lint/deployments/xxxx.json, FILE_NAME: xxxx.json, DIR_NAME:/tmp/lint/deployments, FILE_STATUS: good, INDIVIDUAL_TEST_FOLDER: json, TEST_CASE_DIRECTORY: test/linters/jsonESC[0m
ESC[0m2024-01-04 18:43:46 ESC[0;34m[DEBUG]ESC[0m   Updated TEST_CASE_DIRECTORY for JSON to: test/linters/json/ESC[0m
ESC[0m2024-01-04 18:43:46 ESC[0;34m[INFO]ESC[0m   ---------------------------ESC[0m
ESC[0m2024-01-04 18:43:46 ESC[0;34m[INFO]ESC[0m   File:[/tmp/lint/deployments/xxxx.json]ESC[0m
ESC[0m2024-01-04 18:43:48 ESC[0;34m[INFO]ESC[0m    - File:ESC[0;37m[xxxx.json]ESC[0;34m was linted with ESC[0;37m[eslint]ESC[0;34m successfullyESC[0m
ESC[0m2024-01-04 18:43:48 ESC[0;34m[DEBUG]ESC[0m   Error code: 0. Command output:ESC[0m

Whereas after enabling more debugging information in ESlint this appears to be in ms range
2024-01-04T20:14:28.628Z eslint:file-enumerator Yield: xxxxx.json
2024-01-04T20:14:28.628Z eslintrc:cascading-config-array-factory Load config files for xxxxxxxx.
2024-01-04T20:14:28.628Z eslintrc:cascading-config-array-factory Cache hit: xxxxxxxx.
2024-01-04T20:14:28.628Z eslint:cli-engine Lint xxxxxxxx/xxxxx.json
2024-01-04T20:14:28.628Z eslint:linter Linting code for xxxxxxxx/xxxxx.json (pass 1)
2024-01-04T20:14:28.629Z eslint:linter Verify
2024-01-04T20:14:28.629Z eslint:linter With ConfigArray: xxxxxxxx/xxxxx.json
2024-01-04T20:14:28.629Z eslint:linter Apply the processor: 'json/.json'
2024-01-04T20:14:28.631Z eslint:linter A code block was found: '(unnamed)'
2024-01-04T20:14:28.633Z eslint:linter Parsing: xxxxxxxx/xxxxx.json
2024-01-04T20:14:28.634Z eslint:linter Parsing successful: xxxxxxxx/xxxxx.json
2024-01-04T20:14:28.634Z eslint:linter Scope analysis: xxxxxxxx/xxxxx.json
2024-01-04T20:14:28.635Z eslint:linter Scope analysis successful: xxxxxxxx/xxxxx.json
2024-01-04T20:14:28.640Z eslint:linter Generating fixed text for xxxxxxxx/xxxxx.json (pass 1)
2024-01-04T20:14:28.640Z eslint:source-code-fixer Applying fixes
2024-01-04T20:14:28.640Z eslint:source-code-fixer shouldFix parameter was false, not attempting fixes
2024-01-04T20:14:28.640Z eslintrc:ignore-pattern Check {
  filePath: 'xxxxxxxx/xxxxxxx.json',
  dot: false,
  relativePath: 'deployments/xxxxxxx.json',
  result: false
}

Thanks for the additional data points! They are quite useful.
At least that PR had some effect on the file scan (23 mins vs 15 mins), but it's way too much. Is there a chance you can share the log, so that I can have a look at why it's taking this long for the file scan?
For the linting step, I think we're paying the performance tax to start eslint once per file.
We need to fix both issues.

hey no problem. Happy to answer questions about logs but I can't share entire logs as likely have sensitive data in them.

That's what I imagined :)
I'll see if I can generate some JSON files to reproduce the issue.
Does super-linter report any validation errors? I suppose that this doesn't influence the total run time.

sorry 😄 , I did have a look at generating random JSON myself with something like https://github.com/Ankur-Jat/random-json-generator/tree/master but haven't had time yet

Well, I went the simple route I guess :)
for i in {1..2000}; do
  {
    printf '{"random_numbers": ['
    shuf -i 1-10000000 | head -c 149500 | tr '\n' ','
    printf '1]}\n'
  } > "file_$i.json"
done

nice, how did that go? There must be some start costs of running the linters individually I expect. As to your question before about errors (sorry I missed it), there were a couple of errors out of about 70k files. They didn't seem to have any effect on speed of running eslint directly though :)

With 2000 JSON files, the file listing step completes in under a minute after the optimizations in #5094, so I suppose that's beneficial.
ESlint invocations take a lot of time, file by file so that's an area to improve. I'll think about how to solve this. :)

okay thankyou

Status update: I've sent a few preliminary PRs to pave the way for a scalable and maintainable solution to this issue.

brilliant, thanks very much 🙏

@kftsehk I think is a case for implementing batched (and eventually parallel) support. I'll recover your work in a draft PR so we can collaborate on that one. Thanks for putting it together!

Quick update: we are almost done with the preparatory PRs!

We finally have a PR to (hopefully) fix this, and make the whole process way quicker! #5177

brilliant, thanks for all your hard work @ferrarimarco 🙏

👍
You can try the changes if you want: follow the steps in https://github.com/super-linter/super-linter/issues/5073#issuecomment-1876713819, but checkout the parallel-batched branch instead of the update-detect one. Thanks!

hey, thanks for the tip. I tried it a few times but unfortunately for some reason the perl install and build section keeps failing for me and haven't worked with perl much myself
Dockerfile:171
--------------------
 170 |     ##############################
 171 | >>> RUN apk add --no-cache --virtual .perl-build-deps \
 172 | >>>     gcc \
 173 | >>>     make \
 174 | >>>     musl-dev \
 175 | >>>     perl-dev \
 176 | >>>     && curl --retry 5 --retry-delay 5 -sL https://cpanmin.us/ \
 177 | >>>     | perl - -nq --no-wget \
 178 | >>>     Perl::Critic \
 179 | >>>     Perl::Critic::Bangs \
 180 | >>>     Perl::Critic::Community \
 181 | >>>     Perl::Critic::Lax \
 182 | >>>     Perl::Critic::More \
 183 | >>>     Perl::Critic::StricterSubs \
 184 | >>>     Perl::Critic::Swift \
 185 | >>>     Perl::Critic::Tics \
 186 | >>>     && apk del --no-network --purge .perl-build-deps
 187 |
--------------------
ERROR: failed to solve: process "/bin/bash -o errexit -o nounset -o pipefail -c apk add --no-cache --virtual .perl-build-deps     gcc     make     musl-dev     perl-dev     && curl --retry 5 --retry-delay 5 -sL https://cpanmin.us/     | perl - -nq --no-wget     Perl::Critic     Perl::Critic::Bangs     Perl::Critic::Community     Perl::Critic::Lax     Perl::Critic::More     Perl::Critic::StricterSubs     Perl::Critic::Swift     Perl::Critic::Tics     && apk del --no-network --purge .perl-build-deps" did not complete successfully: exit code: 60
make: *** [docker] Error 1

Ah! Thanks for trying. I don't see that error when building the image. Hopefully it's transient. Let's see...

hmm not sure, have tried several times. I am on a non M1 mac if that context helps at all 🤷♂


Mediapipe effect renderer(face effect) module using python or C/C++

Hello,
I am working on a project that uses a mediapipe to give a face effect.
Is there any way I can use mediapipe's effect renderer module (calculator, https://github.com/google/mediapipe/blob/master/mediapipe/modules/face_geometry/effect_renderer_calculator.cc) in python or C/C++?
If possible, we want information about the pipeline that uses the effect renderer module.
Thank you

Hi @locoChan ,did you a get chance to check this issue.

Sorry for the late reply.
https://github.com/google/mediapipe/issues/1155#issuecomment-995079150
I have already seen this content, and I thought that maybe the Python API is not provided.
Is that right?
I want to study an example of the effect renderer module operated on the desktop.
Again, sorry for the late reply.

Why can't just provide an example of C++, as your open source project is specifically designed to create pitfalls for people?


Adding Openshift Origin v3.7.2, and defaulting to it

yet another update :rice_cracker:

I just published this to the galaxy as v1.0.6. Thanks for the contribution!


Date/time for planner

Implement planner/date_util.js

implemented, but still needs work to get rid of '13 PM' cause we don't need that

13 PM Issue resolved
How about 12am should go to the top like the image below? As 12am (0:00) is next day, I think 12am should start a day, not 1am.

will do

13PM fixed, changed to 12AM at beginning

Very impressive! Will mark as fixed.


dropdown default positioning bleeds over selectivity element

Dropdown does not stick under Selectivity element but bleeds over the element when the dropdown does not fit to the space between the selectivity element and browser window bottom.
This can be tested in https://arendjr.github.io/selectivity/ with the first selectivity selector by placing it near of the browser window bottom.
Should this kind of functionality be a configuration. e.g. fit-in-browser-space: true/false?

This is currently done by design so that the user does not have to scroll. Why exactly would you not want this?

Btw, the behavior can already be customized by passing a custom positionDropdown function with the options. It's not as simple as a boolean option, but allows complete freedom if you like different placement behavior.

It's a matter of ux design and style guides. Even though it's easier to use for the user, it might confuse the user where the actual select box disappeared and it also hides the selected value.
I might be too used to "standard" select functionality that this design felt odd.
Thanks from the hint that I can customize the functionality.

Cool. I take it I can close this?
Btw, regarding your comment that it hides the selected value, there's also #78 which I intent to fix soon, so hopefully that shouldn't be a concern then anymore either.
Cheers!

I would still like to see this as a setting which you could be toggled. So maybe a renaming the issue and tagging it to a feature?
At least then this kind of functionality wouldn't feel odd to old school users ;).
I don't consider this a high priority feature since creating a workaround by overriding the position function isn't that hard.

the replacement was easier than I expected. All I needed to do was to replace positionDropdown with an empty function.

Hm, that's interesting :) The default implementation certainly does more than replacement if there isn't sufficient height, though I can understand the default positioning being kinda okay in some situations... Isn't the width wrong, for instance?

Yeah, I had to hack it abit more :)
          var selectHeight = $selectEl.height()
          var position = $selectEl.position()
          $el.css({
            left: position.left + 'px',
            top: (position.top + selectHeight) + 'px'
          }).width(width - 2)


android编译缺少头文件

修复android编译不通过

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

确实 这个修改可以不加宏 因为这个头文件是标准的


fix: dotnet-uno: missing UNO_DISABLE_OPENGL env var on prod Dockerfile

Signed-off-by: Andre Riesco<EMAIL_ADDRESS>Related-to: TOR-2443

@andreriesco you tested Debug one?

@andreriesco you tested Debug one?

Yes, the debug one doesn't have this problem because it defines this variable on the launch.json file


use Bound instead of PyObject where possible

Change Summary
Micro-optimization which should make Clone / Drop implementations more efficient in function stacks. Hopefully reduces binary size a bit / allows better unwinding on early returns.
Related issue number

Checklist

[ ] Unit tests for the changes exist
[ ] Documentation reflects the changes where applicable
[ ] Pydantic tests pass with this pydantic-core (except for expected changes)
[ ] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

I think one day I'll make PyO3 nudge to do this by better traits; I might save the work here until PyO3 supports this more. This does just fractionally help perf but it's not hugely relevant at all compared to lower hanging fruit.


Language selection more prominent (native/mobile)

Problem
We got feedback that the language selection is not prominent enough while being one of the most important features in the app.
We don't really know which is the best solution here so we want to do a user testing.
Possible ideas

Display additional information in the header (less space, more prominent):

Flag (e.g. Germany for German) -> no clear matching for all languages, e.g. German also spoken in Austria and Switzerland
Language code (e.g. de for German, ckb for Sorani) -> do all users now the codes? 2 vs. 3 letter codes, special codes such as German simple
Full language name (e.g. German) -> less space
Just the icon (perhaps replaced by the google translate icon) -> do all users understand it?

Keep it in the overflow menu/kebab menu -> not prompinent

Related issues
Desktop issue: #2831.
Additional information
See discussion below. Possible designs are shown here
Old Description
I have received feedback from the project "Digital Active Women": Changing the language is one of the most important technical functionalities of our Web App (maybe not so much for the Integreat App as languages are saved?). The button, however, can be a little hard to find and/or identify as the language change button. Not neccesarily a change we need to make, but at least should think about: Could we use text here or any other visible distinguisher to emphasize the language change more?

We have received a similar feedback from municipality survey #2656

@dkehne @clarabracklo this only concerns the web app, right? Because in the old ticket #2656 Daniel mentioned the same problem in the "app". I don't know if you mean native or web. Because for native the language is presetted from the device settings. So language change is a rare use case normally.

@nikolahoff Initially this feedback came up regarding the mobile app. I have observed that there are quite a few people using their phones in English/German (device settings). I am not sure why that is - maybe wanting to improve the language skills. But they still want to access Integreat in their own language.

Here are the design proposals for Desktop and Mobile

I like v2 more than v1. Good drafts!

I think this is a good proposal for Desktop. Sadly I am not that sure about mobile/native, as space in the header is very limited... Especially if we have long city names, I don't think there is enough space to show the language icon and a two to three letter code. Also I am not sure if everybody knows what less common codes like ckb stand for :see_no_evil:

ok, good point about the limited space. Another option would be to use a flag, because it's also a common and known way to change language. Maybe it's more obvious than the worls icon.

Thanks for your thoughts and designs. I think the web design v2 (but with an icon and not the flag) is nice and we can implement it.
Problems with flags: Languages do not always match with countries and I think its quite hard to use flags for languages without fretting someone. For German this is still relatively easy (even though there is also Switzerland and Austria) but for other languages this gets a lot harder. Probably there is even countries where two languages are mainly spoken...
We talked about this and we thought that maybe another icon could solve this problem to some extent? E.g. youtube, google translate and wikipedia use this icon:

Since google translate is probably really well known, this could make it clearer.
I am not sure if we want to move the icon on mobile out of the sidebar/kebap menu as this issue is mostly about desktop.  Maybe we should do a user testing here though.
To summarize:

Web is fine (I prefer v2 without flags and perhaps the other icon)
I think we should not use flags
We can think of changing the icon
We should evaluate whether the language change needs to be more prominent on mobile (since we have limited space and we don't have real feedback for either)

@steffenkleinle your considerations are important and sensible, the proposed icon corresponds to best practice in other applications. if the icon is to correspond to the respective language, I would alternatively recommend Language Initials (DE for german, EN for english, etc.) in Bold (font style). both options are great.

@steffenkleinle your considerations are important and sensible, the proposed icon corresponds to best practice in other applications. if the icon is to correspond to the respective language, I would alternatively recommend Language Initials (DE for german, EN for english, etc.) in Bold (font style). both options are great.

Thanks! Do we know whether the initials of lesser known languages are well known of users, e.g. ckb (Sorani). Maybe this would be a question to be asked in the target group.

I guess this is not really a problem, because when you have chosen the language you know what it stands for. And the menu that pops open for selecting the language has the whole word written.

@nikolahoff @steffenkleinle I agree, it would definitely be necessary to provide both the initials of the language and the written out language.

I guess this is not really a problem, because when you have chosen the language you know what it stands for.

Hmm not sure about that:

Users don't have to "choose" a language, it is initialized from their system language. So it might just be ckb from the start without them knowing what it means.
I think the connection from selecting Sorani to it showing ckb is not necessarily clear, I am not sure if we can assume that everybody who selects Sorani knows that ckb is its language code. Especially because there are different languages codes, e.g. for Farsi there is fa and per... https://iso639-3.sil.org/code/per

And the menu that pops open for selecting the language has the whole word written.

Agreed, no problem there.

Let's discuss this in our meeting today if we have time or we schedule another meeting.

As discussed in our meeting we develop first the desktop version, which you can find here
The mobile version needs a testing before implementing a new solution.

As discussed in our meeting we develop first the desktop version, which you can find here The mobile version needs a testing before implementing a new solution.

@nikolahoff so we want to keep the current globe icon?

Yes for now until we did the user testing with new icon versions. On desktop there is the language written besides the icon, so it is understandable. Thats why we wanted to develop desktop already and wait with the mobile version after the testing.

FYI: The user testing, Julia and Leonie did showed that 15 of 17 users were able to change language. @steffenkleinle

So, looks like we can leave the language change the way it is in mobile and it has been changed in the desktop version in https://github.com/digitalfabrik/integreat-app/issues/2831
It looks to me like this issue is finished for now. Other opinions?


"Failed to connect to proxy" error="websocket: bad handshake" while importing existing k8s cluster

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
2 K8s clusters are created on VirtualBox.
Cluster 1 VMs. Kmaster, knode1, knode1
Cluster 2 VMs. Kmd, kn1, kn2
kubectl v1.14.2 on all vms
Rancher container is up using below command in kmd(Master of cluster 2).
docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -v /home//rancher:/var/lib/rancher rancher/rancher:latest
Rancher 2.2.3 is running.
Imported cluster 2 successfully in rancher.
When I try to import cluster 1, it is in "Pending" state.
I tried removing cattle-system namespace re-creating cattle pods, but it did not help.
Result:
on kmaster
kubectl get pods -o wide --all-namespaces
NAMESPACE        NAME                                     READY   STATUS             RESTARTS   AGE     IP             NODE   NOMINATED NODE   READINESS GATES
cattle-system    cattle-cluster-agent-59c8cc49d5-st9qm    1/1     Running            6          2d1h    <IP_ADDRESS>   kn2
cattle-system    cattle-node-agent-fz7w6                  1/1     Running            6          2d1h    <IP_ADDRESS>   kn1
cattle-system    cattle-node-agent-t5v22                  1/1     Running            6          2d1h    <IP_ADDRESS>   kn2

In Rancher UI, I see below.
This cluster is currently Pending; areas that interact directly with it will not be available until the API is ready.
Response in Kmaster (Cluster 1 master)
kubectl logs pod/cattle-cluster-agent-59c8cc49d5-st9qm  -n cattle-system
W0611 15:19:35.167659       1 reflector.go:270] github.com/rancher/norman/controller/generic_controller.go:175: watch of *v1.Endpoints ended with: too old resource version: 164863 (164880)
W0611 15:43:00.204276       1 reflector.go:270] github.com/rancher/norman/controller/generic_controller.go:175: watch of *v1.Endpoints ended with: too old resource version: 166576 (167240)
W0611 16:05:10.316230       1 reflector.go:270] github.com/rancher/norman/controller/generic_controller.go:175: watch of *v1.Endpoints ended with: too old resource version: 168914 (169454)
kubectl -n cattle-system logs -l app=cattle-agent
time="2019-06-11T13:14:12Z" level=info msg="Option requestedHostname=kn2"
time="2019-06-11T13:14:12Z" level=info msg="Listening on /tmp/log.sock"
time="2019-06-11T13:14:13Z" level=info msg="Connecting to wss://<IP_ADDRESS>/v3/connect with token vhdkjsdcn22lkr9dc9p55lglzqgjxzflk9gv4v95dwprbrtvj979tq"
time="2019-06-11T13:14:13Z" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>/v3/connect"
time="2019-06-11T13:14:13Z" level=info msg="Starting plan monitor"
Other details that may be helpful:
on kmaster, I am able to curl k8s api.
curl --insecure -Iv http://<IP_ADDRESS>:443

Expire in 0 ms for 6 (transfer 0x556ad9bc35c0)
Trying <IP_ADDRESS>...
TCP_NODELAY set
Expire in 200 ms for 4 (transfer 0x556ad9bc35c0)
Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 443 (#0)

HEAD / HTTP/1.1
Host: <IP_ADDRESS>:443
User-Agent: curl/7.64.0
Accept: /

Closing connection 0
curl: (8) Weird server reply

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):

Installation option (single install/HA):
Single install

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):VM
Kubernetes version (use kubectl version):1.14

(paste the output here)

Docker version (use docker version):
ocker version
Client:
Version:           18.09.5
API version:       1.39
Go version:        go1.10.4
Git commit:        e8ff056
Built:             Fri Apr 12 00:34:27 2019
OS/Arch:           linux/amd64
Experimental:      false

Server:
Engine:
Version:          18.09.5
API version:      1.39 (minimum version 1.12)
Go version:       go1.10.4
Git commit:       e8ff056
Built:            Fri Apr 12 00:27:37 2019
OS/Arch:          linux/amd64
Experimental:     false
(paste the output here)

resolved. missed to bind role.

i have the same issue

Same issue

same issue with rancher v2.2.6

same issue with rancher v2.2.5

same issue with rancher v2.2.7
The main problem is that there isn't enough information for debugging this issue.

A potential solution for some folks: https://github.com/rancher/rancher/issues/20651#issuecomment-528683673


Question: How to type "a color"?

This is just running fine:
const DEFAULT_COLORS: [string, string, string] = ['white', 'yellow', 'red'];
console.log(pc[DEFAULT_COLORS[1]]('sad'));

https://codesandbox.io/p/sandbox/picocolors-types-29zfg9?file=%2Fsrc%2Findex.ts%3A11%2C1
But how to type this correct?
For DEFAULT_COLORS[1]
I get this:
// Element implicitly has an 'any' type because expression of
// type 'string' can't be used to indextype
// 'Colors & { createColors: (enabled?: boolean | undefined) => Colors; }'.
//  No index signature with a parameter of type 'string' was
// found on type 'Colors & { createColors: (enabled?: boolean | undefined) => Colors; }'.

Problem is that a user can just overwrite colors by using own colors handed in as strings. So I'm trying to stick to that.

You can define a Color type as a key of the package object
import pc from "picocolors";

type Color = keyof typeof pc;

const DEFAULT_COLORS: [Color, Color, Color] = ["white", "yellow", "red"];

Thanks for your reply!
Unfortunately with this I get an error and no more output:
This expression is not callable.
  Not all constituents of type 'boolean | Formatter | ((enabled?: boolean) => Colors)' are callable.
    Type 'false' has no call signatures.typescript(2349)
const DEFAULT_COLORS: [keyof Colors | "createColors", keyof Colors | "createColors", keyof Colors | "createColors"]

Update the sandbox:
https://codesandbox.io/p/sandbox/picocolors-types-29zfg9?file=%2Fsrc%2Findex.ts%3A7%2C1


Add installation documentation

Still haven't finished rewriting the course management script documentation, but I wanted to get it done before 8AM. I'll finish cleaning up the documentation for course management later today.

Also add this if you have time: "uninstalling ngshare"

Codecov Report

Merging #106 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #106   +/-   ##
=======================================
  Coverage   99.76%   99.76%
=======================================
  Files          12       12
  Lines        1709     1709
=======================================
  Hits         1705     1705
  Misses          4        4

Continue to review full report at Codecov.

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


Loader issue in SPFx while using react-image-focal-point

Node Version 16
React Version 17.0.1
npm 8.19.2

I've got the same issue. Did you manage to fix it?

Do you have some codesandbox or similar to reproduce the issue? With that info we don't know if the issue is in the library

I'm building it locally, I'm running it on node version 16.16.0 React Version 16.8.5, npm version 6.14.12.


Update cryptography version to 39

Description
Bump cryptography from 3.3.2 to 39.0.1 in /contributions
Acceptance Criteria
Cryptography version updated in contributions requirements.txt and auth_middleware setup.py
Contributions BB and catalog BB runs fine in docker and python.

Deployed contributionsBB to develop.
Tested in dev instance. Works fine.


Should use Record as type instead Object

Refer to the typescript-eslint rule ban-types. Use Record<string, unknown> as type instead of Object or object.

Thanks for the PR! It will however conflict with #1424 where this is also adressed. There I'm using template literal types so that object keys needs to be on the model or in a deep structure of the object (for example, passing  {"address.city": "London"} is ok if the the model has {address: { city: string }}).


Fix noise offset not affecting domain warp

Fixes #61160.
I also added domain warp to get_noise_1d() where it was missing.

Thanks!

Thank you for fixing this so quickly!


Consider setting ExecutionInput.Locale property automatically

ExecutionInput has a Locale property. Assuming spring (boot) populates a Locale it should be set automatically.

For Spring MVC this can be probably be based on AcceptHeaderLocaleResolver, i.e. "Accept-Language" header via request.getLocales() with a fallback on Boot's "spring.mvc.locale" property. For WebFlux, similar logic based directly on the "Accept-Language" request header.


Change to make ZK connection more robust. issue 353

Draft PR for comments
Making the ZooKeeper connect a bit more robust. Based on ZOOKEEPER-1057 looks like if there is a failure with connecting to first node in the ZK host names passed i.e it is down, then connection seem to fail even though there is a ZK quorum.

Hi @bijugs can this code be moved to locking_restart now that all locking code is there? For format zkfc, perhaps we can make a clean API from locking resource for it to use so we don't have duplicate code (or we just accept duplication for now).

@bijugs Please commit this to  bloomberg/locking_resource-cookbook; closing here as no-longer applicable.


gaussian_dlm_obs should allow nonnegative-definite matrices

Summary:
Although it is not specified in the manual, gaussian_dlm_obs() gives an error if the C0 argument is nonnegative definite instead of positive definite.
Description:
The C0 argument is the prior covariance matrix for the latent state vector. It is perfectly legitimate, and sometimes useful, for C0 (likewise W) to be merely nonnegative-definite instead of positive definite.
Not sure if this should be a bug or an enhancement request, but at a minimum the manual should make it clear when nonnegative-definite is not good enough.
Reproducible Steps:
Program:
data {
  int<lower = 1> N;
  vector[N] y;
  real<lower = 0.0, upper = 1.0> rho_;
  real mu_;
  real<lower = 0.0> sigma_;
  real<lower = 0.0> sigma_h_scale_;
}
transformed data {
  matrix[1, N] yy = to_matrix(y');
  vector[2] Z_0_ = to_vector({1.0, 1.0});
  vector[2] a1_0_ = to_vector({0.0, mu_});
  matrix[2, 2] P1_0_ = diag_matrix(to_vector({square(sigma_), 0.0}));
}
parameters {
  real<lower = 0.0> raw_0_;
}
transformed parameters {
}
model {
  real sigma_h_ = raw_0_ * sigma_h_scale_;
  real phi_ = sqrt(1.0 - square(rho_));
  real H_0_ = square(sigma_h_);
  matrix[2, 2] T_0_ = diag_matrix(to_vector({phi_, 1.0}));
  matrix[2, 2] Q_0_ = diag_matrix(to_vector({square(rho_ * sigma_), 0.0}));
  raw_0_ ~ normal(0.0, 1.0) T[0.0, ];
  yy ~ gaussian_dlm_obs(to_matrix(Z_0_), T_0_, rep_matrix(H_0_, 1, 1), Q_0_, a1_0_, P1_0_);
}

data:
list(
  N=100,
  y=c(118, 123, 123, 125, 131, 103, 103, 112, 89, 99, 96, 100, 107, 80, 91, 110, 98, 115, 98, 81, 86, 82, 74, 81, 72, 95, 94, 120, 83, 59, 79, 60, 79, 81, 100, 111, 50, 112, 103, 86, 93, 106, 91, 114, 122, 82, 113, 92, 102, 99, 100, 128, 113, 96, 116, 116, 93, 123, 104, 107, 120, 114, 136, 95, 136, 140, 132, 145, 151, 139, 136, 123, 148, 115, 117, 143, 132, 118, 101, 106, 122, 119, 78, 98, 133, 109, 117, 129, 125, 112, 133, 113, 80, 128, 135, 137, 150, 141, 142, 131),
  rho_=0.1,
  mu_=100,
  sigma_=50,
  sigma_h_scale_=30)

Current Output:
Rejecting initial value:
  Error evaluating the log probability at the initial value.
Exception: gaussian_dlm_obs_lpdf: C0 is not positive definite.

Current Version:
v2.17

I had to look up in the Wikipedia to figure out "positive semidefinite" and "nonnegative definite" are synonyms.
Is this one of these cases where semidefiniteness means that normalization is over some subspace?

Nonnegative definiteness means that eigenvalues are all nonnegative. The zero eigenvalues correspond to things known with complete certainty. The most common way this can arise is if the initial value of element k of the latent state is known with certainty to be mu[k]; then both column and row k of C0 are all zeroes.


Android ExoPlayer picks up textTracks but they are not shown on the screen when selected.

Current behavior
Subtitles appear after onLoad in textTracks, but they do not come up in screen. This started happening after latest release.
Reproduction steps
Load a video with subtitles, and choose the textTrack you'd like to display.
Expected behavior
You see the subtitles on screen.
Platform
Which player are you experiencing the problem on:

Android ExoPlayer

I believe this might be an issue with my video since it's not getting picked up by other hls video players either.


Failing to build ZLUDA

System:
Ubuntu22.04

(base) r4-0@r40-desktop:~/ZLUDA$ cargo xtask --release
    Updating crates.io index
  Downloaded bitflags v2.4.1
  Downloaded argh_shared v0.1.12
  Downloaded adler v1.0.2
  Downloaded time-core v0.1.1
  Downloaded num_threads v0.1.7
  Downloaded cfg-if v1.0.0
  Downloaded filetime v0.2.23
  Downloaded errno v0.3.8
  Downloaded cargo_metadata v0.17.0
  Downloaded itoa v1.0.10
  Downloaded camino v1.1.6
  Downloaded argh v0.1.12
  Downloaded cargo-platform v0.1.5
  Downloaded argh_derive v0.1.12
  Downloaded thiserror v1.0.51
  Downloaded xattr v1.2.0
  Downloaded quote v1.0.33
  Downloaded thiserror-impl v1.0.51
  Downloaded semver v1.0.20
  Downloaded miniz_oxide v0.7.2
  Downloaded serde_derive v1.0.193
  Downloaded crc32fast v1.4.0
  Downloaded proc-macro2 v1.0.70
  Downloaded tar v0.4.40
  Downloaded unicode-ident v1.0.12
  Downloaded ryu v1.0.16
  Downloaded cc v1.0.83
  Downloaded serde v1.0.193
  Downloaded flate2 v1.0.29
  Downloaded cloudflare-zlib-sys v0.3.3
  Downloaded serde_json v1.0.108
  Downloaded time v0.3.23
  Downloaded syn v2.0.41
  Downloaded rustix v0.38.28
  Downloaded libc v0.2.151
  Downloaded linux-raw-sys v0.4.12
  Downloaded 36 crates (4.1 MB) in 0.81s (largest was `linux-raw-sys` at 1.5 MB)
   Compiling proc-macro2 v1.0.70
   Compiling unicode-ident v1.0.12
   Compiling serde v1.0.193
   Compiling libc v0.2.151
   Compiling cfg-if v1.0.0
   Compiling rustix v0.38.28
   Compiling crc32fast v1.4.0
   Compiling bitflags v2.4.1
   Compiling serde_json v1.0.108
   Compiling linux-raw-sys v0.4.12
   Compiling thiserror v1.0.51
   Compiling camino v1.1.6
   Compiling semver v1.0.20
   Compiling ryu v1.0.16
   Compiling adler v1.0.2
   Compiling itoa v1.0.10
   Compiling num_threads v0.1.7
   Compiling miniz_oxide v0.7.2
   Compiling time-core v0.1.1
   Compiling quote v1.0.33
   Compiling syn v2.0.41
   Compiling cc v1.0.83
   Compiling filetime v0.2.23
   Compiling time v0.3.23
   Compiling xattr v1.2.0
   Compiling tar v0.4.40
   Compiling cloudflare-zlib-sys v0.3.3
   Compiling serde_derive v1.0.193
   Compiling thiserror-impl v1.0.51
   Compiling flate2 v1.0.29
   Compiling argh_shared v0.1.12
   Compiling cargo-platform v0.1.5
   Compiling argh_derive v0.1.12
   Compiling cargo_metadata v0.17.0
   Compiling argh v0.1.12
   Compiling xtask v0.0.0 (/home/r4-0/ZLUDA/xtask)
    Finished dev [unoptimized + debuginfo] target(s) in 3m 46s
     Running `target/debug/xtask --release`
  Downloaded allocator-api2 v0.2.16
  Downloaded arrayref v0.3.7
  Downloaded scroll_derive v0.11.1
  Downloaded sha2 v0.10.8
  Downloaded arrayvec v0.7.4
  Downloaded anyhow v1.0.79
  Downloaded ahash v0.8.7
  Downloaded crunchy v0.2.2
  Downloaded cloudflare-zlib v0.2.10
  Downloaded enum-iterator v1.5.0
  Downloaded phf_shared v0.10.0
  Downloaded tinyvec_macros v0.1.1
  Downloaded new_debug_unreachable v1.0.4
  Downloaded smallvec v1.11.2
  Downloaded slab v0.4.9
  Downloaded num_enum_derive v0.4.3
  Downloaded equivalent v1.0.1
  Downloaded precomputed-hash v0.1.1
  Downloaded percent-encoding v2.3.1
  Downloaded dirs-sys-next v0.1.2
  Downloaded cmake v0.1.50
  Downloaded block-buffer v0.10.4
  Downloaded bit-set v0.5.3
  Downloaded bit-vec v0.6.3
  Downloaded ascii-canvas v3.0.0
  Downloaded cpufeatures v0.2.11
  Downloaded string_cache v0.8.7
  Downloaded thread-id v4.2.1
  Downloaded subtle v2.5.0
  Downloaded static_assertions v1.1.0
  Downloaded siphasher v0.3.11
  Downloaded const_format_proc_macros v0.2.32
  Downloaded autocfg v1.1.0
  Downloaded crypto-common v0.1.6
  Downloaded convert_case v0.5.0
  Downloaded constant_time_eq v0.2.6
  Downloaded memoffset v0.8.0
  Downloaded enum-iterator-derive v1.3.0
  Downloaded form_urlencoded v1.2.1
  Downloaded generic-array v0.14.7
  Downloaded ena v0.14.2
  Downloaded dynasmrt v1.2.3
  Downloaded byteorder v1.5.0
  Downloaded fallible-streaming-iterator v0.1.9
  Downloaded unicode-xid v0.2.4
  Downloaded either v1.9.0
  Downloaded digest v0.10.7
  Downloaded dirs-sys v0.3.7
  Downloaded is-terminal v0.4.9
  Downloaded plain v0.2.3
  Downloaded lalrpop-util v0.20.0
  Downloaded pkg-config v0.3.29
  Downloaded tiny-keccak v2.0.2
  Downloaded version_check v0.9.4
  Downloaded fallible-iterator v0.2.0
  Downloaded getset v0.1.2
  Downloaded paste v1.0.14
  Downloaded time-macros v0.2.10
  Downloaded fixedbitset v0.4.2
  Downloaded rustversion v1.0.14
  Downloaded dirs-next v2.0.0
  Downloaded pico-args v0.5.0
  Downloaded scopeguard v1.2.0
  Downloaded rustc-hash v1.1.0
  Downloaded fastrand v2.0.1
  Downloaded lazy_static v1.4.0
  Downloaded capnpc v0.17.2
  Downloaded dirs v4.0.0
  Downloaded memmap2 v0.5.10
  Downloaded lock_api v0.4.11
  Downloaded jobserver v0.1.27
  Downloaded hashlink v0.8.4
  Downloaded scroll v0.11.0
  Downloaded proc-macro-error-attr v1.0.4
  Downloaded tempfile v3.8.1
  Downloaded log v0.4.20
  Downloaded libloading v0.8.1
  Downloaded parking_lot_core v0.9.9
  Downloaded term v0.7.0
  Downloaded proc-macro-crate v0.1.5
  Downloaded once_cell v1.19.0
  Downloaded proc-macro-error v1.0.4
  Downloaded bitflags v1.3.2
  Downloaded crossbeam-utils v0.8.17
  Downloaded vergen v7.5.1
  Downloaded derivative v2.2.0
  Downloaded parking_lot v0.12.1
  Downloaded diff v0.1.13
  Downloaded typenum v1.17.0
  Downloaded toml v0.5.11
  Downloaded tinyvec v1.6.0
  Downloaded half v1.8.2
  Downloaded num-traits v0.2.17
  Downloaded indexmap v2.1.0
  Downloaded aho-corasick v1.1.2
  Downloaded cpp_demangle v0.3.5
  Downloaded unicode-bidi v0.3.15
  Downloaded url v2.5.0
  Downloaded const_format v0.2.32
  Downloaded crossbeam-channel v0.5.9
  Downloaded unicode-normalization v0.1.22
  Downloaded dynasm v1.2.3
  Downloaded memchr v2.6.4
  Downloaded capnp v0.17.2
  Downloaded libm v0.2.8
  Downloaded zerocopy v0.7.32
  Downloaded hashbrown v0.14.3
  Downloaded rusqlite v0.28.0
  Downloaded goblin v0.5.4
  Downloaded itertools v0.10.5
  Downloaded blake3 v1.3.3
  Downloaded vcpkg v0.2.15
  Downloaded syn v1.0.109
  Downloaded petgraph v0.6.4
  Downloaded git2 v0.16.1
  Downloaded lalrpop v0.20.0
  Downloaded regex v1.10.2
  Downloaded idna v0.5.0
  Downloaded regex-syntax v0.7.5
  Downloaded regex-syntax v0.8.2
  Downloaded lz4-sys v1.9.4
  Downloaded regex-automata v0.4.3
  Downloaded num_enum v0.4.3
  Downloaded libgit2-sys v0.14.2+1.5.1
  Downloaded libz-sys v1.1.15
  Downloaded libsqlite3-sys v0.25.2
  Downloaded 126 crates (17.8 MB) in 1.94s (largest was `libsqlite3-sys` at 4.8 MB)
   Compiling libc v0.2.151
   Compiling proc-macro2 v1.0.70
   Compiling version_check v0.9.4
   Compiling unicode-ident v1.0.12
   Compiling syn v1.0.109
   Compiling pkg-config v0.3.29
   Compiling vcpkg v0.2.15
   Compiling autocfg v1.1.0
   Compiling cfg-if v1.0.0
   Compiling serde v1.0.193
   Compiling typenum v1.17.0
   Compiling unicode-xid v0.2.4
   Compiling hip_runtime-sys v0.0.0 (/home/r4-0/ZLUDA/hip_runtime-sys)
   Compiling once_cell v1.19.0
   Compiling memchr v2.6.4
   Compiling zerocopy v0.7.32
   Compiling ahash v0.8.7
   Compiling generic-array v0.14.7
   Compiling serde_json v1.0.108
   Compiling allocator-api2 v0.2.16
   Compiling subtle v2.5.0
   Compiling ryu v1.0.16
   Compiling rustc-hash v1.1.0
   Compiling rustix v0.38.28
   Compiling itoa v1.0.10
   Compiling quote v1.0.33
   Compiling hashbrown v0.14.3
   Compiling proc-macro-error-attr v1.0.4
   Compiling plain v0.2.3
   Compiling syn v2.0.41
   Compiling fallible-iterator v0.2.0
   Compiling log v0.4.20
   Compiling const_format_proc_macros v0.2.32
   Compiling cpufeatures v0.2.11
   Compiling bitflags v1.3.2
   Compiling bitflags v2.4.1
   Compiling either v1.9.0
   Compiling fallible-streaming-iterator v0.1.9
   Compiling smallvec v1.11.2
   Compiling hashlink v0.8.4
   Compiling itertools v0.10.5
   Compiling lock_api v0.4.11
   Compiling jobserver v0.1.27
   Compiling proc-macro-error v1.0.4
   Compiling libloading v0.8.1
   Compiling crypto-common v0.1.6
   Compiling block-buffer v0.10.4
   Compiling cc v1.0.83
   Compiling parking_lot_core v0.9.9
   Compiling paste v1.0.14
   Compiling digest v0.10.7
   Compiling thiserror v1.0.51
   Compiling const_format v0.2.32
   Compiling sha2 v0.10.8
   Compiling capnp v0.17.2
   Compiling dirs-sys-next v0.1.2
   Compiling aho-corasick v1.1.2
   Compiling scopeguard v1.2.0
   Compiling tinyvec_macros v0.1.1
   Compiling regex-syntax v0.8.2
   Compiling crunchy v0.2.2
   Compiling tinyvec v1.6.0
   Compiling dirs-next v2.0.0
   Compiling libsqlite3-sys v0.25.2
   Compiling cloudflare-zlib-sys v0.3.3
   Compiling lz4-sys v1.9.4
   Compiling libz-sys v1.1.15
   Compiling cmake v0.1.50
   Compiling bit-vec v0.6.3
   Compiling anyhow v1.0.79
   Compiling siphasher v0.3.11
   Compiling serde_derive v1.0.193
   Compiling scroll_derive v0.11.1
   Compiling thiserror-impl v1.0.51
   Compiling rustversion v1.0.14
   Compiling linux-raw-sys v0.4.12
   Compiling tiny-keccak v2.0.2
   Compiling regex-automata v0.4.3
   Compiling convert_case v0.5.0
   Compiling equivalent v1.0.1
   Compiling indexmap v2.1.0
   Compiling scroll v0.11.0
   Compiling llvm-sys v150.1.2 (/home/r4-0/ZLUDA/ext/llvm-sys.rs)
   Compiling goblin v0.5.4
   Compiling phf_shared v0.10.0
   Compiling unicode-normalization v0.1.22
   Compiling parking_lot v0.12.1
   Compiling term v0.7.0
   Compiling libgit2-sys v0.14.2+1.5.1
   Compiling thread-id v4.2.1
   Compiling precomputed-hash v0.1.1
   Compiling libm v0.2.8
   Compiling unicode-bidi v0.3.15
   Compiling fixedbitset v0.4.2
   Compiling regex v1.10.2
   Compiling percent-encoding v2.3.1
   Compiling time-core v0.1.1
   Compiling new_debug_unreachable v1.0.4
   Compiling string_cache v0.8.7
   Compiling cuda_base v0.0.0 (/home/r4-0/ZLUDA/cuda_base)
   Compiling lalrpop-util v0.20.0
   Compiling bit-set v0.5.3
   Compiling time v0.3.23
   Compiling idna v0.5.0
   Compiling form_urlencoded v1.2.1
   Compiling petgraph v0.6.4
   Compiling is-terminal v0.4.9
   Compiling ascii-canvas v3.0.0
   Compiling ena v0.14.2
   Compiling num-traits v0.2.17
   Compiling cuda_types v0.0.0 (/home/r4-0/ZLUDA/cuda_types)
   Compiling diff v0.1.13
   Compiling regex-syntax v0.7.5
   Compiling pico-args v0.5.0
   Compiling vergen v7.5.1
   Compiling url v2.5.0
   Compiling enum-iterator-derive v1.3.0
   Compiling zluda_llvm v0.0.0 (/home/r4-0/ZLUDA/zluda_llvm)
   Compiling cpp_demangle v0.3.5
   Compiling enum-iterator v1.5.0
   Compiling lalrpop v0.20.0
   Compiling getset v0.1.2
   Compiling half v1.8.2
   Compiling toml v0.5.11
   Compiling blake3 v1.3.3
   Compiling memoffset v0.8.0
   Compiling crossbeam-utils v0.8.17
   Compiling lazy_static v1.4.0
   Compiling proc-macro-crate v0.1.5
   Compiling num_enum_derive v0.4.3
   Compiling derivative v2.2.0
   Compiling dirs-sys v0.3.7
   Compiling slab v0.4.9
   Compiling rocm_smi-sys v0.0.0 (/home/r4-0/ZLUDA/rocm_smi-sys)
   Compiling constant_time_eq v0.2.6
   Compiling arrayvec v0.7.4
   Compiling rocblas-sys v0.0.0 (/home/r4-0/ZLUDA/rocblas-sys)
   Compiling arrayref v0.3.7
   Compiling rocsolver-sys v0.0.0 (/home/r4-0/ZLUDA/rocsolver-sys)
   Compiling hipblaslt-sys v0.0.0 (/home/r4-0/ZLUDA/hipblaslt-sys)
   Compiling hipfft-sys v0.0.0 (/home/r4-0/ZLUDA/hipfft-sys)
   Compiling fastrand v2.0.1
   Compiling rocsparse-sys v0.0.0 (/home/r4-0/ZLUDA/rocsparse-sys)
   Compiling byteorder v1.5.0
   Compiling miopen-sys v0.0.0 (/home/r4-0/ZLUDA/miopen-sys)
   Compiling dynasm v1.2.3
   Compiling tempfile v3.8.1
   Compiling dirs v4.0.0
   Compiling memmap2 v0.5.10
   Compiling static_assertions v1.1.0
   Compiling num_enum v0.4.3
   Compiling crossbeam-channel v0.5.9
   Compiling zluda_ml v0.0.0 (/home/r4-0/ZLUDA/zluda_ml)
   Compiling zluda_ccl v0.0.0 (/home/r4-0/ZLUDA/zluda_ccl)
   Compiling zluda_dnn v0.0.0 (/home/r4-0/ZLUDA/zluda_dnn)
   Compiling ptx v0.0.0 (/home/r4-0/ZLUDA/ptx)
   Compiling cloudflare-zlib v0.2.10
   Compiling dynasmrt v1.2.3
   Compiling git2 v0.16.1
   Compiling zluda v0.0.0 (/home/r4-0/ZLUDA/zluda)
   Compiling rusqlite v0.28.0
   Compiling hip_common v0.0.0 (/home/r4-0/ZLUDA/hip_common)
   Compiling zluda_dark_api v0.0.0 (/home/r4-0/ZLUDA/zluda_dark_api)
   Compiling comgr v0.0.0 (/home/r4-0/ZLUDA/comgr)
   Compiling zluda_fft v0.0.0 (/home/r4-0/ZLUDA/zluda_fft)
   Compiling zluda_sparse v0.0.0 (/home/r4-0/ZLUDA/zluda_sparse)
   Compiling zluda_blas v0.0.0 (/home/r4-0/ZLUDA/zluda_blas)
   Compiling zluda_blaslt v0.0.0 (/home/r4-0/ZLUDA/zluda_blaslt)
warning: crate `cublasLt` should have a snake case name
  |
  = help: convert the identifier to snake case: `cublas_lt`
  = note: `#[warn(non_snake_case)]` on by default

warning: `zluda_blaslt` (lib) generated 1 warning
error: failed to run custom build command for `llvm-sys v150.1.2 (/home/r4-0/ZLUDA/ext/llvm-sys.rs)`

Caused by:
  process didn't exit successfully: `/home/r4-0/ZLUDA/target/release/build/llvm-sys-04d8e9102fc43ca1/build-script-build` (exit status: 101)
  --- stdout
  cargo:rerun-if-changed=build.rs
  cargo:rerun-if-changed=/home/r4-0/ZLUDA/ext/llvm-project/llvm
  cargo:rerun-if-changed=/home/r4-0/ZLUDA/ext/llvm-sys.rs/build.cmake
  CMAKE_TOOLCHAIN_FILE_x86_64-unknown-linux-gnu = None
  CMAKE_TOOLCHAIN_FILE_x86_64_unknown_linux_gnu = None
  HOST_CMAKE_TOOLCHAIN_FILE = None
  CMAKE_TOOLCHAIN_FILE = None
  CMAKE_PREFIX_PATH_x86_64-unknown-linux-gnu = None
  CMAKE_PREFIX_PATH_x86_64_unknown_linux_gnu = None
  HOST_CMAKE_PREFIX_PATH = None
  CMAKE_PREFIX_PATH = None
  CMAKE_x86_64-unknown-linux-gnu = None
  CMAKE_x86_64_unknown_linux_gnu = None
  HOST_CMAKE = None
  CMAKE = None
  running: "cmake" "/home/r4-0/ZLUDA/ext/llvm-project/llvm" "-G" "Ninja" "-DLLVM_ENABLE_LIBXML2=OFF" "-DLLVM_ENABLE_ZLIB=OFF" "-DLLVM_ENABLE_ZSTD=OFF" "-DLLVM_ENABLE_CURL=OFF" "-DLLVM_ENABLE_HTTPLIB=OFF" "-DLLVM_ENABLE_LIBEDIT=OFF" "-DLLVM_ENABLE_TERMINFO=OFF" "-DLLVM_BUILD_TOOLS=OFF" "-DLLVM_TARGETS_TO_BUILD=" "-DLLVM_ENABLE_PROJECTS=" "-DCMAKE_PROJECT_INCLUDE_BEFORE=/home/r4-0/ZLUDA/ext/llvm-sys.rs/build.cmake" "-DCMAKE_INSTALL_PREFIX=/home/r4-0/ZLUDA/target/release/build/llvm-sys-22ea7c535897be01/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/home/r4-0/miniconda3/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_ASM_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_ASM_COMPILER=/home/r4-0/miniconda3/bin/cc" "-DCMAKE_BUILD_TYPE=Release"
  -- The C compiler identification is GNU 12.1.0
  -- The CXX compiler identification is GNU 11.4.0
  -- The ASM compiler identification is GNU
  -- Found assembler: /home/r4-0/miniconda3/bin/cc
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Check for working C compiler: /home/r4-0/miniconda3/bin/cc - skipped
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Check for working CXX compiler: /usr/bin/c++ - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- Looking for dlfcn.h
  -- Looking for dlfcn.h - found
  -- Looking for errno.h
  -- Looking for errno.h - found
  -- Looking for fcntl.h
  -- Looking for fcntl.h - found
  -- Looking for link.h
  -- Looking for link.h - found
  -- Looking for malloc/malloc.h
  -- Looking for malloc/malloc.h - not found
  -- Looking for pthread.h
  -- Looking for pthread.h - found
  -- Looking for signal.h
  -- Looking for signal.h - found
  -- Looking for sys/ioctl.h
  -- Looking for sys/ioctl.h - found
  -- Looking for sys/mman.h
  -- Looking for sys/mman.h - found
  -- Looking for sys/param.h
  -- Looking for sys/param.h - found
  -- Looking for sys/resource.h
  -- Looking for sys/resource.h - found
  -- Looking for sys/stat.h
  -- Looking for sys/stat.h - found
  -- Looking for sys/time.h
  -- Looking for sys/time.h - found
  -- Looking for sys/types.h
  -- Looking for sys/types.h - found
  -- Looking for sysexits.h
  -- Looking for sysexits.h - found
  -- Looking for termios.h
  -- Looking for termios.h - found
  -- Looking for unistd.h
  -- Looking for unistd.h - found
  -- Looking for valgrind/valgrind.h
  -- Looking for valgrind/valgrind.h - not found
  -- Looking for fenv.h
  -- Looking for fenv.h - found
  -- Looking for FE_ALL_EXCEPT
  -- Looking for FE_ALL_EXCEPT - found
  -- Looking for FE_INEXACT
  -- Looking for FE_INEXACT - found
  -- Looking for mach/mach.h
  -- Looking for mach/mach.h - not found
  -- Looking for CrashReporterClient.h
  -- Looking for CrashReporterClient.h - not found
  -- Looking for linux/magic.h
  -- Looking for linux/magic.h - found
  -- Looking for pthread_create in pthread
  -- Looking for pthread_create in pthread - found
  -- Looking for pthread_rwlock_init in pthread
  -- Looking for pthread_rwlock_init in pthread - found
  -- Looking for pthread_mutex_lock in pthread
  -- Looking for pthread_mutex_lock in pthread - found
  -- Looking for dlopen in dl
  -- Looking for dlopen in dl - found
  -- Looking for clock_gettime in rt
  -- Looking for clock_gettime in rt - found
  -- Looking for pfm_initialize in pfm
  -- Looking for pfm_initialize in pfm - not found
  -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
  -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
  -- Looking for pthread_create in pthreads
  -- Looking for pthread_create in pthreads - not found
  -- Looking for pthread_create in pthread
  -- Looking for pthread_create in pthread - found
  -- Found Threads: TRUE
  -- Looking for xar_open in xar
  -- Looking for xar_open in xar - not found
  -- Looking for arc4random
  -- Looking for arc4random - not found
  -- Looking for backtrace
  -- Looking for backtrace - found
  -- backtrace facility detected in default set of libraries
  -- Found Backtrace: /home/r4-0/miniconda3/x86_64-conda-linux-gnu/sysroot/usr/include
  -- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
  -- Performing Test C_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Failed
  -- Looking for __register_frame
  -- Looking for __register_frame - found
  -- Looking for __deregister_frame
  -- Looking for __deregister_frame - found
  -- Looking for __unw_add_dynamic_fde
  -- Looking for __unw_add_dynamic_fde - not found
  -- Looking for _Unwind_Backtrace
  -- Looking for _Unwind_Backtrace - found
  -- Looking for getpagesize
  -- Looking for getpagesize - found
  -- Looking for sysconf
  -- Looking for sysconf - found
  -- Looking for getrusage
  -- Looking for getrusage - found
  -- Looking for setrlimit
  -- Looking for setrlimit - found
  -- Looking for isatty
  -- Looking for isatty - found
  -- Looking for futimens
  -- Looking for futimens - found
  -- Looking for futimes
  -- Looking for futimes - found
  -- Looking for sigaltstack
  -- Looking for sigaltstack - found
  -- Looking for lseek64
  -- Looking for lseek64 - found
  -- Looking for mallctl
  -- Looking for mallctl - not found
  -- Looking for mallinfo
  -- Looking for mallinfo - found
  -- Looking for mallinfo2
  -- Looking for mallinfo2 - not found
  -- Looking for malloc_zone_statistics
  -- Looking for malloc_zone_statistics - not found
  -- Looking for getrlimit
  -- Looking for getrlimit - found
  -- Looking for posix_spawn
  -- Looking for posix_spawn - found
  -- Looking for pread
  -- Looking for pread - found
  -- Looking for sbrk
  -- Looking for sbrk - found
  -- Looking for strerror
  -- Looking for strerror - found
  -- Looking for strerror_r
  -- Looking for strerror_r - found
  -- Looking for strerror_s
  -- Looking for strerror_s - not found
  -- Looking for setenv
  -- Looking for setenv - found
  -- Looking for dlopen
  -- Looking for dlopen - found
  -- Looking for dladdr
  -- Looking for dladdr - not found
  -- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC
  -- Performing Test HAVE_STRUCT_STAT_ST_MTIMESPEC_TV_NSEC - Failed
  -- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC
  -- Performing Test HAVE_STRUCT_STAT_ST_MTIM_TV_NSEC - Success
  -- Looking for __GLIBC__
  -- Looking for __GLIBC__ - found
  -- Looking for pthread_getname_np
  -- Looking for pthread_getname_np - found
  -- Looking for pthread_setname_np
  -- Looking for pthread_setname_np - found
  -- Looking for proc_pid_rusage
  -- Looking for proc_pid_rusage - not found
  -- Performing Test HAVE_STD_IS_TRIVIALLY_COPYABLE
  -- Performing Test HAVE_STD_IS_TRIVIALLY_COPYABLE - Success
  -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB
  -- Performing Test HAVE_CXX_ATOMICS_WITHOUT_LIB - Success
  -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB
  -- Performing Test HAVE_CXX_ATOMICS64_WITHOUT_LIB - Success
  -- Performing Test LLVM_HAS_ATOMICS
  -- Performing Test LLVM_HAS_ATOMICS - Success
  -- Performing Test SUPPORTS_VARIADIC_MACROS_FLAG
  -- Performing Test SUPPORTS_VARIADIC_MACROS_FLAG - Success
  -- Performing Test SUPPORTS_GNU_ZERO_VARIADIC_MACRO_ARGUMENTS_FLAG
  -- Performing Test SUPPORTS_GNU_ZERO_VARIADIC_MACRO_ARGUMENTS_FLAG - Failed
  -- Performing Test HAS_MAYBE_UNINITIALIZED
  -- Performing Test HAS_MAYBE_UNINITIALIZED - Success
  -- Native target X86 is not selected; lli will not JIT code
  -- Threads enabled.
  -- Doxygen disabled.
  -- Go bindings disabled.
  -- Ninja version: 1.10.2
  -- Could NOT find OCaml (missing: OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
  -- Could NOT find OCaml (missing: OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH)
  -- OCaml bindings disabled.
  -- Could NOT find Python module pygments
  -- Could NOT find Python module pygments.lexers.c_cpp
  -- Could NOT find Python module yaml
  -- LLVM host triple: x86_64-unknown-linux-gnu
  -- LLVM default target triple: x86_64-unknown-linux-gnu
  -- Performing Test C_SUPPORTS_FPIC
  -- Performing Test C_SUPPORTS_FPIC - Success
  -- Performing Test CXX_SUPPORTS_FPIC
  -- Performing Test CXX_SUPPORTS_FPIC - Success
  -- Building with -fPIC
  -- Performing Test C_SUPPORTS_FNO_SEMANTIC_INTERPOSITION
  -- Performing Test C_SUPPORTS_FNO_SEMANTIC_INTERPOSITION - Success
  -- Performing Test CXX_SUPPORTS_FNO_SEMANTIC_INTERPOSITION
  -- Performing Test CXX_SUPPORTS_FNO_SEMANTIC_INTERPOSITION - Success
  -- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG
  -- Performing Test SUPPORTS_FVISIBILITY_INLINES_HIDDEN_FLAG - Success
  -- Performing Test C_SUPPORTS_WERROR_DATE_TIME
  -- Performing Test C_SUPPORTS_WERROR_DATE_TIME - Success
  -- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME
  -- Performing Test CXX_SUPPORTS_WERROR_DATE_TIME - Success
  -- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW
  -- Performing Test CXX_SUPPORTS_WERROR_UNGUARDED_AVAILABILITY_NEW - Failed
  -- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG
  -- Performing Test CXX_SUPPORTS_MISSING_FIELD_INITIALIZERS_FLAG - Success
  -- Performing Test C_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG
  -- Performing Test C_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG - Failed
  -- Performing Test CXX_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG
  -- Performing Test CXX_SUPPORTS_CXX98_COMPAT_EXTRA_SEMI_FLAG - Failed
  -- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
  -- Performing Test C_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
  -- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG
  -- Performing Test CXX_SUPPORTS_IMPLICIT_FALLTHROUGH_FLAG - Success
  -- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
  -- Performing Test C_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Failed
  -- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG
  -- Performing Test CXX_SUPPORTS_COVERED_SWITCH_DEFAULT_FLAG - Failed
  -- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG
  -- Performing Test CXX_SUPPORTS_CLASS_MEMACCESS_FLAG - Success
  -- Performing Test CXX_SUPPORTS_REDUNDANT_MOVE_FLAG
  -- Performing Test CXX_SUPPORTS_REDUNDANT_MOVE_FLAG - Success
  -- Performing Test CXX_SUPPORTS_PESSIMIZING_MOVE_FLAG
  -- Performing Test CXX_SUPPORTS_PESSIMIZING_MOVE_FLAG - Success
  -- Performing Test CXX_SUPPORTS_NOEXCEPT_TYPE_FLAG
  -- Performing Test CXX_SUPPORTS_NOEXCEPT_TYPE_FLAG - Success
  -- Performing Test CXX_WONT_WARN_ON_FINAL_NONVIRTUALDTOR
  -- Performing Test CXX_WONT_WARN_ON_FINAL_NONVIRTUALDTOR - Failed
  -- Performing Test CXX_SUPPORTS_SUGGEST_OVERRIDE_FLAG
  -- Performing Test CXX_SUPPORTS_SUGGEST_OVERRIDE_FLAG - Success
  -- Performing Test CXX_WSUGGEST_OVERRIDE_ALLOWS_ONLY_FINAL
  -- Performing Test CXX_WSUGGEST_OVERRIDE_ALLOWS_ONLY_FINAL - Success
  -- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP
  -- Performing Test C_WCOMMENT_ALLOWS_LINE_WRAP - Failed
  -- Performing Test C_SUPPORTS_STRING_CONVERSION_FLAG
  -- Performing Test C_SUPPORTS_STRING_CONVERSION_FLAG - Failed
  -- Performing Test CXX_SUPPORTS_STRING_CONVERSION_FLAG
  -- Performing Test CXX_SUPPORTS_STRING_CONVERSION_FLAG - Failed
  -- Performing Test C_SUPPORTS_MISLEADING_INDENTATION_FLAG
  -- Performing Test C_SUPPORTS_MISLEADING_INDENTATION_FLAG - Success
  -- Performing Test CXX_SUPPORTS_MISLEADING_INDENTATION_FLAG
  -- Performing Test CXX_SUPPORTS_MISLEADING_INDENTATION_FLAG - Success
  -- Performing Test LINKER_SUPPORTS_COLOR_DIAGNOSTICS
  -- Performing Test LINKER_SUPPORTS_COLOR_DIAGNOSTICS - Failed
  -- Performing Test C_SUPPORTS_FNO_FUNCTION_SECTIONS
  -- Performing Test C_SUPPORTS_FNO_FUNCTION_SECTIONS - Success
  -- Performing Test C_SUPPORTS_FFUNCTION_SECTIONS
  -- Performing Test C_SUPPORTS_FFUNCTION_SECTIONS - Success
  -- Performing Test CXX_SUPPORTS_FFUNCTION_SECTIONS
  -- Performing Test CXX_SUPPORTS_FFUNCTION_SECTIONS - Success
  -- Performing Test C_SUPPORTS_FDATA_SECTIONS
  -- Performing Test C_SUPPORTS_FDATA_SECTIONS - Success
  -- Performing Test CXX_SUPPORTS_FDATA_SECTIONS
  -- Performing Test CXX_SUPPORTS_FDATA_SECTIONS - Success
  -- Looking for os_signpost_interval_begin
  -- Looking for os_signpost_interval_begin - not found
  -- Found Python3: /home/r4-0/miniconda3/bin/python3.12 (found suitable version "3.12.2", minimum required is "3.6") found components: Interpreter
  -- Linker detection: GNU ld
  -- Performing Test HAS_WERROR_GLOBAL_CTORS
  -- Performing Test HAS_WERROR_GLOBAL_CTORS - Failed
  -- Looking for __x86_64__
  -- Looking for __x86_64__ - found
  -- Found Git: /usr/bin/git (found version "2.34.1")
  -- Registering Bye as a pass plugin (static build: OFF)
  -- Failed to find LLVM FileCheck
  -- git version: v0.0.0 normalized to 0.0.0
  -- Version: 1.6.0
  -- Looking for shm_open in rt
  -- Looking for shm_open in rt - found
  -- Performing Test HAVE_CXX_FLAG_STD_CXX11
  -- Performing Test HAVE_CXX_FLAG_STD_CXX11 - Success
  -- Performing Test HAVE_CXX_FLAG_WALL
  -- Performing Test HAVE_CXX_FLAG_WALL - Success
  -- Performing Test HAVE_CXX_FLAG_WEXTRA
  -- Performing Test HAVE_CXX_FLAG_WEXTRA - Success
  -- Performing Test HAVE_CXX_FLAG_WSHADOW
  -- Performing Test HAVE_CXX_FLAG_WSHADOW - Success
  -- Performing Test HAVE_CXX_FLAG_WSUGGEST_OVERRIDE
  -- Performing Test HAVE_CXX_FLAG_WSUGGEST_OVERRIDE - Success
  -- Performing Test HAVE_CXX_FLAG_PEDANTIC
  -- Performing Test HAVE_CXX_FLAG_PEDANTIC - Success
  -- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS
  -- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS - Success
  -- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32
  -- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32 - Failed
  -- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING
  -- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING - Success
  -- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED_DECLARATIONS
  -- Performing Test HAVE_CXX_FLAG_WNO_DEPRECATED_DECLARATIONS - Success
  -- Performing Test HAVE_CXX_FLAG_FNO_EXCEPTIONS
  -- Performing Test HAVE_CXX_FLAG_FNO_EXCEPTIONS - Success
  -- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING
  -- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING - Success
  -- Performing Test HAVE_CXX_FLAG_WD654
  -- Performing Test HAVE_CXX_FLAG_WD654 - Failed
  -- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY
  -- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY - Failed
  -- Performing Test HAVE_CXX_FLAG_COVERAGE
  -- Performing Test HAVE_CXX_FLAG_COVERAGE - Success
  -- Performing Test HAVE_GNU_POSIX_REGEX
  -- Performing Test HAVE_GNU_POSIX_REGEX
  -- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
  -- Performing Test HAVE_POSIX_REGEX
  -- Performing Test HAVE_POSIX_REGEX
  -- Performing Test HAVE_POSIX_REGEX -- success
  -- Performing Test HAVE_STEADY_CLOCK
  -- Performing Test HAVE_STEADY_CLOCK
  -- Performing Test HAVE_STEADY_CLOCK -- success
  -- Configuring done (15.7s)
  -- Generating done (1.1s)
  -- Build files have been written to: /home/r4-0/ZLUDA/target/release/build/llvm-sys-22ea7c535897be01/out/build
  running: "cmake" "--build" "."
Error: "\"/home/r4-0/.rustup/toolchains/1.66.1-x86_64-unknown-linux-gnu/bin/cargo\" \"build\" \"--locked\" \"-p\" \"zluda_blas\" \"-p\" \"zluda_blaslt\" \"-p\" \"zluda_ccl\" \"-p\" \"zluda_dnn\" \"-p\" \"zluda_dump\" \"-p\" \"zluda_fft\" \"-p\" \"zluda_ml\" \"-p\" \"zluda_lib\" \"-p\" \"zluda_sparse\" \"--release\" failed with exit code 101"

Try installing build-essential package

Weird, linker is complaining about the lack of pthread libraries, but pthread is so fundamental that it's hard to avoid having it installed.
Check if you have package libc6-dev and if file /usr/lib/x86_64-linux-gnu/libpthread.so.0 exists

I wasn't able to get that instance to work, Normally I would just run a script to setup the OS, this time around I tried installing some unsual packages which I thought might help conpiling.
In the end, I resulted to just reseting everything and with the regular packages it compiled successfully


zerolog: fix Panic/Fatal behaviour #39

When using WithLevel() zerolog doesn't act on Fatal or Panic so we have to.

rebased

typo fixed

rebased


The linguijs translation does not work

What I'm trying to achieve
…
I want to use the linguijs  macro to get translations
Steps to reproduce the problem

Configure as what is said here from linguijs typescript configuration
https://lingui.js.org/guides/typescript.html

2Add any Component for some text
3.run npm start.
What I expected to happen
…
I would expect that what i have configured in the translation *.po file would get loaded into frontend
Screenshots

I checked that in the output from Babel. React.createElement(macro_1.Trans,xxxxx) is used. But in the output js,there is no import from "@lingui/react" since the Trans component comes from @lingui/react module. So has anyone tested the lingui configuration with typescript&babel? Looks like it's not working.  Thankss a lot.
System information
Operating system:Ubuntu
Browser:Chrome

Hi,
You could take a look at this Linguijs issue:
https://github.com/lingui/js-lingui/issues/473

Hi,
You could take a look at this Linguijs issue:
lingui/js-lingui#473

Hi,The comment there  was made by me. Babel does not support export interface.  Only babel is not enough.


fix: typo in show command

show wasn't working

Sorry I missed this - merging it now - only a year late.  :-)


Azk agent not running

I have a few running services inside azk vm and a few azk shells started, which I can access.
The http loadbalancer stopped working (connection reset by peer), and azk status says that agent is not running. However, the containers are open and running. Any ideas ? In the last few days I had a lot of problems with azk (last 2 versions, 0.14.4 and 0.15.0), the vm stopped completely on system sleep twice.
Before, on azk 0.12.1 everything was fine.
Are there any logs I can paste here ?
$ azk status
? The agent is not running, would you like to start it? No
azk: azk agent is required but is not running (try `azk agent status`)

Hi @teodor-pripoae ! Thanks for your feedback!
Sorry about this. The root cause should be a routine inside azk that verifies if Docker daemon is up and, otherwise, stops azk agent.
This was included in #479 and #493.
The goal of those PRs was exactly the opposite: once the agent components wasn't properly working, the agent should shutdown itself and give the user a chance to bring it up again instead of receiving weird error messages.
For now, we recommend you to use azk agent with the option --no-daemon in a separated terminal tab. This way, if the agent stops, you can notice and start it again.
We'll prioritize this for solving.

Hi,
Thanks for your fix !. How is the recommended way to do it ?
# Before I was doing:
$ azk agent start
$ azk start ....

# Now like this ?
$ azk agent --no-daemon # this will keep daemon in foreground ?
$ azk start ...

Is this related to the bug that was causing high cpu usage for the vm when monitoring docker ? It was fixed, since after upgrading my vm is using under 20% CPU with 31 services running, but it keeps stopping.
Can this issue be related to running a lot of services ? Does it hit some timeout when checking each services from docker ?

@fearenales in fact the current approach isn't the best. There are situations in which VirtualBox can suspend the VM for a while or Docker service can go down.
The flux should be modified to:

Check the current VM state if it's running or VirtualBox is hanging it;
Periodically check for Docker service's integrity and restart it if it's down;
If Docker service cannot be restarted, restart the VM;
If none of the actions above can be succesfully run, agent stops with a failure;

Important:

Currently, azk agent is a monolitic block. An improvement to restart components of the agent and making the agent itself a subsystems monitor (our idea for the future) would be needed;
Restarting Docker is specially complex, we have components of azk agent that run inside Docker and those components should also be restarted after Docker is restarted;
After Docker is restarted, all applications started with azk would be down. This is not a real problem, given Docker just has failed, but it's important for the user to know they're down due to this reason, not an internal error.

@nuxlli Are there any places where I can patch and remove this checks until a patch is released ?
I never restart docker service inside the vm, and I can wait a little after I wake the system from sleep.
I don't know if this checks were back in 0.12.1, but I never had problem with docker restarting suddenly. I guess this checks are needed for linux version of azk, but where can I remove them temporarily until next release ?

@teodor-pripoae Yes, --no-daemon will keep agent in foreground, so you'll need to use another terminal to run azk start.
Yes, we've fixed the high CPU usage in azk v0.14.5, but the main issue is the poor check strategy pointed by @nuxlli .

@teodor-pripoae you can do the following patch:

Add a new config (call it monitor) into https://github.com/azukiapp/azk/blob/master/src/config.js#L86-L99, related to a env var (call it AZK_DOCKER_MONITOR) which default value should be true if the current SO is Linux or false otherwise. To check the SO, import so (like this) in the config.js file and use os.platform() == 'linux' as the default value for that config;
Wrap this code with an ifstatement checking if config('docker:monitor') is true;

After doing this, you should be able to run a make and use the azk file placed in the bin file in the azk project dir (it's a good idea to create a new alias for this an use it instead of normal azk meanwhile).
This should work and would be awesome if you could sent your solution as a Pull Request!
Any issue or concern, please let me know!

Cool ! Thank you, I will try this in a few hours and submit a PR if it works :)

Hey @teodor-pripoae , just checked out your PR. Great job! Did that solve your problem?

Yes, azk didn't stopped the vm yet, so it seems to work. :)

I've just run my batch of tests and everything seems ok.

@fearenales
Btw, do you know why the test suite gives me this error ? Do I need linux ?
$ azk nvm npm test

><EMAIL_ADDRESS>test /Users/toni/code/gh/azk
> make test

task: test
/Users/toni/code/gh/azk/bin/azk nvm gulp test  ""
[16:48:30] Using gulpfile ~/code/gh/azk/gulpfile.js
make: *** [test] Error 1
npm ERR! Test failed.  See above for more details.

Use this to run te test suite:
azk nvm gulp test --slow

I'm sorry for not telling you before.

Thanks!
Everything green,except port binding (I already had agent service binding on that port), and file syncing. But I guess the problems are elsewhere. Will investigate later, the main bug didn't happen for 12 hours, so I guess it's ok.
  375 passing (2m)
  1 pending
  4 failing

  1) Azk docker module, run method @slow should support bind ports:
     Error: HTTP code is 500 which indicates error: server error - Cannot start container 9d1ebc5102895ccfdc2dbef55883b986b1e7ffdd19d67449baa3fdb4bf46de40: Error starting userland proxy: listen tcp <IP_ADDRESS>:32777: bind: address already in use

      at _stream_readable.js:944:16

2) Azk sync, Worker module should not include content patterns files from except_from option:
     AssertionError: expected '/private/var/folders/f5/bdtz6z3n4ns8mpkp1npyhj6c0000gn/T/azk-test-54492228zn1s/bar/Fred.txt' not to match /bar\/Fred.txt/
      at Test.callee$1$1$ (/azk:0.15.0/spec/sync/worker_spec.js:216:27)

  3) Azk sync, Worker module should exclude the .gitignore content for default:
     AssertionError: expected '/private/var/folders/f5/bdtz6z3n4ns8mpkp1npyhj6c0000gn/T/azk-test-54492n1w3zrk/ignored/Fred.txt' not to match /ignored\/Fred.txt/
      at Test.callee$1$2$ (/azk:0.15.0/spec/sync/worker_spec.js:241:27)

  4) Azk sync, Worker module should exclude the .syncignore content for default in preference to .gitignore:
     AssertionError: expected '/private/var/folders/f5/bdtz6z3n4ns8mpkp1npyhj6c0000gn/T/azk-test-54492cqjv6qo/foo/Moe.txt' to match /ignored\/Fred.txt/
      at Test.callee$1$3$ (/azk:0.15.0/spec/sync/worker_spec.js:267:23)

hmm.. which version of rsync are you using? Those errors are odd.

Running on OSX. I didn't stop my services or vm when running tests, is this required ?
$ rsync --version
rsync  version 3.1.1  protocol version 31
Copyright (C) 1996-2014 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
    64-bit files, 64-bit inums, 64-bit timestamps, 64-bit long ints,
    socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
    append, ACLs, xattrs, iconv, symtimes, no prealloc, file-flags

Same thing happened at our CI box. I'm going to dig it deeper and ping you back ASAP.

I ran it again and now only one error. It seems it is an intermittent error.
1) Azk sync, Worker module should not include content patterns files from except_from option:
     AssertionError: expected '/private/var/folders/f5/bdtz6z3n4ns8mpkp1npyhj6c0000gn/T/azk-test-562383t7d56o/ignored/Fred.txt' not to match /ignored\/Fred.txt/
      at Test.callee$1$1$ (/azk:0.15.0/spec/sync/worker_spec.js:215:27)

Yes, I've run it again in the CI box and everything passed... It's an intermittent error :/
Well, don't worry, I don't think your changes introduced that but I'll take a closer look on this when I have a chance.
Thank you very much for your PR, we do appreciate.

Thank you for your help, too :)


This fixes #12

PR checklist

[x] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!

[ ] If you've added a new tool - add to the software_versions process and a regex to scrape_software_versions.py
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/pangenome branch on the nf-core/test-datasets repository.

[ ] Make sure your code lints (nf-core lint .).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

Bring the nextflow_schema.json up to date fixing #12.

Note this lint check is expected to fail
╭──────────────────────────────────────────────────────────────────────────────╮
│ [✗] 1 Test Failed                                                            │
├──────────────────────────────────────────────────────────────────────────────┤
│ conda_dockerfile: Could not find Dockerfile file string: FROM nfcore/base:1… │
╰──────────────────────────────────────────────────────────────────────────────╯


Per Pixel Transparency is broken when using borderless windows and fullscreen in godot 3.2.3

Operating System:
Windows 7 Pro SP1.
Godot Version:
Godot 3.2.3 stable.
Issue:
Per Pixel Transparency replaces transparency with black when using Borderless windows and Maximized Mode (or Fullscreen).
On Godot 3.2.2 stable the window works fine only when exporting.
However, on Godot 3.2.3 stable the window replaces transparency with black.
When running the project from the Godot Editor the window is always broken.
Steps to reproduce:
Go to Project Settings and set the window to be borderless and enable Per Pixel Transparency.
Make a new scene and attach a script to it.
Add in the ready function:
get_tree().get_root().set_transparent_background(true)
OS.window_maximized = true
(Change it to false to see the normal condition)
Export the project in Godot 3.2.3 stable and Godot 3.2.2 stable.
Minimal Project:
window_transparency_bug.zip
Exported project (Godot 3.2.2 stable) with the expected behavior:
window_transparency_bug_godot_3.2.2.zip

Godo-3.2.3 had this issue with windows 10 as well.
Building from master branch doesn't seem to have the same problem so I think it might be fixed.

This is expected, in the full screen or borderless full screen (borderless + maximized) mode per-pixel transparency may or may not work depending on GPU driver and OS. When the full screen window is detected, OS can stop rendering other windows.
As a workaround, you can set the window size to be a few pixels smaller than a screen size.

Building from master branch doesn't seem to have the same problem so I think it might be fixed.

Currently, there's no per-pixel transparency support in master at all.

Is this problem already fixed in Godot 3.2.4?

My GPU is a GeForce GTX 1050 Ti and my driver is currently version 456.38.

Is there a way to make a borderless window maximized without being in Fullscreen mode (eg. Showing the taskbar like a normal window would)?

Enablr borderless window in the Project Settings, disable fullscreen and set OS.window_maximized = true in a script.
Note that we don't recommend implementing client-side decorations in Godot as there is no way to implement custom draggable areas yet. Moving the window yourself when the user drags the title bar will lead to desyncs and issues on multi-monitor setups (on top of not being able to benefit from window managers' tiling features).

Closing in favor of https://github.com/godotengine/godot/issues/60665, as this is the same underlying cause.


[Feature Request] Model interpretability for flax

Hi, just like we have support for keras in readme, can we perform interpretation for flax CNN models? https://github.com/google/flax
P.S. I am ready to implement this feature with guidance

Anyone??

Bump for this!


drivers/serial: stm32: fix the uart_irq_tx_ready

The TXE flag is on even then tx irq not enabled, so add check
the tx irq enable status.
Signed-off-by: Harry Jiang<EMAIL_ADDRESS>

There is a long standing debate on whether this is required or not.
Adding it should not break anything on application already using it.
Though, according to API, this is not strictly required:
/**
 * @brief Check if UART TX buffer can accept a new char
 *
 * @details Check if UART TX buffer can accept at least one character
 * for transmission (i.e. uart_fifo_fill() will succeed and return
 * non-zero). This function must be called in a UART interrupt
 * handler, or its result is undefined. Before calling this function
 * in the interrupt handler, uart_irq_update() must be called once per
 * the handler invocation.
 *
 * @param dev UART device structure.
 *
 * @retval 1 If at least one char can be written to UART.
 * @retval 0 Otherwise.
 */
static inline int uart_irq_tx_ready(struct device *dev)

To be clear, current implementation respects the following (but I don't say this is not error prone):
"UART TX buffer can accept at least one character for transmission (i.e. uart_fifo_fill() will succeed and return non-zero) if function is called in a UART interrupt handler"
"This function must be called in a UART interrupt handler, or its result is undefined."
@explora26, does your application respects these guidelines?

Yes, I'm currently develop application follow the guidelines.
Here is my UART handler very similar to subsys/shell/shell_uart.c
static void uart_callback(void *user_data)
{
    const struct shell_uart *sh_uart = (struct shell_uart *)user_data;
    struct device *dev = sh_uart->ctrl_blk->dev;

    uart_irq_update(dev);

    if (uart_irq_rx_ready(dev)) {
        uart_rx_handle(sh_uart);
    }

    if (uart_irq_tx_ready(dev)) {
        uart_tx_handle(sh_uart);
    }
}

I notice that when RX data coming and then both uart_rx_handle() and uart_tx_handle() are called.
Some platform's driver do check is tx interrupt enabled in uart_irq_tx_ready API (uart_cc32xx.c uart_mcux.c uart_nrfx_uarte.c uart_pl011.c ...),  some platform are not , so the result may difference.
Maybe the implementation need discuss with API owner ?

@explora26 , so don't you find the same issue with uart_irq_rx_ready?

uart_irq_rx_ready has the same behavior.
There is an issue #18815 discuss those function, I think i can close this PR currently and wait for the requirement update.


Carthage build fail with version 3.1.0

[x] I have looked at the Documentation
[x] I have read the F.A.Q.
[x] I have filled out this issue template.

Issue Info

Info
Value

Platform
ios

Platform Version
10.0

SnapKit Version
3.1.0

Integration Method
carthage

Issue Description
Hi there,
I have an issue while carthage builds SnapKit 3.1.0. The error looks like this:
` The following build commands failed:
CompileSwift normal x86_64
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
(2 failures)
/Playground/Carthage/Checkouts/SnapKit/Source/LayoutConstraintItem.swift:55:20: error: value of type 'ConstraintLayoutGuide' has no member 'owningView'
A shell task (/usr/bin/xcrun xcodebuild -workspace /Playground/Carthage/Checkouts/SnapKit/SnapKit.xcworkspace -scheme SnapKit -configuration Release ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build) failed with exit code 65:
** BUILD FAILED **
The following build commands failed:
CompileSwift normal x86_64
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
(2 failures) `
The earlier version(3.0.2) works fine.
Thanks

Have the same Issue

Dupe of #348


Building under Cygwin gives the error cc1: error: code model kernel does not support PIC mode

Running the make command on cygwin i get the following output
username@ARK /cygdrive/c/Users/username/OSDev
$ make
git clone https://github.com/limine-bootloader/limine.git --branch=v3.0-branch-binary --depth=1
Cloning into 'limine'...
remote: Enumerating objects: 17, done.
remote: Counting objects: 100% (17/17), done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 17 (delta 3), reused 7 (delta 1), pack-reused 0
Receiving objects: 100% (17/17), 410.04 KiB | 3.15 MiB/s, done.
Resolving deltas: 100% (3/3), done.
make -C limine
make[1]: Entering directory '/cygdrive/c/Users/username/OSDev/limine'
cc -g -O2 -pipe -Wall -Wextra  -std=c99 -D__USE_MINGW_ANSI_STDIO limine-version.c -o limine-version
make[1]: Leaving directory '/cygdrive/c/Users/username/OSDev/limine'
make -C kernel
make[1]: Entering directory '/cygdrive/c/Users/username/OSDev/kernel'
curl https://raw.githubusercontent.com/limine-bootloader/limine/trunk/limine.h -o limine.h
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  9993  100  9993    0     0  44571      0 --:--:-- --:--:-- --:--:-- 44811
cc  -O2 -g -Wall -Wextra -Wpedantic -pipe -I. -std=c11 -ffreestanding -fno-stack-protector -fno-stack-check -fno-pie -fno-pic -m64 -march=x86-64 -mabi=sysv -mno-80387 -mno-mmx -mno-sse -mno-sse2 -mno-red-zone -mcmodel=kernel -MMD -c kernel.c -o kernel.o
cc1: error: code model kernel does not support PIC mode
make[1]: *** [GNUmakefile:89: kernel.o] Error 1
make[1]: Leaving directory '/cygdrive/c/Users/username/OSDev/kernel'
make: *** [GNUmakefile:33: kernel] Error 2

I would provide more information but I'm not really sure what else to include

I think it has something to do with building limine? The only thing I can make from looking it up is the -no-pie -fno-pie and -fno-pic might help but the command the compiles limine excludes those commands

Try replacing the -fno-pic flag with -fno-PIC; should that fail, you will either need to use a cross compiler (for x86_64-elf target) or you can use WSL if you're on Windows 10/11.

Sorry if this is just meant to be general knowledge on linux. How do i tell make to use the cross compiler that i just finished building?

Okay the other thing i was going to try was to compile limine with just CC and then compile the kernel with the cross compiler
username@ARK /cygdrive/c/Users/username/OSDev
$ make distclean
rm -rf iso_root barebones.iso barebones.hdd
make -C kernel clean
make[1]: Entering directory '/cygdrive/c/Users/username/OSDev/kernel'
rm -rf kernel.elf ./kernel.o   ./kernel.d
make[1]: Leaving directory '/cygdrive/c/Users/username/OSDev/kernel'
rm -rf limine ovmf-x64
make -C kernel distclean
make[1]: Entering directory '/cygdrive/c/Users/username/OSDev/kernel'
rm -rf kernel.elf ./kernel.o   ./kernel.d
rm -f limine.h
make[1]: Leaving directory '/cygdrive/c/Users/username/OSDev/kernel'

username@ARK /cygdrive/c/Users/username/OSDev
$ make limine
git clone https://github.com/limine-bootloader/limine.git --branch=v3.0-branch-binary --depth=1
Cloning into 'limine'...
remote: Enumerating objects: 17, done.
remote: Counting objects: 100% (17/17), done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 17 (delta 3), reused 7 (delta 1), pack-reused 0
Receiving objects: 100% (17/17), 410.04 KiB | 4.14 MiB/s, done.
Resolving deltas: 100% (3/3), done.
make -C limine
make[1]: Entering directory '/cygdrive/c/Users/username/OSDev/limine'
cc -g -O2 -pipe -Wall -Wextra  -std=c99 -D__USE_MINGW_ANSI_STDIO limine-version.c -o limine-version
make[1]: Leaving directory '/cygdrive/c/Users/username/OSDev/limine'

username@ARK /cygdrive/c/Users/username/OSDev
$ make CC=$TARGET-gcc
make -C kernel
make[1]: Entering directory '/cygdrive/c/Users/username/OSDev/kernel'
curl https://raw.githubusercontent.com/limine-bootloader/limine/trunk/limine.h -o limine.h
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  9993  100  9993    0     0  41629      0 --:--:-- --:--:-- --:--:-- 41811
i686-elf-gcc  -O2 -g -Wall -Wextra -Wpedantic -pipe -I. -std=c11 -ffreestanding -fno-stack-protector -fno-stack-check -fno-pie -fno-pic -m64 -march=x86-64 -mabi=sysv -mno-80387 -mno-mmx -mno-sse -mno-sse2 -mno-red-zone -mcmodel=kernel -MMD -c kernel.c -o kernel.o
cc1: error: code model 'kernel' not supported in the 32 bit mode
cc1: sorry, unimplemented: 64-bit mode not compiled in
make[1]: *** [GNUmakefile:89: kernel.o] Error 1
make[1]: Leaving directory '/cygdrive/c/Users/username/OSDev/kernel'
make: *** [GNUmakefile:33: kernel] Error 2

Maybe I followed the instructions too closely. I was compiling for i686 elf. I will try again with x86_64-elf as the target

Okay. after redoing everything to compile for x86_64,
redstonedash@ARK /cygdrive/c/Users/redstonedash/OSDev
$ make cc=$TARGET-gcc
make -C kernel
make[1]: Entering directory '/cygdrive/c/Users/redstonedash/OSDev/kernel'
curl https://raw.githubusercontent.com/limine-bootloader/limine/trunk/limine.h -o limine.h
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  9993  100  9993    0     0  44055      0 --:--:-- --:--:-- --:--:-- 44216
cc  -O2 -g -Wall -Wextra -Wpedantic -pipe -I. -std=c11 -ffreestanding -fno-stack-protector -fno-stack-check -fno-pie -fno-pic -m64 -march=x86-64 -mabi=sysv -mno-80387 -mno-mmx -mno-sse -mno-sse2 -mno-red-zone -mcmodel=kernel -MMD -c kernel.c -o kernel.o
cc1: error: code model kernel does not support PIC mode
make[1]: *** [GNUmakefile:89: kernel.o] Error 1
make[1]: Leaving directory '/cygdrive/c/Users/redstonedash/OSDev/kernel'
make: *** [GNUmakefile:33: kernel] Error 2

I can try again with WSL but i feel like this should work. what version of GCC do you use?

cc= should be uppercase...

Ah, my bad. It says it doesn't recognize the option -z
username@ARK /cygdrive/c/Users/username/OSDev
$ make CC=$TARGET-gcc
make -C kernel
make[1]: Entering directory '/cygdrive/c/Users/username/OSDev/kernel'
curl https://raw.githubusercontent.com/limine-bootloader/limine/trunk/limine.h -o limine.h
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  9993  100  9993    0     0  48087      0 --:--:-- --:--:-- --:--:-- 48275
x86_64-elf-gcc  -O2 -g -Wall -Wextra -Wpedantic -pipe -I. -std=c11 -ffreestanding -fno-stack-protector -fno-stack-check -fno-pie -fno-pic -m64 -march=x86-64 -mabi=sysv -mno-80387 -mno-mmx -mno-sse -mno-sse2 -mno-red-zone -mcmodel=kernel -MMD -c kernel.c -o kernel.o
ld ./kernel.o   -nostdlib -static -z max-page-size=0x1000 -T linker.ld -o kernel.elf
ld: unrecognized option '-z'
ld: use the --help option for usage information
make[1]: *** [GNUmakefile:82: kernel.elf] Error 1
make[1]: Leaving directory '/cygdrive/c/Users/username/OSDev/kernel'
make: *** [GNUmakefile:33: kernel] Error 2

Because you also need to pass LD=$TARGET-ld

Thank you. Maybe it should be noted that CC with Cygwin will not work (I assume because it's trying to build a windows executable, which is why the -z command is not present). Other than that most of this thread is just me demonstrating my incompetence on unix systems


Enumerate ovens

In order to display a user's oven, assume that they were minted sequentially and probe the bigmap for (tz1...,0) (tz1..., 1) (tz1..., 2) etc.
However, this could miss some ovens. To deal with this, add a button "track oven" which lets a user enter the address of an oven and adds it as a card on the oven page. Visually distinguish it from the others if the key that's logged in isn't its owner, and disable actions except for deposit and liquidate.

resolved in #15

imported tag for all imported ovens added by track oven button
external tag for ovens where owner is different than the current logged-in user
remaining tasks:

[ ] Disable actions if the owner is not same as logged-in user


setRouter should also update allowances for other tokens

Based on HAECHI audit Axis v3/Smart Contract Security Analysis/Published on : Oct 13, 2021/Version v1.0,
NativeStrategyCurve3Crv does not update Crvallowance setting a new router:
Vulnerability details
The Constructor of BaseStrategy.sol sets an allowance for ETH:
https://github.com/yaxis-project/metavault/blob/aef0124094ed28945cde2e5b80f453cdbca1e8e5/contracts/v3/strategies/BaseStrategy.sol#L67
setRouter() updates this allowance:
https://github.com/yaxis-project/metavault/blob/aef0124094ed28945cde2e5b80f453cdbca1e8e5/contracts/v3/strategies/BaseStrategy.sol#L103-L104
However the Strategy contracts also set allowances for _router, which are not updated with setRouter():
https://github.com/yaxis-project/metavault/blob/aef0124094ed28945cde2e5b80f453cdbca1e8e5/contracts/v3/strategies/NativeStrategyCurve3Crv.sol#L51
https://github.com/yaxis-project/metavault/blob/6c3eac8b45d639339373ea0d6321debf34d5c80c/contracts/v3/strategies/MIMConvexStrategy.sol#L92-L93
https://github.com/yaxis-project/metavault/blob/8f35c3da08c909c2e1879f20d733714ce4a76210/contracts/v3/strategies/GeneralConvexStrategy.sol#L78-L79
https://github.com/yaxis-project/metavault/blob/8f35c3da08c909c2e1879f20d733714ce4a76210/contracts/v3/strategies/ConvexStrategy.sol#L77-L78
Afterthought: reset the allowance for the previous router
Recommended mitigation steps
function setRouter(address _router) virtual external  {
require(msg.sender == manager.governance(), "!governance");
IERC20(weth).safeApprove(address(router), 0); // reset previous allowance
router = ISwap(_router);
IERC20(weth).safeApprove(address(_router), 0);
IERC20(weth).safeApprove(address(_router), type(uint256).max);
}
Implement an override function setRouter() in the following contracts:

NativeStrategyCurve3Crv.sol
MIMConvexStrategy.sol
GeneralConvexStrategy.sol
ConvexStrategy.sol

For example:
function setRouter(address _router) override external  {
require(msg.sender == manager.governance(), "!governance");
IERC20(_crv).safeApprove(address(router), 0);   // reset previous allowance //  except in NativeStrategyCurve3Crv.sol
IERC20(_cvx).safeApprove(address(router), 0);   // reset previous allowance
super.setRouter();
IERC20(_crv).safeApprove(address(_router), 0);   // check if necessary
IERC20(_crv).safeApprove(address(_router), type(uint256).max);
IERC20(_cvx).safeApprove(address(_router), 0);  // check if necessary
IERC20(_cvx).safeApprove(address(_router), type(uint256).max);  // except in NativeStrategyCurve3Crv.sol
}
Note: verify if setting the allowance to 0 first is important as is done in the current setRouter();
If it is important do it before the safeApprove, also in the constructors, to prevent a griefing attack
For WETH is doesn't seem important.

As far as I see, there are two approaches to solving this.
The first one is as above, by approving the corresponding tokens during setRouter.
The second approach is to call approveForSpender, before or after the setRouter call with the correct _spender and _amount.
https://github.com/yaxis-project/metavault/blob/832b83f999c3cd9effcff31bd9aba50a9d626b87/contracts/v3/strategies/BaseStrategy.sol#L80
I kinda favour the second approach, since it requires no changes in the codebase. The only issue is that this needs to go through governance. I assume this isn't a big deal as this can be done at the same time that setRouter governance proposal passes.
If the second approach is chosen, I recommend documenting this somewhere, that approveForSpender needs to be done alongside setRouter governance action.


WIP: separate openai speech API provider

WORK IN PROGRESS
FILING THIS PR MORE FOR AWARENESS/TRACKING RIGHT NOW - SUGGESTIONS WELCOME
In particular, I should:

merge the docker-customized stuff into the repo's own docker files and startup scripts
probably try to implement authenticated remote openai support (though I don't care for it personally) or just not have stub code in there (is_openedai_speech) that hints at future support, for now.

Description
Add support for a separate OpenAI-compatible speech API base URL.
This allows the use of Ollama or an OpenAI-compatible service such as Llama.CPP for text gen (which may be faster / easier for text generation), and another API provider like LocalAI or OpenedAI-Speech for the text-to-speech and speech to text functionality.

Changelog Entry
Added

Add support for a separate OpenAI-compatible speech API providers, using an OPENAI_AUDIO_BASE_URL environment variable.
docker-compose.customized.yaml which sets the new env vars
run_customized.sh which simplifies running openai with the above customized config

Fixed

Allows use of llama.cpp or another text-only OpenAI endpoint / model whilst using a separate/dedicated speech API provider

Changed

Supports a new OPENAI_AUDIO_BASE_URL, which will be used rather than OPENAI_BASE_URL for speech services, when set.

There was another PR that I believe was most of the way there to doing this already before it was closed and the fork branch deleted by the author. Shame, it probably only needed a bit more work. It was decided in discussion of that that we should follow this convention for the environment variable:

Let's follow the existing convention. TTS_OPENAI_API_BASE_URL would be appropriate here. (e.g. check out my custom openai url implementation for RAG embedding model)

Feel free to continue working on this PR but I'll be working on this feature myself following all the existing conventions.

OpenAI-compatible url support has been added to our dev branch, let us know if you encounter any issues!