Memflow build issue: define a minimum rust version

Hi,
It seems that memflow cannot be compiled with the current rust version of Debian sid
https://packages.debian.org/sid/cargo (0.47)
error[E0658]: const generics are unstable
   --> /root/.cargo/registry/src/github.com-1ecc6299db9ec823/dataview-0.1.2/src/lib.rs:170:27
    |
170 | unsafe impl<T: Pod, const N: usize> Pod for [T; N] {}
    |                           ^
    |
    = note: see issue #74878 <https://github.com/rust-lang/rust/issues/74878> for more information

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `dataview`.

Do you think you could declare a minimum rust version in your README ?
Thanks !

Thanks for the hint! I updated the Readme on the next branch to reflect this requirement!
https://github.com/memflow/memflow/tree/next#compilation-support


Enable clock_gettime on wasi

I think this mostly addresses the issues that were brought up in #1307 regarding clock ids; I made clockid_t a wrapper struct because it needs to be Send and Sync to be used in a constant, and I figured it was opaque in wasi-libc anyway. Instead of static ZSTs, I just made them u8s, since I figured it's very unlikely that wasi-libc would change them from struct __clockid { __wasi_clockid_t id; } to struct __clockid {}, and it'll always be valid to treat a static as a /(u8)+/. One thing I was wondering about, should I add a cfg check to build.rs checking for core::ptr::addr_of? Since I think(?) using that would fix any issue of __clockid becoming a "zst" struct in the future.

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit cd57a938cfab04c38c38bb2d5d8be49238c3d43f has been approved by Amanieu

:hourglass: Testing commit cd57a938cfab04c38c38bb2d5d8be49238c3d43f with merge 072d6de366123d32cf7c7b76aa6e37ce5a306404...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 072d6de366123d32cf7c7b76aa6e37ce5a306404 to master...


Fix incorrect GitHub url parameter validation

Properly validates that either a server_url and path are provided, or a full url.
This resolves #9922.
Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context
Fixes #9922 by allowing GitHub urls to be constructed from only the full url.
Tested with additional test cases in fastlane/spec/actions_specs/github_api_spec.rb

I signed the CLA.


SOLR-16403: Cluster Singleton to remove inactive Shards

https://issues.apache.org/jira/browse/SOLR-16403
Description
This PR proposes a configurable cluster singleton plugin to remove inactive shards.
I'd like to get some feedback from the community on whether this is a reasonable thing to do, or if there are other preferred alternatives.
Solution
Adds a Cluster Singleton plugin implementation that can be configured to run periodically and delete inactive shards that have exceeded a TTL period.
Tests
Tests are included. Coverage may be expanded if we move forward
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[x] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

PR Run Status

AI Based Review: Successful
Static Analysis: Failure - Failed to execute static code analysis using FBinfer.

PR Analysis

Main theme: Implementation of a Cluster Singleton plugin for removing inactive shards in Solr.
PR summary: This PR introduces a Cluster Singleton plugin, InactiveShardRemover, aimed at identifying and removing inactive shards that have exceeded a Time-To-Live (TTL) period. It configures a scheduled task to periodically check and delete these shards, thereby helping in maintaining the health and efficiency of the Solr cluster.
Type of PR: Enhancement
Score (0-100, higher is better): 85
Relevant tests added: Yes
Estimated effort to review (1-5, lower is better): 2
The PR is well-structured with a clear purpose. It includes tests which should make the review process straightforward. However, the complexity of the changes and the potential impact on cluster behavior necessitate a thorough review.

PR Feedback

General suggestions: The implementation of the InactiveShardRemover as a Cluster Singleton for removing inactive shards after a TTL is a valuable addition to Solr's maintenance capabilities. The approach of scheduling periodic checks to remove expired shards can help in keeping the cluster lean and efficient. However, it's crucial to ensure that the removal process does not inadvertently affect the cluster's stability or data integrity. To further enhance this feature, consider implementing safety checks that prevent the removal of shards if they are temporarily marked as inactive due to network partitions or other transient issues. Additionally, providing more configurability for the TTL and deletion criteria could allow administrators to tailor the feature to their specific needs. Finally, extensive testing in simulated production environments is recommended to ensure that the feature behaves as expected under various failure scenarios.

Code feedback
file: solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemover.java

Suggestions:

Consider implementing a dry-run mode that logs which shards would be deleted without actually performing the deletion. This can be useful for administrators to safely test the impact of the InactiveShardRemover on their cluster. [important] Relevant line:In solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemover.java at line 85

