Skip to content

Commit

Permalink
Update PRs (#5344)
Browse files Browse the repository at this point in the history
  • Loading branch information
@hyperledger-bot
hyperledger-bot authored Oct 26, 2023
1 parent 023efde commit b77c566
Show file tree
Hide file tree
Showing 5 changed files with 79 additions and 175 deletions.
26 changes: 26 additions & 0 deletions pull-requests/hyperledger-labs/fabric-smart-client.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,32 @@ permalink: /pull-requests/hyperledger-labs/fabric-smart-client
# fabric-smart-client <span class="fs-3 right-align">[GitHub](https://github.com/hyperledger-labs/fabric-smart-client){: .btn .mr-4 }</span>


<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger-labs/fabric-smart-client/pull/506" class=".btn">#506</a>
</td>
<td>
<b>
improved chaincode event view
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
<nil>
</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-26 07:47:00 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
Expand Down
109 changes: 0 additions & 109 deletions pull-requests/hyperledger-labs/open-enterprise-agent.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -330,112 +330,3 @@ Fixes https://input-output.atlassian.net/browse/ATL-5875 CI task from not being
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger-labs/open-enterprise-agent/pull/762" class=".btn">#762</a>
</td>
<td>
<b>
feat: add new auth params
</b>
</td>
</tr>
<tr>
<td>
<span class="chip">infra</span>
</td>
<td>
# Overview

Fixes ATL-5771

## Checklist

### My PR contains...
* [ ] No code changes (changes to documentation, CI, metadata, etc.)
* [ ] Bug fixes (non-breaking change which fixes an issue)
* [x] 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
* [ ] 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-19 11:06:15 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger-labs/open-enterprise-agent/pull/761" class=".btn">#761</a>
</td>
<td>
<b>
test: add tests on keycloak authenticator logic [do not merge]
</b>
</td>
</tr>
<tr>
<td>
<span class="chip">pollux</span><span class="chip">prism-agent</span><span class="chip">build</span><span class="chip">infra</span><span class="chip">connect</span>
</td>
<td>
# Overview
<!-- What this PR does, and why is needed, a useful description is expected, and relevant tickets should be mentioned -->

Do not merge until these 2 PRs are merged and conflicts are resolved
- #758
- #755

## 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-19 09:22:14 +0000 UTC
</div>
</div>

2 changes: 1 addition & 1 deletion pull-requests/hyperledger/besu.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ See https://github.com/hyperledger/besu/issues/6058 - although it may not be com
</td>
<td>
- update to new library
- disable KZG testing on static test vectors till new ones are available



</td>
Expand Down
113 changes: 50 additions & 63 deletions pull-requests/hyperledger/cacti.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,56 @@ permalink: /pull-requests/hyperledger/cacti
# cacti <span class="fs-3 right-align">[GitHub](https://github.com/hyperledger/cacti){: .btn .mr-4 }</span>


<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/cacti/pull/2831" class=".btn">#2831</a>
</td>
<td>
<b>
fix(connector-besu): toBuffer only supports 0x-prefixed hex
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
Commit to be reviewed
---------------

fix(connector-besu): toBuffer only supports 0x-prefixed hex

```
Primary Changes
---------------
1. Updated private-deploy-contract-from-json-web3-eea.test.ts gaslimit from
3000000 to its hex equivalent
```

fixes: #2791

**Pull Request Requirements**
- [x] Rebased onto `upstream/main` branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
- [x] Have git sign off at the end of commit message to avoid being marked red. You can add `-s` flag when using `git commit` command. You may refer to this [link](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) for more information.
- [x] Follow the Commit Linting specification. You may refer to this [link](https://www.conventionalcommits.org/en/v1.0.0-beta.4/#specification) for more information.

**Character Limit**
- [x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
- [x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

**A Must Read for Beginners**
For rebasing and squashing, here's a [must read guide](https://github.com/servo/servo/wiki/Beginner's-guide-to-rebasing-and-squashing) for beginners.
</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-25 03:45:32 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
Expand Down Expand Up @@ -323,66 +373,3 @@ For rebasing and squashing, here's a [must read guide](https://github.com/servo/
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/cacti/pull/2815" class=".btn">#2815</a>
</td>
<td>
<b>
docs(examples/cbdc): update README.md with new instructions to run
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
Update README.md with new instructions to run the frontend. Previously, the source code was not in the project and a default Docker image was being provided. Now, developers can start the frontend development server directly and run the code with live reload.
</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-19 12:17:18 +0000 UTC
</div>
</div>

<div>
<table>
<tr>
<td>
PR <a href="https://github.com/hyperledger/cacti/pull/2814" class=".btn">#2814</a>
</td>
<td>
<b>
feat(connector-corda): support corda 5 RC via TS/HTTP (no JVM)
</b>
</td>
</tr>
<tr>
<td>
</td>
<td>
Fixes #1480
**Pull Request Requirements**
- [ ] Rebased onto `upstream/main` branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
- [ ] Have git sign off at the end of commit message to avoid being marked red. You can add `-s` flag when using `git commit` command. You may refer to this [link](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) for more information.
- [ ] Follow the Commit Linting specification. You may refer to this [link](https://www.conventionalcommits.org/en/v1.0.0-beta.4/#specification) for more information.

**Character Limit**
- [ ] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
- [ ] Commit Message per line must not exceed 80 characters (including spaces and special characters).

**A Must Read for Beginners**
For rebasing and squashing, here's a [must read guide](https://github.com/servo/servo/wiki/Beginner's-guide-to-rebasing-and-squashing) for beginners.
</td>
</tr>
</table>
<div class="right-align">
Created At 2023-10-19 09:30:50 +0000 UTC
</div>
</div>

4 changes: 2 additions & 2 deletions trending/recent-prs.md
View file
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@

[506](https://github.com/hyperledger-labs/fabric-smart-client/pull/506) improved chaincode event view

[4495](https://github.com/hyperledger/fabric/pull/4495) fix : updated broken link in README file

[75](https://github.com/hyperledger-labs/yui-docs/pull/75) Bump google.golang.org/grpc from 1.55.0 to 1.56.3 in /samples/minitoken-besu-ethereum/relayer
Expand All @@ -7,7 +9,5 @@

[1126](https://github.com/hyperledger/fabric-samples/pull/1126) Bump google.golang.org/grpc from 1.53.0 to 1.56.3 in /token-sdk/auditor

[1125](https://github.com/hyperledger/fabric-samples/pull/1125) Bump google.golang.org/grpc from 1.53.0 to 1.56.3 in /token-sdk/owner


[See more >>>](https://start-here.hyperledger.org/pull-requests)

0 comments on commit b77c566

Please sign in to comment.