Drop support for DirectX 9 / OpenGL 2.0

PR Details
Description
This is my attempt to remove DirectX 9 / OpenGL 2.0 (called Level 9) from Stride and set Level 10 as default instead.
Motivation
This is change was inspired by @ykafia (check out his discussion here https://github.com/stride3d/stride/discussions/2185) and based on my personal knowledge.
Stride Engine primarly focus currently on supporting desktop and mobile platforms (but I heard isn't that good tbh), so it would be relevant to check out current state of graphics api distribution among players:
Android

Source: https://developer.android.com/about/dashboards/index.html
As we can see, more than 93% of devices support OpenGL 3.0 or later
Desktop
Since Steam platform is dominant, I think it is also reliable source

As can be observed, DirectX 9 marketshare is basically irrelevant ( almost 97 % of devices are supporting DX10 or later)
Interestingly, Directx 12 alone supports about 90% of the all desktop computers.
Source: https://store.steampowered.com/hwsurvey
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] I have built and run the editor to try this change out.

We should probably make sure we have WebGPU native working as a replacement, wgpu-native has been widely tested to work well on android devices and it's using opengl ES and Vulkan under the hood

My two cents: The DefaultGraphicsProfile changes are fine but I think removing support entirely might be more appropriate for a bigger release (i.e., 4.3) instead of a minor 4.2.x update. It would be easier to communicate and projects that still need feature level 9.x or ES 2.0 can stay on 4.2.x without worry.
Overall it makes sense to streamline supported feature levels. Unity and Unreal dropped support for feature level 9.x about a decade ago, and I believe only the former still supports OpenGL ES 2.
IIRC, feature level 10/OpenGL ES 3.0 work on Android but the Silk implementation on mobile needs improvement. I think we can treat these as two separate and independent issues.


Change to handle commits during rebalancing

The write-up and pull request from Alpakka Kafka were very helpful in solving this.

https://github.com/akka/alpakka-kafka/issues/755
https://github.com/akka/alpakka-kafka/pull/751

@vlovgr Do you have any results of how this solution behaves with real data? I'm still hesitant if https://github.com/akka/alpakka-kafka/pull/751 is ready do go.

@ennru @CremboC have tested this while scaling up consumers, and rebalancing seem to work well, compared to before where CommitFailedException was so prevalent it was difficult to get a stable consumer group. @CremboC might be able to provide more details.
Also, huge thanks for the detailed write-up and pull-request @ennru!

@ennru this PR definitely fixed the issues that I saw.
Essentially, I couldn't use this library at all at our scale and with our configuration with more than a single consumer. Everything worked perfectly fine, but then when the service had to scale up to multiple consumers (i.e. number of messages per second became too high for a single consumer to consume), everything went to hell. They would constantly die with CommitFailedException, as @vlovgr said and would take anywhere between 5 minute and never (yes, never) to fully recover. Every new deployment was the same thing over again - even if there was a single consumer in the previous deployment.
With this PR merged, everything works perfectly - no issues during scale up at all.
The only thing not 100% fixed as far as I'm concerned is I'm still seeing quite a bit of Node 5 was unable to process the fetch request with (sessionId=1545249616, epoch=INITIAL): INVALID_FETCH_SESSION_EPOCH "errors", but I'm not sure if it's related or not.
If you need any numbers, let me know 👍


[1/n] [sui-json-rpc] unit testing

Description
Given the recent changes to error handling and error response codes on rpc, adding some unit tests so we can expect behavior without having to reproduce potentially difficult error states through integration/ e2e tests.

MoveUtils previously took AuthorityState, now has field MoveUtilsInternalTrait trait object. Moved most implementation of MoveUtils input the trait object so we can mock various states and expect the correct success or error response.
Two unit tests for get_normalized_move_module for success and error responses.

Test Plan
Existing tests + new unit tests

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Looks great! do we plan to split the metrics on dash & alerts for user input errors and others?

Yes! I think we'll have to modify how we increment errors_by_routes metric today. It currently gets updated in the metrics logger, which is not able to access the error response code.


Analyzing ORT with itself throws exception

Hi there,
I just started using this tool at work and tried to analyze this repo with it.
Sadly ORT throws an exception, when scanning itself.
Here is the terminal output:
$ docker run --rm -it -v $PWD:/project --entrypoint=/bin/bash censored.url/ort-image:latest
root@2732316eb1e0:/# ort --info analyze \
>     -i /project \
>     -o /project/ort/analyzer;

________ _____________________
\_____  \\______   \__    ___/ the OSS Review Toolkit, version DOCKER-SNAPSHOT-ee57c022fd0d817497999b9bc6f28855ce5c1e54.
 /   |   \|       _/ |    |
/    |    \    |   \ |    |    Running 'analyze' under Java 11.0.15 on Linux with
\_______  /____|_  / |____|    4 CPUs and a maximum of 4002 MiB of memory.
        \/       \/
Environment variables:
ORT_CONFIG_DIR = /root/.ort/config
ORT_DATA_DIR = /root/.ort
TERM = xterm
http_proxy = censored.proxy.url
https_proxy = censored.proxy.url
JAVA_HOME = /opt/java/openjdk
ANDROID_HOME = /opt/android-sdk
GOPATH = /tmp/go

Looking for analyzer-specific configuration in the following files and directories:
        /root/.ort/config/curations.yml (does not exist)
        /root/.ort/config/curations (does not exist)
        /project/.ort.yml
        /root/.ort/config/resolutions.yml (does not exist)
The following package managers are activated:
        Bower, Bundler, Cargo, Carthage, CocoaPods, Composer, Conan, DotNet, GoDep, GoMod, Gradle, Maven, NPM, NuGet, PIP, Pipenv, Pub, SBT, SpdxDocumentFile, Stack, Unmanaged, Yarn
Analyzing project path:
        /project
11:31:41.205 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/examples/notifications/src/main/resources' as it is hard-coded to be ignored.
11:31:41.208 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/examples/evaluator-rules/src/main/resources' as it is hard-coded to be ignored.
11:31:41.215 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/evaluator/src/main/resources' as it is hard-coded to be ignored.
11:31:41.218 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/advisor/src/main/resources' as it is hard-coded to be ignored.
11:31:41.220 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/detekt-rules/src/main/resources' as it is hard-coded to be ignored.
11:31:41.237 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/.git' as it is hard-coded to be ignored.
11:31:41.242 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/scanner/src/main/resources' as it is hard-coded to be ignored.
11:31:41.251 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/analyzer/src/main/resources' as it is hard-coded to be ignored.
11:31:41.274 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/analyzer/src/funTest/assets/projects/synthetic/npm/node-modules/node_modules' as it is hard-coded to be ignored.
11:31:41.278 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/analyzer/src/funTest/assets/projects/synthetic/sbt-http4s-template/src/main/resources' as it is hard-coded to be ignored.
11:31:41.291 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/utils/test/src/main/resources' as it is hard-coded to be ignored.
11:31:41.293 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/utils/spdx/src/main/resources' as it is hard-coded to be ignored.
11:31:41.297 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/utils/common/src/main/resources' as it is hard-coded to be ignored.
11:31:41.307 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/model/src/main/resources' as it is hard-coded to be ignored.
11:31:41.317 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/downloader/src/main/resources' as it is hard-coded to be ignored.
11:31:41.319 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/cli/src/main/resources' as it is hard-coded to be ignored.
11:31:41.321 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/reporter/src/main/resources' as it is hard-coded to be ignored.
11:31:41.328 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/notifier/src/main/resources' as it is hard-coded to be ignored.
11:31:42.014 [main] INFO  org.ossreviewtoolkit.utils.ort.OrtAuthenticator - Authenticator was successfully installed.
11:31:42.037 [main] INFO  org.ossreviewtoolkit.utils.ort.OrtProxySelector - Proxy selector was successfully installed.
11:31:42.042 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/examples/notifications/src/main/resources' as it is hard-coded to be ignored.
11:31:42.043 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/examples/evaluator-rules/src/main/resources' as it is hard-coded to be ignored.
11:31:42.047 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/evaluator/src/main/resources' as it is hard-coded to be ignored.
11:31:42.049 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/advisor/src/main/resources' as it is hard-coded to be ignored.
11:31:42.050 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/detekt-rules/src/main/resources' as it is hard-coded to be ignored.
11:31:42.063 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/.git' as it is hard-coded to be ignored.
11:31:42.066 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/scanner/src/main/resources' as it is hard-coded to be ignored.
11:31:42.069 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/analyzer/src/main/resources' as it is hard-coded to be ignored.
11:31:42.079 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/analyzer/src/funTest/assets/projects/synthetic/npm/node-modules/node_modules' as it is hard-coded to be ignored.
11:31:42.081 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/analyzer/src/funTest/assets/projects/synthetic/sbt-http4s-template/src/main/resources' as it is hard-coded to be ignored.
11:31:42.087 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/utils/test/src/main/resources' as it is hard-coded to be ignored.
11:31:42.088 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/utils/spdx/src/main/resources' as it is hard-coded to be ignored.
11:31:42.090 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/utils/common/src/main/resources' as it is hard-coded to be ignored.
11:31:42.095 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/model/src/main/resources' as it is hard-coded to be ignored.
11:31:42.097 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/downloader/src/main/resources' as it is hard-coded to be ignored.
11:31:42.098 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/cli/src/main/resources' as it is hard-coded to be ignored.
11:31:42.099 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/reporter/src/main/resources' as it is hard-coded to be ignored.
11:31:42.102 [main] INFO  org.ossreviewtoolkit.analyzer.PackageManager - Not analyzing directory '/project/notifier/src/main/resources' as it is hard-coded to be ignored.
11:31:42.210 [main] INFO  org.ossreviewtoolkit.utils.ort.OrtAuthenticator - Authenticator is already installed.
11:31:42.210 [main] INFO  org.ossreviewtoolkit.utils.ort.OrtProxySelector - Proxy selector is already installed.
11:31:42.216 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/analyzer/src/funTest/assets/projects/synthetic/spdx/project-xyz-with-inline-packages.spdx.yml'.
11:31:42.320 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/analyzer/src/funTest/assets/projects/synthetic/spdx/project-xyz-with-transitive-dependencies.spdx.yml'.
11:31:42.324 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/analyzer/src/funTest/assets/projects/synthetic/spdx/project-xyz-with-package-references.spdx.yml'.
11:31:42.327 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/analyzer/src/funTest/assets/projects/synthetic/spdx/libs/openssl/package.spdx.yml'.
11:31:42.330 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/analyzer/src/funTest/assets/projects/synthetic/spdx/libs/curl/package.spdx.yml'.
11:31:42.332 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/analyzer/src/funTest/assets/projects/synthetic/spdx/libs/my-lib/package.spdx.yml'.
11:31:42.337 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/analyzer/src/funTest/assets/projects/synthetic/spdx/libs/zlib/package.spdx.yml'.
11:31:42.338 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/utils/spdx/src/test/assets/spdx-spec-examples/SPDXYAMLExample-2.2.spdx.yaml'.
11:31:42.372 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/utils/spdx/src/test/assets/spdx-spec-examples/SPDXYAMLExample-2.2-no-ranges.spdx.yaml'.
11:31:42.387 [main] INFO  org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache - Loading SpdxDocument from '/project/utils/spdx/src/test/assets/spdx-spec-examples/SPDXYAMLExample-2.2-no-relationship-describes-or-document-describes.spdx.yaml'.
Exception in thread "main" com.fasterxml.jackson.databind.exc.ValueInstantiationException: Cannot construct instance of `org.ossreviewtoolkit.utils.spdx.model.SpdxDocument`, problem: The document must either have at least one relationship of type 'DESCRIBES' or contain the 'documentDescribes' field.
 at [Source: (File); line: 382, column: 1]
        at com.fasterxml.jackson.databind.exc.ValueInstantiationException.from(ValueInstantiationException.java:47)
        at com.fasterxml.jackson.databind.DeserializationContext.instantiationException(DeserializationContext.java:2047)
        at com.fasterxml.jackson.databind.DeserializationContext.handleInstantiationProblem(DeserializationContext.java:1400)
        at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapInstantiationProblem(BeanDeserializerBase.java:1866)
        at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:520)
        at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromObjectUsingNonDefault(BeanDeserializerBase.java:1405)
        at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:351)
        at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:184)
        at com.fasterxml.jackson.databind.deser.DefaultDeserializationContext.readRootValue(DefaultDeserializationContext.java:323)
        at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4674)
        at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3514)
        at org.ossreviewtoolkit.analyzer.managers.utils.SpdxDocumentCache.load(SpdxDocumentCache.kt:70)
        at org.ossreviewtoolkit.analyzer.managers.SpdxDocumentFile.mapDefinitionFiles(SpdxDocumentFile.kt:417)
        at org.ossreviewtoolkit.analyzer.Analyzer.findManagedFiles(Analyzer.kt:77)
        at org.ossreviewtoolkit.cli.commands.AnalyzerCommand.run(AnalyzerCommand.kt:242)
        at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:198)
        at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:211)
        at com.github.ajalt.clikt.parsers.Parser.parse(Parser.kt:18)
        at com.github.ajalt.clikt.core.CliktCommand.parse(CliktCommand.kt:393)
        at com.github.ajalt.clikt.core.CliktCommand.parse$default(CliktCommand.kt:390)
        at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:408)
        at com.github.ajalt.clikt.core.CliktCommand.main(CliktCommand.kt:433)
        at org.ossreviewtoolkit.cli.OrtMainKt.main(OrtMain.kt:81)
Caused by: java.lang.IllegalArgumentException: The document must either have at least one relationship of type 'DESCRIBES' or contain the 'documentDescribes' field.
        at org.ossreviewtoolkit.utils.spdx.model.SpdxDocument.<init>(SpdxDocument.kt:167)
        at org.ossreviewtoolkit.utils.spdx.model.SpdxDocument.<init>(SpdxDocument.kt:36)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
        at kotlin.reflect.jvm.internal.calls.CallerImpl$Constructor.call(CallerImpl.kt:41)
        at kotlin.reflect.jvm.internal.KCallableImpl.callDefaultMethod$kotlin_reflection(KCallableImpl.kt:173)
        at kotlin.reflect.jvm.internal.KCallableImpl.callBy(KCallableImpl.kt:112)
        at com.fasterxml.jackson.module.kotlin.ValueCreator.callBy(ValueCreator.kt:45)
        at com.fasterxml.jackson.module.kotlin.KotlinValueInstantiator.createFromObjectWith(KotlinValueInstantiator.kt:135)
        at com.fasterxml.jackson.databind.deser.impl.PropertyBasedCreator.build(PropertyBasedCreator.java:202)
        at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:518)
        ... 18 more

We are running it in a docker container, which is build from this repo. As you can see the version running here is from Jun 2 (commit ee57c02). The repo I scanned is a bit newer and the most current commit is 1be897cbb787b6fbb9eec2ffdf8e4db09b633749.
I did not have the time today to update both image and repo and test it again, but maybe this helps you as is and this issue is not out of date.
I did not have this issue with other projects I scanned so far. Disclaimer: I only scanned 2 more.
Keep up the good work!

Thanks for reporting @pepper-jk, the test asset is deliberately broken, but this should not crash the analyer. I have created a PR to address that.


A way to add HTML to the  tags to allow for web app manifest

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Ability to add arbitrary html head contents, or generate a manifest.json file, and contents
Describe alternatives you've considered
N/A
Additional context
Chrome web apps, iphone home screen shortcuts etc use manifest.json and link tags in the  to populate icons, background and toolbar colors etc. This is not currently possible

Related to #1091


Use force_override instead of default

If we are in this recipe... it's not a will... it's a fact ;)
Foodcritic <= 4.0.0 fail with force_override

ok for me.


zebra-cli init

Motivation

Needed skeleton program for generating and displaying unified addresses
Specifications

Pulls in zcash_address to encode unified addresses:
https://github.com/zcash/zips/blob/main/zip-0316.rst
Designs
https://zebra.zfnd.org/dev/rfcs/0009-zebra-client.html
Solution

Create zebra-cli with Abscissa (same framework as zebrad), create a subcommand get-new-address, which generates new Sapling and Orchard key trees and encodes them and renders them as a QR code in std out. Does not save any keys, everything is discarded.
Also has the standard version and help commands.

Review

Anyone can review
Follow Up Work

Everything else 😹

This looks great, neat features!
This PR adds another binary to our builds, and we're already exceeding the 10 GB GitHub cache limit. So I'd like to do some of these things before we merge this PR:

set up a merge bot and turn off Windows and macOS builds on PRs
stop caching Windows builds (they are not required to merge anyway)
any other changes that reduce the cache size

As an alternative, we could add this new feature as a zebrad command?
I'm not quite sure how we split features between zebrad, zebra-client, and zebra-cli. So it might be helpful to discuss and document that before we create zebra-cli.

This looks great, neat features!
This PR adds another binary to our builds, and we're already exceeding the 10 GB GitHub cache limit. So I'd like to do some of these things before we merge this PR:

set up a merge bot and turn off Windows and macOS builds on PRs

💯

stop caching Windows builds (they are not required to merge anyway)

💯

any other changes that reduce the cache size

👍

I'm not quite sure how we split features between zebrad, zebra-client, and zebra-cli. So it might be helpful to discuss and document that before we create zebra-cli.

The design in https://zebra.zfnd.org/dev/rfcs/0009-zebra-client.html basically has zebra-client as a library crate to handle 'all functionality related to a particular user's private data', which would then be used by the zebra-cli binary ('the wallet') and also 'a client component for zebrad that handles block chain scanning' which is used by zebrad when a ViewingKey is registered for block chain scanning.
So this PR should probably move the bulk GetNewAddressCmd::run() into zebra-client, at least to have those dependencies in there, and then zebra-cli depend on zebra-client to expose/re-export those dependencies.
But yeah this is strictly non-urgent and can wait to merge until we tidy up our CI caches 📦

The design in https://zebra.zfnd.org/dev/rfcs/0009-zebra-client.html basically has zebra-client as a library crate to handle 'all functionality related to a particular user's private data', which would then be used by the zebra-cli binary ('the wallet') and also 'a client component for zebrad that handles block chain scanning' which is used by zebrad when a ViewingKey is registered for block chain scanning.
So this PR should probably move the bulk GetNewAddressCmd::run() into zebra-client, at least to have those dependencies in there, and then zebra-cli depend on zebra-client to expose/re-export those dependencies.

That makes sense. But I think having zebra-client and zebra-cli could be a bit confusing, because the names are very similar.
So I'm wondering if we want to do some of these things:

rename zebra-client to zebra-wallet
put the wallet and client in the same crate, as a lib and bin target

I marked this as draft, so we don't accidentally merge it.

Should we close this for now?

Should we close this for now?

I'm going to close this PR but leave the branch up


Fix availability-group-manually-configure-tutorial-multi-subnet doc

Without activating the FILESTREAM feature, the Always on Availability Group cannot be created.
To give more context; the Cloud Witness cannot be setup.

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

Hi @fschirinzi! Thank you for the feedback on this content. I have incorporated your changes into another PR with additional details. FILESTREAM doesn't need to be enabled for all AGs, it only needs to be enabled if you're adding a database that uses FILESTREAM. The change should be live later this week. I'll go ahead and close this PR, but feel free to comment if you need anything further.
Thanks!
#please-close


Cmake and SDK installation for sample projects erroring out

Required Info

Camera Model
{ T265 }

Firmware Version
(<IP_ADDRESS>1)

Operating System & Version
{Win (10)

SDK Version
{ 2.0 }

Language
{C++ }

Segment
{AR }

Issue Description
Hi, I am a beginner here and have tried following the SDK 2.0 installation guide both here (https://www.intel.ca/content/www/ca/en/support/articles/000030463/emerging-technologies/intel-realsense-technology.html) and here (https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_windows.md), with CMake, but CMake throws a lot of configuration errors when press generate. is there a step by step SDK installation just to be able to build the sample projects?

please ensure you have network access while doing cmake
when generating the project file, it will need to download some files/firmware from server
it is helpful that you can attached the errors for reference


Using mdlink within a table?

First of all, great github action!
For the example
mdlink – creates markdown link.
Example: {{ "https://github.com" | mdlink "GitHub" }} will be rendered as [GitHub](https://github.com).

I was wondering if there would be a way/future support to allow the above to work within a markdown table such as:
| Github Link                        | Twitter Link                      |
| ----------------------------------- | ------------------------------- |
| {{ "https://github.com" | mdlink "GitHub" }} | {{ "https://twitter.com" | mdlink "Twitter" }} |

Hey, I'm glad you appreciate this GitHub Action.
This is already supported. Action uses Go templates, so it doesn't really matter where you use template functions like mdlink. You can use it in a markdown table, in a JSON file, in a YAML file, in a text file, etc.
Check out the example: template, action run


Automate configuration list through balena API

Add a new page for the configuration list with a dropdown menu for device types
Parsing API response to generate a table with some description
Add page to the /reference/supervisor section
Redirected to raspberrypi3's configuration list as the default device type

TODO

[ ] Need to merge #2144 first to bolt down the configuration variables naming issue
[ ] The redirect is acting up a little where when it redirects but also restores the state of the sidebar for some reason. Need to fix this.
[x] We really need to implement this first: https://jel.ly.fish/e06ebc86-6c96-43cb-9775-415a60156b1e so the API response is standardized in the short term - https://github.com/balena-io/open-balena-api/pull/896

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@vipulgupta2048 Would this PR only be merge-able after the TODOs you listed are complete?

@cywang117 No but I would really like it to. And we are close, I already got the PR open to add the reboot required metadata. https://github.com/balena-io/open-balena-api/pull/896
Need the SV team's help to conclude it now.

@balena-ci rebase

@balena-ci rebase

@balena-ci rebase

@balena-ci I self-certify!


Upgrade website dependencies

I just upgraded all website dependencies in main 👌 so will be closing this one. I did not update the config for external links tho, needed?


Dragging *.obj files imported as Mesh to the editor's viewport issue

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3.0 master https://github.com/godotengine/godot/commit/025f13856138918b13956b085a586a73a584bc04
Issue description:

When dragging an *.obj file imported as a Mesh from the filesystem dock to the viewport the created MeshInstance will be treated as a scene and won't let you save the scene because this error:

It can be added to the scene if you create a MeshInstance and you manually add it to the Mesh property. This way you will be able to save the scene.
Steps to reproduce:

Drag an *.obj file imported as a Mesh into the editor's viewport
Try to save the scene

I experienced this problem about a week ago on Linux with a nightly build. I found the same workaround of creating a MeshInstance and manually adding the .obj to the Mesh property.
FWIW I was using Debian and Xfce at the time. I'm now using Manjaro and i3, will test with alpha 2 and report back later.

I don't know enough about the scene saving system to fix this right now, but the problem is here:
https://github.com/godotengine/godot/blob/67a706fc1b9721f3f06eef8be7312f175e2041ce/scene/resources/packed_scene.cpp#L427
ResourceLoader::load is returning a Ref<Resource>. so the cast to Ref<PackedScene> fails. p_node->get_filename() != String() && p_node->get_owner() == p_owner && instanced_by_owner is false when creating the instance and assigning the mesh manually, so this error doesn't happen in that case.

Alpha 2 seems not to consider obj as meshes, so they can't be assigned to mesh instances :(


Update README

Looking good - sort the MIT link and I'll happily approve

(should we set up PRs-need-a-review rule on this repo?)

Yes


New App: HRBFC

Description
Go Beavers!
This applet displays the latest scores and upcoming game information for the Hampton and Richmond Borough FC Beavers!

Copilot

🤖 Generated by Copilot at 60af0f9
Summary
🦁⚽🕒

This pull request adds a new applet called HRBFC, which shows live scores and upcoming matches for a football club. The applet consists of a Starlark file hrbfc.star that contains the logic and rendering code, and a YAML file manifest.yaml that contains the metadata and configuration. The applet uses the Tidbyt API and a custom AWS Lambda function to fetch and cache the data.

HRBFC applet
Shows the football club's scores
Autumn wind blows cold

Walkthrough

Create and configure a new applet for displaying HRBFC scores and matches (link, link)

Write the main logic of the applet in hrbfc.star using Starlark and Tidbyt API (link)
Fetch and cache data from a custom AWS Lambda function (link)
Handle different game statuses, team names, and time zones (link)
Document the code with comments and follow the style guide (link)
Add the manifest file in manifest.yaml using YAML and Tidbyt schema (link)
Specify the applet ID, name, summary, description, author, file name, and package name (link)

I have read the CLA Document and I hereby sign the CLA


Stopped working after upgrading Elastic to 2.2

From @MonDeveloper on March 11, 2016 0:36
Copied from original issue: urielha/log4stash-old#16

Do you have any error message?

I succeeded in using it with elastic 2.3.
The error I had when logging was related to using the '_ttl' field with this configuration:
<ElasticFilters>
      <Add>
        <Key>_ttl</Key>
        <Value>3d</Value>
      </Add>
</ElasticFilters>

Any way of fixing it?

Hi,
I have seen that _ttl parameter is deprecated in Elastic 2.*
https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-ttl-field.html
I haven't checked this myself already but maybe this is the issue.
Please update about your insights

Yep, I saw it has been deprecated after 2.0, but since they didn't provide any alternative they said it would work until they provide another way to do this. A friend said I might need to create a custom mapping  to make it work, but I remember that it used to work without any custom mapping.

For the mapping you can use the <template> option of log4stash.
Here is a gist [example of template] (https://gist.github.com/urielha/fd6dbf29e40da96a7c768e0d8359d365) with ttl enabled.
Pay attention to configure the timestamp as date.
Have a look at the config example from log4stash tests to see how to configure it.
If there are still problems I will try to test it myself later this week.
Best regards.

@MonDeveloper, Please open this again if you still have the issue after upgrading to 2.0.1


is this a card?

And now it's an issue

Yes it is

And the comments are  markdown, so here's a picture:


Increase maximum size of json file that will be read for annotations.

This is still constrained more than desirable, and could use refactoring.  This is not the whole solution for #1073.

Note that prior to #989, we would try to load arbitrarily large json files BUT only from filesystem assetstores.


Custom variable application fields in application

[ ] render fields on application fill-out page
Dependency:
#322

As
user
I want to
be able to fill out the custom fields that the event organizer provided
In order to
share the information that the organizers need to pick me

🍪 20


Issue: Tags move around the tag list.

this was fixed for the tags modal for lassoing, now fixing it for the other modal (tags modal from notebook)

#236 fixed with 166a84e11b6a4968546354ca60b22f998ccd1589


Minutes 2021-08-11

Apologies I missed out on some bits of the conversation @bblfish and @elf-pavlik. Might require a bit of a review this week.

Ok, let me try to update this before I forget what went on...


[cli] How can I use flutter project as CLI application?

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Use case
Hi. I have an existing application uses Flutter as framework. I need to use it as a Command Line Interface tool. I've found a way how to quickly hide desktop window on Win/Nix/Mac OS but this is not applicable to Nix servers (in my case I would like to run app on the Ubuntu server 22.04) which has no window interfaces at all.
There are few ways how to run code in CLI using dart but it is not works for me for some reasons:

I'd like to hide source code from end-user
I'd like to avoid requesting install dart as an required component
My app uses Rust plugin compiles at every build and that code must be hidden too

Is there any ways to run FlDartProject without creating any UI elements?
Proposal
I would like to have a way how to start app w/o running any windows. If it is gonna be separate executable this also wold be great.

@13thdeus
Can you take a look at this and check if it helps in your case ?

I've checked melos but it seems it would not be helpful. I need to find a way how to run flutter/dart code on windowless OS without providing source code. Looks like melos couldn't help with it.

@13thdeus
Are you looking for this use case to specifically run on windows platform ?

@darshankawar I'm looking for way to run an app on Linux at first.

Can you take a look at https://github.com/flutter/flutter/issues/41737 and see if it helps in your case ?

I've found that is enough for me to just use dart compile exe command instead of flutter. I still need to update app but that way looks correct for me. Yeah, there is a question how to use rust in this case but it is another question


Make unincorporate task a batch task

Avoids gateway time out message

@johnt-freecen The record removal has been changed to a rake task. Deployed to test3

Hello Kirk,
I have just run this task. All seems ok, sample records checked were removed from the system and a completion message received.
I am now running the re-implement the file  process.
Regards
John
Sent from Mail for Windows 10
From: Kirk Dawson
Sent: 12 October 2020 00:04
To: FreeUKGen/FreeCENMigration
Cc: johnt-freecen; Mention
Subject: Re: [FreeUKGen/FreeCENMigration] Make unincorporate task a batch task(#1008)
@johnt-freecen The record removal has been changed to a rake task. Deployed to test3
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hello Kirk,
All seems to be working I have done a remove a file, edit the file and re-implementation to check the change is in place.
Regards
John
Sent from Mail for Windows 10
From: Kirk Dawson
Sent: 12 October 2020 00:04
To: FreeUKGen/FreeCENMigration
Cc: johnt-freecen; Mention
Subject: Re: [FreeUKGen/FreeCENMigration] Make unincorporate task a batch task(#1008)
@johnt-freecen The record removal has been changed to a rake task. Deployed to test3
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks @johnt-freecen


Update to finagle-postgres 0.3.2

finagle-postgres from 0.2.0 -> 0.3.2 support

db-async-common from 0.2.20 -> 0.2.21

mysql-async from 0.2.20 -> 0.2.21

postgresql-async from 0.2.20 -> 0.2.21

cassandra-driver-core from 3.1.2 -> 3.1.3

monix from 2.1.1 -> 2.1.2

DB drivers for testing

tut-plugin from 0.4.7 -> 0.4.8

sbt-mima-plugin 0.1.9 -> 0.1.13

sbt-scalajs 0.6.13 -> 0.6.14

HikariCP in tests 2.5.1 -> 2.6.0

monix 2.1.2 -> 2.2.1

logback-classic 1.1.8 -> 1.1.9

Fixes #issue_number
Problem
Explain here the context, and why you're making that change.
What is the problem you're trying to solve?
Solution
Describe the modifications you've done.
Notes
Additional notes.
Checklist

[x] Unit test all changes
[x] Update README.md if applicable
[x] Add [WIP] to the pull request title if it's work in progress
[x] Squash commits that aren't meaningful changes
[x] Run sbt scalariformFormat test:scalariformFormat to make sure that the source files are formatted

@getquill/maintainers

@mxl - can you release minor release, after merging this PR?

@golem131 Yes.


Issues with impute_confidence.

Baxter's comment in the source about issues with impute_confidence for continuous values should be documented somewhere more stable + visible (ie here).
    # The confidence in continuous imputation is "the probability that
    # there exists a unimodal summary" which is defined as the proportion of
    # probability mass in the largest mode of a DPMM inferred from the simulate
    # samples. We use crosscat on the samples for a given number of iterations,
    # then calculate the proportion of mass in the largest mode.
    #
    # NOTE: The definition of confidence and its implementation do not agree.
    # The probability of a unimodal summary is P(k=1|X), where k is the number
    # of components in some infinite mixture model. I would describe the
    # current implementation as "Is there a mode with sufficient enough mass
    # that we can ignore the other modes". If this second formulation is to be
    # used, it means that we need to not use the median of all the samples as
    # the imputed value, but the median of the samples of the summary mode,
    # because the summary (the imputed value) should come from the summary
    # mode.
    #
    # There are a lot of problems with this second formulation.
    # 0. SLOW. Like, for real.
    # 1. Non-deterministic. The answer will be different given the same
    #   samples.
    # 2. Inaccurate. Approximate inference about approximate inferences.
    #   In practice confidences on the sample samples could be significantly
    #   different because the Gibbs sampler that underlies crosscat is
    #   susceptible to getting stuck in local maximum. Of course, this could be
    #   mitigated to some extent by using more chains, but things are slow
    #   enough as it is.
    # 3. Confidence (interval) has a distinct meaning to the people who will
    #   be using this software. A unimodal summary does not necessarily mean
    #   that inferences are within an acceptable range. We are going to need to
    #   be loud about this. Maybe there should be a notion of tolerance?
    #
    # An alternative: mutual predictive coverage
    # ------------------------------------------
    # Divide the number of samples in the intersection of the 90% CI's of each
    # component model by the number of samples in the union of the 90% CI's of
    # each component model.

This should be documented somewhere for 0.1.4, but I'm not sure where it should be documented.


feat: allow the sidebar size to be draggable

Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)-https://linear.app/acryl-data/issue/PRD-851/allow-the-sidebar-size-to-be-draggable
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

Resizer.webm


Fix omitted ids, write tests.

At some point the usage of omitted ids got broken.  There are no unit tests, either.
julia> DeterministicVI.maximize_f(elbo_fft_opt, ea_fft, omitted_ids=[1])

ERROR: BoundsError: attempt to access 28-element Array{Float64,1} at index [29,1]
 in (::Celeste.DeterministicVI.##33#38)(::Array{Float64,1}, ::Array{Float64,1}) at /home/rgiordan/.julia/v0.5/Celeste/src/deterministic_vi/maximize_elbo.jl:67

@jrevels is work on refactoring Transform.jl now. I was thinking we'd get rid of omitted_ids and keep_ids because of the complexity, and because it doesn't seem as necessary any more. If we want to restore that functionality, the way to do it is probably to define another transform, like the box constraints or the simplex constraint that removes certain ids.
Are you using omitted_ids often? Is restoring this functionality a high priority? (It would take resources away from other things.)

Doing it through a transform would be fine, but I do think you should
implement it.
I spent some time digging into why the optimization problem is slow.  Part
of that was digging into why the ELBO Hessian so tightly couples the galaxy
and star parameters.  It turns out that the log term, per our intuition,
actually doesn't couple the parameters much, but the shared location
parameter does.
I then watched some animations of the optimization path, and it occurred to
me that along the way to getting the position correct, it is constantly
updating the galaxy shape parameters, too, since having the implied
position wrong will also bias the size of the galaxy outwards in order to
capture the uneven distribution of light caused by the location being
incorrect.
That suggests optimizing in two steps: first, keeping the galaxy parameters
fixed as if they were a small star, setting a = [1, 0], and optimizing only
the star parameters.  Even if it's a galaxy, since galaxies are symmetric,
this should be a reasonable guess of the shared location.  Then, starting
from that point, we can jointly optimize the star and galaxy parameters.
If this cuts down on the number of Newton steps, it could be a big
practical win.  Also, when we start from peak inits, doing something like
this will probably be sensible.
Incidentally, another possibility would be just to give stars and galaxies
their own location parameters, just like they have their own brightness
parameters.  Even with this, though, we may want to use a star fit to
initialize the galaxy locations.
Investigating this requires something like omitted ids.  I'll look into it
once you've restored the functionality one way or another.  I'll leave it
up to you how to prioritize.
On Mon, Dec 19, 2016 at 1:09 PM, Jeffrey Regier<EMAIL_ADDRESS>wrote:

@jrevels https://github.com/jrevels is work on refactoring Transform.jl
now. I was thinking we'd get rid of omitted_ids and keep_ids because of
the complexity, and because it doesn't seem as necessary any more. If we
want to restore that functionality, the way to do it is probably to define
another transform, like the box constraints or the simplex constraint that
removes certain ids.
Are you using omitted_ids often? Is restoring this functionality a high
priority? (It would take resources away from other things.)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jeff-regier/Celeste.jl/issues/480#issuecomment-268079208,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AESWPhDKW1FiL5KQyAH2tHd9X1rYkptMks5rJvKRgaJpZM4LREv6
.


Anaconda display of Chapter 6 Decision Tree

Because the unix dot command was not available to me on my Windows 10 system, I used python and pydotplus to display and save the decision tree at the start of Chapter 6 in your Machine Learning Book.
I like the book very much and enjoy going through the exercises--so far only to chapter 6.  It is not a problem of course for some not to be able to see the decision tree, but I found it frustrating not to see it.
This is what I used, and perhaps you could add something similar to your notebook which I also found very useful.
Thanks for writing the book and the notebook,
Sabina
from sklearn.externals.six import StringIO
from IPython.display import Image
from sklearn.tree import export_graphviz
import pydotplus
dot_data = StringIO()
export_graphviz(tree_clf, out_file=dot_data,
                filled=True, rounded=True,
                special_characters=True)
graph = pydotplus.graph_from_dot_data(dot_data.getvalue())
graph.write_png("iris_tree.png")
Image(graph.create_png())

Thanks a lot, Sabina, both for your kind words and for your helpful contribution.
I don't use Windows, but I thought GraphViz was available for Windows.  Doesn't it work on Windows 10? Did you have an installation problem? Or does the package not contain the dot command?
FYI, on Linux or MacOSX, the dot command is not included either, it is required to install GraphViz.
Thanks again,
Aurélien

GraphViz was available and installed in Anaconda.  The package did not seem to contain the dot command.
I just realized, I had troubles with using it and had to add the path where it was hidden under .../Anaconda3/Library/bin  in order to use it in Python.
Just tried the dot command again now that the path is fixed for GraphViz and the dot command worked ok.
I know I should switch to Linux for this kind of work.
Sabina

Thanks for your feedback, I'm glad everything works now.


I want top to bottom sheet like notification panel in mobile

is it reverse direction possible?

Hi @rajscet,
unfortunately this is not possible yet.


Incorrect NuGet Package Name for Natural Language API

At Google Cloud Natural Language API Client Library for .NET, under "Downloading the library" at the bottom of the page, the following text is presented: "Install a NuGet package from those available at Google.Apis.language." (See the screenshot below.)
However, the specified NuGet package does not exist. The package should probably be "Google.Apis.CloudNaturalLanguageAPI.v1beta1", as specified at Google.Apis.CloudNaturalLanguageAPI... in the NuGet Gallery.

Thanks for reporting this. I'll pass this on to the team to fix.

I think it was renamed in discovery service.   CloudNaturalLanguageAPI doesn't appear to exist anymore but language does.   Which should mean it will be generated the next time the guys run the generation script.  CloudNaturalLanguageAPI  should probably then disappear, however I cant remember how the generation runs if we kill old ones on nuget or not.
"kind": "discovery#directoryItem",
"id": "language:v1beta1",
"name": "language",
"version": "v1beta1",
"title": "Google Cloud Natural Language API",

This also means that the  Google.Apis.CloudNaturalLanguageAPI.v1beta1 package on NuGet should be pretty much the same thing unless they have made a change to the API over night.

I don't believe we remove any nuget packages.
The discovery doc contains:
"canonicalName": "Cloud Natural Language API"

I suspect that's what's generating that package name, and that it will continue doing so.

I stand corrected i didn't realize we were using conocialName.   Always assumed it was name like when building the get request.
GET https://www.googleapis.com/discovery/v1/apis/language/v1beta1/rest

Seeing the link guess I am not the only one :)

Fixed.


Main commands missing if you are using Install-Module

I uses Install-Module to install this plugin, there are significantly fewer completion available than the completions that are available here.

I just published v1.2 - maybe it fixes your issue.  If not, can you provide details?

I think it will fix it , thanks


docs: Add VS Code mention to the integration section

Since the obsidian plugin is mentionned there, I think it makes sense.
Alternatively, we could have a whole section with a demo image.

We should definitely mention the vscode integration but it should be under a different section as its our official integration and we will hopefully be supporting more in future too.
Probably "Supported Extensions" or something

Ok, should I add another section to the readme ? We could add a demo image similar to this one:

)

Ok, should I add another section to the readme ? We could add a demo image similar to this one:

Yeah I think a different section is better. As per the image I think its not needed, we can just point to the market place vscode extension and the demo will be there


Serializer now works with enums of different type (fix for issue #388)

https://github.com/Unity-Technologies/com.unity.multiplayer.mlapi/issues/388
Its good practice to keep your enums as small as possible, if the enum has fewer than 255 values might as well make it a byte. Before now this was not supported, this should make sure the serializers support that.

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

Yes, if you feel like thats cleaner thats no issue.
Considering Unity is replacing the streamwriter fully i dont expect this to
be merged at all.
On Tue, 8 Dec 2020, 19:26 gIsForGravity<EMAIL_ADDRESS>wrote:

@gIsForGravity commented on this pull request.
In MLAPI/Serialization/BitWriter.cs
https://github.com/Unity-Technologies/com.unity.multiplayer.mlapi/pull/392#discussion_r538695217
:

@@ -182,7 +182,19 @@ public void WriteObjectPacked(object value)
}
else if (value.GetType().IsEnum)
{

           WriteInt32Packed((int)value);

           var underlyingType = System.Enum.GetUnderlyingType(value.GetType());

           if (underlyingType == typeof(Int32))

Is it possible to use a switch case here?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Unity-Technologies/com.unity.multiplayer.mlapi/pull/392#pullrequestreview-547509866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARBM7F4P7VSKL7ZPUGCGNTSTZVVHANCNFSM4UMNZO3Q
.

Is this still relevant at all, with all the other changes Unity is doing?

I don't think we are going to remote BitReader/Writer at the moment so yes?

@MFatihMAR To me this looks good if the else else if is fixed.
Could you look into potentially getting this merged.

we already have this functionality implemented in NetworkSerializer and it's slightly different.
since we're already too far away from this PR, we'd probably bring NetworkSerializer implementation to NetworkReader and NetworkWriter instead.
I will create an internal ticket for tracking and close this issue.
nevertheless, thanks for looking at the same area @TJHeuvel :)

created MTT-714 and we'll address this once triaged.


PF4 Branch: Convert PF3 buttons to PF4 buttons

This PR converts the PF3 buttons to PF4 buttons. Each button was converted from a React component to an HTML button, using className rather than <Button and bsStyle.
No additional changes were done as part of this PR.

Just needs the conflicts resolve.


Let user know how to start crc after guided tour

As of now when user go through the guided tour, once the setup is done the button Start crc activated but that only start the tray and not the actual preset. So we should let user know what to do afterwards, Starting from tray application or from the CLI

We used to have a notification to guide people to the tray application.


Add webhook to trigger status reconciliations faster

Description
As part of https://github.com/kyma-project/telemetry-manager/issues/425 the detection of a bad situation by prometheus should result in an immediate status change in the related k8s resource. As the manager is pulling prometheus, that can take up to one minute. Goal is to introduce a push notification by leveraging the alertmanager protocol to have an immediate reaction in the manager.
Details

Have a dedicated a path exposing a webhook
Configure prometheus to use the webhook as alertmanager endpoint
The webhook will trigger reconcilation
Have a metric counting the invocations, being labeled with the alert type
Have a test assuring that the webhook gets called, verified by metrics

Criterias

An alert on prometheus gets propagated immediately (before you had to wait for next reconcilation)
Operator can see usage of webhook via metrics
the self-monitor is allowed to access the manager port of the webhook only, no other port

Links
https://github.com/kyma-project/telemetry-manager/pull/753/files

All acceptance criteria were implemented except the last one:

Since it's not feasible to whitelist Kubernetes API server IP in the self-monitor network policy, the existing "loose" policy is left unchanged.


all: Use Go module machinery to book-keep external tools

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] This PR adds tests for the most critical parts of the new functionality or fixes.
[x] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[x] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[x] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Track and maintain external tooling through Go's module machinery.
For that, I am using a tools.go file, which seems to be an increasingly-adopted practice.
Why

It centralizes version tracking of tooling instead of having versions spread around in shell-scripts
Where possible (if performance allows it) it saves developers from installing external tools, by using go run, making things work transparently (e.g. it took me a while to find out that the specific version of go-bindata to use was buried in gogenerate.sh)

Known limitations
go run is slower than running a  binary (at least until https://github.com/golang/go/issues/33468 is resolved), so we need to be careful on where to use it (e.g. the shadow binary is installed because go run is too slow).

@leighmcculloch are we planning to break out the code base into different modules? If so, do you know when and where?
Also, regardless of this PR, the Go SDK should be its own module, so that it doesn't drag all the other dependencies.
Once that is done we can evaluate whether it makes sense to push this trick to the new modules or roll it back. Until then (based on the approvals in this PR) I think there is consensus on moving forward with this approach.

There are plans to do it yup, see go modules part 1 and part 2 documents. We've done part 1, haven't done part 2 yet.
I think it is worth considering this after part 2 if the tools.go can live in its own module so that it doesn't pollute any other module. In fact you could probably introduce just that one module now independent of part 2.

@2opremio Yeah this is a plan we've had for a while but haven't had bandwidth to execute. I'd love it if you took some time to read through the links @leighmcculloch shared and then we can discuss what we want to do about it, and when. For now I think we should pause this PR to keep the Go SDK deps frozen. Happy to discuss early next week.

I still need to look at this, but I think we can close it


Zulipchat SSL Error

Describe the bug
Cannot connect to the Rust org on zulipchat.com because Zulip throws an SSL error.
Steps To Reproduce
Steps to reproduce the behavior:

nix-shell -p zulip --run "zulip"

Expected behavior
Zulip can connect to https://rust-lang.zulipchat.com. It works fine when using the official AppImage directly.
Screenshots

Notify maintainers
@andersk @jonafato
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.16.16-200.fc35.x86_64, Fedora Linux, 35 (Workstation Edition)`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.6.0`
 - channels(abbe): `"home-manager, nixgl, toolbelt"`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Yes, seems to work now!


Work around the mustSatisfyAnyOf bug

Log story short, my integration of majoity-multisign into CardStarter-LiquidityBridge got stuck on
Contract instance stopped with error: ConstraintResolutionError CannotSatisfyAny

This turns out to be caused by a bug in the implementation of mustSatisfyAnyOf which I've duly logged at https://github.com/input-output-hk/plutus-apps/issues/101 After taking a closer look, I'm not sure this will be fixed quickly: the underlying constructor MustSatisfyAnyOf [TxConstraint] will probably need to change, and it's public. As the function is undocumented, they might even say this was the expected behaviour. Which is to say that we need to work around the bug/feature of mustSatisfyAnyOf.
Unfortunately we can't completely drop its use, because the Plutus API provides no other way to construct a disjunction of constraints. The function works sensibly iff it's given a list of singleton TxConstraints, but we're currently not using it in this way. What we need to do is convert the TxConstraints expression from the current disjunctive normal form:
mustSatisfyAnyOf [ C11 <> C12 <> ... <> C1n, C21 <> ... <> C2n, ..., Cm1 <> ... <> Cmn ]

to equivalent conjunctive normal form:
mustSatisfyAnyOf [ C11, C21, ..., Cm1 ]
<> mustSatisfyAnyOf [ C12, C21, ..., Cm1 ]
...
<> mustSatisfyAnyOf [ C1n, C21, ..., Cm1 ]
...
<> mustSatisfyAnyOf [ C11, C2n, ..., Cm1 ]
...
<> mustSatisfyAnyOf [ C1n, C2n, ..., Cmn ]

The underlying Plutus bug I reported (https://github.com/input-output-hk/plutus-apps/issues/101) has been fixed sooner that I expected, so this workaround can be stripped once we upgrade Plutus to include the fix.


Plot raw data - visualization bug?

Description of the problem
Hello!
Today I noticed something strange with the plot UI. I describe it as follows:

I used Maxwell function to detect bad channels and I plot the raw data without "Butterfly" effect and the data looks as below.

Then, I clicked on the channel MEG2032 because my algorithm predicts that as a bad channel, too. However, looking at the plot above, MEG2032 seems clean. While trying to investigate, I clicked on that channel and the UI marks it in red color - which is fine, but the waveform changed abruptly to something below.

I wonder if the UI is designed this way or a bug. Please provide your comments.
Steps to reproduce
1. Import raw data
2. Detect bad channels using Maxwell filter by executing the following snippet:

    raw_check.info['bads'] = []
    auto_noisy_chs, auto_flat_chs = find_bad_channels_maxwell(
        raw_check, return_scores=False, verbose=True)
    print(auto_noisy_chs)  # we should find them!
    print(auto_flat_chs)  # none for this dataset

    raw_check.info['bads'] = auto_noisy_chs + auto_flat_chs
    for title, data in zip(['Maxwell Detection'], [raw_check]):
        with mne.viz.use_browser_backend('matplotlib'):
            fig = data.plot(butterfly=False, color='#00000022', bad_color='r')
        fig.subplots_adjust(top=0.9)
        fig.suptitle(title, size='xx-large', weight='bold')

3. Click on a channel not detected as bad by Maxwell function (i.e., the ones in grey color).
4. You might observe the change in shape of the data as I experienced.

Link to data
No response
Expected results
I'd expect the shape of the data to be the same whether I click on a particular sensor or not.
Actual results
As described above, the shape changes with a mouse click over the sensor's data.
Additional information
mne.sys_info()
Platform:         Windows-10-10.0.19044-SP0
Python:           3.8.16 (default, Mar  2 2023, 03:18:16) [MSC v.1916 64 bit (AMD64)]
Executable:       C:\ProgramData\Anaconda3\envs\NEAR\python.exe
CPU:              Intel64 Family 6 Model 158 Stepping 10, GenuineIntel: 8 cores
Memory:           Unavailable (requires "psutil" package)
mne:              1.3.1
numpy:            1.24.2 {OpenBLAS 0.3.21 with 8 threads}
scipy:            1.10.1
matplotlib:       3.7.1 {backend=module://backend_interagg}
sklearn:          1.2.2
numba:            Not found
nibabel:          Not found
nilearn:          Not found
dipy:             Not found
openmeeg:         Not found
cupy:             Not found
pandas:           1.5.3
pyvista:          Not found
pyvistaqt:        Not found
ipyvtklink:       Not found
vtk:              Not found
qtpy:             Not found
ipympl:           Not found
pyqtgraph:        Not found
pooch:            v1.7.0
mne_bids:         Not found
mne_nirs:         Not found
mne_features:     Not found
mne_qt_browser:   Not found
mne_connectivity: Not found
mne_icalabel:     Not found

Are projectors on? Like if you click the "Prj" button in the lower right are things checked? If so, turn them all off and you should see that the data does not change. If this is the case then everything is working correctly. A good channel will be included in projection, but once you mark it as bad it gets excluded from projection, which will cause its values to change (along with values of other channels still included in the projection, albeit less noticably in most cases!).

Thanks, @larsoner. If I toggle them all projectors to OFF, there is no change. I didn't know about the projectors earlier. Is there a way to disable them programmatically?


Create work request list page

As a user, I would like to be able to see the work requests for my profile. It should show me actions I can take based on my entitlement. For example, if I have the AssignWork entitlement, and I submit a new work request, I should see the work request with a status indicating it is waiting on the worker. If I am a worker who received the work request, I should be able to accept or reject it.

Created a super basic page (/work-requests/list.html). Needs to be joined to pull work item name and more details like the worker and requestor names, etc.


Add Svelte Inspector Toggle

By default, the inspector toggle button will only be visible in dev env, as it's always set to false in build.
The toggler is useful to easily jump to component level source while developing.

Thank you but I don't think this is necessary at the moment.


Just wondering, when was the last successful build step?

All of them are failing or turned off so I'm just wondering what to install/pull? There are many, many "closed" issues with the Dockerfile, 'sharp', build step yet none of the suggestions from the team have solved the issues.
Many issues are closed before build step is considered.
Is this stable enough to use in production or no?
Again, getting the basic 2.x, 3.0 create-app Dockerfiles to work is incomplete, so it would be good to focus not on getting a dev environment running (since that only takes you so far!) but can anyone confirm this builds without issues with 'sharp', OOTB, without modifications?
I can link to all of the issues I have mentioned but I have a suspicion a lot of it is fresh in memory for the team :) there are a LOT of complaints about 'sharp', dockerfile from vanilla app not working, but they are closed early.

Hey @mxchinegod are you referring to the Payload core codebase?
In that case we have a LOT of tests and a few specific tests are flaky, so the build can show as errored even if there is a flake in a test. We are working toward ensuring that the flakes are ironed out but it can be difficult especially on the E2E side. We tend to prioritize fixes over flakes and then circle back to ensuring tests are as flake-less as possible.

Many issues are closed before build step is considered.

Issues do not necessarily correlate to build steps, so I am not following there, but we try our hardest to keep up with issues that are reliably reproducible and can be demonstrated to be a bug. In practice, many issues are created which do not have a reproduction, are not reproducible even if we wrote our own, or are not related to Payload code. In those cases we do convert to Discussions in order to keep Payload's GitHub issues related to concrete bugs / issues with Payload core code.

Is this stable enough to use in production or no?

2.0 is, but 3.0 is definitely still in beta. There are lots of people that use it in production and we are close to having full stable, but that's kind of a "choose your own adventure" type deal at this point. If you're looking for as much stability as possible I'd stay on 2.0 until we hit 3.0 stable.
It sounds like you are mostly running into Docker / Sharp issues, which is fair, because Sharp is very, very picky. Generally there is an answer (Sharp is incompatible with certain Docker images, etc) and there are many issues but generally what that means for Payload is that we have to go diagnose someone's exact Docker / Sharp / Node / package manager versions and the answer can change depending on the exact combination of those factors. It's exhausting, frankly, and there might not be a single Dockerfile that works for everyone's exact use case. The Dockerfiles that we ship with might work for one machine, but might not for another.
This is more appropriate as a GitHub discussion though, and not an issue, for some of the reasons that I stated above (it's not a reproducible issue with Payload). Happy to keep the conversation going though and if you'd like to point us to an exact error that you're having, which we can reproduce, we would be happy to tackle it!


Bad keyboard mapping in Linux with macOS virtualization

When creating a new Linux VM using the built-in Apple virtualization, the keyboard mapping is incorrect.
I use an Apple French mapping keyboard. And UTM will map the #/@ key to the </> key located next to the left SHIFT. The top key #/@ under ESC is unrecognized. No problem in other virtualization like Parallels, VMware or in UTM using QEMU instead of the Apple virtualization.
On the screenshot below, the mapping is correct, but doesn't match to the real behavior.

Configuration

Until UTM Version: 4.2.5
macOS Version: from macOS 11 to macOS 13
Mac Chip (Intel, M1, ...): Intel

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Backend</key>
	<string>Apple</string>
	<key>ConfigurationVersion</key>
	<integer>4</integer>
	<key>Display</key>
	<array>
		<dict>
			<key>HeightPixels</key>
			<integer>1200</integer>
			<key>PixelsPerInch</key>
			<integer>80</integer>
			<key>WidthPixels</key>
			<integer>1920</integer>
		</dict>
	</array>
	<key>Drive</key>
	<array>
		<dict>
			<key>Identifier</key>
			<string>039CA56B-8098-4D17-A649-C35F8D3037C7</string>
			<key>ImageName</key>
			<string>039CA56B-8098-4D17-A649-C35F8D3037C7.img</string>
			<key>ReadOnly</key>
			<false/>
		</dict>
	</array>
	<key>Information</key>
	<dict>
		<key>Icon</key>
		<string>linux</string>
		<key>IconCustom</key>
		<false/>
		<key>Name</key>
		<string>Ubuntu Jammy Jellyfish</string>
		<key>UUID</key>
		<string>1E7D631B-24C7-438A-8D49-BEB2F061A675</string>
	</dict>
	<key>Network</key>
	<array>
		<dict>
			<key>MacAddress</key>
			<string>e2:6d:cc:32:01:fb</string>
			<key>Mode</key>
			<string>Shared</string>
		</dict>
	</array>
	<key>Serial</key>
	<array/>
	<key>System</key>
	<dict>
		<key>Architecture</key>
		<string>x86_64</string>
		<key>Boot</key>
		<dict>
			<key>EfiVariableStoragePath</key>
			<string>efi_vars.fd</string>
			<key>OperatingSystem</key>
			<string>Linux</string>
			<key>UEFIBoot</key>
			<true/>
		</dict>
		<key>CPUCount</key>
		<integer>0</integer>
		<key>MemorySize</key>
		<integer>4096</integer>
	</dict>
	<key>Virtualization</key>
	<dict>
		<key>Audio</key>
		<true/>
		<key>Balloon</key>
		<true/>
		<key>ClipboardSharing</key>
		<true/>
		<key>Entropy</key>
		<true/>
		<key>Keyboard</key>
		<true/>
		<key>Pointer</key>
		<true/>
		<key>Rosetta</key>
		<false/>
	</dict>
</dict>
</plist>

It's a bug in Apple's virtualization framework. See #5037 and #4041 for example.
Also report on Apple's Feedback Assistant; there are already several on this bug : FB11898180, FB11489872, etc.

Among the new features of apple's virtualization framework for MacOS Sonoma, I see that a new class has appeared:
VZMacKeyboardConfiguration
Perhaps a solution to our ISO keyboard problems and better management of Mac keyboards?
Even if it's too early (we're only in the first beta of Sonoma), are the UTM teams planning to integrate these new features in a future version of UTM?

The problem ultimately remains with Sonoma (Beta 2).
If the support of the function keys and controls of the Mac are appreciable (globe key, sound, multimedia, etc.), the bug of the bad mapping of the ISO keyboards (French, Danish, German, etc.) is unfortunately not always not corrected, while the keyboard works perfectly on the beta directly installed on a Mac, without going through a VM.
Explanation and solution of this bug:
The code for the @ key on a French ISO keyboard is 0Ah, but the code for this key on an ANSI keyboard is 32h (which is the code for the extra key < in ISO). That explains why I don't see the @. It's on the code key 0Ah which does not exist.
The virtualization framework does, for some reason that I cannot explain, this code replacement for the keys, taking into account neither the settings of the keyboard of the host machine, nor the settings of the keyboard of the virtual machine.

Howard Oakley, from the excellent site The Eclecticlight Company has just published a post on this problem and made a bug report to Apple:
https://eclecticlight.co/2023/06/27/keyboard-layouts-in-lightweight-virtualisation/


remove ray

Remove ray dependencies (see more details in https://gitlab.zgtools.net/analytics/artificial-intelligence/ai-platform/sdks/aip-serving-sdk/-/merge_requests/131)

Looks good. In the latest version, they are using a very recent version. So as we are not using ray, when we upgrade the serving SDK, we would first try to keep ray from OSS and see if it's not breaking anything, correct?

Looks good. In the latest version, they are using a very recent version. So as we are not using ray, when we upgrade the serving SDK, we would first try to keep ray from OSS and see if it's not breaking anything, correct?

Yep we can keep ray in the later OSS versions


Easy SSL setup

Provide a docker image that sets up nginx with certbot or a self-signed cert, as a reverse proxy to the http/electrum servers.
For the http api, this could also throw basic http auth into the mix (this does not solve authentication for the electrum server though, which cannot be done with the current electrum protocol and would require a separate authentication layer, like a vpn or an hidden service).
This could also potentially be implemented as part of the rust server itself (there are a few rust libaries for integrating with letsencrypt), but this is quite more complicated and doesn't seem to add much value over the simpler docker image option.

Nginx might be a hassle, what about Caddy?

Nginx supports terminating SSL for TCP servers (Electrum is JSON-RPC over TCP), it seems like Caddy doesn't support that quite yet [0] and is primarily oriented for HTTP servers. But Caddy is very nice and could be a good solution for the HTTP API, thanks for bringing it up as an option.
Regarding Electrum - after giving this some more thought, I'm not sure that bwt should be making it easier to setup SSL for Electrum. If this doesn't also come with an authentication solution, it would give a false sense of security and encourage people to make the servers publicly accessible in a way that could harm their privacy. I wouldn't want to make it appear like I'm giving a Kosher stamp to something that isn't actually safe. To make this private and secure they'll need to also setup something like a VPN, an SSH tunnel or a Tor hidden service -- in which case SSL doesn't really add much anyway.
[0] It looks like it is being worked on but its very early, with no source code published yet.

@shesek What are your requirements? It's working quite well already. Help me understand what you need.


Added Examples Page

I added an examples page. Right now the link for the follow-path example does not work yet as it has not been merged to master. When it has been though, the link should be fine.
@Wikunia - for some reason I am having difficulty displaying a gif inside the table. Could you take a look at what is going on and why I cannot see the gif being rendered? Thanks!

As mentioned I would make this with three columns and one line per example.
The columns are gif, link and used functions. In this case I would mention: follow_path, makebezierpath, appear(:scale)
Don't you think that this will be helpful if people search for follow_path in the docs?
Maybe because it's not much text it can be:
Two column layout: Gif in one and short explanation of what is done with the link and those tag words in the other.
Explanation would be:
Creating a bezier curve to draw a car and let a circle follow a long that path. The animation uses also appear and disappear functionalities to make the animation more pleasing to watch. Blablabla :smile:


NanoDump Bugfixes

Things changed:

File name separator changed to "_" because this character is valid in Windows file names and invalid for hostnames.
Changed the regex to allow more characters. The original regex caused problems with hostnames containing a dash "-", resulting in the module failing to execute. This one should cover most cases. #564 might be related to this, but from what I'm reading in that pull request, that one only seems to cover the unlikely case of a filename that is exactly the same.
Added support for running the module on a Windows attacking system. In Windows nano_path is "%APPDATA%\CME". I also added quotes to some commands to make sure Windows Paths with spaces won't cause issues.
Changed the default Unix nano_path to "/tmp/cme/" in order to be in line with the Windows addition
Updated to NanoDump binary to the latest version from https://github.com/helpsystems/nanodump and added the 32 bit verison.
Implemented some logic in order to detect the victim's windows architecture and select the corresponding version of NanoDump
Some little typo and QoL fixes (includes #575)

I'm open to feedback ;-)

Scrolling through some issues I realised that my first fix would fail to get the dump file for hostnames containing unicode characters.
I rewrote this again to not rely on regex anymore. Instead, I now decided to go with a random 10 character string.
This also saves a bit of time because the "dir" in the temp directory is no longer required.

Ok looks good, I will recompile the binaries myself to check if the base64 is equal :)


Like game

The like button works now!
Test it on the games page when youre logged in

Whenever I'm trying to like a game, it pops up the review modal and asks me to review the game. Going to try to fix now.

Merge fixed it.


[iOS10] Weather and Calendar data are not loading correctly

Some users are reporting that Weather and Calendar data are not loading correctly on iOS 10:

Weather may never hits a callback
Calendar displays events from a subset of available (and enabled) calendars.

Some further details are available at: https://github.com/Matchstic/Xen/issues/53 and https://github.com/Matchstic/Xen/issues/52

In addition, the issues presented by #11 will compound this issue for Weather data.


field_name override doesn't appear to be working

Describe the Bug
In previous versions of strawberry-graphql-django, this code worked correctly:
import strawberry.django
from django.db import models

class MyModel(models.Model):
    ... other fields ...
    category = models.ForeignKey(Category, on_delete=models.PROTECT, related_name='packages')

@strawberry.django.type(MyModel, name='MyModel')
class MyModelGQL:
    category: int = strawberry.django.field(field_name='category_id')

Using the int type annotation and field_name='category_id' would mean that selecting the category field in GraphQL should return an int (equivalent to model.category_id) for the foreign key, but since the latest update this is resolving to the actual Category (or whatever foreign key'd model) instance - resulting in this:
Int cannot represent non-integer value: <Category instance>

GraphQL request:5:5
4 |     name
5 |     category
  |     ^
6 |   }
Traceback (most recent call last):
  File "/Users/colinmcdonald22/.local/share/virtualenvs/Backend-HOVHWeLv/lib/python3.10/site-packages/graphql/type/scalars.py", line 56, in serialize_int
    num = int(output_value)  # raises ValueError if not an integer
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'Category'

It seems like the int annotation is applying correctly, but the field_name='category_id' override (which should change the resolver impl) isn't doing anything.
System Information

Operating system: macOS / Python 3.11
Strawberry version (if applicable): strawberry 0.193.1 / strawberry-graphql-django 0.10.2

Additional Context

@colinmcdonald22 should be solved in 0.10.3! :)


To_Do list discuss and expand

Needed Additional Features
- Loose coupling of Litentry NFT pallet
- Add fractional nft function in Fairsquares pallet
- Rewrite FairSquares pallet around Litentry nft pallet, instead of Anmol nft pallet
- Voting system for a proposal approval (https://docs.substrate.io/rustdocs/latest/pallet_collective/index.html).
- Proposal destruction function (proposal not approved, or expired projects)
- Design & Implementation of the logic behind the choice of the contributors for each proposal
- Design & Implementation of the rent payment logic.

Closed this as most issues #19 #20 #29 #28 #30 #25 have now their own tracking-issues


Decide whether we should install license files

Some of our packages currently install their license files to the reMarkable. We should decide whether this is needed and whether we actually want this, considering the low amount of space available on the device.

I believe some licenses require the license to be distributed with the application.

I believe some licenses require the license to be distributed with the application.

Indeed. I believe that is the case for GPL and MIT, for example.

Indeed. I believe that is the case for GPL and MIT, for example.

https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
on debian, they require copyright files per package but they usually point to the licenses in /usr/share/common-licenses. i think we can auto generate these files

https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
on debian, they require copyright files per package but they usually point to the licenses in /usr/share/common-licenses. i think we can auto generate these files

on debian, they require copyright files per package but they usually point to the licenses in /usr/share/common-licenses. i think we can auto generate these files

Do you know what happens if we encounter a new license that doesn't exist in that common location? Can a package conditionally add a license?

on debian, they require copyright files per package but they usually point to the licenses in /usr/share/common-licenses. i think we can auto generate these files

Do you know what happens if we encounter a new license that doesn't exist in that common location? Can a package conditionally add a license?

if it's non standard, the text of the license will be in the copyright file instead of the path of the license

if it's non standard, the text of the license will be in the copyright file instead of the path of the license

https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
on debian, they require copyright files per package but they usually point to the licenses in /usr/share/common-licenses. i think we can auto generate these files

Arch also does this.

Indeed. I believe that is the case for GPL and MIT, for example. Also, Entware does not seem to provide license files with their packages.

That's very odd, someone should probably raise an issue with them as they are breaking the license by doing so. Unless they assume those licenses are already in the host's root filesystem?

https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile
on debian, they require copyright files per package but they usually point to the licenses in /usr/share/common-licenses. i think we can auto generate these files

Arch also does this.

Indeed. I believe that is the case for GPL and MIT, for example. Also, Entware does not seem to provide license files with their packages.

That's very odd, someone should probably raise an issue with them as they are breaking the license by doing so. Unless they assume those licenses are already in the host's root filesystem?

For reference, the way Arch does it is by providing the licenses package, which is part of the base install, and installs licenses to /usr/share/licenses/common. It is then up to packagers to check whether their licenses used by the package are among those provided, in which case it can be referenced in the package's build script and metadata by a name such as "GPL3" or "Apache" or what have you. If the package uses a license which isn't part of the licenses package, then the license is listed as "custom:" and any such license is installed to /usr/share/licenses/. Note that this includes many BSD/ISC-style licenses, because they include non-generic text such as the name of the program and the author(s); fortunately, these also tend to be short.


Usage inside ReactJS

This is a fantastic implementation of pivot tables in js and I was wondering if it can be used with React.
I have read previous issues regarding the usage with AngularJS and I was wondering if anyone has tried using it inside React? How would it cooperate with the Virtual DOM?

The virtual DOM would not be able to do much with this library, and you would have to force a re-render. You may want to use http://orbjs.net/ instead.

Update: I have successfully used this library with React :)

Would you mind sharing your integration?

 )

I am trying to use this pivottable in my reactjs project. Firstly I installed jquery and this library using npm. Then, I am now trying to pivot a given data, and it seems that using $('....').pivot is working however $('....').pivotUI is not working, it gives an this error :

Can you please help me out!
Plus, when I am using $('....').pivot, the css is not showing up:

You need jquery-ui as well :)

@nicolaskruchten First of all thank you so much for this pivot table.
I'm trying this out with react right now and it feels like a bit of a hack... separately telling the pivottable to render in componentDid(Mount|Update). Also I've been trying to avoid including jQuery but for this pivottable i'm making an exception. Is this the way you see this all working for the forseeable future?
Thank you,
+Nadim

@nadim it is a bit of a hack, but it's pretty justified in this case because every time you change anything in the input, the whole table gets thrown away and redrawn, so I doubt that React's virtual DOM adds any value here.
I've thought about rewriting this library in React but I just haven't had/likely won't have the time to manage what would effectively be a fork, and in any case I've been moving away from React towards Mithril in my own projects :)

great thank you for the response and useful info about the redraw behaviour.

I experienced the same pivot working and pivotUI not working when I tried using pivottable with the slim build of jQuery  3.x.  Here are the lines that cause the first error/failure.  I am assuming this is caused by the deprecation of bind (see [http://api.jquery.com/bind/]), and that the slim build does not include deprecated functions.  Using the full 3,2.1 build of jQuery, pivottable still worked great.

This is how you utilize pivottable within reactjs https://github.com/kurtzace/pivottableandreact

@kurtzace thanks for sharing!
I should note that I've recently been hired to create an official React-only (no jQuery) port of this library, and the work is underway here: https://github.com/plotly/react-pivottable
I expect a working release sometime in October, as I'm only working on this 1 day/week at the moment.

If anyone wants to give feedback on the React port, I would greatly appreciate it! It's available here https://react-pivottable.js.org/ :)

It's very close to being released, maybe a week!


Negative one item stack quantities

API | Common
As discussed at https://github.com/SpongePowered/SpongeAPI/issues/1392, a -1 quantity would be useful for ignoring stack size differences with Inventory#query(ItemStack).
In my implementation I have added ItemStack.Builder#anySize which can be used for querying inventories.

And as mentioned here it would be far better to decouple these features from the quantity into a different solution.

And as mentioned here it would be far better to decouple these features from the quantity into a different solution.

What do you think about having a zero quantity?

Api features relying on glitches in the base game should generally be avoided because they because very subject to breakages in a future game update.

Zero-quantity is helpful with inventories, as mentioned here.

What do you think about having a zero quantity?

I managed to crash the client when trying to collect a zero quantity stack onto cursor (double click). Not great.

And as mentioned here it would be far better to decouple these features from the quantity into a different solution.

I have changed it to the suggested solution.

I'm pretty sure that negative item stack quantities is no longer valid in 1.11.

@gabizou I poked into the chain of issues connected to the -1/generally negative item quantities and found that people have may have been merging two separate issues. One issue is about the need for a generic ItemStack that matches any size for a generic Inventory#query(ItemStack), which would use a -1 quantity except it can't be built that way. The other is about 0 sized stacks and -1 sized stacks for shops.
The first should be able to be handled with an internal attribute entirely disconnected from quantity right? (That seems the proper solution regardless, unless an abstraction of a fully spec'd item would replace this use of ItemStack That appears to be what this issue is about and the title (and implementation) should likely be updated accordingly.
The other issue may be invalidated by the changes you believe 1.11 has. Are zero quantity stacks still valid?

Zero quantities are no longer valid.


[WIP] Update a development dependency rr to use the latest version.

I want to use latest version rr 1.2.
https://rubygems.org/gems/rr
Is it possible?
I updated as ~> X.Y to avoid below warning.
-  s.add_development_dependency "rr",           "~> 1.0.4"
+  s.add_development_dependency "rr",           "~> 1.2"

$ gem build rspec-core.gemspec
...
WARNING:  pessimistic dependency on rr (~> 1.0.4, development) may be overly strict
  if rr is semantically versioned, use:
    add_development_dependency 'rr', '~> 1.0', '>= 1.0.4'
...
WARNING:  See http://guides.rubygems.org/specification-reference/ for help
  Successfully built RubyGem
  Name: rspec-core
  Version: 3.8.pre
  File: rspec-core-3.8.pre.gem

rr is only used internally by us for testing compatibility, it shouldn't be necessary to update it for you to use it.

@JonRowe okay. The reason is correctly not "I" but we in Fedora Project (RPM Based Linux).
On Fedora Project, we are publishing rspec as RPM package. To publishing it, we need to run unit tests with registered rr RPM package in Fedora Project.
rr is going to be the latest version in Fedora. So, I want to pass tests of rspec-core with the rr.
But I see some tests are failed in Travis CI.
What is the possible way to use latest rr?
If I will send PR to fix the tests, are you fine to use the latest version rr?

Yes

...with the caveat that we don't want to break users that are running the older version of RR.  We don't need to build against both versions of RR (IMO) but should ensure any changes you make still support the older version.

@JonRowe okay.

...with the caveat that we don't want to break users that are running the older version of RR. We don't need to build against both versions of RR (IMO) but should ensure any changes you make still support the older version.

@myronmarston rr is a development dependency used internally. Not runtime dependency of rspec-core. Do we have to support the rr old version for users? (= contributors?)
We might be able to select a good timing to merge this PR not to surprise users.
For example we can merge it at new minor version release RSpec 3.8.0.
I am fine that this PR is not merged soon.

@myronmarston rr is a development dependency used internally. Not runtime dependency of rspec-core. Do we have to support the rr old version for users? (= contributors?)
We might be able to select a good timing to merge this PR not to surprise users.
For example we can merge it at new minor version release RSpec 3.8.0.
I am fine that this PR is not merged soon.

rr is essentially an optional runtime dependency.  RSpec-core is able to integrate with multiple mocking libraries (rspec-mocks, flexmock, rr, mocha).   It does not have a hard dependency on any of them, so we do not declare a runtime dependency on any of them.  rspec-core users can use any of them or none of them as desired.
Given that, ensuring we work with the latest version of rr is definitely worthwhile (so I'm glad you brought this up!) but it's also important that we don't break the integration with older versions of rr that rspec-core users may be using.  Our current interpretation of SemVer is that we can only drop support for old versions of a dependency in a major version change (such as RSpec 3.x -> 4.0).

@myronmarston okay, now I understood why you guys were sensitive about updating rr.
I will consider "we don't break the integration with older versions of rr".

Do we still want to work on this? I think we can close it. :)

Thanks for reminding on this.
Sorry about it. No, I give up this task. Free free to close this ticket.


Add LIndex command

Test cases added.

Related to #123

review @icemint0828

@roseduan
Fix conflicts, please check.

Hi, @roseduan.
Sorry, is there something wrong with my PR?

Hi, @roseduan.
If you have time, may I ask you to check the code?
If something is wrong with me, I would like to correct it.
I am not sure what is going on because there has been no movement for a long time.

sorry, a little busy before

It's ok!
Thanks for your review.


CI: Store test metrics

Description
Per title. @janisz O ised v0.0.8 as I wasn't sure about the extra 0 in the v0.0.07, typo? or?...
Checklist

[ ] Investigated and inspected CI test results

Testing Performed
CI is sufficient. Should see lots of test results in BQ.

Do you think we should also gather unit tests stats?
https://github.com/stackrox/stackrox/blob/master/.github/actions/junit2jira/action.yaml#L32

Do you think we should also gather unit tests stats? https://github.com/stackrox/stackrox/blob/master/.github/actions/junit2jira/action.yaml#L32

Yeah, I think it would be useful. I didn't want to tackle it yet though because it'll need a GCP login and it doesn't feel right to just hack that in to the junit2jira action without a bit of refactoring.


[Plugins] Crash: Opening more than one of the same plugin window crashes Live

Might be DAW-specific, might be Windows specific, but after looking at some of the other issue, this seems to be a common one.
Happens only if you try to open the plugin windows of two of the same plugin (for instance, spectral compressor)
Plugins still work if you have two of them in series or parallel, you jsut can't have them both open at the same time.
Windows 11 64bit
Ableton Live 11, VST3

JIT Debugging is available for the Live crash in Visual Studio, but I don't know how much use that would be :(

It indeed happens regardless of host. I still need to set up a Windows VM to properly debug this (it's almost certainly something in baseview). I'll try to get around to that soon.

Got a VM up and running. The problem is Vizia (the GUI framework used by these plugins) using global state. Specifically, this thing gets shared between plugin instances (when it obviously shouldn't): https://github.com/vizia/vizia/blob/34be9184cd98f3d795d1a73eb9bdccd25b250165/crates/vizia_core/src/context/mod.rs#L63-L64
I have not yet looked into the difficulty of removing these global from Vizia.

This should now be fixed as of 9e2b9cc06eace2f05d430661873202a2154d0f05.
The underlying issue is an architectural choice in the GUI framework used by these plugins, and there's sadly no satisfactory solution for this. But the plugins should now at least no longer crash when using multiple instances on Windows and macOS!