The attached error appears “randomly” (I know, not so helpful) when closing Inkdrop on Windows 11.
Might it be related to an “old” version of node.js I have running? I have 16.18.1 and I cannot upgrade due to the techstack we are using.
craftzdog
(Takuya Matsuyama)
April 18, 2024, 1:19am
2
Hi Patrick,
Thanks for the report.
The error message seems to come from leveldown, which is a database engine.
So, it happens in the native layer.
I guess it’s nothing to do with your installed node version.
I’ll look into the clean-up part!
craftzdog
(Takuya Matsuyama)
April 19, 2024, 6:29am
3
@Patrick_Thomas v5.8.1-beta.1 should solve this issue.
Would you mind testing it?
craftzdog
(Takuya Matsuyama)
May 1, 2024, 2:38am
4
The fix has landed in v5.8.1:
[2024-04-30_Inkdrop Desktop v5.8.1_thumb-play]
Hey Inkdroppers,
Thanks for all the feedback after the release of v5.8.0 and during the beta testing! It’s got much stabler.
Bug fixes
The ‘Readable line length’ option has been disabled by default
The ‘Readable line length’ option was introduced on v5.8.0 . But, this option made the existing users so confused as they reported on the forum (1 , 2 , 3 , 4 , 5 ). Then, Shimizu-san suggested that it’d be nice not to enable this option by default a…
Let me know if the issue still persists.
Lukas
July 21, 2024, 10:35am
5
I still get this error message sometimes.
I can reliably reproduce this error when I update the content of a note and then close the app immediately afterwards.
This situation has been simulated for reproduction. However, the error sometimes occurs even after a longer period of time between changing the note and closing the app.
On a side note: I find it quite unusual that I get this assertion dialog. (By default, these are only shown in debug builds)
craftzdog
(Takuya Matsuyama)
July 22, 2024, 12:44am
6
@Lukas , thanks for the report.
Hmm, the assertion is caused by the leveldown’s native module according to the error message.
I found a similar report on their repos:
opened 10:08AM - 31 Jan 21 UTC
closed 09:12AM - 12 Sep 21 UTC
bug
I am using `node runtime 12.20.0 & 12.18.3` on a `Windows 10 & Mac 10.14.6` mach… ine with following code, which is resulting in lot of Assertion Failed Messages:
```
var level = require('level-party')
var db = level(__dirname + '/data', { keyEncoding: 'binary', valueEncoding: 'json' })
const start = Buffer.allocUnsafe(8);
start.writeBigInt64BE(1n, 0);
const end = Buffer.allocUnsafe(8);
end.writeBigInt64BE(2n, 0);
let x = new Promise((a, r) => {
db.createReadStream({ gte: start, lte: start })
.on('data', function (data) {
console.log(data.key, '=', data.value)
})
.on('error', function (err) {
console.log('Oh my!', err)
r();
})
.on('close', function () {
console.log('Stream closed')
a();
})
.on('end', function () {
console.log('Stream ended')
a();
})
});
x.then((e) =>
console.log("Done")
)
```
Message 1: Assertion Failed at binding.cc @ 545
Message 2:Assertion Failed at version_set.cc @ 798
![Message1](https://user-images.githubusercontent.com/22937426/106380772-65fc8380-63da-11eb-8dcf-5076143146f9.PNG)
![Message2](https://user-images.githubusercontent.com/22937426/106380773-672db080-63da-11eb-952e-44a4ad837c01.PNG)
It is marked as resolved.
The app is still using leveldown@5.6.0. I will try updating it!
my progress note: