Ian Denhardt

We can build `list_project_users` on top of what you're doing in #945, so I don't think any changes are needed to the server at all.

The more I think about it the less comfortable I am adding calls that have different behavior based on the identity of the caller (besides just allow/deny). I worry it...

We could have a "show_user": `GET /users/`. ...but it doesn't nicely fit into the current authorization framework (which is based on project access), which I'm not happy about. Will keep...

@xuhang57, is there a specific pr you're referring to? #730 was a workaround, this issue refers to the more permanent solution.

Quoting Lucas H. Xu (2018-02-07 20:44:16) > [1]@zenhack sorry, I didn't read the entire discussion. I see this > links to a PR and that PR is merged. thanks for...

See the discussion in #730; basicaly, Flask-SQLAlchemy 2.2 changed things so that you need to use an app context instead of a request context. We're pinning the version for now...

afaik this is still current. We haven't actually removed the headnode stuff yet; that has to wait until the openvpn stuff is implemented.

Hm, not sure I agree with closing this going to re-open while we discuss the fate of the issue. We probably will want some way of facilitating managing resource usage,...

I'm also going to change the title to reflect the broader concern.

This might be an artifact of the fact that there was a previous installation on the MRI node -- I ran through the instructions top to bottom many times and...