GitLab

[dataimport] add a filter function to not fail if some extentity has several values for an attribute of final relation

the function will simply record a warning in the import log and keep a value
randomly.

Notice the function has to be explicitly inserted in the transformation stream.

and redirect to the forthcoming import log, for a better user experience (there
is still a lot more to do there though).

Closes #10468967

Let's assume nobody will try upgrading an instance from pre-3.10
cubicweb to 3.23+.  If they do, they're setting themselves up for a lot
of pain anyway.

The merge was clean, just dropped cubicweb/web/data/cubicweb.goa.js.

I don't know what I'm doing, but this seems to work.

Don't use braces for set literals.

[migration] test if entity type has been in  the deleted in the transaction should protect both clauses

else we may attempt to execute the UPDATE query on a table which has been
deleted.

Closes #10692374

as advertized by its help message. This was because "force" argument wasn't
considered by acquire_synchronization_lock().

This avoids calling cubicweb-ctl relatively in tests and could be useful
in virtualenv.

This is just a copy of bin/cubicweb-ctl file, which should probably be
generated from a setuptools entry points.

python is python2 is never >= 3.4.

The index name changed, so we need to follow suit.

This part of commit fdadf59be612 missing the integration window.

The former just works fine now but the later does not play well with py.test.

Generative tests as implemented in logilab.common.testib are not compatible
with tests runner other than lgc.pytest and this implementation differs from
the standard library, which has support for subtests_ since Python 3.4. Use
unittest2 to bridge the gap.

Maybe it'd be good to implement this on logilab.common.testlib side at some
point. Let's see how this gets received here first.

.. _subtests: https://docs.python.org/3/library/unittest.html#subtests

Some programs are in ldap-utils or ldapscripts, which may not be installed
despite slapd may.

Follow-up on 282880f81311.

Looking for VIRTUAL_ENV environment variable as a sign of virtualenv
activation. This at least works for developing CubicWeb itself (not sure yet
about cubes). And it makes `tox --develop` work as well.

Add a test for cwconfig._find_prefix within a virtualenv.

In tox.ini, use `develop option`_ accordingly. This makes tox running
significantly faster since it avoids building and installing the sdist. Aside,
the "develop" install is now performed *after* all test requirements are
processed, which means that the cubicweb package should always be the one from
source -- instead of a released version pulled by a cube through test
dependencies, which may occur in "recreate" step.


.. _`develop option`: <http://tox.readthedocs.org/en/latest/config.html#confval-usedevelop=BOOL