Closed dylanorz closed 1 month ago
Would you mind sharing what distribution you are packaging the program for, @dylanorz? Thanks! Also, please let me know in case you need a new release cut.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 94.58%. Comparing base (
e5d769f
) to head (21abb1c
). Report is 1 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Thank you for your review, @d-e-s-o .
I am contributing to openeuler.org, and I'm really looking forward to the stable version of blazesym-c, which means I can introduce it into openeuler and use it in my program.
Do you have any plans related to it please?
The current plan is to integrate with one higher profile open source application (bpftrace
) to have more confidence in the suitability of the API surface before having the first stable 0.1 blazesym-c
release. This will take some more time. That being said, at this point I wouldn't expect any major breaking changes over what we currently have. If you are able to pin the version in use, there shouldn't be any issue either way.
I encountered the same problem as #767 when packaging blazecli