-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Module base_module_doc_rst migrated from version 6.1 #253
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
Conversation
|
I cleaned what I could (following travis), for the rest I'll need some help. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now you don't need invoke to classes
|
Check pylint error: |
|
That should do it. |
|
Ok, failed builds are not relative to this commit: |
[IMP] Badges and translation config
|
You still have an error: |
|
Done. You made me set up flake and pylint on my local machine to find out what was the problem! ... And they say that an old dog can't learn new tricks! 😄 |
|
he he he. Thanks, Dhaval Patel On Fri, Sep 18, 2015 at 9:10 PM, Matjaz Mozetic notifications@github.com
|
|
@sysadminmatmoz |
|
OK, current errors come from another modules. 👍 |
|
So why not correcting the other modules since I'm here. 😄 |
|
Thanks for your efforts! It seems that something strange has come in your work, because there are some commits that are mixed that doesn't belong to your PR. Trying your PR in runbot, I can't get the relationship graph. Sometimes it doesn't say anything, but no image is presented, and sometimes I get this error: And the RST generated is in an unreadable format. It's not plain RST? |
|
The image gets presented only for the modules that are really currently installed (not just present as installable) in the same database where you run the creation button. The RST is the sphinx RST (as defined in description) - the output file is a gzip archive containing index.rst, module.rst and relations graph. What commits not belonging to the PR do you mean? 2 files are just corrections to modules that Travis complained about, 2 are relative to a merge, since the repository was updated since I made the original PR. Regarding the issue: could it be a rebase problem? It works quite fine on a real instance DB. |
|
Thanks for the explanations. Can you perform then these operations:
|
|
That's one of the reasons I became a member of the community. There are some things I'm good at and some things where I'm not, but I'm sure that someone else in the community is. Professionally I'm a problem solver, I'm good at making things work; but to polish them to the final product I need a specialist, thus someone else 😄 . I'm sure I'd be able to do what you ask eventually (spending hours of study and experiments as with everything else regarding coding, since it's just a hobby for me and not what I usually really do), but there's sure someone in the community that already knows exactly what to do spending minutes where I would spend hours. So, to make it short: if those operations are a must to get things moving, I'll do it (in a month or so, when I'll have some time to spend on it), but I really hope that someone better than me gets his hands on it way before that. 😄 |
|
Well, I was only suggesting that improvements, but I'm not very interested for now in the module itself, so if you can't work on them, at least annotate them on "Know issues" section, and see if any other can improve them. |
|
Moving the PR in #257 and closing, since I messed up my repo. |
[FIX] reset fields' domains if they contain references
Syncing from upstream OCA/server-tools (10.0)


I use it as a tool for the relationship graph mostly, but it could be handy for someone else too.