TypeError: sequence item 1: expected string, NoneType found

Create issue
Issue #274 closed
Frank Löffler created an issue


I executed simfactory to login to hopper, and got:

$ sim login hopper
Warning: Unable to determine CACTUS_PATH, using /home/knarf/utils/simfactory instead
Info: Simfactory command: /home/knarf/utils/simfactory/bin/../lib/sim.py "login" "hopper"
Info: Version 1195M
The Simulation Factory: Manage Cactus simulations

Info: defs: /home/knarf/utils/simfactory/etc/defs.ini
Info: defs.local: /home/knarf/utils/simfactory/etc/defs.local.ini
Info: Executing command: login
Logging into remote machine hopper
Warning: Called from the wrong location.
Current directory is '/home/knarf'
but expected a subdirectory of '/home/knarf'.
It is also be possible that you need to correct your 'sourcebasedir' entry
in the mdb entry for this machine.
Traceback (most recent call last):
  File "/home/knarf/utils/simfactory/bin/../lib/sim.py", line 141, in <module>
  File "/home/knarf/utils/simfactory/bin/../lib/sim.py", line 138, in main
  File "/home/knarf/utils/simfactory/bin/../lib/sim.py", line 105, in CommandDispatch
  File "/home/knarf/utils/simfactory/lib/sim-util.py", line 246, in main
  File "/home/knarf/utils/simfactory/lib/sim-util.py", line 51, in CommandDispatch
    exec("command_%s()" % command)
  File "<string>", line 1, in <module>
  File "/home/knarf/utils/simfactory/lib/sim-util.py", line 125, in command_login
    local_sourcedir = simlib.BuildPath(local_sourcebasedir, source_name)
  File "/home/knarf/utils/simfactory/lib/simlib.py", line 673, in BuildPath
    return os.sep.join(args)
TypeError: sequence item 1: expected string, NoneType found

The warnings about the Cactus location shouldn't be there (simfactory shouldn't care about that, but that is already mentioned in another ticket), and might be unrelated to the error later, which aborts.


Comments (2)

  1. anonymous
    • changed status to resolved
    • removed comment

    sim login will now work if it doesn't know where Cactus is. I also got rid of that weird warning.

  2. Log in to comment