Untitled


(base) C:\Users\lucas>hf

(base) C:\Users\lucas>cd desktop\ic\hf\

(base) C:\Users\lucas\Desktop\ic\hf>conda activate est_fork3

(est_fork3) C:\Users\lucas\Desktop\ic\hf>cd agosto26

(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26>cd nova pasta

(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta>dir
 O volume na unidade C é OS
 O Número de Série do Volume é 5262-F822

 Pasta de C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta

02/09/2021  23:31    <DIR>          .
02/09/2021  23:31    <DIR>          ..
02/09/2021  10:35            53.248 .coverage
02/09/2021  17:58    <DIR>          .noworkflow
03/09/2021  00:21    <DIR>          arvores_scripts
27/08/2021  04:35            57.572 arvores_scripts.zip
02/09/2021  23:31            63.761 console 02nov.txt
02/09/2021  10:35    <DIR>          coverage_data
27/08/2021  04:30               281 diferenças.txt
02/09/2021  10:35               643 exec_tree.gv
02/09/2021  10:35            19.813 exec_tree.gv.pdf
02/09/2021  17:47               126 sbm.py
27/08/2021  03:31               562 shide.py
27/08/2021  03:32            18.242 shide1.gv.pdf
27/08/2021  03:30            25.280 spure.gv.pdf
17/07/2021  16:27               512 spure.py
27/08/2021  03:54            15.207 stoolkit.gv.pdf
02/09/2021  10:38               577 stoolkit.py
02/09/2021  10:35               236 test_shide.py
02/09/2021  10:35    <DIR>          __pycache__
              14 arquivo(s)        256.060 bytes
               6 pasta(s)   26.278.113.280 bytes disponíveis

(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta>cd arvores_scripts

(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>dir
 O volume na unidade C é OS
 O Número de Série do Volume é 5262-F822

 Pasta de C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts

03/09/2021  00:21    <DIR>          .
03/09/2021  00:21    <DIR>          ..
27/08/2021  04:30               281 diferenças.txt
27/08/2021  03:31               562 shide.py
27/08/2021  03:33            18.242 shide1.gv.pdf
27/08/2021  03:30            25.280 spure.gv.pdf
17/07/2021  16:27               512 spure.py
27/08/2021  03:54            15.207 stoolkit.gv.pdf
27/08/2021  03:15               560 stoolkit.py
               7 arquivo(s)         60.644 bytes
               2 pasta(s)   26.278.088.704 bytes disponíveis

(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>more shide.py
import sys
from math import gcd, ceil, sqrt
def is_prime(n):
    from prompt_toolkit.shortcuts import confirm
    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)))


(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>now run shide.py 7
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
[now] ValueError("path is on mount 'D:', start on mount 'C:'")
the execution finished with an uncaught exception. Traceback (most recent call last):
  File "C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts\shide.py", line 23, in <module>
    if __name__ == '__main__':
noworkflow.now.collection.prov_execution.structures.ConditionExceptions.__getitem__.<locals>.ConditionException

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_execution\execution.py", line 64, in collect_provenance
    exec(compiled, metascript.namespace)  # pylint: disable=exec-used
  File "C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts\shide.py", line 25, in <module>
    print(k, is_prime(int(k)))
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_execution\collector.py", line 1202, in _call
    result = future.func(*args, **kwargs)
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_execution\collector.py", line 1363, in new_function_def
    activation, function_def, args, kwargs, default_values, defaults, *args, **kwargs
  File "C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts\shide.py", line 4, in is_prime
    from prompt_toolkit.shortcuts import confirm
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_deployment\py3module.py", line 32, in exec_module
    None, source_path, "module", False, True
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_definition\definition.py", line 75, in create_code_block
    path = os.path.relpath(path, self.metascript.dir)
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\ntpath.py", line 562, in relpath
    path_drive, start_drive))
ValueError: path is on mount 'D:', start on mount 'C:'


(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>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)))


(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>now run stoolkit.py
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
[now] ValueError("path is on mount 'D:', start on mount 'C:'")
the execution finished with an uncaught exception. Traceback (most recent call last):
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_execution\execution.py", line 64, in collect_provenance
    exec(compiled, metascript.namespace)  # pylint: disable=exec-used
  File "C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts\stoolkit.py", line 1, in <module>
    from prompt_toolkit.shortcuts import confirm
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_deployment\py3module.py", line 32, in exec_module
    None, source_path, "module", False, True
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_definition\definition.py", line 75, in create_code_block
    path = os.path.relpath(path, self.metascript.dir)
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\ntpath.py", line 562, in relpath
    path_drive, start_drive))
ValueError: path is on mount 'D:', start on mount 'C:'


(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>now run stoolkit.py 7
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
[now] ValueError("path is on mount 'D:', start on mount 'C:'")
the execution finished with an uncaught exception. Traceback (most recent call last):
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_execution\execution.py", line 64, in collect_provenance
    exec(compiled, metascript.namespace)  # pylint: disable=exec-used
  File "C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts\stoolkit.py", line 1, in <module>
    from prompt_toolkit.shortcuts import confirm
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_deployment\py3module.py", line 32, in exec_module
    None, source_path, "module", False, True
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\noworkflow-2.0.0a0-py3.7.egg\noworkflow\now\collection\prov_definition\definition.py", line 75, in create_code_block
    path = os.path.relpath(path, self.metascript.dir)
  File "D:\Users\lucas\anaconda3\envs\est_fork3\lib\ntpath.py", line 562, in relpath
    path_drive, start_drive))
ValueError: path is on mount 'D:', start on mount 'C:'


(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>now run spure.py 7
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
7 True

(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>now run shide.py
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props
D:\Users\lucas\anaconda3\envs\est_fork3\lib\site-packages\sqlalchemy-1.4.0b1-py3.7-win-amd64.egg\sqlalchemy\orm\relationships.py:3447: 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.   The 'overlaps' parameter may be used to remove this warning.
  for (pr, fr_) in other_props

(est_fork3) C:\Users\lucas\Desktop\ic\hf\agosto26\Nova pasta\arvores_scripts>