+ implements ClusterSingleton, ConfigurablePlugin<InactiveShardRemoverConfig> {

Add metrics or logging to track the number of shards checked and deleted per cycle. This can help in monitoring the effectiveness of the plugin and troubleshooting issues. [important] Relevant line:In solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemover.java at line 176

+ inactiveSlices.stream().limit(maxDeletesPerCycle).forEach(this::deleteShard);

Ensure that the scheduled executor service is properly managed to avoid potential memory leaks. Consider using a try-with-resources statement or similar mechanism to ensure that resources are freed up. [important] Relevant line:In solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemover.java at line 132

+ executor = Executors.newScheduledThreadPool(1, new SolrNamedThreadFactory(PLUGIN_NAME));

Consider adding a feature to notify administrators before deleting shards, possibly through email or a dashboard notification. This could provide an additional layer of safety before data deletion occurs. [medium] Relevant line:In solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemover.java at line 190

+ private void deleteShard(final Slice s) {

file: solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemoverConfig.java

Suggestions:

Validate configuration parameters (e.g., scheduleIntervalSeconds, ttlSeconds, maxDeletesPerCycle) to ensure they are within reasonable limits. This can prevent misconfigurations that could lead to aggressive shard deletions or performance issues. [important] Relevant line:In solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemoverConfig.java at line 47

+ final long scheduleIntervalSeconds, final long ttlSeconds, final int maxDeletesPerCycle) {

Allow dynamic reconfiguration of the InactiveShardRemoverConfig without needing to restart the Solr cluster. This would enable administrators to adjust settings in response to the cluster's current state. [medium] Relevant line:In solr/core/src/java/org/apache/solr/cluster/maintenance/InactiveShardRemoverConfig.java at line 28

+ public InactiveShardRemoverConfig() {

file: solr/core/src/test/org/apache/solr/cluster/maintenance/InactiveShardRemoverTest.java

Suggestions:

Expand test coverage to include scenarios where shards become inactive due to network partitions or other transient conditions. Ensure that the plugin does not delete these shards prematurely. [important] Relevant line:In solr/core/src/test/org/apache/solr/cluster/maintenance/InactiveShardRemoverTest.java at line 210

+ private void setAllShardsInactive(final String collectionName) {

We now have this running in production and have been able to see it working as expected, so I'm taking the PR out of draft status.
@dsmiley fyi.

Test failure is reproducible on the main branch with
gradlew :solr:core:test --tests "org.apache.solr.cloud.OverseerStatusTest.test" -Ptests.jvms=96 "-Ptests.jvmargs=-XX:TieredStopAtLevel=1 -XX:+UseParallelGC -XX:ActiveProcessorCount=1 -XX:ReservedCodeCacheSize=120m" -Ptests.seed=9491A2C35A439099 -Ptests.timeoutSuite=600000! -Ptests.file.encoding=US-ASCII

I already reported org.apache.solr.cloud.OverseerStatusTest.test -- https://github.com/apache/solr/pull/2230#issuecomment-1984524318
BTW this new BitoAgent AI bot reviewer thing is wild.  Not sure it's that helpful.

For all the AI fanciness of that bot, some good old fashioned static analysis is all we would have liked to point out that we are adding methods that are not used (leading to test flapper and follow-up PR).  I suspect the "Muse" bot that was cancelled ~6 months ago would have caught this.


Add "Blazored Typeahead" to Libraries & Extensions

Awesome component by @chrissainty

Thanks for the submission!


About visualization

Hello,
I thoroughly enjoyed reading your paper "LION: Linear Group RNN for 3D Object Detection in Point Clouds."
I am also interested in conducting research using autonomous driving datasets, and I have a question regarding data visualization. Could you share how you approached the visualization in your work and point me to the code where I can find it?
Thank you.

@hdddhdd Thanks for your attention! We will release this code of this visualization. @deepinact

Thank you for your response!
I'm not too familiar with this, so I was wondering what viewers researchers commonly use for 3D autonomous driving datasets?

@hdddhdd Hi, open3d or mayavi may be a good choice. You could refer to the open-source code of OpenPCDet (https://github.com/open-mmlab/OpenPCDet/blob/master/docs/DEMO.md) and have a try.

Thank you for the detailed response😊!! I will try those things.

I've been quite busy lately, but I'll clean up the code for the visualization of the BEV perspective and feature map and release it as soon as possible afterward. As for the visualization of 3D perspective, we achieved that using Open3D.


Not working with Sonatype Nexus raw repositories

The webdav resource cannot currently be used with Sonatype Nexus, but that is a known limitation of Nexus
see https://issues.sonatype.org/browse/NEXUS-14433

Closing as known issue


BUG: error-context not provided for "insufficient funds"

I was testing UX for TX errors in my app.
When I triggered a TX that failed to build due to "Insufficient funds for lovelace", the message was logged as a "warning" (as seen here), but the error in my catch-block resolved with an empty message:
try {
    const unsignedTx = await tx.build() // <--- console.warn triggered by Mesh
    const signedTx = await wallet.signTx(unsignedTx)
    const txHash = await wallet.submitTx(signedTx)
} catch (error: any) {
    console.error(error)
    // Error: txBuildResult error:
    // at CSLSerializer.serializeTxBody (index.js:1076:13)
    // at MeshTxBuilder.complete (index.js:1391:33)

    console.error(error?.message)
    // txBuildResult error:
}

Versions:
{
    "@meshsdk/core": "^1.7.3",
    "@meshsdk/react": "^1.7.3",
}

After digging further, I can confirm the source of the error is here:
https://github.com/MeshJS/mesh/blob/b35b4646c6e412840b3f9bca61b4c1cefbf33129/packages/mesh-core-csl/src/core/serializer.ts#L74
It seems the get_error() method does not work, or resolves with an empty string.


Add Enterprise Management service to project

PR summary
This PR adds the enterprise-management service and test code to the project.
Fixes: n/a
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information
Ignore the first commit (global catalog).   That is contained in an upstream PR.

@mahakAg I had to de-couple the add-em branch from the global-catalog changes as this PR got inadvertently backed up behind the add-gc feature branch.   There is now a new add-em branch which this PR is associated with.   You will need to remove (or rename) your local "add-em" branch, then do a git fetch origin and then check out the add-em branch again and pull the changes down.

:tada: This PR is included in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Added AWS_SECURITY_TOKEN env var

AWS_SECURITY_TOKEN is a legacy env var, replaced by AWS_SESSION_TOKEN.
It is still required by some tools using boto2 like Ansible dynamic EC2 inventory.

Reviews
0/1
Message

More info

+1

Reviews
1/1
Message

grahamjenson
1
+1

Pull request is reviewed and can be merged to master!
More info

Reviews
1/1
Message

grahamjenson
1
approved

Pull request is reviewed and can be merged to master!
More info

Cheers :)


Tween onLoop not firing in v. 2.4.6

onLoop event isn't firing in 2.4.6. Works in 2.3.0 when I tested. Leg is a sprite whose parent is a Phaser.Group whose parent is a Phaser.Group whose parent is the game world (Game World -> Group -> Group -> Sprite) - not sure if that has anything to do with it but worth testing if you can't recreate the problem with just the code below (I've noticed other odd behaviors with this setup, but could be separate issues).
Note that yoyo and repeat are set. The event doesn't fire if yoyo is turned off as well. leg is the sprite I'm tweening in the code below.
function tweenLeg(leg) {

    var pauseTime = 110;

    var legTween = game.add.tween(leg).to({
        x: 5,
    }, 100, Phaser.Easing.Default, false, 0, -1, true);

    legTween.onLoop.add(function() {
    console.log('this never fires in phaser 2.4.6 but does fire in 2.3.0!');
        legTween.pause();
        setTimeout(function() {

            legTween.resume();

        }, pauseTime);

    });

    legTween.start();

}

onLoop
Thanks for submitting this issue. We have fixed this, and the fix has been pushed to the dev branch.


BugFix: #42068: Support Field Removals for IstioOperator

Please provide a description of this PR:
Issue https://github.com/istio/istio/issues/42068
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[X] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[X] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

Hi @Kaushal28. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

I figured out the root cause. It is not using server side apply (SSA) currently. In client side apply, it is using github.com/evanphx/json-patch/v5 library, that is implementing JSON patch merge based on this RFC: https://www.rfc-editor.org/rfc/rfc7396. According to this, JSON patch needs to set null in the value of the key that needs to be removed from the target JSON object. However, in this case, user is completely removing the field and hence that field is not getting updated in the target JSON.
One option is to use server side apply, which is available from K8s 1.16+. As the latest versions of istio only support 1.16+ K8s version (reference), I believe this PR will fix the issue for them. For the earlier versions, a fix for this will increase client side complexity as we will have to somehow figure out a way to determine removed fields and set null for them.
I have tested this change in my local, I can also add a few tests for this if this change makes sense. Let me know your thoughts.

/ok-to-test

@Kaushal28: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Kaushal28: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Kaushal28: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-pilot-multicluster

integ-security-multicluster_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Kaushal28: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-pilot-istiodremote-mc

integ-pilot-multicluster_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-pilot-multicluster

integ-security-multicluster_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-security-multicluster

integ-telemetry-mc_istio
495595f8504cde7f590aa1cf21b797b1fa7dafd0
link
true
/test integ-telemetry-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest-required

/test all

@Kaushal28: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
a982bfac0ce0bfd6801fd9b30384e65bef1606ff
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test all

/test all

/test all

@Kaushal28: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
43a321e5d423d2265276c4477060b6e8dd50be6a
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test unit-tests-arm64

@Kaushal28: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio
59efe5f6aa7a0bdc4e8d028d5d359dd7cdd22784
link
true
/test integ-ambient

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-ambient

LGTM, assigned some folks more familiar with this though

@richardwxn @ostromart Could you please review the changes? Any suggestions/feedback would be really helpful. Thanks.

@hanxiaop added a release note.

@howardjohn @richardwxn @ostromart Could you please review the changes? Any suggestions/feedback would be really helpful. Thanks.

@cnvergence @zirain is it now mergeable then? Let me know any thing is still pending.

I ran make gen after all the approvals and it changed comments in a few generated files and added a new reviewer. Could anyone please have a look?

Hi @zirain, I ran make gen after all the approvals and it changed comments in a few generated files and added a new reviewer. Could you please have a look?

Can anyone please review and provide feedback on this PR?

Hi @howardjohn, @cnvergence Could you please look into this PR? Merge is pending since long time just because of changes in comments of a few auto generated files. Let me know if anything else is missing. Thanks.

@Kaushal28: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

bookinfo-build_istio
345d5c7d1b079a0c114dee9846c6b680e4835df3
link
true
/test bookinfo-build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/retest bookinfo-build_istio

@cnvergence: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test analyze-tests
/test bookinfo-build
/test gencheck
/test integ-ambient
/test integ-basic-arm64
/test integ-cni
/test integ-distroless
/test integ-ds
/test integ-helm
/test integ-ipv6
/test integ-operator-controller
/test integ-pilot
/test integ-pilot-istiodremote
/test integ-pilot-istiodremote-mc
/test integ-pilot-multicluster
/test integ-security
/test integ-security-istiodremote
/test integ-security-multicluster
/test integ-telemetry
/test integ-telemetry-istiodremote
/test integ-telemetry-mc
/test lint
/test release-notes
/test release-test
/test unit-tests
/test unit-tests-arm64

The following commands are available to trigger optional jobs:

/test benchmark
/test integ-assertion

Use /test all to run the following jobs that were automatically triggered:

analyze-tests_istio
gencheck_istio
integ-ambient_istio
integ-basic-arm64_istio
integ-cni_istio
integ-distroless_istio
integ-ds_istio
integ-helm_istio
integ-ipv6_istio
integ-operator-controller_istio
integ-pilot-istiodremote-mc_istio
integ-pilot-istiodremote_istio
integ-pilot-multicluster_istio
integ-pilot_istio
integ-security-istiodremote_istio
integ-security-multicluster_istio
integ-security_istio
integ-telemetry-istiodremote_istio
integ-telemetry-mc_istio
integ-telemetry_istio
lint_istio
release-notes_istio
release-test_istio
unit-tests-arm64_istio
unit-tests_istio

In response to this:

/retest bookinfo-build_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/test bookinfo-build

@Kaushal28 please review the conflicts


Set grpcio minimum version to 1.59.3 so that Alpine py3-grpcio can be used

Motivation
When using the Alpine base image in Pulsar, there's a need to compile grpcio from source when 1.60.0 version is required. It's better to allow grpcio version 1.59.3 so that Alpine's py3-grpcio can be used to fulfill the requirement.
Please see https://github.com/apache/pulsar/pull/22613 for more context.
Modifications

downgrade grpcio dependency to 1.59.3

Additional context

there's no specific minimum version constraint originating from pulsar-client-python

grpcio is required by apache-bookkeeper-client. the dependencies are defined in https://github.com/apache/bookkeeper/blob/master/stream/clients/python/setup.py the version in this file is >= 1.8.2

the grpcio minimum version was set to 1.60.0 in this commit: https://github.com/apache/pulsar-client-python/commit/162afd53bda321992223cb209a509ee1c46f870a . The referenced CVE requires 1.53.0 , so there doesn't seem to be any reason why we couldn't downgrade to 1.59.3 .

I suggest using the 1.53.0 as minimum version, just for consider the multiple os.

I suggest using the 1.53.0 as minimum version, just for consider the multiple os.

There might be other CVEs. Which OS do you have in mind?

There might be other CVEs.

Good catch, see https://github.com/advisories/GHSA-p25m-jpj4-qcrr
Must be equal to or greater than 1.55.3.

Which OS do you have in mind?

Now it seems that only alpine-3.18.
For other OS, the users can use the pip to install the grpcio.

Any updates?

Do you have a release plan?  If not, the pulsar 3.3.0 arm image will take about 2 hours to build the grpcio wheel, please see https://github.com/nodece/pulsar-python-deps-build/actions/runs/8891459473/job/24418839959#step:6:315 for details.


PNT-127 Performance API

https://github.com/pegnet/pegnet/issues/127
Unfortunately because of go's json marshaller, the histogram is sorted lexicographically rather than numerically. Maybe there's an easy way to override it? Or a different format?
Example CLI Command:
pegnet performance prototypeminer001 --start -144 | jq
Example Request:
curl -X POST localhost:8099/v1 --header "Content-Type: application/json" --data '{"method": "performance", "params":{"block_range":{"start":-144}, "miner_id":"prototypeminer001"}}' | jq

Example Response:
{
  "result": {
    "block_range": {
      "start": 7,
      "end": 151
    },
    "submissions": 40,
    "rewards": 18050,
    "difficulty_placements": {
      "1": 7,
      "10": 40,
      "100": 40,
      "1000": 40,
      "10000": 40,
      "25": 40,
      "250": 40,
      "2500": 40,
      "5": 26,
      "50": 40,
      "500": 40,
      "5000": 40,
      "count": 40,
      "sum": 223
    },
    "grading_placements": {
      "1": 4,
      "10": 36,
      "11": 40,
      "12": 40,
      "13": 40,
      "14": 40,
      "15": 40,
      "16": 40,
      "17": 40,
      "18": 40,
      "19": 40,
      "2": 7,
      "20": 40,
      "21": 40,
      "22": 40,
      "23": 40,
      "24": 40,
      "25": 40,
      "26": 40,
      "27": 40,
      "28": 40,
      "29": 40,
      "3": 12,
      "30": 40,
      "31": 40,
      "32": 40,
      "33": 40,
      "34": 40,
      "35": 40,
      "36": 40,
      "37": 40,
      "38": 40,
      "39": 40,
      "4": 15,
      "40": 40,
      "41": 40,
      "42": 40,
      "43": 40,
      "44": 40,
      "45": 40,
      "46": 40,
      "47": 40,
      "48": 40,
      "49": 40,
      "5": 23,
      "50": 40,
      "6": 26,
      "7": 28,
      "8": 32,
      "9": 34,
      "count": 40,
      "sum": 223
    }
  },
  "error": null
}

So using these results, you can compute the following stats for prototypeminer001:

average grading rank when they make it in the top 50: 223 / 40 = 5.575
percentage of submissions that made it into the top 5 ranked by difficulty: 26 / 40 = 0.65

I think the difficulty_placements should only bin to 50, then +Inf. In the future we can optimize to only hash the top 50 honest records, and that would break this api if people rely on it.
Maybe provide some stat like the avg difficulty for the last place? So people can see what the min difficulty is?

Agree with the reducing of hash power buckets, changing that now.
Not sure if the average minimum difficulty belongs in this call though, as that is regarding the entire network of miners rather than just the stats of this individual one


[UPDATE] SAP Installation Issue[BUG]

We cloned the latest release v 3.6.1 into our local repository to install SAP.
We are facing the issue with SAP Installation with below error,

As it has few dependencies with workload zone deployment, we tried to redeploy the workload zone and encountered the error with private dns zone.

[UPDATE]
This issue is with network logical name (network_logical_name = "yyy") , Ideally it should pick the network logical name instead it is picking from the Folder Name (i.e. Sandbox-WEEU-SAP01-INFRASTRUCTURE)

Hi @nehavijpaur
This will be fixed in release 3.8


DataProtection - CreateEncryptor has System.NotSupportedException: Method is not supported

I have 4 apps that shared the data protection with certificate for cookie authentication using these codes:
            services.AddDataProtection()
                .PersistKeysToFileSystem(new DirectoryInfo(imyDataProtectionPath))
                .ProtectKeysWithCertificate(certificate)
                .SetApplicationName(MyAppName);

App1 and App2 has target netcoreapp2.1
   <TargetFramework>netcoreapp2.1</TargetFramework>
App3 and App4 has target net461 as they need to use some legacy .Net SDK components
   <TargetFramework>net461</TargetFramework>
App1 will create a protected cookie, App2, App3 and App4 will read that cookie and unprotect it.
Before I add the .ProtectKeysWithCertificate(certificate), they all works fine.   But after I add that ProtectKeysWithCertificate, in some of the servers, I get this exception in App2 and App3
20181018 20:47:16,761 WARN  [DefaultKeyResolver] Key {4076b197-22b0-4b75-b43c-83b92caa08b5} is ineligible to be the default key because its CreateEncryptor method failed. [(null) (null):19 ]
System.NotSupportedException: Method is not supported.
   at System.Security.Cryptography.RSA.DecryptValue(Byte[] rgb)
   at System.Security.Cryptography.RSAPKCS1KeyExchangeDeformatter.DecryptKeyExchange(Byte[] rgbIn)
   at Microsoft.AspNetCore.DataProtection.XmlEncryption.EncryptedXmlDecryptor.EncryptedXmlWithCertificateKeys.GetKeyFromCert(EncryptedKey encryptedKey, KeyInfoX509Data keyInfo)
   at Microsoft.AspNetCore.DataProtection.XmlEncryption.EncryptedXmlDecryptor.EncryptedXmlWithCertificateKeys.DecryptEncryptedKey(EncryptedKey encryptedKey)
   at System.Security.Cryptography.Xml.EncryptedXml.GetDecryptionKey(EncryptedData encryptedData, String symmetricAlgorithmUri)
   at System.Security.Cryptography.Xml.EncryptedXml.DecryptDocument()
   at Microsoft.AspNetCore.DataProtection.XmlEncryption.EncryptedXmlDecryptor.Decrypt(XElement encryptedElement)
   at Microsoft.AspNetCore.DataProtection.XmlEncryption.XmlEncryptionExtensions.DecryptElement(XElement element, IActivator activator)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager.Microsoft.AspNetCore.DataProtection.KeyManagement.Internal.IInternalXmlKeyManager.DeserializeDescriptorFromKeyElement(XElement keyElement)
   at System.Lazy`1.CreateValue()
   at System.Lazy`1.LazyInitValue()
   at Microsoft.AspNetCore.DataProtection.AuthenticatedEncryption.CngGcmAuthenticatedEncryptorFactory.CreateEncryptorInstance(IKey key)
   at Microsoft.AspNetCore.DataProtection.KeyManagement.KeyBase.CreateEncryptor()
   at Microsoft.AspNetCore.DataProtection.KeyManagement.DefaultKeyResolver.CanCreateAuthenticatedEncryptor(IKey key)

App2 targeting .Net Core works fine, only App3 and App4 targeting .Net SDK has that exception.
However, it happens only a few machines, most machines are working fine.   Is it related to the .Net SDK installed?    I have .Net SDK 4.7.03062 and 4.6.01055 on those machines.

But after I add that ProtectKeysWithCertificate, in some of the servers, I get this exception in App2 and App3
App2 targeting .Net Core works fine, only App3 and App4 targeting .Net SDK has that exception.

Can you clarify which apps have the error? Is it only the apps which have <TargetFramework>net461</TargetFramework>? If so, this could be a bug in .NET Framework.

And what operating system are the failed servers running?

Yes, only those apps target net461 has the error and the server is Win 2012 R2 Standard.

Tagging @morganbr @bartonjs

This issue was moved to dotnet/corefx#32915


[event-hubs] set known amqp props on systemProperties

Fixes #7801
Since systemProperties was already an object with an index signature of string to any, no API changes were needed to support this.
It also turned out every one of the properties added is a typed field on the amqp message.

/azp run js - eventhubs-client - tests


Add fix for PvP Patron Orders

This uses the orderData to see if the heraldry has been provided.

thank you! will probably add that today


[SWARM-2005] KC Multitenancy support

Motivation
At the moment it is not possible to configure a Thorntail instance to get KC validating the clients coming from the different realms - which is what can be expected in the production. This can be required not only for the complex deployments but even for simple cases, for example, the public browser and command line clients are different types of clients as far as their security characteristics are concerned and it can make sense to get them scoped by the different realms.
The simplest way to support the dynamic loading of the KC adapter configurations is to have the path-based selection. Minimum effort should be required from the users. More involved selection strategies might be supported in the future.
Modifications

Introduced a "swarm.keycloak.multitenancy.paths" map property, the key is the relative path, the value - the custom KC json path; the query or headers or even claims based selection may be supported going forward
Added a new KeycloakAdapterConfigResolver, it is statically initialized with the map of the deployments and added as a context parameter to the web.xml.
Even though SecurityArchivePreparer was updated recently to support "classpath:" URIs, it was further updated to try to get the resources from the classpath even without the "classpath:" to make the "swarm.keycloak.multitenancy" config look nicer
Added a simple KeycloakMultitenancyTest - it is very similar to the original KeycloakArquillianTest but it resolves a KC config dynamically using a single entry deployments map

Result
Users will now be able to start experimenting with the multi-tenancy support by doing a very simple Swarm/Thorntail configuration...
Experimenting with securing the management/health and the user resources with KC at the same time will also be possible

LGTM, with my favorite pet peeve about JAX-RS Client: the client instances aren't being closed :-)

Ladislav, refactored a bit the test code to close the clients, it made it look cleaner IMHO, thanks. Also opened RESTEASY-1898 as a result, so your feedback re the JAX-RS Client is very welcomed :-)

Windows build keeps failing due to the lack of space on the disk

Thanks @sberyozkin!

retest this please


[CHA-RL1] Implement Room ATTACH operation

Implement all spec items that come under CHA-RL1.
Implement related integration tests.
Split from #6

┆Issue is synchronized with this Jira Task by Unito

Implemented as a part of https://github.com/ably-labs/ably-chat-kotlin/pull/27

Omitted CHA-RL1i ( make sure room is released before created), this will be covered as a part of Room release operation. Also, there's a discussion about changes in room lifecycle spec. So, related specs might change depending on the same.

Need to write unit tests for

[ ] CHA-RL1a) [Testable] If the room is already in the ATTACHED status, then this operation is no-op.

[ ] (CHA-RL1h) If the room is in the INITIALIZING status, then it must wait for the in-progress RELEASING operation from a previous room instance to complete before proceeding.

[ ] (CHA-RL1b) [Testable] If the room is in the RELEASING status, the operation shall be rejected with an ErrorInfo with the RoomIsReleasing error code from the chat-specific error codes.

[ ] (CHA-RL1c) [Testable] If the room is in the RELEASED status, the operation shall be rejected with an ErrorInfo with the RoomIsReleased error code from the chat-specific error codes.

[ ] (CHA-RL1d) [Testable] If a room lifecycle operation is already in progress, this operation shall wait until the current operation completes before continuing, subject to CHA-RL7.

[ ] (CHA-RL1e) [Testable] Notwithstanding the above points, when the attachment operation begins, the room shall be transitioned to the ATTACHING status.

[ ] (CHA-RL1f) [Testable] The underlying contributors will have their Realtime Channels attached in sequence – an attach call must complete successfully before the next is started.

[ ] (CHA-RL1g) When all contributors Realtime Channels successfully attach (the calls to attach() complete successfully), the operation is now complete and the room is considered attached.

[ ] (CHA-RL1g1) [Testable] The room status shall be transitioned to ATTACHED.

[ ] (CHA-RL1g2) [Testable] Any contributors to room that have a pending discontinuity event against them, must be notified of this fact, using the error that caused the original discontinuity.

[ ] (CHA-RL1g3) [Testable] Any transient disconnect timeouts shall be cleared.

[ ] (CHA-RL1h) If a one of the contributors Realtime Channels fails to attach (i.e. the call to attach() returns an error), then the operation has failed and must be rolled back. The procedure to roll back is described in subsequent points.

[ ] (CHA-RL1h1) [Testable] The attach call must throw an ErrorInfo. The code for this error is determined by the feature that failed (see here for more information on error codes).

[ ] (CHA-RL1h2) [Testable] If the underlying Realtime Channel entered the SUSPENDED state (i.e. the attach() operation fails and upon subsequently checking the channel state, it is SUSPENDED), then the room status will transition to SUSPENDED. The state transition ErrorInfo will use the Realtime Channel error as the cause. The status code shall be 500 and the error code whatever attachment error code corresponds to the feature that has failed, per the error code list.

[ ] (CHA-RL1h3) [Testable] When the room enters the SUSPENDED status as a result of CHA-RL1h2 the attach() operation shall fail using the error from CHA-RL1h2. The room lifecycle shall asynchronously (non-blocking to the ATTACH operation) enter the recovery loop (per CHA-RL5) and attempt to re-establish attachment.

[ ] (CHA-RL1h4) [Testable] If the underlying Realtime Channel entered the FAILED state, then the room status will transition to FAILED, using the error from the realtime channels attach() call as the cause field of the ErrorInfo. The state transition ErrorInfo will use the Realtime Channel error as the cause. The status code shall be 500 and the error code whatever attachment error code corresponds to the feature that has failed, per the error code list. The same error shall be thrown as the result of the ATTACH operation.

[ ] (CHA-RL1h5) [Testable] When the room enters the FAILED status as a result of CHA-RL1h4, asynchronously with respect to CHA-RL1h4, then the room will detach all channels that are not in the FAILED state.

[ ] (CHA-RL1h6) [Testable] If, when performing CHA-RL1h5, a channel fails to detach on command, then the detach operation will be repeated until such a time that all channels have detached successfully.

Two PRs marked as ready for review

Room ATTACH with internal RETRY -> https://github.com/ably-labs/ably-chat-kotlin/pull/33
Room ATTACH unit tests -> https://github.com/ably-labs/ably-chat-kotlin/pull/37


Browser push notifications?

Do you think you'll ever add browser push notifications to this package?

Okay, @raix  I see some of the comments you've made in the past.  It seems like we need to be able to generate the service worker and manifest.json.
I see these two places in the code
webServiceUrl: Match.Optional(String),
      websitePushId: Match.Optional(String),

Is the webservice url the service worker?  Where's it getting the manifest from?

I added this file to it: https://github.com/Neobii/push/blob/v3.x/lib/client/browserPush.js and it's based off of https://developers.google.com/web/updates/2015/03/push-notifications-on-the-open-web?hl=en .
So now, when you call Push.enable(true) and you are in the browser, it will prompt you to "allow or deny" push notifications.  Do you have any guidance on where to take it from here?

I'm getting a little bit closer: https://github.com/Neobii/push , on push configure I'm adding the manifest and service worker which are in the package folder now.

I think the server part adding certificates generating manifests etc. is not implemented - the client browser code might have to be aligned with the latests cordova api

What do you think I should use to generate the manifest and web service worker?  I see cfs:http-methods and WebApp.connectHandlers.  The manifest needs to have
gcm_sender_id and we have that from the config already.
It doesn't look like browser push notifications are implemented in the cordova plugin you're using.

It's best to use connect directly via WebApp - Right the corodva plugin is only for android+iOS - but I've started on the browser client code a long time ago, it's in https://github.com/raix/push/blob/fix-device-dependency-deprecate-json-format/lib/client/browser.js (it needs a clean up or maybe use https://www.npmjs.com/package/push.js for the client-side)

Hmm, are you loading in the service worker in an iframe there?  I don't see where you define the service worker like navigator.serviceWorker.register('/packages/raix_push/browser/service-worker.js').  Are you doing it a different way?

the iframe is a legacy thing - before meteor had cordova support - so that could go

Okay, I'm going to work on generating the manifest.json file from the config, check out this other package that seems to work: https://github.com/taromero/meteor-chrome-push-notifications/ I need a hint on tying the service worker back to the general push stuff.

What do you think about moving the json file to the private folder and loading them in through Assets?

Okay!  I got the browser manifest generating from the push configuration using the push.configuration.js plugin.  https://github.com/Neobii/push/blob/v3.x/lib/server/push.api.js#L50
To add it to the body I simply did $("body").append('<link rel="manifest" href="/push-manifest.json">');, only if they are not running in cordova.
I need to send the subscription id to the server, if someone from chrome connects would an android (gmc) show a connection on the push debug?

The more I think about it, it seems like we should split this into a couple different packages.

One package that connects push notification server and handles subscriptions
One package that handles cordova push notification
One package that handles desktop notification

hi,
this is how i handle "chrome" notification with service worker https://gist.github.com/eskan/133451a13ecb670d253322e1dcdfb033

I can't seem to get this working - may I ask what does your service worker look like?

hum .. i don't remember this gist :D ... the idea is to update raix:push data with the meteor method when a subscription is received. The service worker should be simple as
self.addEventListener('push', function(event) {
  event.waitUntil(self.registration.showNotification('New Message', {
    body: 'new message',
    icon: '/img/icon.png',
    vibrate: [500]
  }));
});

You can test it in Dev tools -> Application -> Service worker -> (push)

Was anyone able to get browser push notifications working with this package?


HMS-1825 build: enhance ephemeral rules

Goal: As a developer I want to enhance the ephemeral rule automation to make them more intuitive for the developer that meet with:
Acceptance Criteria:

rename ephemeral-build-deploy to ephemeral-build. After all the target builds the container image.
change ephemeral-deploy to only deploy the image
add a new target ephemeral-build-deploy that runs ephemeral-build + ephemeral-deploy in right order

This align the frontend with the change at the backend at: https://github.com/podengo-project/idmsvc-backend/pull/94
Depends on #27

I've rebased and force-pushed this branch.  The rebase was clean, but this PR has "aged in oak", and since there was a rebase, I want to CI it again before merge.

OK, green.  I didn't see any concerns in the diff but if something breaks, well, we fix it in a new PR :)


fix: fix typecheck script

Apparently we need to add the -b flag when running tsc on the cypress folder
https://github.com/remix-run/indie-stack/actions/runs/3951228293/jobs/6764810424

@mcansh I updated all my PRs with the -p flag instead of the -b flag

@mcansh I just noticed we now create .js files for all our cypress TS files 😕
Maybe we should go back to -b flag instead?

@mcansh I just noticed we now create .js files for all our cypress TS files 😕
Maybe we should go back to -b flag instead?

hm i had that if i didn't put -p odd

@mcansh Nevermind, can't reproduce it anymore now 😅


BUG: SciPy 1.11.0rc1 not buildable on PPC due to boost submodule

Trying to build rc1 for conda-forge in https://github.com/conda-forge/scipy-feedstock/pull/235, things are looking pretty OK with two exceptions. I'll open another issue for the OSX test failures, but on ppc, the build already fails during compilation:
../scipy/_lib/boost_math/include/boost/math/tools/promotion.hpp:140:27: error: static assertion failed: Sorry, but this platform does not have sufficient long double support for the special functions to be reliably implemented.
  140 |          static_assert((0 == std::is_same<type, long double>::value), "Sorry, but this platform does not have sufficient long double support for the special functions to be reliably implemented.");
      |                        ~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The boostorg/math submodule (or some recent update thereof) seems to contain a static_assert that unconditionally fails compilation on PPC (or maybe we can toggle off the long double support on PPC?)
PPC is our "most niche" platform, but it's still a hard compilation error on a long-standing arch in conda-forge, so I'm tentatively milestoning this for 1.11.
CC @mckib2 @mdhaber @rgommers @tylerjereddy

Do you know which long double format your version of PPC64LE is running (e.g. ibm128 or float128)?

I don't actually... It's actually running through QEMU 7.2 on x64 agent. How would I be able to find that out?

Is there a way to output LDBL_MANT_DIG in your config information. Here's the info on the transition: https://developers.redhat.com/articles/2023/05/16/benefits-fedora-38-long-double-transition-ppc64le#. I'll look through the runner and see if I can find anything.

Here's the info on the transition: https://developers.redhat.com/articles/2023/05/16/benefits-fedora-38-long-double-transition-ppc64le#

Then it's almost certainly the IBM one. We're not on anything nearly as new as Fedora 36 (rather, something like CentOS 7).
PS. Thanks a lot for taking a look at this so quickly, much appreciated!

If you look at the backtrace you'll see that you are explicitly calling the pdf on binomial_distribution<long double>, so if it's a regression I would say it's at your end.  Probably ;)
BTW the reason we treat this as an error is that "double double"'s cause all kinds of issues in some of our code - it's simply not possible to reason about their behaviour in a sensible way because they have a "discontinuous" representation, this is reflected in their value for numeric_limits<long double>::epsilon() which is typically numeric_limits<double>::min().  This is technically correct in that it's the smallest value you can add to 1 and effect a change, but functionally useless in any other sense.
So... my contention has always been that it's just too much work to make these types function correctly inside Boost.Math, but I'm happy to be proved wrong!

So... my contention has always been that it's just too much work to make these types function correctly inside Boost.Math, but I'm happy to be proved wrong!

I completely agree, and I'd like to remove long double support from SciPy (and NumPy) completely.  We just can't rip it out with zero notice unfortunately, so we should try to solve the problem here. gh-16185 already took a pragmatic approach in not supporting long double on Windows (it'd be 64-bit anyway there).

https://github.com/scipy/scipy/blob/ec22c5587f32198758435964697b08d4e8c4119f/scipy/stats/_boost/include/code_gen.py#L189
Looks like we generate a NPY_LONGDOUBLE override on all platform except Windows.  Seems like there's an easy fix to remove the long double code generation -- can we do this without a deprecation cycle?  Seems like we're accidentally supporting this at this point

Thanks for everyone's input! I tested @mckib2's #18630 in https://github.com/conda-forge/scipy-feedstock/pull/235 and compilation on PPC now passes. 🥳
If we need to keep long double for a while longer (if only to deprecate it), then we could easily restrict that patch to PPC (either here or downstream in conda-forge).


[KOGITO-9309] - Timeout on dataindex-embedded addon

See: https://issues.redhat.com/browse/KOGITO-9309
The purpose of this fix is enable the possibility for user to control how long the postgresql process will wait to get started.
In some environments, the default startup timeout is not enough, with this proposed change, users can set the system property to control the timeout.

@fjtirado @tiagodolphine please take a look.

Thanks @fjtirado, changes made.


[Bug] 0.9.5b6 File import of jpg - file node label "None"

I confirm that this is working.
Any chance we can set the Image node label too? Difficulty is that (in my naming convention anyway) label is too long and no idea what algorithm would be sensible to create a short label from a long file name.


wip: testing secret<tensor> or secret<memref>

Assuming we can get Yosys optimized results out of a secret.generic body, we will then need to convert the comb operations inside a secret.generic to CGGI ciphertexts. There is an example IR in tests/comb_to_cggi/add_one.mlir that is produced from the yosys optimizer.
The yosys optimizer splits multi-bit inputs into tensors of single-bits. These are contained within secret.generic bodies.
When the types and ops are hoisted out of the body, we need to convert the secret multi-bit tensors into ciphertext tensors.
This becomes problematic, because the internal ops like tensor.extract do not operate nicely with the secret<tensor<8xi1>>.
We can either (1) support some secret dialect op that would extract / concat or (2) switch again to tensor<secret<i1>>
Here's the debug result that shows the relevant tensor.extracts at the end of this test https://gist.github.com/asraa/f0ccf585aebd35603a10419ac86a3892

Still thinking about this. If we end up wanting to lower SIMD ciphertexts, then I don't think it would matter whether we are using secret<tensor<1024xi8>>, rather than tensor<1024xsecret<i8>>. Inside generic bodies, we would still be operating on the tensors and using tensor arithmetic.
When lowering in the equivalent arith-to-ckks or other RLWE types, then we would still probably hoist these types outside as tensors of RLWE ciphertexts that encode i8's in their coefficients, and then run a pass that can SIMD-ify the computation as desired and transform the tensors of ciphertexts into a single ciphertext (thereby changing the RLWE encoding on the types)

I'm a little confused from the IR you posted. I understand tensor can't take a secret as input, but the input to the tensor.extract is the result of %1 = "secret.cast"(<<UNKNOWN SSA VALUE>>) : (!secret.secret<i8>) -> !secret.secret<tensor<8xi1>>, and that unknown input was presumably the type-casted block argument, %arg0: !lwe.lwe_ciphertext<encoding = #lwe.unspecified_bit_field_encoding<cleartext_bitwidth = 8>>
Does that block argument represent a single i8 LWE ciphertext? The problem here is that we haven't chosen lwe encoding params yet, so we can't lower it to an appropriate tensor of ciphertexts?
It seems like going through the YosysOptimizer pass inherently forces a particular encoding choice: we have a minimum cleartext_bitwidth enforced by the ABC lut size, and we require the ciphertexts semantically represent single bits (so we know we have to lower the arg to a tensor of size 8).
Can't we just force the parameter selection in this lowering, say, by recognizing the use of comb inside a secret.generic? If we do that, then we should be able to resolve all the cast ops.

Does that block argument represent a single i8 LWE ciphertext?

Yes, this is the original i8 argument of the function that's been type converted. The type converter was only converting an int of bit width N to an LWE ciphertext with N bitwidths.

The problem here is that we haven't chosen lwe encoding params yet, so we can't lower it to an appropriate tensor of ciphertexts?

I think I see what you mean - in our case, we want comb-to-cggi to lower the argument to a tensor of single bit LWE encodings, in which case presumably the casts would go away, I think (I'll try!)
However, I don't really understand if this is the right behavior in generality. Shouldn't we pick the encoding at the scheme level? It's still possible to extract out bits of an encoded ciphertext and operate on them (should the circuit require that), rather than breaking up the ciphertext into the most minimally sized parts (i1's here).

we have a minimum cleartext_bitwidth enforced by the ABC lut size, and we require the ciphertexts semantically represent single bits (so we know we have to lower the arg to a tensor of size 8).

Definitely, yes, LUT # -> cleartext_bitwidth makes sense. However, somehow we also have to capture the expected range is single bits for the inputs to the original ciphertext, but I'm assuming that'll come through with the noise interface.

Can't we just force the parameter selection in this lowering, say, by recognizing the use of comb inside a secret.generic? If we do that, then we should be able to resolve all the cast ops.

Let me try that! Thanks. In the meantime I tried working through updating the types, but there's so many cast assumptions on the types that it's proving pretty tedious.

I think this belongs in the comb to CGGI pass, not the yosys optimizer
pass. And even if it's not technically forced, I think starting from that
default assumption is the right approach for now.
On Fri, Dec 8, 2023, 8:57 AM asraa @.***> wrote:

Does that block argument represent a single i8 LWE ciphertext?
Yes, this is the original i8 argument of the function that's been type
converted. The type converter was only converting an int of bit width N to
an LWE ciphertext with N bitwidths.
The problem here is that we haven't chosen lwe encoding params yet, so we
can't lower it to an appropriate tensor of ciphertexts?
I think I see what you mean - in our case, we want comb-to-cggi to lower
the argument to a tensor of single bit LWE encodings, in which case
presumably the casts would go away, I think (I'll try!)
However, I don't really understand if this is the right behavior in
generality. Shouldn't we pick the encoding at the scheme level? It's still
possible to extract out bits of an encoded ciphertext and operate on them
(should the circuit require that), rather than breaking up the ciphertext
into the most minimally sized parts (i1's here).
we have a minimum cleartext_bitwidth enforced by the ABC lut size, and we
require the ciphertexts semantically represent single bits (so we know we
have to lower the arg to a tensor of size 8).
Definitely, yes, LUT # -> cleartext_bitwidth makes sense. However, somehow
we also have to capture the expected range is single bits for the inputs to
the original ciphertext, but I'm assuming that'll come through with the
noise interface.
Can't we just force the parameter selection in this lowering, say, by
recognizing the use of comb inside a secret.generic? If we do that, then we
should be able to resolve all the cast ops.
Let me try that! Thanks. In the meantime I tried working through updating
the types, but there's so many cast assumptions on the types that it's
proving pretty tedious.
—
Reply to this email directly, view it on GitHub
https://github.com/google/heir/pull/326#issuecomment-1847524003, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS2PKXVSX54AOYF6A4F5QDYINBG3AVCNFSM6AAAAABALUJKQ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNBXGUZDIMBQGM
.
You are receiving this because you commented.Message ID:
@.***>

I think this belongs in the comb to CGGI pass,

I agree! The last commit started the changes there. I think the decision should be made at the scheme choice.

@j2kun I finally (finally!) figured out how to get this pass to work. I had to add in a secret.cast pattern as well here, to reconcile the casts Yosys Optimizer places that should become no-ops in this lowering (since secret.secret<i8> is reconciled with secret.secret<tensor<8xi1>>.

I think the test failures may be related to this being deployed https://github.com/bazelbuild/bazel/issues/18958
Now I see this:

WARNING: --enable_bzlmod is set, but no MODULE.bazel file was found at the workspace root. Bazel will create an empty MODULE.bazel file. Please consider migrating your external dependencies from WORKSPACE to MODULE.bazel. For more details, please refer to https://github.com/bazelbuild/bazel/issues/18958.

But I don't see that warning in https://github.com/google/heir/actions/runs/7169640934

Confirmed, it may not be because of bazelmod, but it is definitely due to the one-hour-ago release of bazel version 7.0.0. I will push a patch to force an earlier bazel version for now

See https://github.com/google/heir/pull/331 for the fix


Image upload issue via Perch blog using CKeditor

Attempting to insert an inline image using CKEditor prompts a "server error" browser popup in Chrome. The app within dashboard reports that the image has successfully been submitted and compressed, but checking the directories shows that it has not saved to resources folder, or in fact anywhere within the site (have tried designating a specific bucket also within the blog template, but also without success).

Sorry for not seeing you issue earlier.
can you please add some information about the perch version, operating system etc.
I have added a blog and updated the posts template to use the ckeditor and have had no issues as you have reported.

closing - not able to replicate.


MouseWithoutBorders - firewall rule added at install even when feature is disabled

Microsoft PowerToys version
0.78
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
General, Mouse Without Borders
Steps to reproduce
priority: low
may also be related: https://github.com/microsoft/PowerToys/issues/27337
hi,

set registry value to disable MouseWithoutBorders
`reg add "HKLM\SOFTWARE\Policies\PowerToys" /v "ConfigureEnabledUtilityMouseWithoutBorders" /t REG_DWORD /d 0 /f``
clean install of PowerToysSetup-0.78.0-x64.exe
observe a host firewall rule named "PowerToys.MouseWithoutBorders" is created

have tested in a Windows Sandbox to confirm it's part of the install process
✔ Expected Behavior
firewall rule not to be created when application is configured to disable the associated feature
this may be subjective / my own bias, but would also argue (in a friendly way) that FW rules should be an off by default install option or left as a manual admin task
cheers
❌ Actual Behavior
host firewall rule named "PowerToys.MouseWithoutBorders" is created
Other Software
No response

Similar issue that I posted regarding v0.70.0. Just upgraded to v0.79.0 and the default MWB firewall rules were applied again.
#27337


[SPARK-12585] [SQL] move numFields to constructor of UnsafeRow

Right now, numFields will be passed in by pointTo(), then bitSetWidthInBytes is calculated, making pointTo() a little bit heavy.
It should be part of constructor of UnsafeRow.

Test build #48504 has started for PR 10528 at commit cfef659.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48502/
Test FAILed.

Merged build finished. Test FAILed.

Test build #48504 has finished for PR 10528 at commit cfef659.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48504/
Test PASSed.


Animated: useNativeDriver was not specified

When I was using the package with React Native 0.62, I get the following YellowBox warning:
Animated: `useNativeDriver` was not specified. This is a required option and must be explicitly set to true or false.

I made a pull request: https://github.com/liangl1412/react-native-emoji-keyboard/pull/3

Merged, thank you


Add defaulting to ingress namespace and annotations

While there, skip the double parsing of the ingress filename so a
single ingress object can be carried through each create/delete
operation.
@nikhiljindal @G-Harmon @madhusudancs @perotinus

This change is

@csbell please rebase?

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

app/kubemci/cmd/create.go, line 190 at r1 (raw file):

	clients := map[string]kubeclient.Interface{}
	var ing v1beta1.Ingress
	if err := unmarshall(ingressFilename, &ing); err != nil {

Nice!

app/kubemci/cmd/create.go, line 195 at r1 (raw file):

	glog.V(5).Infof("Unmarshaled this ingress:\n%+v", ing)

	// TODO(nikhiljindal): Validate and optionally add the gce-multi-cluster class annotation to the ingress YAML spec.

Validate TODO, if not the "optionally add the ..." should still exist?

app/kubemci/cmd/create.go, line 244 at r1 (raw file):

		ing.Namespace = defaultIngressNamespace
	}
	ingAnnotations := annotations.IngAnnotations(ing.ObjectMeta.Annotations)

Just use ing.Annotations instead of ing.ObjectMeta.Annotations?

app/kubemci/cmd/create.go, line 253 at r1 (raw file):

		glog.V(3).Infof("Adding class annotation to be of type %v\n", annotations.GceMultiIngressClass)
	} else if class != annotations.GceMultiIngressClass {
		return fmt.Errorf("error definining ingress class to %v, must be %v", class, annotations.GceMultiIngressClass)

I think this is a little confusing. Change it to something like: "ingress class is %v, must be %v"

app/kubemci/cmd/delete_test.go, line 77 at r1 (raw file):

		var ing v1beta1.Ingress
		if err := unmarshallAndApplyDefaults("../../../testdata/ingress.yaml", &ing); err != nil {
			return []string{}, nil, err

return nil, nil, err

Comments from Reviewable

Rebased and issues addressed. PTAL.

Review status: 1 of 5 files reviewed at latest revision, 5 unresolved discussions.

Comments from Reviewable

This is awesome!
Thanks @csbell
/lgtm

lgtm


Dev/brih/task/assessment select first error

This PR fixes #

Please provide some description for the PR and don't leave the default content there.


Cursor freezes in normal mode when pressing <c-h/j/k/l>

Anytime i hit one of the below keys the cursor completly freezes. I can still enter insert mode with a,i,... type and exit it but in normal mode it stays frozen. Keymaps that trigger vscode functionality via VSCodeNotify still work. So does moving the cursor with the mouse.
If I open a different tab and go back everything works again.
This happens on any of the following:
<c-h>,<c-j>,<c-k>,<c-l>

Do you have any custom nvim bindings for those? If so, they will break vscode-neovim.

I double checked using :nmap <c-j>. Indeed I do have some mappings. I created a separate config just for vscode-neovim (to not mess with my default neovim configuration) under .config/vscode-neovim/init.lua. Turns out that even if I pass a custom config path to the vscode-neovim.neovimInitVimPaths option, it still picks up on my default neovim config path and loads all files in the after/plugins directory.
This has some keybindings for navigating between tmux and neovim for me which causes my issue.
Since it is very easy to miss that neovim still loads the default after/plugins files even when pointing to a completely different init.lua i think there should be an option to reconfigure nvims stdpath('config') or at least have a section about after/plugin in the README.
For now I can edit my after/plugin files to early exit when exists('g:vscode') and not load those keybindings to fix my issue. Thank you alot for bringing me on the right track.


v2.2.13 : Client authentication in TLS

Hello,
tls_callhome.xml example shared in example_configuration directory is setting both ca-certs and ee-certs.
While in in ietf-netconf-server, we have the following specification :
refine "client-authentication" {
must 'ca-certs or ee-certs';
Questions :

So why setting both ca-certs and ee-certs in the example, while ietf  Yang model is documented one or the other ?
Does NC Server support setting of only ca-certs ?
Regards.
Christian.

It is using or meaning one, or the other, or both, not nor. Either a known CA certificate or a client certificate directly is needed to authenticate every client and in this case both are being set which does not break anything. I have tried it and it work only with either of them; I think we have not realized it is no longer needed after the last updates but I am not sure it is worth removing.

Thanks for the confirmation


Missing release tag 2.1.5

Looking at what's available https://repo1.maven.org/maven2/com/github/scredis/scredis_2.12/ I see there's a version 2.1.5+19-a5ac3984. Is this usable? I need this version for the akka version 2.5.16 to not conflict with my current project

go with 2.1.9 https://repo1.maven.org/maven2/com/github/scredis/scredis_2.12/2.1.9/
2.1.5+19-a5ac3984 and similar are created after merging anything to master but necessarily associated to any particular release.

@kpbochenek The akka version is too high in that version though, when I start up I get
2018-10-15 20:31:12 - [warn] - akka.util.ManifestInfo - Detected possible incompatible versions on the classpath. Please note that a given Akka version MUST be the same across all modules of Akka that you are using, e.g. if you use [2.5.17] all other modules that are released together MUST be of the same version. Make sure you're using a compatible set of libraries.Possibly conflicting versions [2.5.16, 2.5.17] in libraries [akka-persistence:2.5.16, akka-cluster-sharding:2.5.16, akka-protobuf:2.5.16, akka-persistence-query:2.5.16, akka-actor:2.5.17, akka-slf4j:2.5.16, akka-remote:2.5.16, akka-cluster:2.5.16, akka-distributed-data:2.5.16, akka-stream:2.5.16, akka-cluster-tools:2.5.16]

Ok 2.1.5+19-a5ac3984 should be ok to use, previous releases were not not done by me and were not pushed to maven central that's why you don't see 2.1.5.
Other question, what other library do you use that requires akka 2.5.16 ?
Very weird that difference in minor akka version cause you problems, but try 2.1.5+19-a5ac3984 and let me know if it works for you.

We're using Lagom with SbtReactiveApp which requires akka version 2.5.16. We actually tried that minor version but still ran into the same issue so it's possible it could be a different issue, I'm looking into it further atm

Redis - if you don't provide ActorSystem will try to create one. Because you have in your dependencies AkkaCluster/Remoting Akka by default creates clustered ActorSystem which requires binding to external port. It fails for some reason. You should probably try investigate
In 2.1.9 version you can provide ActorSystem so Redis will not try to create one.

Version 2.1.5+19-a5ac3984 does not work unfortunately. Using this sbt dependencyTree plugin https://github.com/jrudolph/sbt-dependency-graph I see that that still uses akka-actor 2.5.17 unfortunately
 +-com.github.scredis:scredis_2.12:2.1.5+19-a5ac3984 [S]^[[0m
 | +-com.typesafe.akka:akka-actor_2.12:2.5.17 [S]^[[0m
 | | +-com.typesafe:config:1.3.3^[[0m
 | | +-org.scala-lang.modules:scala-java8-compat_2.12:0.8.0 [S]^[[0m
 | | ^[[0m
 | +-com.typesafe.scala-logging:scala-logging_2.12:3.9.0 [S]^[[0m
 | | +-org.scala-lang:scala-reflect:2.12.6 [S]^[[0m
 | | +-org.slf4j:slf4j-api:1.7.25^[[0m
 | | ^[[0m
 | +-com.typesafe:config:1.3.3^[[0m

Could you provide an example how to pass the ActorSystem into Redis? I'm curious if that will work because the library is still a conflicting version

Redis.withActorSystem() and implicit ActorSystem will be picked up.
OR
Redis.withActorSystem()(yourActorSystem)
again I don't think this is a problem of akka version mismatch as it is only one minor version difference.

Oops, I accidentally closed it. I've tried that as well as using dependencyOverriding to up the akka versions in lagom to 2.5.17 but there's another issue
akka.cluster.sharding.ShardRegion - No coordinator found to register. Probably, no seed-nodes configured and manual cluster join not performed? Total [1] buffered messages.

which I'm looking into for now which is probably a different issue.
Thank you for the help so far @kpbochenek ! I'll be sure to report back if the issue was somehow related to this


Fails to detect JSON file if UTF-8 with BOM

The task fails to parse a JSON file with encoding "UTF-8 with BOM":
File could not be parsed as JSON: Unexpected token  in JSON at position 0
Visual Studio (apparently) uses the "UTF-8 with BOM" encoding by default; the BOM is at the beginning of the file, and the task doesn't like it.
I can probably work around the issue by removing the BOM myself (changing the file encoding), but it would be nice if the tool could just ignore it.
If anything, maybe this info will help someone else with the same issue (check your file encoding!).

Thanks for reporting this issue! The task is now handling this case by removing the BOM before parsing and adding it back afterwards just in case. I just published version 1.2.3 on Azure DevOps with this fix.


API first development

Usually every route ends with a call to template 'some.html', { ... };
It might be more interesting if Bailador made it simple to create an API that returns JSON and on top of that to return HTML pages. So a normal route of Bailador would return a datastructure and the name of a template. Then Bailador would either return only the datastructure as a JSON or would call the template() function with the given template and the data structure.
How can this kind of coding made simple and obvious to use?
I'd go even further. Today with the Microservice architecture being popular, a lot of web applications don't even need to return HTML. Just JSON. Even the 404 and 500 pages are different than in the HTML world. IMHO It would be important to make it very easy to write such applications in Bailador.

it reminds me on the respond_to() feature of mojolicious
http://mojolicious.org/perldoc/Mojolicious/Controller#respond_to
i'd say that your Feature requests sounds perfect for the job of a plugin
so you could have some hook, that catches the data retunred from your callback/sub, and passes it to template('template-name.tt'), and this plugin could automatically take the $route-name as template-name
so for the route
get '/foobar' => sub { ....; return %data } t
his plugin should do this for you:
template('foobar.tt', %data)

Does Bailador have a notion of middlewares? Would be helpful for API-style development.

I definitely think API should go first. Most microframeworks don't even bother with HTML, or use some generic templating library for that.


Notebook organization

We now know that the LSP JupyterLab instance has a special "notebooks" folder in each user's home directory, which is where they are advised to keep their notebooks. the DMStackClub repo should be cloned into there, but then the club notebooks should be kept in informatively-named subfolders  (rather than another "notebooks" folder). In this PR we will start this organization scheme based on the topic list.  I suggest we implement the following directory structure:
DMStackClub/GettingStarted
DMStackClub/Visualization
DMStackClub/ImageProcessing

and so on. I've started an index table in the README to explain this, and help people find the right notebooks - as well as including the link to the topic list google doc. I have not yet started the actual re-org - we need to merge the existing PRs first. Comments welcome!

OK, folder names seem OK with everyone, merging.


Income process overhaul: Truncated lognormal

Our default income process should be overhauled to use truncated lognormal distributions with a point mass.  Our calculation of the natural borrowing constraint depends on the "worst income event" in the discrete approximation IncomeDstn.  If the true distribution really is (joint) lognormal with a point mass for unemployment, then the true "worst income event" is arbitrarily close to a permanent income shock of 0, so the natural borrowing constraint is always 0.  In specifications where the artificial borrowing constraint does not exist (or does not bind), we are effectively solving the wrong problem.
In order to have a nonzero natural borrowing constraint, we must lower truncate both the permanent and transitory shock distributions.  The most straightforward, transparent way to do this is to set two new parameters, PermShkLwrBnd and TranShkLwrBnd.  approxLognormal must be adjusted to accept a lower (and upper, while we're at it) bound as an optional input; it will return a discrete approximation to the lognormal conditional on being above (below) the chosen bounds.  approxMeanOneLognormal will need one more line to re-normalize, as the discretization will have a mean slightly different from 1 when there is truncation.  When no lower bound is specified, we might want approxLognormal to add a zero probability point at 0.0 (as long as sigma>0).
I wrote a long-ish email in May 2016 about this; available on request.

Although the upper bound is much less important, whenever this is tackled the person doing it should also truncate at the upper bound, with the natural variable names being PermShkUprBnd and TranShkUprBnd.
The right way to do this is to augment the grids produced by the approximate lognormal tool with very-tiny-but-not-quite-zero pointmasses at exactly each of the bounds.  This will require a very-tiny-but-not-quite-zero adjustment to the values of the discretized points so that the dot product remains exactly 1.
Seems like something that probably people have done somewhere before ...

further discussions in https://github.com/econ-ark/HARK/issues/804


VideoConferenceMute: Clarifying version needed

Provide a description of requested docs changes
I am installing Powetoys on a new machine,
https://docs.microsoft.com/en-us/windows/powertoys/video-conference-mute says "This is a preview feature and only included in the pre-release version of PowerToys."
The main readme says To install the Video Conference mute, please use the v0.36 experimental version of PowerToys to try out this version.
Is the pre-release the same as the experimental version?
v0.36 is from April, so I have to do without all the changes since then?

Experimental v0.46.0 release brought the latest with Video conference mute feature but the docs still need updating

Hi All
I am new to this PowerToys, I have V0.47.1 but Video Conference is missing at my side if you can help with more clarification regarding the version
Thanks :)


build docker images

build docker images

There would also need to be accompanying documentation changes.

I will modify, and request.


Implemented gmail.fetch, message.read? and message.starred?

Hi,
I have implemented the imap fetch command for range based navigation of the gmail inbox, additionally I have also implemented the read? and starred? flags on the message class.
You might want to be a bit selective about pulling in my changes because I have also for example removed the mailbox locking login for no other reason that it made my application a bit harder to code.
Unfortunately I have not been able to write proper tests because I am assuming that your tests run against a specific mailbox with specific data, as a lot of tests were failing using a clean clone of your repository.
I hope there is something useful in my commits and apologies if I have saddled you up with to much merge hastle :-)
Regards,
Waseem

@codyrobbins if you'd like please rebase this PR on master and I'll review.

This issue was moved to gmailgem/gmail#27


Postgres UPDATE statements should convert lists to ARRAY

Hello!
When using the Postgres dialect, a list isn't being converted to an ARRAY for UPDATE statements. Lists are handled correctly for INSERT statements and there's test coverage.
To replicate:
from unittest.case import TestCase

from pypika import Table, Query, PostgreSQLQuery
from pypika.enums import Dialects

class UpdateTest(TestCase):

    def test_dialect(self):

        q = Query.update(Table("abc"), dialect=Dialects.POSTGRESQL).set(1, [1, "a", True])

        self.assertEqual("UPDATE \"abc\" SET \"1\" = ARRAY[1,'a',true]", str(q))

    def test_postgresquery(self):

        q = PostgreSQLQuery.update(Table("abc")).set(1, [1, "a", True])

        self.assertEqual("UPDATE \"abc\" SET \"1\" = ARRAY[1,'a',true]", str(q))

The resulting query is UPDATE "abc" SET "1"=[1, 'a', True] which is incorrect syntax. I'm using version 0.48.0.
Thanks!

Just ran into this issue too, bumping.


More of a feature

Hello this is very nice, it would get a lot more traction if it had a GUI.
I can help build a quick GUI in windows for you, but I need some way to run in with C#.
thanks

A web based GUI would be preferable as opposed to a desktop based GUI, just for cross platform purposes


Use json-stringify-safe for json formatter

Hello @TomFrost and contributors,
Wondering if you'd be open to taking on another dependency and changing the default json formatter to use json-stringify-safe to protect crashing the process when trying to stringify a circular structure?
I'm willing to make a PR if this is something you'd like.
Thanks 👍

Another good suggestion!
My only immediate concern about this would be serialization speed. I'd love to see a benchmark of JSON.stringify versus that lib-- if you wanted to convert Bristol and test that, I wouldn't be opposed!

Awesome!
Since there are no benchmarking tests in Bristol right now, I'll make a PR adding some initial benchmarks to establish a baseline of performance. However, I have no clue what I'm doing in terms of benchmarking, so it'd be awesome to get some feedback on things you'd like to see benchmarked.

@TomFrost json-stringify-safe is infinitely faster on circular references ;)

PR #41


Store run start time

Describe changes
I implemented/fixed _ to achieve _.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@schustmi unfortunately I can't request you to review your own PR ^^


Add data links to tooltips

See https://github.com/USGS-VIZLAB/water-use-15/blob/master/js/map_utils.js#L286-L289 from #35 (pr #55)


chore(deps): bump k8s.io/apimachinery to 0.31.2, add k8s.io/cri-client and k8s.io/endpointslice to replace section

bump k8s.io/apimachinery to 0.31.2, to be consistent with argo-cd
while everything builds and runs fine in command line, when loading the project in my ide, I'm seeing errors like the following. Adding k8s.io/cri-client and k8s.io/endpointslice to the replace section fixes the problem.

go<EMAIL_ADDRESS>invalid version: unknown revision v0.0.0

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 74.64%. Comparing base (6273814) to head (9efc196).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #938   +/-   ##
=======================================
  Coverage   74.64%   74.64%
=======================================
  Files          31       31
  Lines        3913     3913
=======================================
  Hits         2921     2921
  Misses        856      856
  Partials      136      136

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Multipolygon Clipping

Adds multipolygon clipping and a fix for invalid multipolygons due to overlaps in sub-polygons.

If we feel good about the code, I will merge!


[ENH] Add minibatch param in MLPClassifier

Fix #395

Resolved a conflict, we previously decided to move away from the file-based author list. Odd CI didnt run on this before but seems to be fine now.

LGTM, looks correct @hadifawaz1999 ?

LGTM, looks correct @hadifawaz1999 ?

yes looks good just missing the docstring information for the parameter

ah good catch, yeah needs to be added to the docstring 🙂

Will do it ASAP. Thanks 😊


Navbar of Jobs are redirecting to unknown path when clicked on courses and top university #1055

Description
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #1055
Actually Fixed whole Navbar Component Now navbar Components is SImilar to One in dashboard so now we can directly use  in every page
Screenshots

Checklist

[X ] Tests have been added or updated to cover the changes
[X ] Documentation has been updated to reflect the changes
[ X] Code follows the established coding style guidelines
[ X] All tests are passing

hey @thestarsahil please review it whenever possible and let me know changes


Missing options like -xdev or -nf (not following symlinks)

[ x] I have read through the manual page (man fzf)
[ x] I have the latest version of fzf
[ x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[x] bash
[ ] zsh
[ ] fish

Problem / Steps to reproduce
fzf is following all symlinks dirs. I had several looks on your site and web, but got no resolution like an option like -nf (don't follow sysmlinks) or even sometihing like "find's -xdev"

You can write your own command for file traversal. See https://github.com/junegunn/fzf#environment-variables


config: Unmarshal to versioned KubeOneCluster

What this PR does / why we need it:
Currently, the config package is unmarshaling the KubeOneCluster YAML to the internal struct. That's not correct because the config package always produces the v1beta2 YAML. The internal and the v1beta2 APIs can be different, which can cause issues.
Also, for some reason, kubeone config migrate is failing to migrate configs with the containerRuntime block. This is also fixed by using the v1beta2 API instead of the internal API. I tried to investigate this because the ContainerRuntime API is the same across two API versions, but I wasn't able to find the root cause.
Finally, the AssetConfiguration is removed from the example config because it has been removed in the v1beta2 API.
Does this PR introduce a user-facing change?:
Fix an issue with `kubeone config migrate` failing to migrate configs with the `containerRuntime` block

/assign @kron4eg @ahmedwaleedmalik

/cherrypick release/v1.4

/retest


[typescript-urql-svelte] New Codegen Plugin Request

The existing typescript-urql plugin is specific to React, and Svelte is awesome. I have @urql/svelte up and running, and would love to see a typescript-urql-svelte plugin for it.
As of today, the Svelte repo has 41.4k stars, so it should be around a while. :)

@trevyn That sounds great! Would you start with a draft PR to help us? We don't know much about Svelte.

@trevyn That sounds great! Would you start with a draft PR to help us? We don't know much about Svelte.

Sure, I'll take a look. For now, here's my quick-and-dirty @urql/svelte impl. I honestly am not sure about the TypeScript part yet, but I'll keep this thread updated and submit a draft PR if I figure out a sensible plugin. :)

Sure, I'll take a look. For now, here's my quick-and-dirty @urql/svelte impl. I honestly am not sure about the TypeScript part yet, but I'll keep this thread updated and submit a draft PR if I figure out a sensible plugin. :)

Ok, I did a reasonable draft of what the codegen output could look like, and verified it works:
App.svelte (usage)
graphql_ops.svelte (would be codegen'd)
This is just in straight JS, I'll need to add TypeScript.
I also looked at the plugin code for typescript-urql to understand how to actually make the plugin. It looks OK, so I'll probably do that over the next few days. (Unless this is already enough, and you have someone that wants to take it on?)

Ok, I did a reasonable draft of what the codegen output could look like, and verified it works:
App.svelte (usage)
graphql_ops.svelte (would be codegen'd)
This is just in straight JS, I'll need to add TypeScript.
I also looked at the plugin code for typescript-urql to understand how to actually make the plugin. It looks OK, so I'll probably do that over the next few days. (Unless this is already enough, and you have someone that wants to take it on?)

Moving to Discussions :)

Moving to Discussions :)


v0.2.0: conan release is missing

The conan release metall-ffi/0.2.0 is missing from conan.dice-research.org
TODOs:

[ ] investigate why and fix CI if necessary
[x] upload it

#6


[Feature] Make warn_unenforced and warn_unsupported constraint options on the project level

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
I would love to be able to suppress the warning:
18:38:06  [WARNING]: The constraint type primary_key is not enforced by
snowflake. The constraint will be included in this model's DDL statement, but it
will not guarantee anything about the underlying data. Set 'warn_unenforced:
false' on this constraint to ignore this warning.

for dbt run/build. Our users are aware that the constraint is unenforced so the logs are taking up space.
Describe alternatives you've considered
We are trying to require primary keys on all 3k models -- we could also require that we warn_unenforced an all of those primary key yml keys. That is extra work for for us and it adds 3k lines of bytes to our schema files.
I saw a few potentially related issues that were closed in versions after 1.6: https://github.com/dbt-labs/dbt-core/issues/7067 + https://github.com/dbt-labs/dbt-core/issues/6754 -- but I'm not sure this actually addresses the feature. We are on dbt-core 1.6.7 and dbt-snowflake 1.6.8. Maybe this was already addressed?
Who will this benefit?
Anyone using constraints on Snowflake/BQ/Redshift etc
Are you interested in contributing this feature?
If it is reasonably contained I could take a crack at it with some guidance. I did a cursory read of the constraints code and I couldn't really sort it out.
Anything else?
No response

Thanks for reaching out about this @jsnb-devoted !
Wanna take a look at the silence parameter to the warn_error_options flag that was added to v1.8 and see if it would fit the use case you are describing?

Hey @jsnb-devoted !
@dbeatty10 You beat me to it :) I just confirmed that this worked for me locally:
$ dbt run -s model_a --warn-error-options '{"silence": ['ConstraintNotEnforced']}'

This can also be set:

as an env var (DBT_WARN_ERROR_OPTIONS)
in the flags dict of dbt_project.yml (although I believe I found a tiny bug with this)

That looks like what I need. I'll add it to the list of things to check out when we make it to 1.8. Thanks yall.

Sure thing @jsnb-devoted !
I'm going to close this as resolved, but please reach out if run into any issues or have any follow-up feedback.

@dbeatty10 Happy Thursday!
I've tried this in our project and I can't get it to work. A few things...

I actually don't see the original warning posted above at all anymore (though we definitely used to get it). This is true regardless of whether or not I incorporate any changes into my dbt_project.yml:

[WARNING]: The constraint type primary_key is not enforced by
snowflake. The constraint will be included in this model's DDL statement, but it
will not guarantee anything about the underlying data. Set 'warn_unenforced:
false' on this constraint to ignore this warning.

I definitely have models that include a primary_key constraint and that don't specify warn_unenforced. Like this one:

Did something change with this?

We do still get this warning:

[WARNING]: Constraint types are not supported for view materializations
and will be ignored.  Set 'warn_unsupported: false' on this constraint to ignore
this warning.

I've tried adding the following to my dbt_project.yml:

flags:
  warn_error_options:
    silence:
      - ConstraintNotEnforced
      - ConstraintNotSupported

But it doesn't seem to change anything. The not supported warning above still appears. The not enforced one does not (though, again, it doesn't appear regardless of whether or not I have this in the project.yml).
I also want to note that it's a little tricky to test these in the IDE because they don't show up as warnings when you run or build a model but rather during parsing (which is hidden unless you click the little "ready" pill). But then they show up when you run a job.
On a related note, the warning itself could be more informative. 😬 When you're staring at something like this screenshot, and your project has 2,000 models, it's a little hard to know which ones need to be updated. 😃 I mean, if we can turn the warning off entirely, that'd be even. But if we are going to get the warning, would be nice to know which model is generating the warning. Thank you!! Appreciate your help!

Following up in case anyone else comes across this. Looks like we needed to add:
   - UnsupportedConstraintMaterialization
to the list of errors that we're suppressing.
Also, while I found that removing ConstraintNotEnforced had no effect in the IDE, I did find that if I removed it, then our production jobs would throw the unenforced constraint warning. So we also need to leave that one in.


Trace requests with thread context

When a request enters the entry servlet add a fishtag with thread context.
When a request enters otter then check for a trace id header, X-Correlation-ID,  and add it to the thread context.

wont fix, implementing apps should implement this.


Users can join twice after end of a game

Stephen Otunba [4:48 PM]
join
Watch WordsBOT [4:48 PM]
steveo has joined the game!
[4:48]
Here are the teams:
[_Red team_]
sdhar (Leader)
mattb
steveo
[_Blue team_]
eric (Leader)
shruthi
サミア ダー [4:48 PM]
join
Watch WordsBOT [4:48 PM]
sdhar has joined the game!
[4:48]
Here are the teams:
[_Red team_]
sdhar (Leader)
mattb
steveo
[_Blue team_]
eric (Leader)
shruthi
sdhar

Need a way to reproduce this.

No way to reproduce.  Closing.


Controller testing requires more dancing than what the documentation suggests

I was reading this page:
https://github.com/plataformatec/devise/wiki/How-To:-Stub-authentication-in-controller-specs
It suggests mocking warden and controller. But I find that for me, request.env['warden'] is nil, so even with this setup code, every test fails.
A hint somewhere else suggested to use Warden::Test::Mock, but even that wasn't enough, and the bare minimum it appears I can get away with is as follows:
class ActionController::TestCase
  include Devise::TestHelpers
  include Warden::Test::Mock

  setup do
    request.env['devise.mapping'] = Devise.mappings[:users]
    request.env['warden'] = warden     # <= had to explicitly set into environment here!
  end

  def logged_in(user)
    warden.stubs(:authenticate!).returns(user)
    @controller.stubs(:current_user).returns(user)
  end
end

I know I could probably just edit the wiki myself, but I thought I'd run it through as an issue first in case there is a better way.

Have you seen our Testing section on the README? It's probably a more suitable guide for dealing with tests and we need to update/remove that wiki page.
I'm closing this one as it isn't an issue with the codebase.

I had seen the readme as well, but reading that didn't get my tests to pass, and searching for more information was how I found the Wiki page.
Looking at the readme again, though, request.env['warden'] appears to be missing from that as well.

Okay, after giving the non-mocking way another shot, I have eventually got the tests passing again, but only after employing another hack which I believe I should not have to be performing. Here's the situation.
Up in the test helper:
class ActionController::TestCase
  include Devise::Test::ControllerHelpers
  setup do
    request.env['devise.mapping'] = Devise.mappings[:users]
  end
end

We have one test which sets up the user who is about to login and this is the only test which fails. Its setup is as follows:
  setup do
    user = User.create!(name: 'Admin User', email<EMAIL_ADDRESS>                             password: 'password', password_confirmation: 'password')
    user.roles << roles(:administrator)
    sign_in user
  end

Then one of the tests, I'll use the most trivial one:
  test "viewing index page" do
    get :index

    assert_response 200
  end

This fails with response being 302 instead of 200, because it's trying to redirect to the login page.
If I do this instead:
  setup do
    user = User.create!(name: 'Admin User', email<EMAIL_ADDRESS>                             password: 'password', password_confirmation: 'password')
    user.roles << roles(:administrator)

    #HACK: Pull down a new copy of the user, because sign_in doesn't work
    #       with the one we already have!
    user = User.where(id: user.id).first

    sign_in user
  end

Now the test passes. I don't understand why I have to pull a new copy of the user to sign in, but I assume that the instance I had just created was poisoned somehow. Maybe this could also explain why after resetting the password on the real site, I get booted out of the site instead of being signed in, but I'm not really sure if that's the same issue yet.