{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":216610150,"defaultBranch":"main","name":"cacti","ownerLogin":"hyperledger","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2019-10-21T16:06:38.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/7657900?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1720107308.0","currentOid":""},"activityList":{"items":[{"before":"315e345911668a64ff3c493857c34aa06c728828","after":"02efca018a962bbbf480d2d7d98e29bc3879c195","ref":"refs/heads/main","pushedAt":"2024-07-06T02:29:12.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"build(docs/examples): add yarn patch to @ionic deps of example frontend\n\n1. The `main` field of the package.json of these two packages were invalid\nbecause the `main` field was set to `bundle.js` but that file is actually\nunder `ngx/bundle.js` within the package directory and therefore the value\nof it originally was invalid that caused warnings in our tooling.\n2. By using the yarn **patch** feature we overcame this problem by modifying\nthe sources of the dependencies in question: `@ionic-native/splash-screen` and\n`@ionic-native/status-bar`\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"build(docs/examples): add yarn patch to @Ionic deps of example frontend"}},{"before":"c0610a4f890e7114380f4ad4cddbf189dbcf0661","after":"75608722e5ae666c967dd06944b432dd57b79668","ref":"refs/heads/gh-pages","pushedAt":"2024-07-05T23:06:20.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"add Benchmark (benchmarkjs) benchmark result for 315e345911668a64ff3c493857c34aa06c728828","shortMessageHtmlLink":"add Benchmark (benchmarkjs) benchmark result for 315e345"}},{"before":"29ec45c8fce159392606a467acff2ccecddbfaf8","after":"315e345911668a64ff3c493857c34aa06c728828","ref":"refs/heads/main","pushedAt":"2024-07-05T22:49:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"test(common): jest migration of the key-converter utility test cases\n\n1. Also upgraded the tsx dependency to the latest version.\n2. We are planning on retiring ts-node in favor of tsx and this helps with\nfurther triage of it.\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"test(common): jest migration of the key-converter utility test cases"}},{"before":"8c6d9b663612792446dede88f5142979963955e6","after":"29ec45c8fce159392606a467acff2ccecddbfaf8","ref":"refs/heads/main","pushedAt":"2024-07-05T21:02:51.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"build(sync-ts-config): fix no such file or directory protos-js/tsconfig.json\n\nPrimary Changes\n---------------\n\n1. Fix issue with the object key\n2. Temporarily added ignore paths for the missing tsconfig.json so the script will run successfully\n\nFixes: #3069\nRelated to: #3366\n\nSigned-off-by: ruzell22 ","shortMessageHtmlLink":"build(sync-ts-config): fix no such file or directory protos-js/tsconf…"}},{"before":"96a3865ce5404e0fd3bf5a6471eb5a653e579d33","after":"8c6d9b663612792446dede88f5142979963955e6","ref":"refs/heads/main","pushedAt":"2024-07-05T20:50:33.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"docs(faq): added ipv6 default fix\n\n Primary Changes\n ---------------\n 1. Added a new FAQ related to configure script stuck\n at discovering npm registry due to IPv6 defaults\n\nSigned-off-by: jagpreetsinghsasan ","shortMessageHtmlLink":"docs(faq): added ipv6 default fix"}},{"before":"66e3139505c5bb3cd2e2aee86cd635d76d17374e","after":"96a3865ce5404e0fd3bf5a6471eb5a653e579d33","ref":"refs/heads/main","pushedAt":"2024-07-05T20:11:42.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"fix(ci): deprecationWarning in yarn_custom_checks\n\nPrimary Changes\n----------------\n1. Updated the main field to use index.js to fix the Deprecation Warning\n\nPeter's Fixes:\n----------------\n1. I fixed the file paths in the require statements to match the new location\nafter we've remapped the bundle location in the package.json files.\n\nFixes #2956\n\nCo-Authored-by: Peter Somogyvari \n\nSigned-off-by: aldousalvarez \nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"fix(ci): deprecationWarning in yarn_custom_checks"}},{"before":"8c030ae9e739a28ff0900f7af27ec0fbbb4b7ff9","after":"66e3139505c5bb3cd2e2aee86cd635d76d17374e","ref":"refs/heads/main","pushedAt":"2024-07-05T17:48:13.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"perf(ci): only publish artifacts on git version tags of main\n\nPrimary Changes\n----------------\n1. Remove auto publishing of container images in all **publish.yaml\n upon push and maintain automation runs during pull requests\n\nFixes #2360\n\nSigned-off-by: raynato.c.pedrajeta ","shortMessageHtmlLink":"perf(ci): only publish artifacts on git version tags of main"}},{"before":"b818aa8ea7a1f0f526940945d7bc556fe120ccd3","after":"f97bc3cec3a492cbdc63ec8cebbdc3416e204271","ref":"refs/heads/satp-dev","pushedAt":"2024-07-05T14:19:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"RafaelAPB","name":"Rafael Belchior","path":"/RafaelAPB","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/11261236?s=80&v=4"},"commit":{"message":"chore(satp-hermes): rebase with cacti main\n\nSigned-off-by: Rafael Belchior ","shortMessageHtmlLink":"chore(satp-hermes): rebase with cacti main"}},{"before":"9eefa66446a193c7ca164c876f8ed6d5cc56549b","after":"8c030ae9e739a28ff0900f7af27ec0fbbb4b7ff9","ref":"refs/heads/main","pushedAt":"2024-07-04T17:38:37.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"feat(fabric-connector): add getChainInfo, improve getBlock output\n\n- Add new method `getChainInfo` for quering chain information from qscc.\n- Add `GetChainInfoEndpointV1` to allow calling `getChainInfo` remotely.\n- Refactor `getBlock` so it can return same custom block formats\n as `WatchBlocks`. Default remains the same (full decode block).\n BREAKING CHANGE: It accepts `type` instead of `skipDecode` flag.\n- Move common block formatting logic to `cacti-block-formatters.ts`.\n- Add tests for new features. Move test common to quering `qscc` to single file\n to increase CI speed.\n\nSigned-off-by: Michal Bajer ","shortMessageHtmlLink":"feat(fabric-connector): add getChainInfo, improve getBlock output"}},{"before":"e596fad5f92ecd527398da0463ce3a856fc56ece","after":"c0610a4f890e7114380f4ad4cddbf189dbcf0661","ref":"refs/heads/gh-pages","pushedAt":"2024-07-04T15:54:45.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"add Benchmark (benchmarkjs) benchmark result for 9eefa66446a193c7ca164c876f8ed6d5cc56549b","shortMessageHtmlLink":"add Benchmark (benchmarkjs) benchmark result for 9eefa66"}},{"before":"fc9df672cbd30a28d13cb388643b3a51f18304c0","after":"9eefa66446a193c7ca164c876f8ed6d5cc56549b","ref":"refs/heads/main","pushedAt":"2024-07-04T15:37:54.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"fix(cmd-api-server): use ncc bundle in container image - CVE-2024-29415\n\nFixes the CVE mentioned and also improves our response time to future CVEs\nby a very wide margin. Details below.\n\n1. Fixing the mentioned vulnerability in the API server and doing so in\na way so that in the future our dependency upgrades automatically propagate\nto the container builds as well.\n2. The way we are achieving this is by making the container image build\nuse the pre-built bundle instead of pulling the package contents from npm.\n3. This has the advantage of breaking the chicken egg problem with releases\nto npm and container images, so from now on if we are adding a fix to the\nAPI server in the code, the built container image will automatically contain\nthat fix when building on the CI for the pull request.\n4. This is also a new pattern for how to create our container images that\nhas a couple more improvements to it:\n4.1. The .dockerignore file is now specific to the particular package's\ncontainer image instead of the global one in the project root being used.\nThis was needed because we are copying files from the ./dist/ folder of the\npackage to the container image at build time but this was not possible while\nthe root dir .dockerignore file was in effect because it blanket ignores\nthe ./dist/ folders overall and so the image building was failing with errors\nthat it couldn't locate the bundle (which is inside the ./dist/ directory)\n4.2. The healthcheck of the container is now 100% self-contained and needs\nno external dependencies of any kind (neither npm nor operating system level ones)\nThis is beneficial because it reduces the attack-surface of the image and also\nreduce the size of the image by at least a 100 MB.\n4.3. With the introduction of the usage of the bundled version of the code\nwe have **dramatically** reduced the image size overall. The image built from\nthis revision of the code is 221 MB while the previous image versions were\nhovering closer to a 0.5 GB.\n5. Also updated the README of the package so that all the examples pertaining\nto the container image are now fully functional once again.\n6. Simplified the container image's definition: the custom docker entrypoint\nscript and the healthcheck bash script are no longer necessary.\n7. Renamed the container image definition file from `Dockerfile` to\n`cmd-api-server.Dockerfile` because this is mandated by Docker when building\nimages with custom .dockerignore files (it needs the custom filename to\ndisambiguate the .dockerignore files based on it)\n8. Refactored how the CI executes the Trivy scan to reduce resource usage:\n8.1. There is no separate image build job now. This was necessary because\nwith the new image definition we have to have the project compiled first\n(since we no longer install directly from npm) so it would've been a lot of\nduplicated compute time to recompile the project in yet another CI job for the\nimage build.\n\nThe image built from this revision is also published on the official repository\nwith the canary tag of:\n`ghcr.io/hyperledger/cactus-cmd-api-server:2024-07-03T19-32-51-dev-3f5e97893`\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"fix(cmd-api-server): use ncc bundle in container image - CVE-2024-29415"}},{"before":"fc9df672cbd30a28d13cb388643b3a51f18304c0","after":null,"ref":"refs/heads/release-v2.0.0-rc.2","pushedAt":"2024-07-04T15:17:05.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"}},{"before":"08925ffc8815d9613a69204a74c85d168f8a8305","after":"fc9df672cbd30a28d13cb388643b3a51f18304c0","ref":"refs/heads/main","pushedAt":"2024-07-04T15:17:03.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"chore(release): publish v2.0.0-rc.2\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"chore(release): publish v2.0.0-rc.2"}},{"before":"a8cedddb3acdd98860da39545be0fb383373121e","after":"fc9df672cbd30a28d13cb388643b3a51f18304c0","ref":"refs/heads/release-v2.0.0-rc.2","pushedAt":"2024-07-03T22:47:50.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"chore(release): publish v2.0.0-rc.2\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"chore(release): publish v2.0.0-rc.2"}},{"before":null,"after":"a8cedddb3acdd98860da39545be0fb383373121e","ref":"refs/heads/release-v2.0.0-rc.2","pushedAt":"2024-07-03T22:40:44.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"chore(release): publish v2.0.0-rc.2\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"chore(release): publish v2.0.0-rc.2"}},{"before":"d14bf02aed215eeecdba258bb48a330da3fc2c36","after":"08925ffc8815d9613a69204a74c85d168f8a8305","ref":"refs/heads/main","pushedAt":"2024-07-03T15:44:19.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"fix(plugin-persistence-ethereum): make created_at TIMESTAMPTZ in schema\n\n1. The problem was that the database schema was defined in a way that was\ndestroying timestamp information during insertion of records.\n2. Updating the schema to hold the timestamp information made the test pass.\n\nMore information about why it's recommended to store datetime data with\nthe TIMESTAMPTZ column type is explained by the author of the node-postgres\nlibrary which is an important part of the problem (it assumes local time\nfor columns that do not store the timestamp time zone).\n\nhttps://node-postgres.com/features/types#date--timestamp--timestamptz\n\nFixes #3373\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"fix(plugin-persistence-ethereum): make created_at TIMESTAMPTZ in schema"}},{"before":"eaba573e9c9c630f836f92d06ef9c1bb4ea49f4e","after":"d14bf02aed215eeecdba258bb48a330da3fc2c36","ref":"refs/heads/main","pushedAt":"2024-07-02T19:36:48.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"fix(cmd-api-server): shutdown hook was not waiting for promises\n\n1. The library we use for having async functions handle resource deallocation\nwas not being used correctly by the API server.\n2. The library only supports callback style asynchronous code and the API\nserver assumed that it could return a promise from the shutdown hooks which\nlead to the problem that our shutdown hooks were not being awaited for.\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"fix(cmd-api-server): shutdown hook was not waiting for promises"}},{"before":"bf92d3d85bcbb48ffe72d4239436a1860fc4cf35","after":"eaba573e9c9c630f836f92d06ef9c1bb4ea49f4e","ref":"refs/heads/main","pushedAt":"2024-07-02T18:59:31.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"docs(examples/supply-chain-app): fix resource cleanup of shutdown logic\n\n1. Now you can run the supply chain app example locally and then hit CTRL+C\non the terminal and it will gracefully shut down all the containers hosting\nthe infrastructure and only after that the NodeJS process itself will exit.\n2. Previously we had a bug where it wouldn't wait for the containers to wind\ndown and it left them running which was causing problems when people didn't\nnotice this behavior and their machines would get into this broken state where\nthe previous execution's containers were hanging around and one of them blocking\nports too.\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"docs(examples/supply-chain-app): fix resource cleanup of shutdown logic"}},{"before":"fa190eda7a125594e3f7e3c3cef7d05488b82849","after":"bf92d3d85bcbb48ffe72d4239436a1860fc4cf35","ref":"refs/heads/main","pushedAt":"2024-07-01T23:47:02.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"build(connector-besu): fix CVE-2022-21190 CVE-2023-36665 CVE-2022-2421\n\nPrimary Changes\n----------------\n1. Updated the version of the base image that is used in the Dockerfile\n2. Updated the Dockerfile to use the yarn version 4\n3. Updated the README to the new command to run the container\n\nFixes #2745\n\nSigned-off-by: aldousalvarez ","shortMessageHtmlLink":"build(connector-besu): fix CVE-2022-21190 CVE-2023-36665 CVE-2022-2421"}},{"before":"55e631b2aba6a1c301303539b6a3b5aa2b316988","after":"e596fad5f92ecd527398da0463ce3a856fc56ece","ref":"refs/heads/gh-pages","pushedAt":"2024-07-01T17:09:10.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deployed fa190eda7 with MkDocs version: 1.6.0","shortMessageHtmlLink":"Deployed fa190ed with MkDocs version: 1.6.0"}},{"before":"6ef514cc01eda2640ed144bdd4750dbcb1e35e27","after":"fa190eda7a125594e3f7e3c3cef7d05488b82849","ref":"refs/heads/main","pushedAt":"2024-07-01T17:02:41.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"docs(examples/supply-chain-app): print correct web host in the CLI logs\n\n1. The logs were showing the bound host which in our case was 0.0.0.0\nbut that is not accepted by web browsers when you are executing HTTP XHR\nrequests from Javascript.\n2. This change makes it so that even though we bind to 0.0.0.0 the logs\nto the person running the example application will show 127.0.0.1.\nThis might potentially cause further confusion in some people who'd think\nthat we are binding to 127.0.0.1 based on the logs, but this seems like an\nacceptable trade-off for an example which has the number one priority of\nbeing easily digestable.\n\nFixes #2390\n\nDepends on #3362\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"docs(examples/supply-chain-app): print correct web host in the CLI logs"}},{"before":"ff6e5afa5e12df611489a494f2b07d04b017ec00","after":"6ef514cc01eda2640ed144bdd4750dbcb1e35e27","ref":"refs/heads/main","pushedAt":"2024-07-01T16:43:00.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"fix(cmd-api-server): stop changing LoggerProvider log level\n\n1. The API server was mutating global shared state in it's own constructor\nwhich was causing problems with other components (pretty much all of them)\n2. I deleted the line that copies the API server's own log level to the\nLoggerProvider so that the API server's log level can be it's own.\n3. The way this bug came about is that in the supply chain app example\nin the back-end the API server had to be muted (log level WARN) in order\nfor it to stop printing misleading logs due to us binding to the wildcard\nhost it would claim in its own logs that the WWW GUI is accessible on the\nwildcard host in a web browser, but this was wrong and caused many people\na lot of confusion unfortunately.\n4. The fix for the supply chain app is to set the API server's log level to\nWARN and have the supply chain app itself log the correct URLs to the console.\n5. The issue I ran into with that fix is that as soon as I set the log level\nof the API server to WARN, everything else also stopped logging which resulted\nin my fix making everything worse since now the users had absolutely no\nidea what was happening or if the example application had even finished booting\nup or not.\n6. Upon further debugging I discovered that the API server was forcing its\nown log level onto everybody else as the root cause.\n7. A follow-up PR is about to drop with the supply chain app fixes which are\ndependent on this one making it in first.\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"fix(cmd-api-server): stop changing LoggerProvider log level"}},{"before":"5abaaec2019868da40e4a3a66ac63cf9841c7cf2","after":"55e631b2aba6a1c301303539b6a3b5aa2b316988","ref":"refs/heads/gh-pages","pushedAt":"2024-06-28T17:15:28.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"github-actions[bot]","name":null,"path":"/apps/github-actions","primaryAvatarUrl":"https://avatars.githubusercontent.com/in/15368?s=80&v=4"},"commit":{"message":"Deployed ff6e5afa5 with MkDocs version: 1.6.0","shortMessageHtmlLink":"Deployed ff6e5af with MkDocs version: 1.6.0"}},{"before":"88965187de69076420237a93548a9e5fdd7f0e74","after":"ff6e5afa5e12df611489a494f2b07d04b017ec00","ref":"refs/heads/main","pushedAt":"2024-06-28T17:09:06.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"chore(docs): add openapi specs to docs\n\nPrimary Changes\n1. Updated deploy_docs workflow to generate markdown for openapi\n specs files present across packages\n\nSecondary Changes required to incorporate 1)\n2. Added docs/scripts/publish_openapi.py to generate markdown\n3. Added swagger-ui-tag plugin to mkdocs\n4. Updated docs/requirements.txt for the above plugin to be\n downloaded.\n\nSigned-off-by: Jennifer Bell ","shortMessageHtmlLink":"chore(docs): add openapi specs to docs"}},{"before":"199c1f05c282d15ba2ded9e7a69253483fbac2ec","after":"88965187de69076420237a93548a9e5fdd7f0e74","ref":"refs/heads/main","pushedAt":"2024-06-28T11:13:44.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"sandeepnRES","name":"Sandeep Nishad","path":"/sandeepnRES","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/17192099?s=80&v=4"},"commit":{"message":"fix(go-sdk): use protos v1 api for fabric-protos-go unmarshal\n\n ci(release-go-sdk): use make build to test build of go-sdk\n chore: fix update-weaver-version script typo with quotes\n chore: bug fix in release script go-gen-checksum\n test(go-sdk): change test package names to _test, add membership test\n\nSigned-off-by: Sandeep Nishad ","shortMessageHtmlLink":"fix(go-sdk): use protos v1 api for fabric-protos-go unmarshal"}},{"before":"5cbebad5c75b8f43ee515de3f4ef1fc8cf3f088f","after":"199c1f05c282d15ba2ded9e7a69253483fbac2ec","ref":"refs/heads/main","pushedAt":"2024-06-27T19:19:07.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"feat(connector-besu): expose API client and OpenAPI code for web builds\n\n1. We were only exporting the API client and the related data model type\ndefinitions for NodeJS builds but not for the web.\n2. This made it so that you couldn't import/use the Besu API client from\na front-end application such as Angular or React.\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"feat(connector-besu): expose API client and OpenAPI code for web builds"}},{"before":"ac6e8841189bd816ec4efd657123c28dbff4dfb8","after":"5cbebad5c75b8f43ee515de3f4ef1fc8cf3f088f","ref":"refs/heads/main","pushedAt":"2024-06-27T19:02:17.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"build(typescript): upgrade compiler to v5.5.x\n\n1. Brings in size and performance improvements.\n2. Also adds support for some new features such as Ecmascript setters\n3. Also upgraded typedoc project-wide so that its peer dependency constraints\naren't failing the build due to the newer typescript version.\n\nhttps://www.infoworld.com/article/3715246/typescript-adds-support-for-ecmascripts-set-methods.html\n\nFixes #3326\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"build(typescript): upgrade compiler to v5.5.x"}},{"before":"5abbbffb4fc6f1cfbaf758a7bc25166aa6805d9a","after":"ac6e8841189bd816ec4efd657123c28dbff4dfb8","ref":"refs/heads/main","pushedAt":"2024-06-27T17:10:21.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"test(connector-corda): fix deploy-cordapp-jars-to-nodes-v4.8-express\n\n1. Upgrading the images that were being used made it so that now the test\nis no longer flaky/broken (or at least that's what a series of executions\nof it made it looked like on my local machine)\n2. Based on the above it might be worthwhile to put this test back into the\nones that are running (previously it was marked to be skipped).\n3. We should keep an eye on it to make sure it's not flaky on the CI either\n(which has resources much more constrained than my local development machine)\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"test(connector-corda): fix deploy-cordapp-jars-to-nodes-v4.8-express"}},{"before":"d9d590450af6d231c5e38046bffd6d08786c29f4","after":"5abbbffb4fc6f1cfbaf758a7bc25166aa6805d9a","ref":"refs/heads/main","pushedAt":"2024-06-27T16:50:31.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"ci(custom-checks): fix depcheck not detecting missing dependencies\n\n1. The depcheck tool we use have not correctly discovered some of the\nmissing dependencies that we have because it only verifies that the\nimported dependency is present SOMEwhere in the package.json file, not that\nit is specifically present in the production dependencies section which\nleads to crashes and broken packages due to the API server not installing\ndev dependencies when instantiating a plugin and therefore missing a few\nof the dependencies that are otherwise very much needed at runtime in\nproduction.\n2. The solution to the problem was to implement our own typescript parsing\nwith babel and then double check the work of depcheck to make sure that\nthe dependencies that it marks as \"no issues\" are actually OK and have no\nissues.\n3. The hardest edge case was type imports e.g. `import type { Express } from \"express\";`\nbecause the import was there, but we did not actually need that dependency\nin the production dependencies as long as ALL of the imports to it in the\ngiven package were type imports. To robustly verify this being the case or not\nwe had to pull out the big guns and parse all the typescript code per package\nto make sure that we've looked at every single import of the dependency in\nquestion at every single code file of the package in question.\n\nDepends on #3345\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"ci(custom-checks): fix depcheck not detecting missing dependencies"}},{"before":"0508f14c64e452f8f89881db363cd00b3c8c255c","after":"d9d590450af6d231c5e38046bffd6d08786c29f4","ref":"refs/heads/main","pushedAt":"2024-06-27T05:57:17.000Z","pushType":"pr_merge","commitsCount":1,"pusher":{"login":"petermetz","name":"Peter Somogyvari","path":"/petermetz","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/1583231?s=80&v=4"},"commit":{"message":"feat(connector-corda): add initial set of JvmObject factory functions\n\n1. These functions are used so more easily construct the JSON representation\nof JVM objects (references and primitive values) that we need to define when\ninteracting with the Corda JVM connector (which is used for Corda v4 ledgers)\n2. This is not a comprehensive set but more like a trailblazing initial\nimplementation to showcase how to create and use these factory functions.\n\nSigned-off-by: Peter Somogyvari ","shortMessageHtmlLink":"feat(connector-corda): add initial set of JvmObject factory functions"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEeDmawQA","startCursor":null,"endCursor":null}},"title":"Activity · hyperledger/cacti"}