Hope this helps I am currently having the exact same problem. After some experimenting I have found the following: The gitlab user is supposed to be not able to login, so its shell in /etc/passwd is set to /bin/false. For SSH access, there is a forced command defined in ~gitlab/.ssh/authorized_keys that executes the gitlab-shell with the key as an argument to make basic git operations accessible to the connecting user. Now I have found that while the users shell in /etc/passwd is set to /bin/false, the forced command mechanism doesn't work at all, and ssh connections hang up. A workaround is to just give the user a default login shell, so that forced commands get executed.
Getting 502 on gitlab when adding repositories, users or doing other actions
wish help you to fix your issue For future reference: turns out GitLab does not run on Debian 7 32Bit - I can not say for sure, but doubt it has to do with the versions in Debian's 7 repository (which are in general older) as I compiled most of the stuff and with gem it anyway got the versions as defined by GitLab. Very likely GitLab (or gems it is using) does not currently work on a 32Bit system.
Who can access public repos under an Organization in GitHub?
this one helps. I'm assuming that you want myStruct to talk to the classField of the containing myClass instance. If that is the case: then the problem isn't accessibility - it already has access; the problem is scope. As far as the compiler is concerned, nesting here is unrelated to instancing, so the problem is that myStruct has no specific instance of classProperty to talk to. That's why the error is: