Refactored keybindings

This is a refactoring of how keybindings and actions work.
I've modified bindings.go to store keybindings as strings internally instead of as function pointers. This makes it simple to centralize lots of duplicate code related to pre and post actions for plugins. This shaves about ~500 lines of boilerplate from actions.go and creates a pre and post plugin interface that is guaranteed to be the same for all actions. I've created a new function in actions.go, DoActions, that processes a string of actions and executes them.
This is a large change that unfortunately breaks compatibility with plugins. The main API change is that view methods no longer take a usePlugin bool parameter and now all behave as if called with usePlugin=false. I've updated autoclose and linter to work with this change. It should be relatively simple to update other plugins to work with this change.
If a plugin really needs access to an action with usePlugin=true, it can call DoActions directly, which takes a string of actions and handles pre and post plugin callbacks, but I wouldn't expect plugins would generally want this.
In addition to providing a cleaner internal structure, this also makes it simpler to add more complicated bindings since binding strings are now parsed on each key press. It would be possible to add to the DoActions function to do things like handle binding to commands. This would make it possible to do something such as bind a key to "Command: run jshint ${filename}" or something similar. I understand that this overlaps with plugin functionality, but I think it would be handy to add bindings like this.
I've tested this out a bit, and it appears to work fine. I've tested many common actions including macros and verified that the autoclose, linter, and snippets plugins all work with this change.
I don't expect this to get merged right away as it stands, but I'd love to hear feedback on moving in this direction or implementing any part of this.

I've added a commit which allows View actions to optionally take a bool which ends up just being ignored. This means that calling e.g. Backspace(false) is now identical to calling Backspace(). This greatly improves plugin compatibility.
I wouldn't expect many plugins to be calling View actions with usePlugin=true as it would be easy to create an infinite loop that way. If a call such as Backspace(true) is made now, it will succeed, but it will silently skip running any plugin callbacks.


Update cloudwatch, sdk-core, ses, sns, sqs, ssm to 2.20.126

About this PR
📦 Updates

software.amazon.awssdk:cloudwatch
software.amazon.awssdk:sdk-core
software.amazon.awssdk:ses
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:ssm

from 2.20.120 to 2.20.126
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #2850.


Update beacon network test vectors to latest spec

Test vectors did not follow yet the latest spec changes regarding OptimisticUpdate an FinalityUpdate content keys.
Also removed the slot number from them as it doesn't really make sense for most of the objects.

LGTM.  I've verified that we can generate these same new content keys.
One related question, should we also update the name of the field in the content keys for the optimistic and finality updates to be signature_slot instead of optimistic_slot and finalized_slot?

One related question, should we also update the name of the field in the content keys for the optimistic and finality updates to be signature_slot instead of optimistic_slot and finalized_slot?

Yeah, I had the same idea while I was adjusting the code in Fluffy. To rename it to signature_slot instead of optimistic_slot. (or attested_slot in the case we would have taken that one).
Also because I think the optimistic slot typically refers more to the attested_header.slot


Search error

Does this issue occur when all extensions are disabled?: Yes/No

This problem occurs on the vscode server. Here is the version information.
Version: 1.91.1
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:08:03.155Z
Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Steps to Reproduce:
The steps to reproduce are the same as the first issue, but I'm not sure if this issue has been fixed yet. I reproduced the problem on the vscode client, installing the plugin, and connecting to the remote.  My system is Windows OS.

I'm trying to reproduce this problem. On a windows server, the fsPath is spliced by \\. When verifying, The authority of the URI is localhost:8080. Therefore, the verification fails and an error is reported in the search box.
I took a look at the code and changed fsPath to path in line 257 of the queryBuild.ts file. The query works fine. But fsPath is still concatenated with \\.
I would like to ask, what is the difference between fsPath and path? When does fsPath use\\ to concatenate.
Looking forward to your answer.

I found the reproduction scenario of problem three. This is the IDE version information.
Version: 1.91.1 (user setup)
Commit: f1e16e1e6214d7c44d078b1f0607b2388f29d729
Date: 2024-07-09T22:06:49.809Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.19045
Steps to Reproduce:

Installing the vscode and remote-ssh extension
Connecting to a Remote Server
For other operations, see question one.

Can you file separate issues for these three? Or at least a separate one for the first two?

The edit area opens only other files, that is, other files are opened, but the files in the current work area are not opened.

I'm not sure if I understand what you're saying here, can you rephrase?

My system is Windows OS.

What OS is your remote? I'm assuming it's windows if the path uses \\ path separators?

Okay, I've submitted questions one and two separately.

The edit area opens only other files, that is, other files are opened, but the files in the current work area are not opened.
I'm not sure if I understand what you're saying here, can you rephrase?

This means that you open a file in the editing area that is not in the working area. You can open an extra file at will through the Open File... menu.

What OS is your remote?

My remote is linux.

Also, please confirm if this issue is also present on vscode server, I am seeing this issue on vscode server as well

Hmm, yes, I can reproduce this issue.


Example code in hover + css animation doesn't work very good

The example code in the description of this challenge doesn't really work. I'm guessing there's supposed to be a smooth animation, but it doesn't do that - and I can't really keep the image hovered because it changes sizes on hover, which causes me to not have it hovered.

Can I take up this issue?

Hi moT01,
I've created this pull request for the issue you raised.
This is my first open source contribution so I hope it all goes well!

i will work on this issue


feat(serenity-bdd): Support for Serenity BDD 4

Resolves #1147

Requires https://github.com/serenity-bdd/serenity-core/pull/3345

Requires serenity-bdd/serenity-core#3364

New report format
scenario-clear-completed-button-should-be-hidden-when-there-are-no-items-27a82ef199.json


TripleO manual deployment

Following http://www.anstack.com/blog/2016/07/04/manually-installing-tripleo-recipe.html
installation hangs doing introspection, regardless ironic node-list looks good.

Hey dbaxps thanks for the feedback, currently master is having a bug when running introspection, I'll let you know when the issue is solved.

I have rebuilt instack-undercloud-5.0.0-0.20160720101556.38dc0ec.el7.centos.src.rpm via patch
https://review.openstack.org/gitweb?p=openstack/instack-undercloud.git;a=patch;h=33e9d78dcdbc9a3737bfc009660a5bb2698313e4, and pre-installed instack-undercloud-5.0.0-0.20160720101556.38dc0ec.el7.centos.noarch.rpm on VIRTHOST . Right after instack(VM)
creation scp'ed patched rpm to instack,  activated repos and pre-installed patched rpm on instack.
Then run tripleo.sh step by step. Patch works
#################
tripleo.sh -- Register nodes
#################
You must source a stackrc file for the Undercloud.
Attempting to source /home/stack/stackrc
Done
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
Successfully registered node UUID 85948766-9102-43cc-b677-4ff4f45cdadb
Successfully registered node UUID c896bd9c-9be3-430d-8d79-de3d12e4c394
Successfully registered node UUID 8c400e30-5218-4ab0-a80d-8fba961cd469
Successfully registered node UUID 7bfec566-95cf-462a-bd2e-45146147b718
Successfully set all nodes to available.
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
| UUID                                 | Name | Instance UUID | Power State | Provisioning State | Maintenance |
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
| 85948766-9102-43cc-b677-4ff4f45cdadb | None | None          | power off   | available          | False       |
| c896bd9c-9be3-430d-8d79-de3d12e4c394 | None | None          | power off   | available          | False       |
| 8c400e30-5218-4ab0-a80d-8fba961cd469 | None | None          | power off   | available          | False       |
| 7bfec566-95cf-462a-bd2e-45146147b718 | None | None          | power off   | available          | False       |
+--------------------------------------+------+---------------+-------------+--------------------+-------------+
#################
tripleo.sh -- Register nodes - DONE.
#################
[stack@instack ~]$ ./tripleo-ci/scripts/tripleo.sh --introspect-nodes
#################
tripleo.sh -- Introspect nodes
#################
You must source a stackrc file for the Undercloud.
Attempting to source /home/stack/stackrc
Done
WARNING: openstackclient.common.utils is deprecated and will be removed after Jun 2017. Please use osc_lib.utils
Setting nodes for introspection to manageable...
Starting introspection of manageable nodes
Waiting for introspection to finish...
Introspection for UUID 8c400e30-5218-4ab0-a80d-8fba961cd469 finished successfully.
Introspection for UUID 7bfec566-95cf-462a-bd2e-45146147b718 finished successfully.
Introspection for UUID 85948766-9102-43cc-b677-4ff4f45cdadb finished successfully.
Introspection for UUID c896bd9c-9be3-430d-8d79-de3d12e4c394 finished successfully.
Introspection completed.
Setting manageable nodes to available...
#################
tripleo.sh -- Introspect nodes - DONE.
#################


Polices are missing from the default location

Microsoft Best Practice policies are missing on the default installation location. There is no Polices folder under C:\Program Files (x86)\Microsoft SQL Server\140\Tools.  Please let us know if I can download the polices from any other location.

@kasarava : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Yiisoft\Di\NotFoundException No definition or class found or resolvable for "Cycle\ORM\Select" while building "App\Invoice...Controller" -> "App\Service\WebControllerService" -> "App\Invoice......Service" -> "App\Invoice......Repository" -> "Cycle\ORM\Select".

What steps will reproduce the problem? Generate an entity file using the generator
What is the expected result? A smooth run through
What do you get instead? The above error.
Additional info

Q
A

Version
1.0.?

PHP version
8.2.1

Operating system
Windows 10

Go into your entity file and make sure that your entity has been assigned a primary id.
#[Column(type: 'primary')]
    private ?int $id =  null;

Remember to:
1.) Remove your schema.php file from the views/resources/runtime folder so that cycle can rewrite it in write only mode which you changed at ...
2.) config/common/params.php
approx. line 169
 'mode' => PhpFileSchemaProvider::MODE_WRITE_ONLY,

3.) Once the table has been rewritten remember to:
change the mode back to
'mode' => PhpFileSchemaProvider::MODE_READ_AND_WRITE,

If you have built an Entity.php file from an intermediary table using the generator software, remember to delete the intermediary table because cycle will create a table based on the naming convention of the entity file.


libnd4j: cuDNN packaging

Libnd4j (and hence SameDiff) now has cuDNN support.
Building with cuDNN is optional, however.
The question here is releasing nd4j-cuda with vs. without cuDNN.
Clearly, for deep learning use cases, we want cuDNN by default. But for users who need ND4J only (no SameDiff, no DL4J) they will not want the size overhead of cuDNN - i.e., it should be an optional component.
We should be able to to release one binary and dynamically link if cuDNN is available - but there are some questions about how to do this for Windows.
Ideally this would be resolved before release.

cuDNN is like 10 times smaller than the rest of CUDA. Why are we even worried about this?

It's 200MB compressed for Linux.

yeah, it's been rapidly getting bigger with each new release
on windows (uncompressed), cudnn 5 was like 80mb... latest cudnn (7.6.5) is 436mb

And the rest of CUDA is like 700 MB compressed, so what's the point?


feat: slider: Add inline extremity label position option

SUMMARY:
Adds Slider labelPosition prop, adjusts ref and html to enable responsive inline label position.
Minor change to alphabetize Pagination component props.
https://user-images.githubusercontent.com/99700808/200404354-5a72547d-4a65-438c-9a38-a6f0a9330b7e.mp4
JIRA TASK (Eightfold Employees Only):
ENG-32662
CHANGE TYPE:

[ ] Bugfix Pull Request
[X] Feature Pull Request

TEST COVERAGE:

[ ] Tests for this change already exist
[X] I have added unittests for this change

TEST PLAN:
Pull the PR branch and run yarn and yarn storybook. Verify the Slider stories behave as expected.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@3719fa5). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #432   +/-   ##
=======================================
  Coverage        ?   84.50%
=======================================
  Files           ?      724
  Lines           ?    15715
  Branches        ?     5500
=======================================
  Hits            ?    13280
  Misses          ?     2368
  Partials        ?       67

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

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


Added brew relinking

I've found that not only macdeployqt didn't fix the relinking of QT, but wasn't relinking some library that I used from Brew.
For example I link fftw (libfftw3.3.dylib) which is copied in the Frameworks of the bundle but was itself still linking to the brew path /usr/local/lib/gcc/6/libgcc_s.1.dylib
I had a total of 12 libs like these which I had to manually relink using install_name_tool
So I added this for the brew libraries which are located in /usr/local. To do this I added
two regex: BREWLIB_REGEX and a  BREWLIB_NORMALIZED plus the 2 functions is_brew_lib called only if it's not a Qt lib or plugin and normalize_brew_name to relink.
I found that this fixes all my problems and hoe it help someone else.

Didn't have at all some extra time to put on this...
Thanks a lot for sharing!
Also I don't own a mac and i'm aware of macdeployqt problems with brew only since you opened the issue #1 . Does this fixes it?


[Bug]: no such target '@local_config_platform//:constraints.bzl': target 'constraints.bzl'

What happened?
I get an error that seems to be related to this library when executing the stardoc tests in rules_ts_proto. It only occurs with bazel 5.* on CI.
Run bazel --bazelrc=$GITHUB_WORKSPACE/.github/workflows/ci.bazelrc --bazelrc=.bazelrc test //...
2023/03/10 14:44:17 Downloading https://releases.bazel.build/5.3.2/release/bazel-5.3.2-linux-x8[6](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:7)_64...
Starting local Bazel server and connecting to it...
INFO: Invocation ID: 2b3d3c3c-6[7](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:8)0d-4bc1-afad-22177f3199d9
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=0 --terminal_columns=[8](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:9)0
INFO: Reading rc options for 'test' from /home/runner/work/rules_ts_proto/rules_ts_proto/.github/workflows/ci.bazelrc:
  Inherited 'build' options: --announce_rc --disk_cache=~/.cache/bazel --repository_cache=~/.cache/bazel-repo
INFO: Reading rc options for 'test' from /home/runner/work/rules_ts_proto/rules_ts_proto/.github/workflows/ci.bazelrc:
  'test' options: --test_output=errors --test_env=XDG_CACHE_HOME
Loading:
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 2 packages loaded
    currently loading: docs ... (2 packages)
DEBUG: Rule 'rules_proto_grpc' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1675443033 -0800"
DEBUG: Repository rules_proto_grpc instantiated at:
  /home/runner/work/rules_ts_proto/rules_ts_proto/WORKSPACE:18:28: in <toplevel>
  /home/runner/work/rules_ts_proto/rules_ts_proto/ts_proto/repositories.bzl:40:1[9](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:10): in rules_ts_proto_dependencies
  /home/runner/work/rules_ts_proto/rules_ts_proto/ts_proto/repositories.bzl:15:[10](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:11): in git_repository
  /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule git_repository defined at:
  /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
Analyzing: 18 targets (6 packages loaded, 0 targets configured)
DEBUG: Rule 'com_github_grpc_grpc_web' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1673335627 -0800"
DEBUG: Repository com_github_grpc_grpc_web instantiated at:
  /home/runner/work/rules_ts_proto/rules_ts_proto/WORKSPACE:18:28: in <toplevel>
  /home/runner/work/rules_ts_proto/rules_ts_proto/ts_proto/repositories.bzl:[11](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:12)1:19: in rules_ts_proto_dependencies
  /home/runner/work/rules_ts_proto/rules_ts_proto/ts_proto/repositories.bzl:15:10: in git_repository
  /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule git_repository defined at:
  /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
Analyzing: 18 targets (65 packages loaded, 156 targets configured)
DEBUG: Rule 'com_google_protobuf_javascript' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1678429505 -0800"
DEBUG: Repository com_google_protobuf_javascript instantiated at:
  /home/runner/work/rules_ts_proto/rules_ts_proto/WORKSPACE:18:28: in <toplevel>
  /home/runner/work/rules_ts_proto/rules_ts_proto/ts_proto/repositories.bzl:46:19: in rules_ts_proto_dependencies
  /home/runner/work/rules_ts_proto/rules_ts_proto/ts_proto/repositories.bzl:15:10: in git_repository
  /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/bazel_tools/tools/build_defs/repo/utils.bzl:233:18: in maybe
Repository rule git_repository defined at:
  /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
