Getting this error on MacOS Sonoma 14.0 Beta

warning: method `get_event_ids_with_hashtag` is never used

--> src/storage/mod.rs:642:12

|

642 | pub fn get_event_ids_with_hashtag(&self, hashtag: &String) -> Result, Error> {

| ^^^^^^^^^^^^^^^^^^^^^^^^^^

|

= note: `#[warn(dead_code)]` on by default

warning: `gossip` (bin "gossip") generated 1 warning

Finished release [optimized] target(s) in 1m 37s

Error: Error { kind: Lmdb(BadValSize), file: None, line: None }

Reply to this note

Please Login to reply.

Discussion

That last line is the error, the warning is not relevant. Generally this means in a DUP_FIXED database I tried to store a value that is not of the fixed size for that database.

Can you give me the exact version number from Help > About please (or the git commit)?

OR it could be a key that is longer than 511 bytes. More likely it's that. I'll have to scan the code to see where I may have forgotten to trim the key.

The client does not launch because of the error.

I guess it is this -> gossip v0.8.0-unstable

Did this happen the first time you tried the new lmdb work?

I think so. I am not sure though. This error is recent.

Yes the first time…I remember now

Did you try the LMDB branch before and not delete it before it merged into master? Just throwing out ideas cause wherever the problem is it is not obvious

(I wish all my try! (?) statements gave me line numbers! but I can't make such a change with many branches of work still open it would end up in merge madness)

I did not delete anything before - was I supposed to?

Only if you tried the unstable branch or lmdb branch. If you were always on master, it is not an issue. If you tried unstable or lmdb, you should remove the lmdb director and re-import from sqlite.

It sounds like a bug though, just not happening to everybody.

Interesting...I have another computer MacOS and it works fine there...I have not done anything different while updating. I will dig into it a bit on the other machine and see what is going on.

From the computer it works it was updating from below...

From https://github.com/mikedilger/gossip

e88cfe5..39d64a4 master -> origin/master

e88cfe5..5c61905 unstable -> origin/unstable

Where is the lmdm directory…I don’t see it. Below is all I can see.

Wait…found these 2 in target/build…is that what I should delete

lmdb-rkv-sys-d9e52b79a4e3f566

lmdb-rkv-sys-e428970c930e8535

This is fixed now, but for future reference we use this directory:

https://docs.rs/dirs/latest/dirs/fn.data_dir.html

and append "gossip/" afterwards. Then we append "lmdb/" after that for the lmdb database.

thanks Mike

Tried a clean re-install…still getting the error

2023-08-12T13:02:12.404125Z INFO src/storage/import/mod.rs:15: Importing SQLITE data into LMDB...

2023-08-12T13:02:12.406736Z INFO src/storage/import/legacy/mod.rs:106: Database is at version 37

2023-08-12T13:02:12.406751Z INFO src/storage/import/mod.rs:25: LDMB: setup

2023-08-12T13:02:12.406892Z INFO src/storage/import/mod.rs:32: LMDB: imported local settings.

2023-08-12T13:02:12.406971Z INFO src/storage/import/mod.rs:39: LMDB: imported settings.

2023-08-12T13:02:22.020720Z INFO src/storage/import/mod.rs:49: LMDB: imported event-seen-on-relay data.

2023-08-12T13:02:22.092482Z INFO src/storage/import/mod.rs:60: LMDB: imported event-viewed data.

Error: Error { kind: Lmdb(BadValSize), file: None, line: None }

Am on MacOS Sonoma beta 14.0