You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it's possible to specify the time limit and memory limit in ms and kb, but one could make a mistake in the three zeros. It's also a bit not readable -- it takes a bit of time to understand that 16000ms is 16s and not e.g. 1.6s.
What I propose:
leave the possibility of specifying in ms and kB,
add a new way to specify time and memory: memory_limit_mb and time_limit_s, which takes consecutively an integer and a float,
implement the same in sio2,
assert that when someone specifies e.g. both memory_limit and memory_limit_mb, then their values are equal (e.g. 1000 and 1).
The text was updated successfully, but these errors were encountered:
I think that's a good idea, but first I'd like to split sinol package management away from sio2 and sioworkers code. I'll try doing that in the coming months
Currently it's possible to specify the time limit and memory limit in ms and kb, but one could make a mistake in the three zeros. It's also a bit not readable -- it takes a bit of time to understand that
16000ms
is16s
and not e.g.1.6s
.What I propose:
memory_limit_mb
andtime_limit_s
, which takes consecutively an integer and a float,memory_limit
andmemory_limit_mb
, then their values are equal (e.g.1000
and1
).The text was updated successfully, but these errors were encountered: