base on Datadog shared rust-based library. For now only used in other products (e.g. Ruby or PHP libraries). # `libdatadog` `libdatadog` provides a shared library containing common code used in the implementation of Datadog's libraries, including [Continuous Profilers](https://docs.datadoghq.com/tracing/profiler/). (In a past life, `libdatadog` was known as [`libddprof`](https://github.com/DataDog/libddprof) but it was renamed when we decided to increase its scope). **NOTE**: If you're building a new Datadog library/profiler or want to contribute to Datadog's existing tools, you've come to the right place! Otherwise, this is possibly not the droid you were looking for. ## Development ### Contributing See [`CONTRIBUTING.md`](CONTRIBUTING.md). ### Building Build `libdatadog` as usual with `cargo build`. #### Builder crate To generate a release with the builder crate use `cargo build -p builder` this will trigger all the necessary steps to create the libraries, binaries, headers and package config files needed to use libdatadog in your project. The default build does not include any capability so in order to add them here is the list of allowed features: - profiling: includes the profiling ffi calls and headers to the package. - telemetry: adds the telemetry symbols and headers to the package. - data-pipeline: includes the data pipeline ffi calls to the library and headers to the package. - crashtracker: adds crashtracking capabilities to the package. - symbolizer: adds symbolizer capabilities to the package. In order to set an output directory there's the `LIBDD_OUTPUT_FOLDER` environment varibale. Here's an example to create a package with all the features and save the relese on `/opt/release` folder: ```bash LIBDD_OUTPUT_FOLDER=/opt/release cargo build -p builder --features profiling,telemetry,data-pipeline,crashtracker,symbolizer ``` #### Build scripts This is the non-prefered way of building a release, it's use is discouraged and it will be soon deprecated in favour of using the builder crate. To package a release with the generated ffi header and CMake module, use the `build-profiling-ffi.sh` / `build-telemetry-ffi.sh` helper scripts. Here's an example of using on of these scripts, placing the output inside `/opt/libdatadog`: ```bash bash build-profiling-ffi.sh /opt/libdatadog ``` #### Build Dependencies - Rust 1.78.0 or newer with cargo. See the Cargo.toml for information about bumping this version. - `cbindgen` 0.26 - `cmake` and `protoc` ### Running tests This project uses [cargo-nextest][nt] to run tests. ```bash cargo nextest run ``` #### Installing cargo-nextest The simplest way to install [cargo-nextest][nt] is to use `cargo install` like this. ```bash cargo install --locked '[email protected]' ``` #### Skipping tracing integration tests Tracing integration tests require docker to be installed and running. If you don't have docker installed or you want to skip these tests, you can run: ```bash cargo nextest run -E '!test(tracing_integration_tests::)' ``` Please note that the locked version is to make sure that it can be built using rust `1.78.0`, and if you are using a newer rust version, then it's enough to limit the version to `0.9.*`. [nt]: https://nexte.st/ ", Assign "at most 3 tags" to the expected json: {"id":"11602","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"