GitMate.io thinks possibly related issues are #1583 (Create linterbear for Xquery), #973 (Create asciinemas), #161 (setuptools problem - creates requires.txt), #2079 (Create linter for gindent), and #839 (Create coala --bear-details <bear_name>).

Is this Bear supposed to check whether if there is +x permission and if not add it as a patch ?Just checking

Is this Bear supposed to check whether if there is +x permission

Not quite that specific. It is supposed to check whether the file permissions match those given in the setting.

require isnt a good name for the setting, as it is rather ambiguous.

filemode = ... would be better.

However, the first design issue is how do we do this in a way that supports both Windows and Unix.
If you can come up with a sensible solution for that, we can assign the issue to you.

.. and if not add it as a patch

We currently do not have the ability for a 'patch' to modify file permissions.
A first version of this bear that only detects and does not fix would be good.
We could then create a new issue for fixing the problem automatically.

fyi, passwords and such are not appropriate for fixes; the bear would try to change the permissions if it can, otherwise it would not fix. bears escalating privilege levels, or having any access tokens, is not something we're likely to ever do.

If the person running coala wants a bear to do things which require escalated privileges, it should give the coala process those privileges.

Typically, the bear will be run by an account which has write access to the files.

But moreover, a 'fix' for modes can be done as a new 'action' type, but in this case a fix could be a patch as git patches do record changes of file modes. But coala doesnt support that yet iirc.

@jayvdb

However, the first design issue is how do we do this in a way that supports both Windows and Unix.

Confuses me does os module works differently in Windows ( srsly didn't know), if No then we have a
filename in bear arguments which is actually full file path, doesn't this will solve the caveats platform dependent?

https://docs.python.org/3/library/os.html mentions lots of OS specific aspects, and it links to https://github.com/python/cpython/blob/3.7/Lib/os.py which you can see is almost entirely OS specific logic.

Windows and Unix file permissions models are very different. Proper analysis is needed to ensure the bear would work correctly on both platforms.

Reading os.chmod would tell you that this has platform specific problems to it.

This issue reserved for Google Code-in task 6370456127930368.

This issue is reserved under the GSoC project Improve Generic Bear Quality.