Testando pip+debugprov no linux com conda

(base) romer@romer-Z550MA:~/ic/est_fork1$ python scrap.py venv
***************
Comecei usando o venv, mas ele fez uma bagunça nas minhas dependências e ficava exigindo o sudo para qualquer coisa que achei mais vantajoso voltar para o conhecido conda.
***************
(base) romer@romer-Z550MA:~/ic/est_fork1$ python scrap.py venv
******************************************************************************************************************************************************
Comecei usando o venv, mas ele fez uma bagunça nas minhas dependências e ficava exigindo o sudo para qualquer coisa que achei mais vantajoso voltar para o conhecido conda.
******************************************************************************************************************************************************

(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ python scrap.py now1
************************************************************

		    Agora parece que roda o noworkflow
		    sem grandes problemas,

************************************************************
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ now run shide.py 9
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.trial_id to column activation.trial_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.trial_id to activation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.id to column activation.code_block_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.id to activation.code_block_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Activation.evaluations' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Activation.evaluations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.activation' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Evaluation.activation' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.id to column dependency.dependency_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.id to dependency.dependency_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.activation_id to column dependency.dependency_activation_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.activation_id to dependency.dependency_activation_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.trial_id to column dependency.trial_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.trial_id to dependency.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Trial.arguments' will copy column trial.id to column argument.trial_id, which conflicts with relationship(s): 'Argument.trial' (copies trial.id to argument.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="trial"' to the 'Trial.arguments' relationship.
  session.query(cls.m)
9 False
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ now run stoolkit 917
usage: now run [-b] [-d DEPTH] [-c {main,package,all}] [-s SAVE_FREQUENCY]
               [-S CALL_STORAGE_FREQUENCY] [-h] [--name NAME] [--dir DIR] [-v]
               [--message MESSAGE] [--content-engine CONTENT_ENGINE]
               ...
now run: error: argument script: can't open file 'stoolkit': [Errno 2] No such file or directory
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ now run stoolkit.py 917
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.trial_id to column activation.trial_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.trial_id to activation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.id to column activation.code_block_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.id to activation.code_block_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Activation.evaluations' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Activation.evaluations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.activation' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Evaluation.activation' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.id to column dependency.dependency_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.id to dependency.dependency_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.activation_id to column dependency.dependency_activation_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.activation_id to dependency.dependency_activation_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.trial_id to column dependency.trial_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.trial_id to dependency.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Trial.arguments' will copy column trial.id to column argument.trial_id, which conflicts with relationship(s): 'Argument.trial' (copies trial.id to argument.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="trial"' to the 'Trial.arguments' relationship.
  session.query(cls.m)
917 False
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ now run spure.py 917
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.trial_id to column activation.trial_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.trial_id to activation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.id to column activation.code_block_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.id to activation.code_block_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Activation.evaluations' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Activation.evaluations' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.activation' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Evaluation.activation' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.id to column dependency.dependency_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.id to dependency.dependency_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.activation_id to column dependency.dependency_activation_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.activation_id to dependency.dependency_activation_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.trial_id to column dependency.trial_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.trial_id to dependency.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  session.query(cls.m)
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/head.py:87: SAWarning: relationship 'Trial.arguments' will copy column trial.id to column argument.trial_id, which conflicts with relationship(s): 'Argument.trial' (copies trial.id to argument.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="trial"' to the 'Trial.arguments' relationship.
  session.query(cls.m)
917 False
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ python scrap.py now2
************************************************************

		   Exceto por essa verbosidade caracte-
		   rística, é claro.

************************************************************
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ now list
[now] trials available in the provenance store:
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.trial_id to column activation.trial_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.trial_id to activation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  return proxy_gen(session.query(cls.m))
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'CodeBlock.activations' will copy column code_block.id to column activation.code_block_id, which conflicts with relationship(s): 'Activation.code_block' (copies code_block.id to activation.code_block_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="code_block"' to the 'CodeBlock.activations' relationship.
  return proxy_gen(session.query(cls.m))
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'Activation.evaluations' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Activation.evaluations' relationship.
  return proxy_gen(session.query(cls.m))
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'Evaluation.activation' will copy column activation.trial_id to column evaluation.trial_id, which conflicts with relationship(s): 'Activation.this_evaluation' (copies activation.trial_id to evaluation.trial_id), 'Evaluation.this_activation' (copies activation.trial_id to evaluation.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="this_activation,this_evaluation"' to the 'Evaluation.activation' relationship.
  return proxy_gen(session.query(cls.m))
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.id to column dependency.dependency_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.id to dependency.dependency_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  return proxy_gen(session.query(cls.m))
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.activation_id to column dependency.dependency_activation_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.activation_id to dependency.dependency_activation_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  return proxy_gen(session.query(cls.m))
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'Evaluation.dependencies_as_dependency' will copy column evaluation.trial_id to column dependency.trial_id, which conflicts with relationship(s): 'Dependency.dependency' (copies evaluation.trial_id to dependency.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="dependency"' to the 'Evaluation.dependencies_as_dependency' relationship.
  return proxy_gen(session.query(cls.m))
/usr/local/lib/python3.8/dist-packages/noworkflow-2.0.0a0-py3.8.egg/noworkflow/now/persistence/models/base.py:272: SAWarning: relationship 'Trial.arguments' will copy column trial.id to column argument.trial_id, which conflicts with relationship(s): 'Argument.trial' (copies trial.id to argument.trial_id). If this is not the intention, consider if these relationships should be linked with back_populates, or if viewonly=True should be applied to one or more if they are read-only. For the less common case that foreign key constraints are partially overlapping, the orm.foreign() annotation can be used to isolate the columns that should be written towards.   To silence this warning, add the parameter 'overlaps="trial"' to the 'Trial.arguments' relationship.
  return proxy_gen(session.query(cls.m))
  [*]Trial 1: run stoolkit.py 7 13
              with code hash 872544e66e9d04067c379838e85c1472c1805059
              ran from 2021-09-03 03:26:02.304748 to 2021-09-03 03:26:25.501247
              duration: 0:00:23.196499
  [*]Trial 2: run shide.py 9
              with code hash b30d514d02d1e8ac89806a3c3a94edbd81282938
              ran from 2021-09-03 03:45:32.048183 to 2021-09-03 03:45:52.252056
              duration: 0:00:20.203873
  [*]Trial 3: run stoolkit.py 917
              with code hash 872544e66e9d04067c379838e85c1472c1805059
              ran from 2021-09-03 03:47:10.848252 to 2021-09-03 03:47:24.253637
              duration: 0:00:13.405385
  [*]Trial 4: run spure.py 917
              with code hash cd08b5a4a55d5dc38c859899ea80ac0e934efe38
              ran from 2021-09-03 03:47:38.963359 to 2021-09-03 03:47:41.105236
              duration: 0:00:02.141877
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ python scrap.py clear
************************************************************

		    No linux ele não crasha se você não
		    apagar o .noworkflow anterior, mas
		    ele não reconhece o novo.
		    Agora, por exemplo, ele depurará o script
		    errado, ao invés do solicitado. Depois
		    disso apagaremos com um
			"rm -r .noworkflow"
		    Além do mais, parece que minha solução
		    para o clear não funcionou no linux.

************************************************************
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ python find_state.py RR
Roraima
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ more find_state.py
import sys
import json

def find(state):
	with open('estados.json') as json_file:
		data = json.load(json_file)
	for key in data:
		if key.get('sigla') == state:
			return key.get('nome')
	return "Not Found"

print(find(sys.argv[-1]))
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ debugprov find_state.py RR
Roraima

Traceback (most recent call last):
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/main.py", line 8, in main
    ConsoleInterface().run()
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/console_interface.py", line 92, in run
    exec_tree = creator.create_exec_tree()
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/execution_tree_creator.py", line 15, in create_exec_tree
    root_node = self.get_root()
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/execution_tree_creator.py", line 24, in get_root
    raise ValueError(
ValueError: ValueError: Something wrong in database. 25 root nodes found
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ python scrap.py clear2
************************************************************
Parece que o debugprov mudou de opinião quanto a isso
************************************************************
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ rm -r .noworkflow
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ debugprov find_state.py RR
Roraima

Choose a navigation strategy:
[1] - SingleStepping
[2] - TopDown
[3] - HeaviestFirst
[4] - DivideAndQuery
> 1
Do you want to use provenance enhancement?  (y/n) n
-------------------------
Evaluating node 23 open('estados.json')
Parameters: name | value
 'estados.json' | 'estados.json'
 json_file | <_io.TextIOWrapper name='estados.json' mode='r' encoding='UTF-8'>
Returns: <_io.TextIOWrapper name='estados.json' mode='r' encoding='UTF-8'>
Is correct?  (y/n) y
-------------------------
Evaluating node 29 json.load(json_file)
Parameters: name | value
 json_file | <_io.TextIOWrapper name='estados.json' mode='r' encoding='UTF-8'>
Returns: [{'sigla': 'AC', 'nome': 'Acre', 'cidades': ['Acrelândia', 'Assis Brasil', 'Brasiléia', 'Bujari', 'Capixaba', 'Cruzeiro do Sul', 'Epitaciolândia', 'Feijó', 'Jordão', 'Mâncio Lima', 'Manoel Urbano', 'Marechal Thaumaturgo', 'Plácido de Castro', 'Porto Acre', 'Porto Walter', 'Rio Branco', 'Rodrigues Alves', 'Santa Rosa do Purus', 'Sena Madureira', 'Senador Guiomard', 'Tarauacá', 'Xapuri']},
...

{'sigla': 'TO', 'nome': 'Tocantins', 'cidades': 'São Sebastião do Tocantins', 'São Valério', 'Silvanópolis', 'Sítio Novo do Tocantins', 'Sucupira', 'Taguatinga', 'Taipas do Tocantins', 'Talismã', 'Tocantínia', 'Tocantinópolis', 'Tupirama', 'Tupiratins', 'Wanderlândia', 'Xambioá']}]
Is correct?  (y/n) n
Output file name: exec_tree
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ debugprov spure.py 13
13 True

Traceback (most recent call last):
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/main.py", line 8, in main
    ConsoleInterface().run()
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/console_interface.py", line 92, in run
    exec_tree = creator.create_exec_tree()
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/execution_tree_creator.py", line 15, in create_exec_tree
    root_node = self.get_root()
  File "/home/romer/miniconda3/envs/linuxfork1/lib/python3.8/site-packages/debugprov-0.0.1-py3.8.egg/debugprov/execution_tree_creator.py", line 24, in get_root
    raise ValueError(
ValueError: ValueError: Something wrong in database. 4 root nodes found
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ rm -r .noworkflow
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ debugprov stoolkit.py 13
13 True

Choose a navigation strategy:
[1] - SingleStepping
[2] - TopDown
[3] - HeaviestFirst
[4] - DivideAndQuery
> 2
Do you want to use provenance enhancement?  (y/n) n
-------------------------
Evaluating node 1 stoolkit.py
Parameters: name | value
Returns: <module '__main__' from '/home/romer/ic/est_fork1/stoolkit.py'>
Is correct?  (y/n) n
-------------------------
Evaluating node 30 int(k)
Parameters: name | value
 k | '13'
Returns: 13
Is correct?  (y/n) y
-------------------------
Evaluating node 31 is_prime(int(k))
Parameters: name | value
 int(k) | 13
Returns: True
Is correct?  (y/n) y
-------------------------
Evaluating node 78 print(k, is_prime(int(k)))
Parameters: name | value
 k | '13'
 is_prime(int(k)) | True
Returns: None
Is correct?  (y/n) y
Output file name: exec_tree
(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$ more stoolkit.py
from prompt_toolkit.shortcuts import confirm

import sys
from math import gcd, ceil, sqrt
def is_prime(n):
    a=int()
    if n<6:
        if n<2 or n==4:
            return False
        return True
    MULT235 = 2*3*5
    if gcd(n, MULT235)!=1:
        return False
    end = sqrt(n)
    if not end%1:
        return False

    end = int(end)+1

    for x in range(3, end, 2):
        if not n%x:
            return False
    return True
if __name__ == '__main__':
    for k in sys.argv[1:]:
        print(k, is_prime(int(k)))

(linuxfork1) romer@romer-Z550MA:~/ic/est_fork1$