We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Because libbpf is statically linked I think it would be beneficial for compatibility to pin the libbpfgo version. Same applies for libbpfgo headers.
For instance, you could keep libbpfgo as submodule and bump it and test it as soon as a new release or even commit only is available.
The text was updated successfully, but these errors were encountered:
I agree with you, we should pin the libbpf version in order to make harpoon more stable.
harpoon
Sorry, something went wrong.
IMO it is be as simple as adding it as submodule maxgio92/yet-another-profiler#4
No branches or pull requests
Because libbpf is statically linked I think it would be beneficial for compatibility to pin the libbpfgo version.
Same applies for libbpfgo headers.
For instance, you could keep libbpfgo as submodule and bump it and test it as soon as a new release or even commit only is available.
The text was updated successfully, but these errors were encountered: