Hmm, workaround is in using `Integer.MAX_VALUE` in...
# announcements
v
Hmm, workaround is in using
Integer.MAX_VALUE
instead of
Int.MAX_VALUE