ERROR: /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/aspect_bazel_lib/lib/private/docs/BUILD.bazel:10:[12](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:13): no such target '@local_config_platform//:constraints.bzl': target 'constraints.bzl' not declared in package ''; however, a source file of this name exists.  (Perhaps add 'exports_files(["constraints.bzl"])' to /BUILD?) defined by /home/runner/.cache/bazel/_bazel_runner/c1a8ca0554eb96646292b108389786d1/external/local_config_platform/BUILD.bazel and referenced by '@aspect_bazel_lib//lib/private/docs:local_config_platform_constraints'
ERROR: Analysis of target '//docs:rules' failed; build aborted:
INFO: Elapsed time: 6.809s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (67 packages loaded, [15](https://github.com/gonzojive/rules_ts_proto/actions/runs/4385596763/jobs/7678527685#step:6:16)8 targets configured)
ERROR: Couldn't start the build. Unable to run tests
FAILED: Build did NOT complete successfully (67 packages loaded, 158 targets configured)
Error: Process completed with exit code 1.

Version
Development (host) and target OS/architectures:
Output of bazel --version:
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
Language(s) and/or frameworks involved:
How to reproduce
git clone git@github.com:gonzojive/rules_ts_proto.git
cd rules_test_proto
git checkout 84c449c804515328f9a3a8302c28862d30c4bff2
bazel test //...

Any other information?
No response
Fund our work

[ ] Sponsor our open source work by donating a bug bounty

The @local_config_platform//:constraints.bzl export_files was only added in Bazel 6.
For Bazel 5 there is a work-around required.
load("//lib:repositories.bzl", "aspect_bazel_lib_dependencies")

aspect_bazel_lib_dependencies(override_local_config_platform = True)

which creates a local_config_platform instead of relying on the Bazel created one.

Hey @gonzojive I'm assuming Greg's answer solved this, please comment again if not?


Tab bar doesn't follow color scheme

All other parts seem to follow accent, just not tab bar. How do I fix this? This seems to be an error on my part but the stylesheets seem to be correct.
Edit:imgur

After seeing the fix, I applied it but the other parts don't seem to get the accent as shown in the second image of the gallery.


[Cosmos] removing six dependency from SDK

Request from https://github.com/Azure/azure-sdk-for-python/issues/26895. Removing the six package from the SDK entirely as part of the efforts of aligning the SDKs with Python3.

/azp run python - cosmos - tests


Update RawRepresentable conformance of Hashable

Update RawRepresentable conformance of Hashable by Removing deprecated hashValue

Resolves SR-12445 & SR-13851

Closing. The Standard Library merely triggers the issue here, it's not the cause of the problem. The diagnostic is emitted incorrectly, so the right fix is to investigate why that happens and fix the diagnostic logic within the compiler.


Issue: Inability to serialize langchain modules such as conversational retrieval chain, SQL database

Issue you'd like to raise.
In creating an app, ideally, you would like to let's say
db = SQLDatabase.from_uri(DATABASE_URI)
in one endpoint, and use the db in other endpoints,
The second endpoint could be what users get access to, so in getting responses, it should be quick, hence only accessing the already loaded db
but I cannot serialize db from the first endpoint, hence i have to include
db = SQLDatabase.from_uri(DATABASE_URI)
in the user endpoint, meaning anytime they hit the endpoint, db is run which delays significantly, and doesn't make for a good user experience, how do I solve this issue
Suggestion:
No response

So how can i use this approach to store a whole class such as db from db = SQLDatabase.from_uri(DATABASE_URI)
in aMYSQL database in one endpoint, and retrieve it in another endpoint


Enable https

Added in commit c79be99eea2cc6cebc0b2a3ee8994a6b0e2078f8
Author: Piotr Gregor<EMAIL_ADDRESS>Date:   Wed Aug 26 22:47:42 2020 +0000
Fix SSL issues

commit 08f6d17452467660572f72a99eea0a31ea55b138
Author: Piotr Gregor<EMAIL_ADDRESS>Date:   Wed Aug 26 20:22:33 2020 +0000
Use separate cert and key for SSL socket

commit 99c001f39bc245aaf4acc8e1172d80508aa6c5f2
Author: Piotr Gregor<EMAIL_ADDRESS>Date:   Wed Aug 26 17:24:28 2020 +0000
Add support for HTTPS to CA service

commit 0531d66f8b1c1df62d240d2fe7b84829144fca13
Author: Piotr Gregor<EMAIL_ADDRESS>Date:   Tue Aug 25 23:19:35 2020 +0000
Add support for HTTPS to the lib


fix(helm): set chart appVersion to 4.0.2

SUMMARY

Fixed Helm version to match latest release
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Ruh roh... thanks for the approval @dpgaspar but it seems we didn't merge this fast enough! @alecodev could you rebase/update the PR, and we'll try to snipe the merge button a little faster this time?

Moving this to draft mode, hopeful that @alecodev comes back to touch it up and mark it as "ready for review" again :)

watching

I'm assuming @alecodev isn't coming back to rebase this... closing for now, but happy to reopen as needed.


Code Diagramm

Please build a code diagram with different functions or classes. Think about the needs of the different functions (as in the portfolio tasks)

Hey Guys, this is the code diagramm that might work for our project.
Zeichenfläche 1.pdf

I have also created a skeleton document which I will push in a new branch for better understanding.


Logically equivalent functions return different Types when return is a Promise | non Promise

TypeScript Version:  3.2.x -> 3.6.x

Search Terms:
Typescript Promise async inconsisent
Code
ts-playground
interface Type1 {
  a: string;
}

interface Type2 {
  a: string;
  b: number;
}

const func1 = (arg: any) => {
  var a = Promise.resolve({} as Type1);
  var b = Promise.resolve({} as Type2);

  return arg ? a : b; // Promise<Type1>
};

const func1Async = async (arg: any) => {
  var a = Promise.resolve({} as Type1);
  var b = Promise.resolve({} as Type2);

  return arg ? a : b; // Promise<Type1>
};

const func2 = (arg: any) => {
    const func = () => {
        var a = {} as Type1;
        var b = {} as Type2;

        return arg ? a : b;
    }
    return Promise.resolve().then(func) // Promise<Type1>
};

const func2Async = async (arg: any) => {
  var a = {} as Type1;
  var b = {} as Type2;

  return arg ? a : b; // Promise<Type1>
};

const func3 = (arg: any) => {
    const func = () => {
        var a = {} as Type1;
        var b = Promise.resolve({} as Type2);

        return arg ? a : b;
    }
    return Promise.resolve().then(func) // type error
};

const func3Async = async (arg: any) => {
  var a = {} as Type1;
  var b = Promise.resolve({} as Type2);

  return arg ? a : b; // Promise<Type1 | Type2>
};

Expected behavior:
Unless I made a mistake. Everyone of these function is equivalent. They should have equivalent type signatures
Actual behavior:
The return types differ and some have type errors.
This was an actual headache to fix. The logic apparently only works properly inside func3Async
I can maybe live with typescript thinking the first return type is the return type of the function since that mistake is at least consistent. However func3 should not be type erroring.
Playground Link:
http://www.typescriptlang.org/play/#code/JYOwLgpgTgZghgYwgAgCoE8AOECMyDeAUMsnAFzIDOYUoA5gNyEC+hhoksiKG2ATAWKkK1WiEZCARhRABXALaToTVgHpVAWi3aduvdsIIA9iGrIYskAjwBeZAAo4UOhTgh0ASmQ2AfIJIAbk6k3sgAClBG8sCUEAB0UBCURgA2ARD2+MyklGhYuB5MgcGSoRFRMfGJyWkZWTl5-IVsJIlgslAgpM7IAPwhFJIMyOrhkdGxADy8uD4sTIYmZhZWOACClOhWoXCb247Oru5evv7IQVAhduUTVUmp6ZnZu40FReclZeOVCfe1Tw0ZnxmkI2h0uk46H0BsghiNVGMKlMZjg5swmOp9FjsYtTGBzJYEAI7AcXKRjt4-EQSCRjHiCdsSScqUIaTSLlcCM9cij3mzipdSnZ6i8gQt+TSwZ1ulD+nBkINhqzkKw2VKujcftUHhkPHEwAALCAgewrBBeUaa5H5VHzNh05aEvgbLYIHZ7N2ko6eSlnDny4Xc144d4coVcwH5Pji5DqmXQ+WK+GI27TG1ojGabHZnS4x1WADMoS95J9p2pNId+LNxeZZwl-tCIp5Nr5-LDXyRdxqj2br2BMYlcchCYVsKVbNVkog7WlVu7OvsesNxtNhItCLA+WQ0EiUDteerhILLsZOVdDkh3rrFcbgcj2BDQg712+sV+PbqQaBINaM-B8ZymOcKWm+EBpo+yAAD79hmhBAA
Related Issues:

There's no error in the Playground?

type error is fixed with 3.6.3 (was not available in the playground at the time)
The type mismatch with func3Async still exisits

The problem here is that you have two types (Type1 and Type2) that are subtype-relatable, so certain operations that reduce unions of the form T | U to T when U is a subtype of T trigger under certain conditions and not others. Ultimately this is really a type display issue; when these types are used in practice they're converted to their reduced forms. Adding a disjoint member to Type1 causes behavior closer to what you might expect.

Here is an additional simpler example:
http://www.typescriptlang.org/play/?ts=3.6.3&ssl=9&ssc=3&pln=1&pc=1#code/MYewdgzgLgBAZiEMC8MAUBDAXDDYCeAlCgHwwAKATiALYCWEApgHSWMQgA2Abo5ocygALRmDRsIAB1IwA3gCgYMOnHQTJxBUqVsoAV0pgYAcmiU6YAObHFMAL4xGnJnNs7G+wxWr0mrdly8aALCouLs0shkWtrunkYAjAAMSQDcbvaEtnbydoRAA
const foo = (a: any) => Promise.resolve(a).then(resp => {
  if (resp) {
    return 'string'
  } else {
    return Promise.resolve().then(resp => {
      return 100;
    })
  }
})

yields error:
Argument of type '(resp: any) => "string" | Promise<number>' is not assignable to parameter of type '(value: any) => number | PromiseLike<number>'.
  Type '"string" | Promise<number>' is not assignable to type 'number | PromiseLike<number>'.
    Type '"string"' is not assignable to type 'number | PromiseLike<number>'.

Adding async fixes everything
const foo = (a: any) => Promise.resolve(a).then(async resp => {
  if (resp) {
    return 'string'
  } else {
    return Promise.resolve().then(resp => {
      return 100;
    })
  }
})


Regularly pull k8s & CRD updates and upload the generated kcl schemas

Feature Request
Regularly pull k8s & CRD updates and upload the generated kcl schemas to artifacthub.
Regular tasks

[ ] check if there are new Kubernetes openapi releases (and other CRD releases)
[ ] download the oai/crd spec updates
[ ] generate the kcl schemas from the spec
[ ] generate the docs
[ ] package them
[ ] upload: uploading requires authentication, this step could be done manually.

My personal suggestion is to enable the https://operatorhub.io/ CRD ->KCL Schema -> https://artifacthub.io Link to ensure stability while accumulating model libraries.


:bug: CSRF Token unobtainable since syncthing commit 089fca23

syncthing-cli fails with "Failed to get CSRF token" since the token was renamed from
CSRF-Token=

to
CSRF-Token-[ID]=

Due to syncthing's auto-update this change is already released and renders the cli unuseable.

something is not right, it now crashes (see log)
could it be when the following is executed
client.id = request.Header.Get("X-Syncthing-ID")

the request is not done and thus returns null?
$> syncthing-cli id
panic: runtime error: slice bounds out of range

goroutine 1 [running]:
main.getClient(0xc2080560c0, 0xc20801e820)
	/go/src/github.com/syncthing/syncthing-cli/client.go:53 +0x89b
main.httpGet(0xc2080560c0, 0x832830, 0x14, 0x0)
	/go/src/github.com/syncthing/syncthing-cli/client.go:99 +0x33
main.generalStatus(0xc2080560c0)
	/go/src/github.com/syncthing/syncthing-cli/cmd_general.go:62 +0x46
github.com/AudriusButkevicius/cli.Command.Run(0x7f4690, 0x6, 0x0, 0x0, 0x880df0, 0x55, 0x0, 0x0, 0x0, 0x0, ...)
	/go/src/github.com/AudriusButkevicius/cli/command.go:108 +0xe98
github.com/AudriusButkevicius/cli.(*App).Run(0xc20801e680, 0xc20800a000, 0x2, 0x2, 0x0, 0x0)
	/go/src/github.com/AudriusButkevicius/cli/app.go:131 +0xbcd
github.com/AudriusButkevicius/cli.(*App).RunAndExitOnError(0xc20801e680)
	/go/src/github.com/AudriusButkevicius/cli/app.go:142 +0x57
main.main()
	/go/src/github.com/syncthing/syncthing-cli/main.go:60 +0x5bf

goroutine 6 [select]:
net/http.(*persistConn).readLoop(0xc20802e210)
	/usr/local/go/src/net/http/transport.go:928 +0x9ce
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:660 +0xc9f

goroutine 7 [select]:
net/http.(*persistConn).writeLoop(0xc20802e210)
	/usr/local/go/src/net/http/transport.go:945 +0x41d
created by net/http.(*Transport).dialConn
	/usr/local/go/src/net/http/transport.go:661 +0xcbc


Homebridge error Air Pressure range

Is there a way to eliminate or correct this Air Pressure Illegal Value error that fills up the logs?
2022-05-29T00:24:46.986Z Tasmota:mqtt emit homie/aurora-180701044/compressor/discharge-pressure 172.4
2022-05-29T00:24:46.987Z Tasmota:sensor statusUpdate WaterFurnace Compressor Discharge Pressure homie/aurora-180701044/compressor/discharge-pressure 172.4
[5/29/2022, 12:24:46 AM] [Tasmota] Updating 'WaterFurnace Compressor Discharge Pressure:Air Pressure' to 172.4
**_

[5/29/2022, 12:24:46 AM] [homebridge-tasmota] This plugin generated a warning from the characteristic 'Air Pressure': characteristic was supplied illegal value: number 172 exceeded minimum of 300. See https://homebridge.io/w/JtMGR for more info.

_**
[5/29/2022, 12:24:46 AM] [homebridge-tasmota] Error:
at Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2142:105)
at Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2045:14)
at Characteristic.updateValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1457:20)
at tasmotaSensorService.statusUpdate (/homebridge/node_modules/homebridge-tasmota/src/tasmotaSensorService.ts:247:29)
at Mqtt.emit (node:events:526:28)
at MqttClient. (/homebridge/node_modules/homebridge-tasmota/src/lib/Mqtt.ts:83:16)
at MqttClient.emit (node:events:526:28)
at MqttClient._handlePublish (/homebridge/node_modules/homebridge-tasmota/node_modules/mqtt/lib/client.js:1277:12)
at MqttClient._handlePacket (/homebridge/node_modules/homebridge-tasmota/node_modules/mqtt/lib/client.js:410:12)
at work (/homebridge/node_modules/homebridge-tasmota/node_modules/mqtt/lib/client.js:321:12)
2022-05-29T00:24:46.997Z Tasmota:mqtt emit homie/aurora-180701044/compressor/suction-pressure 171.4
2022-05-29T00:24:46.998Z Tasmota:sensor statusUpdate WaterFurnace Compressor Suction Pressure homie/aurora-180701044/compressor/suction-pressure 171.4
[5/29/2022, 12:24:46 AM] [Tasmota] Updating 'WaterFurnace Compressor Suction Pressure:Air Pressure' to 171.4

The maximum and minimum values for an air pressure sensor are here
https://github.com/NorthernMan54/homebridge-tasmota/blob/5859ddc2423c64ae4cc1db3e4aff39ae8da267b5/src/lib/CustomCharacteristics.ts#L68
And I based it on the the supported values from a BME280 sensor.   What range does your sensor support ?

