Dummy PR for HDDS-9206

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
What is the link to the Apache JIRA
(Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
Please replace this section with the link to the Apache JIRA)
How was this patch tested?
(Please explain how this patch was tested. Ex: unit tests, manual tests)
(If this patch involves UI changes, please attach a screen-shot; otherwise, remove this)

Do not review ci.yml and junit.sh files. Those are leftovers configs for running single test class multiple times. There are also some leftover comments. All of the leftovers will be addressed when creating real PR.


Leapdroid self uninstalling.

When I run installer of leapdroid. Its installing and then uninstalling itself.

I meet the same issue. Please fix it.

Could you please provide a bit more information?

This happened at the beginning of installation or in the middle?
Did you see any error messages prompt when this happened?
You system information: OS version, CPU model, GPU model, the version of Leapdroid?
Is your account the administrator on your system?

This happened after few seconds after click install.
There is no errors.
Windows 10
AMD FX-6300
Sapphire Radeon R9 270

Leapdroid - newest version.

Yes

Hi,
Thanks for your reply.
The auto uninstalling is a result of failure detected during installing. We were working on this piece recently. In our next release (which should be soon), we fixed a few things on this. Could you please have a try and let us know the result?

Write to me when You build new version. I will try that.

Hi,
Our new version <IP_ADDRESS> is out. You can get through our website www.leapdroid.com. Let us know the result. We already received some feedback this version helped. But based on your situation (if it is more like a COM error for example), this may not help. Let us know your result. Thanks!


wrong word in sequence_to_sequence_implementation.ipynb

in the section "Sequence to Sequence Model":
We can now stat defining the functions that will build the seq2seq model.
the word "stat" should be "start"

@jetta Thanks! fixed.


:sparkles: multithreading for QuickSim

Why are you using std::thread instead of std::execution_policy?

Actually, my first step was to use std::execution_policy since you mentioned this once. However, I was not able to make it work. As far as I can see, Apple Clang does not yet support parallel algorithms and execution policies.

I can't say for sure and your milage may vary, but I had some luck writing a thin abstraction layer on top of std::execution_policy that makes the general concept available error-free on all platforms we're continuously testing on. That is, if policies are supported, they are used, if not, not. This might still not be the solution you were hoping for and it might not even work on Apple Silicon chips. That requires further testing. If you want to try it at least, please check out the execution policy macros on the placer branch.

Sounds really interesting! Maybe we can keep this in mind. For now, I would suggest using the current implementation since the performance increases as expected and I have already tested/analyzed all the different benchmarks. What is your opinion?

I agree with you.

Could you please add a few tests for varying thread counts? After that, this PR is ready to be merged.


Improve description of the replicaset configuration

you know what, it's a docfix. if there's an issue, we can fix it later. merging!


DDO-2849 Record deployments to pact broker

 Summary

Implementing step 7 to pact nirvana which allows us to record deployments to pact.
Adds 2 data fields. PactParticipant in charts and ParticipatesInPact in environments.

One other comment is just a heads up that this PR doesn't expose the field through Sherlock's API at all. I'm assuming that's intentional and we'll do another change to expose it (but if not, happy to pair on that).


*: support return prev deleted kv

I still need to add a few tests. But I would like to see the feedbacks.
Now the prev value is got from API layer. It is not super efficient. We can do it in mvcc layer. But I feel it is good enough for now.
What do you think /cc @heyitsanthony @gyuho @hongchaodeng @mitake

@xiang90 the idea seems to be reasonable. How do you think about a case of write only permission? Current delete request just requires write permission. This change introduces read operation in the delete request. Maybe permission checking rule needs to be changed for the case of GetDeletedKVs == true?

approach looks OK

@mitake I think it would require read permission.

@heyitsanthony All fixed. PTAL.
@mitake Auth issue resolved. PTAL.

lgtm after fixing final nits

@xiang90 lgtm, thanks


[Migration] Add a fine grained permission for Function Library Management APIs

In 5.11 and older versions, Function Library Management REST APIs [1] and FunctionLibraryManagementAdminService [2] require manage permissions. But ideally, we need to use a fine grained permission for them.
With https://github.com/wso2/carbon-identity-framework#3891 we have added a fine grained permission for Function Library Management APIs.
It is required to mention this configuration change in the 5.12.0 migration docs. Now fined grained permission is enough to access the Function Library Management APIs.
[1] https://github.com/wso2/carbon-identity-framework/blob/master/features/identity-core/org.wso2.carbon.identity.core.server.feature/resources/identity.xml.j2#L2401-L2416
[2] https://github.com/wso2/carbon-identity-framework/blob/2bd15774e9365525cefeaa05428d97de8f7c9288/components/functions-library-mgt/org.wso2.carbon.identity.functions.library.mgt/src/main/resources/META-INF/services.xml#L30-L55

Fixed in https://github.com/wso2/docs-is/pull/2991, https://github.com/wso2/docs-is/pull/2997


[frontend] fix banner spacing

ADO-XXX
Description
List of proposed changes:

fix banner spacing by adding margin bottom

What to test for/How to test
Additional Notes

Looks like in fullscreen there's some padding/margin issues such that the image doesn't fill the container on the right:

This PR don't fix that, only the missing bottom margin. We can create a bug and fix it later.

ah.  In that case approved.


Can't communicate with Sick Tim781

Hello, I'm running Ubuntu 20.04, with ROS 1 Noetic. I'm trying to talk to a Sick TIM781 sensor with firmware v5.10. I was able to ping the device, and then use SOPAS to change the communication to binary. But I still get an error saying it can't communicate and is not getting the expected answer. Here is the full readout:
ROS_MASTER_URI=http://localhost:11311
process[sick_tim_7xx-1]: started with pid [322158]
[ INFO] [1721348868.706815175]: sick_generic_caller V. 3.4.0
[ INFO] [1721348868.707611033]: Program argument 1: /home/akash/hfa_ws/devel_isolated/sick_scan_xd/lib/sick_scan_xd/sick_generic_caller
[ INFO] [1721348868.707640634]: Program argument 2: __log:=/home/akash/.ros/log/07046054-445b-11ef-b03c-0b48c101c823/sick_tim_7xx-1.log
[ INFO] [1721348868.707650405]: Program argument 3: __name:=sick_tim_7xx
[ INFO] [1721348868.707660402]: ==========================================
[ INFO] [1721348868.711701691]: SickTransformPublisher: broadcasting TF messages parent_frame_id="map", child_frame_id="cloud", (x,y,z,roll,pitch,yaw)=(0.0,0.0,0.0,0.0,0.0,0.0), rate=10.0
[ INFO] [1721348868.712722688]: Range filter configuration: range_min=0, range_max=100, range_filter_handling=0
[ INFO] [1721348868.714008978]: Found sopas_protocol_type param overwriting default protocol:
[ INFO] [1721348868.714034421]: Binary protocol activated
[ INFO] [1721348868.714935894]: PointCloudMonitor started.
[ INFO] [1721348868.714955833]: Start initialising scanner [Ip: <IP_ADDRESS>] [Port:2112]
[ INFO] [1721348868.735987792]: Publishing on topic "/sick_tim_7xx/lferec", qos=10
[ INFO] [1721348868.736449774]: Publishing on topic "/sick_tim_7xx/lidoutputstate", qos=10
[ INFO] [1721348868.736812280]: Publishing on topic "/sick_tim_7xx/marker", qos=10
[ INFO] [1721348868.737306813]: SickCloudTransform: add_transform_xyz_rpy = (0,0,0,0,0,0)
[ INFO] [1721348868.737315825]: SickCloudTransform: azimuth_offset = 0 [deg]
[ INFO] [1721348868.737326245]: SickCloudTransform: additional 3x3 rotation matrix = { (1,0,0), (0,1,0), (0,0,1) }
[ INFO] [1721348868.737333851]: SickCloudTransform: apply 3x3 rotation = false
[ INFO] [1721348868.737340998]: SickCloudTransform: additional translation = (0,0,0)
[ INFO] [1721348868.737348848]: SickCloudTransform: check_dynamic_updates = false
[ INFO] [1721348868.737381086]: Publishing lidar pointcloud2 to cloud
[ INFO] [1721348868.737501973]: Publishing on topic "/cloud", qos=10
[ INFO] [1721348868.737862893]: Publishing on topic "/sick_tim_7xx/imu", qos=10
[ INFO] [1721348868.738160463]: Publishing on topic "/sick_tim_7xx/encoder", qos=10
[ INFO] [1721348868.738476130]: Publishing on topic "/scan", qos=10
[ INFO] [1721348868.738948083]: SickCloudTransform: add_transform_xyz_rpy = (0,0,0,0,0,0)
[ INFO] [1721348868.738956843]: SickCloudTransform: azimuth_offset = 0 [deg]
[ INFO] [1721348868.738967528]: SickCloudTransform: additional 3x3 rotation matrix = { (1,0,0), (0,1,0), (0,0,1) }
[ INFO] [1721348868.738975185]: SickCloudTransform: apply 3x3 rotation = false
[ INFO] [1721348868.738982568]: SickCloudTransform: additional translation = (0,0,0)
[ INFO] [1721348868.738991701]: SickCloudTransform: check_dynamic_updates = false
[ INFO] [1721348868.739022377]: sick_scan_xd: Tcp::open: connecting to <IP_ADDRESS>:2112 ...
[ INFO] [1721348868.739646951]: sick_scan_xd Tcp::open: connected to <IP_ADDRESS>:2112
[ INFO] [1721348868.739765460]: SickThread TcpRecvThread started.
[ INFO] [1721348868.740680908]: Parameter setting for <active_echo: 0>
[ INFO] [1721348868.742029990]: Sending  : <Len=0017>sRN SCdevicestate CRC:<0x30>
[ INFO] [1721348868.743799576]: Receiving: sRA SCdevicestate \x01
[ INFO] [1721348868.743848127]: checkColaDialect: lidar response in configured Cola-dialect Cola-B
[ INFO] [1721348868.944213132]: Sending  : <Len=0023>sMN SetAccessMode 0x03 0xf4 0x72 0x47 0x44 CRC:<0xb3>
[ INFO] [1721348868.946663775]: Receiving: sAN SetAccessMode \x00
[ INFO] [1721348869.147025367]: Sending  : <Len=0015>sWN EIHstCola 0x01 CRC:<0x09>
[ INFO] [1721348869.148836878]: Receiving: sFA\x00\x0a
[ WARN] [1721348869.148933552]: Error Sopas answer mismatch: Error unexpected Sopas answer for request <Len=0015>sWN EIHstCola 0x01 CRC:<0x09>, received answer: "sFA\x00\x0a", expected patterns: "sWA EIHstCola","sAN EIHstCola"
[ WARN] [1721348874.149309369]: Timeout during waiting for new datagram
[ WARN] [1721348874.149446382]: Error Sopas answer mismatch: Error unexpected Sopas answer for request <Len=0015>sWN EIHstCola 0x01 CRC:<0x09>, received answer: "", expected patterns: "sWA EIHstCola","sAN EIHstCola"
[ERROR] [1721348874.149554899]: Error unexpected Sopas answer for request <Len=0015>sWN EIHstCola 0x01 CRC:<0x09>, giving up after 1 unexpected answers.
[ INFO] [1721348874.149617679]: Failed to init scanner Error Code: 1
Waiting for timeout...
If the communication mode set in the scanner memory is different from that used by the driver, the scanner's communication mode is changed.
This requires a restart of the TCP-IP connection, which can extend the start time by up to 30 seconds. There are two ways to prevent this:

[Recommended] Set the communication mode with the SOPAS ET software to binary and save this setting in the scanner's EEPROM.
Use the parameter "use_binary_protocol" to overwrite the default settings of the driver.
[ERROR] [1721348874.149687649]: ## ERROR in mainGenericLaser: init failed, retrying...
[ INFO] [1721348874.149724095]: Start initialising scanner [Ip: <IP_ADDRESS>] [Port:2112]
[ WARN] [1721348874.149760133]: Disconnecting TCP-Connection.
[ERROR] [1721348874.150024228]: Tcp::readInputData: Read 0 bytes, connection is lost!
[ INFO] [1721348874.150129095]: SickThread TcpRecvThread finished (flags: threadShouldRun=0, endThread=0).
SickScanCommon closed.

Let me know if I can gather any more useful info.

Thanks for your feedback and logfile. The driver establishes a TCP connection to the lidar and starts the initialisation using typical SOPAS commands. The SOPAS Command "sMN SetAccessMode 0x03 0xf4 0x72 0x47 0x44" should be answered by "sAN SetAccessMode 1", but is instaead acknowledged by "sAN SetAccessMode 0". As a consequence, the following  SOPAS command "sWN EIHstCola 1" for binary cola communication fails with error code 0x0A (Sopas_Error_VARIABLE_WRITE_ACCESSDENIED).
Most probably the password for the "authorized client" has been changed (default hash value is f4724744). Please change the password for "authorized client" back to the default, or reset your device to factory defaults and try again.
Tim781 logfiles with latest sick_scan_xd releases 3.4.0 and 3.5.0 and TiM781 firmware version V5.0 are attached for information.

Hello, thank you so much for your help. We have changed the passwords for our company for safety reasons. Do you know how to access the hash value for the password?

@akashjinandra A direct calculation of the hash values is currently not available. We are clarifying further possibilities together with SICK.

Hello I was able to find away to get the calculated hash value from within the SOPAS ET software. You must be logged in as service level and you can calculate the the hash. However it seems like it did not seem to use the new value. I double checked that when I put the default password for level "authorized client" is "client". I was able to recreate the correct hash that is default in the launch file, however when I put the newly generated hash it doesn't seem to work.

Thanks for new informations! Which version of SOPAS ET do you use? Can you post a screenshot? This topic may also be of interest to other users.
We will soon publish an update to support configurable hashvalues.

@akashjinandra Please use the update in branch https://github.com/SICKAG/sick_scan_xd/tree/feature/issue_update_2407xx to configure hash values for the client authorization in the launchfile.


Bug: insert dom before page loaded made form submit be stopped.

when i run such code with jquery and angular:
 $input = $('<input type="text">');
 $div.prepend($input);

the input's closest form (not ng-form and there is no controller outside) will be automatic add an eventListener by angular:
var t = function(c) {
    a.$apply(function() {
         m.$commitViewValue();
         m.$setSubmitted()
     });
    c.preventDefault()
  } ;
d[0].addEventListener("submit", t, !1);

so I can't use form submit anymore.
if I change my code into this, it will be ok:
 $input = $('<input type="text">');
 $(function(){
    $div.prepend($input);
 });

Hi, thanks for the report. Can you please put a demo of the problem in a https://plnkr.co or similar? That makes it much easier to assess the problem.

I'm going to close this issue because we haven't got any feedback. Feel free to reopen this issue if you can provide new feedback.


DRAFT - SWE l1a algorithm

Change Summary
Overview
This code is still in work. I wanted to open it in case anyone is working on similar task like mine and like to take a look at what I am doing.
New Files
l1a_swe.py contains all of l1a algorithm.
Updated Files

pyproject.toml

It includes libraries that I needed locally to test but could be take away before final PR

swe_packet_definition.xml

updated SWE packet definition to match their latest submission

Testing
None

I am closing this draft PR because this code is going to change a lot after my discussion with SWE team this afternoon.


Make "Open project from URL" block press green flag once loaded

This is hyper-specific and if it is too specific please just close, however
I created this system where we you have one packaged scratch project that can load in other scratch projects. I did this when I was figuring out how websites work on github and it was the first way I figured it out (and retrospectively the most difficult way I could probably do it.)
Essentially, you have a sprite with a script who's soul goal is to load another SB3 based on whatever parameter you give it.

This has the benefit of

Taking ~2.2 MB less space of storage/"Web Page"
Allowing me to easily display my source code
Easier than packaging the project and renaming it index and creating a new folder for every (sub page?)
Not having to put a turbowarp loading screen in between "Web pages," as customizing is entirely outside of my programming knowledge other than changing the background picture essentially
The main issue is that once the new SB3 is loaded, it doesn't start. I know that there are a few blocks that can actually run without pressing the flag, so I create this

I save it as a sprite file put it in any projects that need to automatically start once loaded. It works, but it has a few issues.
Cannot stop the project, so the editor always highlights the flag as if it's running and it seriously messes with my OCD
Is mildly annoying to do, but slightly better than packaging each project individually
To stop it from automatically running while editing I have to pause rather than stop
I have to reset it every time the green flag is clicked manually
I know this is likely impossible; the block is completely missing by the time the next project loads, but it feels like an intuitive behavior. I already have a solution for it, but I figured I might as well make my case for changing it.

If you were wondering why I would bother having a separate SB3 for every page and not just having a single massive project, I'd like to one day host a collection of everything I make and being able to have separate links for everything as well as one main website that links to all of them just seems nice, even if no one ever really will see it.

@snowboyz0825 Actually, (I think) it should be perfectly possible. I'll have a look at it.

@snowboyz0825 Use ShovelUtils import project from URL [] block. It automatically clicks the green flag when the project has loaded. Lily's Asset Manager doesn't do that.

Seems like something you guys can implement and put up a PR


Allow building without poetry

Story
As a package maintainer,
I want to build rpmautospec without poetry,
so that I don’t have to install it and all its dependencies.
Acceptance Criteria

[x] rpmautospec ships with setup.py #134
[x] The RPM spec file allows conditionally building using setuptools instead of poetry

Building packages for F39, 40, Rawhide, EPEL9 from here: https://src.fedoraproject.org/rpms/python-rpmautospec/c/b69a39d380fc17ff3c8a068f8933fb3298cebbfe


feat: add math/base/special/asecf

Resolves #2118 .
Description

What is the purpose of this pull request?

This pull request:

adds math/base/special/asecf, which is the single-precision equivalent of math/base/special/asec.

Related Issues

Does this pull request have any related issues?

This pull request:

fixes #2118

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

Test coverage report:

I've used the term inverse (arc) secant in the descriptions, following math/base/special/asec.

I haven't included (in radians) in the output descriptions, following math/base/special/asec.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@gunjjoshi Yes, go for it! Thanks!

@gunjjoshi Did the test fixtures remain the same? I am guessing yes since you did not add them in the commit.

@kgryte Yes, they did remain the same. To re-check, I even deleted all the fixtures, re-generated them, still they didn't had any changes with the previous ones, and so they didn't come up in the push.

@gunjjoshi Thanks for the following up. In which case, I think this PR is good to go.


feat: add admin_key to node_create.proto, node_update.proto and node.proto

Description:

Related issue(s):
Fixes #379
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

The package move is not correct. We will not be using the incorrect and improper proto package going forward. A future change will move everything to proper packages, but that will also have a HIP associated because it will rewrite substantially every pre-existing file.
The rest are mostly recommendations and typos.

Updated


use Pydantic models to define table schemas and allow instances as input data

Background
We can integrate with pydantic at very low cost and get several nice gains. In all our decorators and methods where we accept TTableSchemaColumns or Sequence[TColumnSchema] we can also accept BaseModel from pydantic.
Our json encoder should be also able to serialize pydantic models instances into json
Tasks

[ ] those features are only enabled when pydantic dependency is installed

[ ] allow for pydantic models everywhere we accept TTableSchemaColumns or Sequence[TColumnSchema] (typically the argument name is columns). be smart with typing! don't replace it with Any -> allow for an union

[ ] in json common module detect pydantic models and serialize them to dictionaries with dict(m)

[ ] place util functions in common/libs - look at parquet. I expect at least pydantic -> TTableSchemaColumns converter

Tests

[ ] add pydantic to dev dependencies

[ ] test json serialization

[ ] test all the methods that allow pydantic models. (surely dlt.resource, apply_hints, pipeline.extract

[ ] at least one end to end test for pydantic -> duckdb

[ ] try nested pydantic model and model with many possible (all relevant) data types

for more context see #338

@rudolfix , can you assign this to me.

@muppinesh you have it! this is way more work compared to #490 but not very complicated. also a lot of fun because Pydantic is very popular and converting schema and accepting objects is big thing for us
make sure you you have poetry installed and you can do make dev and make test-common before you start.
I'm rudolfix on our slack. ping me there if you want to continue

@muppinesh are you still on it?

I was enhancing my GitHub skills in the meantime, so issue was on hold. I will resume my work on  it and update you. Apologies for the delay.

Hi , I won't be able to contribute on this issue . You can reassign to yourself or open it for others.


[Bug]: transactions format

Contact Details
<EMAIL_ADDRESS>Section Number
Figure 1:XX.1-1 and Table 1:XX.1-1 and 1:XX.1.2
What is wrong
in figure 1:XX.1-1 the transactions numbers are missing the []
in section 1:XX.1.2 and Table 1:XX.1-1 all the transactions are missing the transaction numeber (e.g. [ITI-YY1])
Describe the solution you'd like
No response
Relevant log output
No response
Priority
{"Low"=>"Typo or other minor classification that an editor can manage. Requires no group discussion."}
Code of Conduct

[X] I agree to follow the IHE Code of Conduct

check through the document the missing [] also in the use cases


Leptos 0.7 support

It seems new version 0.7.0 breaks functionality

Hi,
thanks for raising this.
The crate doesn't work with Leptos 0.7 and I have no plans to further develop the project or upgrade it to the latest framework releases. The techniques used here aren't going to work in 0.7 anyway.
I intend to completely rewrite this library instead for a more friendly and customizable API.
It may take a few weeks though before I have a 0.7-ready replacement.


Time/Test mode

One of our stretch goals, a timed mode where the player must complete a round (or rounds?) in a certain amount of time. The time will be displayed at the end. Addition: high score field?

I have submitted an pull request(#11) with the first version of Timed Mode. I added mode selection and a timing feature to the code. No high score tracking, yet.


fix(doc): Fixed plot code-snippets references after black formatting

Codecov Report
Patch and project coverage have no change.

Comparison is base (1bbcdf2) 85.06% compared to head (af51cec) 85.06%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #445   +/-   ##
=======================================
  Coverage   85.06%   85.06%
=======================================
  Files         198      198
  Lines       25699    25699
=======================================
  Hits        21862    21862
  Misses       3837     3837

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


Traceback will be generated when processing an onnx model.

This model is modified based on the DiffIR open source model.
command:
onnxslim input.onnx output.onnx --input_shapes input:1,3,-1,-1

I will get the following result as shown in the picture:

Environment:

OnnxSlim Version: 0.1.22
Onnx Version: 1.14.1
OnnxRuntime Version: 1.17.1
Python Version: Python 3.10.9
OS: Windows 10 22H2

duplicate of https://github.com/tsingmicro-toolchain/OnnxSlim/issues/9, I will release a new version soon

Solved👍🏻, works now in new version 0.1.23, Thanks


Support parameter overrides in bicep serialization

This is blocked on upgrading autorest.csharp to consume latest System.ClientModel due to the updated version of Azure.ResourceManager.
It is also blocked on shipping a new version of Azure.ResourceManager with BicepModelReaderWriterOptions.

Closing in favor of https://github.com/Azure/autorest.csharp/pull/4217


4.13, kubevirt: Block metadata server egress

What this PR does / why we need it:
Cherry-pick:

https://github.com/openshift/hypershift/pull/2399

Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/test e2e-kubevirt-aws-ovn

/cc @davidvossel @orenc1

/hold
Checking kubevirt lane manually

manual kubevirt lane test
--- FAIL: TestCreateCluster (1108.30s)
    --- PASS: TestCreateCluster/EnsureNodeCountMatchesNodePoolReplicas (1.06s)
    --- PASS: TestCreateCluster/EnsureNoCrashingPods (0.56s)
    --- PASS: TestCreateCluster/EnsureNodeCommunication (0.94s)
    --- SKIP: TestCreateCluster/EnsureAllRoutesUseHCPRouter (0.00s)
    --- PASS: TestCreateCluster/NoticePreemptionOrFailedScheduling (0.58s)
    --- PASS: TestCreateCluster/EnsureNoPodsWithTooHighPriority (0.23s)
    --- PASS: TestCreateCluster/EnsureHCPContainersHaveResourceRequests (0.20s)
    --- PASS: TestCreateCluster/EnsureAllContainersHavePullPolicyIfNotPresent (0.20s)
    --- PASS: TestCreateCluster/PreTeardownClusterDump (0.00s)
    --- PASS: TestCreateCluster/DestroyCluster_1 (140.19s)
    --- FAIL: TestCreateCluster/EnsureAPIBudget (2.17s)
        --- FAIL: TestCreateCluster/EnsureAPIBudget/control-plane-operator_read (0.70s)
        --- FAIL: TestCreateCluster/EnsureAPIBudget/control-plane-operator_mutate (0.18s)
        --- PASS: TestCreateCluster/EnsureAPIBudget/control-plane-operator_no_404_deletes (0.18s)
        --- PASS: TestCreateCluster/EnsureAPIBudget/hypershift-operator_read (0.18s)
        --- PASS: TestCreateCluster/EnsureAPIBudget/hypershift-operator_mutate (0.18s)
        --- PASS: TestCreateCluster/EnsureAPIBudget/hypershift-operator_no_404_deletes (0.18s)
    --- PASS: TestCreateCluster/DeleteTestNamespace (0.36s)

fixes: https://issues.redhat.com/browse/OCPBUGS-11737

requires https://github.com/openshift/release/pull/38459

/test e2e-kubevirt-aws-ovn

/jira cherry-pick

/test e2e-aws

/jira cherry-pick OCPBUGS-11737

/lgtm
/hold cancel


amsgrad is not defined in AdamW class

Please include amsgrad in init or remove from defaults dict :)

Also, use_variance doesn't look like being used??

Nice catch, fixed : -)


Automate the workflow to release on launchpad

Release Version 0.7.9 was the first one automatically released on launchpad after the github release was done.
With b1a3a0c27561e6a0651b64aa9c5f5ee579088e41 all needed changes are on main branch, so further releases will do the same.
This issue can be closes


Pytorch Autograd no_grad equivalent in Keras

