Myk Melez

> Since XUL extensions are now forbidden, they started to study to remove some XUL features (like XBL), and so it may affect SlimerJS in the long term. We'll see....

> Max environment size (default as 10 MB), once the environment is full, following writes will fail The LMDB docs say that the default is 10MB, but the code actually...

@shivawu You can change the map size using rkv. See #82 for tests that demonstrate how to do that.

> Ah I see, somehow I missed it. Thanks for pointing that out. Probably the local doc does not work that well for me.. Also btw, the online doc is...

@ncloudioj It seems helpful to periodically check stats and preemptively increase the map size if the database is approaching its limit (as well as to periodically call [mdb_reader_check](http://www.lmdb.tech/doc/group__internal.html#ga576f9ec8e49724e52b2cd7ce7b832856) to clear...

This morning it occurred to me that we might implement this in rkv instead of kvstore, in which case rkv consumers more generally would gain the benefit of this automatic...

It occurred to me recently that a reason to do this in rkv rather than kvstore is that even in Firefox there are consumers who are using rkv directly, such...

Note https://www.openldap.org/its/index.cgi/Software%20Bugs?id=8975, which fixes a (rare) error/crash when calling `mdb_env_set_mapsize()` on Windows if `MDB_WRITEMAP` is set. It's already been landed on the mdb.RE/0.9 branch, but a new version of LMDB...

The _Value_ type is designed to prevent an accidental "cast" from one type to another when storing and then retrieving a value. I understand how _Value_ might feel extraneous for...

> ``` > store.put(&mut writer, key, value.to_bytes()?); > store.get(&reader, key).and_then(Value::parse); > ``` This feels harder than it should be to read and write typed values. I wonder if it would...