-
Notifications
You must be signed in to change notification settings - Fork 7
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
Two projects, job submission #89
Comments
In principle this is expected. In our idea two different projects may be more or less like two different setups of fireworks with two different launchpads. So, inside each document in the queue Store there is no information about which project it belongs to, as it is basically assuming that all the jobs will belong to just one project. There are two options:
Would this be fine with you? On the other hand, since the outputs are mainly based on jobflow's uuid, in principle you could use the same collection for the outputs. In any case, thanks for raising the issue. I will clarify this in the documentation. |
Thanks, @gpetretto , for the clarification! I will try your suggestion. I think I will try option 2. Just do add: only one daemon was activated. Thus, I did not expect these side effects. |
With only one daemon activated it is indeed weirder that you got some error. Do you maybe still have the exact error message? |
It raises a remote error and cannot fetch the queueerror from the db. I am also using two remote workers and I am also not sure this is connected. Would need to do a lot of testing that I don't have time for at the moment |
In any case, I will get back to this |
I tried again with the suggested settings. This does not work as well. |
This also does not work:
It never asks me to login. |
Potentially, I have done something stupid with the setup. Will reinstall later and report back. Sorry! |
I should have fixed this in the I will wait for your feedback before investigating the rest of the issue further. |
It now works again. I think I will close this for now, as I did not investigate systematically. I am now using the default collections again and deleted the other project. However, pointing out again that different databases/or different collection names for all required collections are needed if one wants to use two different databases. (Sorry for the mess. I wanted to do something quickly and ended up doing everything 5 times... ) |
I have two projects. When I submit a job with the wrong project (the demon of this project is not running), the job gets submitted to the queue.
Even when I take the correct project name for the submission, the workflow shows up in both projects when typing:
jf -p project2 job list
jf -p project1 job list
I am not sure this is intended. (I am using the same database but have specified different collections for outputs)
Related or maybe not related: then the data retrieval from the remote runner fails.
The text was updated successfully, but these errors were encountered: