Flutter build apk error

Steps to reproduce
1-flutter clean
2-flutter pub get
3-flutter build apk
Expected result
build' process is completed.
Actual Result
You are applying Flutter's app_plugin_loader Gradle plugin imperatively using the apply script method, which is deprecated and will be removed in a future release. Migrate to applying Gradle plugins with the declarative plugins block: https://flutter.dev/go/flutter-gradle-plugin-apply

You are applying Flutter's main Gradle plugin imperatively using the apply script method, which is deprecated and will be removed in a future release. Migrate to applying Gradle plugins with the declarative plugins block: https://flutter.dev/go/flutter-gradle-plugin-apply

Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: /Users/osmandemiroz/.pub-cache/hosted/pub.dev/firebase_messaging-14.7.5/android/src/main/java/io/flutter/plugins/firebase/messaging/FlutterFirebaseMessagingPlugin.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /Users/osmandemiroz/.pub-cache/hosted/pub.dev/cloud_firestore-4.13.2/android/src/main/java/io/flutter/plugins/firebase/firestore/FlutterFirebaseFirestorePlugin.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: /Users/osmandemiroz/.pub-cache/hosted/pub.dev/firebase_dynamic_links-5.4.8/android/src/main/java/io/flutter/plugins/firebase/dynamiclinks/Utils.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Font asset "MaterialIcons-Regular.otf" was tree-shaken, reducing it from 1645184 to 6064 bytes (99.6% reduction). Tree-shaking can be disabled by providing the --no-tree-shake-icons flag when building your app.
e: /Users/osmandemiroz/development/flutterdemos/nerdy/build/flutter_udid/.transforms/7528a263edd3a9d3c05cd02843c5b357/transformed/out/jars/classes.jar!/META-INF/flutter_udid_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/development/flutterdemos/nerdy/build/share_plus/.transforms/988978dd7c70f97d79a2f3af25d0d2f9/transformed/out/jars/classes.jar!/META-INF/share_plus_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/development/flutterdemos/nerdy/build/sign_in_with_apple/.transforms/dd0d0e0a3fdc3eb65b2dbf56c6944898/transformed/out/jars/classes.jar!/META-INF/sign_in_with_apple_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/development/flutterdemos/nerdy/build/speech_to_text/.transforms/7a61a7c03649e9ed0e3ce5840ddb2b3c/transformed/out/jars/classes.jar!/META-INF/speech_to_text_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/development/flutterdemos/nerdy/build/flutter_security_checker/.transforms/5c64c2cb15966bc5f9febfae87c0d1d1/transformed/out/jars/classes.jar!/META-INF/flutter_security_checker_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/development/flutterdemos/nerdy/build/package_info_plus/.transforms/51f06ad580ab3ac777d39d22379c64bf/transformed/out/jars/classes.jar!/META-INF/package_info_plus_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/development/flutterdemos/nerdy/build/device_info_plus/.transforms/a1def4ff9698df0f6b5b4fcdfff42f74/transformed/out/jars/classes.jar!/META-INF/device_info_plus_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/1e4752b80e81e9638b341ae4c3462cbe/transformed/jetified-activity-1.7.2/jars/classes.jar!/META-INF/activity_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/429a98e03593ad26aa04d001228d1436/transformed/lifecycle-livedata-2.6.2/jars/classes.jar!/META-INF/lifecycle-livedata_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/f21f403a6cff190263b1cf4d2ac5295f/transformed/lifecycle-viewmodel-2.6.2/jars/classes.jar!/META-INF/lifecycle-viewmodel_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/c30e0a041fc5dbb20f4617a4d6a19442/transformed/lifecycle-livedata-core-2.6.2/jars/classes.jar!/META-INF/lifecycle-livedata-core_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/04abcc49625d48075ea49d208e1da3e8/transformed/jetified-lifecycle-viewmodel-savedstate-2.6.2/jars/classes.jar!/META-INF/lifecycle-viewmodel-savedstate_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/83d0c8d9e0f7e7be6a67fbb3dbc23a1a/transformed/jetified-core-ktx-1.10.1/jars/classes.jar!/META-INF/core-ktx_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/5233f5da26e5fc1c5d04c9d1b575adef/transformed/core-1.10.1/jars/classes.jar!/META-INF/core_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/db7cad8a5a7927258d286154fe7da045/transformed/lifecycle-runtime-2.6.2/jars/classes.jar!/META-INF/lifecycle-runtime_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/androidx.lifecycle/lifecycle-common/2.6.2/10f354fdb64868baecd67128560c5a0d6312c495/lifecycle-common-2.6.2.jar!/META-INF/lifecycle-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-android/1.7.1/c2d86b569f10b7fc7e28d3f50c0eed97897d77a7/kotlinx-coroutines-android-1.7.1.jar!/META-INF/kotlinx-coroutines-android.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/9b8e14f79120d852a2a84b21523da6c8/transformed/jetified-ads-adservices-java-1.0.0-beta05/jars/classes.jar!/META-INF/ads-adservices-java_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/29390bced8ec90b86aa67aa1c544d1c7/transformed/jetified-ads-adservices-1.0.0-beta05/jars/classes.jar!/META-INF/ads-adservices_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-core-jvm/1.7.1/63a0779cf668e2a47d13fda7c3b0c4f8dc7762f4/kotlinx-coroutines-core-jvm-1.7.1.jar!/META-INF/kotlinx-coroutines-core.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlinx/kotlinx-coroutines-play-services/1.7.1/6333bad6f256e2ca7bc2908f586be7161a41618c/kotlinx-coroutines-play-services-1.7.1.jar!/META-INF/kotlinx-coroutines-play-services.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/transforms-3/4e64669393e02460ae65c53c5ebce34c/transformed/jetified-savedstate-1.2.1/jars/classes.jar!/META-INF/savedstate_release.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.8.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.9.0/8ee15ef0c67dc83d874f412d84378d7f0eb50b63/kotlin-stdlib-1.9.0.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.9.0/8ee15ef0c67dc83d874f412d84378d7f0eb50b63/kotlin-stdlib-1.9.0.jar!/META-INF/kotlin-stdlib-jdk8.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.9.0/8ee15ef0c67dc83d874f412d84378d7f0eb50b63/kotlin-stdlib-1.9.0.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.
e: /Users/osmandemiroz/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib-common/1.9.0/cd65c21cfd1eec4d44ef09f9f52b6d9f8a720636/kotlin-stdlib-common-1.9.0.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.9.0, expected version is 1.6.0.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:packageRelease'.
> A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable
   > SigningConfig "release" is missing required property "storeFile".

* 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

BUILD FAILED in 2m 32s
Running Gradle task 'assembleRelease'...                          153.2s

┌─ Flutter Fix ─────────────────────────────────────────────────────────────────────────────────────┐
│ [!] Your project requires a newer version of the Kotlin Gradle plugin.                            │
│ Find the latest version on https://kotlinlang.org/docs/releases.html#release-details, then update │
│ /Users/osmandemiroz/development/flutterdemos/nerdy/android/build.gradle:                          │
│ ext.kotlin_version = '<latest-version>'                                                           │
└───────────────────────────────────────────────────────────────────────────────────────────────────┘
Gradle task assembleRelease failed with exit code 1

> A failure occurred while executing com.android.build.gradle.tasks.PackageAndroidArtifact$IncrementalSplitterRunnable
   > SigningConfig "release" is missing required property "storeFile".

This is an issue with your release config. From the logs share above, you are missing the storeFile. See https://docs.flutter.dev/deployment/android#reference-the-keystore-from-the-app for how to properly configure your app for release.
Closing from here as this is an issue with your configuration.
Thank you


4 icons added

4 New Icons :
piggy-bank
rocking-chair
landmark
gem

Looks Great!

@b0b90 Can you run the optimise script to refactor the icons?

Unstale.

Rocking chair and landmark icons are added. I removed them from the PR.
Gem icon pr #359  is still open and in discussion.
I optimized the piggy-bank icon for you.


[5.0] Cherry pick swiftSyntax related changes to swift-5.0-branch

This PR cherry picks all swiftSyntax related changes from master to swift-5.0-branch.

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - dd006f152f8ade3c22dda8c82dd13ae1c993ae93

@swift-ci test Linux

Build failed
Swift Test Linux Platform
Git Sha - dd006f152f8ade3c22dda8c82dd13ae1c993ae93


Remove lein2 from .travis.yml

This appears to be not supported anymore. The default is already set to lein 2

From looking at the job it defaulted to using the latest leiningen version 2.7.1, which is a good thing 👍

Merged, thanks!


Empty lists are now rendered as null in the JSON output

Previously they were rendered as an empty string.
This pull request should resolve #22.

:+1: Thank you!

@konklone I can't seem to request a review from you, but feel free to provide one.

I left a review with a (not super important) comment. It's :+1: from me, though as a non-maintainer, formally approving it would feel a bit strange.

This pull request should be ready for merging.  Go ahead and merge it, @h-m-f-t, if you agree.


This does not reflect current state of the Wix which is v5

Type of issue
Code doesn't work
Description
Provided code does not work with Wix v5 which is newest.
[Enter feedback here]
Page URL
https://learn.microsoft.com/en-us/dotnet/core/extensions/windows-service-with-installer?tabs=wix
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/extensions/windows-service-with-installer.md
Document Version Independent Id
83c4d805-1394-90b7-6def-cf809c33ae22
Article author
@IEvangelist
Metadata

ID: e044209a-0802-07c0-7518-208967a3ef02
Service: dotnet-fundamentals

Hi @hebrayah - thank you so much for posting this issue. Is this something you'd be interested in helping fix? When I originally wrote the article, I wrote it targeting v4 and everything worked perfectly there. If v5 introduced breaking changes, it would take me a bit to figure out what changed and how to adjust the article, but I'd be happy to review a PR that fixes it - again, if you're interested. Thank you, regardless.

This looks like a duplicate of #41989. Closing this issue in favor of the other, but the offer still stands @hebrayah - just let me know.

Hello,
Problem is that I am a java guy - so I am kind of learning dotnet - this is
why I cannot do it all by myself.
Also due to coming from the opensource world i am maybe spoiled with
extensive documentation of the opensource libraries - while this wix is
terrible.
Probably you have to pay to get something more informational.
It is not that bad - when I did a few steps back with my program it finally
compiled, however thanks for initiative of writing such documents, I
thought that this was created by Microsoft employees.
I would love to help when I learn a little more :)
Best regards
Marcin
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
Nie
zawiera wirusów.www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
wt., 13 sie 2024 o 16:33 David Pine @.***> napisał(a):

Hi @hebrayah https://github.com/hebrayah - thank you so much for
posting this issue. Is this something you'd be interested in helping fix?
When I originally wrote the article, I wrote it targeting v4 and everything
worked perfectly there. If v5 introduced breaking changes, it would take me
a bit to figure out what changed and how to adjust the article, but I'd be
happy to review a PR that fixes it - again, if you're interested. Thank
you, regardless.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/docs/issues/42118#issuecomment-2286411050, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AECCXSBK6WEY6MXRMSSVH7DZRIKK7AVCNFSM6AAAAABMNBO6FCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBWGQYTCMBVGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


feat: Display RAG results

Allow users to see the sources contributing to the model's output.

@3-ark Do you mean something like this? https://github.com/brianpetro/obsidian-smart-connections?tab=readme-ov-file#smart-chat-ai-conversations-based-on-your-notes

@3-ark So the key difference is showing similarity scores, right?

We have just added a feature to display search results with a similarity score! Check out the updates here and here. The release is scheduled for today.

Thanks for your suggestions!

We'll look into a better way to handle the model list.
For RAG search results, you can actually customize the limit in the Advanced Configuration settings: https://github.com/glowingjade/obsidian-smart-composer/wiki/1.4-Advanced-Configuration#rag-settings
Regarding Jan.ai - while I haven't checked if they support OpenAI-compatible APIs, you can use any provider that does through our custom OpenAI-compatible models option: https://github.com/glowingjade/obsidian-smart-composer/wiki/1.4-Advanced-Configuration#custom-openai-compatible-models


Admin checkbox to disable "Recently Added" on Discover page

Description
I would love ability to disable the "Recently Added" section on the Discover page. I don't mind users seeing content that is available when they come across it in Jellyseerr, but sometimes I don't want to advertise all the weird shiz that gets added. Until there is a way to block users from seeing content that they shouldn't have access to (Parental Controls, for example), a way to disable "Recently Added" would help my situation.
Desired Behavior
A checkbox on the admin settings page for the "Recently Added" section would be sufficient, in my opinion. Or maybe (or in addition to the admin settings toggle) a button on the "Manage Series" page to hide availability or hide from "Recently Added".
Additional Context
Mock-up of checkbox for "Recently Added" next to "Hide Available Media"

Code of Conduct

[x] I agree to follow Overseerr's Code of Conduct

This is already a feature. You can either disable visibility of recently added using the new customise discover page (this will affect you the admin too)

or if you just dont want your users to see recently added then

Disable that in settings > Users for new users and in Users page select all users and press bulk edit and remove view recently added permission.

Oof, thank you @Fallenbagel. Sorry I missed that, I appreciate your help & work on this project!


Explore using basepath to host the prod build under /explore  instead of pages directory folder structure

https://nextjs.org/docs/api-reference/next.config.js/basepath
module.exports = {
  basePath: '/explore',
}

On the prod s3 bucket I need a structure like:
/explore
---- index.html
----_next/
Currently, references to static assets inside index.html look like this:
script src="/_next/static/chunks/framework-5f4595e5518b5600.js"
I think we need them to be more like:
script src="/explore/_next/static/chunks/framework-5f4595e5518b5600.js"
Then, we can remove adding the /explore  directory in the pages directory

Lets discuss!

This ticket was merged in https://github.com/clevercanary/data-browser/pull/203


Useless pings

The problem
Sometimes half of the server gets pinged by the "helper" command for the most basic errors.
My idea for the solution
The bot can first ping On Patrol Helper and wait for 20 seconds, if nobody responds, then ping the related coding help role.
Additional context
I can fork and create a pull request if you approve this idea.

I think we've been looking at other ideas too, but we'll keep this in mind as well.

Yes, I've seen the other ideas for the help procedure but we can use this one until we agree on a new process.

If you wanna make a pr I'd be open to the idea of using it (or something pretty similar) for now.

I'd suggest it does this:

user asks for help
message sent to channel x, mentioning the particular help role (the channel will only be visible by on patrol helpers)
message sent to channel y (mentioning the particular help role), after 5 minutes if an on patrol helper didn't mark it as complete yet

I can add channel ids in later. I'd also be ok with doing it myself if you end up not wanting to.

Rather than this, make it so when they pass on a help, it will be sent to either of a help channel (a,b,c,d,e). If noone responds to the help within 15-20 mins, ping the on-patrol-helpers, if they dont respond, then ping the specific helper role after 25-30 mins. This would minimize pings for both on-patrol helpers and specific lang helpers, because if someone is already there in the help channel they can handle the help instead of pinging anyone

Rather than this, make it so when they pass on a help, it will be sent to either of a help channel (a,b,c,d,e). If noone responds to the help within 15-20 mins, ping the on-patrol-helpers, if they dont respond, then ping the specific helper role after 25-30 mins. This would minimize pings for both on-patrol helpers and specific lang helpers, because if someone is already there in the help channel they can handle the help instead of pinging anyone

I agree with the approach of pings and stuff, but a better solution would be this:

First you also create a claiming system in which a helper can claim a channel, if claimed no more help is to be posted in that channel. The bot can append this to a list which can be a property of the bot variable itself.

Then after that it checks if all channels are claimed or not, and then picks a channel. The second the helper has finished helping someone you can unclaim the channel which removes the channel ID from the list.
This way the bot also doesn't interfere / ping in the middle of a helper talking bigbrain stuff to members.
Also let mods claim and unclaim help channels cuz yes

Closing as this system isn't used anymore.


freestyle project: use build parameter as resource

I was a bit surprised to see that variable interpolation does not work for locking resources in a freestyle job. I'ld like to create a mutex around a build parameter value that can be specified by multiple jobs (the value is not known upfront so i cannot hardcode it as resource labels).

In a pipeline job this seems trivial with something like, is there a limitation that this does not work for freestyle jobs?
    lock("${env.NODE_NAME}-exclusive") {
        //...
    }

It's just not implemented - Many things that are trivial in pipeline need special handling in Freestyle jobs... There is an open pull request(#33) to add this feature, though.

Hello, my life depends on this feature. OK, perhaps it's a bit of exaggeration, but I can't solve my issue otherwise. What would it take to make it work?


Add InfluxDB support

Enhancement summary
At the moment, to configure Telegraf on EOS devices using AVD, we have to add all the configuration in the eos_cli field.
An improvement on this, if the user is knowledgable enough, is to build a custom eos_config_cli template that will generate the configuration.
The enhancement request is to have eos_design functionality to generate the configuration for Telegraf to stream to InfluxDB.
Which component of AVD is impacted
eos_designs
Use case example
To configure Telegraf on EOS devices to stream to InfluxDB.
Describe the solution you would like
The desired solution would :

Allow for Telegraf configuration to be defined in group_vars yaml definitions
eos_designs would pick up these definition and generate the corresponding eos_cli_config_gen structured_config
eos_cli_config_gen would generate the corresponding configuration for EOS devices

Nice to have:

eos_validate_state would verify that Telegraf is running as expected on EOS devices, when such definitions are defined in structured_config

Describe alternatives you have considered

Adding configuration under eos_cli. This solution is not in line with defining the configuration is a structured format.
Custom eos_cli_config_gen to generate the configuration . This solution is not portable to other users, and would require each user to manually add it. Further more, it is not in line with the strategy to capture as much intended state through eos_designs. It does not allow for future development example : eos_validate_state checking telegraf state.

Additional context
No response
Contributing Guide

[X] I agree to follow this project's Code of Conduct

Thank you for taking this on yourself. Please create separate PRs per role. Easiest to start with eos_cli_config_gen.


Add and use the govuk_taxonomy_helpers gem

Added the govuk_taxonomy_helpers gem. We were then able to replace some
existing methods with a method from the gem.
Trello card: https://trello.com/c/PBIEgMMB/520-rummager-cleanup-use-new-taxonomy-gem
Paired with @MatMoore

Bumped this to v0.1.0 of the gem.

We're going to get to this PR next week. Closing in the meantime.


.enabled handling

My apologies, I wanted to make a pull request from your branch to my fork, not vise-versa 😅


FunctionOperatorComposition Lipschitz constant

closes #531

notice that I opened #559 to address the general behaviour of the Lipschitz constant.

we need the same for LeastSquares and also when we have a weight (see PR #553 )

without weight --> L = 2c||A||^{2}
with weight ---> L = 2c||weight|| * ||A||^{2}


Left Sidebar Expandable like less.sidebar

Hi,
I want to make my left side bar expandable to right like less.sidebar on-mouse over. I have many nested  chlids or sub menus. Please help me to, how can i do that.
I need it on urgent bases.

What you mean exactly?

Hello @asadiqbalse
We are not sure what your request is exactly. Please elaborate on the issue if you can.
Please close this issue if you have already found a solution. Thanks!


Issue 37

Fixes #37
Made changes that allows for the following routes:

/stats/user/:user now returns { numWins, numRaces, races }. numWins and numRaces are integers, while races is an array of race documents that correspond to each race that the given user participated in.
/stats/race/:id returns { title, date, difficulty, numParticipants, timeToSolve, winner }. This route takes an ID that can be found in the return of the /stats/user call.

Actually I just realized the 'races' from /stats/user aren't the full race document, they only have the object ID corresponding to each race. I can change this in a little to make this the full race info.

Sorry, I've been swamped with homework for another class for the past two days. Looks good to me!


Missing cloudwatch:DescribeAlarmHistory in serverless function Policy List

Description:
We have a lambda that requires cloudwatch:DescribeAlarmHistory and we want to use sam template for our lambda. However, DescribeAlarmHistory is not one of the available policies.
Steps to reproduce the issue:
Pull request https://github.com/awslabs/serverless-application-model/pull/1264

Is there a reason that your application requires such a specific SAM Policy Template instead of using an IAM Policy object? Arbitrary policies can be assigned to Functions, as you can see in some of the example applications.


Remove contract bug

Problem
If you try to remove a contract from the account in a folder where flow.json doesn't exist you get a crash.
flow accounts remove-contract FungibleToken --signer test -n testnet
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x10 pc=0x1027bcf40]

goroutine 1 [running]:
github.com/onflow/flow-cli/pkg/flowkit.(*Account).Address(...)
	github.com/onflow/flow-cli/pkg/flowkit/account.go:40
github.com/onflow/flow-cli/pkg/flowkit.NewRemoveAccountContractTransaction(0x0, 0x16dd979ee, 0xd, 0x1400047ede8, 0x1400066fab8, 0x102a8a5c0)
	github.com/onflow/flow-cli/pkg/flowkit/transaction.go:89 +0x20
github.com/onflow/flow-cli/pkg/flowkit/services.(*Accounts).RemoveContract(0x1400023b8c0, 0x0, 0x16dd979ee, 0xd, 0x0, 0x0, 0x0)
	github.com/onflow/flow-cli/pkg/flowkit/services/accounts.go:309 +0x54
github.com/onflow/flow-cli/internal/accounts.removeContract(0x1400009b180, 0x1, 0x5, 0x1031ea528, 0x1400023de20, 0x0, 0x0, 0x102bec043, 0x4, 0x0, ...)
	github.com/onflow/flow-cli/internal/accounts/contract-remove.go:58 +0xac
github.com/onflow/flow-cli/internal/command.Command.AddToParent.func1(0x103a09ce0, 0x1400009b180, 0x1, 0x5)
	github.com/onflow/flow-cli/internal/command/command.go:116 +0x2fc
github.com/spf13/cobra.(*Command).execute(0x103a09ce0, 0x1400003c0b0, 0x5, 0x5, 0x103a09ce0, 0x1400003c0b0)
	github.com/spf13/cobra@v1.1.3/command.go:856 +0x1d0
github.com/spf13/cobra.(*Command).ExecuteC(0x14000123180, 0x140004bff10, 0x1, 0x1)
	github.com/spf13/cobra@v1.1.3/command.go:960 +0x258
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.1.3/command.go:897
main.main()

This error is because ByName in Accounts() does not return err when it fails and then it is easy to forget to check it.


Add support for Keycloak scaling and setting resource limits

Added support for the following options:
KC_INSTANCES - number of KC instances
KC_CPU_REQUESTS - minimum cores per KC pod, defaults to 0
KC_CPU_LIMITS - maximum cores per KC pod, defaults to 1
KC_MEMORY_REQUESTS_MB - minimum memory per KC pod in MB, defaults to 1024
KC_MEMORY_LIMITS_MB - maximum memory per KC pod in MB, defaults to 1024
KC_HEAP_INIT_MB - initial heap space size
KC_HEAP_MAX_MB - max heap space size
KC_METASPACE_INIT_MB - initial meta space size
KC_METASPACE_MAX_MB - max meta space size

Looks like the KC pod failed to start in time, possibly due to the default CPU limit (1 cpu) which might be too low.
I re-based on main and I set the limit to 4 CPUs for the GHA environment. Lets see if it helps.

@kami619 I have added options: KC_CPU_REQUESTS and KC_MEMORY_REQUESTS_MB for specifying the lower bounds of KC pod resources. By default the CPU request is set to 0 which should allow us to schedule KC pods in resource-restricted environments like GHA.


link attempt and cli docs to the same place

referenced in https://reference.garak.ai/en/latest/basic.html (to https://reference.garak.ai/en/latest/generated/garak.cli.html) but also https://reference.garak.ai/en/latest/cli.html

fixed in a7ba1b5b3eca25ae613ec6a397999056aca50022


[1.12] How do I charge tools?

It says "FU", what kind of energy is this? RE or FE with are used in very popular mods doesn't seem to work.

These Tools support Redstone Flux, Forge Energy and Tesla.
I can charge them in AA Energizer and RFTools Powercell.
Have you installed Energy Upgrade?

Yes I've installed the energy upgrade and it has 0 energy. Then I tried all kind of charge packs from Industrial Craft 2 that works absolutely fine with my Nano armor but the tools won't get charged.

Are you kidding?
I told you before that RF, FE and Tesla are supported.
And you tried IC2 energy?


Account Switcher - Discord Source - [Issue Report]

wrong url

download here: https://github.com/l0c4lh057/AccountSwitcher/blob/master/AccountSwitcher.plugin.js


Certain actions are getting stuck

Type: Bug
I have started noticing this after upgrading to 1.96, running on macOS 15.2.
Observed the following:

After using VSCode a while, git gets stuck
In a Jupyter notebook, restarting a kernel gets stuck
renaming a python file, and auto updating import statements gets stuck

In all cases the progress indicator keeps spinning (see screenshots).
If I use "Developer: Reload Window" from command palette I can get out of this state, things work for while, and then back to being stuck.

VS Code version: Code 1.96.2 (Universal) (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Darwin arm64 24.2.0
Modes:

System Info

Item
Value

CPUs
Apple M4 Max (16 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
2, 2, 3

Memory (System)
64.00GB (9.65GB free)

Process Argv
--crash-reporter-id 4736207e-5a8b-4f60-9cfc-365cf283c61c

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

debugpy
ms-
2024.14.0

pylint
ms-
2024.0.0

python
ms-
2024.22.0

vscode-pylance
ms-
2024.12.1

jupyter
ms-
2024.11.0

jupyter-keymap
ms-
1.1.2

jupyter-renderers
ms-
1.0.21

vscode-jupyter-cell-tags
ms-
0.1.9

vscode-jupyter-slideshow
ms-
0.1.6

material-icon-theme
PKi
5.16.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31179979
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

I also noticed this, for me the source control keeps spinning.
Testing with Extension Bisect this seems to be caused by pylance.
Reloading the window also fixes this for me for a short while

I'm experiencing something similar with Git / Source Control getting stuck frequently and guaranteed to get stuck after the first commit. The commit is persisted on Window reload, so it gets stuck somewhere after calling git commit.

@TiemenSch please can you filed a separate issues as it's not related to Jupiter/pylance extension

@DonJayamanne I highly appreciate your work, but the windows freezing /endlessly loading does not seem to restrict itself to a particular language or extension. I'm missing the reason for a Pylance scope versus a "source control" scope when reviewing the comments. I'm happily corrected though.


Support deployment in Public cloud

all nodes have public Ip
loadbalancer for the kube-apiserver

(See https://github.com/outscale-mdr/osc-k8s-rke-cluster/actions/runs/2745246478 for run proof)

See success of update https://github.com/outscale-mdr/osc-k8s-rke-cluster/actions/runs/2977682512


Figure out a better type during bitcast of a scalar to a vector

As noted in https://github.com/CraneStation/cranelift/pull/1120#discussion_r335156013, when moving a scalar value (I32 or I64) to a vector register in x86, the destination must be a a I64x2 due to typing restrictions that ensure vectors have more than one lane. This may be rather confusing when looking at CLIF IR because the intent of that move (using the bitcast instruction) is to zero out the upper bits and only load the lower bits using the scalar value--it's more a I128x1 than anything else.
There are several options here, some of which are:

leave as-is with I64x2 and remove the TODO comment
change the typing restrictions to allow I128x1
use a different CLIF instruction altogether
etc.

Is this still a relevant issue with the new backends @abrown?

Nope, closing.


Kafka Connect metrics NPE prevention

Summary:
When a worker is started up but hasn't setup the assignmentSnapshot it
is possible to throw a NPE. This happens in our environment as we have a
custom reporter running every 10 seconds. This change prevents that null
pointer from happening

this was resolved by #7652


FEAT: 0.13.0. Added aarch64 and osx

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@wolfv @jakirkham This recipe builds zig using the upstream binary distribution to compile itself. Both native builds (at least) can use CMake from source, they take about 2x longer. I kept that option in the recipe (using and environment flag to switch to it)
linux-ppc64le is very difficult to get going, I tried several approaches:

Build with CMake native (on Travis)
Build with upstream bootstrap native (on Travis)
Build cross-compiled CMake x86_64->ppc64le with qemu
Build cross-compiled with upstream binary
They all fail for various reasons, oddly the upstream binary does not seem to even run on Travis.

win build is even worse
So, I'd like to merge this PR if you approve (I'll try not to modify it

@pavelzw FYI

Hi @MementoRC - excellent stuff! I am wondering what needs to be done for osx-arm64? :)

I honestly don't know either. Maybe we can ask @andrewrk .
From a selfish perspective I am more interested in osx-arm64 then ppc64le (which is probably the least used platform on conda-forge) :)
By the way, we had some users build some examples with zig for pixi in the "prefix" Discord: https://github.com/kassane/zig-sdl-pixi-sample
Hopefully we can move that to the conda-forge build of zig soon :)

It'd be great if he can take a look and correct the recipes. I left some issues on the repo, but no hints or feedback came trhough. I do admit that I must be missing some fundamentals about zig, this is by far the hardest recipe I worked on. I mean there are at least 4 ways of building it between bootstrap/cmake and native/cross - though, I suspect the cross zig may not use the existing cross-environment

Hopefully we can move that to the conda-forge build of zig soon :)

What do you mean? pixi is already a conda-forge package

Yes, but the example is using ziglang from PyPI (which is a repack of the official binaries into wheels).

https://github.com/kassane/zig-sdl-pixi-sample/blob/d821a61def66fe278225536ed5ff0d05d27cc132/pixi.toml#L17-L18

He could already use 0.13.0 from conda for the few arch, right? just as a test. Are you part of a zig community? are you in touch with Andrew?

Nope, I am just a conda-forge enthusiast :)

Hello, I have been pinged.
I have not taken the time to read the patch, but I highly recommend to use the standard cmake build process for building Zig from source. Using a prior zig version to build itself is often useful for developers, but it is a less robust way to obtain a build for users, and will sometimes fail, or sometimes produce incorrect results, when breaking changes are made to the compiler.
On the other hand, the standard cmake build process will always work correctly, every time, for every commit.

@andrewrk Cool, thank you for the diligent reply. We took the approach of using the binary distribution as our "bootstrap", but we will revisit the CMake build (it's jusr quite slower) based on your input.
We are having extreme difficulties with the windows build (cmake, msvc/clang/gcc or zig) and the ppc64le build and would love to take a look at your build recipe, so far none of the solution works (bootstrap, native, cmake or zig combination). We have PRs that attempt to look at each building procedures
We'll go back to the drawing board and try to ping you astutely when we feel stuck. Thank you

Feel free to file an issue on the ziglang/zig repository if you encounter problems with the standard build process. That will be a productive place to troubleshoot.

I posted an issue a few days ago : https://github.com/ziglang/zig/issues/20335 - since you have a binary distribution for PPC64LE, I must be missing something - though the binary distribution does not run on the Travis runner that I have tried

sorry for the delay @MementoRC
I was a bit "offline" the past few weeks .. thanks for moving this forward
I am starting now to check all my github notifications XD

It looks a bit messy right now. we're close on osx-arm64, but struggling with ppc64le and windows


[AIRFLOW-2534] Fix bug in HiveServer2Hook

(I'll be waiting on Travis to finish successfully before commenting here)
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title.

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

HiveServer2Hook.get_results is overwriting records when multiple sql statements are passed. This might be superflous when the first statements are just SET, but in principle we want to check if that's also the case. This PR addresses that, plus it refactors some existing Python code.
Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

This PR modifies existing methods. The current test suite should catch regressions.
Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[x] In case of new functionality, my PR adds documentation that describes how to use it.

No new functionality added.

Code Quality

[x] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #3432 into master will decrease coverage by <.01%.
The diff coverage is 7.89%.

@@            Coverage Diff             @@
##           master    #3432      +/-   ##
==========================================
- Coverage   76.57%   76.57%   -0.01%
==========================================
  Files         203      203
  Lines       15028    15034       +6
==========================================
+ Hits        11508    11512       +4
- Misses       3520     3522       +2

Impacted Files
Coverage Δ

airflow/hooks/hive_hooks.py
63.96% <7.89%> (-0.24%)
:arrow_down:

airflow/models.py
87.35% <0%> (+0.04%)
: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 11e670d...70b00d3. Read the comment docs.

Since CI is green, adding new tests (they were not present).
I will squash once CI is green.

@yrqls21 I'm not sure I solved it :)
Python 2 tests fail. Is the library compatible with 2?
I think Thrift has some issues of sort (or impyla). I'll try to dig into it.

@gglanzani as far as I can recall, it is that impyla( even the latest version) want thrift <=0.9.3. However the new hmsclient we use in HiveCliHook cannot work with thrift <0.10.0 ( this part I cannot be 100% sure, what I have is that people providing solution saying upgrading it would solve the problem and it indeed solve that problem).

@Fokko Might it be an idea to use PyHive by Dropbox instead of impyla?
From some basic testing it seems to offer the same impyla API, while being more actively maintained.

@gglanzani Could you do the debugging on your own Travis instead of Airflow's travis?  If you open a travis on your own account, it is free.

Hi,
I've rebased and fixed the issues. CI is still not green, but not for issues related to my code (one test is Kubernetes, the other fails after 2 minutes for a permission error on a pandas wheel).
You can see all green Python 2 CI in my Travis here.
@Fokko Can you confirm?
@yrqls21 I've switched impyla for pyhive, and now Python 2 works (updated to Thrift 0.3.0 might have helped as well).

Please make a note of switchi g impyla to pyhive in the upgrade docs. They were not 100% interchangeable we found out in the past.

It used to be that Pyhive was failing for sasl and Kerberos which is why the switch was made to impyla if I recall. Reading through Pyhive GitHub issues it seems fixed.

@artwr correct, but I also recall that Airbnb had to make some changes to some of their code after the switch to impyla. This wasn’t caught by any of the tests at the time, although we test more extensively now

@bolkedebruin Yes, I'm also fixing the handling of Decimal and Timestamp in PyHive (see here).
Hopefully Dropbox' maintainers will be able to merge. Otherwise @Fokko has his forking tools (🍴 ) ready!

@yrqls21 I don't have merge power :)
Anyhow: we're waiting on a couple of PyHive improvements (if they don't happen by next week we'll probably fork). So: let's go ahead with your PR first, I'll rebase against master later.

@gglanzani SGTM, thank you. Let me know if you have more comments on my PR, plan to merge it tomorrow with help of @aoen

@yrqls21 Mainly: it works with Python 2, and is a cleaner code base. Also Dropbox seems (emphasis on seems) a bit more involved there.
@laserson (who contributed a lot to Impyla especially at the beginning) seems not be active in the repo anymore, and @wesm, who also contributed a lot, has since left Cloudera.
The project went without commits (besides a bump) for more than a year, while the number of issues is growing.

Hopefully the PR https://github.com/dropbox/PyHive/pull/219 will be merged quickly and there will be a new release. This will make PyHive fully compatible with Airflow again since we're using SQLAlchemy 1.2.x in Airflow. I'm fine with merging this PR first and then do a quick follow up PR when the Dropbox PR has been merged.

Hey guys, I'm happy to merge dropbox/PyHive#219 and cut a release, I've just left one comment on the PR

@gsilk Thanks! I will update and rebase once PyHive 0.6.0 is out :)

You should be good to go :)

Awesome! https://pypi.org/project/PyHive/

@gsilk @fokko done

Is there anything else on my end that's blocking at this point?

@gsilk Hi Gabriel, no nothing, thanks! A
ll the tests are green, also the ones that previously were not running as Impyla wasn't able to run under Python 2 :)


Regular Dependency Bump

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (50bdf21) compared to base (59b107b).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #36   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          419       419
  Branches        89        89
=========================================
  Hits           419       419

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


new endpoint:  /episodes/byguid

Need an endpoint to satisfy this issue in the namespace:
https://github.com/Podcastindex-org/podcast-namespace/issues/352

Feed + guid, but yea 👍

This endpoint exists here:  https://api.podcastindex.org/api/1.0/episodes/byguid?guid=PC2083&feedid=920666


Installation failing for Ruby 3.0

Seems that the libmspack module is failing on all Ruby 3.0 builds. This is important to fix. @alexeymorozov can you have a look?
Here's the trace from Metanorma:
https://github.com/metanorma/metanorma-itu/pull/273/checks?check_run_id=1932180288
  /Users/runner/work/metanorma-itu/metanorma-itu/vendor/bundle/ruby/3.0.0/gems/libmspack-0.1.0/ext
  /Users/runner/hostedtoolcache/Ruby/3.0.0/x64/bin/ruby
  -I/Users/runner/hostedtoolcache/Ruby/3.0.0/x64/lib/ruby/3.0.0 -rrubygems
  /Users/runner/work/metanorma-itu/metanorma-itu/vendor/bundle/ruby/3.0.0/gems/rake-12.3.3/exe/rake
  RUBYARCHDIR\=/Users/runner/work/metanorma-itu/metanorma-itu/vendor/bundle/ruby/3.0.0/extensions/x86_64-darwin-19/3.0.0/libmspack-0.1.0
  RUBYLIBDIR\=/Users/runner/work/metanorma-itu/metanorma-itu/vendor/bundle/ruby/3.0.0/extensions/x86_64-darwin-19/3.0.0/libmspack-0.1.0
  rake aborted!
  ArgumentError: wrong number of arguments (given 2, expected 1)
  /Users/runner/work/metanorma-itu/metanorma-itu/vendor/bundle/ruby/3.0.0/gems/rake-12.3.3/exe/rake:27:in
  `<main>'
  Tasks: TOP => default => x86_64-darwin/liblibmspack.bundle =>
  x86_64-darwin/cabc.o => x86_64-darwin
  (See full trace by running task with --trace)

  rake failed, exit code 1

  Gem files will remain installed in
  /Users/runner/work/metanorma-itu/metanorma-itu/vendor/bundle/ruby/3.0.0/gems/libmspack-0.1.0
  for inspection.
  Results logged to
  /Users/runner/work/metanorma-itu/metanorma-itu/vendor/bundle/ruby/3.0.0/extensions/x86_64-darwin-19/3.0.0/libmspack-0.1.0/gem_make.out

  An error occurred while installing libmspack (0.1.0), and Bundler cannot
  continue.
  Make sure that `gem install libmspack -v '0.1.0' --source
  'https://rubygems.org/'` succeeds before bundling.

  In Gemfile:
    metanorma-itu was resolved to 1.2.13, which depends on
      metanorma-standoc was resolved to 1.8.3, which depends on
        metanorma-plugin-datastruct was resolved to 0.1.1, which depends on
          isodoc was resolved to 1.5.1, which depends on
            metanorma was resolved to 1.2.5, which depends on
              fontist was resolved to 1.8.6, which depends on
                libmspack

Successfully installed gems, including libmspack, with upgrade of rake from v12 to v13, see Changelog.
Though fontist is still needed to do the same fixes in its code. I mean changes on keyword arguments in Ruby 3.0. Will continue.

Released in v1.8.7 🚀
Please note that rake should be updated to v13 anywhere fontist is used with Ruby 3.0.

Thanks!

Have updated to rake v13 throughout metanorma


[Delta-Iceberg] Fix delta iceberg clone script

Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[X] Other (Delta-Iceberg)

Description
Building UniForm depends on cloning and then building iceberg at a particular commit, in order to apply patch files. It starts this by cloning iceberg master branch. This has been renamed to main, and so we need to update our script to use main accordingly, else it fails to build and tests fail.
How was this patch tested?
Local build.
Does this PR introduce any user-facing changes?
No

lgtm !


Added Prismic

Opened https://github.com/robchahin/sso-wall-of-shame/pull/502 using the new format and current pricing.
This PR can probably be closed.


Fix: Resolve more errors so the cli runs

resolve package name errors (openapi_client -> pieces_os_client)
generally make the cli work from any location after installation (some things were pointing to local, within-repo files which cased issues)
change entry point so it matches
package db into the build
make the db be usable from within site-packages/pieces
fix validation errors on Application deserialization

Yo @hal-8999-alpha here are the changes that I've made to the cli. I'm merging it into Sam's PR branch for now. I'll update the README.md shortly after with recommendations on how to build/run it for reference.


QSDownloads: support Safari download folders containing spaces.

[NSURL URLWithString:downloads] fails when downloads contains spaces. Apparently the solution is to percent-encode the string.

Nice, this is a good fix to have. I'm looking at the code now - I can't get:
NSDictionary *safariPrefs = [defaults<EMAIL_ADDRESS>
to work for me. It just returns nil every time. I think it has something to do with sandboxing (I confirm that the key exists at defaults read com.apple.Safari DownloadsPath).
Also, looking at Firefox, it seems it has its own download setting in ~/Library/Application Support/Firefox/Profiles/XXXXX.default/prefs.js -> browser.download.dir. Seems like each browser may well have their own path.
To avoid us trying to figure out every browser's downloads dir, I suggest we have a setting in Quicksilver to set the downloads folder. A couple of options:

Set it using defaults write com.blacktree.Quicksivler downloadsPath XXXX (easiest)
Add a preference to Quicksilver Prefs > Extras (fairly easy)
Add it as a 'source option' for the 'Latest Download' proxy object catalog source (hardest).

I think it has something to do with sandboxing (I confirm that the key exists at defaults read com.apple.Safari DownloadsPath).

Ah, alas. :-/
This was more of a drive-by fix, so unfortunately I don't think I can contribute more work to it. But feel free to take it and run with it!

I think the right way to fix this is to use -[NSURL fileURLWithString:]. I've pushed straight to master. Thanks for spotting the bug!


feature: nodejs docs

hey @0xneves all nodejs documentation is already added!
PR: https://github.com/blockful-io/swaplace-contracts/issues/139
closes #139

hey @0xneves the branch is already up to date! i checked it!

hey @0xneves the branch is already up to date! i checked it!

Yoo @luislucena16, your fork might not be up to date with the mainstream. Check the TL;DR, it's on the top, and yours is on the bottom.
I did a diff checker  where you can see the differences.

hey @0xneves I think that's it, I've checked how it is in main

It is still different from the main branch :(
Don't just copy-paste the tldr into your commit. Try copying the main branch's readme, then add your changes to it.

hey @0xneves done! check it


Logger::log(message, $priority) got exception : "$priority must be an integer > 0 and < 8;"

When see-ing the Logger const :
    const EMERG  = 0;
    const ALERT  = 1;
    const CRIT   = 2;
    const ERR    = 3;
    const WARN   = 4;
    const NOTICE = 5;
    const INFO   = 6;
    const DEBUG  = 7;

that 0 = EMERG must be included. it means $priority >=0 ?

oh, it works for 0, but the exception need to be updated ?

so, the exception should be :
                '$priority must be an integer >= 0 and < %d; received %s',

I created PR #7239 for it ;)


win11  RuntimeError: Ninja is required to load C++ extensions

hi, please follow the install steps:
First, this extension depends on ComfyUI-3D-Pack, please install it if not, and make sure it works well:
stop ComfyUI if it is running
goto ComfyUI/custom_nodes dir in terminal(cmd)
git clone https://github.com/MrForExample/ComfyUI-3D-Pack
cd ComfyUI-3D-Pack
run install_windows_portable_win_py311_cu121.bat
(Don't start ComfyUI at this moment)
Then, install this extension:
git clone https://github.com/jtydhr88/ComfyUI-InstantMesh
cd ComfyUI-InstantMesh
run install_windows_portable_win_py311_cu121.bat
Start your ComfyUI.

这样就好了

hi, please follow the install steps: First, this extension depends on ComfyUI-3D-Pack, please install it if not, and make sure it works well:
stop ComfyUI if it is running goto ComfyUI/custom_nodes dir in terminal(cmd) git clone https://github.com/MrForExample/ComfyUI-3D-Pack cd ComfyUI-3D-Pack run install_windows_portable_win_py311_cu121.bat (Don't start ComfyUI at this moment) Then, install this extension:
git clone https://github.com/jtydhr88/ComfyUI-InstantMesh cd ComfyUI-InstantMesh run install_windows_portable_win_py311_cu121.bat Start your ComfyUI.

跟这个没关系

ok

ok

然后现在是这个报错

hi, please follow the install steps: First, this extension depends on ComfyUI-3D-Pack, please install it if not, and make sure it works well:
stop ComfyUI if it is running goto ComfyUI/custom_nodes dir in terminal(cmd) git clone https://github.com/MrForExample/ComfyUI-3D-Pack cd ComfyUI-3D-Pack run install_windows_portable_win_py311_cu121.bat (Don't start ComfyUI at this moment) Then, install this extension:
git clone https://github.com/jtydhr88/ComfyUI-InstantMesh cd ComfyUI-InstantMesh run install_windows_portable_win_py311_cu121.bat Start your ComfyUI.

我是完全照着这个来的

hello，确认一下，本地安装Visual Studio Build Tools这个工具了吗
?
我在InstantMesh本身的库里建了个ticket也提到这个了https://github.com/TencentARC/InstantMesh/issues/3

请参考https://github.com/jtydhr88/ComfyUI-InstantMesh/issues/6

 这样就好了

对我不管用，我不知道为什么（哭）


[Feature Request]: express route gateway for Hub Deployment

Description
current express route gateway is not for virtual wan hub, would be nice to have a module for this use-case.

Let's wait for the solution for Firewall, which has a similar issue, see #2457


document is not defined in onDestroy()

the onDestroy() method uses SSR and thus doesn't have the document defined. Needs to be removed.

please see issue https://github.com/LottieFiles/svelte-lottie-player/issues/7 for reference on how to get around the document not found error


No Hover option  on MindSpace Logo in any of the pages in the website.

#Problem||Feature to be Added :
In any of the other pages of the website , there is no option to hover on the MindSpace Icon on the top to navigate back to the home page.
.
#Solution:
The hover with link functionality on the MindSpace logo on any of the pages of the website would enable the user to navigate directly to the home page without clicking on the back/previous page button in order to return to home page .
#Request
Please assign me this task under GSSOC 24

@Ankush-ai I would like to work on this issue in GSSoC'24. Please assign it to me. Thanks!

I am interested in working on this issue ,I will add the hover effect to mindspace logo and can also make changes if any required

Please assign me this task under GSSOC 24.
Thank you


entc/gen: use gotype pkgname as alias in case it does not match pkgpath

Fixed https://github.com/ent/ent/issues/2685

Maybe add a test?

Maybe add a test?

Definitely, working on it. See https://github.com/ent/ent/issues/2685#issuecomment-1165939830 😎

Thanks for the review @rotemtam


Fix mobile layout

Bug Report
Issue:
The layout is broken in mobile landscape mode.
Expected Behavior:
The interface should be fully responsive and functional on mobile devices, including landscape orientation.

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

Mobile Support Status:

Mobile users attempting to access Visio
Current responsive design is not functioning properly

Action Plan:

Immediate Priority:

Deploy a basic functional mobile version ASAP

Long-term Goal:

Develop and implement a mobile-first user experience
Optimize interface specifically for mobile users


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/211 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit af618ce:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


can't build rc tag?

I've enabled build from source in config and I'm attempting to get my server to update to https://github.com/LemmyNet/lemmy/releases/tag/0.18.0-rc.6 but both with and without manual it can't seem to find this version.

It would help if you followed the issue template :)

==== Docker Information ====
Detected runtime: docker (Docker version 24.0.2, build cb74dfcd85)
Detected compose: docker compose (Docker Compose version 2.19.0)
   Runtime state: OK

==== System Information ====
MEMORY:                total        used        free      shared  buff/cache   available
Mem:           2.9Gi       1.3Gi       203Mi        47Mi       1.4Gi       1.4Gi
Swap:             0B          0B          0B

KERNEL: 6.3.8-arch1-1 (x86_64)
SHELL: /bin/bash
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

==== Lemmy Easy Deploy Information ====
Version: 1.1.0
Integrity:
    c8d59317549f098f04a6d333b4cf7fd0c222ad89004f37f18bde5800d469d964  ./deploy.sh
    1e9b0c0988998dcc33cb0fbfdb0e1679229424e724f898b797380adc7d102446  ./templates/Caddy-Dockerfile.template
    c1202e70662dd2228da36a35a0f38ec8fc81bec8964d7315d02e8671a58dd7d7  ./templates/Caddyfile.template
    7754ef7e8aa7e925becfcbbda0f873387533397a0756405741f4f4b9eb7f7253  ./templates/cloudflare.snip
    1df196524e8d55a4be93b5bf401669d61b372c4f6f7670da83ab1947631fd0ed  ./templates/compose-email.snip
    839ce56196227e2bac2291ee045ef95bc6af9c9706396352f39cb0812754c5c1  ./templates/compose-email-volumes.snip
    257270c0a1d59b7b2033b516c21dda10367009d5c66f371b94da39d42c692a1f  ./templates/docker-compose.yml.template
    308b8a122ee03cb9f5279fc2ad79663b0bffb2ed2a4042b96f678715cc997914  ./templates/lemmy-email.snip
    8f25408461972b9b66ee3c4d3f6430e2e1eaa950394d2d8b7e3d1287fe0d8f07  ./templates/lemmy.hjson.template

==== Settings ====
BUILD_FROM_SOURCE=true
CADDY_HTTP_PORT=80
CADDY_HTTPS_PORT=443
USE_EMAIL=false
CADDY_DISABLE_TLS=false
POSTGRES_POOL_SIZE=5
TLS_ENABLED=true

==== Generated Files ====
total 44K
drwxr-xr-x  2 0 0 4.0K Jun 22 01:07 caddy
-rw-r--r--  1 0 0   87 Jun 22 10:59 caddy.env
-rw-r--r--  1 0 0 2.1K Jun 22 10:59 docker-compose.yml
drwxr-xr-x 14 0 0 4.0K Jun 22 11:01 lemmy
-rw-r--r--  1 0 0   50 Jun 22 01:03 lemmy.env
-rw-r--r--  1 0 0  479 Jun 22 10:59 lemmy.hjson
drwxr-xr-x  7 0 0 4.0K Jun 22 11:01 lemmy-ui
-rw-r--r--  1 0 0   49 Jun 22 01:03 pictrs.env
-rw-r--r--  1 0 0   37 Jun 22 10:59 postfix.env
-rw-r--r--  1 0 0   51 Jun 22 01:03 postgres.env
-rw-r--r--  1 0 0    7 Jun 22 01:10 version

Ah, this is because they moved the Dockerfile. Did you see this message when you tried to build?
ERROR: Unable to find Lemmy Dockerfile for building
    No such file: ./live/lemmy/docker/prod/Dockerfile

It is likely that Lemmy restructured their build files in a recent update.
If Lemmy Easy Deploy is already up to date, please report this so I can find the correct file path:
    https://github.com/ubergeek77/Lemmy-Easy-Deploy/issues

(This is why my issue template asks you for logs too, btw)
They keep moving this file every release, so I don't have a great way of dealing with it that won't break both release and RC versions.
For the time being, you can try changing this variable to be docker/Dockerfile:
https://github.com/ubergeek77/Lemmy-Easy-Deploy/blob/2b61859a2122cddcf0aaff140b665f0459b8b755/deploy.sh#L362
That gets a build going for me. Not sure if it will finish successfully though. But any build issues are in the Lemmy team's hands now, I only use their Dockerfile.
Let me know if that works!

Yeah sorry about that, I guess I'm just getting burned out from all the Federation issues. And even just deployment issues, without your script I wouldn't even have an instance. I'm not new to hosting or to docker I have 12 other services that I host regularly without issue but the instructions for lemmy are horribly broken, bothddocker and raw build lol.
I had not seen that message but turns out that's because I formatted my version tag incorrectly i was doing rc-6 instead of rc.6 for some reason and as far as I can tell only releases is checked if a version is not specified.
Thank you for the help, the build sadly failed with "failed to receive status: rpc error: code = Unavailable desc = error reading from server: EOF " although given the lower spec nature of this VPS that very well could have been the build running out of memory and killing itself. Guess I'll have to test this on my server at home but even if it did work there I'm not sure how I would then move it to the VPS

All good!
And yes, I don't automatically search for RC versions at all. I don't want people accidentally installing an untested version that breaks their database. Lemmy does a database migration every release, and if things go wrong, it can easily result in the instance breaking with no option to downgrade. So because of that, I only look for "Release" versions, and leave the manual build tags up to whatever the user wants to use.
Not sure about that build error. It could be your VPS, or it could be that they simply haven't finished the Docker stuff yet. I imagine that would be tested pretty late into the RC. I'm testing this on the cheapest VPS my provider offers though, and the build is still running, so maybe yours did get killed after all?
Once they push the Docker images for 0.18 and formally release it, I'll make sure this project is updated to be as seamless as possible!

I actually managed to get it working.  I was able to get it to deploy! Don't know what it got stuck on before but it is possible to deploy that particular RC tag of 18.6
but the site was half broken and logins were not working so i wiped everything and started from blank. now I'm getting database password failures for user lemmy. so perhaps they use a different login for the rc builds or something.
I am going to just give up and go back to release build but that information might be useful to someone else who wishes to try and dig a Little Deeper at it

Thank you very much for testing! This will be very helpful things to know when I'm updating this project to support 0.18

Just as a quick little update to this. Seeing is how I had a malformed configuration I decided to wipe everything again and try again with this RC tag and it has worked. It is now online and running :) lemmy.kitsuna.net is on rc.6 thanks for all the help today lol

You're welcome! Enjoy the RC! I think I'll put up with the websockets spam down here on 0.17.4 for just a little longer 😅


fix(TS): add touchStart to stateChangeTypes

What:
add touchStart to stateChangeTypes
Why:
I made a pull request earlier for https://github.com/paypal/downshift/issues/508, but missed one place that needs to add touchStart

How:

Checklist:

[ ] Documentation N/A
[ ] Tests N/A
[X ] Ready to be merged

[ ] Added myself to contributors table N/A

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Low overlap stereo cameras

I am trying to run VR datasets with low overlap between the stereo fisheye cameras. And while monocular, monocular-imu seem to track properly, stereo fails likely due to the pre rectification step that occurs when loading datasets. Do you think there can be a reasonable way of making Snake-SLAM run on these datasets without reworking the stereo matcher? SpectacularAI/HybVIO#22 has the same issue
Example frame with overlap in green:

If interested to reproduce the issue you can find the example dataset I am trying to run here.
Since these datasets use radial-tangential8, a small modification to saiga is needed to add the extra k3,k4,k5,k6 parameters.

You are right, stereo fisheye is not supported out of the box. It would be definitely more difficult to implement than standard pinhole stereo, because finding the stereo matches is a lot harder. For "soft" fisheye cameras the current system could still work if the rectification gives decent results.
I would suggest you try out the rectification and the stereo matching by its own to see if works well. Unfortunately I don't have much time to try stuff out myself. So I wish you the best of luck with your project :).


Add reveal.js-menu as submodule in /docs folder

create a submodule with reveal.js-menu

warning: use https submodule (not ssh) for making GitHub pages happy.
It will initialise the submodules without problems.

git submodule add https://github.com/denehyg/reveal.js-menu.git docs/revealjs-menu

pick a released version, take a look at https://github.com/denehyg/reveal.js-menu/releases to select a valid tag

cd docs/revealjs-menu && git checkout tags/2.1.0


hey i want help

hey so i am making a mcc recreation and i have no idea how it works so if u can help me contact me on discord
Matic Mahx#9461
plsss

Hello!
This library is a wrapper to make interacting with the MC Championship API easier in Python. Unfortunately, it doesn't directly interact with Minecraft and isn't a Minecraft server plugin or similar, so I don't think I can help you with your request.


Bugfix/parallel matrix artifacts copy

closes #923

closes #923

To give some context, producer is the one who check if artifact should be copied:
https://github.com/firecow/gitlab-ci-local/blob/90e5f2deea3dbd60c9bfc1a27ca59062a6c923de/src/producers.ts#L6-L38
There are two main cases:

one of job.needs or job.dependencies is present, in which case they will contain the baseName of the needed job
non of them is present, in all of the previous job names will be considered as needed


Some issues about feature propessing.

Hi,
Thanks for your paper. Could you please give me some ideas about my confusion?
Firstly, about the [ xyz in block + rgb + normalized xyz ] , the normalized xyz is normalized according to the xyz in block, or the orginal xyz.
Secondly, why you use the [ xyz in block + rgb + normalized xyz ] as inputs, I check the code, and it seems that you just utilize the xyz in block to voxelize and devoxelize. So why still need normalized xyz as input, is that means you make use of the normalized xyz as a part of features?
Thirdly, what happens if I change the coordinates value when I devoxelize [B,C,R,R,R] features? Will it generated a point feature corresponding to the changing?
Best Regards

Your understanding is correct. Only the coordinates within the block are used for voxelization. All the other dimensions are features.

Thanks for your reply.
There is still one thing that confused me, will the parameters of voxelization and devoxelization join the backward propagation and update parameters?

Thank you so much!


read-only sessions: Move model loading into separate script

When the script is invoked via EASE, one doesn't get any stacktrace. We should move all parts which are unrelated to the workspace import into a separate script. When running externally, we can get the stracktrace, which makes debugging a lot easier.

Resolved with https://github.com/DSD-DBS/capella-dockerimages/pull/275


Matrix-free auxiliary Maxwell solver [barker29/matrix-free-ams]

This implements a matrix-free (or at least "matrix-light") auxiliary space Maxwell solver for high-order Nedelec elements. It uses an (assembled) AMG V-cycle for low-order refined approximations as a replacement for the auxiliary space solves in the auxiliary space framework.
The ideas and algorithm are described here: https://doi.org/10.1002/nla.2348
Run
./ex3p -pa -o 8 --mesh ../data/star.mesh

to see the new solver in action.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#1781
@barker29
@tzanio
@tzanio + @dylan-copeland + @psocratis
01/22/21
⌛due 02/05/21
⌛due 02/12/21

./ex3p -pa -o 8 --mesh ../data/star.mesh

This crashes when I tried the branch out of the box. I think HCURL_MAX_D1D in biliniteg.hpp needs to be increased.

./ex3p -pa -o 8 --mesh ../data/star.mesh

This crashes when I tried the branch out of the box. I think HCURL_MAX_D1D in biliniteg.hpp needs to be increased.

./ex3p -pa -o 8 --mesh ../data/star.mesh

This crashes when I tried the branch out of the box. I think HCURL_MAX_D1D in biliniteg.hpp needs to be increased.

I think HCURL_MAX_D1D should not be too high, because otherwise MFEM will take longer to build. This can be changed for a user who wants to run higher order, but should not be in the master branch.

./ex3p -pa -o 8 --mesh ../data/star.mesh

This crashes when I tried the branch out of the box. I think HCURL_MAX_D1D in biliniteg.hpp needs to be increased.

I think HCURL_MAX_D1D should not be too high, because otherwise MFEM will take longer to build. This can be changed for a user who wants to run higher order, but should not be in the master branch.

I think HCURL_MAX_D1D should not be too high, because otherwise MFEM will take longer to build. This can be changed for a user who wants to run higher order, but should not be in the master branch.

Sure, I agree with this. At least in debug mode can we add an abort message? As it is now it just segfaults

I think HCURL_MAX_D1D should not be too high, because otherwise MFEM will take longer to build. This can be changed for a user who wants to run higher order, but should not be in the master branch.

Sure, I agree with this. At least in debug mode can we add an abort message? As it is now it just segfaults

@psocratis Are you suggesting we change that in this PR? In my view it is a separate issue. Are you saying that since this command line runs (but does not converge) in master it should also work in this branch?

@psocratis Are you suggesting we change that in this PR? In my view it is a separate issue. Are you saying that since this command line runs (but does not converge) in master it should also work in this branch?

@psocratis Are you suggesting we change that in this PR? In my view it is a separate issue. Are you saying that since this command line runs (but does not converge) in master it should also work in this branch?

It is indeed a separate issue, it does not run on master either.  However, since this new matrix-free solver is optimal for high orders, then an example run demonstrating this could be added, and therefore (unavoidably) the MAX_D1D numbers have to be increased. Just so I know ... how much impact in compilation time are we talking about?

@psocratis Are you suggesting we change that in this PR? In my view it is a separate issue. Are you saying that since this command line runs (but does not converge) in master it should also work in this branch?

It is indeed a separate issue, it does not run on master either.  However, since this new matrix-free solver is optimal for high orders, then an example run demonstrating this could be added, and therefore (unavoidably) the MAX_D1D numbers have to be increased. Just so I know ... how much impact in compilation time are we talking about?

@psocratis I'm not sure how much the build time will be affected. We should just experiment and find out. Another issue is memory. If I remember correctly, the original H(curl) PA kernels ran out of memory on the GPU quickly (order 4 or 5) at run time, and then I wrote the shared memory kernels which can go to higher orders, but I think the shared memory kernels can run out of memory at build time if the order is too high. So there are multiple challenges to high order, which may require changes to the kernels other than just increasing the max order allowed. We can experiment with this and see if the order can be increased (probably not much if at all), but for this PR I would be satisfied with order 5 or so, considering the PA kernel issues.

@psocratis I'm not sure how much the build time will be affected. We should just experiment and find out. Another issue is memory. If I remember correctly, the original H(curl) PA kernels ran out of memory on the GPU quickly (order 4 or 5) at run time, and then I wrote the shared memory kernels which can go to higher orders, but I think the shared memory kernels can run out of memory at build time if the order is too high. So there are multiple challenges to high order, which may require changes to the kernels other than just increasing the max order allowed. We can experiment with this and see if the order can be increased (probably not much if at all), but for this PR I would be satisfied with order 5 or so, considering the PA kernel issues.

I thought there may be a broken case, from PR #1761 , depending on mpi_gpu_aware in DeviceConformingProlongationOperator::Mult, but it seems to work in all cases. If you set Device::SetGPUAwareMPI(true); in ex3p and then run with `lrun -M "-gpu", it works fine. I also tested with and without AMGx, and everything is working.

I thought there may be a broken case, from PR #1761 , depending on mpi_gpu_aware in DeviceConformingProlongationOperator::Mult, but it seems to work in all cases. If you set Device::SetGPUAwareMPI(true); in ex3p and then run with `lrun -M "-gpu", it works fine. I also tested with and without AMGx, and everything is working.

This looks great overall, but I'd like to take a closer look and will need a bit more time for the review. Sorry for the delay.

LGTM

Merged in next for testing...

Re-merged in next for testing ...


Allow user to use custom compiler binaries

Usage related changes

User can supply custom build Cairo compiler binaries.
Options flexibility. User can provide any flags specified by Starknet cli.

Development related changes

Cairo->Sierra & Sierra->Casm compilation is now separated.
1-1 flags/options mapping with native cairo cli

Checklist:

[x] Formatted the code
[x] No linter errors + tried to avoid introducing linter warnings
[x] Performed a self-review of the code
[ ] Rebased to the last commit of the target branch (or merged it into my branch)
[x] Documented the changes
[x] Updated the test directory (with a test case consisting of network.json, hardhat.config.ts, check.ts)
[ ] Linked issues which this PR resolves
[ ] Created a PR to the plugin branch of starknet-hardhat-example:

< EXAMPLE_REPO_PR_URL >
[ ] Modified test.sh to use my example repo branch
[ ] Restored test.sh to to use the original branch (after the example repo PR has been merged)

[ ] All tests are passing (for external contributors who don't have access to the CI/CD pipeline)

A PR to the example repo would be useful (which updates the hardhat config there). I am surprised that your pushes did not trigger the workflow on CircleCI, do you need to do something about that? Are you not a member of SpaceShard?

Maybe its related to the last time when my prs weren't ran by CircleCI because I'm Russian.  I remember you had to make a commit for me.


Fixed XIO bug for pre-emption and volume discovery

The cautionary unmount was is now performed earlier so that
prior to attaching a device, the mount table is clear.

This PR fixes an issue found in 0.3.1-RC1 with XtremIO when enabling pre-emption.

The fix was tested to work across all drivers.


Stop using libgdiplus.

It is unsupported.

After a quick investivation, it seems not to be actually used on non-Windows, it is used by the Avalonia.Win32 package. The problem is that it is installed on non-Windows actions for no reason.


Poor performance past 0.2.1

I really should have reported this a while back when I noticed that, but I have been using darkness-0.2.1-all for a while instead of the newer versions due to every version past 0.2.1 cutting my FPS in half.
I decided to do a direct FPS comparison between darkness-0.2.1-all,  darkness-forge-1.12.x-0.4.2, and Hardcore Darkness and here are the results of that.
Unfortunately my FPS on latest version of this is still very bad.
Here is my modpack if you would like the list of mods. I am using the latest forge version of <IP_ADDRESS>60

I did some spark profiling for 0.2.1 and 0.4.2 and something weird is definitely going on.
Here is the 0.2.1 profile and here is the 0.4.2 profile
Whatever the method io.github.yamporg.darkness.asm.EntityRendererHooks.updateLuminance() is taking up over 50% of the client thread in 0.4.2 which would account for my FPS getting cut in half

Seems to be an issue with mod compatibility and hook injection logic. Currently the hook can potentially be injected at multiple points if other coremods insert net.minecraft.client.renderer.texture.DynamicTexture updateDynamicTexture calls in net.minecraft.client.renderer.EntityRenderer updateLightmap.
https://github.com/yamporg/mods/blob/8ee0a09043ff15eae864a85b084a999c6b33c8d6/darkness-forge-1.12.x/src/main/java/io/github/yamporg/darkness/asm/EntityRendererTransformer.java#L45-L86

@TheComputerizer I've published v0.5.0 release with the fix, let me know if the issue is still relevant for you.

Hey @tie:
I have had this issue in the past as well. In my testing with darkness-forge-1.12.x-0.5.0.jar, I have found the issue is no longer relevant. My FPS (when set to unlimited) is upwards of 140, as opposed to 20 fps like it was before.


Does Airflow instantiate task based on historical log or based on current DAG?

Need test.
Scenario:

Run a task today with a templated SQL as an example
Change the SQL of that task, and rerun it tomorrow
Ask Airflow to render the task executed in 1st step and 2nd step
Compare the two, the SQL should be different

Finished testing using QA envs.
Conclusion: Airflow instantiate and render the template of task based on current DAG and operator configuration.


flask_babelex is missing from requirements

After installing the application,
I tried to run it with :
python example/app.py

But crashed with output being :
Traceback (most recent call last):
  File "examples/app.py", line 41, in <module>
    from flask_babelex import Babel
ImportError: No module named flask_babelex

Two occurrences :
 git grep  flask_babelex
examples/app.py:from flask_babelex import Babel
tests/conftest.py:from flask_babelex import Babel

This commit https://github.com/inveniosoftware/invenio-files-rest/commit/55e3d70a2e844955ce3a603591fa90d3f502138d
Seems to remove it, do you know why @lnielsen ?


XdsClient: convert timers to use EE API

I'm doing this to try to make XdsClient depend on fewer things from inside C-core, so that it can be more easily used outside of gRPC.

LGTM, thanks for tackling a piece of the timer migration!


realname and typename are reversed on /user/whois

We will be refactoring the whois endpoint art some point to use the standard user object. No eta yet.

We have updated this now and from version 20150106 whois returns the standard user object.


"Related Content" should be a header like "Data" on reader view of content

Currently it's displayed under data, in the main data list:

It should be it's own heading, as per mockup:

@scottofletcher can you clarify/ further explain this comment from user testing: "Do we need a field for 'Related Methods'? This might just clutter things up - I think it's better if we just capture the methods/tools used in this case and then, if a user is interested, they can go to the methods entry which will have links to related methods. In short: cases should have a field for 'Related Cases', methods should have a field for 'Related Methods', organizations should have a field for 'Related Organizations'."
Maybe we should chat about this in person? I'm not sure if we have the same idea of what related content is supposed to achieve, and this is an important piece to be clear on so we can communicate to users how to properly use this feature.

@jesicarson let's set up a skype call on Slack :)

Hey @jesicarson, I've been thinking about this issue and I don't think we should include 'Methods' and 'Organizations' under the 'Related Content' heading since those fields are part of the data set and so should, technically, be under 'Data'. In fact, 'Methods' is perhaps one of the most important case data fields for comparative researchers. "Related Content" still sounds like it's referring to orgs/methods that weren't directly involved in this case. Are we still going to have Data sub-headings for "Methods and Tools Used" and "Type of Implementing Entity" or are they being replaced with the sub-headings under 'Related Content'?

Hi @scottofletcher. The design decision to highlight related content was exactly for that reason - because methods is likely important to people who are interested. We wanted to put it in a header of its own to call attention to it. It doesn't mean that it's not part of the data or the export, that will all be the same. its only called out in the reader view so people can easily see it. Yesterday I drafted some explanatory text for what related content means in this issue https://github.com/participedia/frontend/issues/572. Check it out and let me know what you think. again, perhaps its the word "related" that's not working?

We ditched related content altogether, closing this.


replace strings buffer with hasher

the buffered value is going into the hasher eventually so write directly to the hasher instead

instead of md5 it would be better if using hash sha256

@H0llyW00dzZ this is only as an extra verification means with object storage – it is not an alternative to the sha256 verification ollama does when pulling models


Add support for Java Gradle and Golang

Description
Hi
I am planning to intergrate this plugin with my service catalog, but it would be useful if we have support for java gradle based projects aswell as golang (go.mod)
Problem Statement/Justification
Extending to java grade and go.mod
Proposed Solution or API
For gradle, we can check the modules. for golang, lets check the go.mod
Alternatives
No response
Additional Information
No response

Hi @Alok650, thank you for your interest.
I have an upcoming version supporting Pom and Gradle files. Go is the next task on the list.
Stay tuned and please report any issues.

@rocha-bruno @Alok650 Java support is now available 🚀

@rocha-bruno @Alok650 Java support is now available 🚀

Thank you for this awesome work!
We will check and give you feedback if we find areas of possible improvements or ideas.

@accezar thank you for adding this functionality. I believe I have found a minor bug though.
In the PomXmlHandler the list of dependencies are determined by result.project.dependencyManagement.dependencies.dependency. However, not all Java projects use the dependencyManagement section, which can result in null pointer issues. Instead, I would suggest something like result.project.dependencyManagement?.dependencies.dependency to check if dependencyManagement is defined, and then adding a second check on result.project.dependencies.dependency. If one/both are populated, their contents can be processed by a shared function to populate the libraries object that is returned.

Thank you @moonfruit85 Can you please open an issue with details and prints if possible? I will take a look.


Find a better way

without using the switch statement in the main.cpp find a better way to do it
Consider a array list : ex

I'll look into it :)


ExecuteSqlCommand when using InMemoryDatabase

I'm trying to execute some raw SQL Update queries. It works with SqlServer, but not with InMemoryDatabase. Is there any way to workaround it with InMemoryDatabase?
Currently it throws following exception:

Result StackTrace:
at Microsoft.Extensions.DependencyInjection.ServiceProviderExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
at Microsoft.Extensions.DependencyInjection.ServiceProviderExtensions.GetRequiredService[T](IServiceProvider provider)
at Microsoft.Data.Entity.Infrastructure.AccessorExtensions.GetService[TService](IInfrastructure`1 accessor)
at Microsoft.Data.Entity.RelationalDatabaseFacadeExtensions.ExecuteSqlCommand(DatabaseFacade databaseFacade, String sql, Object[] parameters)
Result Message:
No service for type 'Microsoft.Data.Entity.Infrastructure.RelationalSqlExecutor' has been registered.

Looks like it's obviously not supported - is it by design, or is it planned to be supported a bit later? Might be there is something that should be configured additionally to make it work?
I'm kind of suspecting there is a little sense to execute raw SQL for in-memory data, but it would be good to have at least some way to mock it.
Or should I use SqlServer provider for such tests with some rollbacking (it would be more like integration tests)? Such raw SQL execution is indeed not will be used everywhere, just in 1-2 places, but these places might be quite critical.

InMemory is a rather simple store designed for simple testing scenarios. There is no SQL query processor and therefore raw SQL APIs are by design out of the scope of what is supported.
We can discuss the priority of improving the exception in triage.
We can also discuss if there is anything we should do differently to help improve testability of these APIs, but my first reaction is that using a real in-memory relational database such as SQLite in-memory mode or creating your own repository abstraction you can easily mock are better patterns tho adopt if your data access code is complex and/or includes provider specific code.

As mentioned, ExecuteSqlCommand is specific to relational database providers (which InMemory is not). If you only install the InMemory provider then this extension method is not available).


Mysql BINARY(16) column not being decoded as uuid::Uuid

Bug Description
According to the sqlx_mysql::types it should have no problem decoded a column of type BINARY(16) using the uuid::Uuid struct given that the uuid feature is enabled.  I am instead getting the error:
35 |           let query = sqlx::query_as!(
   |  _____________________^
36 | |             Self,
37 | |             "SELECT * FROM identities WHERE user_id = ?",
38 | |             user_id
39 | |         );
   | |_________^ the trait `From<JsonValue>` is not implemented for `Uuid`
   |
   = help: the following other types implement trait `From<T>`:
             <Uuid as From<Hyphenated>>
             <Uuid as From<uuid::fmt::Simple>>
             <Uuid as From<Urn>>
             <Uuid as From<Braced>>
   = note: required for `JsonValue` to implement `Into<Uuid>`
   = note: this error originates in the macro `$crate::sqlx_macros::expand_query` which comes from the expansion of the macro `sqlx::query_as` (in Nightly builds, run with -Z macro-backtrace for more info)

Minimal Reproduction
From my Cargo.toml:
serde = { version = "1.0.192", features =  [ "derive" ] }
sqlx = { version = "0.7.2", features = [ "chrono", "mysql", "runtime-tokio", "uuid" ] }
uuid = { version = "1.5.0", features = [ "serde", "v4" ] }

The relevant snippet of my migration:
CREATE TABLE identities (
  user_id BINARY(16) NOT NULL,
  ... other fields ...
  PRIMARY KEY (user_id)
);

The relevant Rust code:
#[derive(sqlx::FromRow)]
pub struct Identities {
  pub user_id: uuid::Uuid;
  ... other fields ...
}

impl Identities {
  pub async fn get(..., user_id: uuid::Uuid) -> ... {
    let query = sqlx::query_as!(
      Self,
      "SELECT * FROM identities WHERE user_id = ?",
      user_id
    );
 }
}

I am not sure what I'm missing here, would love some guidance. Sqlx also has no problem consuming a Uuid as a parameter inside of the query. It's only when decoding it from the query that it raises a problem.
Info

SQLx version: 0.7.2
SQLx features enabled: default, chrono, mysql, runtime-tokio, uuid
Database server and version: MySQL 8.1.0
Operating system: MacOS 12.6.5
rustc --version: 1.72.0

Not a bug. The conversion is supported, but the query macros have no idea you're expecting a Uuid there. The typechecking is a little too naive to do that automatically.
You want to use the type override syntax to tell the macros what you're expecting:
Explicitly: https://docs.rs/sqlx/latest/sqlx/macro.query.html#force-a-differentcustom-type
Implicitly (query_as!() and variants only): https://docs.rs/sqlx/latest/sqlx/macro.query_as.html#column-type-override-infer-from-struct-field


feat(snippets): add a Dynamic Left Sidebar

Dynamic Left Sidebar Description

Makes the left sidebar dynamic, so it only shows when you hover over it and pushes the main content to the right.

Motivation

Previously, I made a New Hover Panel #778  that fixed the legacy Hover Panels. But after some time using it, I found it blocks the beginning of a playlist(can be anything) when I hover the left sidebar that activates the hovering, which is the expected hovering behavior, but it's kinda annoying. Then I made this one to be like when you hover the left side edge, the LeftSidebar appears and pushes the content to the right so nothing is blocked.

Does this replace the other new hover panel snippet? Should we remove it in the code?

Does this replace the other new hover panel snippet? Should we remove it in the code?

Function-wise, it replaces all hovering left sidebar snippets, both can be there in case someone prefers hovering instead of this dynamic one.

Oh, the hover one goes on top of the content vs this moves it to the side?

Exactly. This one pushes the main view to the right without blocking anything below it.


3D Tiles Next roadmap

Roadmap issue to keep track of 3D Tiles Next extensions and their implementation status in Cesium Native.
See 3D Tiles Next README for more background on these extensions.
3D Tiles Next extensions:

[x] 3DTILES_content_gltf
[ ] 3DTILES_metadata
[ ] EXT_mesh_features - Successor to EXT_feature_metadata (#281)
[x] 3DTILES_implicit_tiling - https://github.com/CesiumGS/cesium-native/issues/353
[x] 3DTILES_bounding_volume_S2 - https://github.com/CesiumGS/cesium-native/issues/364
[ ] 3DTILES_multiple_contents

Other useful glTF extensions

[ ] EXT_mesh_gpu_instancing - https://github.com/CesiumGS/cesium-native/pull/290 (related)
[x] KHR_texture_basisu
[ ] EXT_meshopt_compression
[ ] KHR_mesh_quantization

The initial 3D Tiles Next datasets we want to show are OWT and CDB. The OWT base globe uses nearly all the 3D Tiles Next extensions. CDB data can be converted to 3D Tiles Next with the --3d-tiles-next flag once https://github.com/CesiumGS/cdb-to-3dtiles/pull/58 is merged. Datasets like Yemen have raster materials that are converted to feature ID textures.

OWT base globe
CDB with feature ID textures

Most of this has been implemented already, with the exception of multiple contents and EXT_mesh_gpu_instancing (which is being tracked here).


[e2e]: go workflow_dispatch main workflow_inputs-noldflags slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8211110400
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sat Mar  9 01:22:45 UTC 2024

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/8218616175
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.workflow_dispatch.main.workflow_inputs-noldflags.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Sun Mar 10 01:34:08 UTC 2024
Tests are passing now. Closing this issue.


[IMPROVMENT] Remove unnecessary float pass reference in HSV/HSL

Describe your changes
It's not optimal to pass floats by reference since they're 32bits and doing so copies 64bits for the pointer instead of 32bits on 64bit systems.
Checklist before requesting a review

[x] I have performed a self-review of my code.

Why remove reference from output variable?

The hsv get, set should be rename to fromRgba and toRgba

Oh I remember... it's to edit floats right away rather than getting returning things! this PR is wrong

And some function of the class HSL can be improve, i.g.
    Color3B toColor3B();
    Color4B toColor4B();
    Color4F toColor4F();

should changed to:
    Color3B toColor3B() const;
    Color4B toColor4B() const;
    Color4F toColor4F() const;

And
 void set(float r, float g, float b, float a = 1.0F);
    void get(float& r, float& g, float& b) const;
``` changed to
```cpp
 void fromRgba(const Color4F& rgba);
 Color4F toRgba() const;