Feature request

Place the access_log and error_log directives inside the main server block instead of http block.

Feature description

Disable access_log at http block:
File: /etc/nginx/nginx.conf

# ...
http {
    # ...
    access_log off;
    # ...
}
# ...

Enable per site access_log and error_log at main server block:
File: /etc/nginx/

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my [Ory Cl

Current implementation of Go binding can not specify options.

GPUOptions struct is in internal package. And go generate doesn't work for protobuf directory. So we can't specify GPUOptions for NewSession.

• Base README.md
• Quizzes
• Introduction base README
  • Defining Data Science README
  • Defining Data Science assignment
  • Ethics README
  • Ethics assignment
  • Defining Data README
  • Defining Data assignment
  • Stats and Probability README
  • Stats and Probability assignment
• Working with Data base README
  • Rel

Is your feature request related to a problem?

I wanted to create an entity that is only shown to one player, but I can still change and resend. Unfortunately, the only way to do that is to manually run Entity#hideEntity on every player on the server, and any that log on after the entity is spawned.

Describe the solution you'd like.

I would like there to be a Entity#hideEntityByDefault w

Currently if you attempt to fetch a deleted workspace, if it is deleted you need to include ?deleted=true query parameter. We also have a include_deleted query param in the case that it will return regardless if it is deleted or not.

If you fetch workspaces, then the ?deleted query param only shows deleted workspace OR it shows active workspaces. It will never show a mixed set of dele

🚀 Feature Request

HF has some logic under the hood that looks at the number of labels in order to decide if whether to use a BCE, CE, or MSE loss.

Splitting up the BERT class based on the loss and making these distinctions as to what loss is used to the user may be more clear. It also aligns with the work of @Landanjs

Note: this may also require creating a separate .loss method in