Duplicates problem: duplicate messages arrive and stay until the client shutdown #611

New Issue

2014-01-13T05:54:33+01:00

yurivict commented

2014-01-13 05:54:33 +01:00

(Migrated from github.com)

I noticed that when someone answers my message, there is high chance that after a while this same response will come again for no apparent reason. Delay of duplicate varies from 20 min to 2-3 days. Duplicates are time-stamped with the time of arrival. I only noticed this with replies, not the originals.

However, when I shut the client down and restart it, only the latest duplicate would stay, and the earlier version would disappear. So the time on the message would be entirely wrong.

8c900e1194

I noticed that when someone answers my message, there is high chance that after a while this same response will come again for no apparent reason. Delay of duplicate varies from 20 min to 2-3 days. Duplicates are time-stamped with the time of arrival. I only noticed this with replies, not the originals. However, when I shut the client down and restart it, only the latest duplicate would stay, and the earlier version would disappear. So the time on the message would be entirely wrong. 8c900e119488f374b951d012b378bb4adf3ce06b

Atheros1 commented

2014-01-13 05:58:04 +01:00

(Migrated from github.com)

What types of messages is this affecting? Messages received from Chans? Normal person-to-person messages which don't involve chans?

yurivict commented

2014-01-13 06:04:59 +01:00

(Migrated from github.com)

It's person to person

pjf commented

2014-01-13 06:16:33 +01:00

(Migrated from github.com)

Just reporting that I'm seeing this as well for person-to-person messages. I normally leave the client running, so I hadn't noticed that only the most recent message from the duplicates would remain after a restart.

I can also confirm that if you've gone and trashed all the duplicates but the first one to arrive, then that original message disappears on restart (presumably because only the most most recent would be shown, but you've trashed that).

Just reporting that I'm seeing this as well for person-to-person messages. I normally leave the client running, so I hadn't noticed that only the most recent message from the duplicates would remain after a restart. I can also confirm that if you've gone and trashed all the duplicates but the first one to arrive, then that original message disappears on restart (presumably because only the most most recent would be shown, but you've trashed that).

Atheros1 commented

2014-01-13 06:34:28 +01:00

(Migrated from github.com)

To help me diagnose the issue, try this: the next time it happens (or if you have the duplicate messages showing in your UI right now, use the search box to search for something meaningless, then clear the search box and press enter to show all of your inbox messages. Are the duplicates showing? I imagine that they won't.

I also wish to look for patterns: Are you two using the EXE, the DMG, or the source code from December 8th or earlier or later?

To help me diagnose the issue, try this: the next time it happens (or if you have the duplicate messages showing in your UI right now, use the search box to search for something meaningless, then clear the search box and press enter to show all of your inbox messages. Are the duplicates showing? I imagine that they won't. I also wish to look for patterns: Are you two using the EXE, the DMG, or the source code from December 8th or earlier or later?

pjf commented

2014-01-13 06:40:33 +01:00

(Migrated from github.com)

Source code (git clone) as of 4th January, running on ubuntu 12.04. My apologies I don't have a specific commit id.

Alas I don't have any duplicates showing right now but I shall cheerfully try the search-and-clear test if/when I do.

Source code (git clone) as of 4th January, running on ubuntu 12.04. My apologies I don't have a specific commit id. Alas I don't have any duplicates showing right now but I shall cheerfully try the search-and-clear test if/when I do.

Atheros1 commented

2014-01-13 06:42:23 +01:00

(Migrated from github.com)

That's ok; saying January is sufficient (it rules out some things).

pjf commented

2014-01-13 07:07:55 +01:00

(Migrated from github.com)

For the purposes of helping me find my accidentally missing
deleted messages, whereabouts is the application trash? ;)

For the purposes of helping me find my accidentally missing deleted messages, whereabouts is the application trash? ;)

Atheros1 commented

2014-01-13 07:12:45 +01:00

(Migrated from github.com)

If you use a SQLite editor, you can open the messages.dat file. Close Bitmessage first. All of your current and previous inbox messages are in the inbox table. One of the fields is 'folder' which will say either 'inbox' or 'trash'.

pjf commented

2014-01-13 07:28:40 +01:00

(Migrated from github.com)

Aha! They're in the XDG config directory (~/.config/PyBitMessage), not the
XDG data direcotry (~/.local/share/PyBitMessage), that's why I couldn't find
the messages.dat file!

Many thanks!

Aha! They're in the XDG config directory (~/.config/PyBitMessage), not the XDG data direcotry (~/.local/share/PyBitMessage), that's why I couldn't find the `messages.dat` file! Many thanks!

yurivict commented

2014-01-13 07:47:09 +01:00

(Migrated from github.com)

I just run from the source code, git label in my OP

Atheros1 commented

2014-01-14 06:30:58 +01:00

(Migrated from github.com)

A user on Reddit reported probably the same problem here: https://pay.reddit.com/r/bitmessage/comments/1v0to6/help_bitmessage_keeps_sending_me_the_same/ceoyce0

I'm going to leave a node running which is in a bunch of chans and if it happens on my node I will have the console output to look at which should help a lot.

A user on Reddit reported probably the same problem here: https://pay.reddit.com/r/bitmessage/comments/1v0to6/help_bitmessage_keeps_sending_me_the_same/ceoyce0 I'm going to leave a node running which is in a bunch of chans and if it happens on my node I will have the console output to look at which should help a lot.

yurivict commented

2014-01-15 22:50:41 +01:00

(Migrated from github.com)

Someone reported the same on General Chat mailing list: BM-2DAV89w336ovy6BUJnfVRD5B9qipFbRgmr

What's the matter with Bitmessage? I'm receiving all the same messages over and over again!!! Anyone else?

Someone reported the same on General Chat mailing list: BM-2DAV89w336ovy6BUJnfVRD5B9qipFbRgmr ``` What's the matter with Bitmessage? I'm receiving all the same messages over and over again!!! Anyone else? ```

This repo is archived. You cannot comment on issues.