Thanks, it’s actually mapped to suction pressure on a heat pump.  I’m not sure how low it can go.  It’s seems to usually be in the 100’s range.  It monitors the refrigerant charge.
I tried editing CustomCharacteristics.js in the application node_modules but that didn’t work and it wouldn’t be permanent on an update.  I’m running Homebridge in Docker.
Homekit is quite limited on what can be mapped to various sensors.
Thanks for getting back to me.
Kevin

On May 29, 2022, at 9:50 AM, Northern Man @.***> wrote:
The maximum and minimum values for an air pressure sensor are here
https://github.com/NorthernMan54/homebridge-tasmota/blob/5859ddc2423c64ae4cc1db3e4aff39ae8da267b5/src/lib/CustomCharacteristics.ts#L68 https://github.com/NorthernMan54/homebridge-tasmota/blob/5859ddc2423c64ae4cc1db3e4aff39ae8da267b5/src/lib/CustomCharacteristics.ts#L68
And I based it on the the supported values from a BME280 sensor. What range does your sensor support ?
—
Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-tasmota/issues/45#issuecomment-1140453874, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4WTTCTS45RL3L6ICDG7ODVMNY3ZANCNFSM5XHLRDPA.
You are receiving this because you authored the thread.

I would need to do a release to permanently change the lower limit, just need a recommendation for a value

Since atmospheric pressure is never going to approach 300 hPa unless it’s in the eye of a tornado, I’d either drop it to 100 or 0 until Apple adds a Characteristic for pressures other than barometric pressure.
Thanks,
Kevin

On May 29, 2022, at 10:57 AM, Northern Man @.***> wrote:
I would need to do a release to permanently change the lower limit, just need a recommendation for a value
—
Reply to this email directly, view it on GitHub https://github.com/NorthernMan54/homebridge-tasmota/issues/45#issuecomment-1140466295, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4WTTGFWN6UQIESPDH5CTDVMOAXFANCNFSM5XHLRDPA.
You are receiving this because you authored the thread.


[WIP] Export JAVA_OPTS and MAVEN_OPTS

If not in the environment already, export JAVA_OPTS and MAVEN_OPTS with options
that ensure that the JVM respects the cgroup memory size for its heap
calculations.

@bparees @jerboaa @gabemontero going to test this, but would also appreciate your opinions on this.  The intention is to export a small sane JAVA_OPTS such that if the Jenkins slave ends up running Java executables which respect the env var, the heap size calculations will "just work".  Naturally since maven doesn't respect JAVA_OPTS, we do the same for MAVEN_OPTS.
The aim is that anyone who runs gradle (respects JAVA_OPTS) or maven on the slave won't run into trouble with it overallocating and being killed by the OOM killer.
Thoughts?

@bparees @jerboaa @jim-minter I'm wondering if we should just prepend -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -Dsun.zip.disableMemoryMapping=true to JAVA_OPTS and MAVEN_OPTS even if they have some existing value associated with them.
If the user has specified some other -XX option that is somehow contradictory to them, they will still override since the last one wins.  But if the user is specifying other parameters unrelated, they still get the benefits these parameters provide.
Thoughts?
That said, I definitely believe @jim-minter is on the right track here.

I'm wondering if we should just prepend -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -Dsun.zip.disableMemoryMapping=true to JAVA_OPTS and MAVEN_OPTS even if they have some existing value associated with them.

As long as -Xmx overrides +UseCGgroupMemoryLimitForHeap it seems like a reasonable suggestion to me, but we need to confirm that behavior, otherwise we leave users w/ no way to opt out of the cgroup heap memory limit.
@jim-minter assuming your testing proves out, it seems like a reasonable step to me.

@bparees @jerboaa @jim-minter I'm wondering if we should just prepend -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap -Dsun.zip.disableMemoryMapping=true to JAVA_OPTS and MAVEN_OPTS even if they have some existing value associated with them.

This makes a lot of sense to me. At least the UseCGroupMemoryLimitForHeap option as this tells the JVM that it shouldn't use the physical memory of the host, but rather the cgroup limit for sizing its internal structures, choosing a sane default heap (if not set otherwise), etc. Not sure if some people might want to have -Dsun.zip.disableMemoryMapping=false.

As long as -Xmx overrides +UseCGgroupMemoryLimitForHeap it seems like a reasonable suggestion to me, but we need to confirm that behavior, otherwise we leave users w/ no way to opt out of the cgroup heap memory limit.

Setting UseCGgroupMemoryLimitForHeap tells the JVM that it should fail with OOM once the container limit has been reached. If both options, +UseCGgroupMemoryLimitForHeap and -Xmx are set, then instead of choosing the default heap size via ergonomics based on the container limit it will use -Xmx.

I've confirmed @jerboaa statement regarding use of both +UseCGgroupMemoryLimitForHeap and -Xmx, with -Xmx winning.
See https://github.com/openshift/jenkins/issues/418
Also, based on the customer interactions, seems like we should be worrying about GRADLE_OPTS as well, no?

I've confirmed @jerboaa statement regarding use of both +UseCGgroupMemoryLimitForHeap and -Xmx, with -Xmx winning.

The term "winning" is wrong. Without -Xmx and with +UseCGgroupMemoryLimitForHeap the default JVM ergonomics will be in place. It's as if you'd run java on a system with $CONTAINER_LIMIT as physical memory. In that case the JVM will pick some value for MaxHeapSize (usually 25% of that). Defaults can be overriden with various flags, -Xmx is one such hook to override the default.

Closing for https://github.com/openshift/jenkins/pull/442


Magento default frontend form validation does not work with Breeze which works with Luma

Magento default frontend form validation does not work with Breeze which works with Luma.
Using the class name with arguments like "validate-clean-url" does not work.
As an example,
with the breeze:

with no breeze (debug mode):

Even the "validate-email" does not work completely -
with the breeze:

with no breeze (debug mode):

Only "required-entry" works as expected.

Can you change your form to use data-validate attributes? Example: https://github.com/magento/magento2/blob/HEAD/app/code/Magento/Contact/view/frontend/templates/form.phtml#L47
p.s. It will not fix the 'validate-clean-url' because this validator is not implemented in Breeze. For now, I recommend using input type="url": https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/url

Hi @vovayatsyuk
Tested. The validation does not work with the Breeze demo contact form as well.
URL:

Email:

Breeze demo contact form Email and Tel:

Magento has a lot of built-in validators, but I don't think we need them in Breeze out of the box.
For now, I suggest you to add your own validator:
$.validator.validators['validate-clean-url'] = [
    (value) => $.validator.utils.isEmptyNoTrim(value) || /^(http|https|ftp):\/\/(([A-Z0-9][A-Z0-9_-]*)(\.[A-Z0-9][A-Z0-9_-]*)+.(com|org|net|dk|at|us|tv|info|uk|co.uk|biz|se)$)(:(\d+))?\/?/i.test(value) || /^(www)((\.[A-Z0-9][A-Z0-9_-]*)+.(com|org|net|dk|at|us|tv|info|uk|co.uk|biz|se)$)(:(\d+))?\/?/i.test(value),
    $t('Please enter a valid URL. For example http://www.example.com or www.example.com.')
];

Added docs about forms validation: https://breezefront.com/docs/validator


Read Firebase only when there is an update in it OR Get push notifications in NodeMCU

Hi
I need to read firebase only when there is an update in it, because I don't to make connection with it all the time which may increase number of connections in it. As there is a limit of 100 active connections so I have to only connect with the Firebase Realtime Database when there is an update.
Or is there a way to get notifications in NodeMCU the it make connection with database and read the updates.
Your advice is highly appreciated.
Thanks in Advcane.

Closing this, since the change I was pointing to has been merged.

syeedhaiderali did you get any solution because i am facing same problem with no solution
i dont what wrong with path in firebase.stream()
what i actually need to put here
whatever i put e.g node name
streaming error is the error


Provide a make install target.

make install should honor a user installation folder (prefix) or take a system default,

The spec file demonstrates that files need to go into /usr/bin, but I fail to see why all the .x suffixes are needed. This is totally against convention.
@opcm maybe we can fix up the build system to be a bit more modern and do things like installing into the correct locations correct?

https://github.com/clearlinux/distribution/issues/1390

@ahkok  could you please give feedback for https://github.com/opcm/pcm/pull/171

https://github.com/opcm/pcm/pull/172 - very WIP though, this may take me a bit of time.

We are not going to lose interest in cmake but it will take more time to adopt. In meantime we got "make install" with target prefix support: https://github.com/opcm/pcm/pull/178

make install is now suported: https://github.com/opcm/pcm/blob/f4ef45fb99a7adfeb048e2face84450c22cf5028/Makefile#L91

the issue has been resolved


Current stock view buttons not on screen to select

Thanks for the much awaited update to support grocy ver 3. On iPhone Xr the buttons is not available in the stock view and cut out of view. Also not possible to scroll and select the buttons. Workaround at this time is the trun the phone side ways for the buttons to show correctly.
See screen shots attached.
Side ways view the buttons is displayed, but normal way the buttons is out of view.

Uh oh thanks for the report. I'll try to reproduce in the simulator.
Are you able to scan? I'm having trouble with a real device which I can't reproduce easily on the simulator. I'm trying to get that fix out asap.

Just tested now and scan doesn't work. I run IOS 14.5 public beta. The app crash and close when trying to scan. Did confirm that app has camera access in IOS settings.
Let me know if I can test any thing else. I'm happy to assist.

Thanks it look like a lib compatibility problem. I think I have the problem
narrowed down.
On Mon, Mar 22, 2021, 12:27 PM dbruynb @.***> wrote:

Just tested now and scan doesn't work. I run IOS 14.5 public beta. The app
crash and close when trying to scan. Did confirm that app has camera access
in IOS settings.
Let me know if I can test any thing else. I'm happy to assist.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/PantryParty/pantry_party/issues/113#issuecomment-804206528,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABQ6MV5L6EZ5GHXSVVEXJ3TE5VYBANCNFSM4ZTM44RA
.

A new release has been submitted for apple to review. It can take a few hours to a day to be approved and made available for distribution.  The camera worked in the simulator, so lets hope it works when it gets out in the wild

Hey 1.2.2 was just approved and should be available for download. Can you give the camera a try?

Hey 1.2.2 was just approved and should be available for download. Can you give the camera a try?

Thanks, camera is working without any crashes. However the buttons is still out of view as per previous pictures attached.

@dbruynb Yep I didn't get to that one yet, thanks for the confirmation on the camera.


Fix logging so that it shows the task name

Right now, when the framework writes a log it isn't able to determine the name of the task that sent the message, making log messages look like for example like Class :: Wrote system time to hardware clock.
This has annoyed me for a while, and I was poking around genesis anyway so I thought I'd take a stab at fixing it.
This change makes the log DSL method look at the first ancestor (which is the task class) and grab the name from that. I thought Genesis::Framework::Task::SetupNTP was a bit of a mouthful, so I'm only grabbing the last part of it. I'm open for suggestions though.
The end result with the same example looks like this: SetupNTP :: Wrote system time to hardware clock.
@roymarantz @Primer42 @byxorna

sweet!  Would you fix the other instance of using self.class.name at line 171 in #tmp_path (same file) the same way.  Although less visible it is still wrong.  These have bothered me for a long time and I just never got around to fixing them.
:100:

Yeah, good point. Fixed that too now. I also took this opportunity to remove two unused requires from task.rb.

Have you thought of making a "private" method to get the name and using that in both places?  It would avoid the code duplication.

Yeah, sure. Does it need to be private though? I don't think it could hurt exposing the method.

I'm fine either way.  thanks

Sweet!


[HUDI-4911][HUDI-3301] Fixing HoodieMetadataLogRecordReader to avoid flushing cache for every lookup

Change Logs
Currently, HoodieMetadataLogRecordReader is flushing cache for every lookup it's doing, which led to multiple occasions of poor performance as MT had to be re-scanned over and over again, even though nothing really changed.
This PR rectifies that, additionally:

Making sure LogRecordScanner is not extended for MT (there's no reason for that, instead its configuration is simply expanded to accommodate for MT use-case)
Refining and cleaning up the API provided HoodieMetadataLogRecordReader
Avoiding unnecessary locking

Impact
Improved performance of metadata log record reader.
Risk level (write none, low medium or high below)
medium
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@alexeykudinkin : I see a WIP in title. So, is there some pending work in this patch. or good to review.

@nsivabalan this is still very much WIP

Fixed the compilation issue and some older comments.

hudi-bot run azure

@hudi-bot run azure

looks like we are caching all records in memory w/o any eviction policy. So, if we keep re-using the same reader for a long time, would there be any memory issues ?

looks like we are caching all records in memory w/o any eviction policy. So, if we keep re-using the same reader for a long time, would there be any memory issues ?

@nsivabalan we actually use ExternalSpillableMap to hold the records

CI is green:

https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=14262&view=results

CI is green:

https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=14417&view=results


GP not robust to NaN metric

I'm running MOBSTER with default parameters, and my model (for whatever reason) decided to produce np.inf, which took down the tuning process.
In particular, in transform_state_to_data, the normalization makes all the targets be NaN. One option would be to exclude inf from the normalization, but then probably the GP chokes. Setting inf to the largest observed value might make sense? Another option would be excluding the sample.
Any thoughts?

Hi Andreas, thanks for flagging this it seems like a good suggestion, @mseeger is the main author of this code and may be able to help you.


[SPARK-18580] [DStreams] [external/kafka-0-10] Use spark.streaming.backpressure.initialRate in DirectKafkaInputDStream

What changes were proposed in this pull request?
Use spark.streaming.backpressure.initialRate in DirectKafkaInputDStream
How was this patch tested?

unit tests in org.apache.spark.streaming.kafka010.DirectKafkaStreamSuite
tested on live system

This is intended as a PR for SPARK-18580

Can one of the admins verify this patch?

I added new commit, the default value of backpressureInitialRate if spark.streaming.backpressure.initialRate is now taken from spark.streaming.backpressure.pid.minRate, or 100 if that is also not set (which is the same as in org.apache.spark.streaming.scheduler.rate.RateEstimator).
And backpressureInitialRate, when applied, is now shared proportionally among all partitions.

Tests added

Any interest in picking this back up if you can get a committer's attention?

Yes

@zsxwing you or anyone else have time to look at this?

Can one of the admins verify this patch?

ok to test

@omuravskiy can you comment on
https://github.com/apache/spark/pull/19431
since it appears to be based on your PR

#19431 was merged, thanks for your work.  This PR should probably be closed.


404 at /articles/using_supervisord/

I found a broken link : https://docs.docker.com/articles/using_supervisord/

Hey @sscswapnil,
Thanks for reporting the broken link issue. Could you let us know how you arrived at the broken link?


Simplify lookup_nodes creation in the preload_lookup_nodes path

With https://github.com/facebook/akd/pull/436, we're adding additional labels into the BFS filter with some duplicate code. This code can be cleaned up.
This issue is a TODO to track the cleanup along with test-creation

Addressed by #441


Minimum Variance

I'll be implementing the minimum variance reconstruction algorithm.
Mozaffarzadeh, Moein, et al. "Linear-array photoacoustic imaging using minimum variance-based delay multiply and sum adaptive beamforming algorithm." Journal of biomedical optics 23.2 (2018): 026002.

Just to give brief update. I was having some issues with the Covariance matrix in python not matching up with matlab. I think this has to do with different implementations of the hilbert transform in scipy and matlab. Its not massively different, since it looks the same with imagesc() but some values are varying.
I'll look into this a later on, but it should be good enough to at least get the algorithm working.

Just to give a brief update, I am having some issues with the covariance matrix from python not exactly matching the one from Matlab. I believe this is an issue with an implementation difference between the Hilbert transform from scipy and matlab.
While this is something I'll check before the final commit, I think it should be good enough for now. As the covariance matrix looks the same - just some specific values don't match up.

@alexpattyn Will you find the time to open a pull request with your implementation so far? We could take it from there and finalise the code if you like :D Thanks!


Collect build timings

Rust 1.60 now allows collecting build timings.
This PR updates ci.yml to collect a timing report.
The report will be published as an HTML artifact on Github Actions.
This information would be useful to understand how various dependencies affect build times as well as better understand how build times change over time.
More info: https://blog.rust-lang.org/2022/04/07/Rust-1.60.0.html#cargo---timings
Signed-off-by: Maksym Pavlenko<EMAIL_ADDRESS>

Nice. LGTM


Column assignments fails with Float64Dtype type

What happened:
When using pandas' new Float64 nullable type (with pandas >= 1.2), column assignment fails with
TypeError: Cannot interpret 'Float64Dtype()' as a data type

Minimal Complete Verifiable Example:
Fails at least with pandas version 1.2.0 (below that, the new extension type was not introduced).
import pandas as pd
import dask.dataframe as dd

# some example data. Important is only the Float64, the new pandas extension type
df = dd.from_pandas(pd.DataFrame({"a": [1.1]}, dtype="Float64"), npartitions=1)

df.assign(new_col=df["a"])
# TypeError: Cannot interpret 'Float64Dtype()' as a data type

Full stacktrace
Traceback (most recent call last):
  File "bla.py", line 7, in <module>
    df.assign(new_col=df["a"])
  File "/home/nils/anaconda3/envs/dask-sql/lib/python3.8/site-packages/dask/dataframe/core.py", line 4004, in assign
    df2 = self._meta_nonempty.assign(**_extract_meta(kwargs, nonempty=True))
  File "/home/nils/anaconda3/envs/dask-sql/lib/python3.8/site-packages/dask/dataframe/core.py", line 360, in _meta_nonempty
    return meta_nonempty(self._meta)
  File "/home/nils/anaconda3/envs/dask-sql/lib/python3.8/site-packages/dask/utils.py", line 509, in __call__
    return meth(arg, *args, **kwargs)
  File "/home/nils/anaconda3/envs/dask-sql/lib/python3.8/site-packages/dask/dataframe/utils.py", line 391, in meta_nonempty_dataframe
    dt_s_dict[dt] = _nonempty_series(x.iloc[:, i], idx=idx)
  File "/home/nils/anaconda3/envs/dask-sql/lib/python3.8/site-packages/dask/dataframe/utils.py", line 578, in _nonempty_series
    data = np.array([entry, entry], dtype=dtype)
TypeError: Cannot interpret 'Float64Dtype()' as a data type

As a fix, I guess one wants to introduce a function similar to https://github.com/dask/dask/blob/master/dask/dataframe/utils.py#L43 (but for floats) and use it in https://github.com/dask/dask/blob/master/dask/dataframe/utils.py#L540. I am happy to open a PR to fix this if this solution is ok.
Environment:

Dask version: 2021.1.1
Pandas version: 1.2.0
Python version:
Operating System: ubuntu
Install method (conda, pip, source): conda

I think the solution that you propose is very reasonable and if you are willing to open a PR even better! Just as a heads up there is a release planned for friday (tomorrow) so it'd be great to get this in.

@jsignell PR is open - I hope it was still on time yesterday evening (European time)


Replace Gopher with Squid

remove gopher ui
remove mockServiceWorker
add squid widget
wip
pin abitype
remove mock service worker again

Closing in favor of iframe widget from squid router. React component widget is only compatible with NextJS builds :(


operator manifests: Validate repo_replacements

OSBS-8639

Add validation for operator_manifest.repo_replacements, where the user
can configure container image repo replacements that are not available
in OSBS site-configuration.
Signed-off-by: Adam Cmiel<EMAIL_ADDRESS>Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[x] "Signed-off-by:" line is present in each commit
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[x] Pull request includes link to an osbs-docs PR for user documentation updates

Release notes: none needed, support for related atomic-reactor patch


Importer: LTS -> Alpha loses posts_tags relationships etc

Note: We don't yet have a concrete plan for how we're going to do the migration path from LTS to Alpha. It may or may not involve Ghost's export & import functions.
Today I tried out importing an export generated via the LTS into the latest alpha. It mostly worked, and so I think this issue is probably somewhere between a "not considered yet" and a "bug".
All posts, users, tags, subscribers & settings are imported and updated as I'd expect (barring any known issues: https://github.com/TryGhost/Ghost/labels/importer).
However, after importing, posts don't have any tags associated with them.
Steps to Reproduce

Export a JSON file from an LTS blog, I did this from blog.ghost.org
Clear all data on your local blog
Import the JSON file
Check posts, and see that even though tags were imported, no post has a tag associated with it!

I believe this is likely something to do with the change to ObjectIDs and the complexities of the importer and the post -> tag relationships.
Note: this bug is NOT present when exporting and importing on the alpha, only with exports from LTS that are imported on the alpha.
Bonus: this should be much easier to re-implement with the use of ObjectIDs?
Technical details:

Ghost Version: master (4a4b2f6)
Node Version: 4.4.7
Database: Sqlite3

Here.
The strict comparison returns false for '1' === 1. This is what happens when LTS JSON is imported as the ids are integers in LTS db. Changing it to non-strict comparison fixes the issue.

@vivekannan Thanks for getting involved.
https://github.com/TryGhost/Ghost/blob/master/core/server/data/import/utils.js#L118
The post_id is an integer originally, but it get's auto converted into a string, because postsWithTags is an object.
We could either change the id comparison (convert to strings) or we fix the underlying problem and use map, and this is my preferred solution. map does not convert number to string by default.

we fix the underlying problem and use map

I am sorry, but I don't follow. map as in Array's map or underscore's map? Either way, not sure how it will solve the problem.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map
Something like:
postsWithTags = new Map()

each postTags
  postsWithTags.set(...)

each postsWithTags (postId, tagIds)
  ...
  return post.id === postId; // should be true, because post.id is Integer and postId was not converted

JavaScript has Map now? Did not know that! Will soon make a pull req.

Using Map does indeed solve the problem but unfortunately, jsHint complains that Map is undefined in new Map(); statement.  Is that OK?

@vivekannan
We need to update our .jshintrc file to support ES6 notation.
esversion: 6
I will push an update to LTS and master branch. If you rebase against the update, your jshint check should be successful.

OK.
On Mon, Jan 30, 2017 at 4:30 PM, Katharina Irrgang<EMAIL_ADDRESS>
wrote:

@vivekannan https://github.com/vivekannan
We need to update our .jshintrc file to support ES6 notation.
esversion: 6
I will push an update to LTS and master branch. If you rebase against the
update, your jshint check should be successful.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TryGhost/Ghost/issues/7866#issuecomment-276033992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHkl-iSy6m_lMX-YbxeA3ekwzm9hdB2_ks5rXcLDgaJpZM4LpaXL
.


chore: upgrade wagmi, dependencies

Changes

upgraded wagmi to 2.12.9
upgraded node version to v20
upgraded site, package, example dependencies
migrated type linting to new version of biome
fixed esbuild scripts, breaking changes
upgraded create cli template
upgraded typescript to 2.5.2
upgraded pnpm version
upgraded husky and migrated commitlint script

QAd against Chrome on desktop, mobile safari, mobile chrome on iOS, and rainbow browser


The device problem when running the ESM-IF

Hi, there is the problem. How can I solve it?
ubuntu@ip:~/esm/examples/inverse_folding$ python sample_sequences.py data/5YH2.pdb     --chain C --temperature 1 --num-samples 3     --outpath output/sampled_sequences.fasta
Downloading: "https://dl.fbaipublicfiles.com/fair-esm/models/esm_if1_gvp4_t16_142M_UR50.pt" to /home/ubuntu/.cache/torch/hub/checkpoints/esm_if1_gvp4_t16_142M_UR50.pt
/home/ubuntu/.conda/envs/tcrbert/lib/python3.9/site-packages/esm/pretrained.py:215: UserWarning: Regression weights not found, predicting contacts will not produce correct results.
  warnings.warn(
Transferred model to GPU
Native sequence loaded from structure file:
SVLQSLFEHPLYRTVLPDLTEEDTLFNLNAEIRLYPKAASESYPNWLRFHIGINRYELYSRHNPVIAALLRDLLSQKISSVGMKSGGTQLKLIMSFQNYGQALFKPMKQTREQETPPDFFYFSDFERHNAEIAAFHLDRILDFRRVPPVAGRLVNMTREIRDVTRDKKLWRTFFVSPANNICFYGECSYYCSTEHALCGKPDQIEGSLAAFLPDLALAKRKTWRNPWRRSYHKRKKAEWEVDPDYCDEVKQTPPYDRGTRLLDIMDMTIFDFLMGNMDRHHYETFEKFGNDTFIIHLDNGRGFGKHSHDEMSILVPLTQCCRVKRSTYLRLQLLAKEEYKLSSLMEESLLQDRLVPVLIKPHLEALDRRLRLVLKVLSDCVEKDGFSAVVENDLD
Saving sampled sequences to output/sampled_sequences.fasta.

Sampling.. (1 of 3)
Traceback (most recent call last):
  File "/home/ubuntu/esm/examples/inverse_folding/sample_sequences.py", line 124, in <module>
    main()
  File "/home/ubuntu/esm/examples/inverse_folding/sample_sequences.py", line 120, in main
    sample_seq_singlechain(model, alphabet, args)
  File "/home/ubuntu/esm/examples/inverse_folding/sample_sequences.py", line 34, in sample_seq_singlechain
    sampled_seq = model.sample(coords, temperature=args.temperature, device=torch.device('cuda'))
  File "/home/ubuntu/.conda/envs/tcrbert/lib/python3.9/site-packages/esm/inverse_folding/gvp_transformer.py", line 123, in sample
    logits, _ = self.decoder(
  File "/home/ubuntu/.conda/envs/tcrbert/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/ubuntu/.conda/envs/tcrbert/lib/python3.9/site-packages/esm/inverse_folding/transformer_decoder.py", line 117, in forward
    x, extra = self.extract_features(
  File "/home/ubuntu/.conda/envs/tcrbert/lib/python3.9/site-packages/esm/inverse_folding/transformer_decoder.py", line 158, in extract_features
    positions = self.embed_positions(
  File "/home/ubuntu/.conda/envs/tcrbert/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1194, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/ubuntu/.conda/envs/tcrbert/lib/python3.9/site-packages/esm/modules.py", line 276, in forward
    return self.weights.index_select(0, positions.view(-1)).view(bsz, seq_len, -1).detach()
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument index in method wrapper__index_select)

Thank you very much.
Best regards

Looks like a bug, I've opened a PR to address this #488


Bug with Shimmy

Lara refused to continue shimmying in one particular instance. This worked in the OG Tomb4. Its a toggle opacity two door.
https://youtu.be/R2TwwC6sgX8
Level file attached.
37_TombEngine.zip
Compiled level here:
https://github.com/MontyTRC89/TombEngine/files/10249672/Tower.zip

Compiled level here:
https://github.com/MontyTRC89/TombEngine/files/10249672/Tower.zip

Similar to my Monkey Swing Issue if I reduce the slop of triangulated part to 2 then Lara can continue shimmying as intended. This worked on OG Tomb 4 with a higher slope.


samd21_xpro

Hi,
I am running the latest versions of all software (win10 pro+Atom+platform+python2.7)
Everything work fine when using with arduino avr boards.
When i try to build for samd21 xpro board i have the this error:
platformio run --target upload
src\main.cpp:6:21: fatal error: Arduino.h: No such file or directory
#include "Arduino.h"
^
compilation terminated.
scons: *** [.pioenvs\samd21_xpro\src\main.o] Error 1
[ ERROR ] Took 1.26 seconds
Can someone help me here?
Thanks in advance,
Alex Soares

I don't see how this is an Atom issue, as Atom by itself does not support compiling.  This appears to be a platformio or other issue instead.


All steps to Aerospike interaction does not work properly

Hi,
As Stratio Manager does not support Aerospike yet. Vagrant sandbox doesn't contain Aerospike bundles either. I had to build deep-spark from sources.
bin/stratio-deep-shell does not see anything in com.stratio.*. So, I had to manually launch Spark via bin/spark-shell --jars $(echo lib/*.jar | tr ' ' ',').
Then First Steps with Stratio Deep and Aerospike does not work as there are no MessageTestEntity and WordCount in compiled jars. And I haven't managed to implement those is plain Scala to paste it in REPL. (Something about NoSuchMethod exception and <init>).
Then I composed custom SBT project, and put all jars in lib dir to unmanaged dependencies. Now it complains:
[error] (run-main-f) java.lang.NoSuchMethodError: scala.collection.immutable.HashSet$.empty()Lscala/collection/immutable/HashSet;
java.lang.NoSuchMethodError: scala.collection.immutable.HashSet$.empty()Lscala/collection/immutable/HashSet;
        at akka.actor.ActorCell$.<init>(ActorCell.scala:336)
        at akka.actor.ActorCell$.<clinit>(ActorCell.scala)
        at akka.actor.RootActorPath.$div(ActorPath.scala:159)
        at akka.actor.LocalActorRefProvider.<init>(ActorRefProvider.scala:464)
        at akka.remote.RemoteActorRefProvider.<init>(RemoteActorRefProvider.scala:124)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
  // ...

Where is the correct path in whole documentation and examples to launch deep-spark with Aerospike?

Hi Alexander,
Currently, the development of Stratio Deep is deprecated. However, Stratio Crossdata has inherited part of the features of Stratio Deep. Regarding to the use of Spark and Aerospike together, we recommend to combine:

Stratio Crossdata
Aerospark

I Hope it helps

Thanks for fast and honest response. I really suggest you to put this information at the top of README.
Do you think both components are production ready?
I suggest combining those two components is not only about configuration files manipulation -- coding is required as well?

Hi Alexander, thanks for the suggestion.
Regarding the maturity of these two components, we have performed some operations with Aerospark, but they were functional tests so I can't tell how stable is. In the other hand, Crossdata is based on Apache Spark and the stress tests performed have been successful.
Moreover, in order to use Aerospark with Crossdata, only some SQL-like commands are required to set up the environment. Take a look at the Aerospark configuration and examples. The only one change required to use Crossdata is replace the SQLContext by the XDContext.

OK, thank you. We would consider that option.


Scala 3 support

Hi,
Is there a plan to support Scala 3?
I've just checked https://docs.scala-lang.org/scala3/guides/migration/scala3-migrate.html dependency update and scapegoat plugin is blocking migration in my case:
[error]
[error] Incompatible Libraries:
[error] ("com.sksamuel.scapegoat" %% "scalac-scapegoat-plugin" % "2.1.6" % "scapegoat").cross(CrossVersion.full) (Full cross-version)

As far I'm aware the sbt plugin isn't the blocker here. It's the actual compiler plugin. You can track progress on this issue: https://github.com/scapegoat-scala/scapegoat/issues/521


Remove circular require

This fixes a circular require warning I encountered in Peddler when testing against the main branch of HTTP.rb.

Thank you!


Standard RDP security server redirection fix

Fix server redirection with standard security as observed in cases involving a 2012 R2 gateway and a load balanced environment. An optional padding field was considered mandatory, causing a false failure.

+1


NoneType implicit conversion

There is issue with NoneType<double, true> conversion. For exemple put a variable of this type un the log10 function. There is ambigous error. I suspect the double() long() long long() to be ambigous choices. Souldn't be a T() operator instead of all the others (and me be wrong) operaror? It seems to solve this issue but to create other ones where one of this operator is used for implicit conversion

Should be fixed by #939, can you confirm?


Flow error format issue

Currently, the flow maker gives out a relatively uninformative error message.

It only gives out the line number, column, and the first line of the error message. I believe this is because the argument '--one-line' was removed in #265. However, adding that argument isn't ideal either, since the message gets extremely long.

For comparison, running flow by itself on a command line gives

The plugin vim-flow solves this by actually having multiple lines for an error.

Is there any way that we can do this in neomake?

Right now, I am currently writing a utility which takes the flow --json output and formats it to a more neomake friendly message (but WIP)... so far it looks promising, hopefully I can integrate it as a custom maker for the beginning to see how it fits... As soon as I get this thing as I want it (in my daily practise), I will let you know!

vim-flow uses the following errorformat (in https://github.com/flowtype/vim-flow/blob/master/plugin/flow.vim#L36):

'%EFile "%f", line %l, characters %c-%.%#,%Z%m,'

As mentioned, I built a json output formatter, which turned out to be very useful.
I made it public and added directions on how to set everything up with neomake
https://github.com/ryyppy/flow-vim-quickfix

@ryyppy This can now probably be added relatively easily to neomake itself with the new json parse function. See this pull request for an example: https://github.com/neomake/neomake/pull/942

There have been some fixes since this was reported: 92d782b9, bd16a861, and d5582067.
So how much is this an issue still?
Apart from that it might be good to provide steps for actually reproducing this - IIRC you need a config etc.

As for errors on multiple lines, and other ideas see https://github.com/neomake/neomake/issues/832.


Add various notes and suggestions

Signed-off-by: Daniel Hardman<EMAIL_ADDRESS>This PR is not intended to be merged as-is.  We may end up making individual issues out of the various TODOs, accepting a few of the minor verbiage tweaks, and disregarding other items.

Overall, I think we might want to make a few changes to the PR to make it mergeable, but I am in favor of merging it as long as the TODOs are converted to issues.
I think we generally need to address all these concerns before we can have confidence that the spec will work for indy credentials over didcomm... which it needs to support in order to be usable IMO.

great additions!

This PR now has conflicts.... if issues have been captured, I suggest we close the PR, and attempt to address the issues 1 by 1.

@OR13 I will pick at this later like a vulture to see if there are any items uncaptured as issues, but would implore @dhh1128 to give a once over too if there's time

@wyc @dhh1128 we should close this unless there are any other issues which need to be raised.

I'm okay with closing this if @brentzundel feels there's a ticket for each concern that I raised that he believes in. He has my proxy.

I believe that all pertinent TODOs raised in this PR are covered by issues.
In addition to the TODOs, this PR recommends some changes to the spec language that could be valuable.
If given access, I'm happy to resolve the conflict in this PR, and clean up the TODOs so that this can be merged.

If given access

You can modify my PR, Brent. Just raise a PR against my PR. Ping me and I'll tell you how, if that's an unfamiliar git workflow.

Thanks to @brentzundel for resolving some issues and clutter. My PR is now clean and can be merged, if anybody wants to.

fixes #60

@OR13 all TODOs have been removed. @csuwildcat I believe this is ready to merge.

can this be merged?

@brentzundel I suggest we setup CODEOWNERs to make it clear who is responsible for merging PRs... in absence, ping the editors of the spec daily.

I think that's a good idea. I would like to be one of them, if possible.
On Tue, Jul 21, 2020 at 3:09 PM Orie Steele<EMAIL_ADDRESS>wrote:

@brentzundel https://github.com/brentzundel I suggest we setup
CODEOWNERs to make it clear who is responsible for merging PRs... in
absence, ping the editors of the spec daily.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/decentralized-identity/presentation-exchange/pull/18#issuecomment-662107693,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPFKP5MGLYMGDK6DAZ257TR4X7YBANCNFSM4NY6Q6IQ
.

@csuwildcat @OR13 @wyc
merge conflicts fixed, ready for review.

LGTM

please correct merge conflict, so this can be merged.

fixed conflicts, multiple positive reviews, merging.


Add Binary ops to TTNN

Is your feature request related to a problem? Please describe.
We need a new operation to perform binary functions on two input tensors similar to what was implemented in torch.
ex. logical_and , logaddexp , xlogy
Following are the ops needed
logical_and, logical_or, logical_xor, ldexp, xlogy, logaddexp, logaddexp2
Describe the solution you'd like
This will apply element-wise binary function on the two input tensors and return one output tensor
Describe alternatives you've considered
It's possible that ttnn tensors could be converted to a Pytorch tensors and then apply math operations with Pytorch function. The result would then be returned using ttnn.from_torch operation.
Additional context
The reference implementation of a binary function.
import torch

tensor1 = torch.tensor([4.0, 9.0, 7.0])
tensor2 = torch.tensor([1.0, 2.0, 3.0])

result_tensor = torch.logical_and(tensor1, tensor2)
print(result_tensor)

merged to main #5443


AscendEx perp connector

Description

Based on the last quarterly Poll, Binance, Kucoin, Gate.io and AscendEx are the Gold and Silver connectors for Epoch 4, which means that the Foundation maintains and improves them
We have created bounties to add perpetual futures support for all connectors except for AscendEx
This issue creates a bounty to add a perp connector to AscendEx
Developer should follow the latest standards for perp connectors in the Binance Futures connector

Bounty

Sponsor: Hummingbot Foundation
Bounty amount: 750,000 HBOT
Developer portion: 100%
Status: OPEN

@fengtality, CoinAlpha is interested in tackling this ticket

AscendEx informed us that their perpetual futures API is only open to whitelisted institutional users, so it doesn't make sense for the Foundation to fund a bounty for an open source connector.
We will cancel this bounty as CoinAlpha has not yet started work on it.


feat: add @keyvhq/compress

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 10 (80.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 86.902%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/compress/src/index.js
8
10
80.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
272

Relevant Lines:
290

💛  - Coveralls


Fix password reset bug

https://trello.com/c/82WTbqac/1077-reset-password-bug
Description
It seems this bug only shows up in prod/review apps and not locally so it is a little tricky to fully understand but to reproduce the sentry issue found on the trello card I visited /password/edit?reset_password_token=INCORRECTTOKENHERE. The outcome of which can be seen in the before screenshot.
To address this, I changed the order of the guard clauses in the user passwords controller edit action in order to ensue that we would not render signed_in_as_another_user if the token was invalid. This looks to have fixed the issue but I am completely sure why there should be differences between the local and prod environments in this case.
Before:

After:

Checklist:

[ ] Have you documented your changes in the pull request description?
[ ] Does the change present any security considerations?
[ ] Is any gem functionality overloaded? Eg: Devise controller methods being overloaded.
[ ] Has acceptance criteria been tested by a peer?
[ ] Has the CHANGELOG been updated? (If change is worth telling users about.)

General testing (author)

[ ] Test without JavaScript
[ ] Test on small screen

Accessibility testing (author)

[ ] Works keyboard only
[ ] Tested with one screen reader
[ ] Zoom page to 400% - content still visible
[ ] Disable CSS - does content make sense and appear in a logical order?

Codecov Report

Merging #1552 (12bf9c7) into master (138b09e) will decrease coverage by 60.88%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           master    #1552       +/-   ##
===========================================
- Coverage   86.87%   25.99%   -60.89%
===========================================
  Files         388      388
  Lines        8330    10346     +2016
  Branches     1210      661      -549
===========================================
- Hits         7237     2689     -4548
- Misses        900     7572     +6672
+ Partials      193       85      -108

Impacted Files
Coverage Δ

app/controllers/users/passwords_controller.rb
0.00% <0.00%> (-94.03%)
:arrow_down:

app/models/contact.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/accident.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/models/incident.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/forms/alert_form.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/forms/comment_form.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/jobs/send_alert_job.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/policies/team_policy.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/decorators/test_decorator.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

app/forms/reset_password_form.rb
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 276 more

Continue to review full report at Codecov.

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

@KyleMacPherson I think the core issue is the use of invalid reset tokens. Your change avoids but doesn't completely fix the underlying issue, which is that the wrong_user? method assumes user_with_reset_token is not nil.
I'm happy to reorder the guard clauses as they do make more sense this way, but I think we should add a guard to this method to check user_with_reset_token is a valid User.


Fix schedule access in API

The schedules API was incorrectly configured allowing anyone access to
the list of schedules.
@miq-bot add-label api, bug
@miq-bot assign @abellotti

Nice find  🎵    Thanks!!


fix(declarative) migration failed on nested route

when you put a route nested in service it fails to migrate on the fly.

spec/03-plugins/06-statsd/01-log_spec.lua:1216 seems to be a flaky test. I ran 6 times in my local env and it fails for 3 times.


Example does not adhere to "Allman" standard

Type of issue
Typo
Description
Style guidelines specify:

Use the "Allman" style for braces: open and closing brace its own new line. Braces line up with current indentation level.

But this example on the same page doesn't use braces.
foreach (char ch in laugh)
{
    if (ch == 'h')
        Console.Write("H");
    else
        Console.Write(ch);
}
Console.WriteLine();

Examples on the page should be consistent to avoid confusion, or guidelines should specify if the "Allman" style is optional for one-line statements.
Page URL
https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions
Content source URL
https://github.com/dotnet/docs/blob/main/docs/csharp/fundamentals/coding-style/coding-conventions.md
Document Version Independent Id
f940f2ad-e13d-4d37-6439-f8afcbc4e4c7
Article author
@BillWagner
Metadata

ID: 40f42506-f4a5-859a-0266-ded002056d83
Service: dotnet-csharp
Sub-service: fundamentals

This sample should be updated. The if and else clauses should be in Allman braces, as well as the outer foreach loop.


Improve find references query.

support class method definitions
take type hierarchy into account when looking for references
allow for limited search within a single file ("onlySourceFile" query parameter)
update tests

Corrected find type method for MethodDeclaration to work with findDef and doc properly (force pushed). Added scope parameter to callback function in findPropRefs, which is exported and is not equivalent to findRefs in that matter (I need that scope for my custom queries).
Let me know if you would wish this contribution to be split into several smaller ones.

Thanks! Looks good. Merged as a9ba18e049

Thanks!


This adds the initial code for egress (SNAT).

apiVersion: v1
kind: Service
metadata:
  name: sip-client
  labels:
    app: sip-client
  annotations:
    kube-vip.io/egress: "true"

is required as is   externalTrafficPolicy: Local, to ensure that the local ipTables/conntrack rules are written in the same location.

My testing yaml:
apiVersion: v1
kind: Service
metadata:
  name: sip-client
  labels:
    app: sip-client
  annotations:
    kube-vip.io/egress: "true"
spec:
  type: LoadBalancer
  # "Local" preserves the client source IP and avoids a second hop for
  # LoadBalancer and NodePort
  externalTrafficPolicy: Local
  ports:
  - name: sip
    port: 5060
    protocol: UDP
  selector:
    app: sip-client
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: sip-client
  labels:
    app: sip-client
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: sip-client
  template:
    metadata:
      labels:
        app: sip-client
    spec:
      containers:
      - name: sip-client
        image: ctaloi/sipp
        ports:
        - containerPort: 5060
          name: sip
        command: [ '/usr/local/bin/sipp', '-sn', 'uac', "<IP_ADDRESS>" ]
        #readinessGates:
        #- conditionType: kube-vip.io/egress-enabled


Popover throws errors and warnings on web

Description
Popover throws an error that back handler is not supported on web. Everyti´hings´works fine though...
CodeSandbox/Snack link
https://gluestack.io/ui/docs/components/overlay/popover
Steps to reproduce

Go to 'Popover docs'
Open. the console
Click on the example to open the popover
See error

gluestack-ui Version
1.0.35
Platform

[X] Expo
[ ] React Native CLI
[ ] Next
[X] Web
[ ] Android
[ ] iOS

Other Platform
No response
Additional Information
No response

@sem4phor Thanks for reporting this. We're working on it.

Hey @sem4phor , this issue will be fixed in this #1745 PR.


Scheduled FIRRTL output format

Separate issue for scheduled FIRRTL output format, mentioned in #22.

Closed with #40.


fix: Table of Contents doesn't work correctly with Markdown Section in demo site/new components

🐛 Bug Report
Table of Contents cannot scan the content of Markdown Sections when interacting with the application in the usual way, specifically:

When the FluentTableOfContents.QueryDom method is called by FluentTableOfContents.OnAfterRenderAsync, the contents of the Markdown Sections are not present, so the correct table of contents will not be obtained.
After changing the Location, the FluentTableOfContents.QueryDom method is called by FluentTableOfContents.LocationChanged, the same will happen.

The error occurs on pages like DesignTokens, CodeSetup, ...
It is possible to get a Table of Contents as expected of the above pages with the following steps:

Open/refresh the page DesignTokens, wait for the content of the Markdown Section to be present.
According to issue #413, Navigation Menu's selected is Home so we can navigate to DesignTokens to call FluentTableOfContents.QueryDom by FluentTableOfContents.LocationChanged, then we will get a correct table of contents.

Doing the above with the MarkdownSection page, we get a table of contents but it also contains the content of DemoSection.
🤔 Expected Behavior

Table of Contents can scan the content of Markdown Sections.
Exceptions can be set for the scanned contents of the table of contents.

😯 Current Behavior
Can't get a Table of Contents and How to get Table of Contents:
https://github.com/microsoft/fluentui-blazor/assets/72692627/6603f012-52e7-4a4e-b9f5-2cd5c601f0ed
Table of Contents scans the content of DemoSection:
https://github.com/microsoft/fluentui-blazor/assets/72692627/e7e27828-35f1-41ef-8a2c-815e224d9f0a
💁 Possible Solution

🔦 Context

🌍 Your Environment

OS & Device: Windows 10
Browser Microsoft Edge

It is possible to get a Table of Contents as expected of the above pages with the following steps:

Open/refresh the page DesignTokens, wait for the content of the Markdown Section to be present.
According to issue fix: The default selected of the Navigation Menu is incorrect in Demo Site #413, Navigation Menu's selected is Home so we can navigate to DesignTokens to call FluentTableOfContents.QueryDom by FluentTableOfContents.LocationChanged, then we will get a correct table of contents.

Doing the above with the MarkdownSection page, we get a table of contents but it also contains the content of DemoSection.

But this doesn't work anymore when #413 is fixed (which I've already done locally)

Sorry, that information is not necessary and misleading. I just want to say that I should fix #413 before this issue

I have that one fixed already in a local branch. Will be pushed soon.

One other thing; the FluentMarkdownSection will not be part of the next version. It will just be a helper component in the demo.
We decided to remove it from the set as we don't want to have external dependencies (in this case Markdig) in the library package

One more one other thing: The TableOfContents will also not be part of the next version. It too will be just an example component in the demo environment and not an out-of-the-box component.
Reasoning behind this on is actually found in this issue and fix. To make sure the ToC gets updated after new headings have been added to the DOM, we need to make a couple of steps to achieve this:

add an event to the DemoMainLayout
cascade that event down in the @Body
invoke this event from the MarkdownSection component
Reload the ToC component.

These are doable steps, but it is not something we can automate with installation or ServiceCollection or something like that. As there are too many manual steps involved, we do not want to include it in the box but supply code/example how someone can do this/use this in their own project.


drivers: sensor: Add sensor reporters to sensor info

Adds support for sensors to specify an array of other sensors they
depend upon in the devicetree and instantiate an array of references in
the sensor info data structure.
This will be used by virtual sensors that synthesize sensor channels
from one or more other sensors, such as a virtual lid angle sensor
synthesized from a lid accelerometer and a base accelerometer.
The size of the sensor reporters array in the sensor info data structure
is exactly the number of reporters specified in the devicetree for each
node, and can vary from node to node. This enables an efficient use of
data memory compared to an alternative implementation that defines a
constant array size for all nodes. Also note that the sensor reporters
array is constant and instantiated in ROM, without any RAM overhead.
Signed-off-by: Maureen Helm<EMAIL_ADDRESS>$ west build -b native_posix -p auto -t run samples/sensor/sensor_shell

uart:~$ sensor info
device name: bmi160@1, vendor: Bosch Sensortec GmbH, model: bmi160, friendly name: Base Accelerometer, num reporters: 0
device name: bmi160@2, vendor: Bosch Sensortec GmbH, model: bmi160, friendly name: Lid Accelerometer, num reporters: 0
device name: hinge-angle, vendor: (null), model: (null), friendly name: Hinge Angle, num reporters: 2
        reporter: 0, name: bmi160@2, interval: 10, sensitivity: 0
        reporter: 1, name: bmi160@1, interval: 5, sensitivity: 0
device name: motion-detect, vendor: (null), model: (null), friendly name: Motion Detect, num reporters: 1
        reporter: 0, name: bmi160@1, interval: 20, sensitivity: 0

cc: @huhebo

I really like that you are able to see the reporters to the virtual sensor in the shell with this, and that its pretty much optimal in terms of memory usage.


Swipe is not working on iOS

Issue report
Expected Behavior
When using iOS device and trying to swipe away the Toast, the Toast should respond.
Current Behavior
The Swipe feature only appears to be working in Chrome with the mobile simulator. When testing on an iOS emulator, the swipe feature is not recognized.
Possible Solution
None at this time.
Steps to Reproduce (for bugs)

Start ods-toast demo page
Open iOS emulator
Try to swipe away the Toast

Your Environment

Version used: latest dev build
Browser Name and version: current iOS emulator

:tada: This issue has been resolved in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Parameterize and consolidate FFT tests

When you have a chance, could you please take a look at this, @mrocklin? 😄 Should make this a little cleaner and more maintainable in the FFT test suite.

This looks great to me

I wouldn't worry too much about the previous test suite.  I would focus on
what makes the most sense for today.
On Thu, Mar 23, 2017 at 5:09 PM, jakirkham<EMAIL_ADDRESS>wrote:

@jakirkham commented on this pull request.
In dask/array/tests/test_fft.py
https://github.com/dask/dask/pull/2118#discussion_r107784831:

-def test_ihfft():

assert_eq(ihfft(darr), np.fft.ihfft(nparr))
assert_eq(ihfft(darr2, axis=0), np.fft.ihfft(nparr, axis=0))

assert_eq(da_fft(darr),

         np_fft(nparr))

I think part of the test is trying to not always provide all the args
though, right? Though I didn't write it. So I could be wrong.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/2118#discussion_r107784831, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszBHGtGk0pCD8NvEadnBaFGjI6NDbks5rot-ngaJpZM4MnNkL
.

In that case, I'd probably just pick one combination each arg/kwarg instead of having multiple and parameterizing over them. It's not clear to me that having so many axis values or n values is helpful. If it turns out these are helpful, they should really be in a different test function that is descriptive of what they offer instead. For example testing sizes that have particular relevance in comparison to the array size (i.e. larger than, smaller than, and equal to).

How expensive in terms of testing time is it just to blanket everything
like this?  This sort of test gives me a great deal of confidence that
things operate well.
On Thu, Mar 23, 2017 at 5:58 PM, jakirkham<EMAIL_ADDRESS>wrote:

In that case, I'd probably just pick one combination each arg/kwarg
instead of having multiple and parameterizing over them. It's not clear to
me that having so many axis values or n values is helpful. If it turns
out these are helpful, they should really be in a different test function
that is descriptive of what they offer instead. For example testing sizes
that have particular relevance in comparison to the array size (i.e. larger
than, smaller than, and equal to).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/2118#issuecomment-288873432, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszCdTW6c2Vg_mL1a4HGZEyXnm85nvks5rousPgaJpZM4MnNkL
.

Not sure what you are asking, @mrocklin, but the current test time for this module is ~0.5s. Once the N-D FFTs come in it is ~1s. Also what sort of test are you referring too?

Not sure what you are asking, @mrocklin, but the current test time for this module is ~0.5s. Once the N-D FFTs come in it is ~1s. Also what sort of test are you referring too?

Ah sorry, I should have included this message in the thread above that included this test.
function_names = ['fft', 'ifft', 'hfft', 'ihfft', ...]

@pytest.mark.parametrize('axis', [-1, 0])
@pytest.mark.parametrize('n', [0, 5, 13])
@pytest.mark.paramtrize('funcname', function_names)
def test_fft(funcname, axis, n):
    da_fft = getattr(da.fft, funcname)
    np_fft = getattr(np.fft, funcname)
    assert_eq(da_fft(darr, n=n, axis=axis),
              np_fft(nparr, n=n, axis=axis)

It occurs to me that this test covers all of the test cases except as you mention the possibilities of defaults.  I would personally prefer to have such a test than to have a bunch of small tests.  I agree that this can cause some parameter blowup, but if it's fast (and I think that 1s is fast enough) then I think it's better to just have a single comprehensive test like this than to have many small tests that are all individually named.

Generally I suspect that if we disagree on many fine-grained tests and a giant parameterized tests that that disagreement comes from a difference in attention span.  This module is called to my attention once every few months and I am expected to verify that everything works or see if something has gone wrong.  Poring over a detailed test suite with many fine tests takes a lot of time.  Seeing a large parametrized test that covers all possibilities is something that I can look at and understand how it works in a very short amount of time.  Concision in test suites is a virtue for long-term maintenance.
However concision also shouldn't get in the way of writing more tests.  There will always cases that aren't well covered by a comprehensive test, such as the default behavior case that you bring up (what if the user just doesn't provide any keywords?  are the defaults set the same).  But I think that we should add these only after we've established a comprehensive test, and only add tests that aren't well covered by that comprehensive test.
Anyway, that's just my perspective.  I'm not sure there is a well established way of going about this at the moment.

So it is less a question of whether this can or cannot be more compact for me (or whether that is a good thing). It is more a question of priorities and time. Personally I want to prioritize PR ( https://github.com/dask/dask/pull/2116 ) and there are always other things (e.g. changes by infrastructure providers at conda-forge).
Right now I feel like this is in a healthy place. We have cut 42 lines from this file (~27% reduction). Gone from 16 test functions down to 6 test functions (~62.5% reduction), all of which cover the same (and in some cases more) of the parameter space while having a negligible impact on the test run time. All of this to say we definitely made a marked improvement. While we can always find way to make it better, we shouldn't let perfect be the enemy of the good. If you agree, let's merge this and get to work on these other problems.

I agree that this is a great improvement.  Merging.

Thanks @mrocklin.


Unable to get stream video on iOS17.4

Video stream URL cannot be obtained on iOS17.4.
(error)
pattern (ytplayer\.config\s*=\s*) failed:

I tried it with the latest commit and succeeded.
Thank you for your support.