GitLab

As we changed the minimal length we need to have passwords of that length (even for the tests)

As users will be able to modify their own password, we need to give a limit on the minimal password length

Fixes #1682

This is more flexible to add new errors.

We don't store specific rights for modifying user yet.
For now we can only modify our own account (or all accounts
if the person is admin)

See #3913

Fix vdj#880

See previous commit for more information

We add a new field to the results_file stating that they can be hidden.
This means that those results shouldn't appear in the last processed
results. They should not be taken into consideration when fusing results.
They should not be proposed when comparing results.

A first example of those hidden results is when we launch a grep reads.
This is just a process launched behind the scene that should not be
made explicit to the user.

Fix #3899

The parameter can be a dictionary when the dictionary has a success and message key.

We can have a debug output but being in this function is not an error.
Moreover we can't pass a dictionary to the log.

It is useful for the checkProcess function in database.js
Related to #1469

When a process is finished we need to access its result. Thus we provide the result ID.
Related to #1469

Fix #3733

However we pay attention that no one is trying to access a file in a parent directory

In this way it can be used by any controller not just results_file.py

It is required in the remaining of the function

-i was removed in 09f51300, more than two years ago.
Opens #3790.

See #3785.

Follows a first attempt by @flothoni.
Closes #2726

Passing request.vars['samples_id'] as record_id caused some issues when several samples
were contained in the same sample set as the samples_id were separataed with commas, while
we expect a single ID.

See vdj#792

cell or cells exists on TableRow but parent just returns an Element.
Therefore we find another way of having the same behaviour.

Otherwise we get a deprecate warning as the table has changed
since it was retrieved.
See e.g. https://groups.google.com/forum/#!topic/watir-general/rM3LZl9WzKw

Don't know how this could work previously

Use latest Ruby version and Watir instead of watir-webdriver.
This will make it easier to install it on recent OS and it
will also allow us to test on recent Firefox versions.

Some changes in the syntax:
- visible? is deprecated → present?
- wait_until_* are deprecated → wait_until(&: *)
- some way of specifying timeouts

Watir also seems to be quicker thus the need to add
some waits or some sleeps

#3607 should be solved first.

When editing we add an existing tag and we check that we recover it properly.

Now testEditForm() is necessarily called first which modifies the entry
we created tags for.
Thus we should not find those tags anymore

Files can be loaded in any order depending on how glob traverses the directories.
We now sort the files first to have a reproducible order.

Fixes #3682

See #3076

include missing boolean functions in boolean expression
See #3619