[BUG] Cannot recompile Pixel SystemUI

Information

Apktool Version (apktool -version) - 2.9.0
Operating System (Mac, Linux, Windows) - Linux
APK From? (Playstore, ROM, Other) - Stock Pixel barbet
Java Version (java --version) - <IP_ADDRESS>

Stacktrace/Logcat
admin@admin:~/apps$ apktool d SystemUIGoogle.apk
I: Using Apktool 2.9.0 on SystemUIGoogle.apk
I: Loading resource table...
I: Decoding file-resources...
I: Loading resource table from file: /home/admin/.local/share/apktool/framework/1.apk
I: Decoding values */* XMLs...
I: Decoding AndroidManifest.xml with resources...
I: Regular manifest package...
I: Baksmaling classes.dex...
I: Baksmaling classes2.dex...
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...
I: Copying META-INF/services directory

admin@admin:~/apps$ apktool b SystemUIGoogle
I: Using Apktool 2.9.0
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether sources has changed...
I: Smaling smali_classes2 folder into classes2.dex...
I: Checking whether resources has changed...
I: Building resources...
W: /home/admin/apps/SystemUIGoogle/res/values/arrays.xml:84: error: resource android:string/status_bar_vpn is private.
W: /home/admin/apps/SystemUIGoogle/res/values/arrays.xml:85: error: resource android:string/status_bar_battery is private.
W: /home/admin/apps/SystemUIGoogle/res/values/arrays.xml:86: error: resource android:string/status_bar_camera is private.
W: /home/admin/apps/SystemUIGoogle/res/values/arrays.xml:171: error: resource android:string/status_bar_screen_record is private.
W: /home/admin/apps/SystemUIGoogle/res/values/arrays.xml:172: error: resource android:string/status_bar_hotspot is private.
W: /home/admin/apps/SystemUIGoogle/res/values/bools.xml:21: error: resource android:bool/config_enableLockScreenRotation is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:23: error: resource android:color/background_material_light is private.
W: /home/admin/apps/SystemUIGoogle/res/values-night/colors.xml:4: error: resource android:color/background_material_dark is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:24: error: resource android:color/primary_text_default_material_light is private.
W: /home/admin/apps/SystemUIGoogle/res/values-night/colors.xml:5: error: resource android:color/primary_text_default_material_dark is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:75: error: resource android:color/foreground_material_dark is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:79: error: resource android:color/foreground_material_dark is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:298: error: resource android:color/background_device_default_light is private.
W: /home/admin/apps/SystemUIGoogle/res/values-night/colors.xml:29: error: resource android:color/background_device_default_dark is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:301: error: resource android:color/accent_device_default is private.
W: /home/admin/apps/SystemUIGoogle/res/values-night/colors.xml:65: error: resource android:color/notification_primary_text_color_dark is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:368: error: resource android:color/accent_device_default is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:369: error: resource android:color/notification_primary_text_color_light is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:370: error: resource android:color/notification_primary_text_color_dark is private.
W: /home/admin/apps/SystemUIGoogle/res/values/colors.xml:475: error: resource android:color/text_color_primary_device_default_dark is private.
brut.androlib.exceptions.AndrolibException: brut.common.BrutException: could not exec (exit code = 1): [/tmp/brut_util_Jar_20178106122052190306248657875793045585.tmp, link, -o, /tmp/APKTOOL1613291305428299689.tmp, --package-id, 127, --min-sdk-version, 34, --target-sdk-version, 34, --version-code, 34, --version-name, 14, --no-auto-version, --no-version-vectors, --no-version-transitions, --no-resource-deduping, --allow-reserved-package-id, --no-compile-sdk-metadata, -e, /tmp/APKTOOL12871415362735941631.tmp, -0, arsc, -I, /home/admin/.local/share/apktool/framework/1.apk, --manifest, /home/admin/apps/SystemUIGoogle/AndroidManifest.xml, /home/admin/apps/SystemUIGoogle/build/resources.zip]

Steps to Reproduce

apktool  d SystemUIGoogle.apk
apktool  b SystemUIGoogle
Also tried importing frameworks-res.apk from same build but same error

Frameworks
If this APK is from an OEM ROM (Samsung, HTC, LG). Please attach framework files
(.apks that live in /system/framework or /system/priv-app)
APK
If this APK can be freely shared, please upload/attach a link to it.
APK Link
Questions to ask before submission

Have you tried apktool d, apktool b without changing anything? yes
If you are trying to install a modified apk, did you resign it? N/A
Are you using the latest apktool version? yes

This is common when the upgraded build tools (aapt2) are more strict than the original tools used to build application. As those errors suggest - this application is using private resources, which should be avoided and rather copied into project.
However, as you might imagine - changing every application you choose to decode to build up to the modern build tool standards may be insane.
So I prepped a workaround to aapt2 to remove this restriction - https://github.com/iBotPeaches/platform_frameworks_base/pull/14
Also saying that though - who knows if this will work or just move the problem downstream.
So tldr - holding for a bit.

That test semi-worked. You just moved to a new issue, which is a known one in the backlog affecting more and more applications.
➜  3392 apktool b SystemUIGoogle
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
I: Using Apktool v2.9.0-1-d2599874-SNAPSHOT
I: Checking whether resources has changed...
I: Building resources...
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/animator/mtrl_card_state_list_anim.xml:4: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/color/mtrl_card_view_foreground.xml:5: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/color/mtrl_card_view_foreground.xml:6: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/color/mtrl_card_view_ripple.xml:5: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/drawable/qs_media_background.xml:2: error: attribute highlight (aka com.android.systemui:highlight) not found.

https://github.com/iBotPeaches/Apktool/issues/3129#issuecomment-1752162277

That test semi-worked. You just moved to a new issue, which is a known one in the backlog affecting more and more applications.
➜  3392 apktool b SystemUIGoogle
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=on -Dswing.aatext=true
I: Using Apktool v2.9.0-1-d2599874-SNAPSHOT
I: Checking whether resources has changed...
I: Building resources...
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/animator/mtrl_card_state_list_anim.xml:4: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/color/mtrl_card_view_foreground.xml:5: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/color/mtrl_card_view_foreground.xml:6: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/color/mtrl_card_view_ripple.xml:5: error: attribute state_dragged (aka com.android.systemui:state_dragged) not found.
W: /media/ibotpeaches/AOSP/Apktool/3392/SystemUIGoogle/res/drawable/qs_media_background.xml:2: error: attribute highlight (aka com.android.systemui:highlight) not found.

#3129 (comment)

Can you share the updated apktool with resolved resource referencing error? Thanks

Can you share the updated apktool with resolved resource referencing error? Thanks

Sorry I cannot. That build was only with Linux binaries and posting dirty test builds I tend to avoid.

@IgorEisberg - I'm investigating those odd issues in https://github.com/iBotPeaches/Apktool/issues/3129#issuecomment-1752162277. I'm just going to retrace some steps and dig into alias attributes, splits, etc and see if I'm missing something.

@IgorEisberg - I'm investigating those odd issues in #3129 (comment). I'm just going to retrace some steps and dig into alias attributes, splits, etc and see if I'm missing something.

Strangely, when I search the missing attributes in resources.arsc using a hex editor, I can find them.
However, can't find them using aapt2 no matter what I try to dump.
Some of these attributes have enum/flag values, so when decompiled, the resulting value is a raw value rather than its name.
Example: "0" instead of "parent" for "layout_constraintStart_toEndOf", because the missing definition is supposed to be
    <attr name="layout_constraintStart_toEndOf" format="reference">
        <enum name="parent" value="0" />
    </attr>

I'm just happy to know I wasn't going crazy and couldn't make sense of those attributes.

I'm just happy to know I wasn't going crazy and couldn't make sense of those attributes.

Nah, I'm going crazy for a while now trying to make sense of this.


Initial support for querying function parameters in the schema

Make an MVP for accessing function parameters in the schema. Aim to make it possible to write lints that detect changes in the number of parameters a function takes.
Parameter names can be changed without violating semver so are not critical to support, but are a "nice-to-have" for e.g. the Playground. Add them to the schema if possible.
Parameter type information is a bit more difficult to represent due to #149, so feel free to ignore types for now in the interest of moving quickly.
Relevant portion of the schema:
https://github.com/obi1kenobi/trustfall-rustdoc-adapter/blob/main/src/rustdoc_schema.graphql#L430-L493

Implemented in https://github.com/obi1kenobi/cargo-semver-checks/pull/170. Should I close the issue?


[Launcher] Text in search box should be highlighted

If there is text populated on search box when launched, the text should be highlighted so I can just type in a new command. Run prompt does this.

Text is not highlighted when launched using win+r, but it is highlighted when launched using alt+space

#2379 will remove the issue of text not highlighted when using win+r, but this is something we need to fix in the future.

isn't this done?


Can you provide all the features, including ground truth and detected ?

Hi,  when I ran the feature extraction code, some problems came up that were difficult to solve, so can you provide all the features, including ground truth and detected , thank you very much.

Sorry, the feature files are too large and I don't have enough Google Drive space for them...


Remove the views that allow creation of a RawDataLog

Summary
Removes the views that allow creation of a Raw Data Log Ingestor manually. It is created automatically when the user creates a PurchaseOrderAPI instead.
Removed

The ability to manually create a Raw Data Log Ingestor

@freshteapot: I might be more liberal on the delete button than others, so I'm happy to change there. I always keep thinking that we can just restore it from the history later, but then again - you might forget it's even there...


Redistribution

Do modpack authors have the right to redistribute this mod as an override jar, i.e. in Modrinth modpacks? Alternatively, would you like to release on Modrinth or GitHub?
Additional context: Curseforge does not allow downloading mods from curseforge for modrinth modpacks. So when your mod is not available for download elsewhere, the only option is to redistribute the mod's .jar file inside the modpack and move the files to the mods directory. Manually moving files like this in a modpack is called overriding.

someone pointed out to me that curseforge lists the license


Switch from SpecialFunctions.jl to Bessels.jl

Bessels.jl is a lot faster for computing besselj (and has special methods for besselj0 and besselj1 that are incredibly fast).

Are computing bessel functions a serious contributor to computational cost?
Though I guess a benefit is that Bessels.jl is pure Julia

I thought I saw a bunch being computed skimming through the source at https://github.com/JuliaApproximation/FastGaussQuadrature.jl/blob/b654654677bc254e8f936c54bd2128a6dda57bba/src/gaussjacobi.jl#L407, but on closer inspection it appears that this was just broadcasting over 2 scalars, so it's hardly critical.


Implement cloud sdk version checks

fixes https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/1051
Warns the user if they are using an incompatible version of the Cloud SDK. Wherever possible, if an unsupported Cloud SDK version is found, the message will be displayed as a warning, not an error (it will not block the user from performing whatever action they were trying to do).
This check occurs in all of the following places:

as an application-level balloon notification
in the dev_appserver local run configuration
in the app engine deployment run configuration
in the cloud sdk panel (which appears in a couple places)

when creating a new app engine project
in the application servers menu
in the Clouds menu

@etanshaul @joaoandremartins  @patflynn Can you think of anywhere else we might want to perform this check? Is gcloud 131.0.0 required for deployments as well?

why not perform this check on the cloud sdk panel itself?

Also, have you considered making this a warning instead of an error? Meaning they can still proceed at their own risk with local run / deployment? If you move this check to the cloud sdk panel I could see it functioning like this.

I did experiment with adding it to the cloud sdk panel - though as I understand it, that means the user would not see the error/warning unless they open the panel, which they might not if these run configurations are automatically configured for them.

Even if the configurations are automatically configured, they still need to select the cloud sdk path.
But I guess if its autodetected on their path then we run into some difficulty..so you're right in this case.
What if its added in all places? Cloud SDK panel, local run config, and deployment.

you guys don't like doing this as an IDE notification?  Feels like the
cleanest way to handle this to me.
On Thu, Nov 3, 2016 at 10:52 AM, Etan Shaul<EMAIL_ADDRESS>wrote:

Even if the configurations are automatically configured, they still need
to select the cloud sdk path.
But I guess if its autodetected on their path then we run into some
difficulty..so you're right in this case.
What if its added in all places? Cloud SDK panel, local run config, and
deployment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084#issuecomment-258165268,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HbaLsyFwyGSjNn8qZLl51F9Q55ibks5q6fU_gaJpZM4KnwQV
.

I like that idea. Whenever the CloudSdk path is set and is an old version then we could show a notification popup warning.

What about if we trigger the IDE notification when they perform a local run or deploy run config? I like the idea of scoping the notification to the places where it's relevant.

Something like "This version is not supported. Please upgrade or you may see weird behavior"

It would be nice for them to be able to fail fast: e.g. not have to actually run a failing deployment before fixing their gcloud version.
Unless your implying the notification would block the action?

The benefit is when they do a plugin update and their local gcloud is out
of date, they know about it immediately, rather than when they want to go
deploy.
On Thu, Nov 3, 2016 at 10:58 AM, Etan Shaul<EMAIL_ADDRESS>wrote:

I like that idea. Whenever the CloudSdk path is set and is an old version
then we could show a notification popup warning.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084#issuecomment-258167173,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HZ7GrkTtNYaYIm9W3-9WiiO-vOLDks5q6faQgaJpZM4KnwQV
.

@patflynn I see your point, though it would also be nice to only warn within the context where it's relevant. i.e. it might be weird to see a prompt to upgrade the cloud sdk when you are working on an unrelated non-appengine project.

I don't feel strongly about it though - I think the "fail early" principle might take precedence over that.

Since our plugin is not currently bundled with the ide I see your point about working on unrelated projects as less of a concern.

why not perform this check on the cloud sdk panel itself? if you do that, we'll ensure we're covered in all cases.

I may be missing something here, but IMO, it's always good to check the version here and there whenever necessary. For example, you may have a second laptop at home which has an old gcloud version set up in the past. You could check out an App Engine project on that laptop and try to deploy. I think a version check before deploying is a good idea here.
@patflynn's idea about notification could be a solution too. However, even in that case, users could still try deploying without version upgrade, so I think having a check is good.

Yeah that's fair.  If the user ignores the notification, it makes sense to
remind them when they're performing an action that could fail due to this.
On Thu, Nov 3, 2016 at 11:07 AM, Chanseok Oh<EMAIL_ADDRESS>wrote:

why not perform this check on the cloud sdk panel itself? if you do that,
we'll ensure we're covered in all cases.
I may be missing something here, but IMO, it's always good to check the
version here and there whenever necessary. For example, you may have a
second laptop at home which has an old gcloud version set up in the past.
You could check out an App Engine project on that laptop and try to deploy.
I think a version check before deploying is a good idea here.
@patflynn https://github.com/patflynn's idea about notification could
be a solution too. However, even in that case, users could still try
deploying without version upgrade, so I think having a check is good.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084#issuecomment-258169903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HT6kfsjzmq5HBx6KBOFJdr75rxVzks5q6fiogaJpZM4KnwQV
.

I agree. Another reason that's necessary: the user might not have a cloud sdk configured at application/project initialization, so we would not be able to perform this check at that time anyway.

Personally I like having this as a warning - not blocking deployment or local run.
If perform the check at project init and at sdk setting time aren't we covered?

yeah I agree that it shouldn't block the execution. But you can have a
warning on a run config that does that without blocking the run right?  The
way I'm picturing it is that the 'server' or 'cloud' icon has a little red
'x' on it, and the validation for the version is on the cloud SDK config
screen.
On Thu, Nov 3, 2016 at 11:15 AM, Etan Shaul<EMAIL_ADDRESS>wrote:

Personally I like having this as a warning - not blocking deployment or
local run.
If perform the check at project init and at sdk setting time aren't we
covered?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084#issuecomment-258172254,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HSZu0yrKAJSpeIBnjQ7DIKu9Zd0Oks5q6fqFgaJpZM4KnwQV
.

Yeah that is fine. Although I don't think we can add an icon next to the 'server' or 'cloud' ui elements since these are provided by framework components. The best we could do is something on bottom of the panel.

@joaoandremartins @etanshaul @patflynn Requesting a code review. The PR description has been updated to list all of the places this warning will occur.
I also have one last question here - in both the Local Dev run configuration and the App Engine Deployment run configuration, this check is necessarily called synchronously (because validation errors on the run configurations are shown by the framework when our code throws a ConfigurationException). Calling CloudSdk.getVersion under the covers can take over 200ms and blocks the UI thread and makes things feel rather slow.  (I was able to get around this in the CloudSdkPanel by performing this check in a background thread, but that isn't possible for the run configurations because of how the run configurations validation framework works.
I propose removing this check from the run configurations and instead just firing off the application-level balloon notification when they run the local dev server or a deployment. Thoughts?

Another option to fix this performance issue would be to cache the cloud sdk version at the intellij application level, for a given cloud sdk directory, and bust the cache when we detect that the cloud SDK's RELEASE_NOTES file was updated. I think I actually like that better.

I do prefer this check as a notification that doesn't block execution. I personally don't like having this throw a ConfigurationException in our UI panels. But I think there may have been some disagreement on this.
I'm thinking through your other comments.

FYI there are classes of ConfigurationExceptions that intellij treats as warnings (which this PR currently uses here), that show up as an error state but don't block execution. It still might not be completely clear to the user that they can still run it, though. I'll add some screenshots to the PR description to make this discussion easier.

I don't think the balloon style notification is appropriate for a field
level validation on something that hasn't been saved yet. I'd rather we
only apply the validation to the configured global SDK path.
On Wed, Nov 16, 2016 at 11:58 AM, Alex Sloan<EMAIL_ADDRESS>wrote:

@aslo commented on this pull request.
In google-cloud-tools-plugin/src/com/google/cloud/tools/
intellij/appengine/sdk/CloudSdkPanel.java
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084:

}

private void checkSdk() {
String path = cloudSdkDirectoryField.getText();

private void checkSdkInBackground() {
final String path = cloudSdkDirectoryField.getText();
ApplicationManager.getApplication().executeOnPooledThread(new CloudSdkCheckerRunnable(path));

I could, but wouldn't that mean the validation would only occur when the
user clicks "save"? Right now, the validation takes place as soon as the
user selects the cloud sdk directory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HVT8rt8JeX3H7ZFETi0RpJz6lH7Vks5q-zY9gaJpZM4KnwQV
.

This actually is a field-level validation - it actually updates the UI in
the cloud sdk panel with the validation message as the user types. The
system notification (balloon) is used elsewhere (i.e. when starting a local
run or a deployment).
On Wed, Nov 16, 2016 at 12:03 PM, Patrick Flynn<EMAIL_ADDRESS>wrote:

I don't think the balloon style notification is appropriate for a field
level validation on something that hasn't been saved yet. I'd rather we
only apply the validation to the configured global SDK path.
On Wed, Nov 16, 2016 at 11:58 AM, Alex Sloan<EMAIL_ADDRESS>wrote:

@aslo commented on this pull request.
In google-cloud-tools-plugin/src/com/google/cloud/tools/
intellij/appengine/sdk/CloudSdkPanel.java
<https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084
:

}

private void checkSdk() {
String path = cloudSdkDirectoryField.getText();

private void checkSdkInBackground() {
final String path = cloudSdkDirectoryField.getText();
ApplicationManager.getApplication().executeOnPooledThread(new
CloudSdkCheckerRunnable(path));

I could, but wouldn't that mean the validation would only occur when the
user clicks "save"? Right now, the validation takes place as soon as the
user selects the cloud sdk directory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084
,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AHf5HVT8rt8JeX3H7ZFETi0RpJz6lH7Vks5q-zY9gaJpZM4KnwQV>
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084#issuecomment-261005879,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA_cM4zg7eKYgIVV4DG5lNAYJyyq3Je4ks5q-zdugaJpZM4KnwQV
.

@aslo Aha. In that case it's quite alright. I misunderstood from our last discussion with @etanshaul

I think I prefer it.  It seems like the code should be simpler too.
On Wed, Nov 16, 2016 at 3:23 PM, Alex Sloan<EMAIL_ADDRESS>wrote:

@aslo commented on this pull request.
In google-cloud-tools-plugin/src/com/google/cloud/tools/
intellij/appengine/sdk/CloudSdkPanel.java
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084:

     .validateCloudSdk();

 cloudSdkDirectoryField.getTextField().setForeground(JBColor.black);

 warningIcon.setVisible(false);

 warningMessage.setVisible(false);

} catch (AppEngineException aee) {

 cloudSdkDirectoryField.getTextField().setForeground(JBColor.red);

 warningIcon.setVisible(true);

 warningMessage.setVisible(true);

 warningMessage.setText(

     createErrorMessageWithLink(

         GctBundle.message("appengine.cloudsdk.location.invalid.message")));

Set validationResults =

   CloudSdkService.getInstance().validateCloudSdk(Paths.get(path));

// if there are any validation errors, show the first one to the user

FYI Here's another option that uses paragraphs instead of a list. I think
this is better.
[image: screenshot from 2016-11-16 15 22 28]
https://cloud.githubusercontent.com/assets/1039411/20364296/8db03e5c-ac10-11e6-97e1-87635dad7444.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1084,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HS0FNPxt7FswVbb7ZjPQGjxZfVxMks5q-2ZHgaJpZM4KnwQV
.

LGTM


My collection is not displayed

Describe the bug
My collection is shown as empty
To Reproduce
Steps to reproduce the behavior:

Go to https://mtgarena.pro/progress/#SatorArepo

All numbers are 0, except for the vault.
Screenshots

Nevermind, now it is showing. I guess there is some delay in updating the collections in the site's database?


Input vertices had multiple restarts while running load test

Describe the bug
Some of the input vertices had panic and restarted couple of times while running a load test. This was the error seen
panic: Consumer failed with error:
goroutine 276 [running]:
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc003c729c0, {0xc003d84fc0, 0x1, 0x1})
	/Users/yhl01/go/pkg/mod/go.uber.org/zap@v1.19.1/zapcore/entry.go:232 +0x44c
go.uber.org/zap.(*SugaredLogger).log(0xc0001246a0, 0x4, {0x223775f?, 0x25994a0?}, {0x0?, 0x0?, 0xc000054d70?}, {0xc009275f28, 0x1, 0x1})
[Collapse](https://ip.adhoc.splunk.intuit.com/en-US/app/search/search?q=search%20(index%3Do11y-gs)%20((sourcetype%3Deventrouter%20AND%20event.involvedObject.namespace%3Ddev-devx-o11yabstractgs-usw2-stg)%20OR%20(%20kubernetes_namespace%3Ddev-devx-o11yabstractgs-usw2-stg))%20kubernetes_cluster%3Dip-msaas-prod-usw2-k8s%20error%20OR%20exception%20NOT%20%22nats%3A%20no%20keys%20found%22&display.page.search.mode=verbose&dispatch.sample_ratio=1&earliest=1690397288&latest=1690397298.001&sid=1690398079.58771_0E1F1EAB-1964-48F9-8F1D-DA9AE24C48BF#)

To Reproduce
Steps to reproduce the behavior:

Have minimum of 1 pod for source vertex, no max
Inject load (the load when this error occurred was 20k tps)

Expected behavior
No restart was expected
Environment (please complete the following information):

Kubernetes: v4.5.7
Numaflow controller :  v0.0.9-rc4

Additional context
Add any other context about the problem here.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.

looks like in the logger we are reference a nil


[Add] Change the alert.

Details
I want to change the UI of alert
which is showing on failing log in.
Screenshots
Current:

Expected:

Type of Contribution

[ ] Update to an existing Animated Button
[ ] Adding a new Button
[ ] Resolving a bug
[X] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

@soubhik-111 We are using a different library.
So as considering our UI we had decided to use that toast.
Closing this as not required


Reducing/increasing maximum size of backup storage

The following FAQ says "The cost does not change unless you reduce or increase that maximum." I understand that we can set maximum size of backup storage, I couldn't find a topic of how to set the maximum size of backup storage for database - where/how can I set the storage size?
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-faq#how-am-i-charged-for-storage---based-on-what-i-configure-upfront-or-on-what-the-database-uses

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c6183de3-cebc-e546-a5c8-3bd41878bbfd
Version Independent ID: f90294c3-9236-2332-01bc-78fd0adb9374
Content: Azure SQL Database FAQ
Content Source: articles/sql-database/sql-database-faq.md
Service: sql-database
GitHub Login: @CarlRabeler
Microsoft Alias: carlrab

@kazshi Thanks for the feedback. We are actively investigating and will get back to you soon.

@kazshi @anosov1960 Thanks again for your feedback! I have assigned the issue to the content author to evaluate and update as appropriate. Please see the three related questions #14019 #14017 #14013

@anosov1960 @CarlRabeler @Alberto-Vega-MSFT Do you have any updates on this?  Thanks.

@anosov1960 Can you please comment on this customer question?

addressed in this PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/51967
should be live by 10 AM today.

@anosov1960 @CarlRabeler @Alberto-Vega-MSFT Thanks for the update.


Add read_spawn_ids helper func

Add read_spawn_ids helper func
Implement From<X> for various fields of Packet
Fix clippy lints

e.x. to_send.drain(..).collect() is better written as mem::take(&mut to_send) - take returns the current value and replaces the variable with a new value, as long as it the type implements Default

Nice, thanks!


grype: 0.79.0 -> 0.79.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/anchore/grype/releases.
meta.description for grype is: Vulnerability scanner for container images and filesystems
meta.homepage for grype is: https://github.com/anchore/grype
meta.changelog for grype is: https://github.com/anchore/grype/releases/tag/v0.78.0
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.78.0 with grep in /nix/store/dp9k964n0f07kf3dk4086rh16fw5s3bk-grype-0.78.0
found 0.78.0 in filename of file in /nix/store/dp9k964n0f07kf3dk4086rh16fw5s3bk-grype-0.78.0

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

grype
sbomnix

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/c751265221416fea21e14417eb121edc3c8c07e4#grype

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

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

3 packages built:

grype
sbomnix
sbomnix.dist

Maintainer pings
cc @fabaff @06kellyjac @kashw2 for testing.

@ofborg eval

hmm ofborg seems borked for this PR in particular :eyes:

This can probably be closed since https://github.com/NixOS/nixpkgs/pull/320286

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/grype/versions.
meta.description for grype is: Vulnerability scanner for container images and filesystems
meta.homepage for grype is: https://github.com/anchore/grype
meta.changelog for grype is: https://github.com/anchore/grype/releases/tag/v0.79.1
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.79.1 with grep in /nix/store/qhr5lvx9hf6324r8qvp1k3l01vrmq1x4-grype-0.79.1
found 0.79.1 in filename of file in /nix/store/qhr5lvx9hf6324r8qvp1k3l01vrmq1x4-grype-0.79.1

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

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

grype
sbomnix

Instructions to test this update (click to expand)

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

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

Or:
nix build github:r-ryantm/nixpkgs/d0df3dcc3a3c5279a670d009588de13274b6d1c1#grype

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

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

3 packages built:

grype
sbomnix
sbomnix.dist

Maintainer pings
cc @fabaff @06kellyjac @kashw2 for testing.

@NixOS/nixpkgs-merge-bot merge


Please npm publish v0.1.1

https://github.com/jimmycuadra/shellwords/compare/v0.1.0...master
The license information added in 365080696b15e7bff6d59b556bb7d5d85273b33f, but it isn't available on npm.
Could you publish a new version like v0.1.1 to npm?

Done!


Upload to Hackage?

I was looking for a stream tar library and found this repo but it's not up on Hackage.

Indeed, I was always planning to finish it off... to the point where I now can't remember what really needs finishing :) Have you had a play with it? If so, does it do what you want?

Any updates on this, I would like to see this on hackage as well, as this package isn't the easiest to find.

Closing issues here now that tar-conduit is out. I no longer need this project, so it's unlikely to see the light of day any time soon.

Got it. Thanks.


add cli interface for dedicated deployment

Description
add cli interface for dedicated deployment
List any dependencies that are required for this change.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

How has this change been tested, please provide a testcase or example of how you tested the change?
Tested in staging.
Any specific deployment considerations
For example, documentation changes, usability, usage/costs, secrets, etc.
Docs

[ ] Docs updated? What were the changes:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: PacificDou:x: pre-commit-ci[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


Suggestion: Rethink Handling of Unknown Commands

When encountering unknown commands, the current implementation returns specific values:

ESC_UNKNOWN ends with:
return 033;
CX_UNKNOWN ends with:
return CTRL('x');
This can result in some characters being accidentally entered into the buffer. I made a code change in my fork of emsys , but am not submitting a pull request because I am not sure if it's the best solution.

My code change was to comment out the "return CTRL('x');" in CX_UNKNOWN, and ESC_UNKNOWN and discard the rest of the escape sequence:
	ESC_UNKNOWN:;
		char seqR[32];
		seqR[0] = 0;
		char buf[8];
		for (int i = 0; seq[i]; i++) {
			if (seq[i] < ' ') {
				sprintf(buf, "C-%c ", seq[i]+'`');
			} else {
				sprintf(buf, "%c ", seq[i]);
			}
			strcat(seqR, buf);
		}
		editorSetStatusMessage("Unknown command M-%s", seqR);
		// Discard the rest of the escape sequence
    	char discard[32];
    	read(STDIN_FILENO, discard, sizeof(discard)); // Read and discard remaining characters
		//return 033;

The main thing I'm worried about here is that it might sit there discarding everything if whatever condition it wants isn't met. I haven't had the chance to test this yet though so it may be fine.

I just accidentally discovered that if you press C-x C-k C-k, you will get a Segmentation fault (core dumped).

I just accidentally discovered that if you press C-x C-k C-k, you will get a Segmentation fault (core dumped). I tested this on current version and also on version 7652c69 .

Looks like ^K isn't checking for an empty buffer. You don't need to C-x C-k - just C-k on an empty buffer.

ref #34


[BUG] String(s) terminate after 2000 chars

Describe the bug
Within some documents, text fields where the length > 2000 chars are 'interrupted' and no longer treated as strings.
When using the reindex API, I received several mapper_parsing_exception failures that indicated string content was being interpreted literally. Such as below:
{
    "type" : "mapper_parsing_exception",
    "reason" : "failed to parse",
    "caused_by" : {
        "type" : "illegal_argument_exception",
        "reason" : "object field starting or ending with a [.] makes object resolution ambiguous: [\"John is somebody who is going to be a real fighter for the working class ... and I hope very much he joins us in the United States Senate.\"]"
    }
}

In OpenSearch Dashboards (OSD), this behaviour can be seen in the syntax highlighting, where the string/text stops being formatted in green at the ~2000 char mark. See screenshot.
To Reproduce
Steps to reproduce the behavior:

Index a document containing a text field where the string length > 2000 chars.

Potentially, this string may need to be a multiline string.

Attempt a reindex operation with a painless script that does something with the doc _source.

Plugins
All of 'em -- see AWS OSS Plugins, full output from _cat/plugins is here.
Host/Environment (please complete the following information):

OpenSearch 2.3

Additional context

Using one of the broken strings, I calculated the length of the portion that was being treated as a string. Approx. 327 words, 1997 chars.

I thought that perhaps the "ignore_above" mapping/setting [1] may be to blame, but this does not seem to be the case.

This may be a Lucene issue as there's a byte limit of 32766, or 32KB. If a field contains UTF-8 text with non-ASCII characters, each char may take up 4 bytes, so the character limit would be 8191 — (32766 / 4 = 8191) [2]

Again though, the ~2000 character string cut-off point seems to be well-below this number.

I wrote a painless script to return the length of a string for one of the documents where this broken string issue occurs. The string cutoff (where text is no longer green in OS Dashboards) is also just under 2000 chars, however, the query executes successfully and returns a length of 4396.

Query uses params._source['my_broken_field'].toString().length()

[1] https://www.elastic.co/guide/en/elasticsearch/reference/current/ignore-above.html
[2] https://issues.apache.org/jira/browse/LUCENE-5472

Hello, OpenSearch!
Could I take this issue as my first issue as a CCI member?

@Rafae11oB Sure please go for it. Issue already assigned to you. Thanks for your contribution

Hi @Rafae11oB - Did you get a chance to take a look into this?


Slack Relay

Relay Plugin for Slack support.
To be implemented following the new guidelines for bots via Slack apps.
https://github.com/slack-ruby/slack-ruby-client

Implemented with release 0.3.0


Building wheel for opencv-python (pyproject.toml) - MacOS

I am trying to install opencv-python but it is always stuck at: Building wheel for opencv-python (pyproject.toml). I tried installing the older versions but it happens with all of them, just stays at building wheel for an hour and nothing happens. I have done pip install --upgrade pip setuptools wheel as well but no success yet.
OS: MacOS Mojave
Command: pip3 install opencv-python
Issue:

Any update??

I have the same problem and have tested all solutions I could find but no luck :(
macOS: Mojave
Python Version: 3.9
Pip Version: 22.1.1

Hello, I've got (almost) the same problem.
ERROR: Failed building wheel for opencv-python
ERROR: Could not build wheels for opencv-python, which is required to install pyproject.toml-based projects
macOS El Capitan
PyCharm
Python : 3.9.13
pip version : 22.1.2
I tried to install a previous version of openCV but that doesn't work either.

please send solutions if anyone have?

I am installing from Databricks pypl, also had the same issue. Opencv was working until 10:10am UK time for me, and does not work after 11am. The building wheel stage took an hour and I had to end this process. Uninstalling and reinstalling was not helpful. There were no error message and all dependencies are installed.

I am installing from Databricks pypl, also had the same issue. Opencv was working until 10:10am UK time for me, and does not work after 11am. The building wheel stage took an hour and I had to end this process. Uninstalling and reinstalling was not helpful. There were no error message and all dependencies are installed.

I tried installing through !pip install in notebook cell, and the installation is successful but took 33mins. output is listed below:
Building wheel for opencv-python (PEP 517) ... done
Created wheel for opencv-python: filename=opencv_python-<IP_ADDRESS>-cp38-cp38-linux_x86_64.whl size=28434185 sha256=d20c1d2f7c71ca7d9bc47bc6df9217884ee72975f06b2086940c1166ba25d243
Stored in directory: /root/.cache/pip/wheels/8e/34/bd/2f3c3b5c662168447e087c53bde8c070a19313eeb6eb95d1e2
Successfully built opencv-python
Installing collected packages: opencv-python
Successfully installed opencv-python-<IP_ADDRESS>
WARNING: You are using pip version 21.0.1; however, version 22.1.2 is available.
You should consider upgrading via the '/databricks/python3/bin/python -m pip install --upgrade pip' command.
Removed build tracker: '/tmp/pip-req-tracker-0e6xg2r4'

Hello!
It looks like your OS is older than macOS Catalina (10.15.7) which is used for building OpenCV Python packages. That's why you not just install a pre-built wheel (.whl), but build a package using the source package (.tar.gz) what spends some time (~30min-1h).
Could you add --verbose flag for pip command (e.g. python3 -m pip install opencv-python --verbose), it will show more information why package is not installed, and provide a more detailed log?
By the way, the new OpenCV release has happened (4.6.0), you can try to use the latest version of opencv-python Python package installing it (link to PyPI):
python3 -m pip install opencv-python==<IP_ADDRESS> --verbose

I have same problem on Ubuntu! I used the command python3 -m pip install opencv-python==<IP_ADDRESS> --verbose, but a new similar error appeared, with the same identification, but in another part of the process!

have anyone got any solution?
OSx- El Captain
Pip3: 22.2.2
Python: 3.10

I also experience this issue when installing opencv-contrib-python-headless in both python 3.10 and python 3.8 on macOS Mojave.

(MD) (base) MacBook-Air-di-Gianluca:GUI Gianluca$ python3 --version
Python 3.7.6
(MD) (base) MacBook-Air-di-Gianluca:GUI Gianluca$ pip3 --version
pip 22.2.2 from /Users/Gianluca/PycharmProjects/untitled/kivyMD/MD/lib/python3.7/site-packages/pip (python 3.7)
(MD) (base) MacBook-Air-di-Gianluca:GUI Gianluca$ pip install opencv-contrib-python
Collecting opencv-contrib-python
Downloading opencv-contrib-python-<IP_ADDRESS>.tar.gz (149.9 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 149.9/149.9 MB 2.1 MB/s eta 0:00:00
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Collecting numpy>=1.14.5
Downloading numpy-1.21.6-cp37-cp37m-macosx_10_9_x86_64.whl (16.9 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 16.9/16.9 MB 6.8 MB/s eta 0:00:00
Building wheels for collected packages: opencv-contrib-python
Building wheel for opencv-contrib-python (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for opencv-contrib-python (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [2605 lines of output]
Not searching for unused variables given on the command line.
CMake Error: CMake was unable to find a build program corresponding to "Ninja".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
-- Configuring incomplete, errors occurred!
See also "/private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/_cmake_test_compile/build/CMakeFiles/CMakeOutput.log".
Not searching for unused variables given on the command line.
-- The C compiler identification is AppleClang <IP_ADDRESS>00033
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00033
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/_cmake_test_compile/build
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00033
-- The C compiler identification is AppleClang <IP_ADDRESS>00033
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- ocv_init_download: OpenCV source tree is not fetched as git repository. 3rdparty resources will be downloaded from github.com by default.
-- Detected processor: x86_64
-- Found PythonInterp: /Users/Gianluca/PycharmProjects/untitled/kivyMD/MD/bin/python3 (found suitable version "3.7.6", minimum required is "2.7")
CMake Warning at cmake/OpenCVDetectPython.cmake:81 (message):
CMake's 'find_host_package(PythonInterp 2.7)' found wrong Python version:
    PYTHON_EXECUTABLE=/Users/Gianluca/PycharmProjects/untitled/kivyMD/MD/bin/python3

    PYTHON_VERSION_STRING=3.7.6

    Consider providing the 'PYTHON2_EXECUTABLE' variable via CMake command line
    or environment variables

  Call Stack (most recent call first):
    cmake/OpenCVDetectPython.cmake:271 (find_python)
    CMakeLists.txt:628 (include)

  -- Found Python2: /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 (found version "2.7.16") found components: Interpreter
  -- Found PythonInterp: /System/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 (found version "2.7.16")
  -- Could NOT find PythonLibs: Found unsuitable version "3.7.6", but required is exact version "2.7.16" (found /Users/Gianluca/opt/anaconda3/lib/libpython3.7m.dylib)
  -- Found PythonInterp: /Users/Gianluca/PycharmProjects/untitled/kivyMD/MD/bin/python3 (found suitable version "3.7.6", minimum required is "3.2")
  -- Found PythonLibs: /Users/Gianluca/opt/anaconda3/lib/libpython3.7m.dylib (found suitable exact version "3.7.6")
  -- Looking for ccache - not found
  -- Performing Test HAVE_CXX_FSIGNED_CHAR
  -- Performing Test HAVE_CXX_FSIGNED_CHAR - Success
  -- Performing Test HAVE_C_FSIGNED_CHAR
  -- Performing Test HAVE_C_FSIGNED_CHAR - Success
  -- Performing Test HAVE_CXX_W
  -- Performing Test HAVE_CXX_W - Success
  -- Performing Test HAVE_C_W
  -- Performing Test HAVE_C_W - Success
  -- Performing Test HAVE_CXX_WALL
  -- Performing Test HAVE_CXX_WALL - Success
  -- Performing Test HAVE_C_WALL
  -- Performing Test HAVE_C_WALL - Success
  -- Performing Test HAVE_CXX_WRETURN_TYPE
  -- Performing Test HAVE_CXX_WRETURN_TYPE - Success
  -- Performing Test HAVE_C_WRETURN_TYPE
  -- Performing Test HAVE_C_WRETURN_TYPE - Success
  -- Performing Test HAVE_CXX_WNON_VIRTUAL_DTOR
  -- Performing Test HAVE_CXX_WNON_VIRTUAL_DTOR - Success
  -- Performing Test HAVE_C_WNON_VIRTUAL_DTOR
  -- Performing Test HAVE_C_WNON_VIRTUAL_DTOR - Success
  -- Performing Test HAVE_CXX_WADDRESS
  -- Performing Test HAVE_CXX_WADDRESS - Success
  -- Performing Test HAVE_C_WADDRESS
  -- Performing Test HAVE_C_WADDRESS - Success
  -- Performing Test HAVE_CXX_WSEQUENCE_POINT
  -- Performing Test HAVE_CXX_WSEQUENCE_POINT - Success
  -- Performing Test HAVE_C_WSEQUENCE_POINT
  -- Performing Test HAVE_C_WSEQUENCE_POINT - Success
  -- Performing Test HAVE_CXX_WFORMAT
  -- Performing Test HAVE_CXX_WFORMAT - Success
  -- Performing Test HAVE_C_WFORMAT
  -- Performing Test HAVE_C_WFORMAT - Success
  -- Performing Test HAVE_CXX_WFORMAT_SECURITY
  -- Performing Test HAVE_CXX_WFORMAT_SECURITY - Success
  -- Performing Test HAVE_C_WFORMAT_SECURITY
  -- Performing Test HAVE_C_WFORMAT_SECURITY - Success
  -- Performing Test HAVE_CXX_WMISSING_DECLARATIONS
  -- Performing Test HAVE_CXX_WMISSING_DECLARATIONS - Success
  -- Performing Test HAVE_C_WMISSING_DECLARATIONS
  -- Performing Test HAVE_C_WMISSING_DECLARATIONS - Success
  -- Performing Test HAVE_CXX_WMISSING_PROTOTYPES
  -- Performing Test HAVE_CXX_WMISSING_PROTOTYPES - Success
  -- Performing Test HAVE_C_WMISSING_PROTOTYPES
  -- Performing Test HAVE_C_WMISSING_PROTOTYPES - Success
  -- Performing Test HAVE_CXX_WSTRICT_PROTOTYPES
  -- Performing Test HAVE_CXX_WSTRICT_PROTOTYPES - Success
  -- Performing Test HAVE_C_WSTRICT_PROTOTYPES
  -- Performing Test HAVE_C_WSTRICT_PROTOTYPES - Success
  -- Performing Test HAVE_CXX_WUNDEF
  -- Performing Test HAVE_CXX_WUNDEF - Success
  -- Performing Test HAVE_C_WUNDEF
  -- Performing Test HAVE_C_WUNDEF - Success
  -- Performing Test HAVE_CXX_WINIT_SELF
  -- Performing Test HAVE_CXX_WINIT_SELF - Success
  -- Performing Test HAVE_C_WINIT_SELF
  -- Performing Test HAVE_C_WINIT_SELF - Success
  -- Performing Test HAVE_CXX_WPOINTER_ARITH
  -- Performing Test HAVE_CXX_WPOINTER_ARITH - Success
  -- Performing Test HAVE_C_WPOINTER_ARITH
  -- Performing Test HAVE_C_WPOINTER_ARITH - Success
  -- Performing Test HAVE_CXX_WSHADOW
  -- Performing Test HAVE_CXX_WSHADOW - Success
  -- Performing Test HAVE_C_WSHADOW
  -- Performing Test HAVE_C_WSHADOW - Success
  -- Performing Test HAVE_CXX_WSIGN_PROMO
  -- Performing Test HAVE_CXX_WSIGN_PROMO - Success
  -- Performing Test HAVE_C_WSIGN_PROMO
  -- Performing Test HAVE_C_WSIGN_PROMO - Success
  -- Performing Test HAVE_CXX_WUNINITIALIZED
  -- Performing Test HAVE_CXX_WUNINITIALIZED - Success
  -- Performing Test HAVE_C_WUNINITIALIZED
  -- Performing Test HAVE_C_WUNINITIALIZED - Success
  -- Performing Test HAVE_CXX_WNO_DELETE_NON_VIRTUAL_DTOR
  -- Performing Test HAVE_CXX_WNO_DELETE_NON_VIRTUAL_DTOR - Success
  -- Performing Test HAVE_C_WNO_DELETE_NON_VIRTUAL_DTOR
  -- Performing Test HAVE_C_WNO_DELETE_NON_VIRTUAL_DTOR - Success
  -- Performing Test HAVE_CXX_WNO_UNNAMED_TYPE_TEMPLATE_ARGS
  -- Performing Test HAVE_CXX_WNO_UNNAMED_TYPE_TEMPLATE_ARGS - Success
  -- Performing Test HAVE_C_WNO_UNNAMED_TYPE_TEMPLATE_ARGS
  -- Performing Test HAVE_C_WNO_UNNAMED_TYPE_TEMPLATE_ARGS - Success
  -- Performing Test HAVE_CXX_WNO_COMMENT
  -- Performing Test HAVE_CXX_WNO_COMMENT - Success
  -- Performing Test HAVE_C_WNO_COMMENT
  -- Performing Test HAVE_C_WNO_COMMENT - Success
  -- Performing Test HAVE_CXX_FDIAGNOSTICS_SHOW_OPTION
  -- Performing Test HAVE_CXX_FDIAGNOSTICS_SHOW_OPTION - Success
  -- Performing Test HAVE_C_FDIAGNOSTICS_SHOW_OPTION
  -- Performing Test HAVE_C_FDIAGNOSTICS_SHOW_OPTION - Success
  -- Performing Test HAVE_CXX_WNO_LONG_LONG
  -- Performing Test HAVE_CXX_WNO_LONG_LONG - Success
  -- Performing Test HAVE_C_WNO_LONG_LONG
  -- Performing Test HAVE_C_WNO_LONG_LONG - Success
  -- Performing Test HAVE_CXX_QUNUSED_ARGUMENTS
  -- Performing Test HAVE_CXX_QUNUSED_ARGUMENTS - Success
  -- Performing Test HAVE_C_QUNUSED_ARGUMENTS
  -- Performing Test HAVE_C_QUNUSED_ARGUMENTS - Success
  -- Performing Test HAVE_CXX_WNO_SEMICOLON_BEFORE_METHOD_BODY
  -- Performing Test HAVE_CXX_WNO_SEMICOLON_BEFORE_METHOD_BODY - Success
  -- Performing Test HAVE_C_WNO_SEMICOLON_BEFORE_METHOD_BODY
  -- Performing Test HAVE_C_WNO_SEMICOLON_BEFORE_METHOD_BODY - Success
  -- Performing Test HAVE_CXX_FFUNCTION_SECTIONS
  -- Performing Test HAVE_CXX_FFUNCTION_SECTIONS - Success
  -- Performing Test HAVE_C_FFUNCTION_SECTIONS
  -- Performing Test HAVE_C_FFUNCTION_SECTIONS - Success
  -- Performing Test HAVE_CXX_FDATA_SECTIONS
  -- Performing Test HAVE_CXX_FDATA_SECTIONS - Success
  -- Performing Test HAVE_C_FDATA_SECTIONS
  -- Performing Test HAVE_C_FDATA_SECTIONS - Success
  -- Performing Test HAVE_CPU_SSE_SUPPORT (check file: cmake/checks/cpu_sse.cpp)
  -- Performing Test HAVE_CPU_SSE_SUPPORT - Success
  -- Performing Test HAVE_CPU_SSE2_SUPPORT (check file: cmake/checks/cpu_sse2.cpp)
  -- Performing Test HAVE_CPU_SSE2_SUPPORT - Success
  -- Performing Test HAVE_CPU_SSE3_SUPPORT (check file: cmake/checks/cpu_sse3.cpp)
  -- Performing Test HAVE_CPU_SSE3_SUPPORT - Success
  -- Performing Test HAVE_CPU_SSSE3_SUPPORT (check file: cmake/checks/cpu_ssse3.cpp)
  -- Performing Test HAVE_CPU_SSSE3_SUPPORT - Success
  -- Performing Test HAVE_CPU_SSE4_1_SUPPORT (check file: cmake/checks/cpu_sse41.cpp)
  -- Performing Test HAVE_CPU_SSE4_1_SUPPORT - Success
  -- Performing Test HAVE_CPU_POPCNT_SUPPORT (check file: cmake/checks/cpu_popcnt.cpp)
  -- Performing Test HAVE_CPU_POPCNT_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MPOPCNT (check file: cmake/checks/cpu_popcnt.cpp)
  -- Performing Test HAVE_CXX_MPOPCNT - Success
  -- Performing Test HAVE_CPU_SSE4_2_SUPPORT (check file: cmake/checks/cpu_sse42.cpp)
  -- Performing Test HAVE_CPU_SSE4_2_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MSSE4_2 (check file: cmake/checks/cpu_sse42.cpp)
  -- Performing Test HAVE_CXX_MSSE4_2 - Success
  -- Performing Test HAVE_CPU_FP16_SUPPORT (check file: cmake/checks/cpu_fp16.cpp)
  -- Performing Test HAVE_CPU_FP16_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MF16C (check file: cmake/checks/cpu_fp16.cpp)
  -- Performing Test HAVE_CXX_MF16C - Success
  -- Performing Test HAVE_CXX_MFMA
  -- Performing Test HAVE_CXX_MFMA - Success
  -- Performing Test HAVE_CPU_AVX_SUPPORT (check file: cmake/checks/cpu_avx.cpp)
  -- Performing Test HAVE_CPU_AVX_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX (check file: cmake/checks/cpu_avx.cpp)
  -- Performing Test HAVE_CXX_MAVX - Success
  -- Performing Test HAVE_CPU_AVX2_SUPPORT (check file: cmake/checks/cpu_avx2.cpp)
  -- Performing Test HAVE_CPU_AVX2_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX2 (check file: cmake/checks/cpu_avx2.cpp)
  -- Performing Test HAVE_CXX_MAVX2 - Success
  -- Performing Test HAVE_CPU_AVX_512F_SUPPORT (check file: cmake/checks/cpu_avx512.cpp)
  -- Performing Test HAVE_CPU_AVX_512F_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F (check file: cmake/checks/cpu_avx512.cpp)
  -- Performing Test HAVE_CXX_MAVX512F - Success
  -- Performing Test HAVE_CPU_AVX512_COMMON_SUPPORT (check file: cmake/checks/cpu_avx512common.cpp)
  -- Performing Test HAVE_CPU_AVX512_COMMON_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD (check file: cmake/checks/cpu_avx512common.cpp)
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD - Success
  -- Performing Test HAVE_CPU_AVX512_KNL_SUPPORT (check file: cmake/checks/cpu_avx512knl.cpp)
  -- Performing Test HAVE_CPU_AVX512_KNL_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512ER_MAVX512PF (check file: cmake/checks/cpu_avx512knl.cpp)
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512ER_MAVX512PF - Success
  -- Performing Test HAVE_CPU_AVX512_KNM_SUPPORT (check file: cmake/checks/cpu_avx512knm.cpp)
  -- Performing Test HAVE_CPU_AVX512_KNM_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512ER_MAVX512PF_MAVX5124FMAPS_MAVX5124VNNIW_MAVX512VPOPCNTDQ (check file: cmake/checks/cpu_avx512knm.cpp)
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512ER_MAVX512PF_MAVX5124FMAPS_MAVX5124VNNIW_MAVX512VPOPCNTDQ - Failed
  -- AVX512_KNM is not supported by C++ compiler
  -- Performing Test HAVE_CPU_AVX512_SKX_SUPPORT (check file: cmake/checks/cpu_avx512skx.cpp)
  -- Performing Test HAVE_CPU_AVX512_SKX_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ (check file: cmake/checks/cpu_avx512skx.cpp)
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ - Success
  -- Performing Test HAVE_CPU_AVX512_CNL_SUPPORT (check file: cmake/checks/cpu_avx512cnl.cpp)
  -- Performing Test HAVE_CPU_AVX512_CNL_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ_MAVX512IFMA_MAVX512VBMI (check file: cmake/checks/cpu_avx512cnl.cpp)
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ_MAVX512IFMA_MAVX512VBMI - Success
  -- Performing Test HAVE_CPU_AVX512_CLX_SUPPORT (check file: cmake/checks/cpu_avx512clx.cpp)
  -- Performing Test HAVE_CPU_AVX512_CLX_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ_MAVX512VNNI (check file: cmake/checks/cpu_avx512clx.cpp)
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ_MAVX512VNNI - Success
  -- Performing Test HAVE_CPU_AVX512_ICL_SUPPORT (check file: cmake/checks/cpu_avx512icl.cpp)
  -- Performing Test HAVE_CPU_AVX512_ICL_SUPPORT - Failed
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ_MAVX512IFMA_MAVX512VBMI_MAVX512VNNI_MAVX512VBMI2_MAVX512BITALG_MAVX512VPOPCNTDQ (check file: cmake/checks/cpu_avx512icl.cpp)
  -- Performing Test HAVE_CXX_MAVX512F_MAVX512CD_MAVX512VL_MAVX512BW_MAVX512DQ_MAVX512IFMA_MAVX512VBMI_MAVX512VNNI_MAVX512VBMI2_MAVX512BITALG_MAVX512VPOPCNTDQ - Success
  -- Performing Test HAVE_CPU_BASELINE_FLAGS
  -- Performing Test HAVE_CPU_BASELINE_FLAGS - Success
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_SSE4_2
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_SSE4_2 - Success
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_FP16
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_FP16 - Success
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_AVX
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_AVX - Success
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_AVX2
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_AVX2 - Success
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_AVX512_SKX
  -- Performing Test HAVE_CPU_DISPATCH_FLAGS_AVX512_SKX - Success
  -- Performing Test HAVE_CXX_FVISIBILITY_HIDDEN
  -- Performing Test HAVE_CXX_FVISIBILITY_HIDDEN - Success
  -- Performing Test HAVE_C_FVISIBILITY_HIDDEN
  -- Performing Test HAVE_C_FVISIBILITY_HIDDEN - Success
  -- Performing Test HAVE_CXX_FVISIBILITY_INLINES_HIDDEN
  -- Performing Test HAVE_CXX_FVISIBILITY_INLINES_HIDDEN - Success
  -- Performing Test HAVE_C_FVISIBILITY_INLINES_HIDDEN
  -- Performing Test HAVE_C_FVISIBILITY_INLINES_HIDDEN - Success
  -- Performing Test HAVE_LINK_AS_NEEDED
  -- Performing Test HAVE_LINK_AS_NEEDED - Failed
  -- Performing Test HAVE_LINK_NO_UNDEFINED
  -- Performing Test HAVE_LINK_NO_UNDEFINED - Failed
  -- Looking for posix_memalign
  -- Looking for posix_memalign - found
  -- Looking for malloc.h
  -- Looking for malloc.h - not found
  -- Looking for fseeko
  -- Looking for fseeko - found
  -- Looking for unistd.h
  -- Looking for unistd.h - found
  -- Looking for sys/types.h
  -- Looking for sys/types.h - found
  -- Looking for stdint.h
  -- Looking for stdint.h - found
  -- Looking for stddef.h
  -- Looking for stddef.h - found
  -- Check size of off64_t
  -- Check size of off64_t - failed
  -- Performing Test HAVE_C_WNO_SHORTEN_64_TO_32
  -- Performing Test HAVE_C_WNO_SHORTEN_64_TO_32 - Success
  -- Performing Test HAVE_C_WNO_ATTRIBUTES
  -- Performing Test HAVE_C_WNO_ATTRIBUTES - Success
  -- Performing Test HAVE_C_WNO_STRICT_PROTOTYPES
  -- Performing Test HAVE_C_WNO_STRICT_PROTOTYPES - Success
  -- Performing Test HAVE_C_WNO_MISSING_PROTOTYPES
  -- Performing Test HAVE_C_WNO_MISSING_PROTOTYPES - Success
  -- Performing Test HAVE_C_WNO_MISSING_DECLARATIONS
  -- Performing Test HAVE_C_WNO_MISSING_DECLARATIONS - Success
  -- Performing Test HAVE_C_WNO_SHIFT_NEGATIVE_VALUE
  -- Performing Test HAVE_C_WNO_SHIFT_NEGATIVE_VALUE - Success
  -- Performing Test HAVE_C_WNO_UNDEF
  -- Performing Test HAVE_C_WNO_UNDEF - Success
  -- Performing Test HAVE_C_WNO_IMPLICIT_FALLTHROUGH
  -- Performing Test HAVE_C_WNO_IMPLICIT_FALLTHROUGH - Success
  -- Performing Test HAVE_C_WNO_UNUSED_PARAMETER
  -- Performing Test HAVE_C_WNO_UNUSED_PARAMETER - Success
  -- Performing Test HAVE_C_WNO_SIGN_COMPARE
  -- Performing Test HAVE_C_WNO_SIGN_COMPARE - Success
  -- libjpeg-turbo: VERSION = 2.1.2, BUILD = opencv-4.6.0-libjpeg-turbo
  -- Check size of size_t
  -- Check size of size_t - done
  -- Check size of unsigned long
  -- Check size of unsigned long - done
  -- Performing Test HAVE_BUILTIN_CTZL
  -- Performing Test HAVE_BUILTIN_CTZL - Success
  -- Looking for include file locale.h
  -- Looking for include file locale.h - found
  -- Looking for include file stdlib.h
  -- Looking for include file stdlib.h - found
  -- Looking for include file sys/types.h
  -- Looking for include file sys/types.h - found
  -- Looking for assert.h
  -- Looking for assert.h - found
  -- Looking for dlfcn.h
  -- Looking for dlfcn.h - found
  -- Looking for fcntl.h
  -- Looking for fcntl.h - found
  -- Looking for inttypes.h
  -- Looking for inttypes.h - found
  -- Looking for io.h
  -- Looking for io.h - not found
  -- Looking for limits.h
  -- Looking for limits.h - found
  -- Looking for memory.h
  -- Looking for memory.h - found
  -- Looking for search.h
  -- Looking for search.h - found
  -- Looking for string.h
  -- Looking for string.h - found
  -- Looking for strings.h
  -- Looking for strings.h - found
  -- Looking for sys/time.h
  -- Looking for sys/time.h - found
  -- Looking for unistd.h
  -- Looking for unistd.h - found
  -- Performing Test C_HAS_inline
  -- Performing Test C_HAS_inline - Success
  -- Check size of signed short
  -- Check size of signed short - done
  -- Check size of unsigned short
  -- Check size of unsigned short - done
  -- Check size of signed int
  -- Check size of signed int - done
  -- Check size of unsigned int
  -- Check size of unsigned int - done
  -- Check size of signed long
  -- Check size of signed long - done
  -- Check size of signed long long
  -- Check size of signed long long - done
  -- Check size of unsigned long long
  -- Check size of unsigned long long - done
  -- Check size of unsigned char *
  -- Check size of unsigned char * - done
  -- Check size of ptrdiff_t
  -- Check size of ptrdiff_t - done
  -- Check size of INT8
  -- Check size of INT8 - failed
  -- Check size of INT16
  -- Check size of INT16 - failed
  -- Check size of INT32
  -- Check size of INT32 - failed
  -- Looking for floor
  -- Looking for floor - found
  -- Looking for pow
  -- Looking for pow - found
  -- Looking for sqrt
  -- Looking for sqrt - found
  -- Looking for isascii
  -- Looking for isascii - found
  -- Looking for memset
  -- Looking for memset - found
  -- Looking for mmap
  -- Looking for mmap - found
  -- Looking for getopt
  -- Looking for getopt - found
  -- Looking for memmove
  -- Looking for memmove - found
  -- Looking for setmode
  -- Looking for setmode - found
  -- Looking for strcasecmp
  -- Looking for strcasecmp - found
  -- Looking for strchr
  -- Looking for strchr - found
  -- Looking for strrchr
  -- Looking for strrchr - found
  -- Looking for strstr
  -- Looking for strstr - found
  -- Looking for strtol
  -- Looking for strtol - found
  -- Looking for strtol
  -- Looking for strtol - found
  -- Looking for strtoull
  -- Looking for strtoull - found
  -- Looking for lfind
  -- Looking for lfind - found
  -- Performing Test HAVE_SNPRINTF
  -- Performing Test HAVE_SNPRINTF - Success
  -- Performing Test HAVE_C_WNO_UNUSED_BUT_SET_VARIABLE
  -- Performing Test HAVE_C_WNO_UNUSED_BUT_SET_VARIABLE - Failed
  -- Performing Test HAVE_C_WNO_UNUSED
  -- Performing Test HAVE_C_WNO_UNUSED - Success
  -- Performing Test HAVE_C_WNO_CAST_ALIGN
  -- Performing Test HAVE_C_WNO_CAST_ALIGN - Success
  -- Performing Test HAVE_C_WNO_SHADOW
  -- Performing Test HAVE_C_WNO_SHADOW - Success
  -- Performing Test HAVE_C_WNO_MAYBE_UNINITIALIZED
  -- Performing Test HAVE_C_WNO_MAYBE_UNINITIALIZED - Failed
  -- Performing Test HAVE_C_WNO_POINTER_TO_INT_CAST
  -- Performing Test HAVE_C_WNO_POINTER_TO_INT_CAST - Success
  -- Performing Test HAVE_C_WNO_INT_TO_POINTER_CAST
  -- Performing Test HAVE_C_WNO_INT_TO_POINTER_CAST - Success
  -- Performing Test HAVE_C_WNO_MISLEADING_INDENTATION
  -- Performing Test HAVE_C_WNO_MISLEADING_INDENTATION - Failed
  -- Performing Test HAVE_C_WNO_ARRAY_PARAMETER
  -- Performing Test HAVE_C_WNO_ARRAY_PARAMETER - Failed
  -- Performing Test HAVE_CXX_WNO_MISSING_DECLARATIONS
  -- Performing Test HAVE_CXX_WNO_MISSING_DECLARATIONS - Success
  -- Performing Test HAVE_CXX_WNO_UNUSED_PARAMETER
  -- Performing Test HAVE_CXX_WNO_UNUSED_PARAMETER - Success
  -- Performing Test HAVE_CXX_WNO_MISSING_PROTOTYPES
  -- Performing Test HAVE_CXX_WNO_MISSING_PROTOTYPES - Success
  -- Performing Test HAVE_CXX_WNO_UNDEF
  -- Performing Test HAVE_CXX_WNO_UNDEF - Success
  -- Performing Test HAVE_C_STD_C99
  -- Performing Test HAVE_C_STD_C99 - Success
  -- Performing Test HAVE_C_WNO_UNUSED_VARIABLE
  -- Performing Test HAVE_C_WNO_UNUSED_VARIABLE - Success
  -- Performing Test HAVE_C_WNO_UNUSED_FUNCTION
  -- Performing Test HAVE_C_WNO_UNUSED_FUNCTION - Success
  -- Could NOT find OpenJPEG (minimal suitable version: 2.0, recommended version >= 2.3.1). OpenJPEG will be built from sources
  -- Performing Test HAVE_C_WNO_IMPLICIT_CONST_INT_FLOAT_CONVERSION
  -- Performing Test HAVE_C_WNO_IMPLICIT_CONST_INT_FLOAT_CONVERSION - Failed
  -- OpenJPEG: VERSION = 2.4.0, BUILD = opencv-4.6.0-openjp2-2.4.0
  -- Looking for stdio.h
  -- Looking for stdio.h - found
  -- Looking for math.h
  -- Looking for math.h - found
  -- Looking for float.h
  -- Looking for float.h - found
  -- Looking for time.h
  -- Looking for time.h - found
  -- Looking for stdarg.h
  -- Looking for stdarg.h - found
  -- Looking for ctype.h
  -- Looking for ctype.h - found
  -- Looking for stdint.h
  -- Looking for stdint.h - found
  -- Looking for inttypes.h
  -- Looking for inttypes.h - found
  -- Looking for sys/stat.h
  -- Looking for sys/stat.h - found
  -- Looking for include file malloc.h
  -- Looking for include file malloc.h - not found
  -- Looking for _aligned_malloc
  -- Looking for _aligned_malloc - not found
  -- Looking for posix_memalign
  -- Looking for posix_memalign - found
  -- Looking for memalign
  -- Looking for memalign - not found
  -- Performing Test HAVE_C_WNO_CAST_FUNCTION_TYPE
  -- Performing Test HAVE_C_WNO_CAST_FUNCTION_TYPE - Failed
  -- OpenJPEG libraries will be built from sources: libopenjp2 (version "2.4.0")
  -- Performing Test HAVE_C_WNO_NULL_POINTER_SUBTRACTION
  -- Performing Test HAVE_C_WNO_NULL_POINTER_SUBTRACTION - Failed
  -- Performing Test HAVE_CXX_WNO_SHADOW
  -- Performing Test HAVE_CXX_WNO_SHADOW - Success
  -- Performing Test HAVE_CXX_WNO_UNUSED
  -- Performing Test HAVE_CXX_WNO_UNUSED - Success
  -- Performing Test HAVE_CXX_WNO_SIGN_COMPARE
  -- Performing Test HAVE_CXX_WNO_SIGN_COMPARE - Success
  -- Performing Test HAVE_CXX_WNO_UNINITIALIZED
  -- Performing Test HAVE_CXX_WNO_UNINITIALIZED - Success
  -- Performing Test HAVE_CXX_WNO_SWITCH
  -- Performing Test HAVE_CXX_WNO_SWITCH - Success
  -- Performing Test HAVE_CXX_WNO_PARENTHESES
  -- Performing Test HAVE_CXX_WNO_PARENTHESES - Success
  -- Performing Test HAVE_CXX_WNO_ARRAY_BOUNDS
  -- Performing Test HAVE_CXX_WNO_ARRAY_BOUNDS - Success
  -- Performing Test HAVE_CXX_WNO_EXTRA
  -- Performing Test HAVE_CXX_WNO_EXTRA - Success
  -- Performing Test HAVE_CXX_WNO_DEPRECATED_DECLARATIONS
  -- Performing Test HAVE_CXX_WNO_DEPRECATED_DECLARATIONS - Success
  -- Performing Test HAVE_CXX_WNO_MISLEADING_INDENTATION
  -- Performing Test HAVE_CXX_WNO_MISLEADING_INDENTATION - Failed
  -- Performing Test HAVE_CXX_WNO_DEPRECATED
  -- Performing Test HAVE_CXX_WNO_DEPRECATED - Success
  -- Performing Test HAVE_CXX_WNO_SUGGEST_OVERRIDE
  -- Performing Test HAVE_CXX_WNO_SUGGEST_OVERRIDE - Failed
  -- Performing Test HAVE_CXX_WNO_INCONSISTENT_MISSING_OVERRIDE
  -- Performing Test HAVE_CXX_WNO_INCONSISTENT_MISSING_OVERRIDE - Success
  -- Performing Test HAVE_CXX_WNO_IMPLICIT_FALLTHROUGH
  -- Performing Test HAVE_CXX_WNO_IMPLICIT_FALLTHROUGH - Success
  -- Performing Test HAVE_CXX_WNO_TAUTOLOGICAL_COMPARE
  -- Performing Test HAVE_CXX_WNO_TAUTOLOGICAL_COMPARE - Success
  -- Performing Test HAVE_CXX_WNO_REORDER
  -- Performing Test HAVE_CXX_WNO_REORDER - Success
  -- Performing Test HAVE_CXX_WNO_UNUSED_RESULT
  -- Performing Test HAVE_CXX_WNO_UNUSED_RESULT - Success
  -- Performing Test HAVE_CXX_WNO_IMPLICIT_CONST_INT_FLOAT_CONVERSION
  -- Performing Test HAVE_CXX_WNO_IMPLICIT_CONST_INT_FLOAT_CONVERSION - Failed
  -- IPPICV: Downloading ippicv_2020_mac_intel64_20191018_general.tgz from https://raw.githubusercontent.com/opencv/opencv_3rdparty/a56b6ac6f030c312b2dce17430eef13aed9af274/ippicv/ippicv_2020_mac_intel64_20191018_general.tgz
  -- found Intel IPP (ICV version): 2020.0.0 [2020.0.0 Gold]
  -- at: /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/_skbuild/macosx-10.14-x86_64-3.7/cmake-build/3rdparty/ippicv/ippicv_mac/icv
  -- found Intel IPP Integration Wrappers sources: 2020.0.0
  -- at: /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/_skbuild/macosx-10.14-x86_64-3.7/cmake-build/3rdparty/ippicv/ippicv_mac/iw
  -- Could not find OpenBLAS include. Turning OpenBLAS_FOUND off
  -- Could not find OpenBLAS lib. Turning OpenBLAS_FOUND off
  -- Could NOT find Atlas (missing: Atlas_CBLAS_INCLUDE_DIR Atlas_CLAPACK_INCLUDE_DIR Atlas_BLAS_LIBRARY)
  -- Looking for sgemm_
  -- Looking for sgemm_ - not found
  -- Found Threads: TRUE
  -- Looking for dgemm_
  -- Looking for dgemm_ - found
  -- Found BLAS: /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Accelerate.framework
  -- Looking for cheev_
  -- Looking for cheev_ - found
  -- Found LAPACK: /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Accelerate.framework;-lm;-ldl
  -- LAPACK(LAPACK/Apple): LAPACK_LIBRARIES: /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/Accelerate.framework;-lm;-ldl
  -- Looking for Accelerate/Accelerate.h
  -- Looking for Accelerate/Accelerate.h - found
  -- Looking for Accelerate/Accelerate.h
  -- Looking for Accelerate/Accelerate.h - found
  -- LAPACK(LAPACK/Apple): Support is enabled.
  -- Performing Test HAVE_CXX_WNO_UNUSED_LOCAL_TYPEDEFS
  -- Performing Test HAVE_CXX_WNO_UNUSED_LOCAL_TYPEDEFS - Success
  -- Performing Test HAVE_CXX_WNO_SIGN_PROMO
  -- Performing Test HAVE_CXX_WNO_SIGN_PROMO - Success
  -- Performing Test HAVE_CXX_WNO_TAUTOLOGICAL_UNDEFINED_COMPARE
  -- Performing Test HAVE_CXX_WNO_TAUTOLOGICAL_UNDEFINED_COMPARE - Success
  -- Performing Test HAVE_CXX_WNO_IGNORED_QUALIFIERS
  -- Performing Test HAVE_CXX_WNO_IGNORED_QUALIFIERS - Success
  -- Performing Test HAVE_CXX_WNO_UNUSED_FUNCTION
  -- Performing Test HAVE_CXX_WNO_UNUSED_FUNCTION - Success
  -- Performing Test HAVE_CXX_WNO_UNUSED_CONST_VARIABLE
  -- Performing Test HAVE_CXX_WNO_UNUSED_CONST_VARIABLE - Success
  -- Performing Test HAVE_CXX_WNO_SHORTEN_64_TO_32
  -- Performing Test HAVE_CXX_WNO_SHORTEN_64_TO_32 - Success
  -- Performing Test HAVE_CXX_WNO_INVALID_OFFSETOF
  -- Performing Test HAVE_CXX_WNO_INVALID_OFFSETOF - Success
  -- Performing Test HAVE_CXX_WNO_ENUM_COMPARE_SWITCH
  -- Performing Test HAVE_CXX_WNO_ENUM_COMPARE_SWITCH - Success
  -- Found JNI: /Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks/JavaVM.framework/Headers  found components: AWT JVM
  -- VTK is not found. Please set -DVTK_DIR in CMake to VTK build directory, or to VTK install subdirectory with VTKConfig.cmake file
  -- Looking for dlerror in dl
  -- Looking for dlerror in dl - found
  -- ADE: Downloading v0.1.1f.zip from https://github.com/opencv/ade/archive/v0.1.1f.zip
  -- Module opencv_alphamat disabled because the following dependencies are not found: Eigen
  -- freetype2:   NO
  -- harfbuzz:    NO
  -- HDF5 C compiler wrapper is unable to compile a minimal HDF5 program.
  -- Could NOT find HDF5 (missing: HDF5_LIBRARIES HDF5_INCLUDE_DIRS) (found version "")
  -- Julia not found. Not compiling Julia Bindings.
  -- Module opencv_ovis disabled because OGRE3D was not found
  -- No preference for use of exported gflags CMake configuration set, and no hints for include/library directories provided. Defaulting to preferring an installed/exported gflags CMake configuration if available.
  -- Failed to find installed gflags CMake configuration, searching for gflags build directories exported with CMake.
  -- Failed to find gflags - Failed to find an installed/exported CMake configuration for gflags, will perform search for installed gflags components.
  -- Failed to find gflags - Could not find gflags include directory, set GFLAGS_INCLUDE_DIR to directory containing gflags/gflags.h
  -- Failed to find glog - Could not find glog include directory, set GLOG_INCLUDE_DIR to directory containing glog/logging.h
  -- Module opencv_sfm disabled because the following dependencies are not found: Eigen Glog/Gflags
  -- Tesseract:   NO
  -- Allocator metrics storage type: 'long long'
  -- Registering hook 'INIT_MODULE_SOURCES_opencv_dnn': /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv/modules/dnn/cmake/hooks/INIT_MODULE_SOURCES_opencv_dnn.cmake
  -- opencv_dnn: filter out ocl4dnn source code
  -- opencv_dnn: filter out cuda4dnn source code
  -- Excluding from source files list: <BUILD>/modules/dnn/layers/layers_common.rvv.cpp
  -- imgcodecs: OpenEXR codec is disabled in runtime. Details: https://github.com/opencv/opencv/issues/21326
  -- Performing Test HAVE_CXX_FOBJC_EXCEPTIONS
  -- Performing Test HAVE_CXX_FOBJC_EXCEPTIONS - Success
  -- Performing Test HAVE_CXX_WNO_OVERLOADED_VIRTUAL
  -- Performing Test HAVE_CXX_WNO_OVERLOADED_VIRTUAL - Success
  -- Performing Test Iconv_IS_BUILT_IN
  -- Performing Test Iconv_IS_BUILT_IN - Failed
  -- wechat_qrcode: Downloading detect.caffemodel from https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/detect.caffemodel
  -- wechat_qrcode: Downloading detect.prototxt from https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/detect.prototxt
  -- wechat_qrcode: Downloading sr.caffemodel from https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/sr.caffemodel
  -- wechat_qrcode: Downloading sr.prototxt from https://raw.githubusercontent.com/WeChatCV/opencv_3rdparty/a8b69ccc738421293254aec5ddb38bd523503252/sr.prototxt
  -- highgui: using builtin backend: COCOA
  -- rgbd: Eigen support is disabled. Eigen is Required for Posegraph optimization
  -- xfeatures2d/boostdesc: Downloading boostdesc_bgm.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/34e4206aef44d50e6bbcd0ab06354b52e7466d26/boostdesc_bgm.i
  -- xfeatures2d/boostdesc: Downloading boostdesc_bgm_bi.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/34e4206aef44d50e6bbcd0ab06354b52e7466d26/boostdesc_bgm_bi.i
  -- xfeatures2d/boostdesc: Downloading boostdesc_bgm_hd.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/34e4206aef44d50e6bbcd0ab06354b52e7466d26/boostdesc_bgm_hd.i
  -- xfeatures2d/boostdesc: Downloading boostdesc_binboost_064.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/34e4206aef44d50e6bbcd0ab06354b52e7466d26/boostdesc_binboost_064.i
  -- xfeatures2d/boostdesc: Downloading boostdesc_binboost_128.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/34e4206aef44d50e6bbcd0ab06354b52e7466d26/boostdesc_binboost_128.i
  -- xfeatures2d/boostdesc: Downloading boostdesc_binboost_256.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/34e4206aef44d50e6bbcd0ab06354b52e7466d26/boostdesc_binboost_256.i
  -- xfeatures2d/boostdesc: Downloading boostdesc_lbgm.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/34e4206aef44d50e6bbcd0ab06354b52e7466d26/boostdesc_lbgm.i
  -- xfeatures2d/vgg: Downloading vgg_generated_48.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/fccf7cd6a4b12079f73bbfb21745f9babcd4eb1d/vgg_generated_48.i
  -- xfeatures2d/vgg: Downloading vgg_generated_64.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/fccf7cd6a4b12079f73bbfb21745f9babcd4eb1d/vgg_generated_64.i
  -- xfeatures2d/vgg: Downloading vgg_generated_80.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/fccf7cd6a4b12079f73bbfb21745f9babcd4eb1d/vgg_generated_80.i
  -- xfeatures2d/vgg: Downloading vgg_generated_120.i from https://raw.githubusercontent.com/opencv/opencv_3rdparty/fccf7cd6a4b12079f73bbfb21745f9babcd4eb1d/vgg_generated_120.i
  -- data: Downloading face_landmark_model.dat from https://raw.githubusercontent.com/opencv/opencv_3rdparty/8afa57abc8229d611c4937165d20e2a2d9fc5a12/face_landmark_model.dat
  -- Found 'misc' Python modules from /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv/modules/python/package/extra_modules
  -- Found 'mat_wrapper;utils' Python modules from /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv/modules/core/misc/python/package
  -- Found 'gapi' Python modules from /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv/modules/gapi/misc/python/package
  -- Performing Test HAVE_CXX_WNO_UNUSED_PRIVATE_FIELD
  -- Performing Test HAVE_CXX_WNO_UNUSED_PRIVATE_FIELD - Success
  -- Found 'misc' Python modules from /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv/modules/python/package/extra_modules
  -- Found 'mat_wrapper;utils' Python modules from /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv/modules/core/misc/python/package
  -- Found 'gapi' Python modules from /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv/modules/gapi/misc/python/package
  --
  -- General configuration for OpenCV 4.6.0 =====================================
  --   Version control:               unknown
  --
  --   Extra modules:
  --     Location (extra):            /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/opencv_contrib/modules
  --     Version control (extra):     unknown
  --
  --   Platform:
  --     Timestamp:                   2022-10-05T18:05:10Z
  --     Host:                        Darwin 18.7.0 x86_64
  --     CMake:                       3.24.1
  --     CMake generator:             Unix Makefiles
  --     CMake build tool:            /usr/bin/make
  --     Configuration:               Release
  --
  --   CPU/HW features:
  --     Baseline:                    SSE SSE2 SSE3 SSSE3 SSE4_1
  --       requested:                 DETECT
  --     Dispatched code generation:  SSE4_2 FP16 AVX AVX2 AVX512_SKX
  --       requested:                 SSE4_1 SSE4_2 AVX FP16 AVX2 AVX512_SKX
  --       SSE4_2 (1 files):          + POPCNT SSE4_2
  --       FP16 (0 files):            + POPCNT SSE4_2 FP16 AVX
  --       AVX (4 files):             + POPCNT SSE4_2 AVX
  --       AVX2 (31 files):           + POPCNT SSE4_2 FP16 FMA3 AVX AVX2
  --       AVX512_SKX (5 files):      + POPCNT SSE4_2 FP16 FMA3 AVX AVX2 AVX_512F AVX512_COMMON AVX512_SKX
  --
  --   C/C++:
  --     Built as dynamic libs?:
    Command:
      cmake --build . --target install --config Release --
    Install target:
      install
    Source directory:
      /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f
    Working directory:
      /private/var/folders/5d/bt1pynjj6g70s2jxxv7bw9nw0000gn/T/pip-install-qp7tckpn/opencv-contrib-python_ef51384960074dd2aa9142b293afa58f/_skbuild/macosx-10.14-x86_64-3.7/cmake-build
  Please check the install target is valid and see CMake's output for more information.
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for opencv-contrib-python
Failed to build opencv-contrib-python
ERROR: Could not build wheels for opencv-contrib-python, which is required to install pyproject.toml-based projects
This happened on MacOS Mojave 10.14.6

some problem

Same here on raspberry pi. I tried with earlier versions until I got it installed.
opencv-contrib-python==<IP_ADDRESS>
worked for me.

It might have to do with Mojave messing with cMake

None of the solutions work for opencv-python 4.5 in Mac OS El Capitan (10.11.6).... I'm stuck with this OS

Same here on raspberry pi. I tried with earlier versions until I got it installed.
opencv-contrib-python==<IP_ADDRESS>
worked for me.

Comment from molcik:
pip3 install opencv-contrib-python==<IP_ADDRESS>
Also works for me

Hello everyone, I work on Mac OSX.At the moment I am trying to install OpenCV on my Mac OS 10.14.The installation process was successful, up to the lines "Building wheels for collected packages: opencv-python
Building wheel for opencv-python (pyproject.toml) ... -
"After this moment installation not continues.What do?

Save problem with @Bonitodelcapo on Mac Mojave OS, still haven't figure out a solution. Have you solve the problem?
For @Alexandro1112 , a thing that might help is to install using pip -v command, which will log out the current step in building wheels so that you can know the specific problem you are stuck with.

The only thing i could do was to upgrade to another OS version
Il giorno lun 26 dic 2022 alle ore 13:24 Thomaswbt @.***>
ha scritto:

Save problem with @Bonitodelcapo https://github.com/Bonitodelcapo on
Mac Mojave OS, still haven't figure out a solution. Have you solve the
problem?
For @Alexandro1112 https://github.com/Alexandro1112 , a thing that
might help is to install using pip -v command, which will log out the
current step in building wheels so that you can know the specific problem
you are stuck with.
—
Reply to this email directly, view it on GitHub
https://github.com/opencv/opencv-python/issues/657#issuecomment-1365136337,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APO7Y5E7IYIDVV76HSOZEV3WPGFA7ANCNFSM5UGUHXGQ
.

This thread has been very helpful for me, I finally got it properly downloaded after many hours of trying. Theres a few steps I tried that weren't mentioned here but I'll go through my exact steps:
First of all 10.15.7 OS is a must I believe, otherwise this is likely different.
Then download a version of python that works, in my case 3.8 seems like a solid fit. Grab the following (may vary slightly):
python3 -m pip install numpy
python3 -m pip install --upgrade pip setuptools wheel
Secondly (and I haven't seen mentioned yet) you need xCode on mac. It mentions this sometimes when it fails. Sign up as a developer (  https://developer.apple.com/download/all/?q=xcode ) and download a version that works for you (not very hard just need an email). In my case it was 12.4. Then in your mac terminal run "sudo xcodebuild -license" to get it fully setup to use.
Lastly, start the download. For me it took about an hour of shear terror waiting. But ran successfully in the end. Good luck!
python3 -m pip install opencv-contrib-python

@2Arms2Legs  I tried to install via xcode on my macos 13.1, the installation was not supported on my device, and after a long wait it gave me an error. I prefer installing opencv via pip, with command , which i wrote above.

python版本和opencv版本不兼容，请参考https://pypi.tuna.tsinghua.edu.cn/simple/opencv-python/
使用<IP_ADDRESS> opencv版本。
执行命令  pip3 install opencv-python==<IP_ADDRESS>  -i https://pypi.tuna.tsinghua.edu.cn/simple
log如下：
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
Collecting opencv-python==<IP_ADDRESS>
Downloading https://pypi.tuna.tsinghua.edu.cn/packages/af/bf/8d189a5c43460f6b5c8eb81ead8732e94b9f73ef8d9abba9e8f5a61a6531/opencv_python-<IP_ADDRESS>-cp36-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (60.9 MB)
|████████████████████████████████| 60.9 MB 804 kB/s
Requirement already satisfied: numpy>=1.13.3 in /home/edward.zhang/miniconda3/envs/pytorch_pd/lib/python3.6/site-packages (from opencv-python==<IP_ADDRESS>) (1.16.0)
Installing collected packages: opencv-python
Successfully installed opencv-python-<IP_ADDRESS>

infra/python/wheels/requests
<EMAIL_ADDRESS>

command pip3 install opencv-python==<IP_ADDRESS> do actually work! It only cost me few seconds.


Update leetcode night #396

What issue is this referencing?
This pr fixes #396

Do these code changes work locally and have you tested that they fix the issue yourself?

[x] yes!

Does the following command run without warnings or errors?

[x] yes! npm run pr-checks

Have you taken a look at our contributing guidelines?

[x] yes!

My node version matches the one suggested when running nvm use?

[x] yes!

great job @LUCKYINGGG

@allcontributors add @LUCKYINGGG for code


merge from arlac77/template-kronos-module

package.json

chore(package): add arlac77/template-kronos-module (template.inheritFrom)

:tada: This PR is included in version 10.0.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


All development builds gone?

Lastly, i checked for New development builds but almost all builds were one thing called  gone! Fix? Explanation?
-Jamie

The old CI ran out of disk space. (probably because I was storing 200+ old builds.)
I had to move it to a new server, and configure it to only keep the most recent successful build.


Add PandA hdf writer

Adds an HDF writer for the PandA.

Upon initialisation, writer looks at the signals inside the PandA device to see what might be selected for capture.

Upon calling open, which should be triggered by arming the PCAP block, the writer reads from all the capture signals to find which of these were actually marked for capture. It creates datasets based off these

Functionality should be all here now, but I need to address all my TODO comments

@jwlodek This isn't ready to try out on a real panda just yet, but should be in the next few days

I will add some more tests, but other than that I think this is ready. I can make another issue for future improvements:

There is a lot of code which is common between AreaDetector's hdf_writer and this new hdf_writer. Would be nice to put it somewhere common
Use information from the capture table when writing the descriptor (https://github.com/bluesky/ophyd-async/pull/141#discussion_r1521775460)
The HdfSignal class can be removed after https://github.com/PandABlocks/PandABlocks-ioc/issues/101 is fixed
DataBlock in panda.py can be changed to handle Enums properly once https://github.com/bluesky/ophyd-async/pull/152 is merged

I'm currently blocked by this, I'm going to take the liberty of squashing it so I can easily merge with my own branch.

Replced with https://github.com/bluesky/ophyd-async/pull/198


Some funkiness with dates when generateOutDates = .tillEndOfRow and hasStrictBoundaries = true (v 7.0.1)

Sorry to pile on! Another couple of things...
I noticed a couple of issues in version 7.0.1 with incorrect dates when generateOutDates = .tillEndOfRow:

The calendar can duplicate some rows. (E.g. "April 1" appears multiple times.)
The calendar can misalign the dates in the wrong columns. (E.g. "April 1" appears in the Sunday column, when it's actually Saturday.)

Here's a sample project which shows these two issues. Calendar is configured with startDate = May 1, 2016 and endDate = April 30, 2017 (a 1-year span). Everything looks okay when generateOutDates = .off, but not so okay when generateOutDates = .tillEndOfRow.

Also note when you change hasStrictBoundaries to true, even when generateOutDates = .off, the dates are misaligned - April 1, 2017 ends up as a Sunday, rather than a Saturday.

Thanks!. Add all the found issues in here.
I'll check em out after work

Ok i just took a look at it. This does not look like a bug.
I can explain this more to you when youre awake.
I think i'll do a video on this

issue explained. All is well.
Closing this issue.
I will add the enhance we spoke about.
cheers 🍻

Much appreciated for the chat today! For anyone looking at this thread in the future, basically, don't configure the calendar like this. :P If you need an infinite scroll of dates flowing into each other, set generateOutDates = .off. @patchthecode will consider an enhancement which lets you get out dates for the very last week of the calendar for visual consistency.

@UberJason added new feature request issue. -> https://github.com/patchthecode/JTAppleCalendar/issues/380
I'll work on this when i'm free again

@UberJason had one last question, was the reloading dates problem still happening?

Yes, I believe so. I'm working around it for now.

@UberJason alright then, i'll have a look

I have added your comment:

also just leaving this here for you for later...
I stepped through some of the code and see the problem (but not sure the best way to fix, so I'll just alert you to it).
In short, reloadData() is calling selectDates() only after its completion handler gets run.
my usage is this:

calendarView.reloadData() {
    if self.calendarView.selectedDates.count > 0 {
        // do stuff with the selected dates }
}

(couldn't get that formatted right but you get the idea -
I check the selectedDates in the reloadData() completion handler.)
I see under the hood that reloadData() calls selectDates(_:,triggerSelectionDelegate:,keepSelectionIfMultiSelectionAllowed:) and then the completionHandler.
The selectDates(...) function checks if functionIsUnsafeToRun, and if so, it adds itself to the end of the delayed execution queue.

Then the completionHandler runs. Then selectDates(...) is run again, and this time it's safe to run, so it does update the dates.
So in short, the calendar does EVENTUALLY restore selected dates, but not until after the completion handler, which is when my usage requires it.
I'm assuming that I'm not doing some unintended stuff - that the selected dates should be available by the time the completionHandler has run.

the part that i got lost on was this

Then selectDates(...) is run again
You meant to say selectedDates right?
And then you said run again. So my question is -> is this reload code done in the viewDidLoad() function?

No - I'm talking all about code internal to your calendar view. I did not mean selectedDates, I meant selectDates(...) is run again - by that I mean, selectDates(...) adds itself to the end of the delayed execution queue if functionIsUnsafeToRun, which means that after it finishes, it gets called again (it's basically recursion). Does that help?

@UberJason ok i understand. But can you tell me if you reloadData is called in your viewDidLoad?
or maybe you can tell me where in you code you call the reloadData function

I'm calling reloadData on a button press from the user. For us it's a button that toggles the size of the calendar from 2 to 6 rows (with a corresponding increase in the calendar's height to match). On button press, I animate the calendar to alpha = 0, then animate the calendar height increase, then reloadData, and in the completion handler of reloadData, animate the calendar to alpha = 1.0.

Thanks you. will look into this.

@UberJason when ever you get the chance, i wish you can upload a small zipped copy of the issue (with all your secret code removed). I am not able to reproduce it from my end. And I am not good at animation code, so i do not really know how to reproduce it :<

Cool. I'll try to get around to it on Monday - it was code in a work project. It's not a big deal in any case, since the dates do eventually get re-selected and I can just save the date locally before reloading the calendar!

@UberJason it may not be a big deal to you but.. i got many people using this. Dont stress too much, but if its possible, then i'd be grateful :]

Hey man, I've updated my old CalendarBug project to show the problem with selected dates. See the project here: https://github.com/UberJason/CalendarBug
Note the print statements, initially in viewDidAppear I show the calendarView.selectedDates array correctly contains one selected date. Then when you tap "Toggle" to do the calendar animation, in the completion handler of reloadData, you see the selectedDates array is empty. Then after a short while (I chose 1 second but it is probably shorter), the selectedDates array is correctly populated again.

@UberJason thanks! looking into it

Here is the updated code. I hope i didnt break anything.
Still testing.
CalendarBug-master.zip
Library Changes:

reloadData(with anchorDate) has been removed.
Reason: anchorDate was redundant as you can simply do the following plus much more.
calendarView.reloadData {[weak self]
     self.calendarView.scrollToDate(myDate)
}

Oh yeah, I actually only threw anchorDate in there at one point while I was playing with it, and forgot to remove. I'm not doing anything with it myself either.

I had numberOfRows as 1 and I was facing the issue of repeated weeks but after doing the setting as per mentioned by @UberJason i.e.
 let startDate = Date().addInDate(type: .month, add: -12) ?? Date() let endDate = Date().addInDate(type: .month, add: 12) ?? Date() ConfigurationParameters(startDate: startDate,                                        endDate: endDate,                                        numberOfRows: 1,                                        calendar: DateHelper.calendar,                                        generateInDates: .forFirstMonthOnly,                                        generateOutDates: .off,                                        firstDayOfWeek: AppSettings.defaultWeekStartDay == .Monday ? .monday : .sunday,                                        hasStrictBoundaries: false)
I was able to resolve the issue