beta

The ability to move around by rolling a hamster ball

Like this: https://gfycat.com/OpulentExhaustedGoldenretriever

I'll try and contact the author on reddit: https://www.reddit.com/user/Reil

on latest develop, if I run:

go test
ERROR: 2020/10/09 16:43:21 oauth.go:148: viewOauthInit error: pretend unable to write state error
--- FAIL: TestViewOauthCallback (0.00s)
    --- FAIL: TestViewOauthCallback/success (0.00s)
        oauth_test.go:248: 
            	Error Trace:	oauth_test.go:248
            	Error:      	Received unexpected error:
            	            	/logi

Atmo should expose a health endpoint that can be used to determine the health of Atmo. This can include whether or not a bundle has been successfully loaded and Atmo is available to serve requests.

Good first issue because no Unity-specific programming is involved.

Our unit config files allow a c-style #include directive, which lets us break them up into small reusable pieces. Example:

{
    #include "DefaultMobility",
    #include "DefaultHeloArmor",
    "LabelIcon": "D",
    "CategoryKey": "HEL",
    "Name": "AH64D Apache",
    "Price": 20,
}

ConfigReader.cs has s

Description

In a wildcard import, all public names defined in the module are imported. It is advised to explicitly import the values needed or modify the module being imported from and define all to restrict the names to be imported.

Occurrences

There are 3336 occurrences of this issue in the repository.

See all occurrences on DeepSource → [deepsource.io/gh/robotichead/NearB

Something to collect multiple pods, like in cases where you need to watch multiple message types and need to keep references to multiple pods.

Something like:

pods := g.PodGroup()

pods.New().On(...)
pods.New().OnType(...)

It would still be safe since pods retains the pod object so you don't have to if you don't want to.

After updating the build tools while migrating the SDK to Maven Central, we have a lot of new deprecation warnings.