Niklas Fiekas
Niklas Fiekas
This is working in general. Please email [email protected] so that we can debug deliverability for your specific email address.
I agree that this would be nice to have. Currently all statistics are submitted to an InfluxDB instance (that is not intended to be read by lila) instead of the...
I'd imagine that this will be most useful when serializing to disk, so despite the relatively large memory usage as per `sys.getsizeof(bytes(24))`, it's really the `24` that makes it interesting.
Perhaps we could keep a small buffer of vectors with timestamps? The issue exists also for input devices with timer that use `continue_reading`, so if it's not too expensive, this...
No updates, but I am still interested in having this fixed and will get back to it eventually. I am also happy if someone else beats me to it.
Not stale. Still no great solution
Finally here's an attempted fix: #7794.
I think most current issues with invalid object pointers come from mixed ownership. Screens are owned by the application logic. Other objects are owned by their parent object, but the...
A dangling object is not very useful, but it would guarantee valid memory that belongs to the exact object. So all operations on it would still have well-defined and predictable...