Conversation
iyourshaw
commented
Oct 14, 2025
- removed comments mentioning JER
|
@iyourshaw I am getting this error when trying to build the libraries and java bindings: docker compose -f docker-compose-build.yml up --build -d
=> ERROR [build-shared 5/7] ADD ./run-lib.sh /build 0.0s
------
> [build-shared 5/7] ADD ./run-lib.sh /build:
------
Dockerfile-build:29
--------------------
27 | ADD ./asn1_codec/asn1c_combined/generated-files/2024.tar.gz /build
28 | ADD ./CMakeLists.txt /build
29 | >>> ADD ./run-lib.sh /build
30 | COPY ./src /build/src/
31 |
--------------------
failed to solve: failed to compute cache key: failed to calculate checksum of ref 0c9d7b2e-ad0f-48c6-9395-b528cb19f407::wvek12ufytlrxfypondu2ybp9: "/run-lib.sh": not foundI don't see a |
good catch, that is no longer used & was present on my machine but not in github, fixed it |
|
@iyourshaw can you use a tag of the |
Yes, updated it to use the latest |
|
@iyourshaw Can you provide the swagger docs in the API folder? Or add a |
|
@iyourshaw |
|
@iyourshaw Fix extra new-line character between line 64 and 65 in the main README.md |
|
@iyourshaw consider pulling out hard coded payloads in |
|
@iyourshaw it looks like the |
|
@iyourshaw
Also, I don't have the best understanding on memory allocation, but this is chatGPT's thoughts on your implementation. It might be completely wrong but figured I'd let you know: |
|
@iyourshaw
|
Michael7371
left a comment
There was a problem hiding this comment.
Just a few comments to make the repo even more awesome! Nice work with all of this, it is really cool!
|
@linda-baker can you review the C code (in |
|
I didn't see any memory leak issues, the buffer handling seems solid. The only thing that confuses me in the C code is the usage of "exit(EXIT_FAILURE);" when there's an error. I'm not familiar with that function, in my experience with C I'm used to returning -1 (or -2, -3 etc if you want to differentiate) to indicate errors to the caller. It looks like the way you do it works and you probably know something I don't here, but do you really want to terminate if you get an error, or would it be better to pass the error back up to MessageFrameCodec so you can course-correct from there? |
The reason the code had "exit" statements was it was originally part of a standalone command line tool, but you are right, it's better to return an error code since it's now a library with no "main" method. I've updated the C and Java library code, and will also add some unit tests to the Java to test error cases. |
|
|
Michael7371
left a comment
There was a problem hiding this comment.
Looks good, thanks for addressing my comments!
