GitLab

Those are expected to be defined in almost every js files. They were not before
this patch because login form doesn't use the regular main template.

Currently crashed with RequestError: invalid action '__action_cancel'.

It's broken as of https://hg.logilab.org/master/cubicweb/rev/cb217b2b3

This fix is similar as the one done in
https://hg.logilab.org/master/cubicweb/rev/9f1c89e7426d

Closes #13521493

when an unstable variable (ie whose type change from one solution to another) is
used in an EXISTS node but belongs to an outer scope.

Closes #13518646.

Unique was previously detected in a loop triggered only for String columns.

which has been recently broken while some cubes rely on this (eg fastimport).
Do some licensing/pep8 cleanup along the way.

Closes #13385274

but return 'False' instead.

when using (correct login, wrong password) credentials

Closes #12481591.

So that cubes used in test dependencies do not install a released CubicWeb.

cubicweb.wsgi may not be available at all on Debian.

(grafted from 3309ddb97059)

We have some test failures with 16.0.0, such as:

- test_put_content (unittest_server.ETwistHTTPTC)
- test_base_url (unittest_httptest.TwistedCWAnonTC)
(grafted from 10c12f31d0fe)

The response MUST include the following header fields:
[...]
      - ETag and/or Content-Location, if the header would have been sent
        in a 200 response to the same request

https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5

Unfortunately we weren't copying headers from what would have been the
200 response, but from the request.

'Connection' object has no attribute 'HOOKS_DENY_ALL'

When migrating from a pre-3.10 database, the CWSource entity type and
cw_source relation type are not known, but authenticate should still
work to be able to add them.

and so, remove more useless code.

Doing a commit in DataFeedXMLParser.process() is a bad idea because this method
is called for every imported/updated entity, before handling deletions.  So if
we commit here, odds are quite high that we're violating some integrity
constraint and end up with a ValidationError.

Old sqlite3 doesn't provide CHECK constraint names in error messages,
preventing us from translating a backend integrity error into a
ValidationError.  This was added in 2012, but the sqlite3 version in
RHEL6 is older; so if we run on old sqlite, keep checking the
constraints in python rather than only in SQL.

Closes #10927494

The changes from cset 5758ba784ebd "[autoform] when building inlined-form view
for a relation, consider related entities intead of other views" lead to
an unexpected 'add new' link on creation of an entity with inlined form for
a relation of cardinality 1. To avoid this, we should consider formviews and not
existing relations when the entity is being created.

Closes #10860258

So that cubes used in test dependencies do not install a released CubicWeb.