Update dependency biojppm/rapidyaml to v0.16.0

[dashql-renovate]

This PR contains the following updates:

Package	Update	Change
biojppm/rapidyaml	minor	0.12.1 → 0.16.0

---

Release Notes

biojppm/rapidyaml (biojppm/rapidyaml)

v0.16.0: Release 0.16.0

Compare Source

TL;DR

This release focuses on API cleaning and tidying, in preparation of release 1.0:

• improves tracking of nodes causing deserialization errors
• adds serialization to/from Tree (not just NodeRef/ConstNodeRef)
• deprecates a good number of functions, mostly around serialization and tree/node building
• brings code coverage to 100% (rounded from >99.5%)
• remove the c4core submodule, vendoring-in just the required c4core source code.

The API cleanup introduces a number of deprecations, and some other opt-in but recommended changes: see the migration guide in the next section.

Finally there are other fixes and improvements: see the full changelog, below the migration guide.

Migration guide

This is the list of migration changes, linking to the relevant section below:

• Deprecated .to_val() method family for tree building
• Deprecated operators (but define RYML_WITH_LEGACY_OPERATORS to avoid the deprecation):
  • tree building: deprecate operators |= or =
  • serialization: deprecate operators << or >>
• Optional but recommended:
  • user-implemented read() should now return ReadResult
  • user-implemented read()/write() should now receive Tree and id
  • do not use .load() (former >>) inside read()
  • use .deserialize_child() inside read()

Be sure to also read through the quickstart diff for the full overview on how the new features work.

[!TIP]
Hint to see what changed in the quickstart: run git diff v0.15.2...v0.16.0 samples/quickstart.cpp on an up-to-date repo clone.

Deprecate .to_val() family

For tree building, methods .to_*() were deprecated in favour of the newly-added .set_*() methods. See next section.

Deprecate operators |= and =

For tree building, operator|= and operator= were deprecated in favour of the newly-added .set_*() methods:

c4::yml::Tree tree = ...;
c4::yml::id_type node_id = ...;
c4::yml::NodeRef node = ...;

// before (deprecated)
node |= MAP|BLOCK;
node["key"] = "val";
node["key"] |= VAL_SQUO;
node["seq"] |= SEQ|FLOW;
node["seq2"] |= SEQ;
node.append_child().to_seq("map");

// now, same as above:
node.set_map(BLOCK);
node["key"].set_val("val", VAL_SQUO);
node["seq"].set_seq(FLOW);
node["seq2"].set_seq();
c4::yml::NodeRef child = node.append_child();
child.set_seq("map");

// or now, same as above, but from the tree:
// more code, but also more efficient
tree.set_map(node_id, BLOCK);
c4::yml::id_type id_key  = tree.append_child(node_id),
                 id_seq  = tree.append_child(node_id),
                 id_seq2 = tree.append_child(node_id),
                 id_map  = tree.append_child(node_id);
tree.set_key(id_key, "key");
tree.set_val(id_key, "val", VAL_SQUO);
tree.set_key(id_seq, "seq");
tree.set_seq(id_seq, FLOW);
tree.set_key(id_seq2, "seq2");
tree.set_seq(id_seq2);
tree.set_key(id_map, "map");
tree.set_map(id_map);

If you prefer to keep on using the legacy operators =, |=, <<, >>, you can enable the cmake symbol (or define the macro) RYML_WITH_LEGACY_OPERATORS.

Deprecate operators << and >>

For serialization, operator<< and operator>> were deprecated in favour of .set_serialized() and .deserialize() (which introduce return on error) or .save() and .load() (which trigger error callback on error):

c4::yml::Tree tree = ...;
c4::yml::id_type node_id = ...;
c4::yml::NodeRef node = ...;
const T var1 = ...;
T var2 = ...;

// before (deprecated)
node << var1;
node >> var2;
node << key(var1);
node >> key(var2);

// now - save() and load() do checks and call error on failure
node.save(var1);
node.load(&var2);
node.save_key(var1);
node.load_key(&var2);
// or now, without exceptional flow: use .set_serialized() and .deserialize()
node.set_serialized(var1);
if( ! node.deserialize(&var2))
  ...
node.set_key_serialized(var1);
if( ! node.deserialize_key(&var2))
  ...

// also now possible from tree!
tree.save(node_id, var1);
tree.load(node_id, &var2);
tree.save_key(node_id, var1);
tree.load_key(node_id, &var2);
tree.set_serialized(node_id, var1);
if( ! tree.deserialize(node_id, &var2))
  ...
tree.set_key_serialized(node_id, var1);
if( ! tree.deserialize_key(node_id, &var2))
  ...

If you prefer to keep on using the legacy operators =, |=, <<, >>, you can enable the cmake variable (or define the macro) RYML_WITH_LEGACY_OPERATORS.

The rest of the changes are optional, but recommended. If you don't do these changes, your code will go on working as before, but the new features and improved behavior will not be available.

Optional: user-implemented read() should now return ReadResult

Your read() functions should now return a c4::yml::ReadResult. This enables reporting the exact node on which a deserialization error happens, even if it is nested deep in the tree, which in turn helps tremendously pinpointing problems in YAML source (especially with location tracking):

// optional: your implementation of read() should be changed from...
bool read(c4::yml::ConstNodeRef const& node, T *var)
{
    bool success = ...;
    return success;
}
// optional: change to this:
c4::yml::ReadResult read(c4::yml::ConstNodeRef const& node, T *var)
{
    bool success = ...;
    return c4::yml::ReadResult(success, node.id());
}

If you don't change, rapidyaml will still report the error, but on the node of the outer-most function returning false, instead of the node at the inner-most function.

Optional: user-implemented read()/write() should now receive Tree and id

If you want to use deserialization from Tree, your read() and write() implementations should now be rewritten for Tree, instead of NodeRef. This will enable using your read()/write() functions with both the Tree and NodeRef methods:

// optional: your implementation of write()/read() should be changed from...
void write(c4::yml::NodeRef *node, T const& var)
{
    ...
}
c4::yml::ReadResult read(c4::yml::ConstNodeRef const& node, T *var)
{
    bool success = ...;
    return c4::yml::ReadResult(success, node.id());
}

// optional: change to this to enable serialization from/to both Tree and NodeRef:
void write(c4::yml::Tree* tree, c4::yml::id_type id, T const& var)
{
    ...
}
c4::yml::ReadResult read(c4::yml::Tree const* tree, c4::yml::id_type id, T *var)
{
    bool success = ...;
    return c4::yml::ReadResult(success, id);
}

If you don't change, you will not be able to serialize to/from Tree. That is, having only the node implementation will not work with the Tree methods. You can also provide both functions, and they would be picked up correctly, but that is pointless. In short, prefer the Tree version.

Note also that inside the tree version, you can still use the node API. For example:

c4::yml::ReadResult read(c4::yml::Tree const* tree, c4::yml::id_type id, T *var)
{
    c4::yml::ConstNodeRef n(tree, id);
    ... // this way you can keep the function body as before
        // BUT read next note
}

Optional: do not use .load() (former >>) inside read()

Inside your write()/read() implementation you should now use the new .deserialize() calls. On error, these methods will play nice when they are called from .deserialize() on upper-level objects. On the contrary, .load() (formerly >>) will interrupt execution immediately, and this will prevent those upper-level calls from successfully receiving the actual ReadResult and reporting it upwards.

If you want to avoid exceptional flow and write code such as

struct Inner { int foo, bar; };
struct Outer { Inner inner1, inner2; }

Outer outer;
if( ! node.deserialize(&outer))
    ... // we want to enter this branch without triggering an error

... then your read(tree,id,Inner*) implementation should not use .load():

c4::yml::ReadResult read(c4::yml::Tree const* tree, c4::yml::id_type id, Inner *inner)
{
    c4::yml::ReadResult result(tree->is_map(id), id);
    if(result) result = tree->deserialize_child(id, "foo", &inner->foo);
    if(result) result = tree->deserialize_child(id, "bar", &inner->foo);
    return result;
}
// Likewise for the outer type. Note how an Inner error will be
// transparently returned:
c4::yml::ReadResult read(c4::yml::Tree const* tree, c4::yml::id_type id, Outer *outer)
{
    c4::yml::ReadResult result(tree->is_map(id), id);
    if(result) result = tree->deserialize_child(id, "inner1", &outer->inner1);
    if(result) result = tree->deserialize_child(id, "inner2", &outer->inner2);
    return result;
}

In short, implementing read() with .deserialize() plays nice with both upper .deserialize() and .load() calls, whereas implementing read() with .load() will only work with upper .load() calls.

Recommended: use new methods .deserialize_child() in read()

Inside your read() implementation, you should now use the new methods .deserialize_child().

This release also adds a family of methods to simplify read() implementations. Each of these returns a ReadResult object that is ready to return on error. Consider the following node-based read(), already using .deserialize():

ryml::ReadResult read(ryml::ConstNodeRef const& n, my_type *val)
{
    ryml::ReadResult r(n.is_map(), n.id());
    if(r) r = n["v2"].deserialize(&val->v2); // don't. using [] will throw error if "v2" is not a child
    if(r) r = n["v3"].deserialize(&val->v3);
    if(r) r = n["v4"].deserialize(&val->v4);
    if(r) r = n["seq"].deserialize(&val->seq);
    if(r) r = n["map"].deserialize(&val->map);
    return r;
}

Any of the operator[] calls (or more precisely the .deserialize() calls on its result) may trigger a visit error when no such node exists. To avoid exceptional flow in case of error, you should now use .deserialize_child() which simplifies a graceful return with an appropriate error status when the child node does not exist:

ryml::ReadResult read(ryml::ConstNodeRef const& n, my_type *val)
{
    ryml::ReadResult r(n.is_map(), n.id());
    if(r) r = n.deserialize_child(n, "v2", &val->v2); // there is also a fall-back overload
                                                      // receiving a default value when
                                                      // no such child exists
    if(r) r = n.deserialize_child(n, "v3", &val->v3);
    if(r) r = n.deserialize_child(n, "v4", &val->v4);
    if(r) r = n.deserialize_child(n, "seq", &val->seq);
    if(r) r = n.deserialize_child(n, "map", &val->map);
    return r;
}

Here's the list of new ReadResult-returning methods that may be of use in similar scenarios:

• Tree::deserialize_child(), ConstNodeRef::deserialize_child(), ConstNodeRef::deserialize_child(): both for keys and indices (on seqs)
• Tree::child_r(), ConstNodeRef::child_r(), ConstNodeRef::child_r()
• Tree::find_child_r(), ConstNodeRef::find_child_r(), ConstNodeRef::find_child_r()
• likewise for sibling: added sibling_r and find_sibling_r()
• The .get_if() methods were deprecated in favour of .deserialize_child().

Full changelog

• Update c4core to v0.6.0
• PR#649 commit to ABI stability on patch releases before 0.x, then on minor releases after 1.x
• PR#648 improve documentation, add benchmark results
• PR#647 remove support for UTF16 and UTF32 encoded files
• PR#646 improve Doxygen docs, update yamlscript version
• PR#645 tools: unify ryml-parse-emit and ryml-yaml-events, remove ryml-yaml-events
• PR#644 amalgamate: add --fastfloat_sys to use fastfloat from system
• PR#643 reduce source archive size: move large data files used in benchmarks to rapidyaml-data repo.
• PR#642 amalgamate: add option to create single source+header.
• PR#641: change uses of C4_LIKELY() / C4_UNLIKELY() to turn into [[likely]] / [[unlikely]]. No logic changes.
• PR#640: add .deserialize_child() methods to simplify read() implementations
• PR#639: fix names using leading/double underscore (renames only, no logic changes).
• PR#638: improve quickstart-ints.
• PR#637: add cmake option RYML_SYSTEM_C4CORE to consume c4core from find_package(). Thanks @​uilianries!
• PR#636 remove c4core submodule, and copy c4core files to rapidyaml (and manage sync):
  • ext/c4core.src/: c4core code used in the rapidyaml library
  • ext/c4core.dev/: c4core code used by tests/benchmarks
  • proj/: project files like cmake files and toolchains
  • RYML_STANDALONE can still be set to OFF to compile against an out-of-source c4core (see also the newly added RYML_SYSTEM_C4CORE)
  • the amalgamation tool now adds only the files in c4core.src files, and has new option --c4core-dev to include the c4core.dev files
  • adds (internal) tools to manage c4core synchronization scenarios. See ext/README.md for details with this.
• PR#635 API cleanup: NodeType and extra::ievt::EventFlags:
  • On Tree and NodeRef, overloads taking NodeType_e are now receiving type_bits.
  • This saves operator calls on type queries.
  • Remove bitwise operators, no longer needed.
  • Rename NodeType_e to NodeTypeBits (deprecate NodeType_e)
  • Low impact, no changes should be needed on user code, other than renaming unlikely uses of NodeType_e.
  • Also, for int events: rename extra::ievt::EventFlags to extra::ievt::EventBits
• PR#620 API cleanup: Tree and NodeRef:
  • Deprecate NodeInit
  • Tree and NodeRef:
    • deprecate .to_val() and friends -- add .set_val() and friends.
    • deprecate operator=(csubstr) and friends -- use .set_val() instead.
    • deprecate operator|=(NodeType) and operator=(NodeType) -- use appropriate overload .set_*(T, NodeType).
    • You can disable compiler deprecation warnings from use of these operators: by enabling the cmake variable (or defining the macro) RYML_WITH_LEGACY_OPERATORS.
    • deprecate NodeInit and NodeScalar methods in Tree and NodeRef (use .set_*())
    • deprecate single-arg NodeRef::{duplicate,move}(ConstNodeRef)
    • deprecate NodeRef::visit() and NodeRef::visit_stacked()
    • add Tree::arena_rem()
    • add RYML_DEFAULT_TREE_ARENA_CAPACITY_START with default value of 256
  • parse_*(): internal simplification, no semantic changes
• PR#589 API cleanup: serialization and tree building
  • Refactor serialization code:
    • Deprecate operator<<, use .load() / .load_key() or .deserialize() / .deserialize_key()
    • Deprecate operator>>, use .save() / .save_key() or .set_serialized() / .set_key_serialized()
    • Deprecate key() tag function and Key tag type (needed only for the operators above)
    • Migration of code triggering serialization:
    • If you don't want to migrate yet, use RYML_WITH_LEGACY_OPERATORS to disable compiler deprecation warnings from use of these operators.
    • Serialization with Tree API is now fully implemented, working exactly the same as NodeRef
      • serialization:
        • NodeRef serialized with write(NodeRef *, T const&) and write_key()
        • Tree serialized with write(Tree *, id_type, T const&) and write_key()
        • No changes in types using to_chars() serialization
      • deserialization:
        • ConstNodeRef deserialized with read(ConstNodeRef const&, T *) and read_key()
        • Tree deserialized with read(Tree const*, id_type, T *) and read_key() (removed old readkey() approach.)
        • No changes in types using from_chars() serialization
      • Enables bypass of NodeRef serialization to use the tree API, which is faster to compile.
      • Organize serialization in layers, ensuring use of free functions to enable the user to override at all levels with ADL, for total control of type behavior (explained in the doxygen documentation).
      • Added many more unit tests to ensure all scenarios are working.
  • Move scalar specific code to new top-level headers c4/yml/scalar_charconv.hpp and c4/yml/scalar_style.hpp
  • Relax deserialization of nodes with VALNIL or KEYNIL, such that non-fundamental types can now be null-initialized (eg initialize a string from a null scalar). Fundamental types such as ints or floats will still report an error.

    Tree tree = parse_in_arena("{empty: }");
    std::string str;
    tree["empty"].load(&str); // relaxed: no longer a deserialization error
    assert(s.empty());
    int val;
    tree["empty"].load(&val); // ERROR! as before.

• PR#626: ensure accurate reporting of nodes causing deeply nested serialization error. This enables reporting the inner-most node causing the error! To profit from this, read() user functions should now return ReadResult instead of bool. This change is backwards-compatible with legacy read() functions returning bool, but the legacy version will remain less precise: it will report an inner error on the upmost node returning false, possibly the root if all levels are returning bool. See the new sample_deserialize_error() on the quickstart, and the latest doxygen documentation. The user functions should change (but not mandatory):

  // before
  bool read(ryml::ConstNodeRef n, T *var) { ... }
  // now (should be changed, but not mandatory)
  ryml::ReadResult read(ryml::ConstNodeRef n, T *var) { ... }

• PR#625: Set plain scalar style when serializing arithmetic scalars: improves emit speed of numeric-heavy data payloads.
• PR#616 API cleanup: emit
  • WriterFile and WriterOStream no longer track the number of emitted bytes.
  • error_on_excess is now used in the emit-to-buffer overloads, and no longer in the main Emitter::emit_as() driver function.
• PR#617 API cleanup: emit, part 2
  • Tidy emit classes among new top-level header files:
    • c4/yml/emit_container.hpp: emit to resizeable contiguous char container (eg std::string, std::vector<char>)
    • c4/yml/emit_buf.hpp: emit to char buffer (substr)
    • c4/yml/emit_file.hpp: emit to C FILE*
    • c4/yml/emit_ostream.hpp: emit to STL-like ostreams
  • The old c4/yml/emit.hpp is now a pure umbrella header, including all of the above. For better compilation speed, avoid the umbrella header, and prefer including the concrete header (container, buf, file or stream).
  • The rest of the emit code was split over these new implementation headers:
    • c4/yml/emit_options.hpp: options to control emitting
    • c4/yml/emitter.hpp: main emitter class
    • c4/yml/emitter.def.hpp: definitions of main emitter class.
    • c4/yml/writer_buf.hpp: policy class to emit to char buffer (substr)
    • c4/yml/writer_file.hpp: policy class to emit to C FILE*
    • c4/yml/writer_ostream.hpp: policy class to emit to STL-like ostreams
  • There are no semantic changes: all the emit_*() functions remain the same.
  • Other changes in this PR:
    • Added Tree::root_id_maybe() which is safe to call on an empty tree.
    • Deprecate Emitter::max_depth()
    • Deprecate Emitter::options() setter
• PR#618: API cleanup: emit, part 3
  • Improve handling of NaN and Inf in json emitting.
  • Expose scalar style helpers for json emitting:

    bool scalar_is_plain_number_json();
    bool scalar_is_special_json();
    bool scalar_is_inf3();
    bool scalar_is_nan3();
    bool scalar_is_inf_or_nan3();

  • Writers: add C4_ALWAYS_INLINE. Results in ~10-20% emit improvements.
  • file_put_contents(): add FILE* overloads
• PR#621 API cleanup: NodeRef:
  • Simplify internal implementation of {Const}NodeRef::{iterator,children_view}.
  • Stop using SFINAE on Node CRTP to distinguish const vs non const, by duplicating the functions in NodeRef vs ConstNodeRef. No semantic changes. This should improve compilation speed of code containing many node calls.
• PR#622 API cleanup: remove preprocess utilities.
• PR#623: YAML fuzzing fixes, and close to 1 billion fuzz runs without any errors. These were the only two problems found:
  • Ensure parse error on multiline keys opening YAML:

    multiline
      key: value

  • Fix parse error on Byte Order Mark opening containers:

    <BOM>- 
      - a
    -

• PR#628: Add serialization fuzzing. Relax c4::atof() / c4::atod(), disable redundant assertions that prevent returning false on bad strings.
• PR#629: int events:
  • Rename to_chars(substr,DataType) to to_str() (the existing c4 overload would always win because it's an int)
  • Do not use c4/bitmask.hpp
• PR#633: improve coverage to ~99.5%:
  • Add tests to cover missed lines
  • Change some errors to assertions; those errors are caught before calling.
  • Tree and NodeRef: deprecate .type_str(). Use .type().type_str()
  • Tools: add ints parsing to ryml-emit-parse
• PR#634: int events: add sample containing ints-only library
• PR#590: minor: prefer calling some predicates from NodeType

Thanks

• @​uilianries

v0.15.2: Release 0.15.2

Compare Source

See the Doxygen version of this changelog, which links any symbols mentioned here.

• Workaround for Doxygen changelog (use of HTML anchors in .md: doxy 1.15 fails but 1.16 succeeds).

v0.15.1: Release 0.15.1

Compare Source

See the Doxygen version of this changelog, which links the symbols mentioned here.

• PR#618:
  • JSON emitter now adheres to flow style customization from PR#615
  • JSON emitter now tolerates YAML streams (ie a seq of docs), and emits these as a top-level seq. The old behavior of throwing an error on streams can be obtained by using the new option EmitOptions::json_err_on_stream().
  • Fix error in EmitOptions where EmitOptions::emit_nonroot_dash() had the same effect as EmitOptions::json_err_on_tag().

v0.15.0: Release 0.15.0

Compare Source

See the Doxygen version of this changelog, which links the symbols mentioned here.

• PR#615: add flow style customization:
  • Add NodeType_e::FLOW_SPC to force space after comma in flow style containers:

    Tree tree = parse_in_arena("[0,1,2,3,4,5,6]");
    CHECK(emitrs_yaml<std::string>(tree), "[0,1,2,3,4,5,6]");
    tree.rootref().set_container_style(FLOW_SL|FLOW_SPC); // add spaces
    CHECK(emitrs_yaml<std::string>(tree), "[0, 1, 2, 3, 4, 5, 6]");

  • Add FLOW_MLN (flow multiline, multi-values per line, wrapped at max columns). The old FLOW_ML was deprecated, and is now known as FLOW_ML1 (flow multiline, 1 value per line):

    tree.rootref().set_container_style(FLOW_ML1);
    CHECK(emitrs_yaml<std::string>(tree),
          "[\n"
          "  0,\n"
          "  1,\n"
          "  2,\n"
          "  3,\n"
          "  4,\n"
          "  5,\n"
          "  6\n"
          "]\n");
    tree.rootref().set_container_style(FLOW_MLN);
    CHECK(emitrs_yaml<std::string>(tree),
          "[\n"
          "  0,1,2,3,4,5,6\n"
          "]\n");

  • Add FLOW_MLX mask to match both FLOW_ML1 and FLOW_MLN
  • Add EmitOptions::max_cols() to control wrapping of FLOW_MLN:

    CHECK(emitrs_yaml<std::string>(tree, EmitOptions{}.max_cols(8)),
          "[\n"
          "  0,1,2,\n"
          "  3,4,5,\n"
          "  6\n"
          "]\n");

  • Add EmitOptions::force_flow_spc() to override all per-node settings of FLOW_SPC when emitting:

    CHECK(emitrs_yaml<std::string>(tree, EmitOptions{}.force_flow_spc(true)),
          "[\n"
          "  0, 1, 2, 3, 4, 5, 6\n"
          "]\n");

  • Add ParserOptions::flow_ml_style() to choose the multiline flow style to assign while parsing. The default value is still FLOW_ML1 (the old behavior), but this option allows picking any of FLOW_MLN or FLOW_ML1.
  • See sample_style_flow_formatting() in the quickstart for more info.

v0.14.0: Release 0.14.0

Compare Source

• PR#607: add file utilities:
  • file_put_contents()
  • file_get_contents()
  • stdin_get_contents()
• PR#609: fix misbuild in gcc 16.
• PR#610: fix clang warnings: -Weverything. Thanks @​TedLyngmo !
• PR#613: fix #​612: parse error on whitespace-only after block scalar indicators | or >:

  space after: >\space
  tag after: >\t

• PR#614 improve base64 serialization facilities:

  std::string decoded;
  tree["node"] >> fmt::base64(decoded); // now possible
  // also can now obtain the size explicitly:
  substr buf = ...;
  size_t required = 0;
  tree["node"] >> fmt::base64(buf, &required);

• Update c4core to 0.4.0.

Thanks

• @​TedLyngmo

v0.13.0: Release 0.13.0

Compare Source

• PR#606: scalar style utilities now are specific to flow/block mode. This enables stable-style roundtrips of block-mode plain scalars with characters invalid in flow mode:

  # these scalars were previously emitted as single-quoted style
  # because they were conservatively assumed to be in flow mode.
  - doe: a deer, a female deer
  - (10,11)
  - also scalars containing [] and {}

  • scalar_style_choose() was split into scalar_style_choose_{flow,block}()
  • scalar_style_query_plain() was split into scalar_style_query_plain_{flow,block}()
  • NodeType::type_str(NodeType,flags): remove zero-termination, use common approach of returning required size
  • Add NodeType::type_str_sub()
• PR#605: fix parse errors:
  • : and # on continuation lines of multiline plain scalars:

    [plain
     :scalar] # leading colon belongs to the scalar

  • Tabs inside quoted scalars opening a map were mistook for indentation tabs:

    foo:
      '\ta': b

• PR#604: add string_view and span to the c4/yml/std/std.hpp interop umbrella header.
• Fix 600: shared symbols not exported in clang on Windows (PR#601).
• Fix 256: installation directory on Linux 64bit (PR#599). See also original fix at cmake#16. Big thanks to @​GabrielBarrantes and @​musicinmybrain, not just for their fixes but also for all their downstream work!
• PR#591: Add missing includes to avoid compilation warning. Thanks @​GabrielBarrantes!
• Update c4core to 0.3.0.

Thanks

• @​GabrielBarrantes
• @​musicinmybrain

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[ankoh]

@copilot fix this:

WARNING: Download from https://github.com/biojppm/rapidyaml/archive/refs/tags/v0.13.0.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.UnrecoverableHttpException Checksum was 4129525f52fa05c03404d665cf3ee28ef1cbb1e590ba8bcedbd8f31d4869aadf but wanted a0d8e81657f773cc6d906308f88c04dfe3f275ed038609edbb5bd624ee954e9f
INFO: Repo +dashql_core_dependencies+rapidyaml defined by rule http_archive in @@bazel_tools//tools/build_defs/repo:http.bzl
ERROR: /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:200:45: An error occurred during the fetch of repository '+dashql_core_dependencies+rapidyaml':
   Traceback (most recent call last):
	File "/home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl", line 200, column 45, in _http_archive_impl
		download_info = ctx.download_and_extract(
Error in download_and_extract: java.io.IOException: Error downloading [https://github.com/biojppm/rapidyaml/archive/refs/tags/v0.13.0.zip] to /home/runner/.bazel/external/+dashql_core_dependencies+rapidyaml/temp7646181790919435479/v0.13.0.zip: Checksum was 4129525f52fa05c03404d665cf3ee28ef1cbb1e590ba8bcedbd8f31d4869aadf but wanted a0d8e81657f773cc6d906308f88c04dfe3f275ed038609edbb5bd624ee954e9f
Analyzing: 101 targets (47 packages loaded, 2947 targets configured)
[13 / 13] no actions running
ERROR: no such package '@@+dashql_core_dependencies+rapidyaml//': java.io.IOException: Error downloading [https://github.com/biojppm/rapidyaml/archive/refs/tags/v0.13.0.zip] to /home/runner/.bazel/external/+dashql_core_dependencies+rapidyaml/temp7646181790919435479/v0.13.0.zip: Checksum was 4129525f52fa05c03404d665cf3ee28ef1cbb1e590ba8bcedbd8f31d4869aadf but wanted a0d8e81657f773cc6d906308f88c04dfe3f275ed038609edbb5bd624ee954e9f
ERROR: /home/runner/work/dashql/dashql/pa

[Copilot]

@copilot fix this:

WARNING: Download from https://github.com/biojppm/rapidyaml/archive/refs/tags/v0.13.0.zip failed: class com.google.devtools.build.lib.bazel.repository.downloader.Unrecoverabl...

Fixed in commit 7cd1a9d: updated bazel/core_dependencies.bzl with the correct rapidyaml v0.13.0 SHA256 (4129525f52fa05c03404d665cf3ee28ef1cbb1e590ba8bcedbd8f31d4869aadf) that CI reported, so the http_archive fetch checksum now matches.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• releases.bazel.build
  • Triggering command: /usr/local/lib/node_modules/@bazel/bazelisk/bazelisk-linux_amd64 /usr/local/lib/node_modules/@bazel/bazelisk/bazelisk-linux_amd64 build //packages/dashql-core:test_utils (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[ankoh]

Seems like rapidyaml changed something for string literals:

 parser-errors:
-  - message: syntax error, unexpected RRB
+  - message: 'syntax error, unexpected RRB'
     text: ")"
-  - message: syntax error, unexpected EOF
+  - message: 'syntax error, unexpected EOF'
     text: ""
 line-breaks:

)
Expected: true

[  FAILED  ] Regression/ParserSnapshotTestSuite.Test/error_recovery_wrong_leak_assertion, where GetParam() = 0x56366f2ab490 (0 ms)
[----------] 3 tests from Regression/ParserSnapshotTestSuite (0 ms total)

[----------] 4 tests from Dots/ParserSnapshotTestSuite
[ RUN      ] Dots/ParserSnapshotTestSuite.Test/dot_test_space_ident
[       OK ] Dots/ParserSnapshotTestSuite.Test/dot_test_space_ident (0 ms)
[ RUN      ] Dots/ParserSnapshotTestSuite.Test/dot_test_space_keyword
[       OK ] Dots/ParserSnapshotTestSuite.Test/dot_test_space_keyword (0 ms)
[ RUN      ] Dots/ParserSnapshotTestSuite.Test/dot_test_eof
[       OK ] Dots/ParserSnapshotTestSuite.Test/dot_test_eof (0 ms)
[ RUN      ] Dots/ParserSnapshotTestSuite.Test/dot_where_recovery
[       OK ] Dots/ParserSnapshotTestSuite.Test/dot_where_recovery (0 ms)
[----------] 4 tests from Dots/ParserSnapshotTestSuite (0 ms total)

[----------] 3 tests from Set/ParserSnapshotTestSuite
[ RUN      ] Set/ParserSnapshotTestSuite.Test/set_1
[       OK ] Set/ParserSnapshotTestSuite.Test/set_1 (0 ms)
[ RUN      ] Set/ParserSnapshotTestSuite.Test/set_2
[       OK ] Set/ParserSnapshotTestSuite.Test/set_2 (0 ms)
[ RUN      ] Set/ParserSnapshotTestSuite.Test/set_3
[       OK ] Set/ParserSnapshotTestSuite.Test/set_3 (0 ms)
[----------] 3 tests from Set/ParserSnapshotTestSuite (0 ms total)

[----------] 23 tests from VisStatement/ParserSnapshotTestSuite
[ RUN      ] VisStatement/ParserSnapshotTestSuite.Test/vis_statement_visualise_empty
packages/dashql-core/test/parser_snapshot_test_suite.cc:27: Failure
Value of: MatchesContent(out_tree.rootref(), expected_node)
  Actual: false (
HAVE
----------------------------------------
statements: []
scanner-errors: []
parser-errors:
  - message: syntax error, unexpected SEMICOLON
    text: ";"
line-breaks: []
comments: []

EXPECTED
----------------------------------------
statements: []
scanner-errors: []
parser-errors:
  - message: 'syntax error, unexpected SEMICOLON'
    text: ";"
line-breaks: []
comments: []

@@ -2,5 +2,5 @@
 scanner-errors: []
 parser-errors:
-  - message: syntax error, unexpected SEMICOLON
+  - message: 'syntax error, unexpected SEMICOLON'
     text: ";"
 line-breaks: []

)
Expected: true

[  FAILED  ] VisStatement/ParserSnapshotTestSuite.Test/vis_statement_visualise_empty, where GetParam() = 0x56366f42e480 (0 ms)
[ RUN      ] VisStatement/ParserSnapshotTestSuite.Test/vis_statement_visualize_empty
packages/dashql-core/test/parser_snapshot_test_suite.cc:27: Failure
Value of: MatchesContent(out_tree.rootref(), expected_node)
  Actual: false (
HAVE
----------------------------------------
statements: []
scanner-errors: []
parser-errors:
  - message: syntax error, unexpected SEMICOLON
    text: ";"
line-breaks: []
comments: []

EXPECTED
----------------------------------------
statements: []
scanner-errors: []
parser-errors:
  - message: 'syntax error, unexpected SEMICOLON'
    text: ";"
line-breaks: []
comments: []

@@ -2,5 +2,5 @@
 scanner-errors: []
 parser-errors:
-  - message: syntax error, unexpected SEMICOLON
+  - message: 'syntax error, unexpected SEMICOLON'
     text: ";"
 line-breaks: []

)
Expected: true

@copilot Check and fix

[Copilot]

Seems like rapidyaml changed something for string literals:

...

Fixed in 16b380f. I updated EncodeError() in packages/dashql-core/src/testing/yaml_tests.cc to force single-quoted YAML style for message, so parser/scanner error snapshots stay stable with rapidyaml 0.13.0 (message: '...' as expected).

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• releases.bazel.build
  • Triggering command: /usr/local/lib/node_modules/@bazel/bazelisk/bazelisk-linux_amd64 /usr/local/lib/node_modules/@bazel/bazelisk/bazelisk-linux_amd64 test --test_output=errors //packages/dashql-core:parser_tests (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)