Task :app:checkDebugAarMetadata FAILED

Description
i get a mistake when i run 'yarn android'
Task :app:checkDebugAarMetadata FAILED

Task :expo-constants:createDebugExpoConfig
Execution optimizations have been disabled for task ':expo-constants:createDebugExpoConfig' to ensure correctness due to the following reasons:

Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:checkDebugAarMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:compileDebugAidl' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:compileDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:generateDebugBuildConfig' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:javaPreCompileDebug' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:mergeDebugNativeDebugMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:mergeDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:checkDebugAarMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:compileDebugAidl' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:compileDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:generateDebugBuildConfig' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:javaPreCompileDebug' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:mergeDebugNativeDebugMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.
Gradle detected a problem with the following location: '/Users/yujunmiao/Documents/new-century-work/taro-3.6.30/android'. Reason: Task ':expo-constants:createDebugExpoConfig' uses this output of task ':app:mergeDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.5.1/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

FAILURE: Build completed with 2 failures.
1: Task failed with an exception.

What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.

A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
9 issues were found when checking AAR metadata:

   1.  Dependency 'androidx.appcompat:appcompat-resources:1.6.1' requires libraries and applications that
       depend on it to compile against version 33 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.2.1 is 32.

       Recommended action: Update this project's version of the Android Gradle
       plugin to one that supports 33, then update this project to use
       compileSdkVerion of at least 33.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   2.  Dependency 'androidx.appcompat:appcompat:1.6.1' requires libraries and applications that
       depend on it to compile against version 33 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.2.1 is 32.

       Recommended action: Update this project's version of the Android Gradle
       plugin to one that supports 33, then update this project to use
       compileSdkVerion of at least 33.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   3.  Dependency 'androidx.activity:activity-ktx:1.6.0' requires libraries and applications that
       depend on it to compile against version 33 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.2.1 is 32.

       Recommended action: Update this project's version of the Android Gradle
       plugin to one that supports 33, then update this project to use
       compileSdkVerion of at least 33.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   4.  Dependency 'androidx.activity:activity:1.6.0' requires libraries and applications that
       depend on it to compile against version 33 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.2.1 is 32.

       Recommended action: Update this project's version of the Android Gradle
       plugin to one that supports 33, then update this project to use
       compileSdkVerion of at least 33.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   5.  Dependency 'androidx.emoji2:emoji2-views-helper:1.2.0' requires libraries and applications that
       depend on it to compile against version 32 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Recommended action: Update this project to use a newer compileSdkVersion
       of at least 32, for example 32.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   6.  Dependency 'androidx.emoji2:emoji2:1.2.0' requires libraries and applications that
       depend on it to compile against version 32 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Recommended action: Update this project to use a newer compileSdkVersion
       of at least 32, for example 32.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   7.  Dependency 'androidx.core:core-ktx:1.9.0' requires libraries and applications that
       depend on it to compile against version 33 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.2.1 is 32.

       Recommended action: Update this project's version of the Android Gradle
       plugin to one that supports 33, then update this project to use
       compileSdkVerion of at least 33.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   8.  Dependency 'androidx.core:core:1.9.0' requires libraries and applications that
       depend on it to compile against version 33 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.2.1 is 32.

       Recommended action: Update this project's version of the Android Gradle
       plugin to one that supports 33, then update this project to use
       compileSdkVerion of at least 33.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

   9.  Dependency 'androidx.annotation:annotation-experimental:1.3.0' requires libraries and applications that
       depend on it to compile against version 33 or later of the
       Android APIs.

       :app is currently compiled against android-31.

       Also, the maximum recommended compile SDK version for Android Gradle
       plugin 7.2.1 is 32.

       Recommended action: Update this project's version of the Android Gradle
       plugin to one that supports 33, then update this project to use
       compileSdkVerion of at least 33.

       Note that updating a library or application's compileSdkVersion (which
       allows newer APIs to be used) can be done separately from updating
       targetSdkVersion (which opts the app in to new runtime behavior) and
       minSdkVersion (which determines which devices the app can be installed
       on).

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.

What went wrong:
java.lang.StackOverflowError (no error message)

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

Get more help at https://help.gradle.org

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
BUILD FAILED in 21s
64 actionable tasks: 6 executed, 58 up-to-date
Steps to reproduce
yarn add<EMAIL_ADDRESS>yarn android
env:
Android 31
gradle:7.2.1
Snack or a link to a repository
no url
Lottie React Native version
6.5.0
React Native version
0.70.0
Platforms
Android
Workflow
React Native
Architecture
Paper (Old Architecture)
Build type
None
Device
None
Acknowledgements
Yes

Closing this issue due to an invalid reproduction link. To resolve the issue, please try clearing your local gradle cache.
As shown in the CI build status below, the builds are passing successfully, indicating that the issue may be related to your local setup:

Android Fabric Build Status
Android Paper Build Status

If the issue persists after troubleshooting, feel free to reopen the issue with additional details. Thank you!


Bounding box searching in Explore allows invalid geocoordinates

Sorry to drop this on you guys but basically a bug that was not around pre-deployment, pre-integration as I know this was working at one point. It basically prevents a user from panning and seeing results and from sharing urls: (also same behaviour on stamen gtihub instance and prod)
Eg. scroll WEST and search bb on Philippines= invalid results
https://dev-holos.berkeley.edu/explore/#&q=&bbox=-259.365234375,-0.13183582116660822,-212.51953124999997,20.50935458871459&page_size=100
Scroll EAST and search bb on Philippines= ok
https://dev-holos.berkeley.edu/explore/#&q=&bbox=99.36035156249999,3.908098881894123,146.2060546875,24.246964554300924&page_size=100
pls. coordinate with @shoeswat who will help and deploy any fixes on the prod version on holos.berkeley.edu

Can you pls repost on bee so that Brian Galey can look at it? Thanks
On Fri, Jun 5, 2015 at 2:27 PM, Michelle Koo<EMAIL_ADDRESS>wrote:

Sorry to drop this on you guys but basically a bug that was not around
pre-deployment, pre-integration as I know this was working at one point. It
basically prevents a user from panning and seeing results and from sharing
urls: (also same behaviour on stamen gtihub instance and prod)
Eg. scroll WEST and search bb on Philippines= invalid results
https://dev-holos.berkeley.edu/explore/#&q=&bbox=-259.365234375,-0.13183582116660822,-212.51953124999997,20.50935458871459&page_size=100
Scroll EAST and search bb on Philippines= ok
https://dev-holos.berkeley.edu/explore/#&q=&bbox=99.36035156249999,3.908098881894123,146.2060546875,24.246964554300924&page_size=100
pls. coordinate with @shoeswat https://github.com/shoeswat who will
help and deploy any fixes on the prod version on holos.berkeley.edu
—
Reply to this email directly or view it on GitHub
https://github.com/stamen/ecoengine/issues/162.

--
Falk Schuetzenmeister, PhD
Web Application Developer
Geospatial Innovation Facility http://gif.berkeley.edu/
University of California Berkeley
111 Mulford Hall
94720 Berkeley, CA
<EMAIL_ADDRESS>1-510-642-4897

yep!
but this is shared through the instances so fixes anywhere should be shared.

I think the problem is actually specific to slippy map viewers and should indeed be fixed in the ecoengine app by Stamen. @shoeswat Just calculate the valid longitude value with the formel
valid_longitude = ((out_of_range_longitude+180) modulo 360) - 180
prior the AJAX request and it should work

So this is an issue around the dateline, right?
Looks like the search by bbox is determined here:
https://github.com/stamen/ecoengine/blob/master/viewJS/ecoengine-explore.js#L1015-L1022

okay i'll play around with modulo-ing the params dan pointed out -- thanks!
On Fri, Jun 5, 2015 at 3:59 PM, Dan Rademacher<EMAIL_ADDRESS>wrote:

So this is an issue around the dateline, right?
Looks like the search by bbox is determined here:
https://github.com/stamen/ecoengine/blob/master/viewJS/ecoengine-explore.js#L1015-L1022
—
Reply to this email directly or view it on GitHub
https://github.com/stamen/ecoengine/issues/162#issuecomment-109472055.

query() (L1021) submits the query to the API, the API is returning records
though properly (if you look at the bottom and sides, records are
populated), its just not displaying points on the map
how are the points being rendered on the map?
On Fri, Jun 5, 2015 at 4:03 PM, Yugarshi Mondal<EMAIL_ADDRESS>wrote:

okay i'll play around with modulo-ing the params dan pointed out -- thanks!
On Fri, Jun 5, 2015 at 3:59 PM, Dan Rademacher<EMAIL_ADDRESS>wrote:

So this is an issue around the dateline, right?
Looks like the search by bbox is determined here:
https://github.com/stamen/ecoengine/blob/master/viewJS/ecoengine-explore.js#L1015-L1022
—
Reply to this email directly or view it on GitHub
https://github.com/stamen/ecoengine/issues/162#issuecomment-109472055.

oic is this addMarkers() (L500)?
On Fri, Jun 5, 2015 at 4:06 PM, Yugarshi Mondal<EMAIL_ADDRESS>wrote:

query() (L1021) submits the query to the API, the API is returning records
though properly (if you look at the bottom and sides, records are
populated), its just not displaying points on the map
how are the points being rendered on the map?
On Fri, Jun 5, 2015 at 4:03 PM, Yugarshi Mondal<EMAIL_ADDRESS>
wrote:

okay i'll play around with modulo-ing the params dan pointed out --
thanks!
On Fri, Jun 5, 2015 at 3:59 PM, Dan Rademacher<EMAIL_ADDRESS>wrote:

So this is an issue around the dateline, right?
Looks like the search by bbox is determined here:
https://github.com/stamen/ecoengine/blob/master/viewJS/ecoengine-explore.js#L1015-L1022
—
Reply to this email directly or view it on GitHub
https://github.com/stamen/ecoengine/issues/162#issuecomment-109472055.

@shoeswat , it looks like Markers don't automatically repeat themselves with tiled world copies without some configuration.
One option appears to be enabling worldCopyJump
http://stackoverflow.com/questions/28977891/leaflet-mapbox-markers-dont-repeat-after-scrolling-around-the-atlas
Another option could be disabling the tiled world copies by constraining panning to a single world with boundaries.
http://leafletjs.com/reference.html#tilelayer-nowrap

@syntagmatic thanks!
I specified worldCopyJump in the L.map instance and it appears to have worked.

Tested out the Explore links you sent. It works. Nice work Yoshi!

So great to have this fixed! Now can search and map data globally again...
Please let me know when pushed to production.
Stamen: will you update your versions too since it is fundamental to using
the tools? (just curious for future reference)
On Wed, Jun 10, 2015 at 2:58 PM, Kai<EMAIL_ADDRESS>wrote:

Tested out the Explore links you sent. It works. Nice work Yoshi!
—
Reply to this email directly or view it on GitHub
https://github.com/stamen/ecoengine/issues/162#issuecomment-110928813.

@mkoo just pushed the fix!


Some question about iou and beta

Hello! I am interested in your paper. Dynamic RCNN obtains iou and beta according to the current detection results. Have you directly set iou and beta to the values calculated by dynamic rcnn, such as 0.6 and 0.2, for training?

No, but we have tried some values towards the observed trend.
As shown in Table 5, we try some common values of beta (e.g. 0.5-2.0) and find that a smaller value is better than the default one. I also remember directly using L1 Loss instead of SmoothL1 Loss is helpful, but not as good as our DSL. I believe that raising the IoU threshold will draw a similar conclusion.
In fact, as analyzed in the paper, we do not think that directly setting a fixed threshold or hyperparameter is the optimal solution. We hope our work can inspire further researchers to rethink the framework in a dynamic way.

No, but we have tried some values towards the observed trend.
As shown in Table 5, we try some common values of beta (e.g. 0.5-2.0) and find that a smaller value is better than the default one. I also remember directly using L1 Loss instead of SmoothL1 Loss is helpful, but not as good as our DSL. I believe that raising the IoU threshold will draw a similar conclusion.
In fact, as analyzed in the paper, we do not think that directly setting a fixed threshold or hyperparameter is the optimal solution. We hope our work can inspire further researchers to rethink the framework in a dynamic way.

Thank you for your reply! I used dynamic rcnn in the custom data set, but it didn't work. Iou approaches 0.6 after 5 epochs, and beta approaches 0.2 after 2 epochs. It is worth noting that 60% of the object scale in this data set is smaller than 32×32 pixels. Can you give me some suggestions?

The reason is not clear according to your description, but I have some guesses.

As for the object scale part, it seems like the default anchor setting is not reasonable for your custom dataset. You can change the anchor scales and ratios, then calculate the recall of current GTs to decide whether the anchor setting is ok.
As for the Dynamic R-CNN part, our design mainly focus on high quality object detection, so if you use low quality evaluation metrics (like AP50 only), our default hyperparameters may not be helpful.

Thanks for your suggestion.


made compatible with node 0.12

Fixes #3
I'd be happy to see this integrated into a branch like support-node-0.12 and published as a version with that same name. ie not in the main branch but just available to us and people like me

Should be already compatible. Tested against node v0.12.13


Hubble: add possibility to export flows to container logs

This is a modification of the static exporter for flow logs which allows setting the hubble-export-file-path to stdout. This triggers not the creation of rotating files but the direct output to logs.
The benefit is the possibility to ship flow logs to a SIEM for continuous analysis without the deployment of a separate daemonset like used here: https://github.com/cilium/hubble-otel
I am happy for any suggestions.

/test

lgtm 🚀
* could you squash these 2 commits into 1 commit?

* curious how it shows up in kubectl logs. could you post a sample output?

Thanks!
The commits are merged now.
This is how one flow shows up in the log now:
level=info msg="{\"flow\":{\"time\":\"2024-03-15T22:23:36.124398461Z\",\"uuid\":\"a4100bd7-9732-442e-bbc8-beb5c7212f44\",\"verdict\":\"FORWARDED\",\"ethernet\":{\"source\":\"72:c0:06:45:0a:22\",\"destination\":\"76:a3:43:b7:98:5c\"},\"IP\":{\"source\":\"<IP_ADDRESS>\",\"destination\":\"<IP_ADDRESS>\",\"ipVersion\":\"IPv4\"},\"l4\":{\"TCP\":{\"source_port\":4222,\"destination_port\":33564,\"flags\":{\"FIN\":true,\"ACK\":true}}},\"source\":{\"ID\":2864,\"identity\":2542,\"namespace\":\"kube-system\",\"labels\":[\"k8s:app.kubernetes.io/name=hubble-relay\",\"k8s:app.kubernetes.io/part-of=cilium\",\"k8s:io.cilium.k8s.namespace.labels.kubernetes.io/metadata.name=kube-system\",\"k8s:io.cilium.k8s.policy.cluster=kind-kind\",\"k8s:io.cilium.k8s.policy.serviceaccount=hubble-relay\",\"k8s:io.kubernetes.pod.namespace=kube-system\",\"k8s:k8s-app=hubble-relay\"],\"pod_name\":\"hubble-relay-76cbb4895d-hd99d\",\"workloads\":[{\"name\":\"hubble-relay\",\"kind\":\"Deployment\"}]},\"destination\":{\"identity\":1,\"labels\":[\"reserved:host\"]},\"Type\":\"L3_L4\",\"node_name\":\"kind-kind/kind-worker\",\"reply\":true,\"event_type\":{\"type\":4,\"sub_type\":3},\"traffic_direction\":\"INGRESS\",\"trace_observation_point\":\"TO_STACK\",\"is_reply\":true,\"Summary\":\"TCP Flags: ACK, FIN\"},\"node_name\":\"kind-kind/kind-worker\",\"time\":\"2024-03-15T22:23:36.124398461Z\"}" subsys=hubble

/test

looks like https://github.com/cilium/cilium/actions/runs/8302891162/job/22726503509?pr=31422 is complaining about commit message format. there should an extra blank line between the title and body:
Add possibility to export flow logs to stdout

Signed-off-by: siegmund-heiss-ich<EMAIL_ADDRESS>

/test

/test

looks like https://github.com/cilium/cilium/actions/runs/8302891162/job/22726503509?pr=31422 is complaining about commit message format. there should an extra blank line between the title and body:
Add possibility to export flow logs to stdout

Signed-off-by: siegmund-heiss-ich<EMAIL_ADDRESS>

Sorry, I didn't see this message before...
Should be fixed now.

/test

/test

/test

I am sorry for the last change... Didn't recognize at first that the format wasn't valid json anymore.
This now is the last change, unless someone has new suggestions.

/test

Please run make -C Documentation update-cmdref locally and add the changes to your commit, to update the command reference with the updated description for hubble-export-file-path.

/test

According to @glibsm 's change request, the Hubble flows are now directly written to stdout instead of using logrus, because of performance concerns.
In addition, there are no more escaped characters in the output string, which makes it easier to use.
The drawback with this solution is, that there are no additional fields anymore, which shouldn't impose any problems.

Requesting changes to halt the PR for a little bit so it's not merged accidentally.

@glibsm
Is there any news? You've been blocking this PR for over a month now without any further feedback.

Check patch is failing: https://github.com/cilium/cilium/actions/runs/8388580874/job/23305658705?pr=31422

Error: ERROR:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'siegmund-heiss-ich<EMAIL_ADDRESS>
Looks like something is off about your commit/sign-off.

/test


Add youtrack svg

Based on Wikipedia version.
I added a vendor prefix, because there have more on premise software like space, teamcity...
https://commons.wikimedia.org/wiki/File:YouTrack_Icon.svg

Ideally 512x512.


No error on Token Expiry

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Either create a new account or try forgot password on an existing account
Visit the email and copy the reset password link
Wait for sometime (maybe 30 mins) so that the token expires
Try resetting the password.
You can even reproduce this by copying the reset link once, resetting the password successfully and then retrying the same link.

Expected Result:
It should throw an error that Token has expired.
Actual Result:
It throws an exception in the network console but no feedback to the user.

Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
View all open jobs on GitHub

Triggered auto assignment to @CortneyOfstad (AutoAssignerTriage), see https://stackoverflow.com/c/expensify/questions/4749 for more details.

Proposed Solution
Add a catch block to setPassword API:
function setPassword(password, validateCode, accountID) {
  Onyx.merge(ONYXKEYS.ACCOUNT, {...CONST.DEFAULT_ACCOUNT_DATA, loading: true});

  API.SetPassword({
    password,
    validateCode,
    accountID,
  })
    .then((response) => {
         /// existing code
    })
    .catch((err) => {
        Onyx.merge(ONYXKEYS.ACCOUNT, {error: err.message});
    })
   // existing code
}

Triggered auto assignment to @cead22 (Engineering), see https://stackoverflow.com/c/expensify/questions/4319 for more details.

Just updated a few things here as this issue confused me. It seems like it's not an authToken expiring but the validate code.

Hmm this seems to be a duplicate issue of https://github.com/Expensify/App/issues/4737 so I am closing it.
@akshayasalvi feel free to propose your solution there if you'd like.

Okay. Thank you.


Remove another std::call_once to avoid initialization crashes

We ran into this with GCC 11.  Similar fix as before, removing the call_once for a static initializer.

@jmlait I've already fixed this in the PR I put up yesterday, see #1620


ZEPPELIN-3239. unicode characters in an iPython paragraph makes Spark interpreter irresponsive

What is this PR for?
Fix the unicode issues in python2.
What type of PR is it?
[Bug Fix | Improvement ]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-3239

How should this be tested?

Unit test is added

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@Tagar Could you help try verify this PR ? Thanks

thanks @zjffdu! will give this a try today.

Verified manually. Works as expected. Thanks a lot @zjffdu

Awesome，will merge it soon


Use DMatrix Proxy for implementing data callback.

@RAMitchell @hcho3 The second prototype.
Closes #5583, #5571
Please ignore the code in quantile, it's copied and pasted from hist_util.cu.
Depends on #5623 .  First prototype is in #5630 .

One last piece would be the dask interface then the big series will be over.


feat: add popup to layout

Same as with #618: I'm leaving this in draft for now and won't be adding tests or fixing coverage just yet. I'm putting in the effort of accompanying the PR/variant with tests/coverage when the decision is made.

With this variant, the idea is to clearly communicate the intent for creating popups with a distinct struct in the layout module. Alternatively, if you're opposed to the struct, this could be done with plain functions and without the re-export in src/layout.rs, as in ratatui::layout::popup::percentage(x, y, rect), but IMO the struct, which can easily be re-exported in prelude.rs like I did here, serves as a better, more stream-lined entrypoint for users than a module with plain functions would.
The other use cases mentioned in https://github.com/ratatui-org/ratatui/issues/617#issuecomment-1801173192, i.e. popup with explicit size, based on margins, I can add later. With this variant though I'd avoid using generics and rather have individual functions, for the same reason as mentioned before: clearly communicate intent and thus more easily understandable API.

fixes #617

I think at this point, this seems too hyper-specific (or put another way, it solves just one problem which I'm not sure is the right problem to solve). To validate that I'd ask several questions:

why is centered the right way to render this and not right / left aligned?
why is this called popup?
what inherently makes a popup centered?
more questions generally about how the API evolves from here

I suspect the right way to prototype this would be to do so in a second crate and bring the more complete ideas into the core once shown to work well for several apps. Alternatively consider helping spec https://github.com/ratatui-org/ratatui/issues/621 first
Right now the methods in Layout are mostly 1 dimensional rather than 2D - we should probably fix that by moving to a taffy based implementation that does flex/grid layout rather than going more specific like this.

I've updated this draft to use stability::unstable.

There is now tui-popup which is dedicated to building popups. Maintained by @joshka.
I'm closing this. Feel free to reopen if you think it is still relevant.

This is awesome! Thanks @joshka! I already started my own tui-popup crate, including the three variants I proposed here, but I wasn't ready to publish yet :sweat_smile: I'll try out your tui-popup.

There's also https://github.com/sephiroth74/tui-confirm-dialog to take a look at - not mine - but recent also. Uses channels to communicate back to the app, which is a neat but more complex approach.


std.array: check for overflow on allocation sizes

Current coverage is 88.68% (diff: 100%)

Merging #4656 into master will increase coverage by <.01%

@@             master      #4656   diff @@
==========================================
  Files           121        121
  Lines         73827      73833     +6
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          65471      65477     +6
  Misses         8356       8356
  Partials          0          0

Powered by Codecov. Last update 6db08d3...13865f0

LGTM

LGTM

Auto-merge toggled on


feat: tail-recursive and short-circuiting version of List.any/all

I'll close this in favour of leanprover/lean4#2972. Reviews there welcome.


Using enums as a record key

I need to migrate from follow Zod construction with Record
const MyRecordSchema = z.record(z.nativeEnum(KEY_NAME), z.array(z.string().min(1)).nonempty());

If I change this construction to
const MyRecordSchema = record(nativeEnum(KEY_NAME), array(string([minLength(1)]), [minLength(2)]));

I got follow TS error
Types of property  schema  are incompatible.
Type  "native_enum"  is not assignable to type  "string"

So any idea how to fix this error pls? If I ignore it and run parse, it works correctrly, and return error when I try to pass incorrect key (not from KEY_NAME object).

Thank you very much for your hint. I will try to fix that next week. Basically I just need to update the types. As you wrote correctly, it already works technically.

v0.15.0 is now available.


Implement Code Splitting Using lazy()

Right now the app downloads about 300kb of data just to redirect to the link which reduces the speed of the app and hinders  User's experience.So it would be a very good idea to implement Code Splitting using Lazy() to remove slow load times and make it nearly negligible.
Resources:

https://reactjs.org/docs/code-splitting.html
https://web.dev/code-splitting-suspense/

I would like to work on this issue, I am a participant of SWoC.

I would like to work on this issue, I am a participant of SWoC.

Please go ahead @ayushrastogi689

Please go ahead @ayushrastogi689

@monizb can you please tell me how to reach you. Your linkedin id?

@monizb can you please tell me how to reach you. Your linkedin id?

Hey @ayushrastogi689 you can find me on the Discord Channel on the DWOC server's "Fireshort" Channel

Hey @ayushrastogi689 you can find me on the Discord Channel on the DWOC server's "Fireshort" Channel

I will submit my PR for this issue the same day when assigned. please assign me this issue

I will submit my PR for this issue the same day when assigned. please assign me this issue

I will work on this issue & I will submit my PR within a day .

I will work on this issue & I will submit my PR within a day .

@ayushrastogi689 are you still working on this or not?

@ayushrastogi689 are you still working on this or not?

sir this is a very easy task. taking more than 13days is an insane amount of time. Clearly, he is inactive. Please consider reviewing my PR.

sir this is a very easy task. taking more than 13days is an insane amount of time. Clearly, he is inactive. Please consider reviewing my PR.

I have done it within a day. Please consider my PR.

I have done it within a day. Please consider my PR.

@ayushrastogi689 since you aren't responding, you are being unassigned

@ayushrastogi689 since you aren't responding, you are being unassigned


Lberner ado 165297 cable details

@dansisson, @alkohli
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Closing this PR as no longer needed.


Added installation created payload

I am not sure why I created this payload, probably to add some more tests.
But, it might be helpful in the future, so I am opening this PR.

Closing this stale PR.


[Question] Readme example not working for me

Sorry for such a basic question, but the example in the readme does not work for me.  Here is the content of my cargo.toml file:
[package]
name = "cursive_readme_test"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies.cursive]
version = "~0.18"
default-features = false

[features]
crossterm-backend = ["cursive/crossterm-backend"]

In the main.rs file, I have literally copied the code from the readme example (the Hello Dialog example).  The application compiles, but I can't get it to run neither on Windows nor on macOs.
Maybe I am doing something wrong and there is something I never knew on how to start TUI applications.  The only other TUI application I have ever used (I think) is ccmake and all I had to do to use this application is start it in the command line, so I am naively just typing ./target/debug/cursive_readme_test and nothing happens.   I have also tried starting it via cargo (as cargo run), but it won't work either.  No matter what I try, nothing happens.
If anyone could point me to the dumb thing I am forgetting, it would be greatly appreciated.  Again, sorry for such a basic question.

Hi!
Your Cargo.toml defines a crossterm-backend feature that forwards it to cursive. It's exactly what you need to run on windows, but by default it doesn't seem to be enabled.
You turn it on using cargo run --features crossterm-backend. You can also turn it on by default with
[package]
name = "cursive_readme_test"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies.cursive]
version = "~0.18"
default-features = false

[features]
default = ["crossterm-backend"]
crossterm-backend = ["cursive/crossterm-backend"]

Or simply always turn on this feature in cursive:
[package]
name = "cursive_readme_test"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies.cursive]
version = "~0.18"
default-features = false
features = ["crossterm-backend"]

Either of these 3 solutions should get you running.

This worked like a charm.  I guess the crux of the problem was my poor understanding of cargo (crates and features and such).
Thank you sooooo much and sorry for the newbie question.


get_publish_date() Strategy 3 not implemented

https://github.com/codelucas/newspaper/blob/c0eed1a571ab91382ca7e86767b2c26e7e59bbd2/newspaper/extractors.py#L179
Strategy 3 (search body for date) is not implemented, so currently bbc articles, e.g.
http://www.bbc.com/news/business-43133853
Which do not have any data in the URL or meta tags, do not have any publish date even though the date and time is clearly in the HTML as

20 February 2018

Thanks for reminding us of this, will leave this task open for anyone to take it on.

BBC uses schema.org
I have tested it including #385
And it works (tested with https://www.bbc.com/news/business-43133853)


Update checkstyle suppressions

After our client libraries were moved to a different folder structure under sdk, the paths in checkstyle suppressions were no longer valid. This updates those paths.
Fixes the potential null reference exception in .hashCode().

FYI @mitchdenny something to consider when moving things.


Match payload test to the instructions for challenge httpHeaderXssChallenge

Oh, good catch, sir! Thank you!


Which is the right image for the download?

Hi all,
The Windows 10 IoT Core Packages (1809) here is not same as the image here. There are 2 different images on the Windows IoT Core Downloads page: LTSC and SAC.
The pre-build FFU for the DragonBoard 410c is different too.
Which is the right version?
Best regards.

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

ID: 3342816d-89ce-b43f-0db1-76f3d34fe1cc
Version Independent ID: 37cec018-8b1b-379a-4392-f1c4ddbfca86
Content: Downloads - Windows IoT
Content Source: windows-iotcore/Downloads.md
Product: windows-hardware
GitHub Login: @saraclay
Microsoft Alias: saclayt

Hi @moyanming, please refer to "The Latest Windows 10 IoT Core" builds here: https://docs.microsoft.com/en-us/windows/iot-core/downloads#latest-windows-10-iot-core-builds
We have the other builds from past releases due to some servicing requests.

The builds may just be different names... I am confirming this with another member of the team.

Why not use the same name or the same download link?
There are 2 different version of the Windows 10 IoT Core Package (1809) here: LTSC and SAC. But there is only one version can be download here. Is this means there are 3 different version of the Windows 10 IoT Core Package?
BTW, the name of the LTSC and SAC is same and why?
LTSC: Windows10_IoTCore_Packages_ARM32_en-us_17763Oct.ios
SAC:  Windows10_IoTCore_Packages_ARM32_en-us_17763Oct.ios

Hi @moyanming - you are correct in that LTSC and SAC are the same. However, the key you use will be different. For example, if you decide to use Windows 10 IoT Core Services, you will use LTSC/LTSC key. SAC is if you are not using any services. The one on our documentation page is SAC.
We realize this is confusing and will try and think of a better way to message this. I hope this answers your question.


Package renames should affect fingerprints

Added the actual fix, ready for the review.

@bors: r+
Awesome, thanks!

:pushpin: Commit fc72bcb has been approved by alexcrichton

:hourglass: Testing commit fc72bcb4494361ebd0870d09b8352a75eed3323b with merge 2654a6c9ef7fc282c4a230f879cf0a93a007d2b6...

:broken_heart: Test failed - status-travis

@bors: retry
??

:hourglass: Testing commit fc72bcb4494361ebd0870d09b8352a75eed3323b with merge 450aed598b148eb540ce659818ab474441414be2...

:broken_heart: Test failed - status-travis

@bors: retry

:hourglass: Testing commit fc72bcb4494361ebd0870d09b8352a75eed3323b with merge 07d022dc70e419c81f1273a42d8103f8be80f0bb...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 07d022dc70e419c81f1273a42d8103f8be80f0bb to master...


Deployment

Deployment
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser

Successfully launched application


Add dev-rountable-001 thru 004

Resolves #270
Fix typo on roundtable-001 thru 007
Add Roundtable-008 and 009
Add dev-roundtable-001 thru 004
Change past: false to past: true for historic roundtable and dev-roundtable events.
Preview Links
https://deploy-preview-271--navhub.netlify.com/events/
Checklist

[x] Have you assigned/claimed the issues you've resolved in this pull request?
[ ] Have the issues been moved to the QA column of the NavCoin Websites project?
[x] Have you checked there are no merge conflicts?
[x] Have you tested the changes work across both mobile and desktop?

Approved.
Resolves https://github.com/navcoin/NavHub/issues/270
Bounty Medium pending.
Please post a NAV address @roast-nav thanks!


Improve git clone

Is your feature request related to a problem? Please describe.
Before:
git clone https://github.com/EsotericSoftware/spine-runtimes.git -c core.longpaths=true -c core.fsmonitor=false source.tmp\spine-runtimes
Cloning into 'source.tmp\spine-runtimes'...
remote: Enumerating objects: 120521, done.
remote: Counting objects: 100% (8354/8354), done.
remote: Compressing objects: 100% (3149/3149), done.
remote: Total 120521 (delta 5148), reused 7800 (delta 4715), pack-reused 112167 (from 1)
Receiving objects: 100% (120521/120521), 466.56 MiB | 16.85 MiB/s, done.
Resolving deltas: 100% (82459/82459), done.
Updating files: 100% (5541/5541), done.
git -c core.fsmonitor=false checkout d33c10f85634d01efbe4a3ab31dabaeaca41230c
Updating files: 100% (5871/5871), done.

Now:
Add --filter=tree:0 --no-checkout
git clone https://github.com/EsotericSoftware/spine-runtimes.git -c core.longpaths=true -c core.fsmonitor=false --filter=tree:0 --no-checkout source.tmp\spine-runtimes
Cloning into 'source.tmp\spine-runtimes'...
remote: Enumerating objects: 9495, done.
remote: Counting objects: 100% (580/580), done.
remote: Compressing objects: 100% (569/569), done.
remote: Total 9495 (delta 11), reused 571 (delta 11), pack-reused 8915 (from 1)
Receiving objects: 100% (9495/9495), 1.91 MiB | 7.91 MiB/s, done.
Resolving deltas: 100% (176/176), done.
git -c core.fsmonitor=false checkout d33c10f85634d01efbe4a3ab31dabaeaca41230c
remote: Enumerating objects: 703, done.
remote: Counting objects: 100% (507/507), done.
remote: Compressing objects: 100% (422/422), done.
remote: Total 703 (delta 26), reused 308 (delta 21), pack-reused 196 (from 1)
Receiving objects: 100% (703/703), 185.71 KiB | 2.00 MiB/s, done.
Resolving deltas: 100% (27/27), done.
remote: Enumerating objects: 496, done.
remote: Counting objects: 100% (183/183), done.
remote: Compressing objects: 100% (182/182), done.
remote: Total 496 (delta 3), reused 1 (delta 1), pack-reused 313 (from 1)
Receiving objects: 100% (496/496), 136.90 KiB | 1.63 MiB/s, done.
Resolving deltas: 100% (6/6), done.
remote: Enumerating objects: 3505, done.
remote: Counting objects: 100% (1488/1488), done.
remote: Compressing objects: 100% (1121/1121), done.
remote: Total 3505 (delta 908), reused 367 (delta 367), pack-reused 2017 (from 1)
Receiving objects: 100% (3505/3505), 51.29 MiB | 16.72 MiB/s, done.
Resolving deltas: 100% (1491/1491), done.
Updating files: 100% (3907/3907), done.

Describe the solution you'd like
https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone

Treeless clones are really only helpful for automated builds when you want to quickly clone, compile a project, then throw away the repository. In environments like GitHub Actions using public runners, you want to minimize your clone time so you can spend your machine time actually building your software! Treeless clones might be an excellent option for those environments.

Describe alternatives you've considered
No response
Additional context
No response

这两参数的兼容性怎样，低版本 git 支持么

另外，目前 clone 需要指定某个 branch，git clone --depth 1 -b branchname 这种支持么，depth 还需要指定么

这两参数的兼容性怎样，低版本 git 支持么

暂时没找到哪个版本给的，但看 partial-clone 里面的时间，大概 2021 年就有了。

另外，目前 clone 需要指定某个 branch，git clone --depth 1 -b branchname 这种支持么，depth 还需要指定么

看 https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone ，这个就是 depth 1 加强版。

快是快，但是 clone 下来没啥东西么。。
ruki-2:tmp ruki$ git clone --filter=tree:0 --no-checkout git@github.com:xmake-io/xmake.git
Cloning into 'xmake'...
remote: Enumerating objects: 14502, done.
remote: Counting objects: 100% (370/370), done.
remote: Compressing objects: 100% (363/363), done.
remote: Total 14502 (delta 7), reused 330 (delta 7), pack-reused 14132 (from 1)
Receiving objects: 100% (14502/14502), 4.76 MiB | 704.00 KiB/s, done.
Resolving deltas: 100% (44/44), done.
ruki-2:tmp ruki$ cd xmake
ruki-2:xmake ruki$ ls
ruki-2:xmake ruki$ ls -a
.	..	.git

that's because of the --no-checkout, not --filter=tree:0

Useful for package that have git url(imgui docking/spine-runtimes/godotcpp4 etc...)

https://github.blog/open-source/git/get-up-to-speed-with-partial-clone-and-shallow-clone

it works.

On github.com and GitHub Enterprise Server 2.22+, there are two options available:
Treeless clones: git clone --filter=tree:0

Does all git server support it?

https://github.com/xmake-io/xmake/pull/5509

try it again.

测试了下，似乎 depth 1 更快么。
depth 1
[ruki@5dd706d1f15e xmake-repo]$ time xmake update -s -v dev
checking for unzip ... /usr/sbin/unzip
checking for git ... /usr/sbin/git
checking for gzip ... /usr/sbin/gzip
checking for tar ... /usr/sbin/tar
checking for ping ... no
/usr/sbin/git ls-remote --refs https://github.com/xmake-io/xmake.git
update version dev from official source ..
prepared to download to temp dir /tmp/.xmake971/240826/xmakesrc/dev ..
  => downloading https://github.com/xmake-io/xmake.git .. /usr/sbin/git clone https://github.com/xmake-io/xmake.git -b dev --depth 1 -c core.fsmonitor=false /tmp/.xmake971/240826/xmakesrc/dev
Cloning into '/tmp/.xmake971/240826/xmakesrc/dev'...
remote: Enumerating objects: 4233, done.
remote: Counting objects: 100% (4233/4233), done.
remote: Compressing objects: 100% (3288/3288), done.
remote: Total 4233 (delta 1220), reused 2351 (delta 448), pack-reused 0 (from 0)
Receiving objects: 100% (4233/4233), 2.75 MiB | 2.62 MiB/s, done.
Resolving deltas: 100% (1220/1220), done.
  => download https://github.com/xmake-io/xmake.git .. ok
  => install script to /home/ruki/.local/share/xmake .. sh /home/ruki/.local/share/xmake/scripts/update-script.sh /home/ruki/.local/share/xmake /tmp/.xmake971/240826/xmakesrc/dev/xmake
ok

real	0m4.580s
user	0m0.587s
sys	0m0.806s

treeless
[ruki@5dd706d1f15e xmake-repo]$ time xmake update -s -v dev
checking for unzip ... /usr/sbin/unzip
checking for git ... /usr/sbin/git
checking for gzip ... /usr/sbin/gzip
checking for tar ... /usr/sbin/tar
checking for ping ... no
/usr/sbin/git ls-remote --refs https://github.com/xmake-io/xmake.git
update version dev from official source ..
prepared to download to temp dir /tmp/.xmake971/240826/xmakesrc/dev ..
  => downloading https://github.com/xmake-io/xmake.git .. /usr/sbin/git clone https://github.com/xmake-io/xmake.git -b dev --filter=tree:0 -c core.fsmonitor=false /tmp/.xmake971/240826/xmakesrc/dev
Cloning into '/tmp/.xmake971/240826/xmakesrc/dev'...
remote: Enumerating objects: 14506, done.
remote: Counting objects: 100% (374/374), done.
remote: Compressing objects: 100% (367/367), done.
remote: Total 14506 (delta 7), reused 333 (delta 7), pack-reused 14132 (from 1)
Receiving objects: 100% (14506/14506), 4.76 MiB | 3.02 MiB/s, done.
Resolving deltas: 100% (44/44), done.
remote: Enumerating objects: 1349, done.
remote: Counting objects: 100% (322/322), done.
remote: Compressing objects: 100% (288/288), done.
remote: Total 1349 (delta 7), reused 111 (delta 4), pack-reused 1027 (from 1)
Receiving objects: 100% (1349/1349), 160.39 KiB | 423.00 KiB/s, done.
Resolving deltas: 100% (15/15), done.
remote: Enumerating objects: 2883, done.
remote: Counting objects: 100% (2010/2010), done.
remote: Compressing objects: 100% (1720/1720), done.
remote: Total 2883 (delta 1018), reused 355 (delta 289), pack-reused 873 (from 1)
Receiving objects: 100% (2883/2883), 2.61 MiB | 2.20 MiB/s, done.
Resolving deltas: 100% (1168/1168), done.
Updating files: 100% (3494/3494), done.
  => download https://github.com/xmake-io/xmake.git .. ok
  => install script to /home/ruki/.local/share/xmake .. sh /home/ruki/.local/share/xmake/scripts/update-script.sh /home/ruki/.local/share/xmake /tmp/.xmake971/240826/xmakesrc/dev/xmake
ok

real	0m9.093s
user	0m0.932s
sys	0m1.501s

depth 1
[ruki@5dd706d1f15e tmp]$ time git clone https://github.com/EsotericSoftware/spine-runtimes.git --depth 1
Cloning into 'spine-runtimes'...
remote: Enumerating objects: 5367, done.
remote: Counting objects: 100% (5367/5367), done.
remote: Compressing objects: 100% (3886/3886), done.
remote: Total 5367 (delta 1939), reused 3895 (delta 1351), pack-reused 0 (from 0)
Receiving objects: 100% (5367/5367), 81.73 MiB | 3.24 MiB/s, done.
Resolving deltas: 100% (1939/1939), done.
Updating files: 100% (5541/5541), done.

real	0m29.297s
user	0m3.782s
sys	0m7.461s

treeless
[ruki@5dd706d1f15e tmp]$ time git clone https://github.com/EsotericSoftware/spine-runtimes.git --filter=tree:0
Cloning into 'spine-runtimes'...
remote: Enumerating objects: 9496, done.
remote: Counting objects: 100% (581/581), done.
remote: Compressing objects: 100% (570/570), done.
remote: Total 9496 (delta 11), reused 571 (delta 11), pack-reused 8915 (from 1)
Receiving objects: 100% (9496/9496), 1.91 MiB | 1.93 MiB/s, done.
Resolving deltas: 100% (185/185), done.
remote: Enumerating objects: 703, done.
remote: Counting objects: 100% (507/507), done.
remote: Compressing objects: 100% (423/423), done.
remote: Total 703 (delta 25), reused 307 (delta 20), pack-reused 196 (from 1)
Receiving objects: 100% (703/703), 186.42 KiB | 763.00 KiB/s, done.
Resolving deltas: 100% (26/26), done.
remote: Enumerating objects: 4663, done.
remote: Counting objects: 100% (2417/2417), done.
remote: Compressing objects: 100% (1682/1682), done.
remote: Total 4663 (delta 1191), reused 1193 (delta 731), pack-reused 2246 (from 1)
Receiving objects: 100% (4663/4663), 81.45 MiB | 2.81 MiB/s, done.
Resolving deltas: 100% (1789/1789), done.
Updating files: 100% (5541/5541), done.

real	0m36.941s
user	0m4.327s
sys	0m8.773s

I revert it first.

Try xmake l scripts\test.lua --shallow -vD spine-runtimes

Try xmake l scripts\test.lua --shallow -vD spine-runtimes

no package in xmake-repo
see

depth 1
[ruki@5dd706d1f15e tmp]$ time git clone https://github.com/EsotericSoftware/spine-runtimes.git --depth 1
Cloning into 'spine-runtimes'...
remote: Enumerating objects: 5367, done.
remote: Counting objects: 100% (5367/5367), done.
remote: Compressing objects: 100% (3886/3886), done.
remote: Total 5367 (delta 1939), reused 3895 (delta 1351), pack-reused 0 (from 0)
Receiving objects: 100% (5367/5367), 81.73 MiB | 3.24 MiB/s, done.
Resolving deltas: 100% (1939/1939), done.
Updating files: 100% (5541/5541), done.

real	0m29.297s
user	0m3.782s
sys	0m7.461s

treeless
[ruki@5dd706d1f15e tmp]$ time git clone https://github.com/EsotericSoftware/spine-runtimes.git --filter=tree:0
Cloning into 'spine-runtimes'...
remote: Enumerating objects: 9496, done.
remote: Counting objects: 100% (581/581), done.
remote: Compressing objects: 100% (570/570), done.
remote: Total 9496 (delta 11), reused 571 (delta 11), pack-reused 8915 (from 1)
Receiving objects: 100% (9496/9496), 1.91 MiB | 1.93 MiB/s, done.
Resolving deltas: 100% (185/185), done.
remote: Enumerating objects: 703, done.
remote: Counting objects: 100% (507/507), done.
remote: Compressing objects: 100% (423/423), done.
remote: Total 703 (delta 25), reused 307 (delta 20), pack-reused 196 (from 1)
Receiving objects: 100% (703/703), 186.42 KiB | 763.00 KiB/s, done.
Resolving deltas: 100% (26/26), done.
remote: Enumerating objects: 4663, done.
remote: Counting objects: 100% (2417/2417), done.
remote: Compressing objects: 100% (1682/1682), done.
remote: Total 4663 (delta 1191), reused 1193 (delta 731), pack-reused 2246 (from 1)
Receiving objects: 100% (4663/4663), 81.45 MiB | 2.81 MiB/s, done.
Resolving deltas: 100% (1789/1789), done.
Updating files: 100% (5541/5541), done.

real	0m36.941s
user	0m4.327s
sys	0m8.773s

Update xrepo first https://github.com/xmake-io/xmake-repo/pull/5034
spine-runtimes need checkout to specify commit, so depth 1 not be useful on this case

Update xrepo first xmake-io/xmake-repo#5034
spine-runtimes need to checkout specify commit, so depth 1 not be useful on this case

这个不能用来改进 git clone --depth 1，只能用来改进 git clone + git checkout 的 case。
https://github.com/xmake-io/xmake/pull/5510

Useful for package that have git url(imgui docking/spine-runtimes/godotcpp4 etc...)

😥

try it again.


Value in quotes in shorthand publish should be evaluated as string type

Fixes issue https://github.com/StackStorm/orquesta/issues/130
During parse_inline_params is called to parse parameters input, the leading and trailing single/double quotes is removed. Digit and True/False in quotes will be parsed as number and boolean type instead of String after json.loads().
Solution:
For string in quotes (not includes dictionary  'x=\'{\"a\": 1}\''), 'json.loads' is not called.

Codecov Report

Merging #131 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #131      +/-   ##
==========================================
+ Coverage   94.04%   94.05%   +0.01%
==========================================
  Files          38       38
  Lines        2450     2455       +5
  Branches      494      495       +1
==========================================
+ Hits         2304     2309       +5
  Misses         85       85
  Partials       61       61

Impacted Files
Coverage Δ

orquesta/utils/parameters.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Missing content model causes DeliveryClient to silently fail

Brief bug description
When a new content model is created in KC and there is no corresponding POCO in the app (therefore CustomTypeProvider does not recognize the model), DeliveryClient fails when returning content items that contain content items based on this model. It does not throw any exception, but returns with Items property containing null.
Problem is in InlineContentItemsProcessor.cs on line 69 -> inlineContentItem is null, therefore invoking GetType() will generate NullReferenceException. This exception is not propagated to the app, but silently ignored and DeliveryClient just returns null in DeliveryItemListingResponse.
Repro steps

Generate POCO for KC content models
Add new content model in KC
Create content item that has a rich text editor. Add linked item based on the new content model
Get the new content item using DeliveryClient.GetItemsAsync
Items property of the result is null

Expected behavior
I'd expect either null or exception. Not null of the whole Items property, but of the linked item that there is no POCO for.
Test environment

Platform/OS: .NET 4.6

will be released in https://github.com/Kentico/delivery-sdk-net/releases/tag/9.0.0


COMP: Replace SetUseImageSpacing() with SetUseImageSpacing(true)

Use of SetUseImageSpacing(bool) is deprecated in the future

@ntustison I'm working on making ANTs compatible with future versions of ITK.  This change will be necessary to be backward and forward compatible.

Thanks Hans.  Currently away until Sunday but let me know if you need anything from me.

On Aug 5, 2021, at 4:33 PM, Hans Johnson @.***> wrote:

@ntustison I'm working on making ANTs compatible with future versions of ITK. This change will be necessary to be backward and forward compatible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

I think you are the only person who can merge on this repo.  Having a
backup who can merge would be great!
On Thu, Aug 5, 2021 at 6:59 PM Nick Tustison @.***>
wrote:

Thanks Hans. Currently away until Sunday but let me know if you need
anything from me.

On Aug 5, 2021, at 4:33 PM, Hans Johnson @.***> wrote:

@ntustison I'm working on making ANTs compatible with future versions of
ITK. This change will be necessary to be backward and forward compatible.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ntustison/ITKAdaptiveDenoising/pull/8#issuecomment-893901679,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACMU4V65TAAEFSXLE6TDRDT3MQVNANCNFSM5BUZVC7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

--
Hans J. Johnson, Ph.D.
@.***
(319) 621 7185

Okay, let me see if I can fix that.

Okay, I invited you as a collaborator.


Add pod security policy

PSP is deprecated: https://kubernetes.io/blog/2021/04/06/podsecuritypolicy-deprecation-past-present-and-future/


[smarter-device-manager] use /var/log for termination.messagePath (fixes #1092)

Signed-off-by: Andrew Zammit<EMAIL_ADDRESS>
Description of the change

Override the default container terminationMessagePath to allow mounting /dev as read-only. The path is now /var/log/termination-log. Fixes #1092.
Use the container's error log to populate the container termination message, since smarter-device-manager does not support a k8s termination-log.

Benefits
The default values.yaml for this chart now work out-of-the-box.
Possible drawbacks
This chart's common dependency was bumped on 8/12 to v4.0.0, which added support for the termination section. The default values added here may conflict with the consumer's expectation of behavior, albeit it never worked to begin with. If set by the consumer, these default values will have no effect.
Applicable issues

fixes #1092

Additional information

Checklist

[X] Chart version bumped in Chart.yaml according to semver.
[X] Title of the PR starts with chart name (e.g. [home-assistant])
[X] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

Thanks for the fix!


New sync protocol

More or less the complete solution - see TODO below.
Removes the HTTP API for ping, and instead introduce a sync_port where the node will listen for incoming TCP connections. A secure Noise handshake is made (using the protocol version and genesis hash to ensure nodes are compatible) and then this connection is kept for ping, sync, gossip, etc.
This includes a major rewrite of aec_peers and the introduction of aec_peer_connection - the new module contains all the logic for P2P communication (previously scattered between aeu_request, aehttp_dispatch_ext etc...).
TODO:

Document the changes to the configuration
Implement message fragmentation (once serialized blocks gets bigger than 2^16 bytes we hit this)
Fix the tests for blocked nodes + aec_peers
Perhaps some more tests as well
Eventually give up if connection/handshake works but we fail pinging
Remove more dead-code (aeu_request, etc...)

Is there some documentation on how overall sync works, including this?

Read the TODO :-)

Still most of the documentation is TODO... But I'd rather see the code running first!

Rebased on master and (hopefully) fixed peer key deployment - we will need to deploy twice (initially) but otherwise it should be rock solid :-)


Z820 rev 1.00 success (+discussion on possible SPI header pads)

Hi.
Thanks for this great pdf!
I can confirm that a Z820 rev 1.00 board (without E14 jumper) works with boot block update (via SPI) and ME8!
There are some pics of my board in
https://www.win-raid.com/t6670f39-everything-fine-but-No-valid-OEM-data-ICC-not-programmed-1.html
Without desoldering pins the RPi didn't find the chip. Also only VCC desoldering didn't work (maybe because of the other 3.3V connections).
So I desoldered every non-N/C pin (#RESET too). This worked. I connected it (without any resistor) according to your pdf and let #RESET disconnected (it is pull-up internally, #HOLD pin too theoretically..).
I also can confirm (via multimeter) that there are connections to the 8-pin E16 pad. I haven't written down the connections but they should be the same as described in
https://andybrown.me.uk/2014/11/01/z800/

Glad it helped!
Winbond's recommended implementation  for SPI flash is this:

I imagine HP implemented something like that on the board, but there are probably other things on the SPI bus lines (and a lot of other things on the board 3.3v line). I may have been lucky in being able to use my RPi to flash the chip - it defintely always took several attempts at clamping so there are probably severe signal integrity issues going on in addition to the parasitic drain of the rest of the board.
I don't see any E16 pad on the Z820, is it the unpopulated SOP8 next to the SOP16 SPI flash chip in the bottom right corner of the board?
The Z420/Z620 seem to have an unpopulated 7 pin throughhole header left of their flash chip, and 2 unpopulated SOP8 headers (of different width) under PCIe slots.
And also unpopulated pads for 2 switches and 2 seven segment digits, interestingly. I guess those might be power, reset, and POST code.

Here for the z800:
https://andybrown.me.uk/wp-content/images//z800/spi_recovery.jpg
and here for the z820 (on the bottom):

Both are described as E16.
On the z820 there is also the term "SPI" further right.

Ah, I see. Looks like it's common to Zx00 and Zx20 and even possibly Zx40 although that one has 9 pins.
This is very cool - those pads don't look too bad to solder to at all. I guess the issue of parasitic drain is still there though.
I wonder how HP would use it as an "SPI Recovery Header" - I would guess it would be with the workstation turned off, but maybe it's a tool that uses the board 3.3v as a supply. I think the board leaves the SPI flash chip alone after boot if no BIOS updates are being done, but I don't have a scope or logic analyzer to check that.

The one with the electric tape must be somewhere else :)
I used these:
https://www.aliexpress.com/item/33039250212.html
They work very well with unsoldered pins and tend to fall off on the soldered 16-SOP pins (but with not more than 2 side by side it works somehow)
I only can imagine ME stuff written on runtime so it could happen that the machine hangs or reboots at any time when writing via RPi at the same time. But ME can be disabled.
Flashrom seems to be able to write the whole flash only, this might be an additional risk.
On failure of course you could just continue with PC power disconnected :)
People have used external 3.3v (and not connecting the RPi 3.3v) to possibly powering the whole southbridge which is still lower risk than having the PC online.
Still the SPI header helps a lot. I should have soldered pins on it :D

Finally had some time to look at the header next to the SPI flash chip! Giving it a go on my Z400 first to work out any mistakes before I take a soldering iron to my Z620. I probed out the pins and found these results:

When I have some more time I'm going to try using flux and copper wick to clean up the existing solder on the pads, then solder in headers. I will then use those headers to keep a logic analyzer connected while the Z400 boots up and runs, so that I can spy on what HP does with the flash chip at various stages.

Also, on Z400 I noticed a 16 pin header right at the edge that made me think "convenient JTAG header" and I did find there's a 16 pin 'OCDS' jtag standard, although I'm not sure if that's what Intel would be using. There's also a 5 pin header and 6 pin header, it's possible the 5 pin header is for SMBUS.

Dare I ask if anyone with a programmer could try to unlock the following bios options and see what happens?
-overclocking
-sr-iov
I've reviewed a bios dump and the menu options definitely already exist in the AMI bios; they're just hidden.  Flashing a modified bios apparently doesn't work since hp signs the bios and rejects the modified file.  I'd be willing to do the work on my own machine if somebody would throw themselves on the sword to test it first.

@zack4485 let's make another issue to discuss BIOS options! My Z620 is currently doing useful things, but if these options are avaiable for Z400 as well I'm happy to try that out

I have no idea why CS is connected to two pins, including the special square one I would normally expect to be Vcc or GND.
But it does match up with the pinout you found for Z800 and Z820.

I wonder if there is a 0 ohm resistor bridging the pins together somewhere nearby, for when the pins are unpopulated.
Here you pin 1 and 2 are bridged on the Z800 motherboard picture:

I wonder if there is a 0 ohm resistor bridging the pins together somewhere nearby, for when the pins are unpopulated.

@cseufert
Was anyone ever able to use this "SPI header" for any useful flashing? The internet says nothing on the subject ...


Multiple streaming gopros

Hello! Thanks so much for such a useful tool. Do you have thoughts on where to start in order to enable up to four streams simultaneously? Is that possible without a total redesign? Ideally I'd like to be able to start multiple streams and assign IPv4 addresses to each available GoPro device. Thoughts on this much appreciated!

In theory this should be doable but requires changes/loops in some places. I'd think that each connected camera will get its own ip which you could pipe into a separate video device which you can forward to ffmpeg 🤔 Feel free to propose patches 👍🏼


Board for the AI upload console

About the PR
A board for the AI upload console. Liltenhead pointed out an interesting problem.
Why / Balance
You can disassemble and reassemble the console, and now they will not be irretrievably lost when destroyed.
Media

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

:cl: Nimfar11

add: Added a board for the AI upload console.

Thanks for the fix!
Small tip: You don't have to add your name to the :cl: symbol since it is the same as your github username. The bot will use that as a default.


Fix bug in the qr-code for replacing the recovery key

Before:

When the browser extension was unlocked, a valid qr-code for replacing the recovery key was generated.
When the browser extension was locked, an invalid qr-code for replacing the recovery key was generated.

Now:

When the browser extension is unlocked, a valid qr-code for replacing the recovery key is generated.
When the browser extension is locked, a valid qr-code for replacing the recovery key is generated.

🙌


ph7 in android

i try this progy ist perfect, congratulations...
but i find a bug so i reported .
in android (navigation bar) click on (search) is not Stable , for example,,, if u click on search must be show u { Quick search} & {Advance search} but in android this not working exactly ,
Thanks.....

@saman-magnus The application use the browser integrated into Android. We simply make application that call the browser but add option to the URL indicating that it should be optimized for mobile.
PM

Hi @saman-magnus
Thanks for your feedback! I couldn't replicate it. Can you send a screenshot showing the issue?
Thanks

@saman-magnus Hi,
Have you compiled your .apk from the sources or used a prebuilt application ?

@pH-7 We seem to be getting lot more reports from users who create a gitHub account for the sole reason of opening a issue.
We could deduce it as a proof that it's touching a wider visibility.
PM

@pH-7 I checked out his installation on https://azyek.com/ using both plain the Android browser and the Lightning browser. Everything looked fine to me.
@saman-magnus Have tried to create a Persian translation using right to left text language?

hi guys, i uploaded test video in https://youtu.be/tfSZmY-47Lg so u can see whats exactly problem ,i try it in google chrome miniopera and android webbrowser.
last night i try to fix this from css class but nothing :)
so thank u for answering & following...

Thanks @saman-magnus!
This looks like to be on a tablet, so you get a desktop menu.
Can you try to drag your finger from People to "Search" and keep it on Search, then you should see the sub drop-down menu appearing (without clicking on the links). The menus appears when you keep your finger on it, not when you are clicking on it (like when you are navigating on the menu with desktops; It's the same thing).
Thanks for the clear video! I really appreciate it :)

Thanks @saman-magnus!
This looks like to be on a tablet, so you get a desktop resolution menu.
Can you try to slide your finger across the menus, from People to "Search" and keep it on Search, then you should see the sub drop-down menu appearing (without clicking on the links). The menus appears when you keep your finger on it, not when you are clicking on it (like when you are navigating on the menu with desktops; It's the same thing).
Thanks for the clear video! I really appreciate it :)

Hi again @saman-magnus
Hopefully this helps. Let me know if your issue is still relevant?
Thanks

@saman-magnus Since you didn't get back to me, I'm closing it. Please reopen if the issue is still relevant for you. Thanks


Auto generate wire harness based on hardware

Generate wire harness documentation using WireViz (https://github.com/formatc1702/WireViz) based on the hardware definition in MPF (switches, coils, PSUs and specifics for each hardware).

Hey, I would love to help with this. Where should I create the files/code to generate the documentation? I wasn't sure if there was a specific space it should be done at

I guess this could become a separate command in MPF: https://github.com/missionpinball/mpf/tree/dev/mpf/commands. We can then later refactor code into other parts. Does that make sense?

This sounds fascinating but how would it work? Just give the pinouts for the headers on the board, or show the ins and outs of every part? That could be a very big diagram?

For certain hardware (i.e. FAST or Multimorphic) we show the headers for their node boards. Based on that we could generate wire harnesses. I guess we should start simple and then extend from there

So I manually produced this for FAST, how would this then work? Names of the connected switches/drivers shown in place of the ID numbers, or actual wiring shown? Would we need to know the physical locations of the parts on the playfield to get the sequence right?

Yeah exactly. We would have to discover the type of node boards for FAST (code exists for that) and then store a mapping for connectors to inputs/outputs. Based on the defined switches and coils we could generate a wire harness description for wirewiz, excel or similar tools

Ok. I tried to work out the basics of fast PSU mapping and got this, but it seems it could run out of control kind of easily? Also a bunch of confusion trying to work out the mapping but that's probably just me not really knowing anything about this..

Sweet. I guess we can think about separating exports later. This is better than what most makers got initially

I have no idea if it's right though, or what comparable would be for something like PROC. I sure as hell don't want to add something that generates a wiring diagram someone follows and electrocutes themselves.

We can add a warning. This should only be a starting point. In production machines you will probably also have some additional connectors and you would want to edit the wirewiz by hand anyway.

Fair. Should I try to autogenerate FAST or start from a different one? Is there a good example using FAST? I see that demo_man uses P_ROC/WPC which would make sense, but I don't know if generating these diagrams is a priority for WPC tables that have existing wiring harnesses?

Yeah FAST and P3-Roc make the most sense. Demo man is not optimal but it might be easy to modify it for those platforms. I mean just start the command and then we can create (or adjust) unittests in mpf.

Fair enough. Sorry, one other thing you mentioned above. You said that code exists for discovering node board types for FAST, I have found that code, but it applies only if the boards are already connected, is that the stage at which this would be used? Or would it be run before the boards are set up so they are not there to be tested yet?

I've been looking at this but there doesn't seem to be any way to populate the machine. values for lights, switches, coil, etc. without calling initialise_mpf() which will try to connect to actual hardware and halt if it fails (obviously there is no point in calculating wiring for the virtual platform!). It would seem wasteful to use an auxiliary parser to translate all the stuff just for wiring but possibly rather disruptive to divide initialization into two parts?

Ok, gotten this far. Wireviz doesn't like these huge images outputs though. It looks much better in SVG but I can't upload that.

More complete now. Still becomes a huge file. FAST don't seem to have any data on their DMD-based or Servo controllers any more, is there documentation available somewhere?

More complete now. Still becomes a huge file. FAST don't seem to have any data on their DMD-based or Servo controllers any more, is there documentation available somewhere?

Sweet. Maybe we have to generate separate images for separate wire harnesses eventually?
I think I got a datasheet for the servo boards somewhere.

Sweet. Maybe we have to generate separate images for separate wire harnesses eventually?
I think I got a datasheet for the servo boards somewhere.

I'll tidy what I have to pass prospector for now.

I'll tidy what I have to pass prospector for now.

Is there a good archive of test tables? I was only able to use one of the sample open source tables from the web page, since most of the tables are not open source, and many of the open source ones are for older versions or contain specification errors.

Is there a good archive of test tables? I was only able to use one of the sample open source tables from the web page, since most of the tables are not open source, and many of the open source ones are for older versions or contain specification errors.

Have a look at: https://missionpinball.org/projects.html. In the bottom we got a list of machines with source.

Have a look at: https://missionpinball.org/projects.html. In the bottom we got a list of machines with source.

Those are the ones I looked at, but as I said several are obsolete and some will not build.

Those are the ones I looked at, but as I said several are obsolete and some will not build.


Safe helm updates

If a user has a stable chart installed and runs helm upgrade it will automatically upgrade them to the latest published chart (stable or unstable).
This could cause breaking changes or unintended stability issues. I have found 3 possible solutions to make this better for users.

Create separate repos for helm releases (stable and beta?) and let users select which updates they want to subscribe to based on the repo they add in helm. This would prevent stable -> beta changes but would not fix the problem of major releases from stable -> stable if there are breaking changes (e.g. v1 -> v2)
We can use deprecation notifications to block upgrades until users change configuration to meet the new requirements. This is the approach Gitlab uses. It's nice that this doesn't require two repos and requires manual updates from a user to make sure they deploy the correct configuration with each chart if there are breaking changes.
Ideally there would be a way in helm to lock an installed version. This isn't possible today but it could work similar to how apt and yum work by specifying a version inside a config and each time helm upgrade or helm install is run it checks that version. This isn't possible today but I think it's a needed feature in helm in general. I'm going to work work with helm developers to suggest this feature but there's no timeline for when it could be available.

With those options I think number 2 is the easiest and most actionable right now. We don't have any charts that have breaking changes but we should document how to do that in our release documents and mention it in our user documents.
If that sounds like a good plan please :+1: this and I can work on doc changes.

As an example of what a deprecation message looks like you can see what it looks like to install a chart without required parameters. It's not the most user friendly output but it can have free form text to specify what needs to be included.
WARNING: This chart is deprecated
NAME: autoscaler
LAST DEPLOYED: Tue Feb 23 17:58:07 2021
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
NOTES:
##############################################################################
####   ERROR: You must specify values for either                          ####
####   autoDiscovery.clusterName or autoscalingGroups[]                   ####
##############################################################################

The deployment and pod will not be created and the installation is not functional
See README:
  open https://github.com/kubernetes/charts/tree/master/stable/cluster-autoscaler

If a user has a stable chart installed and runs helm upgrade it will automatically upgrade them to the latest published chart (stable or unstable).

Assume the user has helm install'd an ACK service controller chart with a chart:s3-v1-stable tag (note, we have the major version included in the Helm Chart stable tag now; there is no -stable tag suffix without a major version). Let's say this Helm Chart's Deployment image is controller:s3-v1.2.8
Now assume that we release a v2 series S3 ACK service controller and eventually release a Helm Chart that installs a stable image of this v2 series controller with a chart:s3-v2-stable tag. This Helm Chart's Deployment image is controller:s3-v2.0.3.
If the user does a raw helm upgrade, are you saying that Helm will install the chart:s3-v2-stable chart? If that is the case, that is super bad. :(

This could cause breaking changes or unintended stability issues. I have found 3 possible solutions to make this better for users.
1. Create separate repos for helm releases (stable and beta?) and let users select which updates they want to subscribe to based on the repo they add in helm. This would prevent stable -> beta changes but would not fix the problem of major releases from stable -> stable if there are breaking changes (e.g. v1 -> v2)

Yeah, this solution is icky, IMHO.

2. We can use deprecation notifications to block upgrades until users change configuration to meet the new requirements. This is the [approach Gitlab uses](https://docs.gitlab.com/charts/architecture/decisions.html#breaking-changes-via-deprecation). It's nice that this doesn't require two repos and requires manual updates from a user to make sure they deploy the correct configuration with each chart if there are breaking changes.

Slightly less icky, yes.

3. Ideally there would be a way in helm to lock an installed version. This isn't possible today but it could work similar to how apt and yum work by specifying a version inside a config and each time `helm upgrade` or `helm install` is run it checks that version. This isn't possible today but I think it's a needed feature in helm in general. I'm going to work work with helm developers to suggest this feature but there's no timeline for when it could be available.

Awesome. Keep us in the loop as to how that conversation with the Helm devs goes. I'm obviously very interested in the outcome.

With those options I think number 2 is the easiest and most actionable right now. We don't have any charts that have breaking changes but we should document how to do that in our release documents and mention it in our user documents.

Agreed. I'll be working on the release documentation (the contributor-focused docs, not the end-user docs) in the next couple days and will add information about stable releases.

If that sounds like a good plan please +1 this and I can work on doc changes.

:+1: from me, @rothgar

If the user does a raw helm upgrade, are you saying that Helm will install the chart:s3-v2-stable chart?
Yes. helm upgrade will automatically pull in the latest published release and currently there is no way to prevent that unless the user specifies the specific version they want.

If the user does a raw helm upgrade, are you saying that Helm will install the chart:s3-v2-stable chart?

Yes. helm upgrade will automatically pull in the latest published release and currently there is no way to prevent that unless the user specifies the specific version they want.

ewww. Yes, we should definitely work with the Helm community on that. Seems like a big problem.

Following the process for a Helm Improvement Proposal (HIP) I sent an email to the mailing list here before I create a formal proposal.
I'm guessing this feature review, implementation, and release is going to take a while so we should try our best not to make breaking changes without having deprecation notifications.


fix(pkg/oci): trim spaces when handling required_engine_version

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area plugins

/area registry

/area build

/area documentation

What this PR does / why we need it:
Properly trim spaces and parse the required engine version.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign mstemm for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: d4929d49090eeaff34e815d572b2732389f0feb6


python3Packages.plugwise: init at 0.8.5

Motivation for this change
Python module for Plugwise Smiles, Stretch and USB stick
https://github.com/plugwise/python-plugwise
This is a Home Assistant dependency.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110370 run on x86_64-darwin 1

3 packages failed to build and are new build failures:

python37Packages.plugwise: log https://termbin.com/k9u3
python38Packages.plugwise: log https://termbin.com/pb8k
python39Packages.plugwise: log https://termbin.com/87hf

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110370 run on x86_64-darwin 1

3 packages failed to build and are new build failures:

python37Packages.plugwise: log https://termbin.com/k9u3
python38Packages.plugwise: log https://termbin.com/pb8k
python39Packages.plugwise: log https://termbin.com/87hf

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110370 run on x86_64-linux 1

3 packages built:

python37Packages.plugwise
python38Packages.plugwise
python39Packages.plugwise

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110370 run on x86_64-linux 1

3 packages built:

python37Packages.plugwise
python38Packages.plugwise
python39Packages.plugwise

Same as https://github.com/NixOS/nixpkgs/pull/109629#issuecomment-768775218.

Same as https://github.com/NixOS/nixpkgs/pull/109629#issuecomment-768775218.

Thanks

Thanks


commit page not loading

https://hud.pytorch.org/commit/e69d82a9cc8dcbff92b838c1afca11e4b1f9fe95
Here is the console error:

I'm working on item 2, but where does it show in the hud? (I hate screenshots, but can you post one here?)


D/f ratio

The scaling formula based on a pin-hole camera model is
〖Anat〗_cm= 〖Anat〗_px  * ((Sw*(H+β)100))/(FlimW)
Where
〖Anat〗_cm ~ measured structure in cm
〖Anat〗_px  ~ measured structure in pixel units
Sw ~ sensor width in mm
imW ~ sensor (image) size in pixel units
Fl the focal length in mm
H is the distance (height in the case of drones) of sensor to object
ß is a correction factor for cases when the distance does not take the value of H (for example, a drone that is not lifting off at sea level)
in V 0.3 the field for ß is missing; that field should be able to accept any value (+/-) in metres, with two decimal places.

Implemented in v0.4


Prefer gpg2 over gpg.

When both of gpg and gpg2 are installed, gpg is selected currently.
Maybe almost alll users don't care it.
At least, for my usecase (for my own package site), multiple signatures with different hash algorithms are used.
They can be handled not by gpg, which only the first signature is verified, but by gpg2.

Indeed, it makes more sense to prioritize gpg2, doesn't it?
Thank you.


Change cassandra seed provider to jetstack/cassandra-kubernetes-seed-provider

This switches cassandra to use https://github.com/jetstack/cassandra-kubernetes-seed-provider, which is a fork of the seed provider from kubernetes/examples.
Change cassandra seed provider to jetstack/cassandra-kubernetes-seed-provider

navigator-e2e-v1-9  E2E test failure was a flake. See #343

/retest


SAK-44735 allow timerbar to work inside external iframe

CC: @dnhutchins are you willing to review?

/* eslint no-console: ["error", { allow: ["warn"] }] */

okay changes made