Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 

If you are having a problem with Daffodil, and think that perhaps you have found a bug, then we suggest you:

Details are below.

...

Check JIRA to See if your Issue is Already There

First you should give a search of our JIRA tickets to see if the problem is already recorded.

Here's the front page: https://opensource.ncsa.illinois.edu/jira/browse/DFDLHere's a list a list of all tickets about bugs, new features, and improvements. In , in reverse chronological order (most recent first). You may want to change the issue type, or status specifications to narrow down the list, but most commonly you would just put some search keywords into the search box.

Don't go crazy with this searching however, because if you can't find it with reasonable effort (a few good guesses at search terms), then whatever is there isn't tagged sufficiently anyway.

If you do find a bug or a closely related issue that is open status, then you can add your information to it If you do find a bug or a closely related issue that is open status, then you can add your information to it as a comment if you prefer, rather than creating a new issue. Just knowing that another person has run into the issue is helpful at assigning fix priorities.

If you do not easily find an issue, either create a new JIRA bug, email the issue to daffodil-users@oss.tresys.com, or ask about it in the  Daffodil XMPP Chat Room. Additionally, creating a TDML file can greatly help us reproduce the issue and resolve it.

Create a TDML Create a TDML File that Illustrates the Issue

A TDML file is often useful just to ask a question about how something in DFDL works, for example, to get a clarification. It allows for a level of precision that is often lacking, but also often required when discussing complex data format issues.

The absolutely best way to report a bug is by creating a TDML test file that demonstrates the problem.

...