Auction House 'No Applicable Entries' #6633
-
|
AH was fine until I updated from the latest LSB git, now all the sections say 'No Applicable Entries' even after listing items. Could anyone shed some light on this? |
Beta Was this translation helpful? Give feedback.
Replies: 9 comments 6 replies
-
|
I'll see about testing on windows in the morning |
Beta Was this translation helpful? Give feedback.
-
|
set? It seems to work for me -- see these crystal listings -- |
Beta Was this translation helpful? Give feedback.
-
|
I checked that, OMIT_NO_HISTORY is false~ I see the items in the SQL as well. |
Beta Was this translation helpful? Give feedback.
-
|
yeah i'll have to check windows in the morning. I just rewrote the networking portion of search, but not the actual search algorithms but I don't see why it would be OS dependent... |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for getting back to me, totally stumped atm~ |
Beta Was this translation helpful? Give feedback.
-
|
For now you could revert back a couple commits and build the old search. It's fully compatible with the current version of LSB, there were no other changes other than the application itself |
Beta Was this translation helpful? Give feedback.
-
|
I just tested this myself with a fire crystal, I can see it listed but get the same error. Running Win 10 and 97316d9. I can see the sale status for the price listed, just not able to purchase. Also using the !ah command gives same results. |
Beta Was this translation helpful? Give feedback.
-
|
I added some logging to see what was going on with packets, sockets, etc. - All seems normal: This is just: I was suspecting that the socket might not be being kept open (on Windows) and the reply never makes it back to the client, so I stepped through this block: // clang-format off
DebugSockets(fmt::format("async_write: Sending packet to IP {} ({} bytes)", ipAddress, length));
asio::async_write(socket_, asio::buffer(data_, length),
[this, self = shared_from_this()](std::error_code ec, std::size_t /*length*/)
{The client doesn't respond in the AH window until the completion handler (the lambda) starts firing, so the docket is alive and data has been sent. My test is somewhat broken given that my AH is empty, so I get no results when I search for an item while trying to list it, but the AH also fails to list my item when I set the price and submit. When I submit there is no activity in the log with my extra logging - fully none |
Beta Was this translation helpful? Give feedback.
-
|
I believe I am also experiencing this, my partner listed two things, I can see them in the db, but can't get the results to show up when searching.
I can check my omit history settings (don't recall off the top of my head, but I don't think I changed them from the default), but I was just starting to debug this myself.
Ubuntu 24.04 and I am definitely running the new async search (don't have the commit handy, apologies).
…On Thu, Jan 2, 2025, 05:17 Zach Toogood ***@***.***> wrote:
I added some logging to see what was going on with packets, sockets, etc.
- All seems normal:
[01/02/25 10:05:03:101][search][info] starting io_context (SearchServer::SearchServer:112)
[01/02/25 10:06:09:718][search][debug] New connection from IP 127.0.0.1 (search_handler::search_handler:42)
[01/02/25 10:06:09:718][search][debug] Checking if IP is in use: 127.0.0.1 (search_handler::isIPAddressInUse:816)
[01/02/25 10:06:09:718][search][debug] Adding IP to active set: 127.0.0.1 (search_handler::addToUsedIPAddresses:862)
[01/02/25 10:06:09:839][search][debug] async_read_some: Received packet from IP 127.0.0.1 (268 bytes) (search_handler::do_read::<lambda_1>::operator ():97)
[01/02/25 10:06:09:839][search][debug] Decrypting packet from IP 127.0.0.1 (268 bytes) (search_handler::decrypt:130)
[01/02/25 10:06:09:839][search][debug] Validating packet from IP 127.0.0.1 (268 bytes) (search_handler::validatePacket:177)
[01/02/25 10:06:09:839][search][info] Search Request: AH_HISTORY_SINGLE (5), size: 268, ip: 127.0.0.1 (search_handler::read_func:240)
[01/02/25 10:06:09:839][search][debug]
00 00 00 00 00 00 00 00 00 00 80 85 00 00 00 00
96 40 00 00 00 00 00 00 96 40 00 00 00 00 03 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 (DebugPrintPacket:311)
[01/02/25 10:06:09:839][search][debug] Encrypting packet to IP 127.0.0.1 (60 bytes) (search_handler::encrypt:153)
[01/02/25 10:06:09:840][search][debug] async_write: Sending packet to IP 127.0.0.1 (60 bytes) (search_handler::do_write:112)
[01/02/25 10:06:09:840][search][debug] Connection from IP 127.0.0.1 closed (search_handler::~search_handler:77)
[01/02/25 10:06:09:840][search][debug] Removing IP from active set: 127.0.0.1 (search_handler::removeFromUsedIPAddresses:839)
This is just: !ah, try to put an item up for sale, it'll try and go get
that item's price history while you set your price.
I was suspecting that the socket might not be being kept open (on Windows)
and the reply never makes it back to the client, so I stepped through this
block:
// clang-format off
DebugSockets(fmt::format("async_write: Sending packet to IP {} ({} bytes)", ipAddress, length));
asio::async_write(socket_, asio::buffer(data_, length),
[this, self = shared_from_this()](std::error_code ec, std::size_t /*length*/)
{
The client doesn't respond in the AH window until the completion handler
(the lambda) starts firing, so the docket is alive and data has been sent.
My test is somewhat broken given that my AH is empty, so I get no results
when I search for an item while trying to list it, but the AH also fails to
list my item when I set the price and submit. When I submit there is no
activity in the log with my extra logging - fully none
—
Reply to this email directly, view it on GitHub
<#6633 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALVGKSKM4UZ67JPYXUR2RD2IUG2FAVCNFSM6AAAAABUPPERQWVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZRGU3TGOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
I found the bug, working on a fix Oddly, it seems running ffxi through wine is more compliant about the packets than on windows. We're supposed to wait on a reply for each packet sent out but apparently on wine that doesn't matter...? |
Beta Was this translation helpful? Give feedback.
-
|
Fix here #6640 (hopefully) |
Beta Was this translation helpful? Give feedback.
-
|
I rebuilt server and applied Winter's fix, so far so good for the AHbot. |
Beta Was this translation helpful? Give feedback.
-
|
Excellent news, thanks for reporting back here |
Beta Was this translation helpful? Give feedback.
-
|
I can confirm that running on your branch with commit 72ff7a9, the AH is now working (tbf, I only have 2 things for sale but...):
Thanks for fixing this so quickly! |
Beta Was this translation helpful? Give feedback.
Fix here #6640 (hopefully)