Sure, makes sense, thanks! Now renamed to -buildVersion.

Ah, I understand now that -version is a custom flag used by this code, and not something that was baked into Unity (until now, when it's causing problems!).

I've submitted a possible fix as #137.

-version is now used (as of 2019.4.8f1 or earlier) by the Unity CLI to print its own version, then exit with code 0. This interferes with unity-builder's version passing, so I propose renaming the argument to something less likely to collide.

I was unable to run Yarn as requested in the contributing guidelines, as I'm missing tons of prerequisites. Besides whatever CI checks this repo can provide, I can confirm that this fixed #136 in my game's workflow.

After upgrading my Unity version (with no other changes to my use of unity-actions), now build output looks like this:

###########################
#    Building platform    #
###########################

2019.4.8f1 (60781d942082)
Build succeeded

###########################
#     Build directory     #
###########################

total 8.0K
drwxr-xr-x 2 root root 4.0K Aug 15 13:25 .
drwxr-xr-x 3 root root 4.0K Aug 15 13:25 ..

I encountered this by using unityVersion: 2019.4.8f1, but you can reproduce the underlying issue more directly by trying the -version flag:

$ docker pull gableroux/unity3d:2019.4.8f1-linux-il2cpp
$ docker run -it --rm gableroux/unity3d:2019.4.8f1-linux-il2cpp
# /opt/Unity/Editor/Unity -batchmode -version "v1.0" -logfile /dev/stdout
2019.4.8f1 (60781d942082)

It appears that -version is interpreted by the Unity CLI to print its own version, rather than provide a version for the build.

When it's not provided, Unity continues to start up as normal:

# /opt/Unity/Editor/Unity -batchmode -logfile /dev/stdout
[LicensingClient] ERROR Failed to connect to local IPC
[Licensing::Module] Failed to connect to channel: LicenseClient-root
[Licensing::Module] Successfully launched the LicensingClient
[SignatureVerifier] Application signature verification not supported on this platform.
[Licensing::Module] Successfully connected to LicensingClient on channel: LicenseClient-root
[Licensing::Module] Successfully launched and connected to LicensingClient
Entitlement-based licensing initiated
[LicensingClient] Licenses Updated successfully in LicensingClient
Error opening default X display
(Filename: ./Editor/Platform/Linux/X11Quarantine.cpp Line: 33)

(This failure is expected, as I didn't set up an X server for this test.)

I couldn't find any mention of a -version flag even in the 2019.3 docs, so I'm not sure what the best solution is here.

Does it work if you try to write something like this without the @adt sugar? The only thing that I can think of at this point is that there is a genuine mypy bug or limitation.

Thank you for developing this container. My question is not an issue of the container. I was actually wondering how I can change the restart time of ibgateway?

Sorry, I don't know. This project is just a simple wrapper.

I haven't had a chance to try this sample out myself, but my guess is that the typechecker is failing to unify the types of ok and err. If you try the same code, but with lambdas wrapping fun and Result.ERR, does it work?