Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge v0.11.0 into develop #1052

Merged
merged 28 commits into from
Jan 16, 2018
Merged

Merge v0.11.0 into develop #1052

merged 28 commits into from
Jan 16, 2018

Conversation

ltalirz
Copy link
Member

@ltalirz ltalirz commented Jan 16, 2018

No description provided.

giovannipizzi and others added 28 commits January 12, 2018 12:23
Also removing old docs that was a workaround to make sure
one used RSA instead of ECDSA.
…_for_ecdsa

Fix 1036 paramiko upgrade for ecdsa
The bare print messages would be picked up by the celery worker that
was running the task and wrap them in a log message with a level of
WARNING. This made grepping the log output for WARNINGS cluttered
with false positives. Replacing them by info logs to a child logger
of the AiiDA logger, will have these show up as proper log messages
…ements

Replace print statements with log messages in daemon tasks
To correct the appearance of line numbers in the documentation I
updated the sphinx_rtd_theme to the latest version (0.2.5b2). The bug
was fixed in the version 0.2.5b1
add subcommand tab completion for data plugin commands
There is an issue with loading an old-style workflow through the
plugin system with the WorkflowFactory. There is a check in the
constructor of the Workflow class, that will check whether the
class is located in the 'aiida.workflows' module:

if caller_module == None or not caller_module.__name__.startswith("aiida.workflows"):
    raise SystemError("The superclass can't be called directly")

The whole point of the plugin system is of course that subclasses
do not necessarily have to live in that module. Rather than removing
the conditional, we chose to leave it and not support old-style
workflows for the new plugin system. Since they will be soon deprecated
and no longer maintainted, doing so would give the wrong signal.

Rather, we add a note to the developer documentation in the plugin
system section, that old-style workflows are not supported
Docs addition: old-style workflows not supported by plugin system
The async function relied on the ParallelEngine of plum to
launch multiple processes in parallel, however, during testing
we discovered that the orm is not thread safe and race conditions
could lead to unexpected behavior. The future version of plum
that is currently in development for the renewed workflow engine
will not support this for this reason. Therefore we remove this
function here altogether in preparation for the improved workchain
engine.
Remove the async function from aiida.work.run
…dthedocs

Update sphinx_rtd_theme to 0.2.5b2 to fix line numbers of code snippets in docs
In a recent update, various buggy methods of the KpointsData class were
deprecated. The deprecated interface would raise a ValueError if the
set_kpoints_path would be called before a cell had been set, however,
the deprecated methods used to allow for this, as long as the provided
list used explicit reciprocal coordinates and cartesion mode was False.
Always raising when a cell was not defined was therefore breaking backwards
compatibility.

To restore this behavior, we now pass cell=None when it is not set, to the
legacy version of the get_explicit_kpoints_path method. This also required
some minor changes to the helper function analyze_cell

A regression test was added to verify that the old behavior was successfully
restored through these changes
…ards_compatibility

Allow deprecated set_kpoints_path of KpointsData without cell
 * ran helper scripts
 * update AUTHORS.txt
 * checked that CHANGELOG.md is up to date
 * update version number in aiida/__init__.py
Merge release v0.11.0 into master
@ltalirz ltalirz requested a review from sphuber January 16, 2018 14:14
@ltalirz ltalirz merged commit ec93d99 into develop Jan 16, 2018
@ltalirz ltalirz deleted the merge_v0.11.0_into_develop branch January 16, 2018 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants