getodk / getodk/validate

Matching nodes bug

Open
#10 0 comments 0 reactions 1 assignee Claimed by @mitchellsundt View on GitHub
bug
Dominant language
Java
Stars
13
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Issue by [mitchellsundt](https://github.com/mitchellsundt)**
_Thursday Jul 09, 2015 at 19:03 GMT_
_Originally opened as https://github.com/opendatakit/opendatakit/issues/692 (0 comment(s))_

----

Originally reported on Google Code with ID 691

```
If you have instance like so..





And some binds like so...



Currently, Validate (or Collect) do not throw up any errors. It is only at runtime
that you know something is wrong -- Collect crashes.

See the problem? There is no /cluster in the instance, only /data. The binds are referring
to nodes that don't exist. I believe earlier versions of Validate caught this matching
nodes problem.
```

Reported by `yanokwa@nafundi.com` on 2012-09-26 17:07:31



- _Attachment: [Matching nodes bug.xml](https://storage.googleapis.com/google-code-attachments/opendatakit/issue-691/comment-0/Matching nodes bug.xml)_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.