We are pleased to announce 11th beta release of SequenceServer 1.1.0. This
release includes many small-small bug fixes and enhancements.
- Display of large results are handled by rendering results of fifty queries at
a time. However, in each cycle of update, instead of focusing only on the
next fifty queries, React would automatically also check if previously
rendered queries needed to be updated as well. This resulted in each cycle of
update to take more and more time. Prevent that by returning false from
shouldComponentUpdate lifecycle method if the query is already rendered.
- Kablammo / graphical HSP overview:
- Reverse order of HSPs for drawing so that the HSP with stronger evalue
are drawn last, and thus end up on top of HSP with weaker evalue if
- Handle hover events more efficiently.
- Copy-pasting hit sequence from sequence viewer should eliminate whitespace
introduced by grouping of residues, but it didn't. So disabled grouping of
residues in sequence viewer so that the sequence can be copy-pasted as it
- SVG and PNG download links would break into two lines on smaller windows.
- Do not change padding when hit is selected. Further, apply orange border
to selected hits only on the left side instead of on all sides.
- Downloading alignments of selected hits wouldn’t work if sequence ids
included a pipe character. Fixed this.
- Last line of the alignment would sometimes not be shown. Fixed that.
- Expanded error handling:
- Inform user if BLAST's XML output is invalid, and suggest deduplicating
sequence ids or rerunning with a single database (issue #194) (credits:
Ben Woodcroft, Tomáš Pluskal, and others).
- Inform user if BLAST ran out of memory and ask to retry with smaller
query. Should be rare, but is good to know when this happens.
- Inform user if SequenceServer doesn't have permission to create job
directory. Should be particularly helpful when setting up with
- Inform user if SequenceServer/BLAST runs out of disk space.
- Inform user if BLAST produced empty output.
- Update Dockerfile so that docker image is built from the source. This
ensures that the tag applied to docker image and software version are
in sync. (credit: Michał T. Lorenc)
- Don't use symlinks inside of the repository as symlinks are not
supported on all platform and can thus cause installation to
- Ensure the new version can be deployed to a suburi.