Skip to content

Commit

Permalink
Update PRs (#5269)
Browse files Browse the repository at this point in the history
  • Loading branch information
hyperledger-bot authored Oct 11, 2023
1 parent f974074 commit 33e7e6e
Show file tree
Hide file tree
Showing 9 changed files with 260 additions and 197 deletions.
2 changes: 1 addition & 1 deletion pull-requests/hyperledger-labs/fabric-token-sdk.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ permalink: /pull-requests/hyperledger-labs/fabric-token-sdk
</td>
<td>
<b>
Added EWS Provider
Removed tx callback
</b>
</td>
</tr>
Expand Down
162 changes: 108 additions & 54 deletions pull-requests/hyperledger-labs/open-enterprise-agent.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,114 @@ permalink: /pull-requests/hyperledger-labs/open-enterprise-agent
# open-enterprise-agent <span class="fs-3 right-align">[GitHub](https://github.com/hyperledger-labs/open-enterprise-agent){: .btn .mr-4 }</span>


<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger-labs/open-enterprise-agent/pull/753" class=".btn">#753</a>
</td>
<td>
<b>
feat(prism-agent): add keycloak authorization support to endpoints [WIP]
</b>
</td>
</tr>
<tr>
<td>
<span class="chip">prism-agent</span><span class="chip">build</span><span class="chip">infra</span>
</td>
<td>
# Overview
<!-- What this PR does, and why is needed, a useful description is expected, and relevant tickets should be mentioned -->

Fixes ATL-xxxx

## Checklist

### My PR contains...
* [ ] No code changes (changes to documentation, CI, metadata, etc.)
* [ ] Bug fixes (non-breaking change which fixes an issue)
* [ ] Improvements (misc. changes to existing features)
* [ ] Features (non-breaking change which adds functionality)

### My changes...
* [ ] are breaking changes
* [ ] are not breaking changes
* [ ] If yes to above: I have updated the documentation accordingly

### Documentation
* [ ] My changes do not require a change to the project documentation
* [ ] My changes require a change to the project documentation
* [ ] If yes to above: I have updated the documentation accordingly

### Tests
* [ ] My changes can not or do not need to be tested
* [ ] My changes can and should be tested by unit and/or integration tests
* [ ] If yes to above: I have added tests to cover my changes
* [ ] If yes to above: I have taken care to cover edge cases in my tests

</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-11 17:45:35 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger-labs/open-enterprise-agent/pull/752" class=".btn">#752</a>
</td>
<td>
<b>
fix: anoncred's createPresentation
</b>
</td>
</tr>
<tr>
<td>
<span class="chip">pollux</span>
</td>
<td>
# Overview
<!-- What this PR does, and why is needed, a useful description is expected, and relevant tickets should be mentioned -->

Fixes for ATL-4887

## Checklist

### My PR contains...
* [ ] No code changes (changes to documentation, CI, metadata, etc.)
* [x] Bug fixes (non-breaking change which fixes an issue)
* [ ] Improvements (misc. changes to existing features)
* [ ] Features (non-breaking change which adds functionality)

### My changes...
* [ ] are breaking changes
* [ ] are not breaking changes
* [ ] If yes to above: I have updated the documentation accordingly

### Documentation
* [ ] My changes do not require a change to the project documentation
* [ ] My changes require a change to the project documentation
* [ ] If yes to above: I have updated the documentation accordingly

### Tests
* [ ] My changes can not or do not need to be tested
* [ ] My changes can and should be tested by unit and/or integration tests
* [ ] If yes to above: I have added tests to cover my changes
* [ ] If yes to above: I have taken care to cover edge cases in my tests

</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-11 16:43:26 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
Expand Down Expand Up @@ -354,57 +462,3 @@ A `*` can be used to signal any domain
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger-labs/open-enterprise-agent/pull/745" class=".btn">#745</a>
</td>
<td>
<b>
fix: change repository and name for rest api clients
</b>
</td>
</tr>
<tr>
<td>
<span class="chip">prism-agent</span>
</td>
<td>
# Overview
<!-- What this PR does, and why is needed, a useful description is expected, and relevant tickets should be mentioned -->

Fixes repository and names for open enterprise agent rest API clients.

## Checklist

### My PR contains...
* [ ] No code changes (changes to documentation, CI, metadata, etc.)
* [x] Bug fixes (non-breaking change which fixes an issue)
* [ ] Improvements (misc. changes to existing features)
* [ ] Features (non-breaking change which adds functionality)

### My changes...
* [ ] are breaking changes
* [x] are not breaking changes
* [ ] If yes to above: I have updated the documentation accordingly

### Documentation
* [x] My changes do not require a change to the project documentation
* [ ] My changes require a change to the project documentation
* [ ] If yes to above: I have updated the documentation accordingly

### Tests
* [x] My changes can not or do not need to be tested
* [ ] My changes can and should be tested by unit and/or integration tests
* [ ] If yes to above: I have added tests to cover my changes
* [ ] If yes to above: I have taken care to cover edge cases in my tests

</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-04 17:05:02 +0000 UTC
</div>
</div>

57 changes: 31 additions & 26 deletions pull-requests/hyperledger/aries-cloudagent-python.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,37 @@ permalink: /pull-requests/hyperledger/aries-cloudagent-python
# aries-cloudagent-python <span class="fs-3 right-align">[GitHub](https://github.com/hyperledger/aries-cloudagent-python){: .btn .mr-4 }</span>


<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/aries-cloudagent-python/pull/2544" class=".btn">#2544</a>
</td>
<td>
<b>
fix: correct minor typos
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
Fixes some minor spelling typos:

Congradulations -> Congratulations
explicitely -> explicitly
supprting -> supporting

</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-11 13:33:26 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
Expand Down Expand Up @@ -174,29 +205,3 @@ Fixes #2468.
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/aries-cloudagent-python/pull/2529" class=".btn">#2529</a>
</td>
<td>
<b>
Feat: Support subwallet upgradation using the Upgrade command
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
- resolve #2507
</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-04 16:31:37 +0000 UTC
</div>
</div>

36 changes: 0 additions & 36 deletions pull-requests/hyperledger/besu.md
Original file line number Diff line number Diff line change
Expand Up @@ -805,39 +805,3 @@ Add evaluateTransactionPostProcessing to TransactionSelector interface
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/besu/pull/5985" class=".btn">#5985</a>
</td>
<td>
<b>
Transaction detachedCopy to optimize txpool memory usage
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
<!-- Thanks for sending a pull request! Please check out our contribution guidelines: -->
<!-- https://github.com/hyperledger/besu/blob/main/CONTRIBUTING.md -->

## PR description

When a tx is decoded from RLP, some of its fields are reference to slices of the encoded RLP byte array, the latter could be shared by many transactions at the same time, for example when decoding the block body, every tx object keep a reference to the large RLP byte array, that could be hundred of KB long, the same happens when we receive a bunch on txs via p2p in the same message.
This approach works fine if the tx objects are short lived, since it means allocating and copying less data around, but does not fit well for pending txs, since they could live much longer in the txpool and a single tx could keep a reference to a large byte array, while actually only it only needs a small portion of it.

This PR solve this memory inefficiency, by creating a _detachedCopy_ of the tx when this is added to the txpool. A _detachedCopy_ is a copy that does not share any byte array with others. This also changes previous assumptions on the estimation of the amount of memory used by a pending tx, so the calculation have been updated and extended to cover also the Blob tx estimation.

relates #5977
</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-04 12:57:34 +0000 UTC
</div>
</div>

34 changes: 0 additions & 34 deletions pull-requests/hyperledger/fabric.md
Original file line number Diff line number Diff line change
Expand Up @@ -271,37 +271,3 @@ N/A
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/fabric/pull/4466" class=".btn">#4466</a>
</td>
<td>
<b>
Update add_orderer.md
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
#### Type of change

- Documentation update

#### Description

Update add_orderer.md to reflect the correct way to add a new orderer to an existing channel.

</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-04 13:21:35 +0000 UTC
</div>
</div>

30 changes: 30 additions & 0 deletions pull-requests/hyperledger/iroha-java.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,36 @@ permalink: /pull-requests/hyperledger/iroha-java
# iroha-java <span class="fs-3 right-align">[GitHub](https://github.com/hyperledger/iroha-java){: .btn .mr-4 }</span>


<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/iroha-java/pull/375" class=".btn">#375</a>
</td>
<td>
<b>
DOPS-2715: Add workflow to upload test results to Allure Test Ops
</b>
</td>
</tr>
<tr>
<td>
<span class="chip">iroha2</span>
</td>
<td>
## Changes

1. Add workflow to upload iroha2-dev `java-sdk` tests results to Allure Test Ops

Sign-off-by: [zyabkin@soramitsu.co.jp](mailto:zyabkin@soramitsu.co.jp)
</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-11 14:20:03 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
Expand Down
Loading

0 comments on commit 33e7e6e

Please sign in to comment.