Hi, I am not sure if this is a bug/ feature, more of a general issue. I recently came to know of a feature in pytorch Autograd where we can pass no_grad as described here. I read somewhere that pytorch calculates gradients even during inference and ends up consuming more than 1GB GPU RAM due to it. This feature allows users to stop this and save space (I don't use pytorch so not 100pc sure). I am looking around Keras to find if Keras does this too? And is there anything we can do to stop this? (Yet to find something). Any pointers would be appreciated.
Thanks!

You can use tf.stop_gradients: https://www.tensorflow.org/api_docs/python/tf/stop_gradient

Note that Keras does not compute gradients when using predict (or just calling the model via __call__) so it doesn't have this specific issue.


Update README.md to make Persisted Attributes example more clear

I was reading through the README and noticed that the example for Persisted Attributes confused me a bit.
In create_ride_and_audit_record you do a simple Ride.create! and in create_stripe_charge you reference @ride.user, so I felt it should assign that user somewhere. Since the @user and @params instance variables are also in the example I think it makes sense to use them and have a more complete example.
What do you think?
One alternative I considered was Ride.create!(user: user, **@params) but I think it's less pretty.

I'm sorry, for some reason my GitHub notifications did not alert me to this PR, so I am seeing this late. Apologies. I think this is a great suggestion, thank you!


How to get Diff for structs with error field?

For this pretty simple example:
type Cmp struct {
  Err error
}

a := Cmp{
  Err: errors.New("got an error"),
}

b := Cmp{
  Err: errors.New("got a wrong error"),
}

diff := cmp.Diff(a, b)

I've got a panic:
panic: cannot handle unexported field: {Cmp}.Err.(*errors.errorString).s
consider using a custom Comparer; if you control the implementation of type, you can also consider AllowUnexported or cmpopts.IgnoreUnexported

Seems there is no way to use AllowUnexported to make cmp.Diff() possible.
Is there any solution?

You can provide a custom Comparer option that defines how you want to compare errors values.
For example, one possibility (using Go 1.13's errors.Is) might be:
if diff := cmp.Diff(a, b, cmp.Comparer(func(x, y error) bool {
  // Two errors are equal if either Is the other.
  //
  // We need to perform the test in both directions because cmp requires
  // comparer functions to be symmetric, but errors.Is is not.
  return errors.Is(x, y) || errors.Is(y, x)
})); diff != "" {
  // something changed
}

You might also use x == y for a strict equality check, (x == nil) == (y == nil) to compare only nil-ness, or some other test.

To be sure I understand you correctly. In my example, the field is an error interface.
Does it mean inside the Comparer function I need to access those fields manually?
E.g. x.Err and y.Err? Does it also mean I need to handle a comparison of all remaining fields inside the Comparer?

Here's a working example:
https://play.golang.org/p/qTJqbwV9wf0
The comparison function is called with when comparing values of the appropriate type (error in this case).

@neild thanks a lot.


kompose down with openshift doesn't delete  BuildConfig

I tried running kompose down with the buildconfig example here: https://github.com/kubernetes-incubator/kompose/tree/master/examples/buildconfig
It doesn't delete the buildconfig.
$ kompose --provider=openshift -f docker-compose.yml down
WARN[0000] [foo] Service cannot be created because of missing port.
INFO[0000] Buildconfig using https://github.com/skippbox/kompose2.git::master as source.
INFO[0001] Successfully deleted DeploymentConfig: foo
INFO[0001] Successfully deleted ImageStream: foo
$ oc get bc
NAME      TYPE      FROM         LATEST
foo       Docker    Git@master   1

@ashetty1 buildconfig support was not present when kompose down for openshift got merged. Thanks for reporting the issue.
@kadel I'm working on it.

Correct me if I am wrong, but it appears in my testing that this issue hasn't been fixed yet:
Before running kompose down:
NAME          READY     STATUS      RESTARTS   AGE
foo-1-build   0/1       Completed   0          1m
foo-1-lv0q5   1/1       Running     0          29s
Running kompose down:
INFO Buildconfig using https://github.com/kubernetes-incubator/kompose.git::HEAD as source.
INFO Successfully deleted Service: foo
INFO Successfully deleted DeploymentConfig: foo
INFO Successfully deleted ImageStream: foo
INFO Successfully deleted BuildConfig: foo
Looks like the build pod doesn't get deleted: Output of oc get pods:
NAME          READY     STATUS      RESTARTS   AGE
foo-1-build   0/1       Completed   0          2m

@ashetty1 I think this https://github.com/kubernetes-incubator/kompose/pull/483 will solve the problem!

meanwhile keeping this open since this problem is not completelt solved!


Prometheus operator with external prometheus server

I am trying to configure prometheus operator with external prometheus server, but i could’t found solution to this task. What do i need to do to accomplish this task ?

I am trying to configure prometheus operator with external prometheus server, but i could’t found solution to this task. What do i need to do to accomplished this task ?

The Prometheus Operator builds on top of Kubernetes and uses Kubernetes primitives to accomplish its task. Running Prometheus outside of Kubernetes is out of scope for the Prometheus Operator.

@navi86 I am closing here. Please let us know if you have further questions.


Settle parallel branches before re-planning

The agent runtime now runs parallel branches with Promise.allSettled instead of Promise.all. After the execution is finished, if any of the branches returns a failure, the plan execution is interrupted and re-planning proceeds. This prevents moving on too soon when a failure is encountered and causing unnecessary re-plans. This also moves logging earlier in the plan execution to get feedback as soon as an action is executed successfully or it fails.
Change-type: patch

I self-certify!


cmd/go: errors emitted multiple times for packages with missing checksums

$ go mod edit -go=1.17

$ go list all
m.go:3:8: missing go.sum entry for module providing package golang.org/x/tools/go/packages (imported by example.com); to add:
        go get example.com

$ go mod edit -go=1.16

$ go list all
go<EMAIL_ADDRESS>missing go.sum entry; to add it:
        go mod download golang.org/x/tools
go<EMAIL_ADDRESS>missing go.sum entry; to add it:
        go mod download golang.org/x/tools

$ go1.16.4 list all
go<EMAIL_ADDRESS>missing go.sum entry; to add it:
        go mod download golang.org/x/tools

-- go.mod --
module example.com

go 1.17

require golang.org/x/tools v0.1.1
-- m.go --
package example

import _ "golang.org/x/tools/go/packages"

This is a regression introduced in Go 1.17, probably by one of my changes for #36460.
CC @jayconrod @matloob

(Found while writing a regression test for #46141.)

(Unmarking as release-blocker. Realistically, nobody is going to be confused by a duplicated message, and if this were the last bug remaining in the release we wouldn't want to hold it up.)

@bcmills This is in the 1.18 milestone; time to move to 1.19?  Thanks.

@bcmills @matloob This issue is marked for 1.19.  It's just been rolling forward in milestones.  Should it move to Backlog?

I'm unable to reproduce this FWIW:
$ go version
go version go1.19
$ cat go.mod
module github.com/example/example

go 1.17

require golang.org/x/tools v0.1.12 // indirect
deklerk at legate in ~/workspace/mult_errors
$ cat go.sum
deklerk at legate in ~/workspace/mult_errors
$ go list -m all
go<EMAIL_ADDRESS>missing go.sum entry; to add it:
	go mod download golang.org/x/tools
deklerk at legate in ~/workspace/mult_errors
$ go mod edit -go=1.16
deklerk at legate in ~/workspace/mult_errors
$ go list -m all
go<EMAIL_ADDRESS>missing go.sum entry; to add it:
	go mod download golang.org/x/tools

@jadekler, try go list all without setting -m?

Aha, yes, that does it. I somehow thought all was not a valid command line argument anymore. That doesn't make sense from a backwards compatibility perspective. Thanks. =)
I'll poke around and see if I can find a solution.


Locate pangyp via module API

Might fix https://github.com/sass/node-sass/issues/1061

Seems legit. I'll confirm it doesn't break npm@2 and ship

It should also fix cases when pangyp is reachable globally with npm@2

According to the docs this should work as expected :+1:


Restarting Ethermint after crash panics

When Ethermint using Optimint crashed on Mamaki (see https://github.com/celestiaorg/optimint/issues/419) an attempt to restart it with ethermintd start results in another panic
panic: SetIndex requires index to not be set

goroutine 1 [running]:
github.com/cosmos/cosmos-sdk/x/capability/keeper.Keeper.InitializeIndex({{_, _}, {_, _}, {_, _}, _, _, _}, {{0x2b214c8, ...}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.45.1/x/capability/keeper/keeper.go:155 +0x1ea
github.com/cosmos/cosmos-sdk/x/capability.InitGenesis({{0x2b214c8, 0xc0000dc000}, {0x2b347e0, 0xc002cbec00}, {{0x0, 0x0}, {0xc002b448c0, 0xb}, 0x0, {0x1aa014ca, ...}, ...}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.45.1/x/capability/genesis.go:12 +0xf8
github.com/cosmos/cosmos-sdk/x/capability.AppModule.InitGenesis({{{0x2b36538, 0xc0000b1fb0}}, {{0x2b31a98, 0xc0000b1fb0}, {0x2b0abf8, 0xc0019a4550}, {0x2b0ac20, 0xc0019a45f0}, 0xc001c1e870, 0xc001c1e8a0, ...}}, ...)
	github.com/cosmos/cosmos-sdk@v0.45.1/x/capability/module.go:130 +0x17c
github.com/cosmos/cosmos-sdk/types/module.(*Manager).InitGenesis(_, {{0x2b214c8, 0xc0000dc000}, {0x2b347e0, 0xc002cbec00}, {{0x0, 0x0}, {0xc002b448c0, 0xb}, 0x0, ...}, ...}, ...)
	github.com/cosmos/cosmos-sdk@v0.45.1/types/module/module.go:320 +0x29d
github.com/tharsis/ethermint/app.(*EthermintApp).InitChainer(_, {{0x2b214c8, 0xc0000dc000}, {0x2b347e0, 0xc002cbec00}, {{0x0, 0x0}, {0xc002b448c0, 0xb}, 0x0, ...}, ...}, ...)
	github.com/tharsis/ethermint/app/app.go:620 +0x20e
github.com/cosmos/cosmos-sdk/baseapp.(*BaseApp).InitChain(0xc0012c7380, {{0x1aa014ca, 0xeda26fef2, 0x0}, {0xc002b448c0, 0xb}, 0xc00058cba0, {0x3ffbef8, 0x0, 0x0}, ...})
	github.com/cosmos/cosmos-sdk@v0.45.1/baseapp/abci.go:62 +0x455
github.com/tendermint/tendermint/abci/client.(*localClient).InitChainSync(0xc002b72180, {{0x1aa014ca, 0xeda26fef2, 0x0}, {0xc002b448c0, 0xb}, 0xc00058cba0, {0x3ffbef8, 0x0, 0x0}, ...})
	github.com/tendermint/tendermint@v0.34.14/abci/client/local_client.go:272 +0x118
github.com/tendermint/tendermint/proxy.(*appConnConsensus).InitChainSync(0x0?, {{0x1aa014ca, 0xeda26fef2, 0x0}, {0xc002b448c0, 0xb}, 0xc00058cba0, {0x3ffbef8, 0x0, 0x0}, ...})
	github.com/tendermint/tendermint@v0.34.14/proxy/app_conn.go:77 +0x55
github.com/celestiaorg/optimint/state.(*BlockExecutor).InitChain(0xc0012ec310, 0xc000021080)
	github.com/celestiaorg/optimint@v0.3.0/state/executor.go:59 +0x31f
github.com/celestiaorg/optimint/block.NewManager({0x2b248b8?, 0xc002b50a08}, {0x6fc23ac00, 0x6fc23ac00, 0x0, {0x0, 0x1, 0x2, 0x3, 0x4, ...}}, ...)
	github.com/celestiaorg/optimint@v0.3.0/block/manager.go:111 +0x385
github.com/celestiaorg/optimint/node.NewNode({_, _}, {{0xc000054270, 0x16}, {0xc001163e58, 0x4}, {{0xc002b43340, 0x16}, {0x0, 0x0}}, ...}, ...)
	github.com/celestiaorg/optimint@v0.3.0/node/node.go:129 +0xce5
github.com/tharsis/ethermint/server.startInProcess(_, {{0x0, 0x0, 0x0}, {0x2b3e778, 0xc000029620}, {0xc001163b60, 0xb}, {0x2b27490, 0xc0000b1fb0}, ...}, ...)
	github.com/tharsis/ethermint/server/start.go:330 +0xcd0
github.com/tharsis/ethermint/server.StartCmd.func2(0xc000e05180?, {0x3ffbef8?, 0x0?, 0x0?})
	github.com/tharsis/ethermint/server/start.go:122 +0x228
github.com/spf13/cobra.(*Command).execute(0xc000e05180, {0x3ffbef8, 0x0, 0x0})
	github.com/spf13/cobra@v1.4.0/command.go:856 +0x67c
github.com/spf13/cobra.(*Command).ExecuteC(0xc000d8b180)
	github.com/spf13/cobra@v1.4.0/command.go:974 +0x3b4
github.com/spf13/cobra.(*Command).Execute(...)
	github.com/spf13/cobra@v1.4.0/command.go:902
github.com/spf13/cobra.(*Command).ExecuteContext(...)
	github.com/spf13/cobra@v1.4.0/command.go:895
github.com/cosmos/cosmos-sdk/server/cmd.Execute(0x0?, {0xc000054270, 0x16})
	github.com/cosmos/cosmos-sdk@v0.45.1/server/cmd/execute.go:36 +0x1eb
main.main()
	github.com/tharsis/ethermint/cmd/ethermintd/main.go:20 +0x38

Reproduced also with ignite-cli-based app.

There's an issue with state deserialization from KV store. This should be tested by https://github.com/celestiaorg/optimint/blob/147a71c75b40596e4d9e829b22689bc1764d091a/store/store_test.go#L125-L145. But apparently it's too simple case (only one field is used).
Interesting question is: why json.Marshal -> blob -> json.Unmarshal fails.

The issue is NextValidators.Validators.PubKey. It is an interface (crypto.PubKey). It can be easily serialized (as string) but cannot be deserialized (as actual interface implementation is unknown).

#424 reproduces the issue. Easiest working solution would be to use encoding/gob (tested, it works).
But I'm leaning to serialize with protobuf, and at the same time adopt cosmos-sdk approach to script copying proto files from tendermint. This solution would also resolve https://github.com/celestiaorg/optimint/issues/37.


Issue with pool retry logic leads to client hanging in some scenarios.

In cases when server restarts or connection resets the retry logic in pool might lead to a situation where the client hangs for a long time.  Current retry logic gets a new connection when there is any connection error, and  then it puts the new connection back in the queue. Then it call pool.get() to get a connection in this case all connections are bad except the one in the end of the queue. Hence the logic need to cycle through all invalid connection wrappers to get a good connection wrapper. Given the exponential back off logic in retry you can see that if pool size is larger than 15 and max retries is also around that figure the client will hang for a long time until it gets a good connection.

Hi @jalandip, I am no longer actively maintaining this repository.  I have added you as a collaborator on the repo so that you can make any bugfixes you think are needed.  Let me know if you have any questions!

@thobbs Once the new connection is created using it for the current operation instead of checking it back would fix this issue. What do you think?

#243


what's the latest-version

I saw the website which told me that's 1.0,but I noticed the time is '2 years ago' and this project has modified 4 months ago
I use gradle to import this project.
and I find out EmojiconsFragment dont has method "newInstance" but this library does.
I thought there is another version?
or I can only use this library as the latest?

okay, just this website needs to update.
I saw the release and find out the version is 1.2


fix: sanitize field default value when required

Description
DefaultValue was not being checked properly.

[x] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] Existing test suite passes locally with my changes

Closing in favor of #550


feat: add base64url variant to decode and encode

Adding a base64url variant to the bloblang decoder/encoder.
I have a need to be able to decode a JWT token, which is formatted this way.

Thanks @ollystephens, looks great!


Allow selection of network (--net=...) when building the image

In some rare circumstances it is required to bind the intermediate containers to the host network due to restrictions on network interfaces. For example when using ShrewSoft VPN client the tap0 interface does not route packets from other hosts for security reasons which basically makes Docker unusable in those kinds of corporate environments.
Allowing the container to use host network (--net=host) solves that problem.

duplicate of https://github.com/docker/docker/issues/10324


Wallet state management when signing Votes, error when passing other than 8 lanes

When signing real votes with the signVotes() call (https://github.com/input-output-hk/catalyst-core/blob/340401bb5b1e5bdcf7b01a86cdecf11729ff15bd/src/chain-wallet-libs/bindings/wallet-js/js/index.js#L64), shouldn't the spending counter(s) be in sync with the state of the wallet on the network, and hence somehow passed to the wallet? Currently, they seem to be hardcoded to 1 in the logic constructing the wallet
Also, I see that the wallet tries to set up 8 lanes, each one with its own spending counter, and if I try to set up just one "lane", I get an invalid spending counters provided to the set account state function error. Is this behavior expected? Why are multiple lanes needed at all? Isn't the "basic" use case to have just one lane to sign the votes sequentially?

Correct,  each vote contains its pre-calculated spending counter.  This library should not be managing the spending counter, just using the value it is provided by the dapp/wallet.
There is a Lane field missing from the vote,  I am adding that to the CIP-62 draft for the vote record, and I will discuss this issue with @Mr-Leshiy ASAP.

This should have been resolved, closing,


MARP-77: add adobe-esign-connector

Hi @ivy-sgi , @andreasbalsiger ,
We are preparing to publish the Adobe E-Sign connector to Marketplace. Please review the product name, description, tags, and other metadata to ensure they accurately convey the connector's value proposition and capabilities.
Thank you!

Hi @andreasbalsiger , @ivy-sgi ,
Please help me review the product name, description, tags, and other metadata to ensure they accurately convey the connector's value proposition and capabilities.
Thank you!


CUT Martinotti cell

Replace:  somatostatin with correct identifier
No soma location property recorded.  Has layer locations but these are not reasoned over to determine that this is a neocortical cell.

Now fixed.


OAuth2: add retry policy to the OAuth2 filter

Commit Message: Add retry policy to the OAuth2 filter to avoid failing to call the Authorization server.
Additional Description:
Some EG users reported that Authorization servers may timeout TCP connections in the pool but only send an RST when Envoy reuses a connection to send a request to the Authorization server again. This behavior causes the authentication flow to fail. Implementing retries can mitigate this issue.
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] Fixes: https://github.com/envoyproxy/envoy/issues/33572
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]
Related EG issue: https://github.com/envoyproxy/gateway/issues/3178

Hi @envoyproxy/api-shepherds, I have added a retry_policy at the top level of the OAuth2 API for the following reasons:

It doesn't require deprecating the existing token_endpoin and adding a new one with retry_policy in it.
It's future-proof, allowing us to reuse the same retry_policy for accessing other IdP endpoints, e.g, the logout endpoint.

If we agree on the API change, I'll go ahead to add the implementation.

This requirement looks good to me and the jwt_authn filter, gcp_authn filter, RemoteDataSource, etc. have provided similar API.
But I think my question would be should we add the retry_policy in the HttpUri directly? Then we needn't change the API again and again in the future.
cc @htuch @mattklein123

But I think my question would be should we add the retry_policy in the HttpUri directly? Then we needn't change the API again and again in the future.

Good point! The only issue is that if we add retry_policy directly to HTTPUri, it implies all the APIs referencing HTTPUri are expected to support retries. While tit would great to have this feature, the existing implementations may not support it.

We can comment the current situation clearly and do the retry support for other positions in future PR on required

I don't think retry policy is a property of a URI but of a service. So you could potentially add it to the recently added envoy.config.core.v3.HttpService. But in this case I don't feel that strongly.

I don't think retry policy is a property of a URI but of a service. So you could potentially add it to the recently added envoy.config.core.v3.HttpService. But in this case I don't feel that strongly.

I raised this suggestion because the have add timeout in the HttpUri. I agree HttpService is better position but it is come too late and no much scenario are use it.

I agree on the history. Going forward, can we deprecate the existing URI field and replace with Service,  adding this there?

If we could convert everything to use a Service (applies both to HttpService and GrpcService), this would've been great. However, w/o proper API deprecation mechanism this is probably not worth the effort.
At least the code can be refactored to be similar.

@wbpcode @htuch @adisuissa thank you for your thoughtful inputs, I appreciate it. I believe the question of whether the retry policy should be incorporated into HTTPService/GRPCService and the deprecation of HttpUri in existing APIs is a broader topic. Perhaps we could track this in a separate issue if needed?
Regarding this PR, could I proceed with the current standalone retry policy approach?

 Even a API is marked as deprecated, Envoy need to support them forever.
So, it 's hard to replace the HttpUri with HttpService. But as @adisuissa said, at least we can make the code be general.
Any way, this is a bigger topic and it's hard to get a final conclusion in short term.
Specific to this PR, I recommend that let's along the 'tranditional' way first to unblock the following works.

I'm fine with retry policy. where it is in this PR as long as we don't put it in HttpUri.

/lgtm api

/wait
Needs tests and main merge


Unable to hook into certain process, code 15

I am able to hook into pretty much every process except the one i want to hook. RemoteHooking.Inject throws:
Unhandled Exception: System.ApplicationException: STATUS_INTERNAL_ERROR: Unknown error in injected C++ completion routine. (Code: 15)

Server stack trace:
   at EasyHook.NativeAPI.Force(Int32 InErrorCode)
   at EasyHook.RemoteHooking.InjectEx(Int32 InHostPID, Int32 InTargetPID, Int32 InWakeUpTID, Int32 InNativeOptions, String InLibraryPath_x86, String InLibraryPath_x64, Boolean InCanBypassWOW64, Boolean InCanCreateService, Boolean InRequireStrongName, Object[] InPassThruArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at EasyHook.HelperServiceInterface.InjectEx(Int32 InHostPID, Int32 InTargetPID, Int32 InWakeUpTID, Int32 InNativeOptions, String InLibraryPath_x86, String InLibraryPath_x64, Boolean InCanBypassWOW64, Boolean InCanCreateService, Boolean InRequireStrongName, Object[] InPassThruArgs)
   at EasyHook.RemoteHooking.InjectEx(Int32 InHostPID, Int32 InTargetPID, Int32 InWakeUpTID, Int32 InNativeOptions, String InLibraryPath_x86, String InLibraryPath_x64, Boolean InCanBypassWOW64, Boolean InCanCreateService, Boolean InRequireStrongName, Object[] InPassThruArgs)
   at EasyHook.RemoteHooking.Inject(Int32 InTargetPID, InjectionOptions InOptions, String InLibraryPath_x86, String InLibraryPath_x64, Object[] InPassThruArgs)

The target process is 64 bit, just like to injecting program (targeting 64 bit). Any ideas?
Edit: I'm using the binaries from the latest release as of today. Using windows 10 x64. Started everything with admin priv.
Edit2: The target process might be protected by themida zZz

@whosdatdev does this same issue occur if you run as administrator?

You might need SeDebugPrivilege for injecting in you process?
Verify with whoami /priv if it is enabled, enable it if its not and try again.


How to set themeColor with .NET AdaptiveCards SDK

Discussed in https://github.com/microsoft/AdaptiveCards/discussions/6382

Originally posted by soulflyman September 21, 2021
When sending the following json to a MS Teams Webhook I can change the color bar above the message with the themeColor Option:
{
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "type": "MessageCard",
    "themeColor": "ff0000",
    "version": "1.2",
    "title": "Alarm!",
    "text": "Test Message"
}

How is this possible with the .NET AdaptiveCards SDK that ist available via nuget?

Hi @soulflyman - this is a feature specific to Teams and is not an AC feature. Moving over to their repo so they can help provide better guidance

This issue has been copied over to Microsoft Teams repo here: https://github.com/MicrosoftDocs/msteams-docs/issues/4854


Snapshot tracker improvement and new tracker added

This PR split Snapshot class in multiple methods so you can create your custom tracker more easily inheriting from Snapshot class.
The PR also contains a new tracker derived from the Snapshot class to snapshot OLD on Update and Delete, this tracker also allows the user to exclude field names and auto_now fields in the generated sql to compare the rows as mentioned in #83 and #78
Let me know what you think about these new features, feedback always welcome

@quevon24 can you say what's going on with the tests?

@mlissner I've been following the guidelines for contributing, but I was having trouble with a few things
When i try to run the full test suite i get a lots of errors, for some reason tox keeps reusing the database and throwing errors like "django.db.utils.ProgrammingError: relation "tests_afterupdateordeletesnapshotmodel" already exists" or "psycopg2.errors.DuplicateTable: relation "tests_afterupdateordeletesnapshotmodel" already exists" (circleci tests are correct, but causing problems locally) Because of this i can't run my tests locally and then commit them to this PR
Also, the hot reload doesn't seems to work correctly. I did some tests to generate the required migrations, i removed some migration files, and the coverage report throws errors like "No source for code: '/code/pghistory/tests/migrations/0005_auto_20230321_2306.py'" because files are not being reloaded.
I'm trying to figure out the things i mentioned above to finish writing some tests for the new Snapshot class

When i try to run the full test suite i get a lots of errors, for some reason tox keeps reusing the database and throwing errors like "django.db.utils.ProgrammingError: relation "tests_afterupdateordeletesnapshotmodel" already exists" or "psycopg2.errors.DuplicateTable: relation "tests_afterupdateordeletesnapshotmodel" already exists" (circleci tests are correct, but causing problems locally) Because of this i can't run my tests locally and then commit them to this PR

For the error with the db i realized that there is a host volume pointing to /var/lib/postgresql/data, i just deleted the host volume and regenerated it again, and the errors are gone

Also, the hot reload doesn't seems to work correctly. I did some tests to generate the required migrations, i removed some migration files, and the coverage report throws errors like "No source for code: '/code/pghistory/tests/migrations/0005_auto_20230321_2306.py'" because files are not being reloaded.

The problem wasn't with the hot reload, to solve this i deleted the .coverage file that is generated when you run tox
By the way, the library seems to not support WSL, it gets stuck trying to resolve dependencies.

I added tests for possible params variations for the custom snapshot class

Can you remove the stuff that does custom field ignoring so we can add it in a future PR instead?

@mlissner changes are ready

LGTM!

@quevon24 @mlissner , I commented on https://github.com/Opus10/django-pghistory/issues/83 since it's relevant to this comment.
I believe the additions to the Snapshot class here were motivated by #83, right? If my understanding is correct, your issue can already be solved without modifying Snapshot. I.e. by supplying a Condition object to the condition argument. If this is the case, I would prefer to keep the Snapshot class the same and keep these classes simple
For this tracker, it's going to diverge from the other utility trackers like AfterInsertOrUpdate. The other utility trackers are meant to be barebones - no automatic conditions, etc. If this change goes in the library ideally it would behave like every other barebones utility tracker:
class BeforeUpdateOrDelete(PreconfiguredDatabaseTracker):
    """
    A database tracker that snapshots the old row during an update or delete
    """

    operation = pgtrigger.Update | pgtrigger.Delete
    snapshot = "OLD"

(note I named it "Before..." instead of "After...". django-pghistory has a somewhat confusing way of naming these trackers. They're named after the row they're snapshotting, not when the trigger fires).
Once this barebones tracker is in, you also want to put conditions on it so it behaves more like the default Snapshot tracker, right? I.e. ignore snapshotting when fields don't change or when excluded fields don't change).
If that's the case, I'd say let's get this barebones tracker in and I can follow up with a PR that makes it easier to add these conditions. Perhaps in the next major version release I can refactor how all of these utility classes work and just have everything be based off of Snapshot

Let's discuss a bit more and I'll try to get in the changes next release

Thanks for the detailed and thoughtful reply, Wes.

Once this barebones tracker is in, you also want to put conditions on it so it behaves more like the default Snapshot tracker, right? I.e. ignore snapshotting when fields don't change or when excluded fields don't change).

Yes, exactly.

If that's the case, I'd say let's get this barebones tracker in

We'll revise this PR to simplify it down to the barebones tracker, sure.

and I can follow up with a PR that makes it easier to add these conditions

That'd be fantastic, thank you! I think that'd nail all of our needs, yes!

@mlissner @wesleykendall I removed everything from the custom snapshot, i only left the before update or delete backbone trigger
I was thinking of a possible way to let the user have more control for the conditions, maybe one option would be to have some preconfigured conditions that could be used in any of the barebone trackers or also allow the user to create their custom preconfigured conditions using a class that can do the same as Snapshot class when it generates the condition to compare OLD and NEW rows.
Something like:
@pghistory.track(BeforeUpdateOrDelete(condition=pghistory.compare_rows), exclude=["date_modified"])
pghistory.compare_rows will be a preconfigured condition(maybe a class that can be reused and have access to event model) and will have the job to generate the pgtrigger Condition using the model fields(the ones tracked)
And from there the user will have the possibility to build their custom conditions without having to repeat the condition on every pghistory decorator (currentry if you need something complex in the condition, you need to manually write each condition to pass it to the barebone tracker)

Hey @quevon24 @mlissner
I have a change ready to add to this PR in addition to what you have. I wanted to first run it by you first. The change is more in-line with your original PR and makes some edits to the base class to make it less cumbersome.
Preface - I thought about your suggestion a lot, and it's going to be difficult to support that style at the moment because of how things are designed. The condition parameter is just being passed directly to a trigger from django-pgtrigger, and this object has no idea what the model even is until the time the trigger is installed. There would have to be some trickery somewhere to support what you suggested, and it might be easier to support something like this in a totally different interface in the next major version release.
I completely agree that there should be an easier way for people to make custom trackers for their models though, along with not needing to repeat yourself everywhere in a decorator. Here's what I came up with for now. Let me know what you think.
Approach
I made some changes that were more in-line with your original PR that edited the base class:

I added a utility to the base DatabaseTracker object to more easily add/create the snapshot triggers.
I made a standalone Changed condition object. This allows you to easily create a condition that will fire when configured fields change. By default, it fires when any field changes.

With these changes, the Snapshot setup method now looks like this:
def setup(self, event_model):
    self.add_event_trigger(
        event_model=event_model,
        label=self.label,
        name=f"{self.label}_insert",
        snapshot="NEW",
        when=pgtrigger.After,
        operation=pgtrigger.Insert,
    )

    self.add_event_trigger(
        event_model=event_model,
        label=self.label,
        name=f"{self.label}_update",
        snapshot="NEW",
        when=pgtrigger.After,
        operation=pgtrigger.Update,
        condition=Changed(event_model),
    )

I.e. the Insert trigger doesn't have a condition, and the Update trigger uses the Changed utility condition. It fires on any changed field by default.
With this in mind, I believe it should be easier for you to make your own base class to do what you want. Here's an example of a tracker that snapshots OLD rows on update/delete:
class CustomSnapshot(pghistory.Snapshot):
    def setup(self, event_model):
        self.add_event_trigger(
            event_model=event_model,
            label=self.label,
            name=f"{self.label}_update",
            snapshot="OLD",
            when=pgtrigger.After,
            operation=pgtrigger.Update,
            condition=Changed(event_model),
        )

        self.add_event_trigger(
            event_model=event_model,
            label=self.label,
            name=f"{self.label}_delete",
            snapshot="OLD",
            when=pgtrigger.After,
            operation=pgtrigger.Delete,
        )

Let's take this a bit further and only save snapshots when important fields change (i.e. no auto fields).
class IgnoreAutoFieldsSnapshot(pghistory.Snapshot):
    def setup(self, event_model):
        # Warning - this is pseudocode
        fields_to_watch = [f.name for f in event_model.pgh_tracked_model._meta.fields if not is_auto_field(f)]

        self.add_event_trigger(
            event_model=event_model,
            label=self.label,
            name=f"{self.label}_update",
            snapshot="OLD",
            when=pgtrigger.After,
            operation=pgtrigger.Update,
            # The condition here ensures we only make a snapshot when an important field changes
            condition=Changed(event_model, fields=fields_to_watch),
        )

        self.add_event_trigger(
            event_model=event_model,
            label=self.label,
            name=f"{self.label}_delete",
            snapshot="OLD",
            when=pgtrigger.After,
            operation=pgtrigger.Delete,
        )

With this, you now set up your trackers like:
@pghistory.track(IgnoreAutoFieldsSnapshot())
class MyModel(models.Model):
   ...

I.e., you'll be snapshotting all fields, but you'll only be storing updates when the important fields change. Again, not the prettiest interface ever, but it should be much better than before.
Follow up
Does this support your use case? I already have the code ready and can add it in this PR alongside the other utility you added.
If it does, I'll quickly add a test case for a custom tracker like this to double check my logic here. I'll follow up in another PR with an example in the docs. Perhaps we can think of another way to address this in the next major version release. The current interface makes it somewhat cumbersome

This looks great to me. It doesn't even seem all that cumbersome. Sure, it'd be nice to do something like:
class CustomSnapshotter(UpdateSnaptshotter, DeleteSnapshotter):
    ignored_fields = ["date_modified"]

That'd be nice, sure, a dream even, but your solution above is absolutely fine and we'd be perfectly happy with it — unless @quevon24 sees something I don't?

@wesleykendall Your solution looks great, i think it suits our needs, it also greatly reduced code required to add the event triggers and maybe we could use Changed class or method as a guide in case we need to generate a different condition.
I'm looking forward to seeing those changes in the PR, thanks for the effort you make for this library.

thanks for letting me know!
 The change will be part of 2.7.0. Will let you know when it's deployed

@quevon24 I added the change! I updated the test suite to include that custom tracker as an example. I added you as the commit author for both commits since this change was so similar to your initial PR. Will let you know when it's released

released in v2.7

Woo hoo! Thanks Wes! We'll take a look ASAP.


Failed connect from visual code to Azure Ubuntu VM, any method to run applications on the Azure Linux VMs?

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az network bastion ssh
Errors:
The command failed with an unexpected error. Here is the traceback:
The extension ssh is not installed.
Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 658, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 721, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 692, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 328, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/network/custom.py", line 8097, in ssh_bastion_host
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/network/custom.py", line 8030, in _test_extension
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/extension/__init__.py", line 340, in get_extension
azure.cli.core.extension.ExtensionNotInstalledException: The extension ssh is not installed.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az network bastion ssh --name {} --resource-group {} --target-resource-id {} --auth-type {} --username {}

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.33.1

Additional Context

route to CXP team

@billxu2007 Thanks for reaching out to us. Could you please run the below command to install the ssh extension ?
az extension add --name ssh
Then you can run this command and check if that works. Please let me know if you face any issues. Awaiting you reply.

Hi,
Thank you very much for your help!

Can I put the password in the parameters too for this command?
az network bastion ssh --name MyBastionHost --resource-group
MyResourceGroup --target-resource-id vmResourceId --auth-type password
--username xyz

after the SSH authentication, in powershell terminal, I can manual enter
the mount share file command, but in script,
If I want to run the linux command to mount a shortage share file inside an
Azure cli command,
should I use the
az vm run-command invoke -g MyResourceGroup -n MyVm --command-id
RunShellScript --scripts "sudo apt-get update && sudo apt-get install -y
nginx"

or any video or example for this?
My main purpose is connecting to each Linux Servers, downloading the
installation file, then installing it as root in the Linux server.
Thanks,
Bill Xu
On Wed, Mar 2, 2022 at 12:38 AM navba-MSFT @.***> wrote:

@billxu2007 https://github.com/billxu2007 Thanks for reaching out to
us. Could you please run the below command to install the ssh extension
?
az extension add --name ssh
Then you can run this
https://docs.microsoft.com/en-us/cli/azure/network/bastion?view=azure-cli-latest#az-network-bastion-ssh
command and check if that works. Please let me know if you face any issues.
Awaiting you reply.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/21466#issuecomment-1056279086,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEGD2MVEVHCDPWBRY37DSL3U535EDANCNFSM5PSEAXMA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi
After the bastion SSH connection command, then it will open the terminal of
the VM.
But I need to run a script file to connect, mount share storage, download
the file, then install the app.
Any suggestions to run the whole process as a CLI script?
Thanks,
Bill Xu
PS D:\Work\TC3oE> az network bastion ssh  `

--name $myBastionHost `
--resource-group $resourceGroupName `
--target-resource-id $targetId `
--auth-type password `
--username xubi

Command group 'network bastion' is in preview and under development.
Reference and support levels: https://aka.ms/CLI_refstatus
@.***'s password:
Welcome to Ubuntu 20.04.3 LTS (GNU/Linux 5.13.0-1014-azure x86_64)

Documentation:  https://help.ubuntu.com
Management:     https://landscape.canonical.com
Support:        https://ubuntu.com/advantage

System information as of Wed Mar  2 13:40:08 UTC 2022
System load:  0.02               Processes:             241
Usage of /:   12.9% of 28.90GB   Users logged in:       0
Memory usage: 1%                 IPv4 address for eth0: <IP_ADDRESS>
Swap usage:   0%

Super-optimized for small spaces - read how we shrank the memory
footprint of MicroK8s to make it the smallest full K8s around.
https://ubuntu.com/blog/microk8s-memory-optimisation

16 updates can be applied immediately.
To see these additional updates run: apt list --upgradable
*** System restart required ***
Last login: Mon Feb 28 19:03:47 2022 from <IP_ADDRESS>
To run a command as administrator (user "root"), use "sudo ".
See "man sudo_root" for details.
@.:~$ ls
@.:~$ whoami
xubi
@.***:~$ ls /home/xubi
On Wed, Mar 2, 2022 at 12:38 AM navba-MSFT @.***> wrote:

@billxu2007 https://github.com/billxu2007 Thanks for reaching out to
us. Could you please run the below command to install the ssh extension
?
az extension add --name ssh
Then you can run this
https://docs.microsoft.com/en-us/cli/azure/network/bastion?view=azure-cli-latest#az-network-bastion-ssh
command and check if that works. Please let me know if you face any issues.
Awaiting you reply.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/21466#issuecomment-1056279086,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEGD2MVEVHCDPWBRY37DSL3U535EDANCNFSM5PSEAXMA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@billxu2007 Thanks for getting back. I am providing a few suggestions here, inline with your questions:
1. Can I put the password in the parameters too for this command?

Here is the sample command:
az network bastion ssh --name MyBastionHost --resource-group MyResourceGroup --target-resource-id vmResourceId --auth-type password --username xyz

2. After the SSH authentication, in powershell terminal, I can manual enter the mount share file command, but in script,
If I want to run the linux command to mount a shortage share file inside an Azure cli command, should I use the
az vm run-command invoke -g MyResourceGroup -n MyVm --command-id RunShellScript --scripts "sudo apt-get update && sudo apt-get install -y nginx" or any video or example for this?

Run-Command has a few restrictions which are explained here. The bash script to perform manual on-demand share mount is here. The bash script to automatically mount the file share is here. Also If you wish to download the file from Azure File Storage without mounting the share on linux, you can refer this article.

3. Any suggestions to run the whole process as a CLI script?

I couldn't find the custom script in github which serves all the above requirement. So you need to tweak the above commands accordingly to achieve this ask.

Hope this helps.

@billxu2007 I wanted to do quick follow-up to check if you have any follow-up questions on this. Awaiting your reply.

Thank you very much for your email, my client changed his plan, use another
way to do it since this way is a manual operation.
Thanks again
Bill Xu
On Mon, Mar 7, 2022 at 2:02 AM navba-MSFT @.***> wrote:

@billxu2007 https://github.com/billxu2007 I wanted to do quick
follow-up to check if you have any follow-up questions on this. Awaiting
your reply.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/21466#issuecomment-1060253361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEGD2MTG3VGYDF5OCHVDW6LU6WSZPANCNFSM5PSEAXMA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

@billxu2007 Thanks for getting back. We will now proceed with closure of this github issue. If you need any further assistance on this issue in future, please feel free to reopen this thread. We would be happy to help.

Great, thanks!
Thank you very much for your help again!
Cheers,
Bill Xu
On Mon, Mar 7, 2022 at 8:42 AM navba-MSFT @.***> wrote:

@billxu2007 https://github.com/billxu2007 Thanks for getting back. We
will now proceed with closure of this github issue. If you need any further
assistance on this issue in future, please feel free to reopen this thread.
We would be happy to help.
—
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/21466#issuecomment-1060701265,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEGD2MSMARVANNHKX2OXJSDU6YBVTANCNFSM5PSEAXMA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


[PLAT-627] Improve Opt out in notification emails + Update OSF name

Purpose
It's a Gates' suggestion that we add a link on emails to unsubscribe from node specific notifications as well as user specific notifications. While we're at it let's update the image we use too.
Changes

Changes base notification template to send node link.
Add new image

QA Notes
This won't necessarily effect all notification emails, only ones that pertain to specific nodes.
Side Effects
None that I know of.
Ticket
https://openscience.atlassian.net/browse/PLAT-627

Only one small comment -- looks like we're no longer using cos-white2.png so that can be removed from static images. An update with develop should also fix travis issues!

@erinspace should be g2g now.


#18: revamp Hex

This pull request is a minimal re-implementation of Hex as per my suggestion in #18.
The only breaking API change is that .bytes is no longer a field, but a method that returns a slice.  However, it didn't break anything except the tests, so I don't think changing it will be a problem.

Codecov Report

Merging #27 (a404d42) into master (f7a2038) will increase coverage by 0.27%.
The diff coverage is 73.52%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
+ Coverage   63.06%   63.34%   +0.27%
==========================================
  Files          16       16
  Lines        1565     1596      +31
==========================================
+ Hits          987     1011      +24
- Misses        578      585       +7

Impacted Files
Coverage Δ

src/lib.rs
38.54% <ø> (+0.99%)
:arrow_up:

src/hex.rs
89.80% <73.52%> (-0.67%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Another change to be mindful of before merging is that I've moved Hex struct declaration to hex.rs, as per proposed in #28 .

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 4min)


Use prototype-less object for parentInjections

When targeting a function which name is one if the Object.prototype properties (like toString), it will fail due to the if (!parentInjections[funcName]) { check getting skipped

Good catch! Thanks for the contribution


Dependencies Connector & Knowledge Agents Kits

This is a placeholder for the topics appearing in the dependency session between the Connector & Agents Kits for release 24.03
Dismissal of the agent-connector helm charts https://github.com/eclipse-tractusx/knowledge-agents-edc/tree/main/charts in favor to separate agent-plane helm chart (see

https://github.com/eclipse-tractusx/knowledge-agents-edc/issues/61)
Registering an additional plane when its pod has started
    Either setup code in the extension OR
    additional wget/curl commands on the pod
ct test (TRG5) needs a VAULT, a MIW, a keycloak ... will there be some support by tractusx-connector charts?
    MXD mit Terraform

Migration of the v2 Management APIs to the v3 Management APIs
There seems to have been a switch of "connectorId" and "providerId" between TX EDC Control-Plane 0.5.0 and 0.5.1?
What about the "StatusChecker" for particular asset types. This currently leads to non-FINISHED transfer processes in 0.5.1
    do we need to extend the control plane to provide additional checkers OR
    will this be configurable (like a property per address type)
    will there be a default checker (NoopChecker or something)
Should we switch to EDR cache instead of callback (the first will not work with control-plane-memory)
Should we prefer a Data-Plane Proxy / Gateway approach versus Data-Plane Http Transfer
    asynchronous API
    decoupling of baseUrl and backend system

Future of auth-jwt (guess its redundant in the meantime) , synch with approach of @ndr-brt

its a double of the discussion https://github.com/eclipse-tractusx/sig-release/discussions/202


add metrics for individual OVN components

Type of change

[ ] Refactor
[x] New feature
[ ] Bug fix
[ ] Optimization
[ ] Documentation Update

Description
Adding metrics of ovn components (nbdb, sbdb, northd) this helps us narrow down which component has the higher usage than expected
General layout  (no metrics shown intentionally)

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

@smanda99 @rsevilla87 Reviews please 🙏🏾


feat: Add build CUDA version to detect_GPU test scripts

Add build info on CUDA, cuDNN, and NCCL
* Add information on ML library build to detect_GPU test scripts
   - Add build info on CUDA, cuDNN, and NCCL if available

Example
$ printf "\nPyTorch\n" && python torch_detect_GPU.py && printf "\nJAX\n" && python jax_detect_GPU.py && printf "\nTensorFlow\n" && python tf_detect_GPU.py

PyTorch
Number of GPUs found on system: 1
PyTorch has active GPU: True
PyTorch build CUDA version: 10.2
PyTorch build cuDNN version: 7605
PyTorch build NCCL version: 2708

Active GPU index: 0
Active GPU name: GeForce GTX 1650 with Max-Q Design

JAX
Number of GPUs found on system: 1
XLA backend type: gpu

Active GPU index: 0
Active GPU name: GeForce GTX 1650 with Max-Q Design

TensorFlow
2021-01-07 01:01:01.521490: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2021-01-07 01:01:02.179831: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcuda.so.1
2021-01-07 01:01:02.212743: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-07 01:01:02.212990: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1650 with Max-Q Design computeCapability: 7.5
coreClock: 1.245GHz coreCount: 16 deviceMemorySize: 3.82GiB deviceMemoryBandwidth: 104.34GiB/s
2021-01-07 01:01:02.213027: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2021-01-07 01:01:02.214189: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10
2021-01-07 01:01:02.215257: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2021-01-07 01:01:02.215483: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2021-01-07 01:01:02.216833: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.10
2021-01-07 01:01:02.217529: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.10
2021-01-07 01:01:02.217667: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.7
2021-01-07 01:01:02.217777: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-07 01:01:02.218115: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-07 01:01:02.218420: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1858] Adding visible gpu devices: 0
2021-01-07 01:01:02.218576: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero

Number of GPUs found on system: 1
TensorFlow build supports GPU: True
TensorFlow build supports XLA: True
TensorFlow build supports CUDA: True
TensorFlow build CUDA version: 10.1
TensorFlow build cuDNN version: 7

GPU: /physical_device:GPU:0
GPU index: 0
GPU name: GeForce GTX 1650 with Max-Q Design

Example
$ printf "\nPyTorch\n" && python torch_detect_GPU.py && printf "\nJAX\n" && python jax_detect_GPU.py && printf "\nTensorFlow\n" && python tf_detect_GPU.py

PyTorch
Number of GPUs found on system: 1
PyTorch has active GPU: True
PyTorch build CUDA version: 10.2
PyTorch build cuDNN version: 7605
PyTorch build NCCL version: 2708

Active GPU index: 0
Active GPU name: GeForce GTX 1650 with Max-Q Design

JAX
Number of GPUs found on system: 1
XLA backend type: gpu

Active GPU index: 0
Active GPU name: GeForce GTX 1650 with Max-Q Design

TensorFlow
2021-01-07 01:01:01.521490: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2021-01-07 01:01:02.179831: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcuda.so.1
2021-01-07 01:01:02.212743: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-07 01:01:02.212990: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1716] Found device 0 with properties:
pciBusID: 0000:01:00.0 name: GeForce GTX 1650 with Max-Q Design computeCapability: 7.5
coreClock: 1.245GHz coreCount: 16 deviceMemorySize: 3.82GiB deviceMemoryBandwidth: 104.34GiB/s
2021-01-07 01:01:02.213027: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudart.so.10.1
2021-01-07 01:01:02.214189: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcublas.so.10
2021-01-07 01:01:02.215257: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcufft.so.10
2021-01-07 01:01:02.215483: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcurand.so.10
2021-01-07 01:01:02.216833: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusolver.so.10
2021-01-07 01:01:02.217529: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcusparse.so.10
2021-01-07 01:01:02.217667: I tensorflow/stream_executor/platform/default/dso_loader.cc:48] Successfully opened dynamic library libcudnn.so.7
2021-01-07 01:01:02.217777: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-07 01:01:02.218115: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero
2021-01-07 01:01:02.218420: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1858] Adding visible gpu devices: 0
2021-01-07 01:01:02.218576: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:982] successful NUMA node read from SysFS had negative value (-1), but there must be at least one NUMA node, so returning NUMA node zero

Number of GPUs found on system: 1
TensorFlow build supports GPU: True
TensorFlow build supports XLA: True
TensorFlow build supports CUDA: True
TensorFlow build CUDA version: 10.1
TensorFlow build cuDNN version: 7

GPU: /physical_device:GPU:0
GPU index: 0
GPU name: GeForce GTX 1650 with Max-Q Design


mission record is not properly cleaned up (when missions fail)

Example in ALE:
Exception in closing of MissionRecord: boost::filesystem::remove: Directory not empty: "./mission_records/c8ba55fd-cf22-49e5-b20f-82e5f7677d66"
Similarly, in Malmo, mission records are not properly destroyed when a mission fails ("Call to write failed").

Here's one scenario I've managed to reproduce:

Create a MissionRecordSpec. This creates a temp directory and chooses path names.
Call AgentHost.startMission, passing the MissionRecordSpec. This creates a new MissionRecord object from the MissionRecordSpec, which takes its paths.
Mission fails to start
Rety: call AgentHost.startMission passing the same MissionRecordSpec as before. This creates a new MissionRecord object but with the same temp folder as before
The AgentHost's old MissionRecord object gets destroyed as it creates the new one.
The MissionRecord destructor calls close(), which tars and zips everything up, and deletes the temp folder
The mission now runs with the new MissionRecord object
The mission ends, the new MissionRecord object closes, and attempts to zip up a temp folder that no longer exists, resulting in the error "Attempt to write to non-existent directory"

The work-around is to make sure there is a fresh MissionRecordSpec object for every call to startMission - our samples are wrong in this regard.
So far I can't reproduce the "Call to write failed" error. Still looking...

The "Call to write failed" message comes from PosixFrameWriter::doWrite, so this appears to be something to do with attempting to write frames after the ffmpeg pipe has been closed. Not currently sure what effect this has on anything - frames arriving after the mission end are to be expected, and the system ought to be resilient to them...

Building on the above scenario, where we end up using a temp folder that no longer exists:

On windows, the ffmpeg process and the pipe are both created with no errors, even though ffmpeg has been told to write to a non-existent file.
The mission will start running, frames will start being pumped to ffmpeg
Eventually ffmpeg's buffer fills and it attempts to write to file. At this point it fails, and the process ends.
The pipe seems to stay active, but there is now nothing taking data out of the other end.
WindowsFrameWriter::doWrite calls WriteFile, but the pipe is now full. WriteFile helpfully waits until the pipe clears, which it never will since ffmpeg has fled in betrayal - so doWrite never returns.
Meanwhile, the mission ends, and a MissionEnded message is sent to the AgentHost.
AgentHost::onMissionControlMessage is called, and acquires the world_state_mutex
onMissionControlMessage then calls AgentHost::close
AgentHost::close calls VideoServer::stopRecording...
...which calls WindowsFrameWriter::close...
...which calls VideoFrameWriter::close...
...which calls join on the frame writer thread...
but the frame writer thread is still stuck waiting for doWrite to return.
So AgentHost::onMissionControlMessage never returns - and never releases the world_state_mutex.
Meanwhile the agent still wants to know what is going on, so calls getWorldState...
...which waits for the world_state_mutex.

And then everything is stuck.

Have changed the way things work. The MissionRecordSpec is now just that - a spec. It's now safe to reuse as often as you like. The temp folder is now created and owned by the MissionRecord object, so there will always be a new folder for each call to StartMission. This should fix many of the problems we've been having.
The API for getting the location of the temp folder has been moved to the AgentHost, since the MissionRecordSpec no longer knows anything about it.


Add named components

https://github.com/eveningkid/react-native-popable/blob/49515ac06b393bfeb8c34358f3cb901c47e76a5b/src/Popable.tsx#L27
Next.js fast refresh breaks with anonymously named components. It could be solved with export default function Popable.
This also has other implications for debugging.
I can PR this if you'd like.

Definitely, please do and I'll merge it when it's ready!

Just worked on it while I was at it: https://github.com/eveningkid/react-native-popable/pull/5
Would that work you think?


Add Users page

Hi, @satnaing . Thanks for this amazing project! <3
Can I contribute in this project on this task? Maybe you can let me know the design in your mind, and I can create a PR on this?

Hello @WenLonG12345!
I was busy and didn't notice your comment.
I already have some progress for this task by the time you dropped the comment.
However, thanks for your interest in contributing to this project.
I'll also add some contribution guidelines for this project in the future.
So, stay tuned!!!


Added max-product LP relaxation

@iglesias Sorry for late reply! I was busy for a final demo for another project, so this PR was suspended. Sorry that I missed this message as well. I am available again. I think I'll make the review done this weekend.

@hushell I am thinking about re-factory of GMPLP. Because it is essentially a message passing algorithm,   we may consider inheriting from belief propagation class. Anyway, we can discuss it before you start the review.

@Jiaolong: I just went over the MPLP code carefully. I found it's not as clean as what I expected, and its factor implementation (aka Region in their case) is quite different from ours. So I don't think it's easy to reuse our factor implementation and keep their core code only. My suggestions to finish this PR soon are listed as below.

Let's not just treat MPLP (max-product LP) as LP relaxation MAP algorithm. In fact, there are many methods can be called LP relaxation, the categorization was a bit wrong. So we can add a new macro, let's say MAX_PRODUCT_LP_RELAXATION. We'll do other types later.
We'll keep their inner data structure, i.e. Region. We don't change its name to EdgeFactor. It's helpful to try MPLP_ver1, which has simpler input/output. I can share my understandings for Region here:
m_region_inds, lists all nodes participated, e.g., (3,4) is an edge and 3 is a node index, they are both regions (factors/potentials may be more well known).
m_intersect_inds, lists all regions intersect with this region, stores region indices, e.g., region (3,4)'s index is 1, and region 3's index is 183, region 4's index is 184, then [1, 183, 184] will be stored.

UpdateMsgs implements basically the equation in Sontag's thesis (page 104). Note that messages are interpreted as dual variables in MPLP. But the update is different from their ealier conference papers. Here only messages passed from regions to variables, and Region can be viewed as a virtual concept comparing to the old update.
Let's replace their multidim_arr to SGNDArray. I think you have done this already.
You could keep all their STD stuffs, but should be hided well. Reference to BeliefPropagation.h
Let's delete their commented code when pulling into Shogun. But make sure copying their first few lines in their README.

I'll add other thoughts if they came up. If you have time, let's restart this PR, and try to finish it in 2 weeks. Our goal this week is just to import their code and make minimum needed changes.

@hushell I am currently using darwin. The organization of the inference classes in darwin looks elegant, e.g., here
I will take your advise and restart this PR as soon as possible.

Hey, guys. Just giving my point here. Inference in PGMs is a big thing and there are already good open source libraries around there. Thus, imho, it might make no sense at all to re-implement all these stuff in Shogun. However, it can be very cool and powerful to connect it with some of the features of Shogun (e.g. sosvm solvers). Maybe an interface to such a library (e.g. Darwin?) like the one we have for OpenCV is a more suitable solution.

My experience is that not all inference algorithms can be used for sosvm, e.g., loopy belief propagation. So at very beginning of this project, I chose 3 inference algorithms to implement: Tree BP for tree structure, GraphCuts for binary submodular general graph and MPLP for general graph. These are proved to be nice subroutines for sosvm. Another important reason that we want to re-implement these 3, because all other inference libs have their own graph/factorGraph data structure. We didn't want to tie with any of them. So we implemented our own factorGraph and factorGraphModel for sosvm. Yes, it will be good to implement a converter from other libs to our factorGraph.

@Jiaolong I used darwin 2 years ago. I don't suggest to follow or import darwin's code. You'll find darwin's implementation is not as intuitive as it appears. If we want to support a more general inference lib. I'll suggest to go with OpenGM.
Maybe we should think about how to deal with MPLP, as well as future support for other infernece algorithms. For MPLP, we can do either

to wrap MPLP as a 3rd-party, and convert factorGraph to MPLP's Region, which is an idea similar to OpenGM (they have a wrapper for MPLP). Such a converter can be general enough for other libs.
to extract the core inference code of MPLP, and reimplement using our factor representation. It's not very hard if you understand MPLP, which is just one iterative update step. You'll find the core part of MPLP is in UpdateMsgs function (less than 50 lines). I prefer to do this if you have time.

I don't think it is a good idea to re-implement these inference algorithms. We could make some code that translates from Shogun factors to the ones used in other libraries (something similar to what we have with SGMatrix or CFeatures and OpenCV Mat).

@iglesias Yes, this is what we should do to support many other MAP inference algorithms. However, recall that this transform has to be done for each sample in each iteration of sosvm, since factors change as parameters update. For computational efficiency concern, I suggest to reimplement MPLP at least, such that for a general loopy graph, we don't depend on 3rd-party lib. As I said, we have implemented inference algorithms for tree case, and binary loopy graph case.


Fulfillment Outbound

when u will create Class of this endpoint api?
https://github.com/amzn/selling-partner-api-docs/blob/main/references/fulfillment-outbound-api/fulfillmentOutbound_2020-07-01.md

Hi.
I have no plans for this API at the moment and a lot to do with other projects. It will come, but I can't say when.
Feel free to create a pull request with the endpoint and I'll happily merge it.