Log-client user's auctions are not sent (or not parsed)?

[Synesso]

Auction messages sent from the (presumed sole) streaming user do not appear in the live feed. Perhaps they were not sent. Perhaps they are filtered out server-side.

[rslavin]

Do you have an example of an auction string that isn't parsed? There are currently auctions being broadcasted so this may be an issue with the web client not rendering it.

[Synesso]

The text that did not appear is:

Okayokay auctions, 'WTS Forest Loop 350, Golden Star Amulet 50, Idol of Woven Grass 30, Left Goblin Ear (4) 30ea, Golden Star Amulet 30, Chitin Shell Shield 20, Collar of Undead Protection 15'

It now does appear.

Could it be that a second log-client has come online and sees text from 3rd person view? But first-person auctions are not sent.

I will test by moving to another zone.

[Synesso]

Text appeared when auctioned in NRo. Web Client rendering could be the culprit. Closing.

[alexmk92]

@Synesso this is actually a problem with service-collection that I need to address. I built a case that stops the rendering of a line if it already exists in the cache in the last 5 minutes to stop multiple clients streaming the same lines. If a line is rejected it currently does not get pushed to service-relay which is the realtime communication layer between the server/front end. I may need to rethink my approach to always push the auction line to service-relay but prevent its parsing when saved to the DB, if I simply push to service-relay and more than 1 client is streaming the duplicate auction lines will appear in the stream.

I'm reopening this for when I have time to investigate, I'll probably add a second cache for auction lines and set it to 15 seconds to prevent dupes but still have lines that do not need their data passing to be served to service-relay.

Thanks for pointing this out!