search

pydio / pydio-sync

Python version of the Pydio synchronization client
https://pydio.com
GNU General Public License v3.0
82 stars 32 forks source link

fixed a for loop using objects as indexes #88

Closed u210F closed 9 years ago

u210F commented 9 years ago

Hi,

the job scheduler tries to use objects as indizes in the start_all for loop. This seems to have already been fixed in e.g. the pause_all loop, so sorry if this is fixed in some other branch (I did check a bit). This prevented me from using the program at all.

Cheers, Michael

cdujeu commented 9 years ago

well definitely not an issue on my side. Is your code up-to-date? Or maybe it's linked to how you pass server config? Do you use the UI to create synchro, or do you preset a config file? The job_configs object is definitely an associative array, so the job_id is really a key!

u210F commented 9 years ago

Hi,

I am using a config file to pass the jobs via the --file=<> command line argument and that definitely gives me the error: Traceback (most recent call last): File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main "main", fname, loader, pkg_name) File "/usr/lib/python2.7/runpy.py", line 72, in _run_code exec code in run_globals File "/usr/local/lib/python2.7/dist-packages/pydio/main.py", line 291, in main() File "/usr/local/lib/python2.7/dist-packages/pydio/main.py", line 224, in main scheduler.start_all() File "/usr/local/lib/python2.7/dist-packages/pydio/job/scheduler.py", line 42, in start_all job_config = self.job_configs[job_id] TypeError: object cannot be interpreted as an index

But I don't mind, it works with my changes. I did not yet try the UI.

u210F commented 9 years ago

ahyes, the job config file generated when passing commandline arguments is totally different from the one mentioned on the github page.

I am getting further, the rest of the errors are server-sided I believe, thanks.