Skip to content

Error parsing FASTA in multiple passes #659

Closed

Description

@sbliven

Dak reported the following bug on the mailing list:

I have a FASTA file that contain one sequence. I initialized FASTA reader as described in the tutorial, called process() and get one record as expected. However, if I re-initialized another FASTA reader opening the same one-record file, called process(1) and null is returned. If I tried to read two-record FASTA file, the first process(1) works, but not the second call to process(1) return null. Based on a superficial glance, it looks like the if statement at line 194 of FastaReader.java may be the culprit.

@andreasprlic created a branch, https://github.com/biojava/biojava/tree/DakFastaHeader which contains the failing TestFASTAReader.

Activity

  1. psoares commented on Jun 2, 2017

    @psoares
    Contributor

    Looks like a bug introduced a long time ago by #282

  2. added a commit that references this issue on Jul 8, 2017
  3. arojnuckarin commented on Jul 8, 2017

    @arojnuckarin
    Contributor

    Created pull request #687

  4. added a commit that references this issue on Jul 18, 2017
  5. reopened this on Aug 10, 2017
  6. added this to the BioJava 5.0.0 milestone on Aug 10, 2017
  7. lafita commented on Aug 10, 2017

    @lafita
    Member

    Was this completely fixed by #687?

  8. arojnuckarin commented on Nov 29, 2017

    @arojnuckarin
    Contributor

    I recently pulled biojava-core 4.2.9 from maven repo and it looks like this particular bug is still there.
    I was thinking that the since the pull request has been merged, the fix should propagate into maven sooner or later, but it looks like that's not the case.

    Is there something that need to take place before the change can go into the 4.2.x official release? Anything that I need to do?

    Thanks,
    dak

  9. josemduarte commented on Nov 30, 2017

    @josemduarte
    Contributor

    The pull request went into the master branch only and not into the bugfixes-4.2 branch. The fix is already in the 5.0.0-alpha13 release and it will be there also when the final 5.0.0 goes out.

    If you want the fix in the next 4.2.x release, you will need to make a separate pull request for that. You will just need to cherry-pick the appropriate commits. Thanks!

  10. arojnuckarin commented on Nov 30, 2017

    @arojnuckarin
    Contributor
  11. josemduarte commented on Nov 30, 2017

    @josemduarte
    Contributor

    The intention is to release 5.0.0 early next year. Most changes are in the structure module, adapting code that uses the structure module can require some work. For other modules the changes are much less dramatic.

  12. added a commit that references this issue on Dec 12, 2017
  13. josemduarte commented on Dec 12, 2017

    @josemduarte
    Contributor

    @arojnuckarin I've just cherry-picked your fix into the bugfixes-4.2 branch. I'm going to release a new bugfix version in the next days.

  14. josemduarte commented on Mar 7, 2018

    @josemduarte
    Contributor

    Reading the above, it looks that this is fixed. Closing. If you know otherwise please reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugBugs and bugfixes

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions