GSOC 2026 -Pranjal Manhgaye

Pranjal_Manhgaye · March 8, 2026, 1:11pm

Hi @Makis @fsimonis, here’s a quick update on my recent contributions.

Merged PRs (merged) :

Fix precommit hooks by PranjalManhgaye · Pull Request #725 · precice/tutorials · GitHub (system test)

Make clean-tutorial.sh executable from any directory by PranjalManhgaye · Pull Request #716 · precice/tutorials · GitHub (system test)

Fix system test counter to start from 1 instead of 0 by PranjalManhgaye · Pull Request #715 · precice/tutorials · GitHub (system test)

Open PRs (IMPORTANT) :

Archive and compare iterations.log for implicit coupling (fixes #440) by PranjalManhgaye · Pull Request #743 · precice/tutorials · GitHub (system test)

Archive fieldcompare diff files in diff-results/ on failure (fixes #441) by PranjalManhgaye · Pull Request #740 · precice/tutorials · GitHub Archive fieldcompare diff files in diff-results/ on failure (fixes #441) (system test)
feat(systemtests): add per-test max_time override for precice-config closes#402 by PranjalManhgaye · Pull Request #738 · precice/tutorials · GitHub (system test)

Gate gather-refs on trigger-system-tests label in PR workflow by PranjalManhgaye · Pull Request #733 · precice/tutorials · GitHub (system test)

Source test cases from other repositories (Closes #538) by PranjalManhgaye · Pull Request #732 · precice/tutorials · GitHub (system test)

Simplify mapping sanity checks in ParticipantConfiguration by PranjalManhgaye · Pull Request #2486 · precice/precice · GitHub

github.com/precice/precice

Improve XML missing-attribute error context closes(#2441) (#2478)

develop ← PranjalManhgaye:develop

opened 07:19AM - 03 Mar 26 UTC

PranjalManhgaye

+29 -12

## Main changes of this PR - **include tag name in required-attribute errors*…*: extend `precice::xml::XMLAttribute::readValue` to take the tag name and use it when reporting missing required attributes. - **Wire tag context through `XMLTag`**: update `precice::xml::XMLTag::readAttributes` to pass the tag’s `_fullName` to all attributes so error messages can mention the concrete tag (e.g. `<receive-mesh>`). - **Add regression test**: introduce a minimal XML configuration (`src/xml/tests/config_xmltest_missing_attribute.xml`) and a new unit test `MissingRequiredAttributeIncludesTagName` in `ParserTest.cpp` to verify that missing-attribute errors now include the tag name. ## Motivation and additional information This PR addresses the usability issue described in **#2441 (Missing XML tag context)**. Previously, when a required attribute was missing, preCICE emitted an error like: > `Attribute "from" is required, but was not defined.` While technically correct, this gave no indication of **where** in the XML the problem occurred, which is particularly confusing when a configuration contains multiple tags that accept the same attribute name. With this change, the error includes the tag name, for example: > `The tag <receive-mesh> in the configuration is missing required attribute "from".` This makes it much easier for users to locate and fix configuration mistakes, and is consistent with other XML configuration errors that already include tag context (e.g. for unknown attributes). The change is implemented in a generic way, so all missing-required-attribute errors now include their tag name, not just `<receive-mesh>`. The new unit test ensures that this behavior stays stable. ## Author's checklist * [ ] I used the [`pre-commit` hook](https://precice.org/dev-docs-dev-tooling.html#setting-up-pre-commit) to prevent dirty commits and used `pre-commit run --all` to format old commits. * [ ] I added a changelog file with `make changelog` if there are user-observable changes since the last release. * [x] I added a test to cover the proposed changes in our test suite. * [ ] For breaking changes: I documented the changes in the appropriate [porting guide](https://precice.org/couple-your-code-porting-overview.html). * [x] I stuck to C++17 features. * [x] I stuck to CMake version 3.22.1. * [ ] I squashed / am about to squash all commits that should be seen as one. * [ ] I ran the systemtests by adding the label `trigger-system-tests` (may be skipped if minor change) ## Reviewers' checklist * [ ] Does the changelog entry make sense? Is it formatted correctly? * [ ] Do you understand the code changes?

Would be glad to get your feedback on the open ones, especially the tutorials PRs.
Thanks

Topic		Replies	Views
[GSoC 2026 Introduction] Rajdeep Kushwaha — System Tests Improvements GSoC	0	20	March 1, 2026
GSoC 2026 Introduction \| Bhavana Praneeth GSoC	0	40	February 22, 2026
GSOC 2026 : Kishan Singh \| System Tests Improvements GSoC	2	59	March 2, 2026
Introduction - Interested in system test Improvement project GSoC	0	17	March 9, 2026
GSoC 2026 Applicant – Interested in System Tests Improvements GSoC	0	29	February 22, 2026

GSOC 2026 -Pranjal Manhgaye

Related topics