Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Track dropped arbitration messages #85

Closed
cbeams opened this issue Mar 17, 2018 · 2 comments
Closed

Track dropped arbitration messages #85

cbeams opened this issue Mar 17, 2018 · 2 comments

Comments

@cbeams
Copy link
Member

cbeams commented Mar 17, 2018

@cbeams commented on Wed Jan 10 2018

Per details in the description of #1172, this issue exists for tracking arbitration cases where messages have been dropped, or we believe they have been dropped.

To make note of an incident, add a comment to this issue as soon as possible, mention the Trade ID, who the arbitrator is, and explain what happened as best as you can. Do not include identifying details about the trade or traders involved.

Note: this issue and the instructions are primarily intended for @bisq-network/arbitrators, but individual traders are also welcome to follow these instructions if they believe they're experiencing a dropped message problem during arbitration.

In any case, by keeping close track of how often this problem is happening, we'll be able to know when we've solved it.

This issue is closely related to, but distinct from #1174. Please do not confuse the two.


@cbeams commented on Fri Jan 12 2018

For the record, my last known incident with dropped arbitration messages happened on January 6th, as documented in the forum at https://bisq.community/t/cannot-see-answers-of-closed-dispute-ticket/4262. I followed up with the user in a private chat there and all is well.


@keo-bisq commented on Sat Jan 13 2018

I have several disputes where one trader is not responding, possibly due to dropped messages:
0423401, QITYNPXN, 4159602. These disputes have been hanging for weeks now with no messages on the forum.


@ManfredKarrer commented on Sun Jan 14 2018

@keo-bisq Can you post that on the Forum as well?


@cbeams commented on Fri Jan 26 2018

Trade 96205518 definitely just had a dropped arbitration message. Namely, the seller sent me a message that I never received. I confirmed this with the seller via email, and saw a screenshot of his client confirming it. We had successfully exchanged chat messages on this ticket before, and now after the dropped message, but the dropped message never made it through.


@cbeams commented on Fri Feb 09 2018

Trade vNYbeG appears to have dropped its 'payment started' message; I got screenshot proof that the buyer clicked the button, but the seller said they were unable to click 'payment received'.


@cbeams commented on Mon Feb 12 2018

Trade vNYbeG appears to have dropped its 'payment started' message; [...]

Note: adding the above message on this issue was a mistake on my part. I meant to add it to #1174, and I've done that now at bisq-network/bisq#1174 (comment)


@cbeams commented on Mon Feb 26 2018

Trade ID ZKdpG experienced at least one dropped arbitration message on the buyer's side.


@cbeams commented on Sun Mar 11 2018

It appears that the seller in trade KEHENQM never received my initial arbitration chat message, leading to significant delays in the arbitration process.


@cbeams commented on Wed Mar 14 2018

One of my arbitration messages to the buyer in trade 999999 was dropped, and this was verified by the buyer in a series of screenshots of our chat thread.

This dropped message caused at least one full day of unnecessary delay in the arbitration process.

@cbeams
Copy link
Member Author

cbeams commented Mar 22, 2018

Trade 99999 exhibited something similar to this behavior, but instead of dropped arbitration chat messages, the buyer in this trade received duplicates of several of my messages.

@pazza83
Copy link

pazza83 commented Aug 28, 2021

Closing as stale

@pazza83 pazza83 closed this as completed Aug 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants