GitLab

The former would select any Python 3 interpreter.

Previous patches fixed new errors raised in this version.

Also refactor a bit the method to restrict the try/except block to the
code for which we actually want to catch an exception (i.e. the
cnx.execute() + cnx.commit()).

This function is aliased to datetime.datetime.strptime() and exists only
for compatibility with Python <= 2.5 which we no longer support.

This error is about "l" being an ambiguous variable name. Here, it's
arguably acceptable.

This is an error (E741) from flake8 3.5.

to follow the new style layout of cubes among others.

Previously, we raised a plain RemoteCallFailed without a status code, in which
case it defaults to "500 Internal Server Error". Now, for validation
errors, we issue a 400 Bad Request since these are clearly client errors.

We currently have CI failures because cubes used as test dependencies have been
updated to new-style cube layout. To avoid this, pin them to previous released.

Those dependencies should be removed but in the mean time this should be enough
(and backported in all active branches).

--HG--
branch : 3.25

--HG--
branch : 3.25

--HG--
branch : 3.25

--HG--
branch : 3.25

--HG--
branch : 3.25

The "pyramid" instance configuration does not work with "cubiwceb.bwcompat"
mode (on purpose). Yet, having the setting exposed in development.ini file
(generate by `cubicweb-ctl create --config pyramid <cube> <instance>` command)
is misleading and we want to remove it.

Thus, we only query this setting when cubicweb configuration is "all-in-one" and
drop the setting line from templated development.ini file. If the option is
found and True for any other configuration type, we issue a user warning (and
ignore the option).

--HG--
branch : 3.25

For very old instances (namely docaster), this table has never been created.

--HG--
branch : 3.25

Iterate over relations type in alphabetical order, so the order is predictible
dans does not depend on PYTHONHASHSEED.

--HG--
branch : 3.25

which is because facets are replacing the whole #pageContent div, while this one
contains other stuff than the view:

* a type selector component that should be dropped for a while,
* a computed title,
* the page navigation.

Then the view content itself is in a #contentmain div. The thing is that the
navigation should be rebuilded on filtering (this is not the case for other
bullets in the list above). This is currently handled specifically in the
ajaxcontroller (except for the type selector which will disappear... who said it
should be dropped at once?).

So to fix this we:

* put the page navigation into the "contentmain" div
* don't replace anymore "pageContent" but "contentmain"

After that we can even remove from the ajax controller the code that
reimplements title handling similarly to the main template.

Notice the part that changes the main template has to be ported to squareui.

Closes #17074195

When this is clearly a client error, set status to 400. Otherwise, keep the
default value for RemoteCallFailed (status=500).

When we raise a RemoteCallFailed error (erroneously turned into a '500
Internal Server Error' response, but that's another business). In production
environment, we do not want to log the exception in most cases where it's
actually a client error. So only log the exception in debug mode.

When filtering on a relation, find() was generating rql like
'Any X WHERE X is ETYPE, X relation EID' which work without being rewritten (it
should probably not), but when applying some rewrite (eg. permissions) it raise
in rqlrewrite code.

	def _use_orig_term(self, snippet_varname, term):
			...
	>       self.rewritten[key] = term.name
	E       AttributeError: 'Constant' object has no attribute 'name'


Generate valid rql instead 'Any X WHERE X is ETYPE, X relation Y, Y eid EID'.

For readability, avoid escaping using %% and use format() instead.

Display what attribute trigger the NotImplementedError

actually not necessary.

hard one!

We actually want one only if this is not a (`And` / `Or`) binary tree of `Not` or
`Exists` nodes, so write a recursive function to tell so.

Related to #17074119

When some inserted RQL snippet generate more solutions than the original RQL,
the rewriter attempt to duplicate the snippet for each newly introduced
solution. There are though some cases where we do not want this behaviour in
case of ambiguities introduced by:

* NOT(X relation Y) expression, since it won't be
  equivalent to NOT(X relation Y1, Y1 is Type1) OR NOT(X relation Y2, Y2 is
  Type2) ;

* EXISTS(X relation Y, Y is IN (Type1, Type2) expression, since it's not
  actually necessary to split an explicitly introduced ambiguity (and it crash
  if we attempt to do so, so...).

In test, we've to modify the `rewrite()` function because in the newly
introduced test we need the same constraint to be applied to two variables in
the original query, and this was not supported before.

Notice the generated RQL in test is still *NOT CORRECT* "(EXISTS(NOT EXISTS() OR
EXISTS(...))", or at least isn't optimal. This will be fixed in a forthcoming
changeset.

Related to #17074119

--HG--
branch : 3.25

By default after the import processed the importer indicates which external
entities can't be inserted because they are missing dependency data (other
entities, used in inlined or mandatory relations).

It usually helps there to find out which extids / relations are missing, so add
this to the log.