Closed philomorphism closed 5 years ago
okay! i get it! there was a need of "import sys" which i later noticed that is latest commit in release.sos!!
so instead of downloading latest-release-v0.9.5 i downloaded the repo itself and tried to run..
sos run release.sos
ERROR: No step to generate target Py_Module("date_parser") requested by default_1
now what's wrong??
@XinYaanZyoy would you mind checking out release v0.9.6 I just made? The issue you are having is due to absence of date_parser
packages. The current version will install it for you.
ohh i forgot to initiating, adding and commiting to git VCS!
i tried again and the erros is....
Okay then it boils down to a Windows specific problem now: we are looking for /bin/bash
but cannot find it.
There are workarounds but the simplest would be to make sure you have bash
command available from your terminal in the first place?
i have Cygwin64 Terminal and i tried from there!
i tried in the windows command prompt again and this time the error is....
@XinYaanZyoy what's going on there is that you've got some intermediate _index.ipynb
files as relics in your previous failed runs -- you should see them via git status
. It is never an issue to me earlier because all my runs are successfully. For now please manually remove them. I'll try to modify the script to skip them if they exist.
My point previously is that you should first make sure in your shell when you type bash
it works. In any case, let me try to adjust my script a bit more and get back to you hoping we can address both issues from my end. I do not own a windows machine but I think I can guess what's goingon and fix.
@XinYaanZyoy if you pull the latest master
it should solve the bash issue --it will basically try to determine your command shell environment and try to use the approperate interpreter. I am not sure about the _index.ipynb
complaint now that I look at my code because they should be skipped already so there should not be any overlap between input and output files. And I cannot reproduce the issue on my end. In any case possibly manually removing them should work. Sorry we dont own or work with Windows machines. This is possibly the best we can do at this point (other than building and releasing the whole thing with docker.)
no sir, bash is not working on cmd!!
and i downloaded the latest one but it won't work i think because for that you have to change all those instructions like.... rmdir instead of rm for cmd!!
see...
ok let me try to do it by creating docker image with ubuntu and py3.7!
Okay it seems we are one step closer? I just pushed to master
replacing rm
with Python's os.remove
. That should take care of a couple more errors. Not sure if that's enough to get it work.
is it possible that i run " sos run release.sos clean" and the next ones from gitlab pipeline, if we use docker image which has python, pip, git, sos, jupyter???
Yes it should work for Windows if we provide a docker image that contains all the resource necessary to run this. I was just trying to remove blockers you've identified to try get away with making a docker image.
Congratulations! clean works!
V:\Yaan\learn\test007>sos run release.sos clean
INFO: Running clean:
INFO: Workflow clean (ID=bee5e6c592ab83e6) is executed successfully with 1 completed step.
but...
`V:\Yaan\learn\test007>sos run release.sos -s force INFO: Running Configure website:
Right, it means the core command jupyter nbconvert
does not work and there is no way around it. You'd have to either configure Windows properly, or perhaps a lot easier, create a docker image and run from there. Would be nice if you give a stab at the latter. I might find some time to do it later but not promises now.
thank you for your responses, i'm now working on the docker solution! will inform details here; either errors or success!
(off topic) can you say what i understand is correct or not(it'll help me in writing dockerfile and gitlab-ci.yml)
so i need write permission from gitlab to github, right?
Not familiar about gitlab (never used it). But your 1&2 are correct. If you decide to do it I'd suggest starting simple -- create Ubuntu virtual machine from your Windows OS, then try to install software in the VM until you are able to get it work. Then whatever you did to setup the Ubuntu VM will end up in your docker, if you take good notes of what you did in Ubuntu. For folder accessibility issues it should be docker
parameter -v
(for volume
) to map directories so you can have access to your disk from docker container instances. But that's the next step.