maliput / maliput/maliput_malidrive
Allow predecessor / successor inconsistencies in permissive mode
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
RoadRunner may export .xodr maps with successor / predecessor inconsistencies. Currently, the builder will crash with the following error:
terminate called after throwing an instance of 'maliput::common::assertion_error'
what(): db_manager.cc:VerifyLinkingIsReciprocal:430: JunctionId: 106 is different from -1
See this Slack post. Let's allow for this type of inconsistency when the builder is set to permissive mode.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by locating the builder's permissive-mode handling and VerifyLinkingIsReciprocal in db_manager.cc, then reproduce the reported successor/predecessor inconsistency. Done means permissive mode builds the map without this assertion while strict-mode validation remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100